Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Hypertext Transfer Protocol (HTTP) Client-Initiated Content-Encoding (RFC7694)

IP.com Disclosure Number: IPCOM000245051D
Original Publication Date: 2015-Nov-01
Included in the Prior Art Database: 2016-Feb-07
Document File: 14 page(s) / 14K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

J. Reschke: AUTHOR

Abstract

In HTTP, content codings allow for payload encodings such as for compression or integrity checks ([RFC7231], Section 3.1.2). In particular, the "gzip" content coding ([RFC7230], Section 4.2) is widely used for payload data sent in response messages.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 20% of the total text.

Internet Engineering Task Force (IETF)                        J. Reschke Request for Comments: 7694                                    greenbytes Category: Standards Track                                  November 2015 ISSN: 2070-1721

   Hypertext Transfer Protocol (HTTP) Client-Initiated Content-Encoding

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.

Status of This Memo

   This is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force    (IETF).  It represents the consensus of the IETF community.  It has    received public review and has been approved for publication by the    Internet Engineering Steering Group (IESG).  Further information on    Internet Standards is available in Section 2 of RFC 5741.

   Information about the current status of this document, any errata,    and how to provide feedback on it may be obtained at    http://www.rfc-editor.org/info/rfc7694.

Copyright Notice

   Copyright (c) 2015 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.

 Reschke                      Standards Track                    [Page 1]
 RFC 7694                        HTTP CICE                  November 2015

 Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2

   2.  Notational Conventions  . . . . . . . . . . . . . . . . . . .   2

   3.  Using the 'Accept-Encoding' Header Field in Responses . . . .   3

   4.  Example . . . . . . . . . . . . . . . . . . . . . . . . . . .   4

   5.  Deployment Considerations . . . . . . . . . . . . . . . . . .   4

   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   5

   7.  IANA Considerat...