mirror of
https://git.haproxy.org/git/haproxy.git/
synced 2026-01-20 17:41:06 +01:00
2ee5c8b3dd
STREAM frames which are not acknowledged in order are inserted in ->tx.acked_frms tree ordered by the STREAM frame offset values. Then, they are consumed in order by qcs_try_to_consume(). But, when we retransmit frames, we possibly have to insert the same STREAM frame node (with the same offset) in this tree. The problem is when they have different lengths. Unfortunately the restransmitted frames are not inserted because of the tree nature (EB_ROOT_UNIQUE). If the STREAM frame which has been successfully inserted has a smaller length than the retransmitted ones, when it is consumed they are tailing bytes in the STREAM (retransmitted ones) which indefinitively remains in the STREAM TX buffer which will never properly be consumed, leading to a blocking state. At this time this may happen because we sometimes build STREAM frames with null lengths. But this is another issue. The solution is to use an EB_ROOT tree to support the insertion of STREAM frames with the same offset but with different lengths. As qcs_try_to_consume() support the STREAM frames retransmission this modification should not have any impact.
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)