c1d714156e
Most of the time STREAM frames emitted by QUIC MUX have some data in it. However, it is possible to use an empty frame when a delayed FIN must be transferred. Recently, QUIC MUX send callback notification has been refactored. Now, this callback is blindly called by quic_conn lower layer each time a STREAM frame is built into a newly Tx packet. QUIC MUX is responsible to ensure the notified frame corresponds to newly emitted data or retransmission. Offsets are used for this comparison, but this requires special care for empty FIN frames. Sadly, the comparison written to determine if an empty FIN frame was sent for the first time or retransmitted is not correct. This caused such frame to always be dismissed as retransmission in QUIC MUX sent callback. This prevented the related QCS instance to be removed from the send_list, causing qcc_io_send() to retry a new emission. This was finally interrupted by the BUG_ON() assertion to prevent an infinite loop. Fix this crash by updating the condition in QUIC MUX send callback. For empty STREAM frame, it is sufficient to check if QC_SF_FIN_STREAM was already removed or not to detect a retransmission. Indeed, empty STREAM frames are never used outside of delayed FIN reporting. No need to backport. This crash was introduced in the current dev branch by the following commit. d7f4e5abf0b7129329d0ea716c104474fd934bc6 MEDIUM: quic: strengthen MUX send notification
HAProxy
HAProxy is a free, very fast and reliable reverse-proxy offering high availability, load balancing, and proxying for TCP and HTTP-based applications.
Installation
The INSTALL file describes how to build HAProxy. A list of packages is also available on the wiki.
Getting help
The discourse and the mailing-list are available for questions or configuration assistance. You can also use the slack or IRC channel. Please don't use the issue tracker for these.
The issue tracker is only for bug reports or feature requests.
Documentation
The HAProxy documentation has been split into a number of different files for ease of use. It is available in text format as well as HTML. The wiki is also meant to replace the old architecture guide.
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)
License
HAProxy is licensed under GPL 2 or any later version, the headers under LGPL 2.1. See the LICENSE file for a more detailed explanation.