mirror of
https://git.haproxy.org/git/haproxy.git/
synced 2025-09-22 06:11:32 +02:00
fbdf90a6f9
The mux-h1 doesn't properly propagate end of streams to the application layer when requests are pipelined. This is visible by launching h2load in h1 mode with -m greater than 1 : issuing Ctrl-C has no effect until the client timeout expires. The reason is that among the checks conditionning the reporting of the end of stream status and waking up the streams, is a test on the presence of remaining input data in the demux. But with pipelining, these data may be present for another stream and should not prevent the end of stream condition from being reported. This patch addresses this issue by introducing a new function "h1s_data_pending" which returns a boolean indicating if there are in the demux buffer any data for the current stream. That is, if the stream is in H1_MSG_DONE state, there are never any data for it. And if it's in a different state, then the demux buffer is checked. This replaces the tests on b_data(&h1c->ibuf) and correctly allows end of streams to be reported at the end of requests. It's worth noting that 1.9 doesn't suffer from this issue but it possibly isn't completely immune either given that the same tests are present.
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 - 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)