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.¶
This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.¶
Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at http://datatracker.ietf.org/drafts/current/.¶
Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as “work in progress”.¶
This Internet-Draft will expire on November 11, 2014.¶
Copyright (c) 2014 IETF Trust and the persons identified as the document authors. All rights reserved.¶
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.¶
Distribution of this document is unlimited. Although this is not a work item of the HTTPbis Working Group, comments should be sent to the Hypertext Transfer Protocol (HTTP) mailing list at email@example.com, which may be joined by sending a message with subject "subscribe" to firstname.lastname@example.org.¶
XML versions, latest edits, and the issues list for this document are available from <http://greenbytes.de/tech/webdav/#draft-reschke-http-cice>.¶
|I edit (type: edit, status: open)|
|email@example.com||2011-04-15||Umbrella issue for editorial fixes/enhancements.|
In HTTP, "Content Codings" allow for payload encodings such as for compression or integrity checks ([HTTPSEM], Section 3.1.2). In particular, the "gzip" content coding is widely used for payload data sent in response messages.¶
This specification extends that definition to allow "Accept-Encoding" as response header field as well. When present, it indicates what content codings a server is willing to accept in requests. In particular, a field value that contains "identity" only implies that no content codings are supported at all.¶
Note that this information applies to the resource to which the request was addressed. The set of supported encodings might vary for different resources on the same server, and could also vary depending on other aspects of the request (such as the request method).¶
Servers that fail a request due to an unsupported content coding SHOULD respond with a 415 status and SHOULD include an "Accept-Encoding" header in that response, allowing clients to distinguish between content coding related issues and media type related issues.¶
POST /edit/ HTTP/1.1 Host: example.org Content-Type: application/atom+xml;type=entry Content-Encoding: compress ...compressed payload...
Server rejects request because it only allows the "gzip" content coding:¶
HTTP/1.1 415 Unsupported Media Type Date: Fri, 09 May 2014 11:43:53 GMT Accept-Encoding: gzip Content-Length: 68 Content-Type: text/plain This resource only supports the "gzip" content coding in requests.
...at which point the client can retry the request with the supported "gzip" content coding.¶
Alternatively, a server that does not support any content codings in requests could answer with:¶
HTTP/1.1 415 Unsupported Media Type Date: Fri, 09 May 2014 11:43:53 GMT Accept-Encoding: identity Content-Length: 61 Content-Type: text/plain This resource does not support content codings in requests.
This document updates the definition of the "Accept-Encoding" header field, so the "Permanent Message Header Field Names" registry shall be updated accordingly:¶