Hypertext Transfer Protocol (HTTP) Client-Initiated Content-Encoding
draft-reschke-http-cice-01
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Replaced".
Expired & archived
|
|
|---|---|---|---|
| Author | Julian Reschke | ||
| Last updated | 2015-01-03 (Latest revision 2014-07-02) | ||
| Replaced by | draft-ietf-httpbis-cice, RFC 7694 | ||
| RFC stream | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
In HTTP, "Content Codings" allow for payload encodings such as for compression or integrity checks. In particular, the "gzip" content coding is widely used for payload data sent in response messages. Content Codings can be used in request messages as well, however discoverability is not on par with response messages. This document extends the HTTP "Accept-Encoding" header field for use in responses.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)