mirror of
https://git.haproxy.org/git/haproxy.git/
synced 2025-08-07 23:56:57 +02:00
da3adebd06
HAproxy only handles "chunked" encoding internally. Because it is a gateway, we stated it was not a problem if unknown encodings were applied on a message because it is the recipient responsibility to accept the message or not. And indeed, it is not a problem if both the client and the server connections are using H1. However, Transfer-Encoding headers are dropped from H2 messages. It is not a problem for chunk-encoded payload because dechunking is performed during H1 parsing. But, for any other encodings, the xferred H2 message is invalid. It is also a problem for internal payload manipulations (lua, filters...). Because the TE request headers are now sanitiezd, unsupported encoding should not be used by servers. Thus it is only a problem for the request messages. For this reason, such messages are now rejected. And if a server decides to use an unknown encoding, the response will also be rejected. Note that it is pretty uncommon to use other encoding than "chunked" on the request payload. So it is not necessary to backport it. This patch should fix the issue #1301. No backport is needed. |
||
|---|---|---|
| .github | ||
| addons | ||
| admin | ||
| dev | ||
| doc | ||
| examples | ||
| include | ||
| reg-tests | ||
| scripts | ||
| src | ||
| tests | ||
| .cirrus.yml | ||
| .gitattributes | ||
| .gitignore | ||
| .mailmap | ||
| .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)