HTTP Caching¶
Fielding, R. T., Nottingham, & Reschke, J. F. (2022). HTTP Caching: HTTP Caching. RFC 9111.
Cited by¶
5 citations across 5 artifacts.
Each citation links to the sentence it supports in the citing article.
Primes¶
Mechanisms¶
- Cached Representation Service
- Its defining failure mode is serving a copy that no longer represents the principal: cache invalidation is famously one of the hard problems in computing, and a service that expires too slowly, or misses a change signal, will confidently answer with yesterday's truth.
This sourceExplains that stale cached responses can cease to represent the current origin state and specifies expiration, validation, and invalidation controls.
- Its defining failure mode is serving a copy that no longer represents the principal: cache invalidation is famously one of the hard problems in computing, and a service that expires too slowly, or misses a change signal, will confidently answer with yesterday's truth.
- Edge Cache with Origin Synchronization
- Cache invalidation is famously one of the genuinely hard parts of the craft, which is exactly why the rules are made explicit rather than assumed.
This sourceSpecifies explicit HTTP cache freshness, validation, and invalidation rules.
- Cache invalidation is famously one of the genuinely hard parts of the craft, which is exactly why the rules are made explicit rather than assumed.
- Time-to-Live (TTL) Policy
- The discipline is to set lifetimes to the layer's real freshness horizon, add jitter to desynchronise cohort expiry, and never point a bare TTL at layers whose loss isn't cheaply reversible.
This sourceDefines freshness lifetime and the conditions under which a stored HTTP response is fresh or stale.
- The discipline is to set lifetimes to the layer's real freshness horizon, add jitter to desynchronise cohort expiry, and never point a bare TTL at layers whose loss isn't cheaply reversible.
- Timestamp and Freshness Badge
- The discipline is to timestamp at the true source, tune the threshold so the warning stays meaningful, and pair the badge with a Stale Data Revalidation Gate wherever seeing the staleness isn't enough.
This sourceDefines cached-response age relative to origin generation or validation time and origin Date information.
- The discipline is to timestamp at the true source, tune the threshold so the warning stays meaningful, and pair the badge with a Stale Data Revalidation Gate wherever seeing the staleness isn't enough.
Verification¶
Does it exist? Confirmed. This work's DOI resolves to a registered record, which fixes its identity. That is all it fixes.
Does it back the claim? Not recorded. Neither this nor any other of the 5 citations of this work carries a recorded support check.
Was it audited? Yes. A second, independent pass read the citation against the article text and recorded a verdict.
Support is checked per citation rather than per work — the same source can be cited soundly in one article and wrongly in another. Per-citation recording began recently, so a citation with no recorded check is a gap in the record rather than evidence it went unchecked.
See how references were verified.
Links previously used in the corpus¶
Before the registry existed this work was also linked 2 other ways.
Registry ID ref:33f5418cb9ea · see in the full table