mirror of
https://git.haproxy.org/git/haproxy.git/
synced 2025-09-22 14:21:25 +02:00
57a1816fae
Christopher found another issue in the H2 backend implementation that results from a miss in the H2 spec: the processing of a HEADERS frame is always permitted in IDLE state, but this doesn't make sense on the response path! And here when facing such a frame, we try to decode it while we didn't allocate any stream, so we end up trying to fill the idle stream's buffer (read-only) and crash. What we're doing here is that if we get a HEADERS frame in IDLE state from a server, we terminate the connection with a PROTOCOL_ERROR. No such transition seems to be permitted by the spec but it seems to be the only sane solution. This fix must be backported as far as 1.9. Note that in 2.0 and earlier there's no h2_frame_check_vs_state() function, instead the check is inlined in h2_process_demux().
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)