mirror of
https://git.haproxy.org/git/haproxy.git/
synced 2025-09-21 22:01:31 +02:00
47ed1181f2
When no client timeout is defined in the configuration, QCC timeout task is never allocated. However, a NULL timeout task is also used as a criteria in qcc_is_dead() to consider that the MUX instance should be released as timeout stroke earlier. This bug causes every connection to be closed by haproxy side with a CONNECTION_CLOSE. This is notable when using several streams per connection with only the first stream completed and the others failed. To fix this, change timeout task allocation policy. It is now always allocated. This means that if no timeout is defined, it will never be run. This is not considered a waste of resource as no timeout in the configuration is considered as an exception case. However, this has the advantage to simplify the rest of the code which can now check for the task instance without having an extra check on the timeout value. This bug is labelled as minor as it only occurs if no timeout client is defined which reports warning on startup as it may caused unexpected behavior. This bug should be backported up to 2.6.
The HAProxy documentation has been split into a number of different files for ease of use. Please refer to the following files depending on what you're looking for : - INSTALL for instructions on how to build and install HAProxy - BRANCHES to understand the project's life cycle and what version to use - LICENSE for the project's license - CONTRIBUTING for the process to follow to submit contributions The more detailed documentation is located into the doc/ directory : - doc/intro.txt for a quick introduction on HAProxy - doc/configuration.txt for the configuration's reference manual - doc/lua.txt for the Lua's reference manual - doc/SPOE.txt for how to use the SPOE engine - doc/network-namespaces.txt for how to use network namespaces under Linux - doc/management.txt for the management guide - doc/regression-testing.txt for how to use the regression testing suite - doc/peers.txt for the peers protocol reference - doc/coding-style.txt for how to adopt HAProxy's coding style - doc/internals for developer-specific documentation (not all up to date)