mirror of
http://git.haproxy.org/git/haproxy.git/
synced 2024-12-22 04:10:48 +00:00
3bc6af417d
RFC 7231#5.3.4 makes a difference between a completely missing 'accept-encoding' header and an 'accept-encoding' header without any values. This case was already correctly handled by accident, because an empty accept encoding does not match any known encoding. However this resulted in the 'other' encoding being added to the bitmap. Usually this also succeeds in serving cached responses, because the cached response likely has no 'content-encoding', thus matching the identity case instead of not serving the response, due to the 'other' encoding. But it's technically not 100% correct. Fix this by special-casing 'accept-encoding' values with a length of zero and extend the test to check that an empty accept-encoding is correctly handled. Due to the reasons given above the test also passes without the change in cache.c. Vary support was added in HAProxy 2.4. This fix should be backported to 2.4+. |
||
|---|---|---|
| .. | ||
| basic.vtc | ||
| caching_rules.vtc | ||
| expires.vtc | ||
| if-modified-since.vtc | ||
| if-none-match.vtc | ||
| post_on_entry.vtc | ||
| sample_fetches.vtc | ||
| vary_accept_encoding.vtc | ||
| vary.vtc | ||