A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://dx.doi.org/10.17487/RFC7694 below:

Information on RFC 7694 ยป RFC Editor

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 list ietf-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 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.


RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4