mirror of
https://github.com/haproxy/haproxy.git
synced 2026-03-03 13:50:26 -05:00
HAProxy - Load balancer
b8d148a93f
204 and 304 HTTP responses must no contain message body. These status codes are correctly handled when the responses are received from a server. But there is no specific processing for internal HTTP reponses (errorfile and http replies). Now, when errorfiles or an http replies are parsed during the configuration parsing, an error is triggered if a 204/304 message contains a body. An extra check is also performed to ensure the body length matches the announce content-length. This patch should fix the issue #891. It must be backported as far as 2.0. For 2.1 and 2.0, only the http_str_to_htx() function must be fixed. http_parse_http_reply() function does not exist. |
||
|---|---|---|
| .github | ||
| contrib | ||
| doc | ||
| examples | ||
| include | ||
| reg-tests | ||
| scripts | ||
| src | ||
| tests | ||
| .cirrus.yml | ||
| .gitattributes | ||
| .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)