What does the s-maxage response directive do, and which caches does it apply to?
q12 · grounded · HTTP 200 · index 0fc1763d6701
What survived the check — each claim with the passage that supports it
The s-maxage response directive applies to a shared cache.
rfc9111#5.2.2.10 — 83% of
this claim's content words appear in that passage.
For a shared cache, the s-maxage response directive overrides the maximum age specified by either the max-age directive or the Expires header field.
rfc9111#5.2.2.10 — 100% of
this claim's content words appear in that passage.
For a shared cache, the s-maxage response directive incorporates the semantics of the proxy-revalidate response directive.
rfc9111#5.2.2.10 — 100% of
this claim's content words appear in that passage.
A shared cache MUST NOT reuse a stale response with s-maxage to satisfy another request until it has been successfully validated by the origin.
rfc9111#5.2.2.10 — 100% of
this claim's content words appear in that passage.
The s-maxage response directive permits a shared cache to reuse a response to a request containing an Authorization header field, subject to the directive's requirements on maximum age and revalidation.
rfc9111#5.2.2.10 — 100% of
this claim's content words appear in that passage.
What was retrieved — the passages the drafter saw, and nothing else
| rank | section | score |
|---|---|---|
| 1 | RFC 9111 Section 5.2.2.10: s-maxage |
0.6373 |
| 2 | RFC 9111 Section 3: Storing Responses in Caches |
0.6315 |
| 3 | RFC 9111 Section 5.2.2: Response Directives |
0.6048 |
| 4 | RFC 9111 Section 5.2.1: Request Directives |
0.5938 |
| 5 | RFC 9111 Section 3.5: Storing Responses to Authenticated Requests |
0.5681 |
| 7 | RFC 9111 Section 5.2.2.3: must-understand |
0.5473 |
| 8 | RFC 9111 Section 8.2: Cache Directive Registration |
0.5437 |
| 9 | RFC 9111 Section 5.2.3: Extension Directives |
0.5305 |