mirror of
http://git.haproxy.org/git/haproxy.git/
synced 2025-03-05 02:49:01 +00:00
57a374131c
Since we've fixed the way URIs are handled in 2.1, some users have started to experience inconsistencies in "balance uri" between requests received over H1 and the same ones received over H2. This is caused by the fact that H1 rarely uses absolute URIs while H2 always uses them. Similar issues were reported already around replace-uri etc, leading to "pathq" recently being introduced, so this isn't new. Here what this patch does is add a new option to "balance uri" to indicate that the hashing should only start at the path and not cover the authority. This makes H1 relative URIs and H2 absolute URI hashes equally again. Some extra options could be added to normalize URIs by always hashing the authority (or host) in front of them, which would make sure that both absolute and relative requests provide the same hash. This is left for later if needed. |
||
|---|---|---|
| .. | ||
| 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 | ||
| seamless_reload.txt | ||
| SOCKS4.protocol.txt | ||
| SPOE.txt | ||
| WURFL-device-detection.txt | ||