Hypertext Transfer Protocol (HTTP) Client-Initiated Content-Encoding, November 2015
- File formats:
- PROPOSED STANDARD
- Obsoleted by:
- RFC 9110
- J. Reschke
- httpbis (art)
Cite this RFC: TXT | XML | BibTeX
Discuss this RFC: Send questions or comments to the mailing list firstname.lastname@example.org
Other actions: Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 7694
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, to indicate the content codings that are supported in requests.
For the definition of Status, see RFC 2026.
For the definition of Stream, see RFC 8729.