mirror of
http://git.haproxy.org/git/haproxy.git/
synced 2025-02-11 07:58:32 +00:00
e4421dec7e
The accept-encoding part of the secondary key (vary) was only built out of the first occurrence of the header. So if a client had two accept-encoding headers, gzip and br for instance, the key would have been built out of the gzip string. So another client that only managed gzip would have been sent the cached resource, even if it was a br resource. The http_find_header function is now called directly by the normalizers so that they can manage multiple headers if needed. A request that has more than 16 encodings will be considered as an illegitimate request and its response will not be stored. This fixes GitHub issue #987. It does not need any backport. |
||
|---|---|---|
| .. | ||
| basic.vtc | ||
| caching_rules.vtc | ||
| expires.vtc | ||
| if-modified-since.vtc | ||
| if-none-match.vtc | ||
| post_on_entry.vtc | ||
| sample_fetches.vtc | ||
| vary.vtc | ||