mirror of
https://git.haproxy.org/git/haproxy.git/
synced 2025-09-23 06:41:32 +02:00
52fc0cbaad
When we want to establish a tunnel on a side, we wait to have flush all data from the buffer. At this stage the other side is at least in DONE state. But there is no real reason to wait. We are already in DONE state on its side. So all the HTTP message was already forwarded or planned to be forwarded. Depending on the scheduling if the mux already started to transfer tunneled data, these data may block the switch in TUNNEL state and thus block these data infinitly. This bug exists since the early days of HTX. May it was mandatory but today it seems useless. But I honestly don't remember why this prerequisite was added. So be careful during the backports. This patch should be backported with caution. At least as far as 2.4. For 2.2 and 2.0, it seems to be mandatory too. But a review must be performed.
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)