The Key HTTP Response Header Field
draft-ietf-httpbis-key-01
| Document | Type | Expired Internet-Draft (httpbis WG) | |
|---|---|---|---|
| Last updated | 2016-09-02 (latest revision 2016-03-01) | ||
| Replaces | draft-fielding-http-key | ||
| Stream | IETF | ||
| Intended RFC status | Proposed Standard | ||
| Formats |
Expired & archived
plain text
pdf
html
bibtex
|
||
| Stream | WG state | Parked WG Document (wg milestone: May 2016 - Submit the Key HTTP ... ) | |
| Document shepherd | Martin Thomson | ||
| IESG | IESG state | Expired | |
| Consensus Boilerplate | Unknown | ||
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | "Martin Thomson" <mt@mozilla.com> | ||
https://www.ietf.org/archive/id/draft-ietf-httpbis-key-01.txt
Abstract
The 'Key' header field for HTTP responses allows an origin server to describe the secondary cache key (RFC 7234, Section 4.1) for a resource, by conveying what is effectively a short algorithm that can be used upon later requests to determine if a stored response is reusable for a given request. Key has the advantage of avoiding an additional round trip for validation whenever a new request differs slightly, but not significantly, from prior requests. Key also informs user agents of the request characteristics that might result in different content, which can be useful if the user agent is not sending request header fields in order to reduce the risk of fingerprinting.
Authors
Roy Fielding
(fielding@gbiv.com)
Mark Nottingham
(mnot@mnot.net)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)