RFC 9211: The Cache-Status HTTP Response Header Field
In plain English — editorial summary, not part of the RFC
To aid debugging, HTTP caches often append header fields to a response, explaining how they handled the request in an ad hoc manner. This specification defines a standard mechanism to do so that is aligned with HTTP's caching model.
Document record
- Document ID
- RFC9211
- Published
- June 2022
- Authors
- M. Nottingham
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- wit
- Pages
- 9
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9264Linkset: Media Types and a Link Relation Type for Link SetsCurrent
July 2022
- RFC 9297HTTP Datagrams and the Capsule ProtocolCurrent
August 2022
- RFC 9298Proxying UDP in HTTPUpdated
August 2022
- RFC 9113HTTP/2Current
June 2022
- RFC 9112HTTP/1.1Updated
June 2022
- RFC 9111HTTP CachingCurrent
June 2022
- RFC 9110HTTP SemanticsCurrent
June 2022
- RFC 9440Client-Cert HTTP Header FieldCurrent
July 2023
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?