mirror of
https://git.haproxy.org/git/haproxy.git/
synced 2025-09-23 14:51:27 +02:00
15dbedd63d
It was reported in issue #13 that a GOAWAY frame was sent on timeout even if no SETTINGS frame was sent. The approach imagined by then was to track the fact that a SETTINGS frame was already sent to avoid this, but that's already what is done through the state, though it doesn't stand due to the fact that we switch the frame to the error state. Thus instead what we're doing here is to instead set the GOAWAY_FAILED flag in h2c_error() before switching to the ERROR state when the state indicates we've not yet sent settings, and refrain from sending anything from the h2c_send_goaway_error() function for such states. This could be backported to all versions where it applies well.
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)