mirror of
https://git.haproxy.org/git/haproxy.git/
synced 2026-02-26 19:52:06 +01:00
2c4dfaeff6
Since we dropped support for legacy mode, it's not the stream which deals with the connection but the mux, and there's no point in closing the client connection after most internal status codes. For example if the client gets a 401 or a 503 because a server doesn't respond, it makes no sense forcing the connection to close after reporting this status, because it's already done by the mux if the client asks for it or is not compatible with keep-alive. This current state was inherited from the early days but is still limiting the amount of client-side connection reuse in a number of circumstances (typically server-side errors). This change was planned for 2.1 but forgotten. The status codes for which the connection is not closed anymore are those that do not depend on the client side connection itself, which are all except 400 and 408. This could be backported to 2.1 but not further, in order to make sure legacy and HTX behave strictly similarly.
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)