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

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

prepare publication of -13

  • Property svn:eol-style set to native
File size: 128.9 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">
[1145]15  <!ENTITY ID-MONTH "March">
[1099]16  <!ENTITY ID-YEAR "2011">
[1101]17  <!ENTITY mdash "&#8212;">
[424]18  <!ENTITY notation                 "<xref target='Part1' x:rel='#notation' xmlns:x=''/>">
[205]19  <!ENTITY notation-abnf            "<xref target='Part1' x:rel='#notation.abnf' xmlns:x=''/>">
20  <!ENTITY basic-rules              "<xref target='Part1' x:rel='#basic.rules' xmlns:x=''/>">
[115]21  <!ENTITY caching-neg-resp         "<xref target='Part6' x:rel='#caching.negotiated.responses' xmlns:x=''/>">
[31]22  <!ENTITY header-transfer-encoding "<xref target='Part1' x:rel='#header.transfer-encoding' xmlns:x=''/>">
23  <!ENTITY header-content-length    "<xref target='Part1' x:rel='#header.content-length' xmlns:x=''/>">
24  <!ENTITY header-content-range     "<xref target='Part5' x:rel='#header.content-range' xmlns:x=''/>">
25  <!ENTITY header-expires           "<xref target='Part6' x:rel='#header.expires' xmlns:x=''/>">
26  <!ENTITY header-last-modified     "<xref target='Part4' x:rel='#header.last-modified' xmlns:x=''/>">
27  <!ENTITY header-user-agent        "<xref target='Part2' x:rel='#header.user-agent' xmlns:x=''/>">
[115]28  <!ENTITY header-vary              "<xref target='Part6' x:rel='#header.vary' xmlns:x=''/>">
[31]29  <!ENTITY message-body             "<xref target='Part1' x:rel='#message.body' xmlns:x=''/>">
30  <!ENTITY multipart-byteranges     "<xref target='Part5' x:rel='' xmlns:x=''/>">
[580]31  <!ENTITY full-date                "<xref target='Part1' x:rel='' xmlns:x=''/>">
[457]32  <!ENTITY qvalue                   "<xref target='Part1' x:rel='#quality.values' xmlns:x=''/>">
[374]33  <!ENTITY uri                      "<xref target='Part1' x:rel='#uri' xmlns:x=''/>">
[823]34  <!ENTITY effective-request-uri    "<xref target='Part1' x:rel='#effective.request.uri' xmlns:x=''/>">
[808]35  <!ENTITY compression-codings      "<xref target='Part1' x:rel='#compression.codings' xmlns:x=''/>">
36  <!ENTITY transfer-codings         "<xref target='Part1' x:rel='#transfer.codings' xmlns:x=''/>">
[673]37  <!ENTITY compress-coding          "<xref target='Part1' x:rel='#compress.coding' xmlns:x=''/>">
38  <!ENTITY deflate-coding           "<xref target='Part1' x:rel='#deflate.coding' xmlns:x=''/>">
39  <!ENTITY gzip-coding              "<xref target='Part1' x:rel='#gzip.coding' xmlns:x=''/>">
[716]40  <!ENTITY response-representation  "<xref target='Part2' x:rel='#identifying.response.associated.with.representation' xmlns:x=''/>">
42<?rfc toc="yes" ?>
[29]43<?rfc symrefs="yes" ?>
44<?rfc sortrefs="yes" ?>
[8]45<?rfc compact="yes"?>
46<?rfc subcompact="no" ?>
47<?rfc linkmailto="no" ?>
48<?rfc editing="no" ?>
[203]49<?rfc comments="yes"?>
50<?rfc inline="yes"?>
[799]51<?rfc rfcedstyle="yes"?>
[8]52<?rfc-ext allow-markup-in-artwork="yes" ?>
53<?rfc-ext include-references-in-index="yes" ?>
[308]54<rfc obsoletes="2616" category="std" x:maturity-level="draft"
[446]55     ipr="pre5378Trust200902" docName="draft-ietf-httpbis-p3-payload-&ID-VERSION;"
[153]56     xmlns:x=''>
[120]59  <title abbrev="HTTP/1.1, Part 3">HTTP/1.1, part 3: Message Payload and Content Negotiation</title>
[29]61  <author initials="R." surname="Fielding" fullname="Roy T. Fielding" role="editor">
[1106]62    <organization abbrev="Adobe">Adobe Systems Incorporated</organization>
[8]63    <address>
64      <postal>
[1106]65        <street>345 Park Ave</street>
66        <city>San Jose</city>
[8]67        <region>CA</region>
[1106]68        <code>95110</code>
[29]69        <country>USA</country>
[8]70      </postal>
[29]71      <email></email>
72      <uri></uri>
[8]73    </address>
74  </author>
[29]76  <author initials="J." surname="Gettys" fullname="Jim Gettys">
[844]77    <organization abbrev="Alcatel-Lucent">Alcatel-Lucent Bell Labs</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>
[844]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">
[1106]121    <organization abbrev="Adobe">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
[848]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>
[1180]220    The changes in this draft are summarized in <xref target="changes.since.13"/>.
[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
[908]230   might influence content selection, and the various selection algorithms
[161]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.
[980]236   A future draft will reorganize the sections to better reflect the content.
[161]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
[856]255      servicing a request. The representation in any response
[660]256      can be negotiated (including error responses).
257    </t>
258  </list>
[96]262<section title="Requirements" anchor="intro.requirements">
264   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
265   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
266   document are to be interpreted as described in <xref target="RFC2119"/>.
269   An implementation is not compliant if it fails to satisfy one or more
[847]270   of the "MUST" or "REQUIRED" level requirements for the protocols it
271   implements. An implementation that satisfies all the "MUST" or "REQUIRED"
272   level and all the "SHOULD" level requirements for its protocols is said
273   to be "unconditionally compliant"; one that satisfies all the "MUST"
274   level requirements but not all the "SHOULD" level requirements for its
275   protocols is said to be "conditionally compliant".
[424]279<section title="Syntax Notation" anchor="notation">
[425]280  <x:anchor-alias value="ALPHA"/>
281  <x:anchor-alias value="CR"/>
282  <x:anchor-alias value="DIGIT"/>
283  <x:anchor-alias value="LF"/>
284  <x:anchor-alias value="OCTET"/>
285  <x:anchor-alias value="VCHAR"/>
286  <x:anchor-alias value="WSP"/>
[543]288  This specification uses the ABNF syntax defined in &notation; (which
289  extends the syntax defined in <xref target="RFC5234"/> with a list rule).
290  <xref target="collected.abnf"/> shows the collected ABNF, with the list
291  rule expanded.
[425]294  The following core rules are included by
295  reference, as defined in <xref target="RFC5234" x:fmt="," x:sec="B.1"/>:
296  ALPHA (letters), CR (carriage return), CRLF (CR LF), CTL (controls),
297  DIGIT (decimal 0-9), DQUOTE (double quote),
298  HEXDIG (hexadecimal 0-9/A-F/a-f), LF (line feed),
299  OCTET (any 8-bit sequence of data), SP (space),
300  VCHAR (any visible USASCII character),
301  and WSP (whitespace).
304<section title="Core Rules" anchor="core.rules">
[229]305  <x:anchor-alias value="token"/>
[810]306  <x:anchor-alias value="word"/>
[357]307  <x:anchor-alias value="OWS"/>
[424]309  The core rules below are defined in &basic-rules;:
311<figure><artwork type="abnf2616">
[229]312  <x:ref>token</x:ref>          = &lt;token, defined in &basic-rules;&gt;
[810]313  <x:ref>word</x:ref>           = &lt;word, defined in &basic-rules;&gt;
[357]314  <x:ref>OWS</x:ref>            = &lt;OWS, defined in &basic-rules;&gt;
318<section title="ABNF Rules defined in other Parts of the Specification" anchor="abnf.dependencies">
[374]319  <x:anchor-alias value="absolute-URI"/>
[391]320  <x:anchor-alias value="partial-URI"/>
[457]321  <x:anchor-alias value="qvalue"/>
[206]323  The ABNF rules below are defined in other parts:
[207]325<figure><!--Part1--><artwork type="abnf2616">
[374]326  <x:ref>absolute-URI</x:ref>   = &lt;absolute-URI, defined in &uri;&gt;
[391]327  <x:ref>partial-URI</x:ref>    = &lt;partial-URI, defined in &uri;&gt;
[457]328  <x:ref>qvalue</x:ref>         = &lt;qvalue, defined in &qvalue;&gt;
[8]336<section title="Protocol Parameters" anchor="protocol.parameters">
[1176]338<section title="Character Encodings (charset)" anchor="character.sets">
[1176]340   HTTP uses charset names to indicate the character encoding of a
341   textual representation.
[229]343<t anchor="rule.charset">
344  <x:anchor-alias value="charset"/>
[1176]345   A character encoding is identified by a case-insensitive token. The
[8]346   complete set of tokens is defined by the IANA Character Set registry
[91]347   (<eref target=""/>).
349<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="charset"/>
[229]350  <x:ref>charset</x:ref> = <x:ref>token</x:ref>
353   Although HTTP allows an arbitrary token to be used as a charset
354   value, any token that has a predefined value within the IANA
[1176]355   Character Set registry &MUST; represent the character encoding defined
[8]356   by that registry. Applications &SHOULD; limit their use of character
[1176]357   encodings to those defined within the IANA registry.
[81]360   HTTP uses charset in two contexts: within an Accept-Charset request
[994]361   header field (in which the charset value is an unquoted token) and as the
362   value of a parameter in a Content-Type header field (within a request or
[81]363   response), in which case the parameter value of the charset parameter
[908]364   can be quoted.
[969]367   Implementors need to be aware of IETF character set requirements <xref target="RFC3629"/>
[8]368   <xref target="RFC2277"/>.
371<section title="Missing Charset" anchor="missing.charset">
[994]373   Some HTTP/1.0 software has interpreted a Content-Type header field without
[879]374   charset parameter incorrectly to mean "recipient should guess".
[211]375   Senders wishing to defeat this behavior &MAY; include a charset
376   parameter even when the charset is ISO-8859-1 (<xref target="ISO-8859-1"/>) and &SHOULD; do so when
377   it is known that it will not confuse the recipient.
380   Unfortunately, some older HTTP/1.0 clients did not deal properly with
381   an explicit charset parameter. HTTP/1.1 recipients &MUST; respect the
382   charset label provided by the sender; and those user agents that have
383   a provision to "guess" a charset &MUST; use the charset from the
384   content-type field if they support that charset, rather than the
385   recipient's preference, when initially displaying a document. See
386   <xref target="canonicalization.and.text.defaults"/>.
391<section title="Content Codings" anchor="content.codings">
[229]392  <x:anchor-alias value="content-coding"/>
394   Content coding values indicate an encoding transformation that has
[866]395   been or can be applied to a representation. Content codings are primarily
396   used to allow a representation to be compressed or otherwise usefully
[8]397   transformed without losing the identity of its underlying media type
[866]398   and without loss of information. Frequently, the representation is stored in
[8]399   coded form, transmitted directly, and only decoded by the recipient.
401<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="content-coding"/>
[229]402  <x:ref>content-coding</x:ref>   = <x:ref>token</x:ref>
405   All content-coding values are case-insensitive. HTTP/1.1 uses
406   content-coding values in the Accept-Encoding (<xref target="header.accept-encoding"/>) and
407   Content-Encoding (<xref target="header.content-encoding"/>) header fields. Although the value
408   describes the content-coding, what is more important is that it
409   indicates what decoding mechanism will be required to remove the
410   encoding.
[673]413   compress<iref item="compress (Coding Format)"/><iref item="Coding Format" subitem="compress"/>
414  <list>
415    <t>
416      See &compress-coding;.
417    </t>
418  </list>
[673]421   deflate<iref item="deflate (Coding Format)"/><iref item="Coding Format" subitem="deflate"/>
[8]422  <list>
423    <t>
[673]424      See &deflate-coding;.
[8]425    </t>
426  </list>
[673]429   gzip<iref item="gzip (Coding Format)"/><iref item="Coding Format" subitem="gzip"/>
430  <list>
431    <t>
432      See &gzip-coding;.
433    </t>
434  </list>
[673]437   identity<iref item="identity (Coding Format)"/><iref item="Coding Format" subitem="identity"/>
[8]438  <list><t>
439        The default (identity) encoding; the use of no transformation
440        whatsoever. This content-coding is used only in the Accept-Encoding
[994]441        header field, and &SHOULD-NOT;  be used in the Content-Encoding
442        header field.
[8]443  </t></list>
446<section title="Content Coding Registry" anchor="content.coding.registry">
[670]448   The HTTP Content Coding Registry defines the name space for the content
449   coding names.
452   Registrations &MUST; include the following fields:
453   <list style="symbols">
454     <t>Name</t>
455     <t>Description</t>
456     <t>Pointer to specification text</t>
457   </list>
[808]460   Names of content codings &MUST-NOT; overlap with names of transfer codings
461   (&transfer-codings;), unless the encoding transformation is identical (as it
462   is the case for the compression codings defined in
463   &compression-codings;).
[942]466   Values to be added to this name space require a specification
467   (see "Specification Required" in
[670]468   <xref target="RFC5226" x:fmt="of" x:sec="4.1"/>), and &MUST;
[8]469   conform to the purpose of content coding defined in this section.
472   The registry itself is maintained at
473   <eref target=""/>.
[8]479<section title="Media Types" anchor="media.types">
[229]480  <x:anchor-alias value="media-type"/>
481  <x:anchor-alias value="type"/>
482  <x:anchor-alias value="subtype"/>
[152]484   HTTP uses Internet Media Types <xref target="RFC2046"/> in the Content-Type (<xref target="header.content-type"/>)
[8]485   and Accept (<xref target="header.accept"/>) header fields in order to provide
486   open and extensible data typing and type negotiation.
488<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]489  <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> )
490  <x:ref>type</x:ref>       = <x:ref>token</x:ref>
491  <x:ref>subtype</x:ref>    = <x:ref>token</x:ref>
[229]493<t anchor="rule.parameter">
494  <x:anchor-alias value="attribute"/>
495  <x:anchor-alias value="parameter"/>
496  <x:anchor-alias value="value"/>
[1153]497   The type/subtype &MAY; be followed by parameters in the form of
498   attribute/value pairs.
[29]500<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]501  <x:ref>parameter</x:ref>      = <x:ref>attribute</x:ref> "=" <x:ref>value</x:ref>
502  <x:ref>attribute</x:ref>      = <x:ref>token</x:ref>
[810]503  <x:ref>value</x:ref>          = <x:ref>word</x:ref>
506   The type, subtype, and parameter attribute names are case-insensitive.
[370]507   Parameter values might or might not be case-sensitive, depending on the
508   semantics of the parameter name.  The presence or absence of a parameter might
[8]509   be significant to the processing of a media-type, depending on its
510   definition within the media type registry.
[908]513   A parameter value that matches the <x:ref>token</x:ref> production can be
[297]514   transmitted as either a token or within a quoted-string. The quoted and
515   unquoted values are equivalent.
[8]518   Note that some older HTTP applications do not recognize media type
519   parameters. When sending data to older HTTP applications,
520   implementations &SHOULD; only use media type parameters when they are
521   required by that type/subtype definition.
524   Media-type values are registered with the Internet Assigned Number
[91]525   Authority (IANA). The media type registration process is
[115]526   outlined in <xref target="RFC4288"/>. Use of non-registered media types is
[8]527   discouraged.
530<section title="Canonicalization and Text Defaults" anchor="canonicalization.and.text.defaults">
[874]532   Internet media types are registered with a canonical form. A
533   representation transferred via HTTP messages &MUST; be in the
[8]534   appropriate canonical form prior to its transmission except for
535   "text" types, as defined in the next paragraph.
538   When in canonical form, media subtypes of the "text" type use CRLF as
539   the text line break. HTTP relaxes this requirement and allows the
540   transport of text media with plain CR or LF alone representing a line
[874]541   break when it is done consistently for an entire representation. HTTP
542   applications &MUST; accept CRLF, bare CR, and bare LF as indicating
543   a line break in text media received via HTTP. In
544   addition, if the text is in a character encoding that does not
[8]545   use octets 13 and 10 for CR and LF respectively, as is the case for
[874]546   some multi-byte character encodings, HTTP allows the use of whatever octet
547   sequences are defined by that character encoding to represent the
[8]548   equivalent of CR and LF for line breaks. This flexibility regarding
[874]549   line breaks applies only to text media in the payload body; a bare CR
[8]550   or LF &MUST-NOT; be substituted for CRLF within any of the HTTP control
551   structures (such as header fields and multipart boundaries).
[874]554   If a representation is encoded with a content-coding, the underlying
[8]555   data &MUST; be in a form defined above prior to being encoded.
[211]558   The "charset" parameter is used with some media types to define the
[874]559   character encoding (<xref target="character.sets"/>) of the data. When no explicit charset
[211]560   parameter is provided by the sender, media subtypes of the "text"
561   type are defined to have a default charset value of "ISO-8859-1" when
[874]562   received via HTTP. Data in character encodings other than "ISO-8859-1" or
[211]563   its subsets &MUST; be labeled with an appropriate charset value. See
564   <xref target="missing.charset"/> for compatibility problems.
568<section title="Multipart Types" anchor="multipart.types">
[1101]570   MIME provides for a number of "multipart" types &mdash; encapsulations of
[874]571   one or more representations within a single message-body. All multipart
[97]572   types share a common syntax, as defined in <xref target="RFC2046" x:sec="5.1.1" x:fmt="of"/>,
573   and &MUST; include a boundary parameter as part of the media type
[8]574   value. The message body is itself a protocol element and &MUST;
575   therefore use only CRLF to represent line breaks between body-parts.
578   In general, HTTP treats a multipart message-body no differently than
[852]579   any other media type: strictly as payload.  HTTP does not use the
580   multipart boundary as an indicator of message-body length.
[97]581   <!-- jre: re-insert removed text pointing to caching? -->
[852]582   In all other respects, an HTTP user agent &SHOULD; follow the same or similar
[8]583   behavior as a MIME user agent would upon receipt of a multipart type.
584   The MIME header fields within each body-part of a multipart message-body
585   do not have any significance to HTTP beyond that defined by
586   their MIME semantics.
589   If an application receives an unrecognized multipart subtype, the
590   application &MUST; treat it as being equivalent to "multipart/mixed".
593  <t>
594    <x:h>Note:</x:h> The "multipart/form-data" type has been specifically defined
595    for carrying form data suitable for processing via the POST
596    request method, as described in <xref target="RFC2388"/>.
597  </t>
602<section title="Language Tags" anchor="language.tags">
[229]603  <x:anchor-alias value="language-tag"/>
[690]605   A language tag, as defined in <xref target="RFC5646"/>, identifies a
[613]606   natural language spoken, written, or otherwise conveyed by human beings for
607   communication of information to other human beings. Computer languages are
608   explicitly excluded. HTTP uses language tags within the Accept-Language and
609   Content-Language fields.
[613]612   In summary, a language tag is composed of one or more parts: A primary
613   language subtag followed by a possibly empty series of subtags:
[613]615<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="language-tag"/>
[690]616  <x:ref>language-tag</x:ref> = &lt;Language-Tag, defined in <xref target="RFC5646" x:sec="2.1"/>&gt;
619   White space is not allowed within the tag and all tags are case-insensitive.
[613]620   The name space of language subtags is administered by the IANA (see
621   <eref target=""/>).
624  <preamble>Example tags include:</preamble>
625<artwork type="example">
626  en, en-US, es-419, az-Arab, x-pig-latin, man-Nkoo-GN
[690]630   See <xref target="RFC5646"/> for further information.
[965]635<section title="Payload" anchor="payload">
[965]637   HTTP messages &MAY; transfer a payload if not otherwise restricted by
638   the request method or response status code.  The payload consists of
639   metadata, in the form of header fields, and data, in the form of the
640   sequence of octets in the message-body after any transfer-coding has
641   been decoded.
[965]643<iref item="payload"/>
645   A "<x:dfn>payload</x:dfn>" in HTTP is always a partial or complete
646   representation of some resource.  We use separate terms for payload
647   and representation because some messages contain only the associated
648   representation's header fields (e.g., responses to HEAD) or only some
649   part(s) of the representation (e.g., the 206 status code).
651<section title="Payload Header Fields" anchor="payload.header.fields">
652  <x:anchor-alias value="payload-header"/>
[965]654   HTTP header fields that specifically define the payload, rather than the
655   associated representation, are referred to as "payload header fields".
656   The following payload header fields are defined by HTTP/1.1:
[1138]658<texttable align="left">
659  <ttcol>Header Field Name</ttcol>
660  <ttcol>Defined in...</ttcol>
662  <c>Content-Length</c> <c>&header-content-length;</c>
663  <c>Content-MD5</c> <c><xref target="header.content-md5"/></c>
664  <c>Content-Range</c> <c>&header-content-range;</c>
[874]668<section title="Payload Body" anchor="payload.body">
669  <x:anchor-alias value="payload-body"/>
[874]671   A payload body is only present in a message when a message-body is
672   present, as described in &message-body;. The payload body is obtained
[8]673   from the message-body by decoding any Transfer-Encoding that might
674   have been applied to ensure safe and proper transfer of the message.
[965]679<section title="Representation" anchor="representation">
680<iref item="representation"/>
[965]682   A "<x:dfn>representation</x:dfn>" is information in a format that can be readily
683   communicated from one party to another.  A resource representation
684   is information that reflects the state of that resource, as observed
685   at some point in the past (e.g., in a response to GET) or to be
686   desired at some point in the future (e.g., in a PUT request).
689   Most, but not all, representations transferred via HTTP are intended
690   to be a representation of the target resource (the resource identified
691   by the effective request URI).  The precise semantics of a representation
692   are determined by the type of message (request or response), the request
693   method, the response status code, and the representation metadata.
694   For example, the above semantic is true for the representation in any
695   200 (OK) response to GET and for the representation in any PUT request.
696   A 200 response to PUT, in contrast, contains either a representation
697   that describes the successful action or a representation of the target
698   resource, with the latter indicated by a Content-Location header field
699   with the same value as the effective request URI.  Likewise, response
700   messages with an error status code usually contain a representation that
701   describes the error and what next steps are suggested for resolving it.
704<section title="Representation Header Fields" anchor="representation.header.fields">
705  <x:anchor-alias value="representation-header"/>
707   Representation header fields define metadata about the representation data
708   enclosed in the message-body or, if no message-body is present, about
709   the representation that would have been transferred in a 200 response
710   to a simultaneous GET request with the same effective request URI.
713   The following header fields are defined as representation metadata:
[1138]715<texttable align="left">
716  <ttcol>Header Field Name</ttcol>
717  <ttcol>Defined in...</ttcol>
719  <c>Content-Encoding</c> <c><xref target="header.content-encoding"/></c>
720  <c>Content-Language</c> <c><xref target="header.content-language"/></c>
721  <c>Content-Location</c> <c><xref target="header.content-location"/></c>
722  <c>Content-Type</c> <c><xref target="header.content-type"/></c>
723  <c>Expires</c> <c>&header-expires;</c>
724  <c>Last-Modified</c> <c>&header-last-modified;</c>
728<section title="Representation Data" anchor="">
729  <x:anchor-alias value="representation-data"/>
731   The representation body associated with an HTTP message is
732   either provided as the payload body of the message or
733   referred to by the message semantics and the effective request
734   URI.  The representation data is in a format and encoding defined by
735   the representation metadata header fields.
738   The data type of the representation data
739   is determined via the header fields Content-Type and Content-Encoding.
[8]740   These define a two-layer, ordered encoding model:
742<figure><artwork type="example">
[965]743  representation-data := Content-Encoding( Content-Type( bits ) )
[965]746   Content-Type specifies the media type of the underlying data, which
747   defines both the data format and how that data &SHOULD; be processed
748   by the recipient (within the scope of the request method semantics).
749   Any HTTP/1.1 message containing a payload body &SHOULD; include a
750   Content-Type header field defining the media type of the associated
751   representation unless that metadata is unknown to the sender.
[831]752   If the Content-Type header field is not present, it indicates that
[965]753   the sender does not know the media type of the representation;
754   recipients &MAY; either assume that the media type is
755   "application/octet-stream" (<xref target="RFC2046" x:fmt="," x:sec="4.5.1"/>)
[592]756   or examine the content to determine its type.
[965]759   In practice, resource owners do not always properly configure their origin
760   server to provide the correct Content-Type for a given representation,
761   with the result that some clients will examine a response body's content
762   and override the specified type.
[908]763   Clients that do so risk drawing incorrect conclusions, which might expose
[965]764   additional security risks (e.g., "privilege escalation").  Furthermore,
765   it is impossible to determine the sender's intent by examining the data
766   format: many data formats match multiple media types that differ only in
767   processing semantics.  Implementers are encouraged to provide a means of
768   disabling such "content sniffing" when it is used.
[908]771   Content-Encoding is used to indicate any additional content
[8]772   codings applied to the data, usually for the purpose of data
[965]773   compression, that are a property of the representation.  If
774   Content-Encoding is not present, then there is no additional
775   encoding beyond that defined by the Content-Type.
780<section title="Content Negotiation" anchor="content.negotiation">
[745]782   HTTP responses include a representation which contains information for
783   interpretation, whether by a human user or for further processing.
784   Often, the server has different ways of representing the
785   same information; for example, in different formats, languages,
786   or using different character encodings.
[745]789   HTTP clients and their users might have different or variable
790   capabilities, characteristics or preferences which would influence
791   which representation, among those available from the server,
792   would be best for the server to deliver. For this reason, HTTP
[1101]793   provides mechanisms for "content negotiation" &mdash; a process of
[745]794   allowing selection of a representation of a given resource,
795   when more than one is available.
[745]798   This specification defines two patterns of content negotiation;
799   "server-driven", where the server selects the representation based
800   upon the client's stated preferences, and "agent-driven" negotiation,
801   where the server provides a list of representations for the client to
802   choose from, based upon their metadata. In addition,  there are
803   other patterns: some applications use an "active content" pattern,
804   where the server returns active content which runs on the client
805   and, based on client available parameters, selects additional
806   resources to invoke. "Transparent Content Negotiation" (<xref target="RFC2295"/>)
807   has also been proposed.
810   These patterns are all widely used, and have trade-offs in applicability
811   and practicality. In particular, when the number of preferences or
812   capabilities to be expressed by a client are large (such as when many
813   different formats are supported by a user-agent), server-driven
[908]814   negotiation becomes unwieldy, and might not be appropriate. Conversely,
[745]815   when the number of representations to choose from is very large,
[908]816   agent-driven negotiation might not be appropriate.
819   Note that in all cases, the supplier of representations has the
820   responsibility for determining which representations might be
821   considered to be the "same information".
824<section title="Server-driven Negotiation" anchor="server-driven.negotiation">
826   If the selection of the best representation for a response is made by
827   an algorithm located at the server, it is called server-driven
828   negotiation. Selection is based on the available representations of
[763]829   the response (the dimensions over which it can vary; e.g., language,
[8]830   content-coding, etc.) and the contents of particular header fields in
831   the request message or on other information pertaining to the request
832   (such as the network address of the client).
835   Server-driven negotiation is advantageous when the algorithm for
836   selecting from among the available representations is difficult to
837   describe to the user agent, or when the server desires to send its
838   "best guess" to the client along with the first response (hoping to
839   avoid the round-trip delay of a subsequent request if the "best
840   guess" is good enough for the user). In order to improve the server's
841   guess, the user agent &MAY; include request header fields (Accept,
842   Accept-Language, Accept-Encoding, etc.) which describe its
843   preferences for such a response.
846   Server-driven negotiation has disadvantages:
847  <list style="numbers">
848    <t>
849         It is impossible for the server to accurately determine what
850         might be "best" for any given user, since that would require
851         complete knowledge of both the capabilities of the user agent
852         and the intended use for the response (e.g., does the user want
853         to view it on screen or print it on paper?).
854    </t>
855    <t>
856         Having the user agent describe its capabilities in every
857         request can be both very inefficient (given that only a small
858         percentage of responses have multiple representations) and a
859         potential violation of the user's privacy.
860    </t>
861    <t>
862         It complicates the implementation of an origin server and the
863         algorithms for generating responses to a request.
864    </t>
865    <t>
[908]866         It might limit a public cache's ability to use the same response
[8]867         for multiple user's requests.
868    </t>
869  </list>
[1163]872   HTTP/1.1 includes the following header fields for enabling
[8]873   server-driven negotiation through description of user agent
874   capabilities and user preferences: Accept (<xref target="header.accept"/>), Accept-Charset
875   (<xref target="header.accept-charset"/>), Accept-Encoding (<xref target="header.accept-encoding"/>), Accept-Language
[745]876   (<xref target="header.accept-language"/>), and User-Agent (&header-user-agent;).
877   However, an origin server is not limited to these dimensions and &MAY; vary
[1163]878   the response based on any aspect of the request, including aspects
879   of the connection (e.g., IP address) or information within extension
880   header fields not defined by this specification.
883  <t>
884    <x:h>Note:</x:h> In practice, User-Agent based negotiation is fragile,
885    because new clients might not be recognized.
886  </t>
[115]889   The Vary header field (&header-vary;) can be used to express the parameters the
[8]890   server uses to select a representation that is subject to server-driven
[29]891   negotiation.
895<section title="Agent-driven Negotiation" anchor="agent-driven.negotiation">
897   With agent-driven negotiation, selection of the best representation
898   for a response is performed by the user agent after receiving an
899   initial response from the origin server. Selection is based on a list
900   of the available representations of the response included within the
[874]901   header fields or body of the initial response, with each
[8]902   representation identified by its own URI. Selection from among the
[908]903   representations can be performed automatically (if the user agent is
[8]904   capable of doing so) or manually by the user selecting from a
905   generated (possibly hypertext) menu.
908   Agent-driven negotiation is advantageous when the response would vary
909   over commonly-used dimensions (such as type, language, or encoding),
910   when the origin server is unable to determine a user agent's
911   capabilities from examining the request, and generally when public
912   caches are used to distribute server load and reduce network usage.
915   Agent-driven negotiation suffers from the disadvantage of needing a
916   second request to obtain the best alternate representation. This
917   second request is only efficient when caching is used. In addition,
918   this specification does not define any mechanism for supporting
919   automatic selection, though it also does not prevent any such
920   mechanism from being developed as an extension and used within
921   HTTP/1.1.
[745]924   This specification defines the 300 (Multiple Choices) and 406 (Not Acceptable)
[8]925   status codes for enabling agent-driven negotiation when the server is
926   unwilling or unable to provide a varying response using server-driven
927   negotiation.
[8]932<section title="Header Field Definitions" anchor="header.fields">
[117]934   This section defines the syntax and semantics of HTTP/1.1 header fields
935   related to the payload of messages.
[8]938<section title="Accept" anchor="header.accept">
[1120]939  <iref primary="true" item="Accept header field" x:for-anchor=""/>
940  <iref primary="true" item="Header Fields" subitem="Accept" x:for-anchor=""/>
[229]941  <x:anchor-alias value="Accept"/>
[357]942  <x:anchor-alias value="Accept-v"/>
[370]943  <x:anchor-alias value="accept-ext"/>
[229]944  <x:anchor-alias value="accept-params"/>
945  <x:anchor-alias value="media-range"/>
[1163]947   The "Accept" header field can be used by user agents to specify
[994]948   response media types that are acceptable. Accept header fields can be used to
[698]949   indicate that the request is specifically limited to a small set of desired
950   types, as in the case of a request for an in-line image.
[370]952<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]953  <x:ref>Accept</x:ref>   = "Accept" ":" <x:ref>OWS</x:ref> <x:ref>Accept-v</x:ref>
[357]954  <x:ref>Accept-v</x:ref> = #( <x:ref>media-range</x:ref> [ <x:ref>accept-params</x:ref> ] )
[229]956  <x:ref>media-range</x:ref>    = ( "*/*"
[334]957                   / ( <x:ref>type</x:ref> "/" "*" )
958                   / ( <x:ref>type</x:ref> "/" <x:ref>subtype</x:ref> )
[370]959                   ) *( <x:ref>OWS</x:ref> ";" <x:ref>OWS</x:ref> <x:ref>parameter</x:ref> )
960  <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> )
[1039]961  <x:ref>accept-ext</x:ref>     = <x:ref>OWS</x:ref> ";" <x:ref>OWS</x:ref> <x:ref>token</x:ref> [ "=" <x:ref>word</x:ref> ]
964   The asterisk "*" character is used to group media types into ranges,
965   with "*/*" indicating all media types and "type/*" indicating all
966   subtypes of that type. The media-range &MAY; include media type
967   parameters that are applicable to that range.
970   Each media-range &MAY; be followed by one or more accept-params,
971   beginning with the "q" parameter for indicating a relative quality
972   factor. The first "q" parameter (if any) separates the media-range
973   parameter(s) from the accept-params. Quality factors allow the user
974   or user agent to indicate the relative degree of preference for that
[457]975   media-range, using the qvalue scale from 0 to 1 (&qvalue;). The
[8]976   default value is q=1.
979  <t>
980    <x:h>Note:</x:h> Use of the "q" parameter name to separate media type
981    parameters from Accept extension parameters is due to historical
982    practice. Although this prevents any media type parameter named
983    "q" from being used with a media range, such an event is believed
984    to be unlikely given the lack of any "q" parameters in the IANA
985    media type registry and the rare usage of any media type
986    parameters in Accept. Future media types are discouraged from
987    registering any parameter named "q".
988  </t>
991   The example
993<figure><artwork type="example">
[357]994  Accept: audio/*; q=0.2, audio/basic
997   &SHOULD; be interpreted as "I prefer audio/basic, but send me any audio
[879]998   type if it is the best available after an 80% mark-down in quality".
1001   If no Accept header field is present, then it is assumed that the
1002   client accepts all media types. If an Accept header field is present,
1003   and if the server cannot send a response which is acceptable
1004   according to the combined Accept field value, then the server &SHOULD;
[137]1005   send a 406 (Not Acceptable) response.
1008   A more elaborate example is
1010<figure><artwork type="example">
[357]1011  Accept: text/plain; q=0.5, text/html,
1012          text/x-dvi; q=0.8, text/x-c
1015   Verbally, this would be interpreted as "text/html and text/x-c are
1016   the preferred media types, but if they do not exist, then send the
[866]1017   text/x-dvi representation, and if that does not exist, send the text/plain
[879]1018   representation".
1021   Media ranges can be overridden by more specific media ranges or
1022   specific media types. If more than one media range applies to a given
1023   type, the most specific reference has precedence. For example,
1025<figure><artwork type="example">
[357]1026  Accept: text/*, text/html, text/html;level=1, */*
1029   have the following precedence:
[459]1030   <list style="numbers">
1031    <t>text/html;level=1</t>
1032    <t>text/html</t>
1033    <t>text/*</t>
1034    <t>*/*</t>
1035   </list>
1038   The media type quality factor associated with a given type is
1039   determined by finding the media range with the highest precedence
1040   which matches that type. For example,
1042<figure><artwork type="example">
[357]1043  Accept: text/*;q=0.3, text/html;q=0.7, text/html;level=1,
1044          text/html;level=2;q=0.4, */*;q=0.5
1047   would cause the following values to be associated:
[459]1049<texttable align="left">
1050  <ttcol>Media Type</ttcol><ttcol>Quality Value</ttcol>
1051  <c>text/html;level=1</c>    <c>1</c>
1052  <c>text/html</c>            <c>0.7</c>
1053  <c>text/plain</c>           <c>0.3</c>
1054  <c>image/jpeg</c>           <c>0.5</c>
1055  <c>text/html;level=2</c>    <c>0.4</c>
1056  <c>text/html;level=3</c>    <c>0.7</c>
1059      <x:h>Note:</x:h> A user agent might be provided with a default set of quality
1060      values for certain media ranges. However, unless the user agent is
1061      a closed system which cannot interact with other rendering agents,
1062      this default set ought to be configurable by the user.
1066<section title="Accept-Charset" anchor="header.accept-charset">
[1120]1067  <iref primary="true" item="Accept-Charset header field" x:for-anchor=""/>
1068  <iref primary="true" item="Header Fields" subitem="Accept-Charset" x:for-anchor=""/>
[229]1069  <x:anchor-alias value="Accept-Charset"/>
[357]1070  <x:anchor-alias value="Accept-Charset-v"/>
[1163]1072   The "Accept-Charset" header field can be used by user agents to
[1176]1073   indicate what character encodings are acceptable in a response
1074   payload. This field allows
[8]1075   clients capable of understanding more comprehensive or special-purpose
[1176]1076   character encodings to signal that capability to a server which is capable of
1077   representing documents in those character encodings.
[357]1079<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Accept-Charset"/><iref primary="true" item="Grammar" subitem="Accept-Charset-v"/>
[366]1080  <x:ref>Accept-Charset</x:ref>   = "Accept-Charset" ":" <x:ref>OWS</x:ref>
[357]1081          <x:ref>Accept-Charset-v</x:ref>
[376]1082  <x:ref>Accept-Charset-v</x:ref> = 1#( ( <x:ref>charset</x:ref> / "*" )
1083                         [ <x:ref>OWS</x:ref> ";" <x:ref>OWS</x:ref> "q=" <x:ref>qvalue</x:ref> ] )
[1176]1086   Character encoding values (a.k.a., charsets) are described in
1087   <xref target="character.sets"/>. Each charset &MAY; be given an
1088   associated quality value which represents the user's preference
1089   for that charset. The default value is q=1. An example is
1091<figure><artwork type="example">
[357]1092  Accept-Charset: iso-8859-5, unicode-1-1;q=0.8
1095   The special value "*", if present in the Accept-Charset field,
[1176]1096   matches every character encoding (including ISO-8859-1) which is not
[8]1097   mentioned elsewhere in the Accept-Charset field. If no "*" is present
[1176]1098   in an Accept-Charset field, then all character encodings not explicitly
[8]1099   mentioned get a quality value of 0, except for ISO-8859-1, which gets
1100   a quality value of 1 if not explicitly mentioned.
[994]1103   If no Accept-Charset header field is present, the default is that any
[1176]1104   character encoding is acceptable. If an Accept-Charset header field is present,
[8]1105   and if the server cannot send a response which is acceptable
[994]1106   according to the Accept-Charset header field, then the server &SHOULD; send
[137]1107   an error response with the 406 (Not Acceptable) status code, though
[8]1108   the sending of an unacceptable response is also allowed.
1112<section title="Accept-Encoding" anchor="header.accept-encoding">
[1120]1113  <iref primary="true" item="Accept-Encoding header field" x:for-anchor=""/>
1114  <iref primary="true" item="Header Fields" subitem="Accept-Encoding" x:for-anchor=""/>
[229]1115  <x:anchor-alias value="Accept-Encoding"/>
[357]1116  <x:anchor-alias value="Accept-Encoding-v"/>
[229]1117  <x:anchor-alias value="codings"/>
[1163]1119   The "Accept-Encoding" header field can be used by user agents to
[698]1120   indicate what response content-codings (<xref target="content.codings"/>)
1121   are acceptable in the response.
[357]1123<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]1124  <x:ref>Accept-Encoding</x:ref>    = "Accept-Encoding" ":" <x:ref>OWS</x:ref>
[357]1125                     <x:ref>Accept-Encoding-v</x:ref>
1126  <x:ref>Accept-Encoding-v</x:ref>  =
[370]1127                     #( <x:ref>codings</x:ref> [ <x:ref>OWS</x:ref> ";" <x:ref>OWS</x:ref> "q=" <x:ref>qvalue</x:ref> ] )
[357]1128  <x:ref>codings</x:ref>            = ( <x:ref>content-coding</x:ref> / "*" )
[248]1131   Each codings value &MAY; be given an associated quality value which
1132   represents the preference for that encoding. The default value is q=1.
[8]1135   Examples of its use are:
1137<figure><artwork type="example">
[357]1138  Accept-Encoding: compress, gzip
1139  Accept-Encoding:
1140  Accept-Encoding: *
1141  Accept-Encoding: compress;q=0.5, gzip;q=1.0
1142  Accept-Encoding: gzip;q=1.0, identity; q=0.5, *;q=0
1145   A server tests whether a content-coding is acceptable, according to
1146   an Accept-Encoding field, using these rules:
1147  <list style="numbers">
1148      <t>If the content-coding is one of the content-codings listed in
1149         the Accept-Encoding field, then it is acceptable, unless it is
[457]1150         accompanied by a qvalue of 0. (As defined in &qvalue;, a
[879]1151         qvalue of 0 means "not acceptable".)</t>
1153      <t>The special "*" symbol in an Accept-Encoding field matches any
1154         available content-coding not explicitly listed in the header
1155         field.</t>
1157      <t>If multiple content-codings are acceptable, then the acceptable
1158         content-coding with the highest non-zero qvalue is preferred.</t>
1160      <t>The "identity" content-coding is always acceptable, unless
1161         specifically refused because the Accept-Encoding field includes
1162         "identity;q=0", or because the field includes "*;q=0" and does
1163         not explicitly include the "identity" content-coding. If the
1164         Accept-Encoding field-value is empty, then only the "identity"
1165         encoding is acceptable.</t>
1166  </list>
1169   If an Accept-Encoding field is present in a request, and if the
1170   server cannot send a response which is acceptable according to the
[994]1171   Accept-Encoding header field, then the server &SHOULD; send an error response
[8]1172   with the 406 (Not Acceptable) status code.
1175   If no Accept-Encoding field is present in a request, the server &MAY;
1176   assume that the client will accept any content coding. In this case,
1177   if "identity" is one of the available content-codings, then the
1178   server &SHOULD; use the "identity" content-coding, unless it has
1179   additional information that a different content-coding is meaningful
1180   to the client.
1183  <t>
1184    <x:h>Note:</x:h> If the request does not include an Accept-Encoding field,
1185    and if the "identity" content-coding is unavailable, then
1186    content-codings commonly understood by HTTP/1.0 clients (i.e.,
1187    "gzip" and "compress") are preferred; some older clients
1188    improperly display messages sent with other content-codings.  The
1189    server might also make this decision based on information about
1190    the particular user-agent or client.
1191  </t>
1194  <t>
1195    <x:h>Note:</x:h> Most HTTP/1.0 applications do not recognize or obey qvalues
1196    associated with content-codings. This means that qvalues will not
1197    work and are not permitted with x-gzip or x-compress.
1198  </t>
1202<section title="Accept-Language" anchor="header.accept-language">
[1120]1203  <iref primary="true" item="Accept-Language header field" x:for-anchor=""/>
1204  <iref primary="true" item="Header Fields" subitem="Accept-Language" x:for-anchor=""/>
[229]1205  <x:anchor-alias value="Accept-Language"/>
[357]1206  <x:anchor-alias value="Accept-Language-v"/>
[229]1207  <x:anchor-alias value="language-range"/>
[1163]1209   The "Accept-Language" header field can be used by user agents to
[698]1210   indicate the set of natural languages that are preferred in the response.
1211   Language tags are defined in <xref target="language.tags"/>.
[357]1213<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]1214  <x:ref>Accept-Language</x:ref>   = "Accept-Language" ":" <x:ref>OWS</x:ref>
[357]1215                    <x:ref>Accept-Language-v</x:ref>
1216  <x:ref>Accept-Language-v</x:ref> =
[370]1217                    1#( <x:ref>language-range</x:ref> [ <x:ref>OWS</x:ref> ";" <x:ref>OWS</x:ref> "q=" <x:ref>qvalue</x:ref> ] )
[357]1218  <x:ref>language-range</x:ref>    =
[303]1219            &lt;language-range, defined in <xref target="RFC4647" x:fmt="," x:sec="2.1"/>&gt;
[303]1222   Each language-range can be given an associated quality value which
[8]1223   represents an estimate of the user's preference for the languages
1224   specified by that range. The quality value defaults to "q=1". For
1225   example,
1227<figure><artwork type="example">
[357]1228  Accept-Language: da, en-gb;q=0.8, en;q=0.7
1231   would mean: "I prefer Danish, but will accept British English and
[879]1232   other types of English".
[724]1233   (see also <xref target="RFC4647" x:sec="2.3" x:fmt="of"/>)
[724]1236   For matching, <xref target="RFC4647" x:sec="3" x:fmt="of"/> defines
1237   several matching schemes. Implementations can offer the most appropriate
1238   matching scheme for their requirements.
1241  <t>
[756]1242    <x:h>Note:</x:h> The "Basic Filtering" scheme (<xref target="RFC4647"
[724]1243    x:fmt="," x:sec="3.3.1"/>) is identical to the matching scheme that was
1244    previously defined in <xref target="RFC2616" x:fmt="of" x:sec="14.4"/>.
[563]1245  </t>
1248   It might be contrary to the privacy expectations of the user to send
[994]1249   an Accept-Language header field with the complete linguistic preferences of
[8]1250   the user in every request. For a discussion of this issue, see
[994]1251   <xref target=""/>.
1254   As intelligibility is highly dependent on the individual user, it is
1255   recommended that client applications make the choice of linguistic
1256   preference available to the user. If the choice is not made
1257   available, then the Accept-Language header field &MUST-NOT; be given in
1258   the request.
1261  <t>
1262    <x:h>Note:</x:h> When making the choice of linguistic preference available to
1263    the user, we remind implementors of  the fact that users are not
1264    familiar with the details of language matching as described above,
[969]1265    and ought to be provided appropriate guidance. As an example, users
[563]1266    might assume that on selecting "en-gb", they will be served any
1267    kind of English document if British English is not available. A
1268    user agent might suggest in such a case to add "en" to get the
1269    best matching behavior.
1270  </t>
1274<section title="Content-Encoding" anchor="header.content-encoding">
[1120]1275  <iref primary="true" item="Content-Encoding header field" x:for-anchor=""/>
1276  <iref primary="true" item="Header Fields" subitem="Content-Encoding" x:for-anchor=""/>
[229]1277  <x:anchor-alias value="Content-Encoding"/>
[357]1278  <x:anchor-alias value="Content-Encoding-v"/>
[965]1280   The "Content-Encoding" header field indicates what content-codings
[866]1281   have been applied to the representation, and thus what decoding mechanisms
[698]1282   must be applied in order to obtain the media-type referenced by the
1283   Content-Type header field. Content-Encoding is primarily used to allow a
[866]1284   representation to be compressed without losing the identity of its underlying
[698]1285   media type.
[357]1287<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Content-Encoding"/><iref primary="true" item="Grammar" subitem="Content-Encoding-v"/>
[366]1288  <x:ref>Content-Encoding</x:ref>   = "Content-Encoding" ":" <x:ref>OWS</x:ref> <x:ref>Content-Encoding-v</x:ref>
[357]1289  <x:ref>Content-Encoding-v</x:ref> = 1#<x:ref>content-coding</x:ref>
1292   Content codings are defined in <xref target="content.codings"/>. An example of its use is
1294<figure><artwork type="example">
[357]1295  Content-Encoding: gzip
[866]1298   The content-coding is a characteristic of the representation.
1299   Typically, the representation body is stored with this
[8]1300   encoding and is only decoded before rendering or analogous usage.
[1107]1301   However, a transforming proxy &MAY; modify the content-coding if the
[8]1302   new coding is known to be acceptable to the recipient, unless the
1303   "no-transform" cache-control directive is present in the message.
[866]1306   If the content-coding of a representation is not "identity", then the
1307   representation metadata &MUST; include a Content-Encoding header
1308   field (<xref target="header.content-encoding"/>)
[8]1309   that lists the non-identity content-coding(s) used.
[874]1312   If the content-coding of a representation in a request message is not
[8]1313   acceptable to the origin server, the server &SHOULD; respond with a
1314   status code of 415 (Unsupported Media Type).
[866]1317   If multiple encodings have been applied to a representation, the content
[8]1318   codings &MUST; be listed in the order in which they were applied.
1319   Additional information about the encoding parameters &MAY; be provided
[866]1320   by other header fields not defined by this specification.
1324<section title="Content-Language" anchor="header.content-language">
[1120]1325  <iref primary="true" item="Content-Language header field" x:for-anchor=""/>
1326  <iref primary="true" item="Header Fields" subitem="Content-Language" x:for-anchor=""/>
[229]1327  <x:anchor-alias value="Content-Language"/>
[357]1328  <x:anchor-alias value="Content-Language-v"/>
[965]1330   The "Content-Language" header field describes the natural
[866]1331   language(s) of the intended audience for the representation. Note that this might
[874]1332   not be equivalent to all the languages used within the representation.
[357]1334<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Content-Language"/><iref primary="true" item="Grammar" subitem="Content-Language-v"/>
[366]1335  <x:ref>Content-Language</x:ref>   = "Content-Language" ":" <x:ref>OWS</x:ref> <x:ref>Content-Language-v</x:ref>
[357]1336  <x:ref>Content-Language-v</x:ref> = 1#<x:ref>language-tag</x:ref>
1339   Language tags are defined in <xref target="language.tags"/>. The primary purpose of
1340   Content-Language is to allow a user to identify and differentiate
[866]1341   representations according to the user's own preferred language. Thus, if the
[8]1342   body content is intended only for a Danish-literate audience, the
1343   appropriate field is
1345<figure><artwork type="example">
[357]1346  Content-Language: da
1349   If no Content-Language is specified, the default is that the content
1350   is intended for all language audiences. This might mean that the
1351   sender does not consider it to be specific to any natural language,
1352   or that the sender does not know for which language it is intended.
1355   Multiple languages &MAY; be listed for content that is intended for
1356   multiple audiences. For example, a rendition of the "Treaty of
[879]1357   Waitangi", presented simultaneously in the original Maori and English
[8]1358   versions, would call for
1360<figure><artwork type="example">
[357]1361  Content-Language: mi, en
[866]1364   However, just because multiple languages are present within a representation
[8]1365   does not mean that it is intended for multiple linguistic audiences.
1366   An example would be a beginner's language primer, such as "A First
[879]1367   Lesson in Latin", which is clearly intended to be used by an
[8]1368   English-literate audience. In this case, the Content-Language would
1369   properly only include "en".
[1101]1372   Content-Language &MAY; be applied to any media type &mdash; it is not
[8]1373   limited to textual documents.
1377<section title="Content-Location" anchor="header.content-location">
[1120]1378  <iref primary="true" item="Content-Location header field" x:for-anchor=""/>
1379  <iref primary="true" item="Header Fields" subitem="Content-Location" x:for-anchor=""/>
[229]1380  <x:anchor-alias value="Content-Location"/>
[357]1381  <x:anchor-alias value="Content-Location-v"/>
[856]1383   The "Content-Location" header field supplies a URI that can be used
1384   as a specific identifier for the representation in this message.
1385   In other words, if one were to perform a GET on this URI at the time
1386   of this message's generation, then a 200 response would contain the
1387   same representation that is enclosed as payload in this message.
[357]1389<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Content-Location"/><iref primary="true" item="Grammar" subitem="Content-Location-v"/>
[366]1390  <x:ref>Content-Location</x:ref>   = "Content-Location" ":" <x:ref>OWS</x:ref>
[357]1391                    <x:ref>Content-Location-v</x:ref>
1392  <x:ref>Content-Location-v</x:ref> =
[391]1393                    <x:ref>absolute-URI</x:ref> / <x:ref>partial-URI</x:ref>
[972]1396   The Content-Location value is not a replacement for the effective
[856]1397   Request URI (&effective-request-uri;).  It is representation metadata.
1398   It has the same syntax and semantics as the header field of the same name
[858]1399   defined for MIME body parts in <xref target="RFC2557" x:fmt="of" x:sec="4"/>.
[856]1400   However, its appearance in an HTTP message has some special implications
1401   for HTTP recipients.
[856]1404   If Content-Location is included in a response message and its value
[965]1405   is the same as the effective request URI, then the response payload
[856]1406   &SHOULD; be considered the current representation of that resource.
1407   For a GET or HEAD request, this is the same as the default semantics
1408   when no Content-Location is provided by the server.  For a state-changing
[1161]1409   request like PUT or POST, it implies that the server's response contains
[856]1410   the new representation of that resource, thereby distinguishing it from
1411   representations that might only report about the action (e.g., "It worked!").
1412   This allows authoring applications to update their local copies without
1413   the need for a subsequent GET request.
[856]1416   If Content-Location is included in a response message and its value
[965]1417   differs from the effective request URI, then the origin server is
[856]1418   informing recipients that this representation has its own, presumably
1419   more specific, identifier.  For a GET or HEAD request, this is an
[965]1420   indication that the effective request URI identifies a resource that
[856]1421   is subject to content negotiation and the representation selected for
1422   this response can also be found at the identified URI.  For other
1423   methods, such a Content-Location indicates that this representation
1424   contains a report on the action's status and the same report is
1425   available (for future access with GET) at the given URI.  For
[1161]1426   example, a purchase transaction made via a POST request might
[856]1427   include a receipt document as the payload of the 200 response;
1428   the Content-Location value provides an identifier for retrieving
1429   a copy of that same receipt in the future.
1432   If Content-Location is included in a request message, then it &MAY;
1433   be interpreted by the origin server as an indication of where the
1434   user agent originally obtained the content of the enclosed
1435   representation (prior to any subsequent modification of the content
1436   by that user agent).  In other words, the user agent is providing
1437   the same representation metadata that it received with the original
1438   representation.  However, such interpretation &MUST-NOT; be used to
1439   alter the semantics of the method requested by the client.  For
1440   example, if a client makes a PUT request on a negotiated resource
1441   and the origin server accepts that PUT (without redirection), then the
1442   new set of values for that resource is expected to be consistent with
1443   the one representation supplied in that PUT; the Content-Location
1444   cannot be used as a form of reverse content selection that
1445   identifies only one of the negotiated representations to be updated.
1446   If the user agent had wanted the latter semantics, it would have applied
1447   the PUT directly to the Content-Location URI.
1450   A Content-Location field received in a request message is transitory
1451   information that &SHOULD-NOT; be saved with other representation
1452   metadata for use in later responses.  The Content-Location's value
1453   might be saved for use in other contexts, such as within source links
1454   or other metadata.
1457   A cache cannot assume that a representation with a Content-Location
[8]1458   different from the URI used to retrieve it can be used to respond to
[856]1459   later requests on that Content-Location URI.
[965]1462   If the Content-Location value is a partial URI, the partial URI is
1463   interpreted relative to the effective request URI.
1467<section title="Content-MD5" anchor="header.content-md5">
[1120]1468  <iref primary="true" item="Content-MD5 header field" x:for-anchor=""/>
1469  <iref primary="true" item="Header Fields" subitem="Content-MD5" x:for-anchor=""/>
[229]1470  <x:anchor-alias value="Content-MD5"/>
[357]1471  <x:anchor-alias value="Content-MD5-v"/>
[965]1473   The "Content-MD5" header field, as defined in <xref target="RFC1864"/>, is
[874]1474   an MD5 digest of the payload body that provides an end-to-end message
1475   integrity check (MIC) of the payload body (the message-body after any
1476   transfer-coding is decoded). Note that a MIC is good for
1477   detecting accidental modification of the payload body in transit, but is not
[699]1478   proof against malicious attacks.
[357]1480<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Content-MD5"/><iref primary="true" item="Grammar" subitem="Content-MD5-v"/>
[366]1481  <x:ref>Content-MD5</x:ref>   = "Content-MD5" ":" <x:ref>OWS</x:ref> <x:ref>Content-MD5-v</x:ref>
[357]1482  <x:ref>Content-MD5-v</x:ref> = &lt;base64 of 128 bit MD5 digest as per <xref target="RFC1864"/>&gt;
1485   The Content-MD5 header field &MAY; be generated by an origin server or
[874]1486   client to function as an integrity check of the payload body. Only
1487   origin servers or user agents &MAY; generate the Content-MD5 header field;
[1173]1488   proxies &MUST-NOT; generate it, as this would defeat its
[874]1489   value as an end-to-end integrity check. Any recipient &MAY; check that
1490   the digest value in this header field matches a corresponding digest
1491   calculated on payload body as received.
[874]1494   The MD5 digest is computed based on the content of the payload body,
1495   including any content-coding, but not including any transfer-coding
1496   applied to the message-body because such transfer-codings might be
1497   applied or removed anywhere along the request/response chain.
1498   If the message is received with a transfer-coding, that encoding &MUST;
1499   be decoded prior to checking the Content-MD5 value against the received
1500   payload.
1503   HTTP extends RFC 1864 to permit the digest to be computed for MIME
1504   composite media-types (e.g., multipart/* and message/rfc822), but
1505   this does not change how the digest is computed as defined in the
1506   preceding paragraph.
[874]1509   There are several consequences of this. The payload for composite
[8]1510   types &MAY; contain many body-parts, each with its own MIME and HTTP
[994]1511   header fields (including Content-MD5, Content-Transfer-Encoding, and
1512   Content-Encoding header fields). If a body-part has a Content-Transfer-Encoding
1513   or Content-Encoding header field, it is assumed that the content
[8]1514   of the body-part has had the encoding applied, and the body-part is
[1101]1515   included in the Content-MD5 digest as is &mdash; i.e., after the
[8]1516   application. The Transfer-Encoding header field is not allowed within
1517   body-parts.
1520   Conversion of all line breaks to CRLF &MUST-NOT; be done before
1521   computing or checking the digest: the line break convention used in
1522   the text actually transmitted &MUST; be left unaltered when computing
1523   the digest.
1526  <t>
[756]1527    <x:h>Note:</x:h> While the definition of Content-MD5 is exactly the same for
[563]1528    HTTP as in RFC 1864 for MIME entity-bodies, there are several ways
1529    in which the application of Content-MD5 to HTTP entity-bodies
1530    differs from its application to MIME entity-bodies. One is that
1531    HTTP, unlike MIME, does not use Content-Transfer-Encoding, and
1532    does use Transfer-Encoding and Content-Encoding. Another is that
1533    HTTP more frequently uses binary content types than MIME, so it is
1534    worth noting that, in such cases, the byte order used to compute
1535    the digest is the transmission byte order defined for the type.
1536    Lastly, HTTP allows transmission of text types with any of several
1537    line break conventions and not just the canonical form using CRLF.
1538  </t>
1542<section title="Content-Type" anchor="header.content-type">
[1120]1543  <iref primary="true" item="Content-Type header field" x:for-anchor=""/>
1544  <iref primary="true" item="Header Fields" subitem="Content-Type" x:for-anchor=""/>
[229]1545  <x:anchor-alias value="Content-Type"/>
[357]1546  <x:anchor-alias value="Content-Type-v"/>
[965]1548   The "Content-Type" header field indicates the media type of the
[874]1549   representation. In the case of responses to the HEAD method, the media type is
[698]1550   that which would have been sent had the request been a GET.
[357]1552<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Content-Type"/><iref primary="true" item="Grammar" subitem="Content-Type-v"/>
[366]1553  <x:ref>Content-Type</x:ref>   = "Content-Type" ":" <x:ref>OWS</x:ref> <x:ref>Content-Type-v</x:ref>
[357]1554  <x:ref>Content-Type-v</x:ref> = <x:ref>media-type</x:ref>
1557   Media types are defined in <xref target="media.types"/>. An example of the field is
1559<figure><artwork type="example">
[357]1560  Content-Type: text/html; charset=ISO-8859-4
[965]1563   Further discussion of Content-Type is provided in <xref target=""/>.
[29]1569<section title="IANA Considerations" anchor="IANA.considerations">
[921]1570<section title="Header Field Registration" anchor="header.field.registration">
[969]1572   The Message Header Field Registry located at <eref target=""/> shall be updated
[290]1573   with the permanent registrations below (see <xref target="RFC3864"/>):
[680]1575<?BEGININC p3-payload.iana-headers ?>
[253]1576<!--AUTOGENERATED FROM extract-header-defs.xslt, do not edit manually-->
[290]1577<texttable align="left" suppress-title="true" anchor="iana.header.registration.table">
[253]1578   <ttcol>Header Field Name</ttcol>
1579   <ttcol>Protocol</ttcol>
1580   <ttcol>Status</ttcol>
1581   <ttcol>Reference</ttcol>
1583   <c>Accept</c>
1584   <c>http</c>
1585   <c>standard</c>
1586   <c>
1587      <xref target="header.accept"/>
1588   </c>
1589   <c>Accept-Charset</c>
1590   <c>http</c>
1591   <c>standard</c>
1592   <c>
1593      <xref target="header.accept-charset"/>
1594   </c>
1595   <c>Accept-Encoding</c>
1596   <c>http</c>
1597   <c>standard</c>
1598   <c>
1599      <xref target="header.accept-encoding"/>
1600   </c>
1601   <c>Accept-Language</c>
1602   <c>http</c>
1603   <c>standard</c>
1604   <c>
1605      <xref target="header.accept-language"/>
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>
[937]1639   <c>standard</c>
[291]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=""/>
[969]1658   shall 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.
[994]1700<section title="Privacy Issues Connected to Accept Header Fields" anchor="">
[1163]1702   Accept headers fields can reveal information about the user to all
[994]1703   servers which are accessed. The Accept-Language header field in particular
[8]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
[994]1708   Accept-Language header field to be sent in every request are strongly
[8]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
[994]1714   to omit the sending of Accept-Language header fields by default, and to ask
1715   the user whether or not to start sending Accept-Language header fields to a
[1163]1716   server if it detects, by looking for any Vary header fields
[8]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
[994]1732   measure, proxies could filter the accept header fields in relayed requests.
[8]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.
1741<section title="Acknowledgments" anchor="ack">
[119]1746<references title="Normative References">
[121]1748<reference anchor="ISO-8859-1">
1749  <front>
1750    <title>
1751     Information technology -- 8-bit single-byte coded graphic character sets -- Part 1: Latin alphabet No. 1
1752    </title>
1753    <author>
1754      <organization>International Organization for Standardization</organization>
1755    </author>
1756    <date year="1998"/>
1757  </front>
1758  <seriesInfo name="ISO/IEC" value="8859-1:1998"/>
[31]1761<reference anchor="Part1">
[119]1762  <front>
1763    <title abbrev="HTTP/1.1">HTTP/1.1, part 1: URIs, Connections, and Message Parsing</title>
1764    <author initials="R." surname="Fielding" fullname="Roy T. Fielding" role="editor">
[1106]1765      <organization abbrev="Adobe">Adobe Systems Incorporated</organization>
[119]1766      <address><email></email></address>
1767    </author>
1768    <author initials="J." surname="Gettys" fullname="Jim Gettys">
[844]1769      <organization abbrev="Alcatel-Lucent">Alcatel-Lucent Bell Labs</organization>
1770      <address><email></email></address>
[119]1771    </author>
1772    <author initials="J." surname="Mogul" fullname="Jeffrey C. Mogul">
1773      <organization abbrev="HP">Hewlett-Packard Company</organization>
1774      <address><email></email></address>
1775    </author>
1776    <author initials="H." surname="Frystyk" fullname="Henrik Frystyk Nielsen">
1777      <organization abbrev="Microsoft">Microsoft Corporation</organization>
1778      <address><email></email></address>
1779    </author>
1780    <author initials="L." surname="Masinter" fullname="Larry Masinter">
[1106]1781      <organization abbrev="Adobe">Adobe Systems Incorporated</organization>
[119]1782      <address><email></email></address>
1783    </author>
1784    <author initials="P." surname="Leach" fullname="Paul J. Leach">
1785      <organization abbrev="Microsoft">Microsoft Corporation</organization>
1786      <address><email></email></address>
1787    </author>
1788    <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
1789      <organization abbrev="W3C/MIT">World Wide Web Consortium</organization>
1790      <address><email></email></address>
1791    </author>
1792    <author initials="Y." surname="Lafon" fullname="Yves Lafon" role="editor">
1793      <organization abbrev="W3C">World Wide Web Consortium</organization>
1794      <address><email></email></address>
1795    </author>
1796    <author initials="J. F." surname="Reschke" fullname="Julian F. Reschke" role="editor">
1797      <organization abbrev="greenbytes">greenbytes GmbH</organization>
1798      <address><email></email></address>
1799    </author>
1800    <date month="&ID-MONTH;" year="&ID-YEAR;"/>
1801  </front>
1802  <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p1-messaging-&ID-VERSION;"/>
1803  <x:source href="p1-messaging.xml" basename="p1-messaging"/>
1806<reference anchor="Part2">
[119]1807  <front>
1808    <title abbrev="HTTP/1.1">HTTP/1.1, part 2: Message Semantics</title>
1809    <author initials="R." surname="Fielding" fullname="Roy T. Fielding" role="editor">
[1106]1810      <organization abbrev="Adobe">Adobe Systems Incorporated</organization>
[119]1811      <address><email></email></address>
1812    </author>
1813    <author initials="J." surname="Gettys" fullname="Jim Gettys">
[844]1814      <organization abbrev="Alcatel-Lucent">Alcatel-Lucent Bell Labs</organization>
1815      <address><email></email></address>
[119]1816    </author>
1817    <author initials="J." surname="Mogul" fullname="Jeffrey C. Mogul">
1818      <organization abbrev="HP">Hewlett-Packard Company</organization>
1819      <address><email></email></address>
1820    </author>
1821    <author initials="H." surname="Frystyk" fullname="Henrik Frystyk Nielsen">
1822      <organization abbrev="Microsoft">Microsoft Corporation</organization>
1823      <address><email></email></address>
1824    </author>
1825    <author initials="L." surname="Masinter" fullname="Larry Masinter">
[1106]1826      <organization abbrev="Adobe">Adobe Systems Incorporated</organization>
[119]1827      <address><email></email></address>
1828    </author>
1829    <author initials="P." surname="Leach" fullname="Paul J. Leach">
1830      <organization abbrev="Microsoft">Microsoft Corporation</organization>
1831      <address><email></email></address>
1832    </author>
1833    <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
1834      <organization abbrev="W3C/MIT">World Wide Web Consortium</organization>
1835      <address><email></email></address>
1836    </author>
1837    <author initials="Y." surname="Lafon" fullname="Yves Lafon" role="editor">
1838      <organization abbrev="W3C">World Wide Web Consortium</organization>
1839      <address><email></email></address>
1840    </author>
1841    <author initials="J. F." surname="Reschke" fullname="Julian F. Reschke" role="editor">
1842      <organization abbrev="greenbytes">greenbytes GmbH</organization>
1843      <address><email></email></address>
1844    </author>
1845    <date month="&ID-MONTH;" year="&ID-YEAR;"/>
1846  </front>
1847  <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p2-semantics-&ID-VERSION;"/>
1848  <x:source href="p2-semantics.xml" basename="p2-semantics"/>
1851<reference anchor="Part4">
[119]1852  <front>
1853    <title abbrev="HTTP/1.1">HTTP/1.1, part 4: Conditional Requests</title>
1854    <author initials="R." surname="Fielding" fullname="Roy T. Fielding" role="editor">
[1106]1855      <organization abbrev="Adobe">Adobe Systems Incorporated</organization>
[119]1856      <address><email></email></address>
1857    </author>
1858    <author initials="J." surname="Gettys" fullname="Jim Gettys">
[844]1859      <organization abbrev="Alcatel-Lucent">Alcatel-Lucent Bell Labs</organization>
1860      <address><email></email></address>
[119]1861    </author>
1862    <author initials="J." surname="Mogul" fullname="Jeffrey C. Mogul">
1863      <organization abbrev="HP">Hewlett-Packard Company</organization>
1864      <address><email></email></address>
1865    </author>
1866    <author initials="H." surname="Frystyk" fullname="Henrik Frystyk Nielsen">
1867      <organization abbrev="Microsoft">Microsoft Corporation</organization>
1868      <address><email></email></address>
1869    </author>
1870    <author initials="L." surname="Masinter" fullname="Larry Masinter">
[1106]1871      <organization abbrev="Adobe">Adobe Systems Incorporated</organization>
[119]1872      <address><email></email></address>
1873    </author>
1874    <author initials="P." surname="Leach" fullname="Paul J. Leach">
1875      <organization abbrev="Microsoft">Microsoft Corporation</organization>
1876      <address><email></email></address>
1877    </author>
1878    <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
1879      <organization abbrev="W3C/MIT">World Wide Web Consortium</organization>
1880      <address><email></email></address>
1881    </author>
1882    <author initials="Y." surname="Lafon" fullname="Yves Lafon" role="editor">
1883      <organization abbrev="W3C">World Wide Web Consortium</organization>
1884      <address><email></email></address>
1885    </author>
1886    <author initials="J. F." surname="Reschke" fullname="Julian F. Reschke" role="editor">
1887      <organization abbrev="greenbytes">greenbytes GmbH</organization>
1888      <address><email></email></address>
1889    </author>
1890    <date month="&ID-MONTH;" year="&ID-YEAR;"/>
1891  </front>
1892  <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p4-conditional-&ID-VERSION;"/>
1893  <x:source href="p4-conditional.xml" basename="p4-conditional"/>
1896<reference anchor="Part5">
[119]1897  <front>
1898    <title abbrev="HTTP/1.1">HTTP/1.1, part 5: Range Requests and Partial Responses</title>
1899    <author initials="R." surname="Fielding" fullname="Roy T. Fielding" role="editor">
[1106]1900      <organization abbrev="Adobe">Adobe Systems Incorporated</organization>
[119]1901      <address><email></email></address>
1902    </author>
1903    <author initials="J." surname="Gettys" fullname="Jim Gettys">
[844]1904      <organization abbrev="Alcatel-Lucent">Alcatel-Lucent Bell Labs</organization>
1905      <address><email></email></address>
[119]1906    </author>
1907    <author initials="J." surname="Mogul" fullname="Jeffrey C. Mogul">
1908      <organization abbrev="HP">Hewlett-Packard Company</organization>
1909      <address><email></email></address>
1910    </author>
1911    <author initials="H." surname="Frystyk" fullname="Henrik Frystyk Nielsen">
1912      <organization abbrev="Microsoft">Microsoft Corporation</organization>
1913      <address><email></email></address>
1914    </author>
1915    <author initials="L." surname="Masinter" fullname="Larry Masinter">
[1106]1916      <organization abbrev="Adobe">Adobe Systems Incorporated</organization>
[119]1917      <address><email></email></address>
1918    </author>
1919    <author initials="P." surname="Leach" fullname="Paul J. Leach">
1920      <organization abbrev="Microsoft">Microsoft Corporation</organization>
1921      <address><email></email></address>
1922    </author>
1923    <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
1924      <organization abbrev="W3C/MIT">World Wide Web Consortium</organization>
1925      <address><email></email></address>
1926    </author>
1927    <author initials="Y." surname="Lafon" fullname="Yves Lafon" role="editor">
1928      <organization abbrev="W3C">World Wide Web Consortium</organization>
1929      <address><email></email></address>
1930    </author>
1931    <author initials="J. F." surname="Reschke" fullname="Julian F. Reschke" role="editor">
1932      <organization abbrev="greenbytes">greenbytes GmbH</organization>
1933      <address><email></email></address>
1934    </author>
1935    <date month="&ID-MONTH;" year="&ID-YEAR;"/>
1936  </front>
1937  <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p5-range-&ID-VERSION;"/>
1938  <x:source href="p5-range.xml" basename="p5-range"/>
1941<reference anchor="Part6">
[119]1942  <front>
1943    <title abbrev="HTTP/1.1">HTTP/1.1, part 6: Caching</title>
1944    <author initials="R." surname="Fielding" fullname="Roy T. Fielding" role="editor">
[1106]1945      <organization abbrev="Adobe">Adobe Systems Incorporated</organization>
[119]1946      <address><email></email></address>
1947    </author>
1948    <author initials="J." surname="Gettys" fullname="Jim Gettys">
[844]1949      <organization abbrev="Alcatel-Lucent">Alcatel-Lucent Bell Labs</organization>
1950      <address><email></email></address>
[119]1951    </author>
1952    <author initials="J." surname="Mogul" fullname="Jeffrey C. Mogul">
1953      <organization abbrev="HP">Hewlett-Packard Company</organization>
1954      <address><email></email></address>
1955    </author>
1956    <author initials="H." surname="Frystyk" fullname="Henrik Frystyk Nielsen">
1957      <organization abbrev="Microsoft">Microsoft Corporation</organization>
1958      <address><email></email></address>
1959    </author>
1960    <author initials="L." surname="Masinter" fullname="Larry Masinter">
[1106]1961      <organization abbrev="Adobe">Adobe Systems Incorporated</organization>
[119]1962      <address><email></email></address>
1963    </author>
1964    <author initials="P." surname="Leach" fullname="Paul J. Leach">
1965      <organization abbrev="Microsoft">Microsoft Corporation</organization>
1966      <address><email></email></address>
1967    </author>
1968    <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
1969      <organization abbrev="W3C/MIT">World Wide Web Consortium</organization>
1970      <address><email></email></address>
1971    </author>
1972    <author initials="Y." surname="Lafon" fullname="Yves Lafon" role="editor">
1973      <organization abbrev="W3C">World Wide Web Consortium</organization>
1974      <address><email></email></address>
1975    </author>
[601]1976    <author initials="M." surname="Nottingham" fullname="Mark Nottingham" role="editor">
1977      <address><email></email></address>
1978    </author>
[119]1979    <author initials="J. F." surname="Reschke" fullname="Julian F. Reschke" role="editor">
1980      <organization abbrev="greenbytes">greenbytes GmbH</organization>
1981      <address><email></email></address>
1982    </author>
1983    <date month="&ID-MONTH;" year="&ID-YEAR;"/>
1984  </front>
1985  <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p6-cache-&ID-VERSION;"/>
1986  <x:source href="p6-cache.xml" basename="p6-cache"/>
[131]1989<reference anchor="RFC1864">
1990  <front>
1991    <title abbrev="Content-MD5 Header Field">The Content-MD5 Header Field</title>
1992    <author initials="J." surname="Myers" fullname="John G. Myers">
1993      <organization>Carnegie Mellon University</organization>
1994      <address><email></email></address>
1995    </author>
1996    <author initials="M." surname="Rose" fullname="Marshall T. Rose">
1997      <organization>Dover Beach Consulting, Inc.</organization>
1998      <address><email></email></address>
1999    </author>
2000    <date month="October" year="1995"/>
2001  </front>
2002  <seriesInfo name="RFC" value="1864"/>
[122]2005<reference anchor="RFC1950">
2006  <front>
2007    <title>ZLIB Compressed Data Format Specification version 3.3</title>
2008    <author initials="L.P." surname="Deutsch" fullname="L. Peter Deutsch">
2009      <organization>Aladdin Enterprises</organization>
2010      <address><email></email></address>
2011    </author>
[713]2012    <author initials="J-L." surname="Gailly" fullname="Jean-Loup Gailly"/>
[122]2013    <date month="May" year="1996"/>
2014  </front>
2015  <seriesInfo name="RFC" value="1950"/>
2016  <annotation>
[908]2017    RFC 1950 is an Informational RFC, thus it might be less stable than
[122]2018    this specification. On the other hand, this downward reference was
[277]2019    present since the publication of RFC 2068 in 1997 (<xref target="RFC2068"/>),
2020    therefore it is unlikely to cause problems in practice. See also
2021    <xref target="BCP97"/>.
[122]2022  </annotation>
[806]2025<reference anchor="RFC1951">
2026  <front>
2027    <title>DEFLATE Compressed Data Format Specification version 1.3</title>
2028    <author initials="P." surname="Deutsch" fullname="L. Peter Deutsch">
2029      <organization>Aladdin Enterprises</organization>
2030      <address><email></email></address>
2031    </author>
2032    <date month="May" year="1996"/>
2033  </front>
2034  <seriesInfo name="RFC" value="1951"/>
2035  <annotation>
[908]2036    RFC 1951 is an Informational RFC, thus it might be less stable than
[806]2037    this specification. On the other hand, this downward reference was
2038    present since the publication of RFC 2068 in 1997 (<xref target="RFC2068"/>),
2039    therefore it is unlikely to cause problems in practice. See also
2040    <xref target="BCP97"/>.
2041  </annotation>
[122]2044<reference anchor="RFC1952">
2045  <front>
2046    <title>GZIP file format specification version 4.3</title>
2047    <author initials="P." surname="Deutsch" fullname="L. Peter Deutsch">
2048      <organization>Aladdin Enterprises</organization>
2049      <address><email></email></address>
2050    </author>
2051    <author initials="J-L." surname="Gailly" fullname="Jean-Loup Gailly">
2052      <address><email></email></address>
2053    </author>
2054    <author initials="M." surname="Adler" fullname="Mark Adler">
2055      <address><email></email></address>
2056    </author>
2057    <author initials="L.P." surname="Deutsch" fullname="L. Peter Deutsch">
2058      <address><email></email></address>
2059    </author>
2060    <author initials="G." surname="Randers-Pehrson" fullname="Glenn Randers-Pehrson">
2061      <address><email></email></address>
2062    </author>
2063    <date month="May" year="1996"/>
2064  </front>
2065  <seriesInfo name="RFC" value="1952"/>
2066  <annotation>
[908]2067    RFC 1952 is an Informational RFC, thus it might be less stable than
[122]2068    this specification. On the other hand, this downward reference was
[277]2069    present since the publication of RFC 2068 in 1997 (<xref target="RFC2068"/>),
2070    therefore it is unlikely to cause problems in practice. See also
2071    <xref target="BCP97"/>.
[122]2072  </annotation>
[131]2075<reference anchor="RFC2045">
2076  <front>
2077    <title abbrev="Internet Message Bodies">Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies</title>
2078    <author initials="N." surname="Freed" fullname="Ned Freed">
2079      <organization>Innosoft International, Inc.</organization>
2080      <address><email></email></address>
2081    </author>
2082    <author initials="N.S." surname="Borenstein" fullname="Nathaniel S. Borenstein">
2083      <organization>First Virtual Holdings</organization>
2084      <address><email></email></address>
2085    </author>
2086    <date month="November" year="1996"/>
2087  </front>
2088  <seriesInfo name="RFC" value="2045"/>
2091<reference anchor="RFC2046">
2092  <front>
2093    <title abbrev="Media Types">Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types</title>
2094    <author initials="N." surname="Freed" fullname="Ned Freed">
2095      <organization>Innosoft International, Inc.</organization>
2096      <address><email></email></address>
2097    </author>
2098    <author initials="N." surname="Borenstein" fullname="Nathaniel S. Borenstein">
2099      <organization>First Virtual Holdings</organization>
2100      <address><email></email></address>
2101    </author>
2102    <date month="November" year="1996"/>
2103  </front>
2104  <seriesInfo name="RFC" value="2046"/>
[119]2107<reference anchor="RFC2119">
2108  <front>
2109    <title>Key words for use in RFCs to Indicate Requirement Levels</title>
2110    <author initials="S." surname="Bradner" fullname="Scott Bradner">
2111      <organization>Harvard University</organization>
2112      <address><email></email></address>
2113    </author>
2114    <date month="March" year="1997"/>
2115  </front>
2116  <seriesInfo name="BCP" value="14"/>
2117  <seriesInfo name="RFC" value="2119"/>
[303]2120<reference anchor='RFC4647'>
2121  <front>
2122    <title>Matching of Language Tags</title>
2123    <author initials='A.' surname='Phillips' fullname='Addison Phillips' role="editor">
2124      <organization>Yahoo! Inc.</organization>
2125      <address><email></email></address>
2126    </author>
2127    <author initials='M.' surname='Davis' fullname='Mark Davis' role="editor">
2128      <organization>Google</organization>
2129      <address><email></email></address>
2130    </author>
2131    <date year='2006' month='September' />
2132  </front>
2133  <seriesInfo name='BCP' value='47' />
2134  <seriesInfo name='RFC' value='4647' />
[425]2137<reference anchor="RFC5234">
2138  <front>
2139    <title abbrev="ABNF for Syntax Specifications">Augmented BNF for Syntax Specifications: ABNF</title>
2140    <author initials="D." surname="Crocker" fullname="Dave Crocker" role="editor">
2141      <organization>Brandenburg InternetWorking</organization>
2142      <address>
[728]2143        <email></email>
2144      </address> 
[425]2145    </author>
2146    <author initials="P." surname="Overell" fullname="Paul Overell">
2147      <organization>THUS plc.</organization>
2148      <address>
[728]2149        <email></email>
2150      </address>
[425]2151    </author>
2152    <date month="January" year="2008"/>
2153  </front>
2154  <seriesInfo name="STD" value="68"/>
2155  <seriesInfo name="RFC" value="5234"/>
[690]2158<reference anchor='RFC5646'>
[613]2159  <front>
2160    <title>Tags for Identifying Languages</title>
2161    <author initials='A.' surname='Phillips' fullname='Addison Phillips' role='editor'>
2162      <organization>Lab126</organization>
2163      <address><email></email></address>
2164    </author>
2165    <author initials='M.' surname='Davis' fullname='Mark Davis' role='editor'>
2166      <organization>Google</organization>
2167      <address><email></email></address>
2168    </author>
[690]2169    <date month='September' year='2009' />
[613]2170  </front>
[690]2171  <seriesInfo name='BCP' value='47' />
2172  <seriesInfo name='RFC' value='5646' />
2177<references title="Informative References">
[129]2179<reference anchor="RFC1945">
2180  <front>
2181    <title abbrev="HTTP/1.0">Hypertext Transfer Protocol -- HTTP/1.0</title>
2182    <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
2183      <organization>MIT, Laboratory for Computer Science</organization>
2184      <address><email></email></address>
2185    </author>
2186    <author initials="R.T." surname="Fielding" fullname="Roy T. Fielding">
2187      <organization>University of California, Irvine, Department of Information and Computer Science</organization>
2188      <address><email></email></address>
2189    </author>
2190    <author initials="H.F." surname="Nielsen" fullname="Henrik Frystyk Nielsen">
2191      <organization>W3 Consortium, MIT Laboratory for Computer Science</organization>
2192      <address><email></email></address>
2193    </author>
2194    <date month="May" year="1996"/>
2195  </front>
2196  <seriesInfo name="RFC" value="1945"/>
2199<reference anchor="RFC2049">
2200  <front>
2201    <title abbrev="MIME Conformance">Multipurpose Internet Mail Extensions (MIME) Part Five: Conformance Criteria and Examples</title>
2202    <author initials="N." surname="Freed" fullname="Ned Freed">
2203      <organization>Innosoft International, Inc.</organization>
2204      <address><email></email></address>
2205    </author>
2206    <author initials="N.S." surname="Borenstein" fullname="Nathaniel S. Borenstein">
2207      <organization>First Virtual Holdings</organization>
2208      <address><email></email></address>
2209    </author>
2210    <date month="November" year="1996"/>
2211  </front>
2212  <seriesInfo name="RFC" value="2049"/>
[133]2215<reference anchor="RFC2068">
2216  <front>
2217    <title abbrev="HTTP/1.1">Hypertext Transfer Protocol -- HTTP/1.1</title>
2218    <author initials="R." surname="Fielding" fullname="Roy T. Fielding">
2219      <organization>University of California, Irvine, Department of Information and Computer Science</organization>
2220      <address><email></email></address>
2221    </author>
2222    <author initials="J." surname="Gettys" fullname="Jim Gettys">
2223      <organization>MIT Laboratory for Computer Science</organization>
2224      <address><email></email></address>
2225    </author>
2226    <author initials="J." surname="Mogul" fullname="Jeffrey C. Mogul">
2227      <organization>Digital Equipment Corporation, Western Research Laboratory</organization>
2228      <address><email></email></address>
2229    </author>
2230    <author initials="H." surname="Nielsen" fullname="Henrik Frystyk Nielsen">
2231      <organization>MIT Laboratory for Computer Science</organization>
2232      <address><email></email></address>
2233    </author>
2234    <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
2235      <organization>MIT Laboratory for Computer Science</organization>
2236      <address><email></email></address>
2237    </author>
2238    <date month="January" year="1997"/>
2239  </front>
2240  <seriesInfo name="RFC" value="2068"/>
[129]2243<reference anchor="RFC2076">
2244  <front>
2245    <title abbrev="Internet Message Headers">Common Internet Message Headers</title>
2246    <author initials="J." surname="Palme" fullname="Jacob Palme">
2247      <organization>Stockholm University/KTH</organization>
2248      <address><email></email></address>
2249    </author>
2250    <date month="February" year="1997"/>
2251  </front>
2252  <seriesInfo name="RFC" value="2076"/>
2255<reference anchor="RFC2277">
2256  <front>
2257    <title abbrev="Charset Policy">IETF Policy on Character Sets and Languages</title>
2258    <author initials="H.T." surname="Alvestrand" fullname="Harald Tveit Alvestrand">
2259      <organization>UNINETT</organization>
2260      <address><email></email></address>
2261    </author>
2262    <date month="January" year="1998"/>
2263  </front>
2264  <seriesInfo name="BCP" value="18"/>
2265  <seriesInfo name="RFC" value="2277"/>
[745]2268<reference anchor='RFC2295'>
2269  <front>
2270    <title abbrev='HTTP Content Negotiation'>Transparent Content Negotiation in HTTP</title>
2271    <author initials='K.' surname='Holtman' fullname='Koen Holtman'>
2272      <organization>Technische Universiteit Eindhoven</organization>
2273      <address>
2274        <email></email>
2275      </address>
2276    </author>
2277    <author initials='A.H.' surname='Mutz' fullname='Andrew H. Mutz'>
2278      <organization>Hewlett-Packard Company</organization>
2279      <address>
2280        <email></email>
2281      </address>
2282    </author>
2283    <date year='1998' month='March'/>
2284  </front>
2285  <seriesInfo name='RFC' value='2295'/>
[129]2288<reference anchor="RFC2388">
2289  <front>
2290    <title abbrev="multipart/form-data">Returning Values from Forms:  multipart/form-data</title>
2291    <author initials="L." surname="Masinter" fullname="Larry Masinter">
2292      <organization>Xerox Palo Alto Research Center</organization>
2293      <address><email></email></address>
2294    </author>
2295    <date year="1998" month="August"/>
2296  </front>
2297  <seriesInfo name="RFC" value="2388"/>
2300<reference anchor="RFC2557">
2301  <front>
2302    <title abbrev="MIME Encapsulation of Aggregate Documents">MIME Encapsulation of Aggregate Documents, such as HTML (MHTML)</title>
2303    <author initials="F." surname="Palme" fullname="Jacob Palme">
2304      <organization>Stockholm University and KTH</organization>
2305      <address><email></email></address>
2306    </author>
2307    <author initials="A." surname="Hopmann" fullname="Alex Hopmann">
2308      <organization>Microsoft Corporation</organization>
2309      <address><email></email></address>
2310    </author>
2311    <author initials="N." surname="Shelness" fullname="Nick Shelness">
2312      <organization>Lotus Development Corporation</organization>
2313      <address><email></email></address>
2314    </author>
2315    <author initials="E." surname="Stefferud" fullname="Einar Stefferud">
2316      <address><email></email></address>
2317    </author>
2318    <date year="1999" month="March"/>
2319  </front>
2320  <seriesInfo name="RFC" value="2557"/>
[119]2323<reference anchor="RFC2616">
2324  <front>
2325    <title>Hypertext Transfer Protocol -- HTTP/1.1</title>
2326    <author initials="R." surname="Fielding" fullname="R. Fielding">
2327      <organization>University of California, Irvine</organization>
2328      <address><email></email></address>
2329    </author>
2330    <author initials="J." surname="Gettys" fullname="J. Gettys">
2331      <organization>W3C</organization>
2332      <address><email></email></address>
2333    </author>
2334    <author initials="J." surname="Mogul" fullname="J. Mogul">
2335      <organization>Compaq Computer Corporation</organization>
2336      <address><email></email></address>
2337    </author>
2338    <author initials="H." surname="Frystyk" fullname="H. Frystyk">
2339      <organization>MIT Laboratory for Computer Science</organization>
2340      <address><email></email></address>
2341    </author>
2342    <author initials="L." surname="Masinter" fullname="L. Masinter">
2343      <organization>Xerox Corporation</organization>
2344      <address><email></email></address>
2345    </author>
2346    <author initials="P." surname="Leach" fullname="P. Leach">
2347      <organization>Microsoft Corporation</organization>
2348      <address><email></email></address>
2349    </author>
2350    <author initials="T." surname="Berners-Lee" fullname="T. Berners-Lee">
2351      <organization>W3C</organization>
2352      <address><email></email></address>
2353    </author>
2354    <date month="June" year="1999"/>
2355  </front>
2356  <seriesInfo name="RFC" value="2616"/>
[129]2359<reference anchor="RFC3629">
2360  <front>
2361    <title>UTF-8, a transformation format of ISO 10646</title>
2362    <author initials="F." surname="Yergeau" fullname="F. Yergeau">
2363      <organization>Alis Technologies</organization>
2364      <address><email></email></address>
2365    </author>
2366    <date month="November" year="2003"/>
2367  </front>
[1003]2368  <seriesInfo name="STD" value="63"/>
[129]2369  <seriesInfo name="RFC" value="3629"/>
[253]2372<reference anchor='RFC3864'>
2373  <front>
2374    <title>Registration Procedures for Message Header Fields</title>
2375    <author initials='G.' surname='Klyne' fullname='G. Klyne'>
2376      <organization>Nine by Nine</organization>
2377      <address><email></email></address>
2378    </author>
2379    <author initials='M.' surname='Nottingham' fullname='M. Nottingham'>
2380      <organization>BEA Systems</organization>
2381      <address><email></email></address>
2382    </author>
2383    <author initials='J.' surname='Mogul' fullname='J. Mogul'>
2384      <organization>HP Labs</organization>
2385      <address><email></email></address>
2386    </author>
2387    <date year='2004' month='September' />
2388  </front>
2389  <seriesInfo name='BCP' value='90' />
2390  <seriesInfo name='RFC' value='3864' />
[200]2393<reference anchor="RFC4288">
2394  <front>
2395    <title>Media Type Specifications and Registration Procedures</title>
2396    <author initials="N." surname="Freed" fullname="N. Freed">
2397      <organization>Sun Microsystems</organization>
2398      <address>
2399        <email></email>
2400      </address>
2401    </author>
2402    <author initials="J." surname="Klensin" fullname="J. Klensin">
2403      <address>
2404        <email></email>
2405      </address>
2406    </author>
2407    <date year="2005" month="December"/>
2408  </front>
2409  <seriesInfo name="BCP" value="13"/>
2410  <seriesInfo name="RFC" value="4288"/>
[670]2413<reference anchor='RFC5226'>
2414  <front>
2415    <title>Guidelines for Writing an IANA Considerations Section in RFCs</title>
2416    <author initials='T.' surname='Narten' fullname='T. Narten'>
2417      <organization>IBM</organization>
2418      <address><email></email></address>
2419    </author>
2420    <author initials='H.' surname='Alvestrand' fullname='H. Alvestrand'>
2421      <organization>Google</organization>
2422      <address><email></email></address>
2423    </author>
2424    <date year='2008' month='May' />
2425  </front>
2426  <seriesInfo name='BCP' value='26' />
2427  <seriesInfo name='RFC' value='5226' />
[327]2430<reference anchor="RFC5322">
2431  <front>
2432    <title>Internet Message Format</title>
2433    <author initials="P." surname="Resnick" fullname="P. Resnick">
2434      <organization>Qualcomm Incorporated</organization>
2435    </author>
2436    <date year="2008" month="October"/>
2437  </front>
2438  <seriesInfo name="RFC" value="5322"/>
[277]2441<reference anchor='BCP97'>
2442  <front>
2443    <title>Handling Normative References to Standards-Track Documents</title>
2444    <author initials='J.' surname='Klensin' fullname='J. Klensin'>
2445      <address>
2446        <email></email>
2447      </address>
2448    </author>
2449    <author initials='S.' surname='Hartman' fullname='S. Hartman'>
2450      <organization>MIT</organization>
2451      <address>
2452        <email></email>
2453      </address>
2454    </author>
2455    <date year='2007' month='June' />
2456  </front>
2457  <seriesInfo name='BCP' value='97' />
2458  <seriesInfo name='RFC' value='4897' />
[874]2464<section title="Differences between HTTP and MIME" anchor="differences.between.http.and.mime">
[327]2466   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
[874]2467   allow a message-body to be transmitted in an open variety of
[8]2468   representations and with extensible mechanisms. However, RFC 2045
2469   discusses mail, and HTTP has a few features that are different from
[874]2470   those described in MIME. These differences were carefully chosen
[8]2471   to optimize performance over binary connections, to allow greater
2472   freedom in the use of new media types, to make date comparisons
2473   easier, and to acknowledge the practice of some early HTTP servers
2474   and clients.
[874]2477   This appendix describes specific areas where HTTP differs from MIME.
2478   Proxies and gateways to strict MIME environments &SHOULD; be
[8]2479   aware of these differences and provide the appropriate conversions
2480   where necessary. Proxies and gateways from MIME environments to HTTP
2481   also need to be aware of the differences because some conversions
2482   might be required.
[8]2485<section title="MIME-Version" anchor="mime-version">
[1120]2486  <iref primary="true" item="MIME-Version header field" x:for-anchor=""/>
2487  <iref primary="true" item="Header Fields" subitem="MIME-Version" x:for-anchor=""/>
[229]2488  <x:anchor-alias value="MIME-Version"/>
[357]2489  <x:anchor-alias value="MIME-Version-v"/>
2491   HTTP is not a MIME-compliant protocol. However, HTTP/1.1 messages &MAY;
[1163]2492   include a single MIME-Version header field to indicate what
[8]2493   version of the MIME protocol was used to construct the message. Use
2494   of the MIME-Version header field indicates that the message is in
[115]2495   full compliance with the MIME protocol (as defined in <xref target="RFC2045"/>).
[8]2496   Proxies/gateways are responsible for ensuring full compliance (where
2497   possible) when exporting HTTP messages to strict MIME environments.
[357]2499<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="MIME-Version"/><iref primary="true" item="Grammar" subitem="MIME-Version-v"/>
[366]2500  <x:ref>MIME-Version</x:ref>   = "MIME-Version" ":" <x:ref>OWS</x:ref> <x:ref>MIME-Version-v</x:ref>
[357]2501  <x:ref>MIME-Version-v</x:ref> = 1*<x:ref>DIGIT</x:ref> "." 1*<x:ref>DIGIT</x:ref>
2504   MIME version "1.0" is the default for use in HTTP/1.1. However,
2505   HTTP/1.1 message parsing and semantics are defined by this document
2506   and not the MIME specification.
2510<section title="Conversion to Canonical Form" anchor="">
[874]2512   MIME requires that an Internet mail body-part be converted to
[115]2513   canonical form prior to being transferred, as described in <xref target="RFC2049" x:fmt="of" x:sec="4"/>.
[97]2514   <xref target="canonicalization.and.text.defaults"/> of this document describes the forms
[8]2515   allowed for subtypes of the "text" media type when transmitted over
[97]2516   HTTP. <xref target="RFC2046"/> requires that content with a type of "text" represent
[8]2517   line breaks as CRLF and forbids the use of CR or LF outside of line
2518   break sequences. HTTP allows CRLF, bare CR, and bare LF to indicate a
2519   line break within text content when a message is transmitted over
2520   HTTP.
2523   Where it is possible, a proxy or gateway from HTTP to a strict MIME
2524   environment &SHOULD; translate all line breaks within the text media
[1176]2525   types described in <xref target="canonicalization.and.text.defaults"/>
2526   of this document to the RFC 2049
[8]2527   canonical form of CRLF. Note, however, that this might be complicated
2528   by the presence of a Content-Encoding and by the fact that HTTP
[1176]2529   allows the use of some character encodings which do not use octets 13 and
2530   10 to represent CR and LF, respectively, as is the case for some multi-byte
2531   character encodings.
[969]2534   Conversion will break any cryptographic
[8]2535   checksums applied to the original content unless the original content
2536   is already in canonical form. Therefore, the canonical form is
2537   recommended for any content that uses such checksums in HTTP.
2542<section title="Conversion of Date Formats" anchor="">
2544   HTTP/1.1 uses a restricted set of date formats (&full-date;) to
2545   simplify the process of date comparison. Proxies and gateways from
2546   other protocols &SHOULD; ensure that any Date header field present in a
2547   message conforms to one of the HTTP/1.1 formats and rewrite the date
2548   if necessary.
[8]2552<section title="Introduction of Content-Encoding" anchor="introduction.of.content-encoding">
[874]2554   MIME does not include any concept equivalent to HTTP/1.1's
[8]2555   Content-Encoding header field. Since this acts as a modifier on the
2556   media type, proxies and gateways from HTTP to MIME-compliant
2557   protocols &MUST; either change the value of the Content-Type header
[874]2558   field or decode the representation before forwarding the message. (Some
[8]2559   experimental applications of Content-Type for Internet mail have used
2560   a media-type parameter of ";conversions=&lt;content-coding&gt;" to perform
2561   a function equivalent to Content-Encoding. However, this parameter is
[874]2562   not part of the MIME standards).
2566<section title="No Content-Transfer-Encoding" anchor="no.content-transfer-encoding">
[874]2568   HTTP does not use the Content-Transfer-Encoding field of MIME.
2569   Proxies and gateways from MIME-compliant protocols to HTTP &MUST;
[85]2570   remove any Content-Transfer-Encoding
[8]2571   prior to delivering the response message to an HTTP client.
2574   Proxies and gateways from HTTP to MIME-compliant protocols are
2575   responsible for ensuring that the message is in the correct format
2576   and encoding for safe transport on that protocol, where "safe
2577   transport" is defined by the limitations of the protocol being used.
2578   Such a proxy or gateway &SHOULD; label the data with an appropriate
2579   Content-Transfer-Encoding if doing so will improve the likelihood of
2580   safe transport over the destination protocol.
2584<section title="Introduction of Transfer-Encoding" anchor="introduction.of.transfer-encoding">
[29]2586   HTTP/1.1 introduces the Transfer-Encoding header field (&header-transfer-encoding;).
[8]2587   Proxies/gateways &MUST; remove any transfer-coding prior to
2588   forwarding a message via a MIME-compliant protocol.
2592<section title="MHTML and Line Length Limitations" anchor="mhtml.line.length">
[129]2594   HTTP implementations which share code with MHTML <xref target="RFC2557"/> implementations
[8]2595   need to be aware of MIME line length limitations. Since HTTP does not
2596   have this limitation, HTTP does not fold long lines. MHTML messages
2597   being transported by HTTP follow all conventions of MHTML, including
2598   line length limitations and folding, canonicalization, etc., since
2599   HTTP transports all message-bodies as payload (see <xref target="multipart.types"/>) and
2600   does not interpret the content or any MIME header lines that might be
2601   contained therein.
2606<section title="Additional Features" anchor="additional.features">
[97]2608   <xref target="RFC1945"/> and <xref target="RFC2068"/> document protocol elements used by some
[8]2609   existing HTTP implementations, but not consistently and correctly
2610   across most HTTP/1.1 applications. Implementors are advised to be
2611   aware of these features, but cannot rely upon their presence in, or
2612   interoperability with, other HTTP/1.1 applications. Some of these
2613   describe proposed experimental features, and some describe features
2614   that experimental deployment found lacking that are now addressed in
2615   the base HTTP/1.1 specification.
[994]2618   A number of other header fields, such as Content-Disposition and Title,
[97]2619   from SMTP and MIME are also often implemented (see <xref target="RFC2076"/>).
[99]2623<section title="Changes from RFC 2616" anchor="changes.from.rfc.2616">
2625  Clarify contexts that charset is used in.
2626  (<xref target="character.sets"/>)
[712]2629  Remove base URI setting semantics for Content-Location due to poor
[714]2630  implementation support, which was caused by too many broken servers emitting
[994]2631  bogus Content-Location header fields, and also the potentially undesirable effect
[714]2632  of potentially breaking relative links in content-negotiated resources.
[712]2633  (<xref target="header.content-location"/>)
[104]2636  Remove reference to non-existant identity transfer-coding value tokens.
2637  (<xref target="no.content-transfer-encoding"/>)
[680]2641<?BEGININC p3-payload.abnf-appendix ?>
[427]2642<section xmlns:x="" title="Collected ABNF" anchor="collected.abnf">
2644<artwork type="abnf" name="p3-payload.parsed-abnf">
2645<x:ref>Accept</x:ref> = "Accept:" OWS Accept-v
2646<x:ref>Accept-Charset</x:ref> = "Accept-Charset:" OWS Accept-Charset-v
2647<x:ref>Accept-Charset-v</x:ref> = *( "," OWS ) ( charset / "*" ) [ OWS ";" OWS "q="
[425]2648 qvalue ] *( OWS "," [ OWS ( charset / "*" ) [ OWS ";" OWS "q="
2649 qvalue ] ] )
[427]2650<x:ref>Accept-Encoding</x:ref> = "Accept-Encoding:" OWS Accept-Encoding-v
2651<x:ref>Accept-Encoding-v</x:ref> = [ ( "," / ( codings [ OWS ";" OWS "q=" qvalue ] )
[425]2652 ) *( OWS "," [ OWS codings [ OWS ";" OWS "q=" qvalue ] ] ) ]
[427]2653<x:ref>Accept-Language</x:ref> = "Accept-Language:" OWS Accept-Language-v
2654<x:ref>Accept-Language-v</x:ref> = *( "," OWS ) language-range [ OWS ";" OWS "q="
[425]2655 qvalue ] *( OWS "," [ OWS language-range [ OWS ";" OWS "q=" qvalue ]
2656 ] )
[427]2657<x:ref>Accept-v</x:ref> = [ ( "," / ( media-range [ accept-params ] ) ) *( OWS "," [
[425]2658 OWS media-range [ accept-params ] ] ) ]
[427]2660<x:ref>Content-Encoding</x:ref> = "Content-Encoding:" OWS Content-Encoding-v
2661<x:ref>Content-Encoding-v</x:ref> = *( "," OWS ) content-coding *( OWS "," [ OWS
[425]2662 content-coding ] )
[427]2663<x:ref>Content-Language</x:ref> = "Content-Language:" OWS Content-Language-v
2664<x:ref>Content-Language-v</x:ref> = *( "," OWS ) language-tag *( OWS "," [ OWS
[425]2665 language-tag ] )
[427]2666<x:ref>Content-Location</x:ref> = "Content-Location:" OWS Content-Location-v
2667<x:ref>Content-Location-v</x:ref> = absolute-URI / partial-URI
2668<x:ref>Content-MD5</x:ref> = "Content-MD5:" OWS Content-MD5-v
2669<x:ref>Content-MD5-v</x:ref> = &lt;base64 of 128 bit MD5 digest as per [RFC1864]&gt;
2670<x:ref>Content-Type</x:ref> = "Content-Type:" OWS Content-Type-v
2671<x:ref>Content-Type-v</x:ref> = media-type
2673<x:ref>MIME-Version</x:ref> = "MIME-Version:" OWS MIME-Version-v
2674<x:ref>MIME-Version-v</x:ref> = 1*DIGIT "." 1*DIGIT
2676<x:ref>OWS</x:ref> = &lt;OWS, defined in [Part1], Section 1.2.2&gt;
[648]2678<x:ref>absolute-URI</x:ref> = &lt;absolute-URI, defined in [Part1], Section 2.6&gt;
[810]2679<x:ref>accept-ext</x:ref> = OWS ";" OWS token [ "=" word ]
[427]2680<x:ref>accept-params</x:ref> = OWS ";" OWS "q=" qvalue *accept-ext
2681<x:ref>attribute</x:ref> = token
2683<x:ref>charset</x:ref> = token
2684<x:ref>codings</x:ref> = ( content-coding / "*" )
2685<x:ref>content-coding</x:ref> = token
[427]2687<x:ref>language-range</x:ref> = &lt;language-range, defined in [RFC4647], Section 2.1&gt;
[690]2688<x:ref>language-tag</x:ref> = &lt;Language-Tag, defined in [RFC5646], Section 2.1&gt;
2690<x:ref>media-range</x:ref> = ( "*/*" / ( type "/*" ) / ( type "/" subtype ) ) *( OWS
[425]2691 ";" OWS parameter )
[427]2692<x:ref>media-type</x:ref> = type "/" subtype *( OWS ";" OWS parameter )
2694<x:ref>parameter</x:ref> = attribute "=" value
[648]2695<x:ref>partial-URI</x:ref> = &lt;partial-URI, defined in [Part1], Section 2.6&gt;
[678]2697<x:ref>qvalue</x:ref> = &lt;qvalue, defined in [Part1], Section 6.4&gt;
2699<x:ref>subtype</x:ref> = token
2701<x:ref>token</x:ref> = &lt;token, defined in [Part1], Section 1.2.2&gt;
2702<x:ref>type</x:ref> = token
[810]2704<x:ref>value</x:ref> = word
2706<x:ref>word</x:ref> = &lt;word, defined in [Part1], Section 1.2.2&gt;
[532]2709<figure><preamble>ABNF diagnostics:</preamble><artwork type="inline">
2710; Accept defined but not used
[425]2711; Accept-Charset defined but not used
2712; Accept-Encoding defined but not used
2713; Accept-Language defined but not used
[968]2714; Content-Encoding defined but not used
2715; Content-Language defined but not used
2716; Content-Location defined but not used
2717; Content-MD5 defined but not used
2718; Content-Type defined but not used
[425]2719; MIME-Version defined but not used
[680]2721<?ENDINC p3-payload.abnf-appendix ?>
[252]2723<section title="Change Log (to be removed by RFC Editor before publication)" anchor="change.log">
[1002]2725<section title="Since RFC 2616">
2727  Extracted relevant partitions from <xref target="RFC2616"/>.
2731<section title="Since draft-ietf-httpbis-p3-payload-00">
[116]2733  Closed issues:
2734  <list style="symbols">
2735    <t>
[324]2736      <eref target=""/>:
[116]2737      "Media Type Registrations"
2738      (<eref target=""/>)
2739    </t>
2740    <t>
[324]2741      <eref target=""/>:
[116]2742      "Clarification regarding quoting of charset values"
2743      (<eref target=""/>)
2744    </t>
2745    <t>
[324]2746      <eref target=""/>:
[116]2747      "Remove 'identity' token references"
2748      (<eref target=""/>)
2749    </t>
2750    <t>
[324]2751      <eref target=""/>:
[126]2752      "Accept-Encoding BNF"
2753    </t>
2754    <t>
[324]2755      <eref target=""/>:
[152]2756      "Normative and Informative references"
2757    </t>
2758    <t>
[324]2759      <eref target=""/>:
[116]2760      "RFC1700 references"
2761    </t>
[122]2762    <t>
[324]2763      <eref target=""/>:
[200]2764      "Updating to RFC4288"
2765    </t>
2766    <t>
[324]2767      <eref target=""/>:
[129]2768      "Informative references"
2769    </t>
2770    <t>
[324]2771      <eref target=""/>:
[123]2772      "ISO-8859-1 Reference"
2773    </t>
2774    <t>
[324]2775      <eref target=""/>:
[122]2776      "Encoding References Normative"
2777    </t>
[131]2778    <t>
[324]2779      <eref target=""/>:
[131]2780      "Normative up-to-date references"
2781    </t>
[116]2782  </list>
[170]2786<section title="Since draft-ietf-httpbis-p3-payload-01">
[324]2788  Ongoing work on ABNF conversion (<eref target=""/>):
[205]2789  <list style="symbols">
2790    <t>
2791      Add explicit references to BNF syntax and rules imported from other parts of the specification.
2792    </t>
2793  </list>
[252]2797<section title="Since draft-ietf-httpbis-p3-payload-02" anchor="changes.since.02">
[232]2799  Closed issues:
2800  <list style="symbols">
2801    <t>
[324]2802      <eref target=""/>:
[251]2803      "Quoting Charsets"
2804    </t>
2805    <t>
[324]2806      <eref target=""/>:
[232]2807      "Classification for Allow header"
2808    </t>
[248]2809    <t>
[324]2810      <eref target=""/>:
[248]2811      "missing default for qvalue in description of Accept-Encoding"
2812    </t>
[232]2813  </list>
[994]2816  Ongoing work on IANA Message Header Field Registration (<eref target=""/>):
[253]2817  <list style="symbols">
2818    <t>
[994]2819      Reference RFC 3984, and update header field registrations for headers defined
[253]2820      in this document.
2821    </t>
2822  </list>
[267]2826<section title="Since draft-ietf-httpbis-p3-payload-03" anchor="changes.since.03">
[269]2828  Closed issues:
2829  <list style="symbols">
2830    <t>
[297]2831      <eref target=""/>:
2832      "Quoting Charsets"
2833    </t>
2834    <t>
[303]2835      <eref target=""/>:
2836      "language tag matching (Accept-Language) vs RFC4647"
2837    </t>
2838    <t>
[277]2839      <eref target=""/>:
[269]2840      "RFC 1806 has been replaced by RFC2183"
2841    </t>
2842  </list>
2845  Other changes:
2846  <list style="symbols">
2847    <t>
2848      <eref target=""/>:
[1101]2849      "Encoding References Normative" &mdash; rephrase the annotation and reference
[277]2850      <xref target="BCP97"/>.
2851    </t>
2852  </list>
[269]2854 </section>
[323]2856<section title="Since draft-ietf-httpbis-p3-payload-04" anchor="changes.since.04">
[327]2858  Closed issues:
2859  <list style="symbols">
2860    <t>
2861      <eref target=""/>:
2862      "RFC 2822 is updated by RFC 5322"
2863    </t>
2864  </list>
2867  Ongoing work on ABNF conversion (<eref target=""/>):
2868  <list style="symbols">
2869    <t>
2870      Use "/" instead of "|" for alternatives.
2871    </t>
[357]2872    <t>
2873      Introduce new ABNF rules for "bad" whitespace ("BWS"), optional
2874      whitespace ("OWS") and required whitespace ("RWS").
2875    </t>
2876    <t>
2877      Rewrite ABNFs to spell out whitespace rules, factor out
[994]2878      header field value format definitions.
[357]2879    </t>
[334]2880  </list>
[382]2884<section title="Since draft-ietf-httpbis-p3-payload-05" anchor="changes.since.05">
[385]2886  Closed issues:
2887  <list style="symbols">
2888    <t>
2889      <eref target=""/>:
2890      "Join "Differences Between HTTP Entities and RFC 2045 Entities"?"
2891    </t>
2892  </list>
[543]2895  Final work on ABNF conversion (<eref target=""/>):
[421]2896  <list style="symbols">
2897    <t>
[424]2898      Add appendix containing collected and expanded ABNF, reorganize ABNF introduction.
[421]2899    </t>
2900  </list>
2903  Other changes:
2904  <list style="symbols">
2905    <t>
2906      Move definition of quality values into Part 1.
2907    </t>
2908  </list>
[547]2912<section title="Since draft-ietf-httpbis-p3-payload-06" anchor="changes.since.06">
[577]2914  Closed issues:
2915  <list style="symbols">
2916    <t>
2917      <eref target=""/>:
2918      "Content-Location isn't special"
2919    </t>
[592]2920    <t>
2921      <eref target=""/>:
2922      "Content Sniffing"
2923    </t>
[577]2924  </list>
[604]2928<section title="Since draft-ietf-httpbis-p3-payload-07" anchor="changes.since.07">
[613]2930  Closed issues:
2931  <list style="symbols">
2932    <t>
[670]2933      <eref target=""/>:
[613]2934      "Updated reference for language tags"
2935    </t>
[663]2936    <t>
[716]2937      <eref target=""/>:
2938      "Clarify rules for determining what entities a response carries"
2939    </t>
2940    <t>
[712]2941      <eref target=""/>:
2942      "Content-Location base-setting problems"
2943    </t>
2944    <t>
[663]2945      <eref target=""/>:
2946      "Content Sniffing"
2947    </t>
[670]2948    <t>
2949      <eref target=""/>:
2950      "pick IANA policy (RFC5226) for Transfer Coding / Content Coding"
2951    </t>
[673]2952    <t>
2953      <eref target=""/>:
2954      "move definitions of gzip/deflate/compress to part 1"
2955    </t>
[613]2956  </list>
2959  Partly resolved issues:
2960  <list style="symbols">
2961    <t>
2962      <eref target=""/>:
2963      "update IANA requirements wrt Transfer-Coding values" (add the
2964      IANA Considerations subsection)
2965    </t>
[668]2966    <t>
2967      <eref target=""/>:
2968      "update IANA requirements wrt Content-Coding values" (add the
2969      IANA Considerations subsection)
2970    </t>
[667]2971  </list>
[720]2975<section title="Since draft-ietf-httpbis-p3-payload-08" anchor="changes.since.08">
[724]2977  Closed issues:
2978  <list style="symbols">
2979    <t>
[745]2980      <eref target=""/>:
2981      "Content Negotiation for media types"
2982    </t>
2983    <t>
[724]2984      <eref target=""/>:
2985      "Accept-Language: which RFC4647 filtering?"
2986    </t>
2987  </list>
[773]2991<section title="Since draft-ietf-httpbis-p3-payload-09" anchor="changes.since.09">
[808]2993  Closed issues:
2994  <list style="symbols">
2995    <t>
[937]2996      <eref target=""/>:
2997      "MIME-Version not listed in P1, general header fields"
2998    </t>
2999    <t>
[808]3000      <eref target=""/>:
3001      "IANA registry for content/transfer encodings"
3002    </t>
[810]3003    <t>
[831]3004      <eref target=""/>:
3005      "Content Sniffing"
3006    </t>
3007    <t>
[810]3008      <eref target=""/>:
3009      "use of term "word" when talking about header structure"
3010    </t>
[808]3011  </list>
3014  Partly resolved issues:
3015  <list style="symbols">
3016    <t>
3017      <eref target=""/>:
3018      "Term for the requested resource's URI"
3019    </t>
3020  </list>
[841]3024<section title="Since draft-ietf-httpbis-p3-payload-10" anchor="changes.since.10">
[854]3026  Closed issues:
3027  <list style="symbols">
3028    <t>
[858]3029      <eref target=""/>:
3030      "Clarify 'Requested Variant'"
3031    </t>
3032    <t>
3033      <eref target=""/>:
3034      "Content-Location isn't special"
3035    </t>
3036    <t>
[854]3037      <eref target=""/>:
3038      "Delimiting messages with multipart/byteranges"
3039    </t>
[858]3040    <t>
3041      <eref target=""/>:
3042      "Clarify entity / representation / variant terminology"
3043    </t>
3044    <t>
3045      <eref target=""/>:
3046      "confusing req. language for Content-Location"
3047    </t>
3048    <t>
3049      <eref target=""/>:
3050      "Content-Location on 304 responses"
3051    </t>
[882]3052    <t>
3053      <eref target=""/>:
3054      "'requested resource' in content-encoding definition"
3055    </t>
[911]3056    <t>
3057      <eref target=""/>:
3058      "consider removing the 'changes from 2068' sections"
3059    </t>
[854]3060  </list>
3063  Partly resolved issues:
3064  <list style="symbols">
3065    <t>
3066      <eref target=""/>:
3067      "Content-MD5 and partial responses"
3068    </t>
3069  </list>
[973]3073<section title="Since draft-ietf-httpbis-p3-payload-11" anchor="changes.since.11">
[987]3075  Closed issues:
3076  <list style="symbols">
3077    <t>
3078      <eref target=""/>:
3079      "Factor out Content-Disposition"
3080    </t>
3081  </list>
[1052]3085<section title="Since draft-ietf-httpbis-p3-payload-12" anchor="changes.since.12">
[1153]3087  Closed issues:
3088  <list style="symbols">
3089    <t>
[1165]3090      <eref target=""/>:
3091      "Header Classification"
3092    </t>
3093    <t>
[1167]3094      <eref target=""/>:
3095      "untangle ABNFs for header fields"
3096    </t>
3097    <t>
[1153]3098      <eref target=""/>:
3099      "potentially misleading MAY in media-type def"
3100    </t>
3101  </list>
[1180]3105<section title="Since draft-ietf-httpbis-p3-payload-13" anchor="changes.since.13">
3107  None yet.
Note: See TracBrowser for help on using the repository browser.