Search RFCs
RFC 7694
Hypertext Transfer Protocol (HTTP) Client-Initiated Content-Encoding,November 2015
- File formats:
- Status:
- PROPOSED STANDARD
- Obsoleted by:
- RFC 9110
- Author:
- J. Reschke
- Stream:
- IETF
- Source:
- httpbis (wit)
Cite this RFC:TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC7694
Discuss this RFC: Send questions or comments to the mailing listietf-http-wg@w3.org
Other actions:Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 7694
Abstract
In HTTP, content codings allow for payload encodings such as forcompression or integrity checks. In particular, the "gzip" contentcoding 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 documentextends the HTTP "Accept-Encoding" header field for use in responses,to indicate the content codings that are supported in requests.
For the definition ofStatus,seeRFC 2026.
For the definition ofStream, seeRFC 8729.