mirror of
https://git.haproxy.org/git/haproxy.git/
synced 2025-11-28 14:21:00 +01:00
5b78cbae77
When an error on the H2 connection is detected when sending data, only a pending error is reported, waiting for an error or a shutdown on the read side. However if a shutdown was already received, the pending error is switched to a definitive error. At this stage, we must also wait to have flushed the demux buffer. Otherwise, if some data must still be demux, messages for one or more streams may be truncated. There is already the flag H2_CF_END_REACHED to know a shutdown was received and we no longer progress on demux side (buffer empty or data truncated). On sending side, we should use this flag instead to report a definitive error. This patch is part of a series that should fix a bug reported in issue #2388 (#2388#issuecomment-1855735144). Backport instructions will be shipped in the last commit of the series.
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)