mirror of
http://git.haproxy.org/git/haproxy.git/
synced 2025-03-31 15:47:10 +00:00
6c9bbb2265
The option http-tunnel disables any HTTP processing past the first transaction. In HTX, it works for full h1 transactions. As for the legacy HTTP, it is a workaround, but it works. But it is impossible to make it works with an h2 connection. In such case, it has no effect, the stream is closed at the end of the transaction. So to avoid any inconsistancies between h1 and h2 connections, this option is now always ignored when the HTX is enabled. It is also a good opportinity to deprecate an old and ugly option. A warning is emitted during HAProxy startup to encourage users to remove this option. Note that in legacy HTTP, this option only works with full h1 transactions too. If an h2 connection is established on a frontend with this option enabled, it will have no effect at all. But we keep it for the legacy HTTP for compatibility purpose. It will be removed with the legacy HTTP. So to be short, if you have to really (REALLY) use it, it will only work for legacy HTTP frontends with H1 clients. The documentation has been updated accordingly. This patch must be backported to 1.9. It is not strictly speaking required but it will ease futur backports. |
||
|---|---|---|
| .. | ||
| design-thoughts | ||
| internals | ||
| lua-api | ||
| 51Degrees-device-detection.txt | ||
| acl.fig | ||
| architecture.txt | ||
| close-options.txt | ||
| coding-style.txt | ||
| configuration.txt | ||
| cookie-options.txt | ||
| DeviceAtlas-device-detection.txt | ||
| gpl.txt | ||
| haproxy.1 | ||
| intro.txt | ||
| lgpl.txt | ||
| linux-syn-cookies.txt | ||
| lua.txt | ||
| management.txt | ||
| netscaler-client-ip-insertion-protocol.txt | ||
| network-namespaces.txt | ||
| peers-v2.0.txt | ||
| peers.txt | ||
| proxy-protocol.txt | ||
| queuing.fig | ||
| regression-testing.txt | ||
| SPOE.txt | ||