552601d5fd
This bug was introduced by the previous commit (9f5382e45 Revert "MEDIUM: http-ana: Deal with L7 retries in HTTP analysers") because I failed the revert. On L7 retry, if the maximum connection retries is reached, an error must be return to the client. Depending the situation, it may be a 502-Bad-Gateway (empty-response or junk-response), a 504-Gateway-Timeout (response-timeout) or a 425-Too-Early (0rtt-rejected). But contrary to what the comment says, the do_l7_retry() function always returns a success. Note it is not a problem for L7 retries on the response status code because the stream-interface already takes care to have not reached the maximum connection retries counter to trigger a L7 retry. This patch must be backported to 2.4 because the commit must also be backported to 2.4.
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)