mirror of
https://git.haproxy.org/git/haproxy.git/
synced 2025-09-21 05:41:26 +02:00
da24bcfad3
A recent series of commit have been introduced to rework error generation on QUIC MUX side. Now, all MUX/APP functions uses qcc_set_error() to set the flag QC_CF_ERRL on error. Then, this flag is converted to QC_CF_ERRL_DONE with a CONNECTION_CLOSE emission by qc_send(). This has the advantage of centralizing the CONNECTION_CLOSE generation in one place and reduces the link between MUX and quic-conn layer. However, we must now ensure that every qcc_set_error() call is followed by a QUIC MUX tasklet to invoke qc_send(). This was not the case, thus when there is no active transfer, no CONNECTION_CLOSE frame is emitted and the connection remains opened. To fix this, add a tasklet_wakeup() directly in qcc_set_error(). This is a brute force solution as this may be unneeded when already in the MUX tasklet context. However, it is the simplest solution as it is too tedious for the moment to list all qcc_set_error() invocation outside of the tasklet. This must be backported up 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)