forked/hyper
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix(client): Handle connection error

Browse Source 
Previously, the connection would be kept alive if there was a connect
error. Now it's closed immediately.
This commit is contained in:
Joe Wilm
2016-10-11 14:20:30 -07:00
parent 27a480c327
commit ef4c08c9e9
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
src/client/mod.rs
View File

@@ -483,11 +483,11 @@ where C: Connect,
if let Some(err) = seed.1.take_socket_error().err() { if let Some(err) = seed.1.take_socket_error().err() {
debug!("error while connecting: {:?}", err); debug!("error while connecting: {:?}", err);
scope.pop_queue(&seed.0).map(move |mut queued| queued.handler.on_error(::Error::Io(err))); scope.pop_queue(&seed.0).map(move |mut queued| queued.handler.on_error(::Error::Io(err)));
rotor::Response::done()
} else { } else {
trace!("connecting is_error, but no socket error"); trace!("connecting is_error, but no socket error");
rotor::Response::ok(ClientFsm::Connecting(seed))
} }
rotor::Response::done()
} else if events.is_writable() { } else if events.is_writable() {
if scope.queue.contains_key(&seed.0) { if scope.queue.contains_key(&seed.0) {
trace!("connected and writable {:?}", seed.0); trace!("connected and writable {:?}", seed.0);