HTTP Immutable Responses
draft-mcmanus-immutable-01
| Document | Type | Replaced Internet-Draft (individual) | |
|---|---|---|---|
| Author | Patrick McManus | ||
| Last updated | 2016-12-19 | ||
| Replaced by | RFC 8246 | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
plain text
xml
htmlized
pdfized
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-httpbis-immutable | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of
the expired Internet-Draft can be found at:
https://www.ietf.org/archive/id/draft-mcmanus-immutable-01.txt
https://www.ietf.org/archive/id/draft-mcmanus-immutable-01.txt
Abstract
The immutable HTTP response Cache-Control extension allows servers to identify resources that will not be updated during their freshness lifetime. This assures that a client never needs to revalidate a cached fresh resource to be certain it has not been modified.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)