mirror of
https://git.haproxy.org/git/haproxy.git/
synced 2026-02-15 06:11:10 +01:00
eb346074bb
When message headers are parsed and an HTX start-line is created, if we detect the response must not have any payload, a specific flag must be set on the HTX start-line. It happens for instance for response to HEAD requests. This flag is useb by the multiplexers to know response payload, if any, must be silently skipped. This was not performed when h2 HEADERS frames were decoded. This HTX flag was specifically added to fix a bug when the splicing is inuse. Thus the H2 multiplexer was not concerned. Because the mux-to-mux fast-forwarding will be introduced, it is important handle this flag in the H2 multiplexer too.
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)