mirror of
https://git.haproxy.org/git/haproxy.git/
synced 2025-09-25 07:41:36 +02:00
5647fbacdf
CF_FL_ANALYZE flag is used to know a channel is filtered. It is important to synchronize request and response channels when the filtering ends. However, it is possible to call all request analyzers before starting the filtering on the response channel. This means flt_end_analyze() may be called for the request channel before flt_start_analyze() on the response channel. Thus because CF_FL_ANALYZE flag is not set on the response channel, we consider the filtering is finished on both sides. The consequence is that flt_end_analyze() is not called for the response and backend filters are unregistered before their execution on the response channel. It is possible to encounter this bug on TCP frontend or CONNECT request on HTTP frontend if the client shutdown is reveiced with the first read. To fix this bug, CF_FL_ANALYZE is set when filters are attached to the stream. It means, on the request channel when the stream is created, in flt_stream_start(). And on both channels when the backend is set, in flt_set_stream_backend(). This patch must be backported as far as 1.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)