mirror of
http://git.haproxy.org/git/haproxy.git
synced 2026-02-09 22:42:39 +02:00
97b3a61449
When a TCP stream is first upgraded to H1 and then to H2, we must be sure to inhibit any connect and to properly handle the TCP stream destruction. When the TCP stream is upgraded to H1, the HTTP analysers are set. Thus http_wait_for_request() is called. In this case, the server connection must be blocked, waiting for the request analysis. Otherwise, a server may be assigned to the stream too early. It is especially a problem if the stream is finally destroyed because of an implicit upgrade to H2. In this case, the stream processing must be properly aborted to not have a stalled stream. Thus, if a shutdown is detected in http_wait_for_request() when an HTTP upgrade is performed, the stream is aborted. It is a 2.4-specific bug. No backport is needed.
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)