Hypertext Transfer Protocol Client-Initiated Content- Encoding
RFC 7694, “Hypertext Transfer Protocol Client-Initiated Content- Encoding”, is a Proposed Standard document published in November 2015 by J. Reschke. It has been obsoleted by RFC 9110 — refer to the newer document for the authoritative version. The canonical text is published by the RFC Editor.
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, to indicate the content codings that are supported in requests.
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
The canonical text of RFC 7694 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 7693 The BLAKE2 Cryptographic Hash and Message Authentication Code
- RFC 7695 Distributed Prefix Assignment Algorithm
- RFC 7692 Compression Extensions for WebSocket
- RFC 7696 Guidelines for Cryptographic Algorithm Agility and Selecting Mandatory-to-Implement Algorithms
- RFC 7691 Updating the Term Dates of IETF Administrative Oversight Committee Members
- RFC 7698 Framework and Requirements for GMPLS-Based Control of Flexi-Grid Dense Wavelength Division Multiplexing Networks
- RFC 7689 Signaling Extensions for Wavelength Switched Optical Networks
- RFC 7699 Generalized Labels for the Flexi-Grid in Lambda Switch Capable Label Switching Routers