haproxy/reg-tests/cache
Remi Tricot-Le Breton ca4fd73938 BUG/MINOR: cache: A 'max-age=0' cache-control directive can be overriden by a s-maxage
When a s-maxage cache-control directive is present, it overrides any
other max-age or expires value (see section 5.2.2.9 of RFC7234). So if
we have a max-age=0 alongside a strictly positive s-maxage, the response
should be cached.

This bug was raised in GitHub issue #2203.
The fix can be backported to all stable branches.
2023-07-04 22:15:00 +02:00
..
basic.vtc REGTESTS: Remove REQUIRE_VERSION=1.9 from all tests 2023-01-05 09:11:38 +01:00
caching_rules.vtc BUG/MINOR: cache: A 'max-age=0' cache-control directive can be overriden by a s-maxage 2023-07-04 22:15:00 +02:00
expires.vtc REGTESTS: extend the default I/O timeouts and make them overridable 2021-11-18 17:57:11 +01:00
if-modified-since.vtc REGTESTS: cache: Use rxresphdrs to only get headers for 304 responses 2023-02-22 16:12:45 +01:00
if-none-match.vtc REGTESTS: cache: Use rxresphdrs to only get headers for 304 responses 2023-02-22 16:12:45 +01:00
post_on_entry.vtc REGTESTS: extend the default I/O timeouts and make them overridable 2021-11-18 17:57:11 +01:00
sample_fetches.vtc REGTESTS: Remove REQUIRE_VERSION=1.9 from all tests 2023-01-05 09:11:38 +01:00
vary_accept_encoding.vtc REGTESTS: extend the default I/O timeouts and make them overridable 2021-11-18 17:57:11 +01:00
vary.vtc REGTESTS: extend the default I/O timeouts and make them overridable 2021-11-18 17:57:11 +01:00