ca4fd73938
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. |
||
|---|---|---|
| .. | ||
| basic.vtc | ||
| caching_rules.vtc | ||
| expires.vtc | ||
| if-modified-since.vtc | ||
| if-none-match.vtc | ||
| post_on_entry.vtc | ||
| sample_fetches.vtc | ||
| vary.vtc | ||
| vary_accept_encoding.vtc | ||