RFC 8246: HTTP Immutable Responses
In plain English — editorial summary, not part of the RFC
The immutable HTTP response Cache-Control extension allows servers to identify resources that will not be updated during their freshness lifetime. This ensures that a client never needs to revalidate a cached fresh resource to be certain it has not been modified.
Document record
- Document ID
- RFC8246
- Published
- September 2017
- Authors
- P. McManus
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- wit
- Pages
- 6
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8257Data Center TCP (DCTCP): TCP Congestion Control for Data CentersCurrent
October 2017
- RFC 8260Stream Schedulers and User Message Interleaving for the Stream Control Transmission ProtocolCurrent
November 2017
- RFC 8261Datagram Transport Layer Security (DTLS) Encapsulation of SCTP PacketsUpdated
November 2017
- RFC 8267Network File System (NFS) Upper-Layer Binding to RPC-over-RDMA Version 1Current
October 2017
- RFC 8269The ARIA Algorithm and Its Use with the Secure Real-Time Transport Protocol (SRTP)Current
October 2017
- RFC 8275Allowing Inheritable NFSv4 Access Control Entries to Override the UmaskCurrent
December 2017
- RFC 8276File System Extended Attributes in NFSv4Current
December 2017
- RFC 8285A General Mechanism for RTP Header ExtensionsCurrent
October 2017
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?