mirror of
https://git.haproxy.org/git/haproxy.git/
synced 2025-09-23 06:41:32 +02:00
48726b78e5
When an HTTP response is received, at the stream-interface level, if a L7 retry must be triggered because of the status code, the response is trashed and a read error is reported on the response channel. Then the stream handles this error and perform the retry. Except if the maximum connection retries is reached. In this case, an error is reported. Because the server response was already trashed by the stream-interface, a generic 502 error is returned to the client instead of the server's one. Now, the stream-interface triggers a L7 retry only if the maximum connection retries is not already reached. Thus, at the end, the last server's response is returned. This patch must be backported to 2.1 and 2.0. It should fix the issue #439.
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)