tree 4ca60fe47825123d1803b583d8d62772d6af8f35
parent 9580d16e4018e9d2db1a9fcad21ba17c367f0436
author Willy Tarreau <w@1wt.eu> 1337503126 +0200
committer Willy Tarreau <w@1wt.eu> 1337503126 +0200
encoding latin1

BUG/MINOR: stop connect timeout when connect succeeds

If the connect succeeds exactly at the same millisecond as the connect
timeout is supposed to strike, the timeout is still considered while
data may have already be sent. This results in a new connection attempt
with no data and with the response being lost.

Note that in practice the only real-world situation where this is observed
is when connect timeouts are extremely low, too low for safe operations.
This bug was encountered with a 1ms connect timeout.

It is also present on 1.4 and needs to be fixed there too.