source: draft-ietf-httpbis/latest/p3-payload.xml @ 806

Last change on this file since 806 was 806, checked in by julian.reschke@…, 10 years ago

"deflate": make the IANA entry more consistent with the actual description (related to #73)

  • Property svn:eol-style set to native
File size: 131.7 KB
[29]1<?xml version="1.0" encoding="utf-8"?>
[101]2<?xml-stylesheet type='text/xsl' href='../myxml2rfc.xslt'?>
[8]3<!DOCTYPE rfc [
4  <!ENTITY MAY "<bcp14 xmlns=''>MAY</bcp14>">
5  <!ENTITY MUST "<bcp14 xmlns=''>MUST</bcp14>">
6  <!ENTITY MUST-NOT "<bcp14 xmlns=''>MUST NOT</bcp14>">
7  <!ENTITY OPTIONAL "<bcp14 xmlns=''>OPTIONAL</bcp14>">
8  <!ENTITY RECOMMENDED "<bcp14 xmlns=''>RECOMMENDED</bcp14>">
9  <!ENTITY REQUIRED "<bcp14 xmlns=''>REQUIRED</bcp14>">
10  <!ENTITY SHALL "<bcp14 xmlns=''>SHALL</bcp14>">
11  <!ENTITY SHALL-NOT "<bcp14 xmlns=''>SHALL NOT</bcp14>">
12  <!ENTITY SHOULD "<bcp14 xmlns=''>SHOULD</bcp14>">
13  <!ENTITY SHOULD-NOT "<bcp14 xmlns=''>SHOULD NOT</bcp14>">
[29]14  <!ENTITY ID-VERSION "latest">
[799]15  <!ENTITY ID-MONTH "April">
[741]16  <!ENTITY ID-YEAR "2010">
[424]17  <!ENTITY notation                 "<xref target='Part1' x:rel='#notation' xmlns:x=''/>">
[205]18  <!ENTITY notation-abnf            "<xref target='Part1' x:rel='#notation.abnf' xmlns:x=''/>">
19  <!ENTITY basic-rules              "<xref target='Part1' x:rel='#basic.rules' xmlns:x=''/>">
[115]20  <!ENTITY caching-neg-resp         "<xref target='Part6' x:rel='#caching.negotiated.responses' xmlns:x=''/>">
[31]21  <!ENTITY header-transfer-encoding "<xref target='Part1' x:rel='#header.transfer-encoding' xmlns:x=''/>">
22  <!ENTITY header-content-length    "<xref target='Part1' x:rel='#header.content-length' xmlns:x=''/>">
23  <!ENTITY header-content-range     "<xref target='Part5' x:rel='#header.content-range' xmlns:x=''/>">
24  <!ENTITY header-expires           "<xref target='Part6' x:rel='#header.expires' xmlns:x=''/>">
25  <!ENTITY header-last-modified     "<xref target='Part4' x:rel='#header.last-modified' xmlns:x=''/>">
26  <!ENTITY header-user-agent        "<xref target='Part2' x:rel='#header.user-agent' xmlns:x=''/>">
[115]27  <!ENTITY header-vary              "<xref target='Part6' x:rel='#header.vary' xmlns:x=''/>">
[31]28  <!ENTITY message-body             "<xref target='Part1' x:rel='#message.body' xmlns:x=''/>">
29  <!ENTITY message-length           "<xref target='Part1' x:rel='#message.length' xmlns:x=''/>">
[647]30  <!ENTITY header-fields            "<xref target='Part1' x:rel='#header.fields' xmlns:x=''/>">
[31]31  <!ENTITY multipart-byteranges     "<xref target='Part5' x:rel='' xmlns:x=''/>">
[580]32  <!ENTITY full-date                "<xref target='Part1' x:rel='' xmlns:x=''/>">
[457]33  <!ENTITY qvalue                   "<xref target='Part1' x:rel='#quality.values' xmlns:x=''/>">
[374]34  <!ENTITY uri                      "<xref target='Part1' x:rel='#uri' xmlns:x=''/>">
[673]35  <!ENTITY compress-coding          "<xref target='Part1' x:rel='#compress.coding' xmlns:x=''/>">
36  <!ENTITY deflate-coding           "<xref target='Part1' x:rel='#deflate.coding' xmlns:x=''/>">
37  <!ENTITY gzip-coding              "<xref target='Part1' x:rel='#gzip.coding' xmlns:x=''/>">
[716]38  <!ENTITY response-representation  "<xref target='Part2' x:rel='#identifying.response.associated.with.representation' xmlns:x=''/>">
40<?rfc toc="yes" ?>
[29]41<?rfc symrefs="yes" ?>
42<?rfc sortrefs="yes" ?>
[8]43<?rfc compact="yes"?>
44<?rfc subcompact="no" ?>
45<?rfc linkmailto="no" ?>
46<?rfc editing="no" ?>
[203]47<?rfc comments="yes"?>
48<?rfc inline="yes"?>
[799]49<?rfc rfcedstyle="yes"?>
[8]50<?rfc-ext allow-markup-in-artwork="yes" ?>
51<?rfc-ext include-references-in-index="yes" ?>
[308]52<rfc obsoletes="2616" category="std" x:maturity-level="draft"
[446]53     ipr="pre5378Trust200902" docName="draft-ietf-httpbis-p3-payload-&ID-VERSION;"
[153]54     xmlns:x=''>
[120]57  <title abbrev="HTTP/1.1, Part 3">HTTP/1.1, part 3: Message Payload and Content Negotiation</title>
[29]59  <author initials="R." surname="Fielding" fullname="Roy T. Fielding" role="editor">
60    <organization abbrev="Day Software">Day Software</organization>
[8]61    <address>
62      <postal>
[29]63        <street>23 Corporate Plaza DR, Suite 280</street>
64        <city>Newport Beach</city>
[8]65        <region>CA</region>
[29]66        <code>92660</code>
67        <country>USA</country>
[8]68      </postal>
[29]69      <phone>+1-949-706-5300</phone>
70      <facsimile>+1-949-706-5305</facsimile>
71      <email></email>
72      <uri></uri>
[8]73    </address>
74  </author>
[29]76  <author initials="J." surname="Gettys" fullname="Jim Gettys">
77    <organization>One Laptop per Child</organization>
[8]78    <address>
79      <postal>
[29]80        <street>21 Oak Knoll Road</street>
81        <city>Carlisle</city>
[8]82        <region>MA</region>
[29]83        <code>01741</code>
84        <country>USA</country>
[8]85      </postal>
[29]86      <email></email>
87      <uri></uri>
[8]88    </address>
89  </author>
91  <author initials="J." surname="Mogul" fullname="Jeffrey C. Mogul">
[29]92    <organization abbrev="HP">Hewlett-Packard Company</organization>
[8]93    <address>
94      <postal>
[29]95        <street>HP Labs, Large Scale Systems Group</street>
96        <street>1501 Page Mill Road, MS 1177</street>
[8]97        <city>Palo Alto</city>
98        <region>CA</region>
[29]99        <code>94304</code>
100        <country>USA</country>
[8]101      </postal>
[29]102      <email></email>
[8]103    </address>
104  </author>
106  <author initials="H." surname="Frystyk" fullname="Henrik Frystyk Nielsen">
[29]107    <organization abbrev="Microsoft">Microsoft Corporation</organization>
[8]108    <address>
109      <postal>
[29]110        <street>1 Microsoft Way</street>
111        <city>Redmond</city>
112        <region>WA</region>
113        <code>98052</code>
114        <country>USA</country>
[8]115      </postal>
[29]116      <email></email>
[8]117    </address>
118  </author>
120  <author initials="L." surname="Masinter" fullname="Larry Masinter">
[29]121    <organization abbrev="Adobe Systems">Adobe Systems, Incorporated</organization>
[8]122    <address>
123      <postal>
[29]124        <street>345 Park Ave</street>
125        <city>San Jose</city>
[8]126        <region>CA</region>
[29]127        <code>95110</code>
128        <country>USA</country>
[8]129      </postal>
[29]130      <email></email>
131      <uri></uri>
[8]132    </address>
133  </author>
135  <author initials="P." surname="Leach" fullname="Paul J. Leach">
136    <organization abbrev="Microsoft">Microsoft Corporation</organization>
137    <address>
138      <postal>
139        <street>1 Microsoft Way</street>
140        <city>Redmond</city>
141        <region>WA</region>
142        <code>98052</code>
143      </postal>
144      <email></email>
145    </address>
146  </author>
148  <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
149    <organization abbrev="W3C/MIT">World Wide Web Consortium</organization>
150    <address>
151      <postal>
[34]152        <street>MIT Computer Science and Artificial Intelligence Laboratory</street>
153        <street>The Stata Center, Building 32</street>
154        <street>32 Vassar Street</street>
[8]155        <city>Cambridge</city>
156        <region>MA</region>
157        <code>02139</code>
[29]158        <country>USA</country>
[8]159      </postal>
160      <email></email>
[34]161      <uri></uri>
[8]162    </address>
163  </author>
[95]165  <author initials="Y." surname="Lafon" fullname="Yves Lafon" role="editor">
[94]166    <organization abbrev="W3C">World Wide Web Consortium</organization>
167    <address>
168      <postal>
169        <street>W3C / ERCIM</street>
170        <street>2004, rte des Lucioles</street>
171        <city>Sophia-Antipolis</city>
172        <region>AM</region>
173        <code>06902</code>
174        <country>France</country>
175      </postal>
176      <email></email>
177      <uri></uri>
178    </address>
179  </author>
[95]181  <author initials="J. F." surname="Reschke" fullname="Julian F. Reschke" role="editor">
182    <organization abbrev="greenbytes">greenbytes GmbH</organization>
183    <address>
184      <postal>
185        <street>Hafenweg 16</street>
186        <city>Muenster</city><region>NW</region><code>48155</code>
187        <country>Germany</country>
188      </postal>
[609]189      <phone>+49 251 2807760</phone>
190      <facsimile>+49 251 2807761</facsimile>
191      <email></email>
192      <uri></uri>
[95]193    </address>
194  </author>
[31]196  <date month="&ID-MONTH;" year="&ID-YEAR;"/>
[440]197  <workgroup>HTTPbis Working Group</workgroup>
201   The Hypertext Transfer Protocol (HTTP) is an application-level
202   protocol for distributed, collaborative, hypermedia information
[29]203   systems. HTTP has been in use by the World Wide Web global information
[35]204   initiative since 1990. This document is Part 3 of the seven-part specification
[29]205   that defines the protocol referred to as "HTTP/1.1" and, taken together,
[42]206   obsoletes RFC 2616.  Part 3 defines HTTP message content,
[29]207   metadata, and content negotiation.
211<note title="Editorial Note (To be removed by RFC Editor)">
212  <t>
213    Discussion of this draft should take place on the HTTPBIS working group
214    mailing list ( The current issues list is
[324]215    at <eref target=""/>
[36]216    and related documents (including fancy diffs) can be found at
[324]217    <eref target=""/>.
[36]218  </t>
[153]219  <t>
[773]220    The changes in this draft are summarized in <xref target="changes.since.09"/>.
[153]221  </t>
225<section title="Introduction" anchor="introduction">
[163]227   This document defines HTTP/1.1 message payloads (a.k.a., content), the
[161]228   associated metadata header fields that define how the payload is intended
229   to be interpreted by a recipient, the request header fields that
230   may influence content selection, and the various selection algorithms
231   that are collectively referred to as HTTP content negotiation.
234   This document is currently disorganized in order to minimize the changes
235   between drafts and enable reviewers to see the smaller errata changes.
236   The next draft will reorganize the sections to better reflect the content.
237   In particular, the sections on entities will be renamed payload and moved
238   to the first half of the document, while the sections on content negotiation
239   and associated request header fields will be moved to the second half.  The
240   current mess reflects how widely dispersed these topics and associated
241   requirements had become in <xref target="RFC2616"/>.
[660]244<section title="Terminology" anchor="terminology">
246   This specification uses a number of terms to refer to the roles
247   played by participants in, and objects of, the HTTP communication.
250  <iref item="content negotiation"/>
251  <x:dfn>content negotiation</x:dfn>
252  <list>
253    <t>
254      The mechanism for selecting the appropriate representation when
255      servicing a request. The representation of entities in any response
256      can be negotiated (including error responses).
257    </t>
258  </list>
261  <iref item="entity"/>
262  <x:dfn>entity</x:dfn>
263  <list>
264    <t>
265      The information transferred as the payload of a request or
266      response. An entity consists of metadata in the form of
267      entity-header fields and content in the form of an entity-body.
268    </t>
269  </list>
272  <iref item="representation"/>
273  <x:dfn>representation</x:dfn>
274  <list>
275    <t>
276      An entity included with a response that is subject to content
277      negotiation. There may exist multiple
278      representations associated with a particular response status.
279    </t>
280  </list>
283  <iref item="variant"/>
284  <x:dfn>variant</x:dfn>
285  <list>
286    <t>
287      A resource may have one, or more than one, representation(s)
288      associated with it at any given instant. Each of these
[746]289      representations is termed a "variant".  Use of the term "variant"
[660]290      does not necessarily imply that the resource is subject to content
291      negotiation.
292    </t>
293  </list>
[96]297<section title="Requirements" anchor="intro.requirements">
299   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
300   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
301   document are to be interpreted as described in <xref target="RFC2119"/>.
304   An implementation is not compliant if it fails to satisfy one or more
305   of the &MUST; or &REQUIRED; level requirements for the protocols it
306   implements. An implementation that satisfies all the &MUST; or &REQUIRED;
307   level and all the &SHOULD; level requirements for its protocols is said
308   to be "unconditionally compliant"; one that satisfies all the &MUST;
309   level requirements but not all the &SHOULD; level requirements for its
310   protocols is said to be "conditionally compliant."
[424]314<section title="Syntax Notation" anchor="notation">
[425]315  <x:anchor-alias value="ALPHA"/>
316  <x:anchor-alias value="CR"/>
317  <x:anchor-alias value="DIGIT"/>
318  <x:anchor-alias value="LF"/>
319  <x:anchor-alias value="OCTET"/>
320  <x:anchor-alias value="VCHAR"/>
321  <x:anchor-alias value="WSP"/>
[543]323  This specification uses the ABNF syntax defined in &notation; (which
324  extends the syntax defined in <xref target="RFC5234"/> with a list rule).
325  <xref target="collected.abnf"/> shows the collected ABNF, with the list
326  rule expanded.
[425]329  The following core rules are included by
330  reference, as defined in <xref target="RFC5234" x:fmt="," x:sec="B.1"/>:
331  ALPHA (letters), CR (carriage return), CRLF (CR LF), CTL (controls),
332  DIGIT (decimal 0-9), DQUOTE (double quote),
333  HEXDIG (hexadecimal 0-9/A-F/a-f), LF (line feed),
334  OCTET (any 8-bit sequence of data), SP (space),
335  VCHAR (any visible USASCII character),
336  and WSP (whitespace).
339<section title="Core Rules" anchor="core.rules">
[229]340  <x:anchor-alias value="quoted-string"/>
341  <x:anchor-alias value="token"/>
[357]342  <x:anchor-alias value="OWS"/>
[424]344  The core rules below are defined in &basic-rules;:
346<figure><artwork type="abnf2616">
[229]347  <x:ref>quoted-string</x:ref>  = &lt;quoted-string, defined in &basic-rules;&gt;
348  <x:ref>token</x:ref>          = &lt;token, defined in &basic-rules;&gt;
[357]349  <x:ref>OWS</x:ref>            = &lt;OWS, defined in &basic-rules;&gt;
353<section title="ABNF Rules defined in other Parts of the Specification" anchor="abnf.dependencies">
[374]354  <x:anchor-alias value="absolute-URI"/>
[229]355  <x:anchor-alias value="Allow"/>
356  <x:anchor-alias value="Content-Length"/>
357  <x:anchor-alias value="Content-Range"/>
358  <x:anchor-alias value="Expires"/>
359  <x:anchor-alias value="Last-Modified"/>
[647]360  <x:anchor-alias value="header-field"/>
[391]361  <x:anchor-alias value="partial-URI"/>
[457]362  <x:anchor-alias value="qvalue"/>
[206]364  The ABNF rules below are defined in other parts:
[207]366<figure><!--Part1--><artwork type="abnf2616">
[374]367  <x:ref>absolute-URI</x:ref>   = &lt;absolute-URI, defined in &uri;&gt;
[229]368  <x:ref>Content-Length</x:ref> = &lt;Content-Length, defined in &header-content-length;&gt;
[647]369  <x:ref>header-field</x:ref>   = &lt;header-field, defined in &header-fields;&gt;
[391]370  <x:ref>partial-URI</x:ref>    = &lt;partial-URI, defined in &uri;&gt;
[457]371  <x:ref>qvalue</x:ref>         = &lt;qvalue, defined in &qvalue;&gt;
373<figure><!--Part4--><artwork type="abnf2616">
[229]374  <x:ref>Last-Modified</x:ref>  = &lt;Last-Modified, defined in &header-last-modified;&gt;
376<figure><!--Part5--><artwork type="abnf2616">
[229]377  <x:ref>Content-Range</x:ref>  = &lt;Content-Range, defined in &header-content-range;&gt;
379<figure><!--Part6--><artwork type="abnf2616">
[229]380  <x:ref>Expires</x:ref>        = &lt;Expires, defined in &header-expires;&gt;
[8]388<section title="Protocol Parameters" anchor="protocol.parameters">
390<section title="Character Sets" anchor="character.sets">
392   HTTP uses the same definition of the term "character set" as that
393   described for MIME:
396   The term "character set" is used in this document to refer to a
397   method used with one or more tables to convert a sequence of octets
398   into a sequence of characters. Note that unconditional conversion in
399   the other direction is not required, in that not all characters may
400   be available in a given character set and a character set may provide
401   more than one sequence of octets to represent a particular character.
402   This definition is intended to allow various kinds of character
403   encoding, from simple single-table mappings such as US-ASCII to
404   complex table switching methods such as those that use ISO-2022's
405   techniques. However, the definition associated with a MIME character
406   set name &MUST; fully specify the mapping to be performed from octets
407   to characters. In particular, use of external profiling information
408   to determine the exact mapping is not permitted.
411  <t>
412    <x:h>Note:</x:h> This use of the term "character set" is more commonly
413    referred to as a "character encoding." However, since HTTP and
414    MIME share the same registry, it is important that the terminology
415    also be shared.
416  </t>
[229]418<t anchor="rule.charset">
419  <x:anchor-alias value="charset"/>
[8]420   HTTP character sets are identified by case-insensitive tokens. The
421   complete set of tokens is defined by the IANA Character Set registry
[91]422   (<eref target=""/>).
424<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="charset"/>
[229]425  <x:ref>charset</x:ref> = <x:ref>token</x:ref>
428   Although HTTP allows an arbitrary token to be used as a charset
429   value, any token that has a predefined value within the IANA
[91]430   Character Set registry &MUST; represent the character set defined
[8]431   by that registry. Applications &SHOULD; limit their use of character
432   sets to those defined by the IANA registry.
[81]435   HTTP uses charset in two contexts: within an Accept-Charset request
436   header (in which the charset value is an unquoted token) and as the
[115]437   value of a parameter in a Content-Type header (within a request or
[81]438   response), in which case the parameter value of the charset parameter
439   may be quoted.
[129]442   Implementors should be aware of IETF character set requirements <xref target="RFC3629"/>
[8]443   <xref target="RFC2277"/>.
446<section title="Missing Charset" anchor="missing.charset">
448   Some HTTP/1.0 software has interpreted a Content-Type header without
449   charset parameter incorrectly to mean "recipient should guess."
450   Senders wishing to defeat this behavior &MAY; include a charset
451   parameter even when the charset is ISO-8859-1 (<xref target="ISO-8859-1"/>) and &SHOULD; do so when
452   it is known that it will not confuse the recipient.
455   Unfortunately, some older HTTP/1.0 clients did not deal properly with
456   an explicit charset parameter. HTTP/1.1 recipients &MUST; respect the
457   charset label provided by the sender; and those user agents that have
458   a provision to "guess" a charset &MUST; use the charset from the
459   content-type field if they support that charset, rather than the
460   recipient's preference, when initially displaying a document. See
461   <xref target="canonicalization.and.text.defaults"/>.
466<section title="Content Codings" anchor="content.codings">
[229]467  <x:anchor-alias value="content-coding"/>
469   Content coding values indicate an encoding transformation that has
470   been or can be applied to an entity. Content codings are primarily
471   used to allow a document to be compressed or otherwise usefully
472   transformed without losing the identity of its underlying media type
473   and without loss of information. Frequently, the entity is stored in
474   coded form, transmitted directly, and only decoded by the recipient.
476<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="content-coding"/>
[229]477  <x:ref>content-coding</x:ref>   = <x:ref>token</x:ref>
480   All content-coding values are case-insensitive. HTTP/1.1 uses
481   content-coding values in the Accept-Encoding (<xref target="header.accept-encoding"/>) and
482   Content-Encoding (<xref target="header.content-encoding"/>) header fields. Although the value
483   describes the content-coding, what is more important is that it
484   indicates what decoding mechanism will be required to remove the
485   encoding.
[673]488   compress<iref item="compress (Coding Format)"/><iref item="Coding Format" subitem="compress"/>
489  <list>
490    <t>
491      See &compress-coding;.
492    </t>
493  </list>
[673]496   deflate<iref item="deflate (Coding Format)"/><iref item="Coding Format" subitem="deflate"/>
[8]497  <list>
498    <t>
[673]499      See &deflate-coding;.
[8]500    </t>
501  </list>
[673]504   gzip<iref item="gzip (Coding Format)"/><iref item="Coding Format" subitem="gzip"/>
505  <list>
506    <t>
507      See &gzip-coding;.
508    </t>
509  </list>
[673]512   identity<iref item="identity (Coding Format)"/><iref item="Coding Format" subitem="identity"/>
[8]513  <list><t>
514        The default (identity) encoding; the use of no transformation
515        whatsoever. This content-coding is used only in the Accept-Encoding
516        header, and &SHOULD-NOT;  be used in the Content-Encoding
517        header.
518  </t></list>
521<section title="Content Coding Registry" anchor="content.coding.registry">
[670]523   The HTTP Content Coding Registry defines the name space for the content
524   coding names.
527   Registrations &MUST; include the following fields:
528   <list style="symbols">
529     <t>Name</t>
530     <t>Description</t>
531     <t>Pointer to specification text</t>
532   </list>
535   Values to be added to this name space require expert review and a specification
536   (see "Expert Review" and "Specification Required" in
537   <xref target="RFC5226" x:fmt="of" x:sec="4.1"/>), and &MUST;
[8]538   conform to the purpose of content coding defined in this section.
541   The registry itself is maintained at
542   <eref target=""/>.
[8]548<section title="Media Types" anchor="media.types">
[229]549  <x:anchor-alias value="media-type"/>
550  <x:anchor-alias value="type"/>
551  <x:anchor-alias value="subtype"/>
[152]553   HTTP uses Internet Media Types <xref target="RFC2046"/> in the Content-Type (<xref target="header.content-type"/>)
[8]554   and Accept (<xref target="header.accept"/>) header fields in order to provide
555   open and extensible data typing and type negotiation.
557<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="media-type"/><iref primary="true" item="Grammar" subitem="type"/><iref primary="true" item="Grammar" subitem="subtype"/>
[357]558  <x:ref>media-type</x:ref> = <x:ref>type</x:ref> "/" <x:ref>subtype</x:ref> *( <x:ref>OWS</x:ref> ";" <x:ref>OWS</x:ref> <x:ref>parameter</x:ref> )
559  <x:ref>type</x:ref>       = <x:ref>token</x:ref>
560  <x:ref>subtype</x:ref>    = <x:ref>token</x:ref>
[229]562<t anchor="rule.parameter">
563  <x:anchor-alias value="attribute"/>
564  <x:anchor-alias value="parameter"/>
565  <x:anchor-alias value="value"/>
[8]566   Parameters &MAY; follow the type/subtype in the form of attribute/value
[29]567   pairs.
[29]569<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="parameter"/><iref primary="true" item="Grammar" subitem="attribute"/><iref primary="true" item="Grammar" subitem="value"/>
[250]570  <x:ref>parameter</x:ref>      = <x:ref>attribute</x:ref> "=" <x:ref>value</x:ref>
571  <x:ref>attribute</x:ref>      = <x:ref>token</x:ref>
[334]572  <x:ref>value</x:ref>          = <x:ref>token</x:ref> / <x:ref>quoted-string</x:ref>
575   The type, subtype, and parameter attribute names are case-insensitive.
[370]576   Parameter values might or might not be case-sensitive, depending on the
577   semantics of the parameter name.  The presence or absence of a parameter might
[8]578   be significant to the processing of a media-type, depending on its
579   definition within the media type registry.
[297]582   A parameter value that matches the <x:ref>token</x:ref> production may be
583   transmitted as either a token or within a quoted-string. The quoted and
584   unquoted values are equivalent.
[8]587   Note that some older HTTP applications do not recognize media type
588   parameters. When sending data to older HTTP applications,
589   implementations &SHOULD; only use media type parameters when they are
590   required by that type/subtype definition.
593   Media-type values are registered with the Internet Assigned Number
[91]594   Authority (IANA). The media type registration process is
[115]595   outlined in <xref target="RFC4288"/>. Use of non-registered media types is
[8]596   discouraged.
599<section title="Canonicalization and Text Defaults" anchor="canonicalization.and.text.defaults">
601   Internet media types are registered with a canonical form. An
602   entity-body transferred via HTTP messages &MUST; be represented in the
603   appropriate canonical form prior to its transmission except for
604   "text" types, as defined in the next paragraph.
607   When in canonical form, media subtypes of the "text" type use CRLF as
608   the text line break. HTTP relaxes this requirement and allows the
609   transport of text media with plain CR or LF alone representing a line
610   break when it is done consistently for an entire entity-body. HTTP
611   applications &MUST; accept CRLF, bare CR, and bare LF as being
612   representative of a line break in text media received via HTTP. In
613   addition, if the text is represented in a character set that does not
614   use octets 13 and 10 for CR and LF respectively, as is the case for
615   some multi-byte character sets, HTTP allows the use of whatever octet
616   sequences are defined by that character set to represent the
617   equivalent of CR and LF for line breaks. This flexibility regarding
618   line breaks applies only to text media in the entity-body; a bare CR
619   or LF &MUST-NOT; be substituted for CRLF within any of the HTTP control
620   structures (such as header fields and multipart boundaries).
623   If an entity-body is encoded with a content-coding, the underlying
624   data &MUST; be in a form defined above prior to being encoded.
[211]627   The "charset" parameter is used with some media types to define the
628   character set (<xref target="character.sets"/>) of the data. When no explicit charset
629   parameter is provided by the sender, media subtypes of the "text"
630   type are defined to have a default charset value of "ISO-8859-1" when
631   received via HTTP. Data in character sets other than "ISO-8859-1" or
632   its subsets &MUST; be labeled with an appropriate charset value. See
633   <xref target="missing.charset"/> for compatibility problems.
637<section title="Multipart Types" anchor="multipart.types">
639   MIME provides for a number of "multipart" types -- encapsulations of
640   one or more entities within a single message-body. All multipart
[97]641   types share a common syntax, as defined in <xref target="RFC2046" x:sec="5.1.1" x:fmt="of"/>,
642   and &MUST; include a boundary parameter as part of the media type
[8]643   value. The message body is itself a protocol element and &MUST;
644   therefore use only CRLF to represent line breaks between body-parts.
645   Unlike in RFC 2046, the epilogue of any multipart message &MUST; be
646   empty; HTTP applications &MUST-NOT; transmit the epilogue (even if the
647   original multipart contains an epilogue). These restrictions exist in
648   order to preserve the self-delimiting nature of a multipart message-body,
649   wherein the "end" of the message-body is indicated by the
650   ending multipart boundary.
653   In general, HTTP treats a multipart message-body no differently than
654   any other media type: strictly as payload. The one exception is the
[29]655   "multipart/byteranges" type (&multipart-byteranges;) when it appears in a 206
[97]656   (Partial Content) response.
657   <!-- jre: re-insert removed text pointing to caching? -->
658   In all
[8]659   other cases, an HTTP user agent &SHOULD; follow the same or similar
660   behavior as a MIME user agent would upon receipt of a multipart type.
661   The MIME header fields within each body-part of a multipart message-body
662   do not have any significance to HTTP beyond that defined by
663   their MIME semantics.
666   In general, an HTTP user agent &SHOULD; follow the same or similar
667   behavior as a MIME user agent would upon receipt of a multipart type.
668   If an application receives an unrecognized multipart subtype, the
669   application &MUST; treat it as being equivalent to "multipart/mixed".
672  <t>
673    <x:h>Note:</x:h> The "multipart/form-data" type has been specifically defined
674    for carrying form data suitable for processing via the POST
675    request method, as described in <xref target="RFC2388"/>.
676  </t>
681<section title="Language Tags" anchor="language.tags">
[229]682  <x:anchor-alias value="language-tag"/>
[690]684   A language tag, as defined in <xref target="RFC5646"/>, identifies a
[613]685   natural language spoken, written, or otherwise conveyed by human beings for
686   communication of information to other human beings. Computer languages are
687   explicitly excluded. HTTP uses language tags within the Accept-Language and
688   Content-Language fields.
[613]691   In summary, a language tag is composed of one or more parts: A primary
692   language subtag followed by a possibly empty series of subtags:
[613]694<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="language-tag"/>
[690]695  <x:ref>language-tag</x:ref> = &lt;Language-Tag, defined in <xref target="RFC5646" x:sec="2.1"/>&gt;
698   White space is not allowed within the tag and all tags are case-insensitive.
[613]699   The name space of language subtags is administered by the IANA (see
700   <eref target=""/>).
703  <preamble>Example tags include:</preamble>
704<artwork type="example">
705  en, en-US, es-419, az-Arab, x-pig-latin, man-Nkoo-GN
[690]709   See <xref target="RFC5646"/> for further information.
714<section title="Entity" anchor="entity">
716   Request and Response messages &MAY; transfer an entity if not otherwise
717   restricted by the request method or response status code. An entity
718   consists of entity-header fields and an entity-body, although some
719   responses will only include the entity-headers.
722   In this section, both sender and recipient refer to either the client
723   or the server, depending on who sends and who receives the entity.
726<section title="Entity Header Fields" anchor="entity.header.fields">
[229]727  <x:anchor-alias value="entity-header"/>
728  <x:anchor-alias value="extension-header"/>
730   Entity-header fields define metainformation about the entity-body or,
731   if no body is present, about the resource identified by the request.
733<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="entity-header"/><iref primary="true" item="Grammar" subitem="extension-header"/>
[232]734  <x:ref>entity-header</x:ref>  = <x:ref>Content-Encoding</x:ref>         ; <xref target="header.content-encoding"/>
[334]735                 / <x:ref>Content-Language</x:ref>         ; <xref target="header.content-language"/>
736                 / <x:ref>Content-Length</x:ref>           ; &header-content-length;
737                 / <x:ref>Content-Location</x:ref>         ; <xref target="header.content-location"/>
738                 / <x:ref>Content-MD5</x:ref>              ; <xref target="header.content-md5"/>
739                 / <x:ref>Content-Range</x:ref>            ; &header-content-range;
740                 / <x:ref>Content-Type</x:ref>             ; <xref target="header.content-type"/>
741                 / <x:ref>Expires</x:ref>                  ; &header-expires;
742                 / <x:ref>Last-Modified</x:ref>            ; &header-last-modified;
743                 / <x:ref>extension-header</x:ref>
[647]745  <x:ref>extension-header</x:ref> = <x:ref>header-field</x:ref>
748   The extension-header mechanism allows additional entity-header fields
749   to be defined without changing the protocol, but these fields cannot
750   be assumed to be recognizable by the recipient. Unrecognized header
751   fields &SHOULD; be ignored by the recipient and &MUST; be forwarded by
752   transparent proxies.
756<section title="Entity Body" anchor="entity.body">
[229]757  <x:anchor-alias value="entity-body"/>
759   The entity-body (if any) sent with an HTTP request or response is in
760   a format and encoding defined by the entity-header fields.
762<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="entity-body"/>
[229]763  <x:ref>entity-body</x:ref>    = *<x:ref>OCTET</x:ref>
766   An entity-body is only present in a message when a message-body is
[29]767   present, as described in &message-body;. The entity-body is obtained
[8]768   from the message-body by decoding any Transfer-Encoding that might
769   have been applied to ensure safe and proper transfer of the message.
772<section title="Type" anchor="type">
774   When an entity-body is included with a message, the data type of that
775   body is determined via the header fields Content-Type and Content-Encoding.
776   These define a two-layer, ordered encoding model:
778<figure><artwork type="example">
[458]779  entity-body := Content-Encoding( Content-Type( data ) )
[592]782   Content-Type specifies the media type of the underlying data. Any HTTP/1.1
783   message containing an entity-body &SHOULD; include a Content-Type header
784   field defining the media type of that body, unless that information is
785   unknown.  If the Content-Type header field is not present, it indicates that
786   the sender does not know the media type of the data; recipients &MAY;
787   either assume that it is "application/octet-stream" (<xref target="RFC2046" x:fmt="," x:sec="4.5.1"/>)
788   or examine the content to determine its type.
[8]791   Content-Encoding may be used to indicate any additional content
792   codings applied to the data, usually for the purpose of data
[592]793   compression, that are a property of the requested resource.  There is
[8]794   no default encoding.
798<section title="Entity Length" anchor="entity.length">
800   The entity-length of a message is the length of the message-body
[29]801   before any transfer-codings have been applied. &message-length; defines
[8]802   how the transfer-length of a message-body is determined.
808<section title="Content Negotiation" anchor="content.negotiation">
[745]810   HTTP responses include a representation which contains information for
811   interpretation, whether by a human user or for further processing.
812   Often, the server has different ways of representing the
813   same information; for example, in different formats, languages,
814   or using different character encodings.
[745]817   HTTP clients and their users might have different or variable
818   capabilities, characteristics or preferences which would influence
819   which representation, among those available from the server,
820   would be best for the server to deliver. For this reason, HTTP
821   provides mechanisms for "content negotiation" -- a process of
822   allowing selection of a representation of a given resource,
823   when more than one is available.
[745]826   This specification defines two patterns of content negotiation;
827   "server-driven", where the server selects the representation based
828   upon the client's stated preferences, and "agent-driven" negotiation,
829   where the server provides a list of representations for the client to
830   choose from, based upon their metadata. In addition,  there are
831   other patterns: some applications use an "active content" pattern,
832   where the server returns active content which runs on the client
833   and, based on client available parameters, selects additional
834   resources to invoke. "Transparent Content Negotiation" (<xref target="RFC2295"/>)
835   has also been proposed.
838   These patterns are all widely used, and have trade-offs in applicability
839   and practicality. In particular, when the number of preferences or
840   capabilities to be expressed by a client are large (such as when many
841   different formats are supported by a user-agent), server-driven
842   negotiation becomes unwieldy, and may not be appropriate. Conversely,
843   when the number of representations to choose from is very large,
844   agent-driven negotiation may not be appropriate.
847   Note that in all cases, the supplier of representations has the
848   responsibility for determining which representations might be
849   considered to be the "same information".
852<section title="Server-driven Negotiation" anchor="server-driven.negotiation">
854   If the selection of the best representation for a response is made by
855   an algorithm located at the server, it is called server-driven
856   negotiation. Selection is based on the available representations of
[763]857   the response (the dimensions over which it can vary; e.g., language,
[8]858   content-coding, etc.) and the contents of particular header fields in
859   the request message or on other information pertaining to the request
860   (such as the network address of the client).
863   Server-driven negotiation is advantageous when the algorithm for
864   selecting from among the available representations is difficult to
865   describe to the user agent, or when the server desires to send its
866   "best guess" to the client along with the first response (hoping to
867   avoid the round-trip delay of a subsequent request if the "best
868   guess" is good enough for the user). In order to improve the server's
869   guess, the user agent &MAY; include request header fields (Accept,
870   Accept-Language, Accept-Encoding, etc.) which describe its
871   preferences for such a response.
874   Server-driven negotiation has disadvantages:
875  <list style="numbers">
876    <t>
877         It is impossible for the server to accurately determine what
878         might be "best" for any given user, since that would require
879         complete knowledge of both the capabilities of the user agent
880         and the intended use for the response (e.g., does the user want
881         to view it on screen or print it on paper?).
882    </t>
883    <t>
884         Having the user agent describe its capabilities in every
885         request can be both very inefficient (given that only a small
886         percentage of responses have multiple representations) and a
887         potential violation of the user's privacy.
888    </t>
889    <t>
890         It complicates the implementation of an origin server and the
891         algorithms for generating responses to a request.
892    </t>
893    <t>
894         It may limit a public cache's ability to use the same response
895         for multiple user's requests.
896    </t>
897  </list>
900   HTTP/1.1 includes the following request-header fields for enabling
901   server-driven negotiation through description of user agent
902   capabilities and user preferences: Accept (<xref target="header.accept"/>), Accept-Charset
903   (<xref target="header.accept-charset"/>), Accept-Encoding (<xref target="header.accept-encoding"/>), Accept-Language
[745]904   (<xref target="header.accept-language"/>), and User-Agent (&header-user-agent;).
905   However, an origin server is not limited to these dimensions and &MAY; vary
906   the response based on any aspect of the request, including information
[8]907   outside the request-header fields or within extension header fields
908   not defined by this specification.
911  <t>
912    <x:h>Note:</x:h> In practice, User-Agent based negotiation is fragile,
913    because new clients might not be recognized.
914  </t>
[115]917   The Vary header field (&header-vary;) can be used to express the parameters the
[8]918   server uses to select a representation that is subject to server-driven
[29]919   negotiation.
923<section title="Agent-driven Negotiation" anchor="agent-driven.negotiation">
925   With agent-driven negotiation, selection of the best representation
926   for a response is performed by the user agent after receiving an
927   initial response from the origin server. Selection is based on a list
928   of the available representations of the response included within the
929   header fields or entity-body of the initial response, with each
930   representation identified by its own URI. Selection from among the
931   representations may be performed automatically (if the user agent is
932   capable of doing so) or manually by the user selecting from a
933   generated (possibly hypertext) menu.
936   Agent-driven negotiation is advantageous when the response would vary
937   over commonly-used dimensions (such as type, language, or encoding),
938   when the origin server is unable to determine a user agent's
939   capabilities from examining the request, and generally when public
940   caches are used to distribute server load and reduce network usage.
943   Agent-driven negotiation suffers from the disadvantage of needing a
944   second request to obtain the best alternate representation. This
945   second request is only efficient when caching is used. In addition,
946   this specification does not define any mechanism for supporting
947   automatic selection, though it also does not prevent any such
948   mechanism from being developed as an extension and used within
949   HTTP/1.1.
[745]952   This specification defines the 300 (Multiple Choices) and 406 (Not Acceptable)
[8]953   status codes for enabling agent-driven negotiation when the server is
954   unwilling or unable to provide a varying response using server-driven
955   negotiation.
[8]960<section title="Header Field Definitions" anchor="header.fields">
[117]962   This section defines the syntax and semantics of HTTP/1.1 header fields
963   related to the payload of messages.
966   For entity-header fields, both sender and recipient refer to either the
967   client or the server, depending on who sends and who receives the entity.
[8]970<section title="Accept" anchor="header.accept">
971  <iref primary="true" item="Accept header" x:for-anchor=""/>
972  <iref primary="true" item="Headers" subitem="Accept" x:for-anchor=""/>
[229]973  <x:anchor-alias value="Accept"/>
[357]974  <x:anchor-alias value="Accept-v"/>
[370]975  <x:anchor-alias value="accept-ext"/>
[229]976  <x:anchor-alias value="accept-params"/>
977  <x:anchor-alias value="media-range"/>
[698]979   The "Accept" request-header field can be used by user agents to specify
980   response media types that are acceptable. Accept headers can be used to
981   indicate that the request is specifically limited to a small set of desired
982   types, as in the case of a request for an in-line image.
[370]984<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Accept"/><iref primary="true" item="Grammar" subitem="Accept-v"/><iref primary="true" item="Grammar" subitem="media-range"/><iref primary="true" item="Grammar" subitem="accept-params"/><iref primary="true" item="Grammar" subitem="accept-ext"/>
[366]985  <x:ref>Accept</x:ref>   = "Accept" ":" <x:ref>OWS</x:ref> <x:ref>Accept-v</x:ref>
[357]986  <x:ref>Accept-v</x:ref> = #( <x:ref>media-range</x:ref> [ <x:ref>accept-params</x:ref> ] )
[229]988  <x:ref>media-range</x:ref>    = ( "*/*"
[334]989                   / ( <x:ref>type</x:ref> "/" "*" )
990                   / ( <x:ref>type</x:ref> "/" <x:ref>subtype</x:ref> )
[370]991                   ) *( <x:ref>OWS</x:ref> ";" <x:ref>OWS</x:ref> <x:ref>parameter</x:ref> )
992  <x:ref>accept-params</x:ref>  = <x:ref>OWS</x:ref> ";" <x:ref>OWS</x:ref> "q=" <x:ref>qvalue</x:ref> *( <x:ref>accept-ext</x:ref> )
[376]993  <x:ref>accept-ext</x:ref>     = <x:ref>OWS</x:ref> ";" <x:ref>OWS</x:ref> <x:ref>token</x:ref>
994                   [ "=" ( <x:ref>token</x:ref> / <x:ref>quoted-string</x:ref> ) ]
997   The asterisk "*" character is used to group media types into ranges,
998   with "*/*" indicating all media types and "type/*" indicating all
999   subtypes of that type. The media-range &MAY; include media type
1000   parameters that are applicable to that range.
1003   Each media-range &MAY; be followed by one or more accept-params,
1004   beginning with the "q" parameter for indicating a relative quality
1005   factor. The first "q" parameter (if any) separates the media-range
1006   parameter(s) from the accept-params. Quality factors allow the user
1007   or user agent to indicate the relative degree of preference for that
[457]1008   media-range, using the qvalue scale from 0 to 1 (&qvalue;). The
[8]1009   default value is q=1.
1012  <t>
1013    <x:h>Note:</x:h> Use of the "q" parameter name to separate media type
1014    parameters from Accept extension parameters is due to historical
1015    practice. Although this prevents any media type parameter named
1016    "q" from being used with a media range, such an event is believed
1017    to be unlikely given the lack of any "q" parameters in the IANA
1018    media type registry and the rare usage of any media type
1019    parameters in Accept. Future media types are discouraged from
1020    registering any parameter named "q".
1021  </t>
1024   The example
1026<figure><artwork type="example">
[357]1027  Accept: audio/*; q=0.2, audio/basic
1030   &SHOULD; be interpreted as "I prefer audio/basic, but send me any audio
1031   type if it is the best available after an 80% mark-down in quality."
1034   If no Accept header field is present, then it is assumed that the
1035   client accepts all media types. If an Accept header field is present,
1036   and if the server cannot send a response which is acceptable
1037   according to the combined Accept field value, then the server &SHOULD;
[137]1038   send a 406 (Not Acceptable) response.
1041   A more elaborate example is
1043<figure><artwork type="example">
[357]1044  Accept: text/plain; q=0.5, text/html,
1045          text/x-dvi; q=0.8, text/x-c
1048   Verbally, this would be interpreted as "text/html and text/x-c are
1049   the preferred media types, but if they do not exist, then send the
1050   text/x-dvi entity, and if that does not exist, send the text/plain
1051   entity."
1054   Media ranges can be overridden by more specific media ranges or
1055   specific media types. If more than one media range applies to a given
1056   type, the most specific reference has precedence. For example,
1058<figure><artwork type="example">
[357]1059  Accept: text/*, text/html, text/html;level=1, */*
1062   have the following precedence:
[459]1063   <list style="numbers">
1064    <t>text/html;level=1</t>
1065    <t>text/html</t>
1066    <t>text/*</t>
1067    <t>*/*</t>
1068   </list>
1071   The media type quality factor associated with a given type is
1072   determined by finding the media range with the highest precedence
1073   which matches that type. For example,
1075<figure><artwork type="example">
[357]1076  Accept: text/*;q=0.3, text/html;q=0.7, text/html;level=1,
1077          text/html;level=2;q=0.4, */*;q=0.5
1080   would cause the following values to be associated:
[459]1082<texttable align="left">
1083  <ttcol>Media Type</ttcol><ttcol>Quality Value</ttcol>
1084  <c>text/html;level=1</c>    <c>1</c>
1085  <c>text/html</c>            <c>0.7</c>
1086  <c>text/plain</c>           <c>0.3</c>
1087  <c>image/jpeg</c>           <c>0.5</c>
1088  <c>text/html;level=2</c>    <c>0.4</c>
1089  <c>text/html;level=3</c>    <c>0.7</c>
1092      <x:h>Note:</x:h> A user agent might be provided with a default set of quality
1093      values for certain media ranges. However, unless the user agent is
1094      a closed system which cannot interact with other rendering agents,
1095      this default set ought to be configurable by the user.
1099<section title="Accept-Charset" anchor="header.accept-charset">
1100  <iref primary="true" item="Accept-Charset header" x:for-anchor=""/>
1101  <iref primary="true" item="Headers" subitem="Accept-Charset" x:for-anchor=""/>
[229]1102  <x:anchor-alias value="Accept-Charset"/>
[357]1103  <x:anchor-alias value="Accept-Charset-v"/>
[698]1105   The "Accept-Charset" request-header field can be used by user agents to
1106   indicate what response character sets are acceptable. This field allows
[8]1107   clients capable of understanding more comprehensive or special-purpose
[698]1108   character sets to signal that capability to a server which is capable of
1109   representing documents in those character sets.
[357]1111<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Accept-Charset"/><iref primary="true" item="Grammar" subitem="Accept-Charset-v"/>
[366]1112  <x:ref>Accept-Charset</x:ref>   = "Accept-Charset" ":" <x:ref>OWS</x:ref>
[357]1113          <x:ref>Accept-Charset-v</x:ref>
[376]1114  <x:ref>Accept-Charset-v</x:ref> = 1#( ( <x:ref>charset</x:ref> / "*" )
1115                         [ <x:ref>OWS</x:ref> ";" <x:ref>OWS</x:ref> "q=" <x:ref>qvalue</x:ref> ] )
1118   Character set values are described in <xref target="character.sets"/>. Each charset &MAY;
1119   be given an associated quality value which represents the user's
1120   preference for that charset. The default value is q=1. An example is
1122<figure><artwork type="example">
[357]1123  Accept-Charset: iso-8859-5, unicode-1-1;q=0.8
1126   The special value "*", if present in the Accept-Charset field,
1127   matches every character set (including ISO-8859-1) which is not
1128   mentioned elsewhere in the Accept-Charset field. If no "*" is present
1129   in an Accept-Charset field, then all character sets not explicitly
1130   mentioned get a quality value of 0, except for ISO-8859-1, which gets
1131   a quality value of 1 if not explicitly mentioned.
1134   If no Accept-Charset header is present, the default is that any
1135   character set is acceptable. If an Accept-Charset header is present,
1136   and if the server cannot send a response which is acceptable
1137   according to the Accept-Charset header, then the server &SHOULD; send
[137]1138   an error response with the 406 (Not Acceptable) status code, though
[8]1139   the sending of an unacceptable response is also allowed.
1143<section title="Accept-Encoding" anchor="header.accept-encoding">
1144  <iref primary="true" item="Accept-Encoding header" x:for-anchor=""/>
1145  <iref primary="true" item="Headers" subitem="Accept-Encoding" x:for-anchor=""/>
[229]1146  <x:anchor-alias value="Accept-Encoding"/>
[357]1147  <x:anchor-alias value="Accept-Encoding-v"/>
[229]1148  <x:anchor-alias value="codings"/>
[698]1150   The "Accept-Encoding" request-header field can be used by user agents to
1151   indicate what response content-codings (<xref target="content.codings"/>)
1152   are acceptable in the response.
[357]1154<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Accept-Encoding"/><iref primary="true" item="Grammar" subitem="Accept-Encoding-v"/><iref primary="true" item="Grammar" subitem="codings"/>
[366]1155  <x:ref>Accept-Encoding</x:ref>    = "Accept-Encoding" ":" <x:ref>OWS</x:ref>
[357]1156                     <x:ref>Accept-Encoding-v</x:ref>
1157  <x:ref>Accept-Encoding-v</x:ref>  =
[370]1158                     #( <x:ref>codings</x:ref> [ <x:ref>OWS</x:ref> ";" <x:ref>OWS</x:ref> "q=" <x:ref>qvalue</x:ref> ] )
[357]1159  <x:ref>codings</x:ref>            = ( <x:ref>content-coding</x:ref> / "*" )
[248]1162   Each codings value &MAY; be given an associated quality value which
1163   represents the preference for that encoding. The default value is q=1.
[8]1166   Examples of its use are:
1168<figure><artwork type="example">
[357]1169  Accept-Encoding: compress, gzip
1170  Accept-Encoding:
1171  Accept-Encoding: *
1172  Accept-Encoding: compress;q=0.5, gzip;q=1.0
1173  Accept-Encoding: gzip;q=1.0, identity; q=0.5, *;q=0
1176   A server tests whether a content-coding is acceptable, according to
1177   an Accept-Encoding field, using these rules:
1178  <list style="numbers">
1179      <t>If the content-coding is one of the content-codings listed in
1180         the Accept-Encoding field, then it is acceptable, unless it is
[457]1181         accompanied by a qvalue of 0. (As defined in &qvalue;, a
[8]1182         qvalue of 0 means "not acceptable.")</t>
1184      <t>The special "*" symbol in an Accept-Encoding field matches any
1185         available content-coding not explicitly listed in the header
1186         field.</t>
1188      <t>If multiple content-codings are acceptable, then the acceptable
1189         content-coding with the highest non-zero qvalue is preferred.</t>
1191      <t>The "identity" content-coding is always acceptable, unless
1192         specifically refused because the Accept-Encoding field includes
1193         "identity;q=0", or because the field includes "*;q=0" and does
1194         not explicitly include the "identity" content-coding. If the
1195         Accept-Encoding field-value is empty, then only the "identity"
1196         encoding is acceptable.</t>
1197  </list>
1200   If an Accept-Encoding field is present in a request, and if the
1201   server cannot send a response which is acceptable according to the
1202   Accept-Encoding header, then the server &SHOULD; send an error response
1203   with the 406 (Not Acceptable) status code.
1206   If no Accept-Encoding field is present in a request, the server &MAY;
1207   assume that the client will accept any content coding. In this case,
1208   if "identity" is one of the available content-codings, then the
1209   server &SHOULD; use the "identity" content-coding, unless it has
1210   additional information that a different content-coding is meaningful
1211   to the client.
1214  <t>
1215    <x:h>Note:</x:h> If the request does not include an Accept-Encoding field,
1216    and if the "identity" content-coding is unavailable, then
1217    content-codings commonly understood by HTTP/1.0 clients (i.e.,
1218    "gzip" and "compress") are preferred; some older clients
1219    improperly display messages sent with other content-codings.  The
1220    server might also make this decision based on information about
1221    the particular user-agent or client.
1222  </t>
1225  <t>
1226    <x:h>Note:</x:h> Most HTTP/1.0 applications do not recognize or obey qvalues
1227    associated with content-codings. This means that qvalues will not
1228    work and are not permitted with x-gzip or x-compress.
1229  </t>
1233<section title="Accept-Language" anchor="header.accept-language">
1234  <iref primary="true" item="Accept-Language header" x:for-anchor=""/>
1235  <iref primary="true" item="Headers" subitem="Accept-Language" x:for-anchor=""/>
[229]1236  <x:anchor-alias value="Accept-Language"/>
[357]1237  <x:anchor-alias value="Accept-Language-v"/>
[229]1238  <x:anchor-alias value="language-range"/>
[698]1240   The "Accept-Language" request-header field can be used by user agents to
1241   indicate the set of natural languages that are preferred in the response.
1242   Language tags are defined in <xref target="language.tags"/>.
[357]1244<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Accept-Language"/><iref primary="true" item="Grammar" subitem="Accept-Language-v"/><iref primary="true" item="Grammar" subitem="language-range"/>
[366]1245  <x:ref>Accept-Language</x:ref>   = "Accept-Language" ":" <x:ref>OWS</x:ref>
[357]1246                    <x:ref>Accept-Language-v</x:ref>
1247  <x:ref>Accept-Language-v</x:ref> =
[370]1248                    1#( <x:ref>language-range</x:ref> [ <x:ref>OWS</x:ref> ";" <x:ref>OWS</x:ref> "q=" <x:ref>qvalue</x:ref> ] )
[357]1249  <x:ref>language-range</x:ref>    =
[303]1250            &lt;language-range, defined in <xref target="RFC4647" x:fmt="," x:sec="2.1"/>&gt;
[303]1253   Each language-range can be given an associated quality value which
[8]1254   represents an estimate of the user's preference for the languages
1255   specified by that range. The quality value defaults to "q=1". For
1256   example,
1258<figure><artwork type="example">
[357]1259  Accept-Language: da, en-gb;q=0.8, en;q=0.7
1262   would mean: "I prefer Danish, but will accept British English and
[303]1263   other types of English."
[724]1264   (see also <xref target="RFC4647" x:sec="2.3" x:fmt="of"/>)
[724]1267   For matching, <xref target="RFC4647" x:sec="3" x:fmt="of"/> defines
1268   several matching schemes. Implementations can offer the most appropriate
1269   matching scheme for their requirements.
1272  <t>
[756]1273    <x:h>Note:</x:h> The "Basic Filtering" scheme (<xref target="RFC4647"
[724]1274    x:fmt="," x:sec="3.3.1"/>) is identical to the matching scheme that was
1275    previously defined in <xref target="RFC2616" x:fmt="of" x:sec="14.4"/>.
[563]1276  </t>
1279   It might be contrary to the privacy expectations of the user to send
1280   an Accept-Language header with the complete linguistic preferences of
1281   the user in every request. For a discussion of this issue, see
1282   <xref target=""/>.
1285   As intelligibility is highly dependent on the individual user, it is
1286   recommended that client applications make the choice of linguistic
1287   preference available to the user. If the choice is not made
1288   available, then the Accept-Language header field &MUST-NOT; be given in
1289   the request.
1292  <t>
1293    <x:h>Note:</x:h> When making the choice of linguistic preference available to
1294    the user, we remind implementors of  the fact that users are not
1295    familiar with the details of language matching as described above,
1296    and should provide appropriate guidance. As an example, users
1297    might assume that on selecting "en-gb", they will be served any
1298    kind of English document if British English is not available. A
1299    user agent might suggest in such a case to add "en" to get the
1300    best matching behavior.
1301  </t>
1305<section title="Content-Encoding" anchor="header.content-encoding">
1306  <iref primary="true" item="Content-Encoding header" x:for-anchor=""/>
1307  <iref primary="true" item="Headers" subitem="Content-Encoding" x:for-anchor=""/>
[229]1308  <x:anchor-alias value="Content-Encoding"/>
[357]1309  <x:anchor-alias value="Content-Encoding-v"/>
[698]1311   The "Content-Encoding" entity-header field indicates what content-codings
1312   have been applied to the entity-body, and thus what decoding mechanisms
1313   must be applied in order to obtain the media-type referenced by the
1314   Content-Type header field. Content-Encoding is primarily used to allow a
1315   document to be compressed without losing the identity of its underlying
1316   media type.
[357]1318<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Content-Encoding"/><iref primary="true" item="Grammar" subitem="Content-Encoding-v"/>
[366]1319  <x:ref>Content-Encoding</x:ref>   = "Content-Encoding" ":" <x:ref>OWS</x:ref> <x:ref>Content-Encoding-v</x:ref>
[357]1320  <x:ref>Content-Encoding-v</x:ref> = 1#<x:ref>content-coding</x:ref>
1323   Content codings are defined in <xref target="content.codings"/>. An example of its use is
1325<figure><artwork type="example">
[357]1326  Content-Encoding: gzip
1329   The content-coding is a characteristic of the entity identified by
[391]1330   the request-target. Typically, the entity-body is stored with this
[8]1331   encoding and is only decoded before rendering or analogous usage.
1332   However, a non-transparent proxy &MAY; modify the content-coding if the
1333   new coding is known to be acceptable to the recipient, unless the
1334   "no-transform" cache-control directive is present in the message.
1337   If the content-coding of an entity is not "identity", then the
1338   response &MUST; include a Content-Encoding entity-header (<xref target="header.content-encoding"/>)
1339   that lists the non-identity content-coding(s) used.
1342   If the content-coding of an entity in a request message is not
1343   acceptable to the origin server, the server &SHOULD; respond with a
1344   status code of 415 (Unsupported Media Type).
1347   If multiple encodings have been applied to an entity, the content
1348   codings &MUST; be listed in the order in which they were applied.
1349   Additional information about the encoding parameters &MAY; be provided
1350   by other entity-header fields not defined by this specification.
1354<section title="Content-Language" anchor="header.content-language">
1355  <iref primary="true" item="Content-Language header" x:for-anchor=""/>
1356  <iref primary="true" item="Headers" subitem="Content-Language" x:for-anchor=""/>
[229]1357  <x:anchor-alias value="Content-Language"/>
[357]1358  <x:anchor-alias value="Content-Language-v"/>
[697]1360   The "Content-Language" entity-header field describes the natural
[698]1361   language(s) of the intended audience for the entity. Note that this might
1362   not be equivalent to all the languages used within the entity-body.
[357]1364<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Content-Language"/><iref primary="true" item="Grammar" subitem="Content-Language-v"/>
[366]1365  <x:ref>Content-Language</x:ref>   = "Content-Language" ":" <x:ref>OWS</x:ref> <x:ref>Content-Language-v</x:ref>
[357]1366  <x:ref>Content-Language-v</x:ref> = 1#<x:ref>language-tag</x:ref>
1369   Language tags are defined in <xref target="language.tags"/>. The primary purpose of
1370   Content-Language is to allow a user to identify and differentiate
1371   entities according to the user's own preferred language. Thus, if the
1372   body content is intended only for a Danish-literate audience, the
1373   appropriate field is
1375<figure><artwork type="example">
[357]1376  Content-Language: da
1379   If no Content-Language is specified, the default is that the content
1380   is intended for all language audiences. This might mean that the
1381   sender does not consider it to be specific to any natural language,
1382   or that the sender does not know for which language it is intended.
1385   Multiple languages &MAY; be listed for content that is intended for
1386   multiple audiences. For example, a rendition of the "Treaty of
1387   Waitangi," presented simultaneously in the original Maori and English
1388   versions, would call for
1390<figure><artwork type="example">
[357]1391  Content-Language: mi, en
1394   However, just because multiple languages are present within an entity
1395   does not mean that it is intended for multiple linguistic audiences.
1396   An example would be a beginner's language primer, such as "A First
1397   Lesson in Latin," which is clearly intended to be used by an
1398   English-literate audience. In this case, the Content-Language would
1399   properly only include "en".
1402   Content-Language &MAY; be applied to any media type -- it is not
1403   limited to textual documents.
1407<section title="Content-Location" anchor="header.content-location">
1408  <iref primary="true" item="Content-Location header" x:for-anchor=""/>
1409  <iref primary="true" item="Headers" subitem="Content-Location" x:for-anchor=""/>
[229]1410  <x:anchor-alias value="Content-Location"/>
[357]1411  <x:anchor-alias value="Content-Location-v"/>
[698]1413   The "Content-Location" entity-header field is used to supply a URI for the
1414   entity in the message when it is accessible from a location separate from
1415   the requested resource's URI.
1418   A server &SHOULD; provide a Content-Location for the variant corresponding
1419   to the response entity, especially in the case where a resource has multiple
1420   entities associated with it, and those entities actually have separate
1421   locations by which they might be individually accessed, the server &SHOULD;
1422   provide a Content-Location for the particular variant which is returned.
[357]1424<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Content-Location"/><iref primary="true" item="Grammar" subitem="Content-Location-v"/>
[366]1425  <x:ref>Content-Location</x:ref>   = "Content-Location" ":" <x:ref>OWS</x:ref>
[357]1426                    <x:ref>Content-Location-v</x:ref>
1427  <x:ref>Content-Location-v</x:ref> =
[391]1428                    <x:ref>absolute-URI</x:ref> / <x:ref>partial-URI</x:ref>
1431   The Content-Location value is not a replacement for the original
1432   requested URI; it is only a statement of the location of the resource
1433   corresponding to this particular entity at the time of the request.
[391]1434   Future requests &MAY; specify the Content-Location URI as the request-target
[8]1435   if the desire is to identify the source of that particular
1436   entity.
[716]1439   &response-representation; describes how clients may process the Content-Location header field.
[8]1442   A cache cannot assume that an entity with a Content-Location
1443   different from the URI used to retrieve it can be used to respond to
1444   later requests on that Content-Location URI. However, the Content-Location
1445   can be used to differentiate between multiple entities
[115]1446   retrieved from a single requested resource, as described in &caching-neg-resp;.
1449   If the Content-Location is a relative URI, the relative URI is
[391]1450   interpreted relative to the request-target.
[577]1453   The meaning of the Content-Location header in requests is
[8]1454   undefined; servers are free to ignore it in those cases.
1458<section title="Content-MD5" anchor="header.content-md5">
1459  <iref primary="true" item="Content-MD5 header" x:for-anchor=""/>
1460  <iref primary="true" item="Headers" subitem="Content-MD5" x:for-anchor=""/>
[229]1461  <x:anchor-alias value="Content-MD5"/>
[357]1462  <x:anchor-alias value="Content-MD5-v"/>
[697]1464   The "Content-MD5" entity-header field, as defined in <xref target="RFC1864"/>, is
[699]1465   an MD5 digest of the entity-body that provides an end-to-end message
1466   integrity check (MIC) of the entity-body. Note that a MIC is good for
1467   detecting accidental modification of the entity-body in transit, but is not
1468   proof against malicious attacks.
[357]1470<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Content-MD5"/><iref primary="true" item="Grammar" subitem="Content-MD5-v"/>
[366]1471  <x:ref>Content-MD5</x:ref>   = "Content-MD5" ":" <x:ref>OWS</x:ref> <x:ref>Content-MD5-v</x:ref>
[357]1472  <x:ref>Content-MD5-v</x:ref> = &lt;base64 of 128 bit MD5 digest as per <xref target="RFC1864"/>&gt;
1475   The Content-MD5 header field &MAY; be generated by an origin server or
1476   client to function as an integrity check of the entity-body. Only
1477   origin servers or clients &MAY; generate the Content-MD5 header field;
1478   proxies and gateways &MUST-NOT; generate it, as this would defeat its
1479   value as an end-to-end integrity check. Any recipient of the entity-body,
1480   including gateways and proxies, &MAY; check that the digest value
1481   in this header field matches that of the entity-body as received.
1484   The MD5 digest is computed based on the content of the entity-body,
1485   including any content-coding that has been applied, but not including
1486   any transfer-encoding applied to the message-body. If the message is
1487   received with a transfer-encoding, that encoding &MUST; be removed
1488   prior to checking the Content-MD5 value against the received entity.
1491   This has the result that the digest is computed on the octets of the
1492   entity-body exactly as, and in the order that, they would be sent if
1493   no transfer-encoding were being applied.
1496   HTTP extends RFC 1864 to permit the digest to be computed for MIME
1497   composite media-types (e.g., multipart/* and message/rfc822), but
1498   this does not change how the digest is computed as defined in the
1499   preceding paragraph.
1502   There are several consequences of this. The entity-body for composite
1503   types &MAY; contain many body-parts, each with its own MIME and HTTP
1504   headers (including Content-MD5, Content-Transfer-Encoding, and
1505   Content-Encoding headers). If a body-part has a Content-Transfer-Encoding
1506   or Content-Encoding header, it is assumed that the content
1507   of the body-part has had the encoding applied, and the body-part is
1508   included in the Content-MD5 digest as is -- i.e., after the
1509   application. The Transfer-Encoding header field is not allowed within
1510   body-parts.
1513   Conversion of all line breaks to CRLF &MUST-NOT; be done before
1514   computing or checking the digest: the line break convention used in
1515   the text actually transmitted &MUST; be left unaltered when computing
1516   the digest.
1519  <t>
[756]1520    <x:h>Note:</x:h> While the definition of Content-MD5 is exactly the same for
[563]1521    HTTP as in RFC 1864 for MIME entity-bodies, there are several ways
1522    in which the application of Content-MD5 to HTTP entity-bodies
1523    differs from its application to MIME entity-bodies. One is that
1524    HTTP, unlike MIME, does not use Content-Transfer-Encoding, and
1525    does use Transfer-Encoding and Content-Encoding. Another is that
1526    HTTP more frequently uses binary content types than MIME, so it is
1527    worth noting that, in such cases, the byte order used to compute
1528    the digest is the transmission byte order defined for the type.
1529    Lastly, HTTP allows transmission of text types with any of several
1530    line break conventions and not just the canonical form using CRLF.
1531  </t>
1535<section title="Content-Type" anchor="header.content-type">
1536  <iref primary="true" item="Content-Type header" x:for-anchor=""/>
1537  <iref primary="true" item="Headers" subitem="Content-Type" x:for-anchor=""/>
[229]1538  <x:anchor-alias value="Content-Type"/>
[357]1539  <x:anchor-alias value="Content-Type-v"/>
[697]1541   The "Content-Type" entity-header field indicates the media type of the
[698]1542   entity-body. In the case of responses to the HEAD method, the media type is
1543   that which would have been sent had the request been a GET.
[357]1545<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Content-Type"/><iref primary="true" item="Grammar" subitem="Content-Type-v"/>
[366]1546  <x:ref>Content-Type</x:ref>   = "Content-Type" ":" <x:ref>OWS</x:ref> <x:ref>Content-Type-v</x:ref>
[357]1547  <x:ref>Content-Type-v</x:ref> = <x:ref>media-type</x:ref>
1550   Media types are defined in <xref target="media.types"/>. An example of the field is
1552<figure><artwork type="example">
[357]1553  Content-Type: text/html; charset=ISO-8859-4
1556   Further discussion of methods for identifying the media type of an
1557   entity is provided in <xref target="type"/>.
[29]1563<section title="IANA Considerations" anchor="IANA.considerations">
[253]1564<section title="Message Header Registration" anchor="message.header.registration">
1566   The Message Header Registry located at <eref target=""/> should be updated
1567   with the permanent registrations below (see <xref target="RFC3864"/>):
[680]1569<?BEGININC p3-payload.iana-headers ?>
[253]1570<!--AUTOGENERATED FROM extract-header-defs.xslt, do not edit manually-->
[290]1571<texttable align="left" suppress-title="true" anchor="iana.header.registration.table">
[253]1572   <ttcol>Header Field Name</ttcol>
1573   <ttcol>Protocol</ttcol>
1574   <ttcol>Status</ttcol>
1575   <ttcol>Reference</ttcol>
1577   <c>Accept</c>
1578   <c>http</c>
1579   <c>standard</c>
1580   <c>
1581      <xref target="header.accept"/>
1582   </c>
1583   <c>Accept-Charset</c>
1584   <c>http</c>
1585   <c>standard</c>
1586   <c>
1587      <xref target="header.accept-charset"/>
1588   </c>
1589   <c>Accept-Encoding</c>
1590   <c>http</c>
1591   <c>standard</c>
1592   <c>
1593      <xref target="header.accept-encoding"/>
1594   </c>
1595   <c>Accept-Language</c>
1596   <c>http</c>
1597   <c>standard</c>
1598   <c>
1599      <xref target="header.accept-language"/>
1600   </c>
1601   <c>Content-Disposition</c>
1602   <c>http</c>
[291]1603   <c/>
[253]1604   <c>
1605      <xref target="content-disposition"/>
1606   </c>
1607   <c>Content-Encoding</c>
1608   <c>http</c>
1609   <c>standard</c>
1610   <c>
1611      <xref target="header.content-encoding"/>
1612   </c>
1613   <c>Content-Language</c>
1614   <c>http</c>
1615   <c>standard</c>
1616   <c>
1617      <xref target="header.content-language"/>
1618   </c>
1619   <c>Content-Location</c>
1620   <c>http</c>
1621   <c>standard</c>
1622   <c>
1623      <xref target="header.content-location"/>
1624   </c>
1625   <c>Content-MD5</c>
1626   <c>http</c>
1627   <c>standard</c>
1628   <c>
1629      <xref target="header.content-md5"/>
1630   </c>
1631   <c>Content-Type</c>
1632   <c>http</c>
1633   <c>standard</c>
1634   <c>
1635      <xref target="header.content-type"/>
1636   </c>
[291]1637   <c>MIME-Version</c>
1638   <c>http</c>
1639   <c/>
1640   <c>
1641      <xref target="mime-version"/>
1642   </c>
[680]1645<?ENDINC p3-payload.iana-headers ?>
[290]1647   The change controller is: "IETF ( - Internet Engineering Task Force".
[668]1651<section title="Content Coding Registry" anchor="content.coding.registration">
1653   The registration procedure for HTTP Content Codings is now defined
[670]1654   by <xref target="content.coding.registry"/> of this document.
1657   The HTTP Content Codings Registry located at <eref target=""/>
[673]1658   should be updated with the registration below:
1660<texttable align="left" suppress-title="true" anchor="iana.content.coding.registration.table">
[670]1661   <ttcol>Name</ttcol>
[668]1662   <ttcol>Description</ttcol>
1663   <ttcol>Reference</ttcol>
1664   <c>compress</c>
1665   <c>UNIX "compress" program method</c>
1666   <c>
[673]1667      &compress-coding;
[668]1668   </c>
1669   <c>deflate</c>
[806]1670   <c>"deflate" compression mechanism (<xref target="RFC1951"/>) used inside
1671   the "zlib" data format (<xref target="RFC1950"/>)
1672   </c>
[668]1673   <c>
[673]1674      &deflate-coding;
[668]1675   </c>
1676   <c>gzip</c>
1677   <c>Same as GNU zip <xref target="RFC1952"/></c>
1678   <c>
[673]1679      &gzip-coding;
[668]1680   </c>
1681   <c>identity</c>
1682   <c>No transformation</c>
1683   <c>
1684      <xref target="content.codings"/>
1685   </c>
[8]1691<section title="Security Considerations" anchor="security.considerations">
1693   This section is meant to inform application developers, information
1694   providers, and users of the security limitations in HTTP/1.1 as
1695   described by this document. The discussion does not include
1696   definitive solutions to the problems revealed, though it does make
1697   some suggestions for reducing security risks.
1700<section title="Privacy Issues Connected to Accept Headers" anchor="">
1702   Accept request-headers can reveal information about the user to all
1703   servers which are accessed. The Accept-Language header in particular
1704   can reveal information the user would consider to be of a private
1705   nature, because the understanding of particular languages is often
1706   strongly correlated to the membership of a particular ethnic group.
1707   User agents which offer the option to configure the contents of an
1708   Accept-Language header to be sent in every request are strongly
1709   encouraged to let the configuration process include a message which
1710   makes the user aware of the loss of privacy involved.
1713   An approach that limits the loss of privacy would be for a user agent
1714   to omit the sending of Accept-Language headers by default, and to ask
1715   the user whether or not to start sending Accept-Language headers to a
1716   server if it detects, by looking for any Vary response-header fields
1717   generated by the server, that such sending could improve the quality
1718   of service.
1721   Elaborate user-customized accept header fields sent in every request,
1722   in particular if these include quality values, can be used by servers
1723   as relatively reliable and long-lived user identifiers. Such user
1724   identifiers would allow content providers to do click-trail tracking,
1725   and would allow collaborating content providers to match cross-server
1726   click-trails or form submissions of individual users. Note that for
1727   many users not behind a proxy, the network address of the host
1728   running the user agent will also serve as a long-lived user
1729   identifier. In environments where proxies are used to enhance
1730   privacy, user agents ought to be conservative in offering accept
1731   header configuration options to end users. As an extreme privacy
1732   measure, proxies could filter the accept headers in relayed requests.
1733   General purpose user agents which provide a high degree of header
1734   configurability &SHOULD; warn users about the loss of privacy which can
1735   be involved.
1739<section title="Content-Disposition Issues" anchor="content-disposition.issues">
[269]1741   <xref target="RFC2183"/>, from which the often implemented Content-Disposition
[8]1742   (see <xref target="content-disposition"/>) header in HTTP is derived, has a number of very
1743   serious security considerations. Content-Disposition is not part of
1744   the HTTP standard, but since it is widely implemented, we are
[269]1745   documenting its use and risks for implementors. See <xref target="RFC2183" x:fmt="of" x:sec="5"/>
1746   for details.
1752<section title="Acknowledgments" anchor="ack">
[119]1757<references title="Normative References">
[121]1759<reference anchor="ISO-8859-1">
1760  <front>
1761    <title>
1762     Information technology -- 8-bit single-byte coded graphic character sets -- Part 1: Latin alphabet No. 1
1763    </title>
1764    <author>
1765      <organization>International Organization for Standardization</organization>
1766    </author>
1767    <date year="1998"/>
1768  </front>
1769  <seriesInfo name="ISO/IEC" value="8859-1:1998"/>
[31]1772<reference anchor="Part1">
[119]1773  <front>
1774    <title abbrev="HTTP/1.1">HTTP/1.1, part 1: URIs, Connections, and Message Parsing</title>
1775    <author initials="R." surname="Fielding" fullname="Roy T. Fielding" role="editor">
1776      <organization abbrev="Day Software">Day Software</organization>
1777      <address><email></email></address>
1778    </author>
1779    <author initials="J." surname="Gettys" fullname="Jim Gettys">
1780      <organization>One Laptop per Child</organization>
1781      <address><email></email></address>
1782    </author>
1783    <author initials="J." surname="Mogul" fullname="Jeffrey C. Mogul">
1784      <organization abbrev="HP">Hewlett-Packard Company</organization>
1785      <address><email></email></address>
1786    </author>
1787    <author initials="H." surname="Frystyk" fullname="Henrik Frystyk Nielsen">
1788      <organization abbrev="Microsoft">Microsoft Corporation</organization>
1789      <address><email></email></address>
1790    </author>
1791    <author initials="L." surname="Masinter" fullname="Larry Masinter">
1792      <organization abbrev="Adobe Systems">Adobe Systems, Incorporated</organization>
1793      <address><email></email></address>
1794    </author>
1795    <author initials="P." surname="Leach" fullname="Paul J. Leach">
1796      <organization abbrev="Microsoft">Microsoft Corporation</organization>
1797      <address><email></email></address>
1798    </author>
1799    <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
1800      <organization abbrev="W3C/MIT">World Wide Web Consortium</organization>
1801      <address><email></email></address>
1802    </author>
1803    <author initials="Y." surname="Lafon" fullname="Yves Lafon" role="editor">
1804      <organization abbrev="W3C">World Wide Web Consortium</organization>
1805      <address><email></email></address>
1806    </author>
1807    <author initials="J. F." surname="Reschke" fullname="Julian F. Reschke" role="editor">
1808      <organization abbrev="greenbytes">greenbytes GmbH</organization>
1809      <address><email></email></address>
1810    </author>
1811    <date month="&ID-MONTH;" year="&ID-YEAR;"/>
1812  </front>
1813  <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p1-messaging-&ID-VERSION;"/>
1814  <x:source href="p1-messaging.xml" basename="p1-messaging"/>
1817<reference anchor="Part2">
[119]1818  <front>
1819    <title abbrev="HTTP/1.1">HTTP/1.1, part 2: Message Semantics</title>
1820    <author initials="R." surname="Fielding" fullname="Roy T. Fielding" role="editor">
1821      <organization abbrev="Day Software">Day Software</organization>
1822      <address><email></email></address>
1823    </author>
1824    <author initials="J." surname="Gettys" fullname="Jim Gettys">
1825      <organization>One Laptop per Child</organization>
1826      <address><email></email></address>
1827    </author>
1828    <author initials="J." surname="Mogul" fullname="Jeffrey C. Mogul">
1829      <organization abbrev="HP">Hewlett-Packard Company</organization>
1830      <address><email></email></address>
1831    </author>
1832    <author initials="H." surname="Frystyk" fullname="Henrik Frystyk Nielsen">
1833      <organization abbrev="Microsoft">Microsoft Corporation</organization>
1834      <address><email></email></address>
1835    </author>
1836    <author initials="L." surname="Masinter" fullname="Larry Masinter">
1837      <organization abbrev="Adobe Systems">Adobe Systems, Incorporated</organization>
1838      <address><email></email></address>
1839    </author>
1840    <author initials="P." surname="Leach" fullname="Paul J. Leach">
1841      <organization abbrev="Microsoft">Microsoft Corporation</organization>
1842      <address><email></email></address>
1843    </author>
1844    <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
1845      <organization abbrev="W3C/MIT">World Wide Web Consortium</organization>
1846      <address><email></email></address>
1847    </author>
1848    <author initials="Y." surname="Lafon" fullname="Yves Lafon" role="editor">
1849      <organization abbrev="W3C">World Wide Web Consortium</organization>
1850      <address><email></email></address>
1851    </author>
1852    <author initials="J. F." surname="Reschke" fullname="Julian F. Reschke" role="editor">
1853      <organization abbrev="greenbytes">greenbytes GmbH</organization>
1854      <address><email></email></address>
1855    </author>
1856    <date month="&ID-MONTH;" year="&ID-YEAR;"/>
1857  </front>
1858  <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p2-semantics-&ID-VERSION;"/>
1859  <x:source href="p2-semantics.xml" basename="p2-semantics"/>
1862<reference anchor="Part4">
[119]1863  <front>
1864    <title abbrev="HTTP/1.1">HTTP/1.1, part 4: Conditional Requests</title>
1865    <author initials="R." surname="Fielding" fullname="Roy T. Fielding" role="editor">
1866      <organization abbrev="Day Software">Day Software</organization>
1867      <address><email></email></address>
1868    </author>
1869    <author initials="J." surname="Gettys" fullname="Jim Gettys">
1870      <organization>One Laptop per Child</organization>
1871      <address><email></email></address>
1872    </author>
1873    <author initials="J." surname="Mogul" fullname="Jeffrey C. Mogul">
1874      <organization abbrev="HP">Hewlett-Packard Company</organization>
1875      <address><email></email></address>
1876    </author>
1877    <author initials="H." surname="Frystyk" fullname="Henrik Frystyk Nielsen">
1878      <organization abbrev="Microsoft">Microsoft Corporation</organization>
1879      <address><email></email></address>
1880    </author>
1881    <author initials="L." surname="Masinter" fullname="Larry Masinter">
1882      <organization abbrev="Adobe Systems">Adobe Systems, Incorporated</organization>
1883      <address><email></email></address>
1884    </author>
1885    <author initials="P." surname="Leach" fullname="Paul J. Leach">
1886      <organization abbrev="Microsoft">Microsoft Corporation</organization>
1887      <address><email></email></address>
1888    </author>
1889    <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
1890      <organization abbrev="W3C/MIT">World Wide Web Consortium</organization>
1891      <address><email></email></address>
1892    </author>
1893    <author initials="Y." surname="Lafon" fullname="Yves Lafon" role="editor">
1894      <organization abbrev="W3C">World Wide Web Consortium</organization>
1895      <address><email></email></address>
1896    </author>
1897    <author initials="J. F." surname="Reschke" fullname="Julian F. Reschke" role="editor">
1898      <organization abbrev="greenbytes">greenbytes GmbH</organization>
1899      <address><email></email></address>
1900    </author>
1901    <date month="&ID-MONTH;" year="&ID-YEAR;"/>
1902  </front>
1903  <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p4-conditional-&ID-VERSION;"/>
1904  <x:source href="p4-conditional.xml" basename="p4-conditional"/>
1907<reference anchor="Part5">
[119]1908  <front>
1909    <title abbrev="HTTP/1.1">HTTP/1.1, part 5: Range Requests and Partial Responses</title>
1910    <author initials="R." surname="Fielding" fullname="Roy T. Fielding" role="editor">
1911      <organization abbrev="Day Software">Day Software</organization>
1912      <address><email></email></address>
1913    </author>
1914    <author initials="J." surname="Gettys" fullname="Jim Gettys">
1915      <organization>One Laptop per Child</organization>
1916      <address><email></email></address>
1917    </author>
1918    <author initials="J." surname="Mogul" fullname="Jeffrey C. Mogul">
1919      <organization abbrev="HP">Hewlett-Packard Company</organization>
1920      <address><email></email></address>
1921    </author>
1922    <author initials="H." surname="Frystyk" fullname="Henrik Frystyk Nielsen">
1923      <organization abbrev="Microsoft">Microsoft Corporation</organization>
1924      <address><email></email></address>
1925    </author>
1926    <author initials="L." surname="Masinter" fullname="Larry Masinter">
1927      <organization abbrev="Adobe Systems">Adobe Systems, Incorporated</organization>
1928      <address><email></email></address>
1929    </author>
1930    <author initials="P." surname="Leach" fullname="Paul J. Leach">
1931      <organization abbrev="Microsoft">Microsoft Corporation</organization>
1932      <address><email></email></address>
1933    </author>
1934    <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
1935      <organization abbrev="W3C/MIT">World Wide Web Consortium</organization>
1936      <address><email></email></address>
1937    </author>
1938    <author initials="Y." surname="Lafon" fullname="Yves Lafon" role="editor">
1939      <organization abbrev="W3C">World Wide Web Consortium</organization>
1940      <address><email></email></address>
1941    </author>
1942    <author initials="J. F." surname="Reschke" fullname="Julian F. Reschke" role="editor">
1943      <organization abbrev="greenbytes">greenbytes GmbH</organization>
1944      <address><email></email></address>
1945    </author>
1946    <date month="&ID-MONTH;" year="&ID-YEAR;"/>
1947  </front>
1948  <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p5-range-&ID-VERSION;"/>
1949  <x:source href="p5-range.xml" basename="p5-range"/>
1952<reference anchor="Part6">
[119]1953  <front>
1954    <title abbrev="HTTP/1.1">HTTP/1.1, part 6: Caching</title>
1955    <author initials="R." surname="Fielding" fullname="Roy T. Fielding" role="editor">
1956      <organization abbrev="Day Software">Day Software</organization>
1957      <address><email></email></address>
1958    </author>
1959    <author initials="J." surname="Gettys" fullname="Jim Gettys">
1960      <organization>One Laptop per Child</organization>
1961      <address><email></email></address>
1962    </author>
1963    <author initials="J." surname="Mogul" fullname="Jeffrey C. Mogul">
1964      <organization abbrev="HP">Hewlett-Packard Company</organization>
1965      <address><email></email></address>
1966    </author>
1967    <author initials="H." surname="Frystyk" fullname="Henrik Frystyk Nielsen">
1968      <organization abbrev="Microsoft">Microsoft Corporation</organization>
1969      <address><email></email></address>
1970    </author>
1971    <author initials="L." surname="Masinter" fullname="Larry Masinter">
1972      <organization abbrev="Adobe Systems">Adobe Systems, Incorporated</organization>
1973      <address><email></email></address>
1974    </author>
1975    <author initials="P." surname="Leach" fullname="Paul J. Leach">
1976      <organization abbrev="Microsoft">Microsoft Corporation</organization>
1977      <address><email></email></address>
1978    </author>
1979    <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
1980      <organization abbrev="W3C/MIT">World Wide Web Consortium</organization>
1981      <address><email></email></address>
1982    </author>
1983    <author initials="Y." surname="Lafon" fullname="Yves Lafon" role="editor">
1984      <organization abbrev="W3C">World Wide Web Consortium</organization>
1985      <address><email></email></address>
1986    </author>
[601]1987    <author initials="M." surname="Nottingham" fullname="Mark Nottingham" role="editor">
1988      <address><email></email></address>
1989    </author>
[119]1990    <author initials="J. F." surname="Reschke" fullname="Julian F. Reschke" role="editor">
1991      <organization abbrev="greenbytes">greenbytes GmbH</organization>
1992      <address><email></email></address>
1993    </author>
1994    <date month="&ID-MONTH;" year="&ID-YEAR;"/>
1995  </front>
1996  <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p6-cache-&ID-VERSION;"/>
1997  <x:source href="p6-cache.xml" basename="p6-cache"/>
[131]2000<reference anchor="RFC1864">
2001  <front>
2002    <title abbrev="Content-MD5 Header Field">The Content-MD5 Header Field</title>
2003    <author initials="J." surname="Myers" fullname="John G. Myers">
2004      <organization>Carnegie Mellon University</organization>
2005      <address><email></email></address>
2006    </author>
2007    <author initials="M." surname="Rose" fullname="Marshall T. Rose">
2008      <organization>Dover Beach Consulting, Inc.</organization>
2009      <address><email></email></address>
2010    </author>
2011    <date month="October" year="1995"/>
2012  </front>
2013  <seriesInfo name="RFC" value="1864"/>
[122]2016<reference anchor="RFC1950">
2017  <front>
2018    <title>ZLIB Compressed Data Format Specification version 3.3</title>
2019    <author initials="L.P." surname="Deutsch" fullname="L. Peter Deutsch">
2020      <organization>Aladdin Enterprises</organization>
2021      <address><email></email></address>
2022    </author>
[713]2023    <author initials="J-L." surname="Gailly" fullname="Jean-Loup Gailly"/>
[122]2024    <date month="May" year="1996"/>
2025  </front>
2026  <seriesInfo name="RFC" value="1950"/>
2027  <annotation>
[277]2028    RFC 1950 is an Informational RFC, thus it may be less stable than
[122]2029    this specification. On the other hand, this downward reference was
[277]2030    present since the publication of RFC 2068 in 1997 (<xref target="RFC2068"/>),
2031    therefore it is unlikely to cause problems in practice. See also
2032    <xref target="BCP97"/>.
[122]2033  </annotation>
[806]2036<reference anchor="RFC1951">
2037  <front>
2038    <title>DEFLATE Compressed Data Format Specification version 1.3</title>
2039    <author initials="P." surname="Deutsch" fullname="L. Peter Deutsch">
2040      <organization>Aladdin Enterprises</organization>
2041      <address><email></email></address>
2042    </author>
2043    <date month="May" year="1996"/>
2044  </front>
2045  <seriesInfo name="RFC" value="1951"/>
2046  <annotation>
2047    RFC 1951 is an Informational RFC, thus it may be less stable than
2048    this specification. On the other hand, this downward reference was
2049    present since the publication of RFC 2068 in 1997 (<xref target="RFC2068"/>),
2050    therefore it is unlikely to cause problems in practice. See also
2051    <xref target="BCP97"/>.
2052  </annotation>
[122]2055<reference anchor="RFC1952">
2056  <front>
2057    <title>GZIP file format specification version 4.3</title>
2058    <author initials="P." surname="Deutsch" fullname="L. Peter Deutsch">
2059      <organization>Aladdin Enterprises</organization>
2060      <address><email></email></address>
2061    </author>
2062    <author initials="J-L." surname="Gailly" fullname="Jean-Loup Gailly">
2063      <address><email></email></address>
2064    </author>
2065    <author initials="M." surname="Adler" fullname="Mark Adler">
2066      <address><email></email></address>
2067    </author>
2068    <author initials="L.P." surname="Deutsch" fullname="L. Peter Deutsch">
2069      <address><email></email></address>
2070    </author>
2071    <author initials="G." surname="Randers-Pehrson" fullname="Glenn Randers-Pehrson">
2072      <address><email></email></address>
2073    </author>
2074    <date month="May" year="1996"/>
2075  </front>
2076  <seriesInfo name="RFC" value="1952"/>
2077  <annotation>
[277]2078    RFC 1952 is an Informational RFC, thus it may be less stable than
[122]2079    this specification. On the other hand, this downward reference was
[277]2080    present since the publication of RFC 2068 in 1997 (<xref target="RFC2068"/>),
2081    therefore it is unlikely to cause problems in practice. See also
2082    <xref target="BCP97"/>.
[122]2083  </annotation>
[131]2086<reference anchor="RFC2045">
2087  <front>
2088    <title abbrev="Internet Message Bodies">Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies</title>
2089    <author initials="N." surname="Freed" fullname="Ned Freed">
2090      <organization>Innosoft International, Inc.</organization>
2091      <address><email></email></address>
2092    </author>
2093    <author initials="N.S." surname="Borenstein" fullname="Nathaniel S. Borenstein">
2094      <organization>First Virtual Holdings</organization>
2095      <address><email></email></address>
2096    </author>
2097    <date month="November" year="1996"/>
2098  </front>
2099  <seriesInfo name="RFC" value="2045"/>
2102<reference anchor="RFC2046">
2103  <front>
2104    <title abbrev="Media Types">Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types</title>
2105    <author initials="N." surname="Freed" fullname="Ned Freed">
2106      <organization>Innosoft International, Inc.</organization>
2107      <address><email></email></address>
2108    </author>
2109    <author initials="N." surname="Borenstein" fullname="Nathaniel S. Borenstein">
2110      <organization>First Virtual Holdings</organization>
2111      <address><email></email></address>
2112    </author>
2113    <date month="November" year="1996"/>
2114  </front>
2115  <seriesInfo name="RFC" value="2046"/>
[119]2118<reference anchor="RFC2119">
2119  <front>
2120    <title>Key words for use in RFCs to Indicate Requirement Levels</title>
2121    <author initials="S." surname="Bradner" fullname="Scott Bradner">
2122      <organization>Harvard University</organization>
2123      <address><email></email></address>
2124    </author>
2125    <date month="March" year="1997"/>
2126  </front>
2127  <seriesInfo name="BCP" value="14"/>
2128  <seriesInfo name="RFC" value="2119"/>
[303]2131<reference anchor='RFC4647'>
2132  <front>
2133    <title>Matching of Language Tags</title>
2134    <author initials='A.' surname='Phillips' fullname='Addison Phillips' role="editor">
2135      <organization>Yahoo! Inc.</organization>
2136      <address><email></email></address>
2137    </author>
2138    <author initials='M.' surname='Davis' fullname='Mark Davis' role="editor">
2139      <organization>Google</organization>
2140      <address><email></email></address>
2141    </author>
2142    <date year='2006' month='September' />
2143  </front>
2144  <seriesInfo name='BCP' value='47' />
2145  <seriesInfo name='RFC' value='4647' />
[425]2148<reference anchor="RFC5234">
2149  <front>
2150    <title abbrev="ABNF for Syntax Specifications">Augmented BNF for Syntax Specifications: ABNF</title>
2151    <author initials="D." surname="Crocker" fullname="Dave Crocker" role="editor">
2152      <organization>Brandenburg InternetWorking</organization>
2153      <address>
[728]2154        <email></email>
2155      </address> 
[425]2156    </author>
2157    <author initials="P." surname="Overell" fullname="Paul Overell">
2158      <organization>THUS plc.</organization>
2159      <address>
[728]2160        <email></email>
2161      </address>
[425]2162    </author>
2163    <date month="January" year="2008"/>
2164  </front>
2165  <seriesInfo name="STD" value="68"/>
2166  <seriesInfo name="RFC" value="5234"/>
[690]2169<reference anchor='RFC5646'>
[613]2170  <front>
2171    <title>Tags for Identifying Languages</title>
2172    <author initials='A.' surname='Phillips' fullname='Addison Phillips' role='editor'>
2173      <organization>Lab126</organization>
2174      <address><email></email></address>
2175    </author>
2176    <author initials='M.' surname='Davis' fullname='Mark Davis' role='editor'>
2177      <organization>Google</organization>
2178      <address><email></email></address>
2179    </author>
[690]2180    <date month='September' year='2009' />
[613]2181  </front>
[690]2182  <seriesInfo name='BCP' value='47' />
2183  <seriesInfo name='RFC' value='5646' />
2188<references title="Informative References">
[129]2190<reference anchor="RFC1945">
2191  <front>
2192    <title abbrev="HTTP/1.0">Hypertext Transfer Protocol -- HTTP/1.0</title>
2193    <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
2194      <organization>MIT, Laboratory for Computer Science</organization>
2195      <address><email></email></address>
2196    </author>
2197    <author initials="R.T." surname="Fielding" fullname="Roy T. Fielding">
2198      <organization>University of California, Irvine, Department of Information and Computer Science</organization>
2199      <address><email></email></address>
2200    </author>
2201    <author initials="H.F." surname="Nielsen" fullname="Henrik Frystyk Nielsen">
2202      <organization>W3 Consortium, MIT Laboratory for Computer Science</organization>
2203      <address><email></email></address>
2204    </author>
2205    <date month="May" year="1996"/>
2206  </front>
2207  <seriesInfo name="RFC" value="1945"/>
2210<reference anchor="RFC2049">
2211  <front>
2212    <title abbrev="MIME Conformance">Multipurpose Internet Mail Extensions (MIME) Part Five: Conformance Criteria and Examples</title>
2213    <author initials="N." surname="Freed" fullname="Ned Freed">
2214      <organization>Innosoft International, Inc.</organization>
2215      <address><email></email></address>
2216    </author>
2217    <author initials="N.S." surname="Borenstein" fullname="Nathaniel S. Borenstein">
2218      <organization>First Virtual Holdings</organization>
2219      <address><email></email></address>
2220    </author>
2221    <date month="November" year="1996"/>
2222  </front>
2223  <seriesInfo name="RFC" value="2049"/>
[133]2226<reference anchor="RFC2068">
2227  <front>
2228    <title abbrev="HTTP/1.1">Hypertext Transfer Protocol -- HTTP/1.1</title>
2229    <author initials="R." surname="Fielding" fullname="Roy T. Fielding">
2230      <organization>University of California, Irvine, Department of Information and Computer Science</organization>
2231      <address><email></email></address>
2232    </author>
2233    <author initials="J." surname="Gettys" fullname="Jim Gettys">
2234      <organization>MIT Laboratory for Computer Science</organization>
2235      <address><email></email></address>
2236    </author>
2237    <author initials="J." surname="Mogul" fullname="Jeffrey C. Mogul">
2238      <organization>Digital Equipment Corporation, Western Research Laboratory</organization>
2239      <address><email></email></address>
2240    </author>
2241    <author initials="H." surname="Nielsen" fullname="Henrik Frystyk Nielsen">
2242      <organization>MIT Laboratory for Computer Science</organization>
2243      <address><email></email></address>
2244    </author>
2245    <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
2246      <organization>MIT Laboratory for Computer Science</organization>
2247      <address><email></email></address>
2248    </author>
2249    <date month="January" year="1997"/>
2250  </front>
2251  <seriesInfo name="RFC" value="2068"/>
[129]2254<reference anchor="RFC2076">
2255  <front>
2256    <title abbrev="Internet Message Headers">Common Internet Message Headers</title>
2257    <author initials="J." surname="Palme" fullname="Jacob Palme">
2258      <organization>Stockholm University/KTH</organization>
2259      <address><email></email></address>
2260    </author>
2261    <date month="February" year="1997"/>
2262  </front>
2263  <seriesInfo name="RFC" value="2076"/>
2266<reference anchor="RFC2183">
2267  <front>
2268    <title abbrev="Content-Disposition">Communicating Presentation Information in Internet Messages: The Content-Disposition Header Field</title>
2269    <author initials="R." surname="Troost" fullname="Rens Troost">
2270      <organization>New Century Systems</organization>
2271      <address><email></email></address>
2272    </author>
2273    <author initials="S." surname="Dorner" fullname="Steve Dorner">
2274      <organization>QUALCOMM Incorporated</organization>
2275      <address><email></email></address>
2276    </author>
2277    <author initials="K." surname="Moore" fullname="Keith Moore">
2278      <organization>Department of Computer Science</organization>
2279      <address><email></email></address>
2280    </author>
2281    <date month="August" year="1997"/>
2282  </front>
2283  <seriesInfo name="RFC" value="2183"/>
2286<reference anchor="RFC2277">
2287  <front>
2288    <title abbrev="Charset Policy">IETF Policy on Character Sets and Languages</title>
2289    <author initials="H.T." surname="Alvestrand" fullname="Harald Tveit Alvestrand">
2290      <organization>UNINETT</organization>
2291      <address><email></email></address>
2292    </author>
2293    <date month="January" year="1998"/>
2294  </front>
2295  <seriesInfo name="BCP" value="18"/>
2296  <seriesInfo name="RFC" value="2277"/>
[745]2299<reference anchor='RFC2295'>
2300  <front>
2301    <title abbrev='HTTP Content Negotiation'>Transparent Content Negotiation in HTTP</title>
2302    <author initials='K.' surname='Holtman' fullname='Koen Holtman'>
2303      <organization>Technische Universiteit Eindhoven</organization>
2304      <address>
2305        <email></email>
2306      </address>
2307    </author>
2308    <author initials='A.H.' surname='Mutz' fullname='Andrew H. Mutz'>
2309      <organization>Hewlett-Packard Company</organization>
2310      <address>
2311        <email></email>
2312      </address>
2313    </author>
2314    <date year='1998' month='March'/>
2315  </front>
2316  <seriesInfo name='RFC' value='2295'/>
[129]2319<reference anchor="RFC2388">
2320  <front>
2321    <title abbrev="multipart/form-data">Returning Values from Forms:  multipart/form-data</title>
2322    <author initials="L." surname="Masinter" fullname="Larry Masinter">
2323      <organization>Xerox Palo Alto Research Center</organization>
2324      <address><email></email></address>
2325    </author>
2326    <date year="1998" month="August"/>
2327  </front>
2328  <seriesInfo name="RFC" value="2388"/>
2331<reference anchor="RFC2557">
2332  <front>
2333    <title abbrev="MIME Encapsulation of Aggregate Documents">MIME Encapsulation of Aggregate Documents, such as HTML (MHTML)</title>
2334    <author initials="F." surname="Palme" fullname="Jacob Palme">
2335      <organization>Stockholm University and KTH</organization>
2336      <address><email></email></address>
2337    </author>
2338    <author initials="A." surname="Hopmann" fullname="Alex Hopmann">
2339      <organization>Microsoft Corporation</organization>
2340      <address><email></email></address>
2341    </author>
2342    <author initials="N." surname="Shelness" fullname="Nick Shelness">
2343      <organization>Lotus Development Corporation</organization>
2344      <address><email></email></address>
2345    </author>
2346    <author initials="E." surname="Stefferud" fullname="Einar Stefferud">
2347      <address><email></email></address>
2348    </author>
2349    <date year="1999" month="March"/>
2350  </front>
2351  <seriesInfo name="RFC" value="2557"/>
[119]2354<reference anchor="RFC2616">
2355  <front>
2356    <title>Hypertext Transfer Protocol -- HTTP/1.1</title>
2357    <author initials="R." surname="Fielding" fullname="R. Fielding">
2358      <organization>University of California, Irvine</organization>
2359      <address><email></email></address>
2360    </author>
2361    <author initials="J." surname="Gettys" fullname="J. Gettys">
2362      <organization>W3C</organization>
2363      <address><email></email></address>
2364    </author>
2365    <author initials="J." surname="Mogul" fullname="J. Mogul">
2366      <organization>Compaq Computer Corporation</organization>
2367      <address><email></email></address>
2368    </author>
2369    <author initials="H." surname="Frystyk" fullname="H. Frystyk">
2370      <organization>MIT Laboratory for Computer Science</organization>
2371      <address><email></email></address>
2372    </author>
2373    <author initials="L." surname="Masinter" fullname="L. Masinter">
2374      <organization>Xerox Corporation</organization>
2375      <address><email></email></address>
2376    </author>
2377    <author initials="P." surname="Leach" fullname="P. Leach">
2378      <organization>Microsoft Corporation</organization>
2379      <address><email></email></address>
2380    </author>
2381    <author initials="T." surname="Berners-Lee" fullname="T. Berners-Lee">
2382      <organization>W3C</organization>
2383      <address><email></email></address>
2384    </author>
2385    <date month="June" year="1999"/>
2386  </front>
2387  <seriesInfo name="RFC" value="2616"/>
[129]2390<reference anchor="RFC3629">
2391  <front>
2392    <title>UTF-8, a transformation format of ISO 10646</title>
2393    <author initials="F." surname="Yergeau" fullname="F. Yergeau">
2394      <organization>Alis Technologies</organization>
2395      <address><email></email></address>
2396    </author>
2397    <date month="November" year="2003"/>
2398  </front>
2399  <seriesInfo name="RFC" value="3629"/>
2400  <seriesInfo name="STD" value="63"/>
[253]2403<reference anchor='RFC3864'>
2404  <front>
2405    <title>Registration Procedures for Message Header Fields</title>
2406    <author initials='G.' surname='Klyne' fullname='G. Klyne'>
2407      <organization>Nine by Nine</organization>
2408      <address><email></email></address>
2409    </author>
2410    <author initials='M.' surname='Nottingham' fullname='M. Nottingham'>
2411      <organization>BEA Systems</organization>
2412      <address><email></email></address>
2413    </author>
2414    <author initials='J.' surname='Mogul' fullname='J. Mogul'>
2415      <organization>HP Labs</organization>
2416      <address><email></email></address>
2417    </author>
2418    <date year='2004' month='September' />
2419  </front>
2420  <seriesInfo name='BCP' value='90' />
2421  <seriesInfo name='RFC' value='3864' />
[200]2424<reference anchor="RFC4288">
2425  <front>
2426    <title>Media Type Specifications and Registration Procedures</title>
2427    <author initials="N." surname="Freed" fullname="N. Freed">
2428      <organization>Sun Microsystems</organization>
2429      <address>
2430        <email></email>
2431      </address>
2432    </author>
2433    <author initials="J." surname="Klensin" fullname="J. Klensin">
2434      <address>
2435        <email></email>
2436      </address>
2437    </author>
2438    <date year="2005" month="December"/>
2439  </front>
2440  <seriesInfo name="BCP" value="13"/>
2441  <seriesInfo name="RFC" value="4288"/>
[670]2444<reference anchor='RFC5226'>
2445  <front>
2446    <title>Guidelines for Writing an IANA Considerations Section in RFCs</title>
2447    <author initials='T.' surname='Narten' fullname='T. Narten'>
2448      <organization>IBM</organization>
2449      <address><email></email></address>
2450    </author>
2451    <author initials='H.' surname='Alvestrand' fullname='H. Alvestrand'>
2452      <organization>Google</organization>
2453      <address><email></email></address>
2454    </author>
2455    <date year='2008' month='May' />
2456  </front>
2457  <seriesInfo name='BCP' value='26' />
2458  <seriesInfo name='RFC' value='5226' />
[327]2461<reference anchor="RFC5322">
2462  <front>
2463    <title>Internet Message Format</title>
2464    <author initials="P." surname="Resnick" fullname="P. Resnick">
2465      <organization>Qualcomm Incorporated</organization>
2466    </author>
2467    <date year="2008" month="October"/>
2468  </front>
2469  <seriesInfo name="RFC" value="5322"/>
[277]2472<reference anchor='BCP97'>
2473  <front>
2474    <title>Handling Normative References to Standards-Track Documents</title>
2475    <author initials='J.' surname='Klensin' fullname='J. Klensin'>
2476      <address>
2477        <email></email>
2478      </address>
2479    </author>
2480    <author initials='S.' surname='Hartman' fullname='S. Hartman'>
2481      <organization>MIT</organization>
2482      <address>
2483        <email></email>
2484      </address>
2485    </author>
2486    <date year='2007' month='June' />
2487  </front>
2488  <seriesInfo name='BCP' value='97' />
2489  <seriesInfo name='RFC' value='4897' />
[8]2495<section title="Differences Between HTTP Entities and RFC 2045 Entities" anchor="differences.between.http.entities.and.rfc.2045.entities">
[327]2497   HTTP/1.1 uses many of the constructs defined for Internet Mail (<xref target="RFC5322"/>) and the Multipurpose Internet Mail Extensions (MIME <xref target="RFC2045"/>) to
[8]2498   allow entities to be transmitted in an open variety of
2499   representations and with extensible mechanisms. However, RFC 2045
2500   discusses mail, and HTTP has a few features that are different from
2501   those described in RFC 2045. These differences were carefully chosen
2502   to optimize performance over binary connections, to allow greater
2503   freedom in the use of new media types, to make date comparisons
2504   easier, and to acknowledge the practice of some early HTTP servers
2505   and clients.
2508   This appendix describes specific areas where HTTP differs from RFC
2509   2045. Proxies and gateways to strict MIME environments &SHOULD; be
2510   aware of these differences and provide the appropriate conversions
2511   where necessary. Proxies and gateways from MIME environments to HTTP
2512   also need to be aware of the differences because some conversions
2513   might be required.
[8]2516<section title="MIME-Version" anchor="mime-version">
[291]2517  <iref primary="true" item="MIME-Version header" x:for-anchor=""/>
2518  <iref primary="true" item="Headers" subitem="MIME-Version" x:for-anchor=""/>
[229]2519  <x:anchor-alias value="MIME-Version"/>
[357]2520  <x:anchor-alias value="MIME-Version-v"/>
2522   HTTP is not a MIME-compliant protocol. However, HTTP/1.1 messages &MAY;
2523   include a single MIME-Version general-header field to indicate what
2524   version of the MIME protocol was used to construct the message. Use
2525   of the MIME-Version header field indicates that the message is in
[115]2526   full compliance with the MIME protocol (as defined in <xref target="RFC2045"/>).
[8]2527   Proxies/gateways are responsible for ensuring full compliance (where
2528   possible) when exporting HTTP messages to strict MIME environments.
[357]2530<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="MIME-Version"/><iref primary="true" item="Grammar" subitem="MIME-Version-v"/>
[366]2531  <x:ref>MIME-Version</x:ref>   = "MIME-Version" ":" <x:ref>OWS</x:ref> <x:ref>MIME-Version-v</x:ref>
[357]2532  <x:ref>MIME-Version-v</x:ref> = 1*<x:ref>DIGIT</x:ref> "." 1*<x:ref>DIGIT</x:ref>
2535   MIME version "1.0" is the default for use in HTTP/1.1. However,
2536   HTTP/1.1 message parsing and semantics are defined by this document
2537   and not the MIME specification.
2541<section title="Conversion to Canonical Form" anchor="">
[97]2543   <xref target="RFC2045"/> requires that an Internet mail entity be converted to
[115]2544   canonical form prior to being transferred, as described in <xref target="RFC2049" x:fmt="of" x:sec="4"/>.
[97]2545   <xref target="canonicalization.and.text.defaults"/> of this document describes the forms
[8]2546   allowed for subtypes of the "text" media type when transmitted over
[97]2547   HTTP. <xref target="RFC2046"/> requires that content with a type of "text" represent
[8]2548   line breaks as CRLF and forbids the use of CR or LF outside of line
2549   break sequences. HTTP allows CRLF, bare CR, and bare LF to indicate a
2550   line break within text content when a message is transmitted over
2551   HTTP.
2554   Where it is possible, a proxy or gateway from HTTP to a strict MIME
2555   environment &SHOULD; translate all line breaks within the text media
2556   types described in <xref target="canonicalization.and.text.defaults"/> of this document to the RFC 2049
2557   canonical form of CRLF. Note, however, that this might be complicated
2558   by the presence of a Content-Encoding and by the fact that HTTP
2559   allows the use of some character sets which do not use octets 13 and
2560   10 to represent CR and LF, as is the case for some multi-byte
2561   character sets.
2564   Implementors should note that conversion will break any cryptographic
2565   checksums applied to the original content unless the original content
2566   is already in canonical form. Therefore, the canonical form is
2567   recommended for any content that uses such checksums in HTTP.
2572<section title="Conversion of Date Formats" anchor="">
2574   HTTP/1.1 uses a restricted set of date formats (&full-date;) to
2575   simplify the process of date comparison. Proxies and gateways from
2576   other protocols &SHOULD; ensure that any Date header field present in a
2577   message conforms to one of the HTTP/1.1 formats and rewrite the date
2578   if necessary.
[8]2582<section title="Introduction of Content-Encoding" anchor="introduction.of.content-encoding">
2584   RFC 2045 does not include any concept equivalent to HTTP/1.1's
2585   Content-Encoding header field. Since this acts as a modifier on the
2586   media type, proxies and gateways from HTTP to MIME-compliant
2587   protocols &MUST; either change the value of the Content-Type header
2588   field or decode the entity-body before forwarding the message. (Some
2589   experimental applications of Content-Type for Internet mail have used
2590   a media-type parameter of ";conversions=&lt;content-coding&gt;" to perform
2591   a function equivalent to Content-Encoding. However, this parameter is
2592   not part of RFC 2045).
2596<section title="No Content-Transfer-Encoding" anchor="no.content-transfer-encoding">
[85]2598   HTTP does not use the Content-Transfer-Encoding field of RFC
[8]2599   2045. Proxies and gateways from MIME-compliant protocols to HTTP &MUST;
[85]2600   remove any Content-Transfer-Encoding
[8]2601   prior to delivering the response message to an HTTP client.
2604   Proxies and gateways from HTTP to MIME-compliant protocols are
2605   responsible for ensuring that the message is in the correct format
2606   and encoding for safe transport on that protocol, where "safe
2607   transport" is defined by the limitations of the protocol being used.
2608   Such a proxy or gateway &SHOULD; label the data with an appropriate
2609   Content-Transfer-Encoding if doing so will improve the likelihood of
2610   safe transport over the destination protocol.
2614<section title="Introduction of Transfer-Encoding" anchor="introduction.of.transfer-encoding">
[29]2616   HTTP/1.1 introduces the Transfer-Encoding header field (&header-transfer-encoding;).
[8]2617   Proxies/gateways &MUST; remove any transfer-coding prior to
2618   forwarding a message via a MIME-compliant protocol.
2622<section title="MHTML and Line Length Limitations" anchor="mhtml.line.length">
[129]2624   HTTP implementations which share code with MHTML <xref target="RFC2557"/> implementations
[8]2625   need to be aware of MIME line length limitations. Since HTTP does not
2626   have this limitation, HTTP does not fold long lines. MHTML messages
2627   being transported by HTTP follow all conventions of MHTML, including
2628   line length limitations and folding, canonicalization, etc., since
2629   HTTP transports all message-bodies as payload (see <xref target="multipart.types"/>) and
2630   does not interpret the content or any MIME header lines that might be
2631   contained therein.
2636<section title="Additional Features" anchor="additional.features">
[97]2638   <xref target="RFC1945"/> and <xref target="RFC2068"/> document protocol elements used by some
[8]2639   existing HTTP implementations, but not consistently and correctly
2640   across most HTTP/1.1 applications. Implementors are advised to be
2641   aware of these features, but cannot rely upon their presence in, or
2642   interoperability with, other HTTP/1.1 applications. Some of these
2643   describe proposed experimental features, and some describe features
2644   that experimental deployment found lacking that are now addressed in
2645   the base HTTP/1.1 specification.
2648   A number of other headers, such as Content-Disposition and Title,
[97]2649   from SMTP and MIME are also often implemented (see <xref target="RFC2076"/>).
2652<section title="Content-Disposition" anchor="content-disposition">
2653<iref item="Headers" subitem="Content-Disposition" primary="true" x:for-anchor=""/>
2654<iref item="Content-Disposition header" primary="true" x:for-anchor=""/>
[229]2655  <x:anchor-alias value="content-disposition"/>
[357]2656  <x:anchor-alias value="content-disposition-v"/>
[229]2657  <x:anchor-alias value="disposition-type"/>
2658  <x:anchor-alias value="disposition-parm"/>
2659  <x:anchor-alias value="disp-extension-parm"/>
2660  <x:anchor-alias value="disp-extension-token"/>
2661  <x:anchor-alias value="filename-parm"/>
[697]2663   The "Content-Disposition" response-header field has been proposed as a
[8]2664   means for the origin server to suggest a default filename if the user
2665   requests that the content is saved to a file. This usage is derived
[269]2666   from the definition of Content-Disposition in <xref target="RFC2183"/>.
[357]2668<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="content-disposition"/><iref primary="true" item="Grammar" subitem="content-disposition-v"/><iref primary="true" item="Grammar" subitem="disposition-type"/><iref primary="true" item="Grammar" subitem="disposition-parm"/><iref primary="true" item="Grammar" subitem="filename-parm"/><iref primary="true" item="Grammar" subitem="disp-extension-token"/><iref primary="true" item="Grammar" subitem="disp-extension-parm"/>
[366]2669  <x:ref>content-disposition</x:ref> = "Content-Disposition" ":" <x:ref>OWS</x:ref>
[357]2670                        <x:ref>content-disposition-v</x:ref>
[376]2671  <x:ref>content-disposition-v</x:ref> = <x:ref>disposition-type</x:ref>
2672                          *( <x:ref>OWS</x:ref> ";" <x:ref>OWS</x:ref> <x:ref>disposition-parm</x:ref> )
[334]2673  <x:ref>disposition-type</x:ref> = "attachment" / <x:ref>disp-extension-token</x:ref>
2674  <x:ref>disposition-parm</x:ref> = <x:ref>filename-parm</x:ref> / <x:ref>disp-extension-parm</x:ref>
[229]2675  <x:ref>filename-parm</x:ref> = "filename" "=" <x:ref>quoted-string</x:ref>
2676  <x:ref>disp-extension-token</x:ref> = <x:ref>token</x:ref>
[334]2677  <x:ref>disp-extension-parm</x:ref> = <x:ref>token</x:ref> "=" ( <x:ref>token</x:ref> / <x:ref>quoted-string</x:ref> )
2680   An example is
2682<figure><artwork type="example">
[458]2683  Content-Disposition: attachment; filename="fname.ext"
2686   The receiving user agent &SHOULD-NOT;  respect any directory path
2687   information present in the filename-parm parameter, which is the only
2688   parameter believed to apply to HTTP implementations at this time. The
2689   filename &SHOULD; be treated as a terminal component only.
2692   If this header is used in a response with the application/octet-stream
2693   content-type, the implied suggestion is that the user agent
[746]2694   should not display the response, but directly enter a "save response
2695   as..." dialog.
2698   See <xref target="content-disposition.issues"/> for Content-Disposition security issues.
[99]2703<section title="Compatibility with Previous Versions" anchor="compatibility">
[8]2704<section title="Changes from RFC 2068" anchor="changes.from.rfc.2068">
[138]2706   Transfer-coding and message lengths all interact in ways that
2707   required fixing exactly when chunked encoding is used (to allow for
2708   transfer encoding that may not be self delimiting); it was important
2709   to straighten out exactly how message lengths are computed.
2710   (<xref target="entity.length"/>, see also <xref target="Part1"/>,
2711   <xref target="Part5"/> and <xref target="Part6"/>).
[29]2714   Charset wildcarding is introduced to avoid explosion of character set
2715   names in accept headers. (<xref target="header.accept-charset"/>)
2718   Content-Base was deleted from the specification: it was not
2719   implemented widely, and there is no simple, safe way to introduce it
2720   without a robust extension mechanism. In addition, it is used in a
[129]2721   similar, but not identical fashion in MHTML <xref target="RFC2557"/>.
2724   A content-coding of "identity" was introduced, to solve problems
2725   discovered in caching. (<xref target="content.codings"/>)
2728   The Alternates<iref item="Alternates header" primary="true"/><iref item="Headers" subitem="Alternate" primary="true"/>, Content-Version<iref item="Content-Version header" primary="true"/><iref item="Headers" subitem="Content-Version" primary="true"/>, Derived-From<iref item="Derived-From header" primary="true"/><iref item="Headers" subitem="Derived-From" primary="true"/>, Link<iref item="Link header" primary="true"/><iref item="Headers" subitem="Link" primary="true"/>, URI<iref item="URI header" primary="true"/><iref item="Headers" subitem="URI" primary="true"/>, Public<iref item="Public header" primary="true"/><iref item="Headers" subitem="Public" primary="true"/> and
2729   Content-Base<iref item="Content-Base header" primary="true"/><iref item="Headers" subitem="Content-Base" primary="true"/> header fields were defined in previous versions of this
[268]2730   specification, but not commonly implemented. See <xref target="RFC2068" x:fmt="of" x:sec="19.6.2"/>.
2734<section title="Changes from RFC 2616" anchor="changes.from.rfc.2616">
2736  Clarify contexts that charset is used in.
2737  (<xref target="character.sets"/>)
[712]2740  Remove base URI setting semantics for Content-Location due to poor
[714]2741  implementation support, which was caused by too many broken servers emitting
2742  bogus Content-Location headers, and also the potentially undesirable effect
2743  of potentially breaking relative links in content-negotiated resources.
[712]2744  (<xref target="header.content-location"/>)
[104]2747  Remove reference to non-existant identity transfer-coding value tokens.
2748  (<xref target="no.content-transfer-encoding"/>)
[680]2754<?BEGININC p3-payload.abnf-appendix ?>
[427]2755<section xmlns:x="" title="Collected ABNF" anchor="collected.abnf">
2757<artwork type="abnf" name="p3-payload.parsed-abnf">
2758<x:ref>Accept</x:ref> = "Accept:" OWS Accept-v
2759<x:ref>Accept-Charset</x:ref> = "Accept-Charset:" OWS Accept-Charset-v
2760<x:ref>Accept-Charset-v</x:ref> = *( "," OWS ) ( charset / "*" ) [ OWS ";" OWS "q="
[425]2761 qvalue ] *( OWS "," [ OWS ( charset / "*" ) [ OWS ";" OWS "q="
2762 qvalue ] ] )
[427]2763<x:ref>Accept-Encoding</x:ref> = "Accept-Encoding:" OWS Accept-Encoding-v
2764<x:ref>Accept-Encoding-v</x:ref> = [ ( "," / ( codings [ OWS ";" OWS "q=" qvalue ] )
[425]2765 ) *( OWS "," [ OWS codings [ OWS ";" OWS "q=" qvalue ] ] ) ]
[427]2766<x:ref>Accept-Language</x:ref> = "Accept-Language:" OWS Accept-Language-v
2767<x:ref>Accept-Language-v</x:ref> = *( "," OWS ) language-range [ OWS ";" OWS "q="
[425]2768 qvalue ] *( OWS "," [ OWS language-range [ OWS ";" OWS "q=" qvalue ]
2769 ] )
[427]2770<x:ref>Accept-v</x:ref> = [ ( "," / ( media-range [ accept-params ] ) ) *( OWS "," [
[425]2771 OWS media-range [ accept-params ] ] ) ]
[427]2773<x:ref>Content-Encoding</x:ref> = "Content-Encoding:" OWS Content-Encoding-v
2774<x:ref>Content-Encoding-v</x:ref> = *( "," OWS ) content-coding *( OWS "," [ OWS
[425]2775 content-coding ] )
[427]2776<x:ref>Content-Language</x:ref> = "Content-Language:" OWS Content-Language-v
2777<x:ref>Content-Language-v</x:ref> = *( "," OWS ) language-tag *( OWS "," [ OWS
[425]2778 language-tag ] )
[678]2779<x:ref>Content-Length</x:ref> = &lt;Content-Length, defined in [Part1], Section 9.2&gt;
[427]2780<x:ref>Content-Location</x:ref> = "Content-Location:" OWS Content-Location-v
2781<x:ref>Content-Location-v</x:ref> = absolute-URI / partial-URI
2782<x:ref>Content-MD5</x:ref> = "Content-MD5:" OWS Content-MD5-v
2783<x:ref>Content-MD5-v</x:ref> = &lt;base64 of 128 bit MD5 digest as per [RFC1864]&gt;
2784<x:ref>Content-Range</x:ref> = &lt;Content-Range, defined in [Part5], Section 5.2&gt;
2785<x:ref>Content-Type</x:ref> = "Content-Type:" OWS Content-Type-v
2786<x:ref>Content-Type-v</x:ref> = media-type
[538]2788<x:ref>Expires</x:ref> = &lt;Expires, defined in [Part6], Section 3.3&gt;
2790<x:ref>Last-Modified</x:ref> = &lt;Last-Modified, defined in [Part4], Section 6.6&gt;
2792<x:ref>MIME-Version</x:ref> = "MIME-Version:" OWS MIME-Version-v
2793<x:ref>MIME-Version-v</x:ref> = 1*DIGIT "." 1*DIGIT
2795<x:ref>OWS</x:ref> = &lt;OWS, defined in [Part1], Section 1.2.2&gt;
[648]2797<x:ref>absolute-URI</x:ref> = &lt;absolute-URI, defined in [Part1], Section 2.6&gt;
[427]2798<x:ref>accept-ext</x:ref> = OWS ";" OWS token [ "=" ( token / quoted-string ) ]
2799<x:ref>accept-params</x:ref> = OWS ";" OWS "q=" qvalue *accept-ext
2800<x:ref>attribute</x:ref> = token
2802<x:ref>charset</x:ref> = token
2803<x:ref>codings</x:ref> = ( content-coding / "*" )
2804<x:ref>content-coding</x:ref> = token
2805<x:ref>content-disposition</x:ref> = "Content-Disposition:" OWS
[425]2806 content-disposition-v
[427]2807<x:ref>content-disposition-v</x:ref> = disposition-type *( OWS ";" OWS
[425]2808 disposition-parm )
[427]2810<x:ref>disp-extension-parm</x:ref> = token "=" ( token / quoted-string )
2811<x:ref>disp-extension-token</x:ref> = token
2812<x:ref>disposition-parm</x:ref> = filename-parm / disp-extension-parm
2813<x:ref>disposition-type</x:ref> = "attachment" / disp-extension-token
2815<x:ref>entity-body</x:ref> = *OCTET
2816<x:ref>entity-header</x:ref> = Content-Encoding / Content-Language / Content-Length
[425]2817 / Content-Location / Content-MD5 / Content-Range / Content-Type /
2818 Expires / Last-Modified / extension-header
[647]2819<x:ref>extension-header</x:ref> = header-field
2821<x:ref>filename-parm</x:ref> = "filename=" quoted-string
[678]2823<x:ref>header-field</x:ref> = &lt;header-field, defined in [Part1], Section 3.2&gt;
[427]2825<x:ref>language-range</x:ref> = &lt;language-range, defined in [RFC4647], Section 2.1&gt;
[690]2826<x:ref>language-tag</x:ref> = &lt;Language-Tag, defined in [RFC5646], Section 2.1&gt;
2828<x:ref>media-range</x:ref> = ( "*/*" / ( type "/*" ) / ( type "/" subtype ) ) *( OWS
[425]2829 ";" OWS parameter )
[427]2830<x:ref>media-type</x:ref> = type "/" subtype *( OWS ";" OWS parameter )
2832<x:ref>parameter</x:ref> = attribute "=" value
[648]2833<x:ref>partial-URI</x:ref> = &lt;partial-URI, defined in [Part1], Section 2.6&gt;
2835<x:ref>quoted-string</x:ref> = &lt;quoted-string, defined in [Part1], Section 1.2.2&gt;
[678]2836<x:ref>qvalue</x:ref> = &lt;qvalue, defined in [Part1], Section 6.4&gt;
2838<x:ref>subtype</x:ref> = token
2840<x:ref>token</x:ref> = &lt;token, defined in [Part1], Section 1.2.2&gt;
2841<x:ref>type</x:ref> = token
2843<x:ref>value</x:ref> = token / quoted-string
[532]2846<figure><preamble>ABNF diagnostics:</preamble><artwork type="inline">
2847; Accept defined but not used
[425]2848; Accept-Charset defined but not used
2849; Accept-Encoding defined but not used
2850; Accept-Language defined but not used
2851; MIME-Version defined but not used
2852; content-disposition defined but not used
2853; entity-body defined but not used
2854; entity-header defined but not used
[680]2856<?ENDINC p3-payload.abnf-appendix ?>
[252]2858<section title="Change Log (to be removed by RFC Editor before publication)" anchor="change.log">
2860<section title="Since RFC2616">
2862  Extracted relevant partitions from <xref target="RFC2616"/>.
2866<section title="Since draft-ietf-httpbis-p3-payload-00">
[116]2868  Closed issues:
2869  <list style="symbols">
2870    <t>
[324]2871      <eref target=""/>:
[116]2872      "Media Type Registrations"
2873      (<eref target=""/>)
2874    </t>
2875    <t>
[324]2876      <eref target=""/>:
[116]2877      "Clarification regarding quoting of charset values"
2878      (<eref target=""/>)
2879    </t>
2880    <t>
[324]2881      <eref target=""/>:
[116]2882      "Remove 'identity' token references"
2883      (<eref target=""/>)
2884    </t>
2885    <t>
[324]2886      <eref target=""/>:
[126]2887      "Accept-Encoding BNF"
2888    </t>
2889    <t>
[324]2890      <eref target=""/>:
[152]2891      "Normative and Informative references"
2892    </t>
2893    <t>
[324]2894      <eref target=""/>:
[116]2895      "RFC1700 references"
2896    </t>
[122]2897    <t>
[324]2898      <eref target=""/>:
[200]2899      "Updating to RFC4288"
2900    </t>
2901    <t>
[324]2902      <eref target=""/>:
[129]2903      "Informative references"
2904    </t>
2905    <t>
[324]2906      <eref target=""/>:
[123]2907      "ISO-8859-1 Reference"
2908    </t>
2909    <t>
[324]2910      <eref target=""/>:
[122]2911      "Encoding References Normative"
2912    </t>
[131]2913    <t>
[324]2914      <eref target=""/>:
[131]2915      "Normative up-to-date references"
2916    </t>
[116]2917  </list>
[170]2921<section title="Since draft-ietf-httpbis-p3-payload-01">
[324]2923  Ongoing work on ABNF conversion (<eref target=""/>):
[205]2924  <list style="symbols">
2925    <t>
2926      Add explicit references to BNF syntax and rules imported from other parts of the specification.
2927    </t>
2928  </list>
[252]2932<section title="Since draft-ietf-httpbis-p3-payload-02" anchor="changes.since.02">
[232]2934  Closed issues:
2935  <list style="symbols">
2936    <t>
[324]2937      <eref target=""/>:
[251]2938      "Quoting Charsets"
2939    </t>
2940    <t>
[324]2941      <eref target=""/>:
[232]2942      "Classification for Allow header"
2943    </t>
[248]2944    <t>
[324]2945      <eref target=""/>:
[248]2946      "missing default for qvalue in description of Accept-Encoding"
2947    </t>
[232]2948  </list>
[324]2951  Ongoing work on IANA Message Header Registration (<eref target=""/>):
[253]2952  <list style="symbols">
2953    <t>
2954      Reference RFC 3984, and update header registrations for headers defined
2955      in this document.
2956    </t>
2957  </list>
[267]2961<section title="Since draft-ietf-httpbis-p3-payload-03" anchor="changes.since.03">
[269]2963  Closed issues:
2964  <list style="symbols">
2965    <t>
[297]2966      <eref target=""/>:
2967      "Quoting Charsets"
2968    </t>
2969    <t>
[303]2970      <eref target=""/>:
2971      "language tag matching (Accept-Language) vs RFC4647"
2972    </t>
2973    <t>
[277]2974      <eref target=""/>:
[269]2975      "RFC 1806 has been replaced by RFC2183"
2976    </t>
2977  </list>
2980  Other changes:
2981  <list style="symbols">
2982    <t>
2983      <eref target=""/>:
2984      "Encoding References Normative" -- rephrase the annotation and reference
2985      <xref target="BCP97"/>.
2986    </t>
2987  </list>
[269]2989 </section>
[323]2991<section title="Since draft-ietf-httpbis-p3-payload-04" anchor="changes.since.04">
[327]2993  Closed issues:
2994  <list style="symbols">
2995    <t>
2996      <eref target=""/>:
2997      "RFC 2822 is updated by RFC 5322"
2998    </t>
2999  </list>
3002  Ongoing work on ABNF conversion (<eref target=""/>):
3003  <list style="symbols">
3004    <t>
3005      Use "/" instead of "|" for alternatives.
3006    </t>
[357]3007    <t>
3008      Introduce new ABNF rules for "bad" whitespace ("BWS"), optional
3009      whitespace ("OWS") and required whitespace ("RWS").
3010    </t>
3011    <t>
3012      Rewrite ABNFs to spell out whitespace rules, factor out
3013      header value format definitions.
3014    </t>
[334]3015  </list>
[382]3019<section title="Since draft-ietf-httpbis-p3-payload-05" anchor="changes.since.05">
[385]3021  Closed issues:
3022  <list style="symbols">
3023    <t>
3024      <eref target=""/>:
3025      "Join "Differences Between HTTP Entities and RFC 2045 Entities"?"
3026    </t>
3027  </list>
[543]3030  Final work on ABNF conversion (<eref target=""/>):
[421]3031  <list style="symbols">
3032    <t>
[424]3033      Add appendix containing collected and expanded ABNF, reorganize ABNF introduction.
[421]3034    </t>
3035  </list>
3038  Other changes:
3039  <list style="symbols">
3040    <t>
3041      Move definition of quality values into Part 1.
3042    </t>
3043  </list>
[547]3047<section title="Since draft-ietf-httpbis-p3-payload-06" anchor="changes.since.06">
[577]3049  Closed issues:
3050  <list style="symbols">
3051    <t>
3052      <eref target=""/>:
3053      "Content-Location isn't special"
3054    </t>
[592]3055    <t>
3056      <eref target=""/>:
3057      "Content Sniffing"
3058    </t>
[577]3059  </list>
[604]3063<section title="Since draft-ietf-httpbis-p3-payload-07" anchor="changes.since.07">
[613]3065  Closed issues:
3066  <list style="symbols">
3067    <t>
[670]3068      <eref target=""/>:
[613]3069      "Updated reference for language tags"
3070    </t>
[663]3071    <t>
[716]3072      <eref target=""/>:
3073      "Clarify rules for determining what entities a response carries"
3074    </t>
3075    <t>
[712]3076      <eref target=""/>:
3077      "Content-Location base-setting problems"
3078    </t>
3079    <t>
[663]3080      <eref target=""/>:
3081      "Content Sniffing"
3082    </t>
[670]3083    <t>
3084      <eref target=""/>:
3085      "pick IANA policy (RFC5226) for Transfer Coding / Content Coding"
3086    </t>
[673]3087    <t>
3088      <eref target=""/>:
3089      "move definitions of gzip/deflate/compress to part 1"
3090    </t>
[613]3091  </list>
3094  Partly resolved issues:
3095  <list style="symbols">
3096    <t>
3097      <eref target=""/>:
3098      "update IANA requirements wrt Transfer-Coding values" (add the
3099      IANA Considerations subsection)
3100    </t>
[668]3101    <t>
3102      <eref target=""/>:
3103      "update IANA requirements wrt Content-Coding values" (add the
3104      IANA Considerations subsection)
3105    </t>
[667]3106  </list>
[720]3110<section title="Since draft-ietf-httpbis-p3-payload-08" anchor="changes.since.08">
[724]3112  Closed issues:
3113  <list style="symbols">
3114    <t>
[745]3115      <eref target=""/>:
3116      "Content Negotiation for media types"
3117    </t>
3118    <t>
[724]3119      <eref target=""/>:
3120      "Accept-Language: which RFC4647 filtering?"
3121    </t>
3122  </list>
[773]3126<section title="Since draft-ietf-httpbis-p3-payload-09" anchor="changes.since.09">
3128  None yet.
Note: See TracBrowser for help on using the repository browser.