RFC 9111: HTTP Caching
In plain English — editorial summary, not part of the RFC
The Hypertext Transfer Protocol (HTTP) is a stateless application-level protocol for distributed, collaborative, hypertext information systems. This document defines HTTP caches and the associated header fields that control cache behavior or indicate cacheable response messages. This document obsoletes RFC 7234.
Document record
- Document ID
- RFC9111
- Published
- June 2022
- Authors
- R. Fielding; M. Nottingham; J. Reschke
- Status
- INTERNET STANDARD
- Stream
- IETF
- Area
- wit
- Pages
- 35
- Also known as
- STD98
- Obsoletes:
- RFC 7234
Topics
Standards lineage
This document is one revision in a chain of 21 RFCs, each formally replacing the one before it.
- RFC 2068 (1997)
- RFC 2069 (1997)
- RFC 2145 (1997)
- RFC 2616 (1999)
- RFC 2617 (1999)
- RFC 2818 (2000)
- RFC 7230 (2014)
- RFC 7231 (2014)
- RFC 7232 (2014)
- RFC 7233 (2014)
- RFC 7234 (2014)
- RFC 7235 (2014)
- RFC 7238 (2014)
- RFC 7538 (2015)
- RFC 7615 (2015)
- RFC 7616 (2015)
- RFC 7617 (2015)
- RFC 7694 (2015)
- RFC 9110 (2022)
- RFC 9111 (2022)
- RFC 9112 (2022) ✓
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9110HTTP SemanticsCurrent
June 2022
- RFC 9112HTTP/1.1Updated
June 2022
- RFC 7237Initial Hypertext Transfer Protocol (HTTP) Method RegistrationsCurrent
June 2014
- RFC 7236Initial Hypertext Transfer Protocol (HTTP) Authentication Scheme RegistrationsCurrent
June 2014
- RFC 7235Hypertext Transfer Protocol (HTTP/1.1): AuthenticationObsoleted
June 2014
- RFC 7232Hypertext Transfer Protocol (HTTP/1.1): Conditional RequestsObsoleted
June 2014
- RFC 7231Hypertext Transfer Protocol (HTTP/1.1): Semantics and ContentObsoleted
June 2014
- RFC 6331Moving DIGEST-MD5 to HistoricCurrent
July 2011
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?