Visual RFC.
ALL RFCs / RFC 9110
Read the RFC ↗
RFC 9110 / RESPONSES AND BOUNDARIES

Caches & revalidation

09

A cache can reuse a prior response when allowed. Stale entries can sometimes be validated without retransmitting content.

Related RFCs and changes

“Updates” changes part of an earlier RFC. “Obsoletes” replaces it. This list shows selected related documents.

DIAGRAM§ 3.8 ↗
RFC 9110 · § 3.8EXAMPLE
4 / 4
Caches & revalidationA stored response progresses from fresh to needing validation; a conditional request yields 304 and the stored content can be reused under caching rules.A saved response has a lifetimeIllustrative revalidation, with RFC 9111 policyStored responseETag: "guide-7"Origincurrent tag: "guide-7"storedfreshvalidateIf-None-Match: "guide-7"check304 Not Modified · no response contentReuse stored content under cache policyUpdate and reuse the cached response
04
Serve the validated response.

The cache applies RFC 9111 rules to update and reuse its stored response.

Protocol participantThreat or exceptionProtocol controlSimplified drawings · precise section references
KEY POINT

Distinguish reuse policy from validation.

  • HTTP caching stores responses for future equivalent requests.
  • Method semantics and response status affect whether a response is cacheable.
  • RFC 9111 supplies the detailed freshness, storage, and reuse rules; RFC 9110 defines the associated semantics and conditional requests.
DETAILS

This chapter illustrates the interface with caching. It does not imply every GET is cacheable, or that a cache may reuse any stored response without checking policy.

Read the RFC section ↗

Diagrams simplify the RFC. Read the linked sections for complete requirements.

Privacy
All chapters in this RFC
  1. One meaning, many transports
  2. Targets, origins & intermediaries
  3. Fields, content & representations
  4. Methods & retry safety
  5. Content negotiation
  6. Validators & conditional requests
  7. Range requests
  8. Status codes & redirects
  9. Caches & revalidation
  10. Authentication, security & extensions
RFC 9700 / CHAPTERS

Chapters

For full details, tables, algorithms, and exceptions, read the original RFC.

RFC status and corrections ↗