365cd65b68
It was inherited from the legacy HTTP mode, but the message parsing is handled by the underlying mux now. Thus, if a message is in HTTP_MSG_ERROR state, it is just an analysis error and not a parsing error. So there is no reason to block the HTTP sample fetch evaluation in this case. This patch could be backported in all stable versions (For the 2.0, only the htx part must be updated). (cherry picked from commit 5aab0a30c5090f54b3e797cb1644b3215d9d6c3c) Signed-off-by: Willy Tarreau <w@1wt.eu> (cherry picked from commit 6efffd09cff6da32986eef24711ab7e23204c59c) Signed-off-by: Christopher Faulet <cfaulet@haproxy.com>
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)