How does a cache calculate the freshness lifetime of a stored response?
q10 · partial · HTTP 200 · index 0fc1763d6701
1 of 8 drafted claims were not supported by the passages they cited and have been withdrawn.
What survived the check — each claim with the passage that supports it
If the cache is shared and the s-maxage response directive is present, the cache uses the s-maxage value as the freshness lifetime.
rfc9111#4.2.1 — 100% of
this claim's content words appear in that passage.
If the max-age response directive is present, the cache uses the max-age value as the freshness lifetime.
rfc9111#4.2.1 — 100% of
this claim's content words appear in that passage.
If the Expires response header field is present, the cache uses the Expires value minus the Date response header field value as the freshness lifetime, using the time the message was received if Date is not present.
rfc9111#4.2.1 — 100% of
this claim's content words appear in that passage.
If no explicit expiration time is present in the response, a heuristic freshness lifetime might be applicable.
rfc9111#4.2.1 — 100% of
this claim's content words appear in that passage.
When more than one value is present for a given freshness directive, the cache should either use the first occurrence or consider the response stale.
rfc9111#4.2.1 — 100% of
this claim's content words appear in that passage.
If freshness directives conflict, the cache should honor the most restrictive directive.
rfc9111#4.2.1 — 88% of
this claim's content words appear in that passage.
Caches are encouraged to consider responses with invalid freshness information to be stale.
rfc9111#4.2.1 — 100% of
this claim's content words appear in that passage.
What was withdrawn — and the rule that withdrew it
A cache calculates a response's freshness lifetime by evaluating the freshness-lifetime rules in order and using the first rule that matches.
literal not in passagerfc9111#4.2.1 does not contain freshness-lifetime.
What was retrieved — the passages the drafter saw, and nothing else
| rank | section | score |
|---|---|---|
| 1 | RFC 9111 Section 4.2.1: Calculating Freshness Lifetime |
0.7818 |
| 2 | RFC 9111 Section 4.2: Freshness |
0.7114 |
| 4 | RFC 9111 Section 4.2.2: Calculating Heuristic Freshness |
0.6621 |
| 5 | RFC 9111 Section 1: Introduction |
0.6486 |
| 6 | RFC 9111 Section 4: Constructing Responses from Caches |
0.6327 |
| 7 | RFC 9111 Section 3: Storing Responses in Caches |
0.6213 |
| 9 | RFC 9111 Section 4.3.4: Freshening Stored Responses upon Validation |
0.6069 |
| 10 | RFC 9111 Section 4.3.5: Freshening Responses with HEAD |
0.6049 |