linkerd2/proxy
Eliza Weisman ad073c79b9
Remove connect timeouts from Bind (#487)
Currently, the `Reconnect` middleware does not reconnect on connection errors (see  #491) and treats them as request errors. This means that when a connection timeout is wrapped in a `Reconnect`, timeout errors are treated as request errors, and the request returns HTTP 500. Since  this is not the desired behavior, the connection timeouts should be removed, at least until their errors can be handled differently.

This PR removes the connect timeouts from `Bind`, as described in https://github.com/runconduit/conduit/pull/483#issuecomment-369380003.

It removes the `CONDUIT_PROXY_PUBLIC_CONNECT_TIMEOUT_MS` environment variable, but _not_ the `CONDUIT_PROXY_PRIVATE_CONNECT_TIMEOUT_MS` variable, since this is also used for the TCP connect timeouts. If we want also want to remove the TCP connection timeouts, I can do that as well.

Closes #483. Fixes #491.
2018-03-05 15:38:20 -08:00
..
controller-grpc Turn off the `use_logging` default feature of quickcheck. (#465) 2018-02-26 16:04:58 -10:00
convert Prepare for the v0.3.0 release (#406) 2018-02-21 11:14:11 -08:00
futures-mpsc-lossy Prepare for the v0.3.0 release (#406) 2018-02-21 11:14:11 -08:00
router Use fmt::Display to format error messages in logs (#477) 2018-03-02 12:44:18 -08:00
src Remove connect timeouts from Bind (#487) 2018-03-05 15:38:20 -08:00
tests proxy: detect TCP socket hang ups from client or server (#463) 2018-03-02 10:14:54 -08:00
Cargo.toml Proxy: Update domain dep. to remove rand 0.3 dep. (#495) 2018-03-01 17:16:21 -10:00
Dockerfile Add flaky_tests feature for skipping some tests on CI (#441) 2018-02-26 10:17:53 -08:00