mirror of
https://git.haproxy.org/git/haproxy.git/
synced 2025-09-23 06:41:32 +02:00
2954bcc1e8
The HTTP message must remains in BODY state during the analysis, to be able to report accurate termination state in logs. It is also important to know the HTTP analysis is still in progress. Thus, when we are waiting for the message payload, the message is no longer switch to DATA state. This was used to not process "Expect: " header at each evaluation. But thanks to the previous patch, it is no long necessary. This patch also fixes a bug in the lua filter api. Some functions must be called during the message analysis and not during the payload forwarding. It is not valid to try to manipulate headers during the forward stage because headers are already forwarded. We rely on the message state to detect errors. So the api was unusable if a "wait-for-body" action was used. This patch shoud fix the issue #2093. It relies on the commit: * MINOR: http-ana: Add a HTTP_MSGF flag to state the Expect header was checked Both must be backported as far as 2.5.
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)