tree 051b9dac3ccb1bc9e38b34ef7111501a2bfb4505
parent 3f527197cd7d34fc1975862f346e2d778dc44dc2
author Christopher Faulet <cfaulet@haproxy.com> 1607539598 +0100
committer Christopher Faulet <cfaulet@haproxy.com> 1607683695 +0100

BUG/MINOR: tcpcheck: Don't rearm the check timeout on each read

The check timeout is used to limit a health-check execution. By default
inter timeout is used. But when defined the check timeout is used. In this
case, the inter timeout (or connect timeout) is used for the connection
establishment only. And the check timeout for the health-check
execution. Thus, it must be set after a successfull connect. It means it is
rearm at the end of each connect rule.

This patch with the previous one (BUG/MINOR: http-check: Use right condition
to consider HTX message as full) should solve the issue #991. It must be
backported as far as 2.2. On the 2.3 and 2.2, there are 2 places were the
connection establishement is handled. The check timeout must be set on both.