mirror of
https://git.haproxy.org/git/haproxy.git/
synced 2026-03-06 15:41:36 +01:00
a4bd7602f3
When a connection error is encountered during a receive, the error is not immediatly reported to the SE descriptor. We take care to process all pending input data first. However, when the error is finally reported, a fatal error is reported only if a read0 was also received. Otherwise, only a pending error is reported. With a raw socket, it is not an issue because shutdowns for read and write are systematically reported too when a connection error is detected. So in this case, the fatal error is always reported to the SE descriptor. But with a SSL socket, in case of pure SSL error, only the connection error is reported. This prevent the fatal error to go up. And because the connection is in error, no more receive or send are preformed on the socket. The mux is blocked till a timeout is triggered at the stream level, looping infinitly to progress. To fix the bug, during the demux stage, when there is no longer pending data, the read error is reported to the SE descriptor, regardless the shutdown for reads was received or not. No more data are expected, so it is safe. This patch should fix the issue #2046. It must be backported to 2.7.
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)