When may a cache use heuristic freshness?
q11 · grounded · HTTP 200 · index 0fc1763d6701
What survived the check — each claim with the passage that supports it
A cache may assign a heuristic expiration time when an explicit expiration time is not specified in the response.
rfc9111#4.2.2 — 100% of
this claim's content words appear in that passage.
A cache must not use heuristics to determine freshness when an explicit expiration time is present in the stored response.
rfc9111#4.2.2 — 100% of
this claim's content words appear in that passage.
A cache can use heuristics only on responses without explicit freshness whose status codes are defined as heuristically cacheable or that have been marked as explicitly cacheable.
rfc9111#4.2.2 — 100% of
this claim's content words appear in that passage.
When s-maxage, max-age, and Expires do not provide an explicit expiration time, a heuristic freshness lifetime might be applicable.
rfc9111#4.2.1 — 92% 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 4.2.2: Calculating Heuristic Freshness |
0.7272 |
| 3 | RFC 9111 Section 4.2: Freshness |
0.6560 |
| 5 | RFC 9111 Section 4.2.1: Calculating Freshness Lifetime |
0.6157 |
| 7 | RFC 9111 Section 1: Introduction |
0.5669 |
| 8 | RFC 9111 Section 4.3.5: Freshening Responses with HEAD |
0.5655 |
| 9 | RFC 9111 Section 6: Relationship to Applications and Other Caches |
0.5567 |