| CARVIEW |
Select Language
HTTP/2 200
date: Thu, 09 Oct 2025 20:32:20 GMT
content-type: text/html; charset=UTF-8
content-encoding: gzip
vary: Accept-Encoding
strict-transport-security: max-age=31536000; includeSubDomains
x-frame-options: SAMEORIGIN
x-xss-protection: 1; mode=block
x-content-type-options: nosniff
cf-cache-status: DYNAMIC
set-cookie: __cf_bm=mMC4UYOpmIdtGRpuWYoQmK1sYAC2O_2rs96iGj9DaWo-1760041940-1.0.1.1-Ie5bsS9Km_5.Lyyqw5uhcPg7scegvpTeUOJOrHfR4qNwbfzIxOlneAqF7k0Uq4DaiPZ5BNQxFgCVIVTNX138scSKTGMoFKLwXQy.73vXpiw; path=/; expires=Thu, 09-Oct-25 21:02:20 GMT; domain=.rfc-editor.org; HttpOnly; Secure; SameSite=None
server: cloudflare
cf-ray: 98c0a588da34c197-BLR
alt-svc: h3=":443"; ma=86400
Information on RFC 8246 » RFC Editor
Search RFCs
RFC 8246
HTTP Immutable Responses, September 2017
Cite this RFC: TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC8246
Discuss this RFC: Send questions or comments to the mailing list ietf-http-wg@w3.org
Other actions: Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 8246
Abstract
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.
For the definition of Status, see RFC 2026.
For the definition of Stream, see RFC 8729.
IAB • IANA • IETF • IRTF • ISE • ISOC • IETF Trust
Reports • Privacy Statement • Site Map • Contact Us