mirror of
http://git.haproxy.org/git/haproxy.git/
synced 2025-04-01 22:48:25 +00:00
haproxy public development tree
When an error file was loaded, the flag HTX_SL_F_XFER_LEN was never set on the HTX start line because of a bug. During the headers parsing, the flag H1_MF_XFER_LEN is never set on the h1m. But it was the condition to set HTX_SL_F_XFER_LEN on the HTX start-line. Instead, we must only rely on the flags H1_MF_CLEN or H1_MF_CHNK. Because of this bug, it was impossible to keep a connection alive for a response generated by HAProxy. Now the flag HTX_SL_F_XFER_LEN is set when an error file have a content length (chunked responses are unsupported at this stage) and the connection may be kept alive if there is no connection header specified to explicitly close it. This patch must be backported to 2.0 and 1.9. |
||
---|---|---|
.github/ISSUE_TEMPLATE | ||
contrib | ||
doc | ||
ebtree | ||
examples | ||
include | ||
reg-tests | ||
scripts | ||
src | ||
tests | ||
.cirrus.yml | ||
.gitignore | ||
.travis.yml | ||
BRANCHES | ||
CHANGELOG | ||
CONTRIBUTING | ||
INSTALL | ||
LICENSE | ||
MAINTAINERS | ||
Makefile | ||
README | ||
ROADMAP | ||
SUBVERS | ||
VERDATE | ||
VERSION |
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)