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

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

PUT and POST requests are not special with respect to Content-Location (related to #80)

  • Property svn:eol-style set to native
File size: 127.3 KB
Line 
1<?xml version="1.0" encoding="utf-8"?>
2<?xml-stylesheet type='text/xsl' href='../myxml2rfc.xslt'?>
3<!DOCTYPE rfc [
4  <!ENTITY MAY "<bcp14 xmlns='http://purl.org/net/xml2rfc/ext'>MAY</bcp14>">
5  <!ENTITY MUST "<bcp14 xmlns='http://purl.org/net/xml2rfc/ext'>MUST</bcp14>">
6  <!ENTITY MUST-NOT "<bcp14 xmlns='http://purl.org/net/xml2rfc/ext'>MUST NOT</bcp14>">
7  <!ENTITY OPTIONAL "<bcp14 xmlns='http://purl.org/net/xml2rfc/ext'>OPTIONAL</bcp14>">
8  <!ENTITY RECOMMENDED "<bcp14 xmlns='http://purl.org/net/xml2rfc/ext'>RECOMMENDED</bcp14>">
9  <!ENTITY REQUIRED "<bcp14 xmlns='http://purl.org/net/xml2rfc/ext'>REQUIRED</bcp14>">
10  <!ENTITY SHALL "<bcp14 xmlns='http://purl.org/net/xml2rfc/ext'>SHALL</bcp14>">
11  <!ENTITY SHALL-NOT "<bcp14 xmlns='http://purl.org/net/xml2rfc/ext'>SHALL NOT</bcp14>">
12  <!ENTITY SHOULD "<bcp14 xmlns='http://purl.org/net/xml2rfc/ext'>SHOULD</bcp14>">
13  <!ENTITY SHOULD-NOT "<bcp14 xmlns='http://purl.org/net/xml2rfc/ext'>SHOULD NOT</bcp14>">
14  <!ENTITY ID-VERSION "latest">
15  <!ENTITY ID-MONTH "May">
16  <!ENTITY ID-YEAR "2009">
17  <!ENTITY notation                 "<xref target='Part1' x:rel='#notation' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
18  <!ENTITY notation-abnf            "<xref target='Part1' x:rel='#notation.abnf' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
19  <!ENTITY basic-rules              "<xref target='Part1' x:rel='#basic.rules' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
20  <!ENTITY caching-neg-resp         "<xref target='Part6' x:rel='#caching.negotiated.responses' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
21  <!ENTITY header-transfer-encoding "<xref target='Part1' x:rel='#header.transfer-encoding' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
22  <!ENTITY header-content-length    "<xref target='Part1' x:rel='#header.content-length' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
23  <!ENTITY header-content-range     "<xref target='Part5' x:rel='#header.content-range' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
24  <!ENTITY header-expires           "<xref target='Part6' x:rel='#header.expires' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
25  <!ENTITY header-last-modified     "<xref target='Part4' x:rel='#header.last-modified' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
26  <!ENTITY header-user-agent        "<xref target='Part2' x:rel='#header.user-agent' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
27  <!ENTITY header-vary              "<xref target='Part6' x:rel='#header.vary' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
28  <!ENTITY message-body             "<xref target='Part1' x:rel='#message.body' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
29  <!ENTITY message-length           "<xref target='Part1' x:rel='#message.length' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
30  <!ENTITY message-headers          "<xref target='Part1' x:rel='#message.headers' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
31  <!ENTITY multipart-byteranges     "<xref target='Part5' x:rel='#internet.media.type.multipart.byteranges' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
32  <!ENTITY full-date                "<xref target='Part1' x:rel='#full.date' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
33  <!ENTITY qvalue                   "<xref target='Part1' x:rel='#quality.values' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
34  <!ENTITY uri                      "<xref target='Part1' x:rel='#uri' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
35]>
36<?rfc toc="yes" ?>
37<?rfc symrefs="yes" ?>
38<?rfc sortrefs="yes" ?>
39<?rfc compact="yes"?>
40<?rfc subcompact="no" ?>
41<?rfc linkmailto="no" ?>
42<?rfc editing="no" ?>
43<?rfc comments="yes"?>
44<?rfc inline="yes"?>
45<?rfc-ext allow-markup-in-artwork="yes" ?>
46<?rfc-ext include-references-in-index="yes" ?>
47<rfc obsoletes="2616" category="std" x:maturity-level="draft"
48     ipr="pre5378Trust200902" docName="draft-ietf-httpbis-p3-payload-&ID-VERSION;"
49     xmlns:x='http://purl.org/net/xml2rfc/ext'>
50<front>
51
52  <title abbrev="HTTP/1.1, Part 3">HTTP/1.1, part 3: Message Payload and Content Negotiation</title>
53
54  <author initials="R." surname="Fielding" fullname="Roy T. Fielding" role="editor">
55    <organization abbrev="Day Software">Day Software</organization>
56    <address>
57      <postal>
58        <street>23 Corporate Plaza DR, Suite 280</street>
59        <city>Newport Beach</city>
60        <region>CA</region>
61        <code>92660</code>
62        <country>USA</country>
63      </postal>
64      <phone>+1-949-706-5300</phone>
65      <facsimile>+1-949-706-5305</facsimile>
66      <email>fielding@gbiv.com</email>
67      <uri>http://roy.gbiv.com/</uri>
68    </address>
69  </author>
70
71  <author initials="J." surname="Gettys" fullname="Jim Gettys">
72    <organization>One Laptop per Child</organization>
73    <address>
74      <postal>
75        <street>21 Oak Knoll Road</street>
76        <city>Carlisle</city>
77        <region>MA</region>
78        <code>01741</code>
79        <country>USA</country>
80      </postal>
81      <email>jg@laptop.org</email>
82      <uri>http://www.laptop.org/</uri>
83    </address>
84  </author>
85 
86  <author initials="J." surname="Mogul" fullname="Jeffrey C. Mogul">
87    <organization abbrev="HP">Hewlett-Packard Company</organization>
88    <address>
89      <postal>
90        <street>HP Labs, Large Scale Systems Group</street>
91        <street>1501 Page Mill Road, MS 1177</street>
92        <city>Palo Alto</city>
93        <region>CA</region>
94        <code>94304</code>
95        <country>USA</country>
96      </postal>
97      <email>JeffMogul@acm.org</email>
98    </address>
99  </author>
100
101  <author initials="H." surname="Frystyk" fullname="Henrik Frystyk Nielsen">
102    <organization abbrev="Microsoft">Microsoft Corporation</organization>
103    <address>
104      <postal>
105        <street>1 Microsoft Way</street>
106        <city>Redmond</city>
107        <region>WA</region>
108        <code>98052</code>
109        <country>USA</country>
110      </postal>
111      <email>henrikn@microsoft.com</email>
112    </address>
113  </author>
114
115  <author initials="L." surname="Masinter" fullname="Larry Masinter">
116    <organization abbrev="Adobe Systems">Adobe Systems, Incorporated</organization>
117    <address>
118      <postal>
119        <street>345 Park Ave</street>
120        <city>San Jose</city>
121        <region>CA</region>
122        <code>95110</code>
123        <country>USA</country>
124      </postal>
125      <email>LMM@acm.org</email>
126      <uri>http://larry.masinter.net/</uri>
127    </address>
128  </author>
129 
130  <author initials="P." surname="Leach" fullname="Paul J. Leach">
131    <organization abbrev="Microsoft">Microsoft Corporation</organization>
132    <address>
133      <postal>
134        <street>1 Microsoft Way</street>
135        <city>Redmond</city>
136        <region>WA</region>
137        <code>98052</code>
138      </postal>
139      <email>paulle@microsoft.com</email>
140    </address>
141  </author>
142   
143  <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
144    <organization abbrev="W3C/MIT">World Wide Web Consortium</organization>
145    <address>
146      <postal>
147        <street>MIT Computer Science and Artificial Intelligence Laboratory</street>
148        <street>The Stata Center, Building 32</street>
149        <street>32 Vassar Street</street>
150        <city>Cambridge</city>
151        <region>MA</region>
152        <code>02139</code>
153        <country>USA</country>
154      </postal>
155      <email>timbl@w3.org</email>
156      <uri>http://www.w3.org/People/Berners-Lee/</uri>
157    </address>
158  </author>
159
160  <author initials="Y." surname="Lafon" fullname="Yves Lafon" role="editor">
161    <organization abbrev="W3C">World Wide Web Consortium</organization>
162    <address>
163      <postal>
164        <street>W3C / ERCIM</street>
165        <street>2004, rte des Lucioles</street>
166        <city>Sophia-Antipolis</city>
167        <region>AM</region>
168        <code>06902</code>
169        <country>France</country>
170      </postal>
171      <email>ylafon@w3.org</email>
172      <uri>http://www.raubacapeu.net/people/yves/</uri>
173    </address>
174  </author>
175
176  <author initials="J. F." surname="Reschke" fullname="Julian F. Reschke" role="editor">
177    <organization abbrev="greenbytes">greenbytes GmbH</organization>
178    <address>
179      <postal>
180        <street>Hafenweg 16</street>
181        <city>Muenster</city><region>NW</region><code>48155</code>
182        <country>Germany</country>
183      </postal>
184      <phone>+49 251 2807760</phone>   
185      <facsimile>+49 251 2807761</facsimile>   
186      <email>julian.reschke@greenbytes.de</email>       
187      <uri>http://greenbytes.de/tech/webdav/</uri>     
188    </address>
189  </author>
190
191  <date month="&ID-MONTH;" year="&ID-YEAR;"/>
192  <workgroup>HTTPbis Working Group</workgroup>
193
194<abstract>
195<t>
196   The Hypertext Transfer Protocol (HTTP) is an application-level
197   protocol for distributed, collaborative, hypermedia information
198   systems. HTTP has been in use by the World Wide Web global information
199   initiative since 1990. This document is Part 3 of the seven-part specification
200   that defines the protocol referred to as "HTTP/1.1" and, taken together,
201   obsoletes RFC 2616.  Part 3 defines HTTP message content,
202   metadata, and content negotiation.
203</t>
204</abstract>
205
206<note title="Editorial Note (To be removed by RFC Editor)">
207  <t>
208    Discussion of this draft should take place on the HTTPBIS working group
209    mailing list (ietf-http-wg@w3.org). The current issues list is
210    at <eref target="http://tools.ietf.org/wg/httpbis/trac/report/11"/>
211    and related documents (including fancy diffs) can be found at
212    <eref target="http://tools.ietf.org/wg/httpbis/"/>.
213  </t>
214  <t>
215    The changes in this draft are summarized in <xref target="changes.since.06"/>.
216  </t>
217</note>
218</front>
219<middle>
220<section title="Introduction" anchor="introduction">
221<t>
222   This document defines HTTP/1.1 message payloads (a.k.a., content), the
223   associated metadata header fields that define how the payload is intended
224   to be interpreted by a recipient, the request header fields that
225   may influence content selection, and the various selection algorithms
226   that are collectively referred to as HTTP content negotiation.
227</t>
228<t>
229   This document is currently disorganized in order to minimize the changes
230   between drafts and enable reviewers to see the smaller errata changes.
231   The next draft will reorganize the sections to better reflect the content.
232   In particular, the sections on entities will be renamed payload and moved
233   to the first half of the document, while the sections on content negotiation
234   and associated request header fields will be moved to the second half.  The
235   current mess reflects how widely dispersed these topics and associated
236   requirements had become in <xref target="RFC2616"/>.
237</t>
238
239<section title="Requirements" anchor="intro.requirements">
240<t>
241   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
242   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
243   document are to be interpreted as described in <xref target="RFC2119"/>.
244</t>
245<t>
246   An implementation is not compliant if it fails to satisfy one or more
247   of the &MUST; or &REQUIRED; level requirements for the protocols it
248   implements. An implementation that satisfies all the &MUST; or &REQUIRED;
249   level and all the &SHOULD; level requirements for its protocols is said
250   to be "unconditionally compliant"; one that satisfies all the &MUST;
251   level requirements but not all the &SHOULD; level requirements for its
252   protocols is said to be "conditionally compliant."
253</t>
254</section>
255
256<section title="Syntax Notation" anchor="notation">
257  <x:anchor-alias value="ALPHA"/>
258  <x:anchor-alias value="CR"/>
259  <x:anchor-alias value="DIGIT"/>
260  <x:anchor-alias value="LF"/>
261  <x:anchor-alias value="OCTET"/>
262  <x:anchor-alias value="VCHAR"/>
263  <x:anchor-alias value="WSP"/>
264<t>
265  This specification uses the ABNF syntax defined in &notation; (which
266  extends the syntax defined in <xref target="RFC5234"/> with a list rule).
267  <xref target="collected.abnf"/> shows the collected ABNF, with the list
268  rule expanded.
269</t>
270<t>
271  The following core rules are included by
272  reference, as defined in <xref target="RFC5234" x:fmt="," x:sec="B.1"/>:
273  ALPHA (letters), CR (carriage return), CRLF (CR LF), CTL (controls),
274  DIGIT (decimal 0-9), DQUOTE (double quote),
275  HEXDIG (hexadecimal 0-9/A-F/a-f), LF (line feed),
276  OCTET (any 8-bit sequence of data), SP (space),
277  VCHAR (any visible USASCII character),
278  and WSP (whitespace).
279</t>
280
281<section title="Core Rules" anchor="core.rules">
282  <x:anchor-alias value="quoted-string"/>
283  <x:anchor-alias value="token"/>
284  <x:anchor-alias value="OWS"/>
285<t>
286  The core rules below are defined in &basic-rules;:
287</t>
288<figure><artwork type="abnf2616">
289  <x:ref>quoted-string</x:ref>  = &lt;quoted-string, defined in &basic-rules;&gt;
290  <x:ref>token</x:ref>          = &lt;token, defined in &basic-rules;&gt;
291  <x:ref>OWS</x:ref>            = &lt;OWS, defined in &basic-rules;&gt;
292</artwork></figure>
293</section>
294
295<section title="ABNF Rules defined in other Parts of the Specification" anchor="abnf.dependencies">
296  <x:anchor-alias value="absolute-URI"/>
297  <x:anchor-alias value="Allow"/>
298  <x:anchor-alias value="Content-Length"/>
299  <x:anchor-alias value="Content-Range"/>
300  <x:anchor-alias value="Expires"/>
301  <x:anchor-alias value="Last-Modified"/>
302  <x:anchor-alias value="message-header"/>
303  <x:anchor-alias value="partial-URI"/>
304  <x:anchor-alias value="qvalue"/>
305<t>
306  The ABNF rules below are defined in other parts:
307</t>
308<figure><!--Part1--><artwork type="abnf2616">
309  <x:ref>absolute-URI</x:ref>   = &lt;absolute-URI, defined in &uri;&gt;
310  <x:ref>Content-Length</x:ref> = &lt;Content-Length, defined in &header-content-length;&gt;
311  <x:ref>message-header</x:ref> = &lt;message-header, defined in &message-headers;&gt;
312  <x:ref>partial-URI</x:ref>    = &lt;partial-URI, defined in &uri;&gt;
313  <x:ref>qvalue</x:ref>         = &lt;qvalue, defined in &qvalue;&gt;
314</artwork></figure>
315<figure><!--Part4--><artwork type="abnf2616">
316  <x:ref>Last-Modified</x:ref>  = &lt;Last-Modified, defined in &header-last-modified;&gt;
317</artwork></figure>
318<figure><!--Part5--><artwork type="abnf2616">
319  <x:ref>Content-Range</x:ref>  = &lt;Content-Range, defined in &header-content-range;&gt;
320</artwork></figure>
321<figure><!--Part6--><artwork type="abnf2616">
322  <x:ref>Expires</x:ref>        = &lt;Expires, defined in &header-expires;&gt;
323</artwork></figure>
324</section>
325
326</section>
327
328</section>
329
330<section title="Protocol Parameters" anchor="protocol.parameters">
331
332<section title="Character Sets" anchor="character.sets">
333<t>
334   HTTP uses the same definition of the term "character set" as that
335   described for MIME:
336</t>
337<t>
338   The term "character set" is used in this document to refer to a
339   method used with one or more tables to convert a sequence of octets
340   into a sequence of characters. Note that unconditional conversion in
341   the other direction is not required, in that not all characters may
342   be available in a given character set and a character set may provide
343   more than one sequence of octets to represent a particular character.
344   This definition is intended to allow various kinds of character
345   encoding, from simple single-table mappings such as US-ASCII to
346   complex table switching methods such as those that use ISO-2022's
347   techniques. However, the definition associated with a MIME character
348   set name &MUST; fully specify the mapping to be performed from octets
349   to characters. In particular, use of external profiling information
350   to determine the exact mapping is not permitted.
351</t>
352<x:note>
353  <t>
354    <x:h>Note:</x:h> This use of the term "character set" is more commonly
355    referred to as a "character encoding." However, since HTTP and
356    MIME share the same registry, it is important that the terminology
357    also be shared.
358  </t>
359</x:note>
360<t anchor="rule.charset">
361  <x:anchor-alias value="charset"/>
362   HTTP character sets are identified by case-insensitive tokens. The
363   complete set of tokens is defined by the IANA Character Set registry
364   (<eref target="http://www.iana.org/assignments/character-sets"/>).
365</t>
366<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="charset"/>
367  <x:ref>charset</x:ref> = <x:ref>token</x:ref>
368</artwork></figure>
369<t>
370   Although HTTP allows an arbitrary token to be used as a charset
371   value, any token that has a predefined value within the IANA
372   Character Set registry &MUST; represent the character set defined
373   by that registry. Applications &SHOULD; limit their use of character
374   sets to those defined by the IANA registry.
375</t>
376<t>
377   HTTP uses charset in two contexts: within an Accept-Charset request
378   header (in which the charset value is an unquoted token) and as the
379   value of a parameter in a Content-Type header (within a request or
380   response), in which case the parameter value of the charset parameter
381   may be quoted.
382</t>
383<t>
384   Implementors should be aware of IETF character set requirements <xref target="RFC3629"/>
385   <xref target="RFC2277"/>.
386</t>
387
388<section title="Missing Charset" anchor="missing.charset">
389<t>
390   Some HTTP/1.0 software has interpreted a Content-Type header without
391   charset parameter incorrectly to mean "recipient should guess."
392   Senders wishing to defeat this behavior &MAY; include a charset
393   parameter even when the charset is ISO-8859-1 (<xref target="ISO-8859-1"/>) and &SHOULD; do so when
394   it is known that it will not confuse the recipient.
395</t>
396<t>
397   Unfortunately, some older HTTP/1.0 clients did not deal properly with
398   an explicit charset parameter. HTTP/1.1 recipients &MUST; respect the
399   charset label provided by the sender; and those user agents that have
400   a provision to "guess" a charset &MUST; use the charset from the
401   content-type field if they support that charset, rather than the
402   recipient's preference, when initially displaying a document. See
403   <xref target="canonicalization.and.text.defaults"/>.
404</t>
405</section>
406</section>
407
408<section title="Content Codings" anchor="content.codings">
409  <x:anchor-alias value="content-coding"/>
410<t>
411   Content coding values indicate an encoding transformation that has
412   been or can be applied to an entity. Content codings are primarily
413   used to allow a document to be compressed or otherwise usefully
414   transformed without losing the identity of its underlying media type
415   and without loss of information. Frequently, the entity is stored in
416   coded form, transmitted directly, and only decoded by the recipient.
417</t>
418<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="content-coding"/>
419  <x:ref>content-coding</x:ref>   = <x:ref>token</x:ref>
420</artwork></figure>
421<t>
422   All content-coding values are case-insensitive. HTTP/1.1 uses
423   content-coding values in the Accept-Encoding (<xref target="header.accept-encoding"/>) and
424   Content-Encoding (<xref target="header.content-encoding"/>) header fields. Although the value
425   describes the content-coding, what is more important is that it
426   indicates what decoding mechanism will be required to remove the
427   encoding.
428</t>
429<t>
430   The Internet Assigned Numbers Authority (IANA) acts as a registry for
431   content-coding value tokens. Initially, the registry contains the
432   following tokens:
433</t>
434<t>
435   gzip<iref item="gzip"/>
436  <list>
437    <t>
438        An encoding format produced by the file compression program
439        "gzip" (GNU zip) as described in <xref target="RFC1952"/>. This format is a
440        Lempel-Ziv coding (LZ77) with a 32 bit CRC.
441    </t>
442  </list>
443</t>
444<t>
445   compress<iref item="compress"/>
446  <list><t>
447        The encoding format produced by the common UNIX file compression
448        program "compress". This format is an adaptive Lempel-Ziv-Welch
449        coding (LZW).
450</t><t>
451        Use of program names for the identification of encoding formats
452        is not desirable and is discouraged for future encodings. Their
453        use here is representative of historical practice, not good
454        design. For compatibility with previous implementations of HTTP,
455        applications &SHOULD; consider "x-gzip" and "x-compress" to be
456        equivalent to "gzip" and "compress" respectively.
457  </t></list>
458</t>
459<t>
460   deflate<iref item="deflate"/>
461  <list><t>
462        The "zlib" format defined in <xref target="RFC1950"/> in combination with
463        the "deflate" compression mechanism described in <xref target="RFC1951"/>.
464  </t></list>
465</t>
466<t>
467   identity<iref item="identity"/>
468  <list><t>
469        The default (identity) encoding; the use of no transformation
470        whatsoever. This content-coding is used only in the Accept-Encoding
471        header, and &SHOULD-NOT;  be used in the Content-Encoding
472        header.
473  </t></list>
474</t>
475<t>
476   New content-coding value tokens &SHOULD; be registered; to allow
477   interoperability between clients and servers, specifications of the
478   content coding algorithms needed to implement a new value &SHOULD; be
479   publicly available and adequate for independent implementation, and
480   conform to the purpose of content coding defined in this section.
481</t>
482</section>
483
484<section title="Media Types" anchor="media.types">
485  <x:anchor-alias value="media-type"/>
486  <x:anchor-alias value="type"/>
487  <x:anchor-alias value="subtype"/>
488<t>
489   HTTP uses Internet Media Types <xref target="RFC2046"/> in the Content-Type (<xref target="header.content-type"/>)
490   and Accept (<xref target="header.accept"/>) header fields in order to provide
491   open and extensible data typing and type negotiation.
492</t>
493<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"/>
494  <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> )
495  <x:ref>type</x:ref>       = <x:ref>token</x:ref>
496  <x:ref>subtype</x:ref>    = <x:ref>token</x:ref>
497</artwork></figure>
498<t anchor="rule.parameter">
499  <x:anchor-alias value="attribute"/>
500  <x:anchor-alias value="parameter"/>
501  <x:anchor-alias value="value"/>
502   Parameters &MAY; follow the type/subtype in the form of attribute/value
503   pairs.
504</t>
505<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"/>
506  <x:ref>parameter</x:ref>      = <x:ref>attribute</x:ref> "=" <x:ref>value</x:ref>
507  <x:ref>attribute</x:ref>      = <x:ref>token</x:ref>
508  <x:ref>value</x:ref>          = <x:ref>token</x:ref> / <x:ref>quoted-string</x:ref>
509</artwork></figure>
510<t>
511   The type, subtype, and parameter attribute names are case-insensitive.
512   Parameter values might or might not be case-sensitive, depending on the
513   semantics of the parameter name.  The presence or absence of a parameter might
514   be significant to the processing of a media-type, depending on its
515   definition within the media type registry.
516</t>
517<t>
518   A parameter value that matches the <x:ref>token</x:ref> production may be
519   transmitted as either a token or within a quoted-string. The quoted and
520   unquoted values are equivalent.
521</t>
522<t>
523   Note that some older HTTP applications do not recognize media type
524   parameters. When sending data to older HTTP applications,
525   implementations &SHOULD; only use media type parameters when they are
526   required by that type/subtype definition.
527</t>
528<t>
529   Media-type values are registered with the Internet Assigned Number
530   Authority (IANA). The media type registration process is
531   outlined in <xref target="RFC4288"/>. Use of non-registered media types is
532   discouraged.
533</t>
534
535<section title="Canonicalization and Text Defaults" anchor="canonicalization.and.text.defaults">
536<t>
537   Internet media types are registered with a canonical form. An
538   entity-body transferred via HTTP messages &MUST; be represented in the
539   appropriate canonical form prior to its transmission except for
540   "text" types, as defined in the next paragraph.
541</t>
542<t>
543   When in canonical form, media subtypes of the "text" type use CRLF as
544   the text line break. HTTP relaxes this requirement and allows the
545   transport of text media with plain CR or LF alone representing a line
546   break when it is done consistently for an entire entity-body. HTTP
547   applications &MUST; accept CRLF, bare CR, and bare LF as being
548   representative of a line break in text media received via HTTP. In
549   addition, if the text is represented in a character set that does not
550   use octets 13 and 10 for CR and LF respectively, as is the case for
551   some multi-byte character sets, HTTP allows the use of whatever octet
552   sequences are defined by that character set to represent the
553   equivalent of CR and LF for line breaks. This flexibility regarding
554   line breaks applies only to text media in the entity-body; a bare CR
555   or LF &MUST-NOT; be substituted for CRLF within any of the HTTP control
556   structures (such as header fields and multipart boundaries).
557</t>
558<t>
559   If an entity-body is encoded with a content-coding, the underlying
560   data &MUST; be in a form defined above prior to being encoded.
561</t>
562<t>
563   The "charset" parameter is used with some media types to define the
564   character set (<xref target="character.sets"/>) of the data. When no explicit charset
565   parameter is provided by the sender, media subtypes of the "text"
566   type are defined to have a default charset value of "ISO-8859-1" when
567   received via HTTP. Data in character sets other than "ISO-8859-1" or
568   its subsets &MUST; be labeled with an appropriate charset value. See
569   <xref target="missing.charset"/> for compatibility problems.
570</t>
571</section>
572
573<section title="Multipart Types" anchor="multipart.types">
574<t>
575   MIME provides for a number of "multipart" types -- encapsulations of
576   one or more entities within a single message-body. All multipart
577   types share a common syntax, as defined in <xref target="RFC2046" x:sec="5.1.1" x:fmt="of"/>,
578   and &MUST; include a boundary parameter as part of the media type
579   value. The message body is itself a protocol element and &MUST;
580   therefore use only CRLF to represent line breaks between body-parts.
581   Unlike in RFC 2046, the epilogue of any multipart message &MUST; be
582   empty; HTTP applications &MUST-NOT; transmit the epilogue (even if the
583   original multipart contains an epilogue). These restrictions exist in
584   order to preserve the self-delimiting nature of a multipart message-body,
585   wherein the "end" of the message-body is indicated by the
586   ending multipart boundary.
587</t>
588<t>
589   In general, HTTP treats a multipart message-body no differently than
590   any other media type: strictly as payload. The one exception is the
591   "multipart/byteranges" type (&multipart-byteranges;) when it appears in a 206
592   (Partial Content) response.
593   <!-- jre: re-insert removed text pointing to caching? -->
594   In all
595   other cases, an HTTP user agent &SHOULD; follow the same or similar
596   behavior as a MIME user agent would upon receipt of a multipart type.
597   The MIME header fields within each body-part of a multipart message-body
598   do not have any significance to HTTP beyond that defined by
599   their MIME semantics.
600</t>
601<t>
602   In general, an HTTP user agent &SHOULD; follow the same or similar
603   behavior as a MIME user agent would upon receipt of a multipart type.
604   If an application receives an unrecognized multipart subtype, the
605   application &MUST; treat it as being equivalent to "multipart/mixed".
606</t>
607<x:note>
608  <t>
609    <x:h>Note:</x:h> The "multipart/form-data" type has been specifically defined
610    for carrying form data suitable for processing via the POST
611    request method, as described in <xref target="RFC2388"/>.
612  </t>
613</x:note>
614</section>
615</section>
616
617<section title="Language Tags" anchor="language.tags">
618  <x:anchor-alias value="language-tag"/>
619  <x:anchor-alias value="primary-tag"/>
620  <x:anchor-alias value="subtag"/>
621<t>
622   A language tag identifies a natural language spoken, written, or
623   otherwise conveyed by human beings for communication of information
624   to other human beings. Computer languages are explicitly excluded.
625   HTTP uses language tags within the Accept-Language and Content-Language
626   fields.
627</t>
628<t>
629   The syntax and registry of HTTP language tags is the same as that
630   defined by <xref target="RFC1766"/>. In summary, a language tag is composed of 1
631   or more parts: A primary language tag and a possibly empty series of
632   subtags:
633</t>
634<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="language-tag"/><iref primary="true" item="Grammar" subitem="primary-tag"/><iref primary="true" item="Grammar" subitem="subtag"/>
635  <x:ref>language-tag</x:ref>  = <x:ref>primary-tag</x:ref> *( "-" <x:ref>subtag</x:ref> )
636  <x:ref>primary-tag</x:ref>   = 1*8<x:ref>ALPHA</x:ref>
637  <x:ref>subtag</x:ref>        = 1*8<x:ref>ALPHA</x:ref>
638</artwork></figure>
639<t>
640   White space is not allowed within the tag and all tags are case-insensitive.
641   The name space of language tags is administered by the
642   IANA. Example tags include:
643</t>
644<figure><artwork type="example">
645  en, en-US, en-cockney, i-cherokee, x-pig-latin
646</artwork></figure>
647<t>
648   where any two-letter primary-tag is an ISO-639 language abbreviation
649   and any two-letter initial subtag is an ISO-3166 country code. (The
650   last three tags above are not registered tags; all but the last are
651   examples of tags which could be registered in future.)
652</t>
653</section>
654</section>
655
656<section title="Entity" anchor="entity">
657<t>
658   Request and Response messages &MAY; transfer an entity if not otherwise
659   restricted by the request method or response status code. An entity
660   consists of entity-header fields and an entity-body, although some
661   responses will only include the entity-headers.
662</t>
663<t>
664   In this section, both sender and recipient refer to either the client
665   or the server, depending on who sends and who receives the entity.
666</t>
667
668<section title="Entity Header Fields" anchor="entity.header.fields">
669  <x:anchor-alias value="entity-header"/>
670  <x:anchor-alias value="extension-header"/>
671<t>
672   Entity-header fields define metainformation about the entity-body or,
673   if no body is present, about the resource identified by the request.
674</t>
675<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="entity-header"/><iref primary="true" item="Grammar" subitem="extension-header"/>
676  <x:ref>entity-header</x:ref>  = <x:ref>Content-Encoding</x:ref>         ; <xref target="header.content-encoding"/>
677                 / <x:ref>Content-Language</x:ref>         ; <xref target="header.content-language"/>
678                 / <x:ref>Content-Length</x:ref>           ; &header-content-length;
679                 / <x:ref>Content-Location</x:ref>         ; <xref target="header.content-location"/>
680                 / <x:ref>Content-MD5</x:ref>              ; <xref target="header.content-md5"/>
681                 / <x:ref>Content-Range</x:ref>            ; &header-content-range;
682                 / <x:ref>Content-Type</x:ref>             ; <xref target="header.content-type"/>
683                 / <x:ref>Expires</x:ref>                  ; &header-expires;
684                 / <x:ref>Last-Modified</x:ref>            ; &header-last-modified;
685                 / <x:ref>extension-header</x:ref>
686 
687  <x:ref>extension-header</x:ref> = <x:ref>message-header</x:ref>
688</artwork></figure>
689<t>
690   The extension-header mechanism allows additional entity-header fields
691   to be defined without changing the protocol, but these fields cannot
692   be assumed to be recognizable by the recipient. Unrecognized header
693   fields &SHOULD; be ignored by the recipient and &MUST; be forwarded by
694   transparent proxies.
695</t>
696</section>
697
698<section title="Entity Body" anchor="entity.body">
699  <x:anchor-alias value="entity-body"/>
700<t>
701   The entity-body (if any) sent with an HTTP request or response is in
702   a format and encoding defined by the entity-header fields.
703</t>
704<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="entity-body"/>
705  <x:ref>entity-body</x:ref>    = *<x:ref>OCTET</x:ref>
706</artwork></figure>
707<t>
708   An entity-body is only present in a message when a message-body is
709   present, as described in &message-body;. The entity-body is obtained
710   from the message-body by decoding any Transfer-Encoding that might
711   have been applied to ensure safe and proper transfer of the message.
712</t>
713
714<section title="Type" anchor="type">
715<t>
716   When an entity-body is included with a message, the data type of that
717   body is determined via the header fields Content-Type and Content-Encoding.
718   These define a two-layer, ordered encoding model:
719</t>
720<figure><artwork type="example">
721  entity-body := Content-Encoding( Content-Type( data ) )
722</artwork></figure>
723<t>
724   Content-Type specifies the media type of the underlying data.
725   Content-Encoding may be used to indicate any additional content
726   codings applied to the data, usually for the purpose of data
727   compression, that are a property of the requested resource. There is
728   no default encoding.
729</t>
730<t>
731   Any HTTP/1.1 message containing an entity-body &SHOULD; include a
732   Content-Type header field defining the media type of that body. If
733   and only if the media type is not given by a Content-Type field, the
734   recipient &MAY; attempt to guess the media type via inspection of its
735   content and/or the name extension(s) of the URI used to identify the
736   resource. If the media type remains unknown, the recipient &SHOULD;
737   treat it as type "application/octet-stream" (<xref target="RFC2046" x:fmt="," x:sec="4.5.1"/>).
738</t>
739</section>
740   
741<section title="Entity Length" anchor="entity.length">
742<t>
743   The entity-length of a message is the length of the message-body
744   before any transfer-codings have been applied. &message-length; defines
745   how the transfer-length of a message-body is determined.
746</t>
747</section>
748</section>
749</section>
750
751<section title="Content Negotiation" anchor="content.negotiation">
752<t>
753   Most HTTP responses include an entity which contains information for
754   interpretation by a human user. Naturally, it is desirable to supply
755   the user with the "best available" entity corresponding to the
756   request. Unfortunately for servers and caches, not all users have the
757   same preferences for what is "best," and not all user agents are
758   equally capable of rendering all entity types. For that reason, HTTP
759   has provisions for several mechanisms for "content negotiation" --
760   the process of selecting the best representation for a given response
761   when there are multiple representations available.
762</t>
763<x:note>
764  <t>
765    <x:h>Note:</x:h> This is not called "format negotiation" because the
766    alternate representations may be of the same media type, but use
767    different capabilities of that type, be in different languages,
768    etc.
769  </t>
770</x:note>
771<t>
772   Any response containing an entity-body &MAY; be subject to negotiation,
773   including error responses.
774</t>
775<t>
776   There are two kinds of content negotiation which are possible in
777   HTTP: server-driven and agent-driven negotiation. These two kinds of
778   negotiation are orthogonal and thus may be used separately or in
779   combination. One method of combination, referred to as transparent
780   negotiation, occurs when a cache uses the agent-driven negotiation
781   information provided by the origin server in order to provide
782   server-driven negotiation for subsequent requests.
783</t>
784
785<section title="Server-driven Negotiation" anchor="server-driven.negotiation">
786<t>
787   If the selection of the best representation for a response is made by
788   an algorithm located at the server, it is called server-driven
789   negotiation. Selection is based on the available representations of
790   the response (the dimensions over which it can vary; e.g. language,
791   content-coding, etc.) and the contents of particular header fields in
792   the request message or on other information pertaining to the request
793   (such as the network address of the client).
794</t>
795<t>
796   Server-driven negotiation is advantageous when the algorithm for
797   selecting from among the available representations is difficult to
798   describe to the user agent, or when the server desires to send its
799   "best guess" to the client along with the first response (hoping to
800   avoid the round-trip delay of a subsequent request if the "best
801   guess" is good enough for the user). In order to improve the server's
802   guess, the user agent &MAY; include request header fields (Accept,
803   Accept-Language, Accept-Encoding, etc.) which describe its
804   preferences for such a response.
805</t>
806<t>
807   Server-driven negotiation has disadvantages:
808  <list style="numbers">
809    <t>
810         It is impossible for the server to accurately determine what
811         might be "best" for any given user, since that would require
812         complete knowledge of both the capabilities of the user agent
813         and the intended use for the response (e.g., does the user want
814         to view it on screen or print it on paper?).
815    </t>
816    <t>
817         Having the user agent describe its capabilities in every
818         request can be both very inefficient (given that only a small
819         percentage of responses have multiple representations) and a
820         potential violation of the user's privacy.
821    </t>
822    <t>
823         It complicates the implementation of an origin server and the
824         algorithms for generating responses to a request.
825    </t>
826    <t>
827         It may limit a public cache's ability to use the same response
828         for multiple user's requests.
829    </t>
830  </list>
831</t>
832<t>
833   HTTP/1.1 includes the following request-header fields for enabling
834   server-driven negotiation through description of user agent
835   capabilities and user preferences: Accept (<xref target="header.accept"/>), Accept-Charset
836   (<xref target="header.accept-charset"/>), Accept-Encoding (<xref target="header.accept-encoding"/>), Accept-Language
837   (<xref target="header.accept-language"/>), and User-Agent (&header-user-agent;). However, an
838   origin server is not limited to these dimensions and &MAY; vary the
839   response based on any aspect of the request, including information
840   outside the request-header fields or within extension header fields
841   not defined by this specification.
842</t>
843<t>
844   The Vary header field (&header-vary;) can be used to express the parameters the
845   server uses to select a representation that is subject to server-driven
846   negotiation.
847</t>
848</section>
849
850<section title="Agent-driven Negotiation" anchor="agent-driven.negotiation">
851<t>
852   With agent-driven negotiation, selection of the best representation
853   for a response is performed by the user agent after receiving an
854   initial response from the origin server. Selection is based on a list
855   of the available representations of the response included within the
856   header fields or entity-body of the initial response, with each
857   representation identified by its own URI. Selection from among the
858   representations may be performed automatically (if the user agent is
859   capable of doing so) or manually by the user selecting from a
860   generated (possibly hypertext) menu.
861</t>
862<t>
863   Agent-driven negotiation is advantageous when the response would vary
864   over commonly-used dimensions (such as type, language, or encoding),
865   when the origin server is unable to determine a user agent's
866   capabilities from examining the request, and generally when public
867   caches are used to distribute server load and reduce network usage.
868</t>
869<t>
870   Agent-driven negotiation suffers from the disadvantage of needing a
871   second request to obtain the best alternate representation. This
872   second request is only efficient when caching is used. In addition,
873   this specification does not define any mechanism for supporting
874   automatic selection, though it also does not prevent any such
875   mechanism from being developed as an extension and used within
876   HTTP/1.1.
877</t>
878<t>
879   HTTP/1.1 defines the 300 (Multiple Choices) and 406 (Not Acceptable)
880   status codes for enabling agent-driven negotiation when the server is
881   unwilling or unable to provide a varying response using server-driven
882   negotiation.
883</t>
884</section>
885
886<section title="Transparent Negotiation" anchor="transparent.negotiation">
887<t>
888   Transparent negotiation is a combination of both server-driven and
889   agent-driven negotiation. When a cache is supplied with a form of the
890   list of available representations of the response (as in agent-driven
891   negotiation) and the dimensions of variance are completely understood
892   by the cache, then the cache becomes capable of performing server-driven
893   negotiation on behalf of the origin server for subsequent
894   requests on that resource.
895</t>
896<t>
897   Transparent negotiation has the advantage of distributing the
898   negotiation work that would otherwise be required of the origin
899   server and also removing the second request delay of agent-driven
900   negotiation when the cache is able to correctly guess the right
901   response.
902</t>
903<t>
904   This specification does not define any mechanism for transparent
905   negotiation, though it also does not prevent any such mechanism from
906   being developed as an extension that could be used within HTTP/1.1.
907</t>
908</section>
909</section>
910
911<section title="Header Field Definitions" anchor="header.fields">
912<t>
913   This section defines the syntax and semantics of HTTP/1.1 header fields
914   related to the payload of messages.
915</t>
916<t>
917   For entity-header fields, both sender and recipient refer to either the
918   client or the server, depending on who sends and who receives the entity.
919</t>
920
921<section title="Accept" anchor="header.accept">
922  <iref primary="true" item="Accept header" x:for-anchor=""/>
923  <iref primary="true" item="Headers" subitem="Accept" x:for-anchor=""/>
924  <x:anchor-alias value="Accept"/>
925  <x:anchor-alias value="Accept-v"/>
926  <x:anchor-alias value="accept-ext"/>
927  <x:anchor-alias value="accept-params"/>
928  <x:anchor-alias value="media-range"/>
929<t>
930   The request-header field "Accept" can be used to specify certain media
931   types which are acceptable for the response. Accept headers can be
932   used to indicate that the request is specifically limited to a small
933   set of desired types, as in the case of a request for an in-line
934   image.
935</t>
936<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"/>
937  <x:ref>Accept</x:ref>   = "Accept" ":" <x:ref>OWS</x:ref> <x:ref>Accept-v</x:ref>
938  <x:ref>Accept-v</x:ref> = #( <x:ref>media-range</x:ref> [ <x:ref>accept-params</x:ref> ] )
939 
940  <x:ref>media-range</x:ref>    = ( "*/*"
941                   / ( <x:ref>type</x:ref> "/" "*" )
942                   / ( <x:ref>type</x:ref> "/" <x:ref>subtype</x:ref> )
943                   ) *( <x:ref>OWS</x:ref> ";" <x:ref>OWS</x:ref> <x:ref>parameter</x:ref> )
944  <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> )
945  <x:ref>accept-ext</x:ref>     = <x:ref>OWS</x:ref> ";" <x:ref>OWS</x:ref> <x:ref>token</x:ref>
946                   [ "=" ( <x:ref>token</x:ref> / <x:ref>quoted-string</x:ref> ) ]
947</artwork></figure>
948<t>
949   The asterisk "*" character is used to group media types into ranges,
950   with "*/*" indicating all media types and "type/*" indicating all
951   subtypes of that type. The media-range &MAY; include media type
952   parameters that are applicable to that range.
953</t>
954<t>
955   Each media-range &MAY; be followed by one or more accept-params,
956   beginning with the "q" parameter for indicating a relative quality
957   factor. The first "q" parameter (if any) separates the media-range
958   parameter(s) from the accept-params. Quality factors allow the user
959   or user agent to indicate the relative degree of preference for that
960   media-range, using the qvalue scale from 0 to 1 (&qvalue;). The
961   default value is q=1.
962</t>
963<x:note>
964  <t>
965    <x:h>Note:</x:h> Use of the "q" parameter name to separate media type
966    parameters from Accept extension parameters is due to historical
967    practice. Although this prevents any media type parameter named
968    "q" from being used with a media range, such an event is believed
969    to be unlikely given the lack of any "q" parameters in the IANA
970    media type registry and the rare usage of any media type
971    parameters in Accept. Future media types are discouraged from
972    registering any parameter named "q".
973  </t>
974</x:note>
975<t>
976   The example
977</t>
978<figure><artwork type="example">
979  Accept: audio/*; q=0.2, audio/basic
980</artwork></figure>
981<t>
982   &SHOULD; be interpreted as "I prefer audio/basic, but send me any audio
983   type if it is the best available after an 80% mark-down in quality."
984</t>
985<t>
986   If no Accept header field is present, then it is assumed that the
987   client accepts all media types. If an Accept header field is present,
988   and if the server cannot send a response which is acceptable
989   according to the combined Accept field value, then the server &SHOULD;
990   send a 406 (Not Acceptable) response.
991</t>
992<t>
993   A more elaborate example is
994</t>
995<figure><artwork type="example">
996  Accept: text/plain; q=0.5, text/html,
997          text/x-dvi; q=0.8, text/x-c
998</artwork></figure>
999<t>
1000   Verbally, this would be interpreted as "text/html and text/x-c are
1001   the preferred media types, but if they do not exist, then send the
1002   text/x-dvi entity, and if that does not exist, send the text/plain
1003   entity."
1004</t>
1005<t>
1006   Media ranges can be overridden by more specific media ranges or
1007   specific media types. If more than one media range applies to a given
1008   type, the most specific reference has precedence. For example,
1009</t>
1010<figure><artwork type="example">
1011  Accept: text/*, text/html, text/html;level=1, */*
1012</artwork></figure>
1013<t>
1014   have the following precedence:
1015   <list style="numbers">
1016    <t>text/html;level=1</t>
1017    <t>text/html</t>
1018    <t>text/*</t>
1019    <t>*/*</t>
1020   </list>
1021</t>
1022<t>
1023   The media type quality factor associated with a given type is
1024   determined by finding the media range with the highest precedence
1025   which matches that type. For example,
1026</t>
1027<figure><artwork type="example">
1028  Accept: text/*;q=0.3, text/html;q=0.7, text/html;level=1,
1029          text/html;level=2;q=0.4, */*;q=0.5
1030</artwork></figure>
1031<t>
1032   would cause the following values to be associated:
1033</t>
1034<texttable align="left">
1035  <ttcol>Media Type</ttcol><ttcol>Quality Value</ttcol>
1036  <c>text/html;level=1</c>    <c>1</c>
1037  <c>text/html</c>            <c>0.7</c>
1038  <c>text/plain</c>           <c>0.3</c>
1039  <c>image/jpeg</c>           <c>0.5</c>
1040  <c>text/html;level=2</c>    <c>0.4</c>
1041  <c>text/html;level=3</c>    <c>0.7</c>
1042</texttable>
1043<t>
1044      <x:h>Note:</x:h> A user agent might be provided with a default set of quality
1045      values for certain media ranges. However, unless the user agent is
1046      a closed system which cannot interact with other rendering agents,
1047      this default set ought to be configurable by the user.
1048</t>
1049</section>
1050
1051<section title="Accept-Charset" anchor="header.accept-charset">
1052  <iref primary="true" item="Accept-Charset header" x:for-anchor=""/>
1053  <iref primary="true" item="Headers" subitem="Accept-Charset" x:for-anchor=""/>
1054  <x:anchor-alias value="Accept-Charset"/>
1055  <x:anchor-alias value="Accept-Charset-v"/>
1056<t>
1057   The request-header field "Accept-Charset" can be used to indicate what
1058   character sets are acceptable for the response. This field allows
1059   clients capable of understanding more comprehensive or special-purpose
1060   character sets to signal that capability to a server which is
1061   capable of representing documents in those character sets.
1062</t>
1063<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Accept-Charset"/><iref primary="true" item="Grammar" subitem="Accept-Charset-v"/>
1064  <x:ref>Accept-Charset</x:ref>   = "Accept-Charset" ":" <x:ref>OWS</x:ref>
1065          <x:ref>Accept-Charset-v</x:ref>
1066  <x:ref>Accept-Charset-v</x:ref> = 1#( ( <x:ref>charset</x:ref> / "*" )
1067                         [ <x:ref>OWS</x:ref> ";" <x:ref>OWS</x:ref> "q=" <x:ref>qvalue</x:ref> ] )
1068</artwork></figure>
1069<t>
1070   Character set values are described in <xref target="character.sets"/>. Each charset &MAY;
1071   be given an associated quality value which represents the user's
1072   preference for that charset. The default value is q=1. An example is
1073</t>
1074<figure><artwork type="example">
1075  Accept-Charset: iso-8859-5, unicode-1-1;q=0.8
1076</artwork></figure>
1077<t>
1078   The special value "*", if present in the Accept-Charset field,
1079   matches every character set (including ISO-8859-1) which is not
1080   mentioned elsewhere in the Accept-Charset field. If no "*" is present
1081   in an Accept-Charset field, then all character sets not explicitly
1082   mentioned get a quality value of 0, except for ISO-8859-1, which gets
1083   a quality value of 1 if not explicitly mentioned.
1084</t>
1085<t>
1086   If no Accept-Charset header is present, the default is that any
1087   character set is acceptable. If an Accept-Charset header is present,
1088   and if the server cannot send a response which is acceptable
1089   according to the Accept-Charset header, then the server &SHOULD; send
1090   an error response with the 406 (Not Acceptable) status code, though
1091   the sending of an unacceptable response is also allowed.
1092</t>
1093</section>
1094
1095<section title="Accept-Encoding" anchor="header.accept-encoding">
1096  <iref primary="true" item="Accept-Encoding header" x:for-anchor=""/>
1097  <iref primary="true" item="Headers" subitem="Accept-Encoding" x:for-anchor=""/>
1098  <x:anchor-alias value="Accept-Encoding"/>
1099  <x:anchor-alias value="Accept-Encoding-v"/>
1100  <x:anchor-alias value="codings"/>
1101<t>
1102   The request-header field "Accept-Encoding" is similar to Accept, but
1103   restricts the content-codings (<xref target="content.codings"/>) that are acceptable in
1104   the response.
1105</t>
1106<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"/>
1107  <x:ref>Accept-Encoding</x:ref>    = "Accept-Encoding" ":" <x:ref>OWS</x:ref>
1108                     <x:ref>Accept-Encoding-v</x:ref>
1109  <x:ref>Accept-Encoding-v</x:ref>  =
1110                     #( <x:ref>codings</x:ref> [ <x:ref>OWS</x:ref> ";" <x:ref>OWS</x:ref> "q=" <x:ref>qvalue</x:ref> ] )
1111  <x:ref>codings</x:ref>            = ( <x:ref>content-coding</x:ref> / "*" )
1112</artwork></figure>
1113<t>
1114   Each codings value &MAY; be given an associated quality value which
1115   represents the preference for that encoding. The default value is q=1.
1116</t>
1117<t>
1118   Examples of its use are:
1119</t>
1120<figure><artwork type="example">
1121  Accept-Encoding: compress, gzip
1122  Accept-Encoding:
1123  Accept-Encoding: *
1124  Accept-Encoding: compress;q=0.5, gzip;q=1.0
1125  Accept-Encoding: gzip;q=1.0, identity; q=0.5, *;q=0
1126</artwork></figure>
1127<t>
1128   A server tests whether a content-coding is acceptable, according to
1129   an Accept-Encoding field, using these rules:
1130  <list style="numbers">
1131      <t>If the content-coding is one of the content-codings listed in
1132         the Accept-Encoding field, then it is acceptable, unless it is
1133         accompanied by a qvalue of 0. (As defined in &qvalue;, a
1134         qvalue of 0 means "not acceptable.")</t>
1135
1136      <t>The special "*" symbol in an Accept-Encoding field matches any
1137         available content-coding not explicitly listed in the header
1138         field.</t>
1139
1140      <t>If multiple content-codings are acceptable, then the acceptable
1141         content-coding with the highest non-zero qvalue is preferred.</t>
1142
1143      <t>The "identity" content-coding is always acceptable, unless
1144         specifically refused because the Accept-Encoding field includes
1145         "identity;q=0", or because the field includes "*;q=0" and does
1146         not explicitly include the "identity" content-coding. If the
1147         Accept-Encoding field-value is empty, then only the "identity"
1148         encoding is acceptable.</t>
1149  </list>
1150</t>
1151<t>
1152   If an Accept-Encoding field is present in a request, and if the
1153   server cannot send a response which is acceptable according to the
1154   Accept-Encoding header, then the server &SHOULD; send an error response
1155   with the 406 (Not Acceptable) status code.
1156</t>
1157<t>
1158   If no Accept-Encoding field is present in a request, the server &MAY;
1159   assume that the client will accept any content coding. In this case,
1160   if "identity" is one of the available content-codings, then the
1161   server &SHOULD; use the "identity" content-coding, unless it has
1162   additional information that a different content-coding is meaningful
1163   to the client.
1164</t>
1165<x:note>
1166  <t>
1167    <x:h>Note:</x:h> If the request does not include an Accept-Encoding field,
1168    and if the "identity" content-coding is unavailable, then
1169    content-codings commonly understood by HTTP/1.0 clients (i.e.,
1170    "gzip" and "compress") are preferred; some older clients
1171    improperly display messages sent with other content-codings.  The
1172    server might also make this decision based on information about
1173    the particular user-agent or client.
1174  </t>
1175</x:note>
1176<x:note>
1177  <t>
1178    <x:h>Note:</x:h> Most HTTP/1.0 applications do not recognize or obey qvalues
1179    associated with content-codings. This means that qvalues will not
1180    work and are not permitted with x-gzip or x-compress.
1181  </t>
1182</x:note>
1183</section>
1184
1185<section title="Accept-Language" anchor="header.accept-language">
1186  <iref primary="true" item="Accept-Language header" x:for-anchor=""/>
1187  <iref primary="true" item="Headers" subitem="Accept-Language" x:for-anchor=""/>
1188  <x:anchor-alias value="Accept-Language"/>
1189  <x:anchor-alias value="Accept-Language-v"/>
1190  <x:anchor-alias value="language-range"/>
1191<t>
1192   The request-header field "Accept-Language" is similar to Accept, but
1193   restricts the set of natural languages that are preferred as a
1194   response to the request. Language tags are defined in <xref target="language.tags"/>.
1195</t>
1196<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"/>
1197  <x:ref>Accept-Language</x:ref>   = "Accept-Language" ":" <x:ref>OWS</x:ref>
1198                    <x:ref>Accept-Language-v</x:ref>
1199  <x:ref>Accept-Language-v</x:ref> =
1200                    1#( <x:ref>language-range</x:ref> [ <x:ref>OWS</x:ref> ";" <x:ref>OWS</x:ref> "q=" <x:ref>qvalue</x:ref> ] )
1201  <x:ref>language-range</x:ref>    =
1202            &lt;language-range, defined in <xref target="RFC4647" x:fmt="," x:sec="2.1"/>&gt;
1203</artwork></figure>
1204<t>
1205   Each language-range can be given an associated quality value which
1206   represents an estimate of the user's preference for the languages
1207   specified by that range. The quality value defaults to "q=1". For
1208   example,
1209</t>
1210<figure><artwork type="example">
1211  Accept-Language: da, en-gb;q=0.8, en;q=0.7
1212</artwork></figure>
1213<t>
1214   would mean: "I prefer Danish, but will accept British English and
1215   other types of English."
1216</t>
1217<t>
1218   For matching, the "Basic Filtering" matching scheme, defined in
1219   <xref target="RFC4647" x:sec="3.3.1" x:fmt="of"/>, is used:
1220</t>
1221<x:blockquote cite="http://tools.ietf.org/html/rfc4647#section-3.3.1">
1222  <t>
1223     A language range matches a
1224     particular language tag if, in a case-insensitive comparison, it
1225     exactly equals the tag, or if it exactly equals a prefix of the tag
1226     such that the first character following the prefix is "-".
1227  </t>
1228</x:blockquote> 
1229<t>
1230   The special range "*", if present in the Accept-Language field,
1231   matches every tag not matched by any other range present in the
1232   Accept-Language field.
1233</t>
1234<x:note>
1235  <t>
1236    <x:h>Note:</x:h> This use of a prefix matching rule does not imply that
1237    language tags are assigned to languages in such a way that it is
1238    always true that if a user understands a language with a certain
1239    tag, then this user will also understand all languages with tags
1240    for which this tag is a prefix. The prefix rule simply allows the
1241    use of prefix tags if this is the case.
1242  </t>
1243</x:note>
1244<t>
1245   The language quality factor assigned to a language-tag by the
1246   Accept-Language field is the quality value of the longest language-range
1247   in the field that matches the language-tag. If no language-range
1248   in the field matches the tag, the language quality factor
1249   assigned is 0. If no Accept-Language header is present in the
1250   request, the server
1251   &SHOULD; assume that all languages are equally acceptable. If an
1252   Accept-Language header is present, then all languages which are
1253   assigned a quality factor greater than 0 are acceptable.
1254</t>
1255<t>
1256   It might be contrary to the privacy expectations of the user to send
1257   an Accept-Language header with the complete linguistic preferences of
1258   the user in every request. For a discussion of this issue, see
1259   <xref target="privacy.issues.connected.to.accept.headers"/>.
1260</t>
1261<t>
1262   As intelligibility is highly dependent on the individual user, it is
1263   recommended that client applications make the choice of linguistic
1264   preference available to the user. If the choice is not made
1265   available, then the Accept-Language header field &MUST-NOT; be given in
1266   the request.
1267</t>
1268<x:note>
1269  <t>
1270    <x:h>Note:</x:h> When making the choice of linguistic preference available to
1271    the user, we remind implementors of  the fact that users are not
1272    familiar with the details of language matching as described above,
1273    and should provide appropriate guidance. As an example, users
1274    might assume that on selecting "en-gb", they will be served any
1275    kind of English document if British English is not available. A
1276    user agent might suggest in such a case to add "en" to get the
1277    best matching behavior.
1278  </t>
1279</x:note>
1280</section>
1281
1282<section title="Content-Encoding" anchor="header.content-encoding">
1283  <iref primary="true" item="Content-Encoding header" x:for-anchor=""/>
1284  <iref primary="true" item="Headers" subitem="Content-Encoding" x:for-anchor=""/>
1285  <x:anchor-alias value="Content-Encoding"/>
1286  <x:anchor-alias value="Content-Encoding-v"/>
1287<t>
1288   The entity-header field "Content-Encoding" is used as a modifier to the
1289   media-type. When present, its value indicates what additional content
1290   codings have been applied to the entity-body, and thus what decoding
1291   mechanisms must be applied in order to obtain the media-type
1292   referenced by the Content-Type header field. Content-Encoding is
1293   primarily used to allow a document to be compressed without losing
1294   the identity of its underlying media type.
1295</t>
1296<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Content-Encoding"/><iref primary="true" item="Grammar" subitem="Content-Encoding-v"/>
1297  <x:ref>Content-Encoding</x:ref>   = "Content-Encoding" ":" <x:ref>OWS</x:ref> <x:ref>Content-Encoding-v</x:ref>
1298  <x:ref>Content-Encoding-v</x:ref> = 1#<x:ref>content-coding</x:ref>
1299</artwork></figure>
1300<t>
1301   Content codings are defined in <xref target="content.codings"/>. An example of its use is
1302</t>
1303<figure><artwork type="example">
1304  Content-Encoding: gzip
1305</artwork></figure>
1306<t>
1307   The content-coding is a characteristic of the entity identified by
1308   the request-target. Typically, the entity-body is stored with this
1309   encoding and is only decoded before rendering or analogous usage.
1310   However, a non-transparent proxy &MAY; modify the content-coding if the
1311   new coding is known to be acceptable to the recipient, unless the
1312   "no-transform" cache-control directive is present in the message.
1313</t>
1314<t>
1315   If the content-coding of an entity is not "identity", then the
1316   response &MUST; include a Content-Encoding entity-header (<xref target="header.content-encoding"/>)
1317   that lists the non-identity content-coding(s) used.
1318</t>
1319<t>
1320   If the content-coding of an entity in a request message is not
1321   acceptable to the origin server, the server &SHOULD; respond with a
1322   status code of 415 (Unsupported Media Type).
1323</t>
1324<t>
1325   If multiple encodings have been applied to an entity, the content
1326   codings &MUST; be listed in the order in which they were applied.
1327   Additional information about the encoding parameters &MAY; be provided
1328   by other entity-header fields not defined by this specification.
1329</t>
1330</section>
1331
1332<section title="Content-Language" anchor="header.content-language">
1333  <iref primary="true" item="Content-Language header" x:for-anchor=""/>
1334  <iref primary="true" item="Headers" subitem="Content-Language" x:for-anchor=""/>
1335  <x:anchor-alias value="Content-Language"/>
1336  <x:anchor-alias value="Content-Language-v"/>
1337<t>
1338   The entity-header field "Content-Language" describes the natural
1339   language(s) of the intended audience for the enclosed entity. Note
1340   that this might not be equivalent to all the languages used within
1341   the entity-body.
1342</t>
1343<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Content-Language"/><iref primary="true" item="Grammar" subitem="Content-Language-v"/>
1344  <x:ref>Content-Language</x:ref>   = "Content-Language" ":" <x:ref>OWS</x:ref> <x:ref>Content-Language-v</x:ref>
1345  <x:ref>Content-Language-v</x:ref> = 1#<x:ref>language-tag</x:ref>
1346</artwork></figure>
1347<t>
1348   Language tags are defined in <xref target="language.tags"/>. The primary purpose of
1349   Content-Language is to allow a user to identify and differentiate
1350   entities according to the user's own preferred language. Thus, if the
1351   body content is intended only for a Danish-literate audience, the
1352   appropriate field is
1353</t>
1354<figure><artwork type="example">
1355  Content-Language: da
1356</artwork></figure>
1357<t>
1358   If no Content-Language is specified, the default is that the content
1359   is intended for all language audiences. This might mean that the
1360   sender does not consider it to be specific to any natural language,
1361   or that the sender does not know for which language it is intended.
1362</t>
1363<t>
1364   Multiple languages &MAY; be listed for content that is intended for
1365   multiple audiences. For example, a rendition of the "Treaty of
1366   Waitangi," presented simultaneously in the original Maori and English
1367   versions, would call for
1368</t>
1369<figure><artwork type="example">
1370  Content-Language: mi, en
1371</artwork></figure>
1372<t>
1373   However, just because multiple languages are present within an entity
1374   does not mean that it is intended for multiple linguistic audiences.
1375   An example would be a beginner's language primer, such as "A First
1376   Lesson in Latin," which is clearly intended to be used by an
1377   English-literate audience. In this case, the Content-Language would
1378   properly only include "en".
1379</t>
1380<t>
1381   Content-Language &MAY; be applied to any media type -- it is not
1382   limited to textual documents.
1383</t>
1384</section>
1385
1386<section title="Content-Location" anchor="header.content-location">
1387  <iref primary="true" item="Content-Location header" x:for-anchor=""/>
1388  <iref primary="true" item="Headers" subitem="Content-Location" x:for-anchor=""/>
1389  <x:anchor-alias value="Content-Location"/>
1390  <x:anchor-alias value="Content-Location-v"/>
1391<t>
1392   The entity-header field "Content-Location" &MAY; be used to supply the
1393   resource location for the entity enclosed in the message when that
1394   entity is accessible from a location separate from the requested
1395   resource's URI. A server &SHOULD; provide a Content-Location for the
1396   variant corresponding to the response entity; especially in the case
1397   where a resource has multiple entities associated with it, and those
1398   entities actually have separate locations by which they might be
1399   individually accessed, the server &SHOULD; provide a Content-Location
1400   for the particular variant which is returned.
1401</t>
1402<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Content-Location"/><iref primary="true" item="Grammar" subitem="Content-Location-v"/>
1403  <x:ref>Content-Location</x:ref>   = "Content-Location" ":" <x:ref>OWS</x:ref>
1404                    <x:ref>Content-Location-v</x:ref>
1405  <x:ref>Content-Location-v</x:ref> =
1406                    <x:ref>absolute-URI</x:ref> / <x:ref>partial-URI</x:ref>
1407</artwork></figure>
1408<t>
1409   The value of Content-Location also defines the base URI for the
1410   entity.
1411</t>
1412<t>
1413   The Content-Location value is not a replacement for the original
1414   requested URI; it is only a statement of the location of the resource
1415   corresponding to this particular entity at the time of the request.
1416   Future requests &MAY; specify the Content-Location URI as the request-target
1417   if the desire is to identify the source of that particular
1418   entity.
1419</t>
1420<t>
1421   A cache cannot assume that an entity with a Content-Location
1422   different from the URI used to retrieve it can be used to respond to
1423   later requests on that Content-Location URI. However, the Content-Location
1424   can be used to differentiate between multiple entities
1425   retrieved from a single requested resource, as described in &caching-neg-resp;.
1426</t>
1427<t>
1428   If the Content-Location is a relative URI, the relative URI is
1429   interpreted relative to the request-target.
1430</t>
1431<t>
1432   The meaning of the Content-Location header in requests is
1433   undefined; servers are free to ignore it in those cases.
1434</t>
1435</section>
1436
1437<section title="Content-MD5" anchor="header.content-md5">
1438  <iref primary="true" item="Content-MD5 header" x:for-anchor=""/>
1439  <iref primary="true" item="Headers" subitem="Content-MD5" x:for-anchor=""/>
1440  <x:anchor-alias value="Content-MD5"/>
1441  <x:anchor-alias value="Content-MD5-v"/>
1442<t>
1443   The entity-header field "Content-MD5", as defined in <xref target="RFC1864"/>, is
1444   an MD5 digest of the entity-body for the purpose of providing an
1445   end-to-end message integrity check (MIC) of the entity-body. (Note: a
1446   MIC is good for detecting accidental modification of the entity-body
1447   in transit, but is not proof against malicious attacks.)
1448</t>
1449<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Content-MD5"/><iref primary="true" item="Grammar" subitem="Content-MD5-v"/>
1450  <x:ref>Content-MD5</x:ref>   = "Content-MD5" ":" <x:ref>OWS</x:ref> <x:ref>Content-MD5-v</x:ref>
1451  <x:ref>Content-MD5-v</x:ref> = &lt;base64 of 128 bit MD5 digest as per <xref target="RFC1864"/>&gt;
1452</artwork></figure>
1453<t>
1454   The Content-MD5 header field &MAY; be generated by an origin server or
1455   client to function as an integrity check of the entity-body. Only
1456   origin servers or clients &MAY; generate the Content-MD5 header field;
1457   proxies and gateways &MUST-NOT; generate it, as this would defeat its
1458   value as an end-to-end integrity check. Any recipient of the entity-body,
1459   including gateways and proxies, &MAY; check that the digest value
1460   in this header field matches that of the entity-body as received.
1461</t>
1462<t>
1463   The MD5 digest is computed based on the content of the entity-body,
1464   including any content-coding that has been applied, but not including
1465   any transfer-encoding applied to the message-body. If the message is
1466   received with a transfer-encoding, that encoding &MUST; be removed
1467   prior to checking the Content-MD5 value against the received entity.
1468</t>
1469<t>
1470   This has the result that the digest is computed on the octets of the
1471   entity-body exactly as, and in the order that, they would be sent if
1472   no transfer-encoding were being applied.
1473</t>
1474<t>
1475   HTTP extends RFC 1864 to permit the digest to be computed for MIME
1476   composite media-types (e.g., multipart/* and message/rfc822), but
1477   this does not change how the digest is computed as defined in the
1478   preceding paragraph.
1479</t>
1480<t>
1481   There are several consequences of this. The entity-body for composite
1482   types &MAY; contain many body-parts, each with its own MIME and HTTP
1483   headers (including Content-MD5, Content-Transfer-Encoding, and
1484   Content-Encoding headers). If a body-part has a Content-Transfer-Encoding
1485   or Content-Encoding header, it is assumed that the content
1486   of the body-part has had the encoding applied, and the body-part is
1487   included in the Content-MD5 digest as is -- i.e., after the
1488   application. The Transfer-Encoding header field is not allowed within
1489   body-parts.
1490</t>
1491<t>
1492   Conversion of all line breaks to CRLF &MUST-NOT; be done before
1493   computing or checking the digest: the line break convention used in
1494   the text actually transmitted &MUST; be left unaltered when computing
1495   the digest.
1496</t>
1497<x:note>
1498  <t>
1499    <x:h>Note:</x:h> while the definition of Content-MD5 is exactly the same for
1500    HTTP as in RFC 1864 for MIME entity-bodies, there are several ways
1501    in which the application of Content-MD5 to HTTP entity-bodies
1502    differs from its application to MIME entity-bodies. One is that
1503    HTTP, unlike MIME, does not use Content-Transfer-Encoding, and
1504    does use Transfer-Encoding and Content-Encoding. Another is that
1505    HTTP more frequently uses binary content types than MIME, so it is
1506    worth noting that, in such cases, the byte order used to compute
1507    the digest is the transmission byte order defined for the type.
1508    Lastly, HTTP allows transmission of text types with any of several
1509    line break conventions and not just the canonical form using CRLF.
1510  </t>
1511</x:note>
1512</section>
1513
1514<section title="Content-Type" anchor="header.content-type">
1515  <iref primary="true" item="Content-Type header" x:for-anchor=""/>
1516  <iref primary="true" item="Headers" subitem="Content-Type" x:for-anchor=""/>
1517  <x:anchor-alias value="Content-Type"/>
1518  <x:anchor-alias value="Content-Type-v"/>
1519<t>
1520   The entity-header field "Content-Type" indicates the media type of the
1521   entity-body sent to the recipient or, in the case of the HEAD method,
1522   the media type that would have been sent had the request been a GET.
1523</t>
1524<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Content-Type"/><iref primary="true" item="Grammar" subitem="Content-Type-v"/>
1525  <x:ref>Content-Type</x:ref>   = "Content-Type" ":" <x:ref>OWS</x:ref> <x:ref>Content-Type-v</x:ref>
1526  <x:ref>Content-Type-v</x:ref> = <x:ref>media-type</x:ref>
1527</artwork></figure>
1528<t>
1529   Media types are defined in <xref target="media.types"/>. An example of the field is
1530</t>
1531<figure><artwork type="example">
1532  Content-Type: text/html; charset=ISO-8859-4
1533</artwork></figure>
1534<t>
1535   Further discussion of methods for identifying the media type of an
1536   entity is provided in <xref target="type"/>.
1537</t>
1538</section>
1539
1540</section>
1541
1542<section title="IANA Considerations" anchor="IANA.considerations">
1543<section title="Message Header Registration" anchor="message.header.registration">
1544<t>
1545   The Message Header Registry located at <eref target="http://www.iana.org/assignments/message-headers/message-header-index.html"/> should be updated
1546   with the permanent registrations below (see <xref target="RFC3864"/>):
1547</t>
1548<!--AUTOGENERATED FROM extract-header-defs.xslt, do not edit manually-->
1549<texttable align="left" suppress-title="true" anchor="iana.header.registration.table">
1550   <ttcol>Header Field Name</ttcol>
1551   <ttcol>Protocol</ttcol>
1552   <ttcol>Status</ttcol>
1553   <ttcol>Reference</ttcol>
1554
1555   <c>Accept</c>
1556   <c>http</c>
1557   <c>standard</c>
1558   <c>
1559      <xref target="header.accept"/>
1560   </c>
1561   <c>Accept-Charset</c>
1562   <c>http</c>
1563   <c>standard</c>
1564   <c>
1565      <xref target="header.accept-charset"/>
1566   </c>
1567   <c>Accept-Encoding</c>
1568   <c>http</c>
1569   <c>standard</c>
1570   <c>
1571      <xref target="header.accept-encoding"/>
1572   </c>
1573   <c>Accept-Language</c>
1574   <c>http</c>
1575   <c>standard</c>
1576   <c>
1577      <xref target="header.accept-language"/>
1578   </c>
1579   <c>Content-Disposition</c>
1580   <c>http</c>
1581   <c/>
1582   <c>
1583      <xref target="content-disposition"/>
1584   </c>
1585   <c>Content-Encoding</c>
1586   <c>http</c>
1587   <c>standard</c>
1588   <c>
1589      <xref target="header.content-encoding"/>
1590   </c>
1591   <c>Content-Language</c>
1592   <c>http</c>
1593   <c>standard</c>
1594   <c>
1595      <xref target="header.content-language"/>
1596   </c>
1597   <c>Content-Location</c>
1598   <c>http</c>
1599   <c>standard</c>
1600   <c>
1601      <xref target="header.content-location"/>
1602   </c>
1603   <c>Content-MD5</c>
1604   <c>http</c>
1605   <c>standard</c>
1606   <c>
1607      <xref target="header.content-md5"/>
1608   </c>
1609   <c>Content-Type</c>
1610   <c>http</c>
1611   <c>standard</c>
1612   <c>
1613      <xref target="header.content-type"/>
1614   </c>
1615   <c>MIME-Version</c>
1616   <c>http</c>
1617   <c/>
1618   <c>
1619      <xref target="mime-version"/>
1620   </c>
1621</texttable>
1622<!--(END)-->
1623<t>
1624   The change controller is: "IETF (iesg@ietf.org) - Internet Engineering Task Force".
1625</t>
1626</section>
1627</section>
1628
1629<section title="Security Considerations" anchor="security.considerations">
1630<t>
1631   This section is meant to inform application developers, information
1632   providers, and users of the security limitations in HTTP/1.1 as
1633   described by this document. The discussion does not include
1634   definitive solutions to the problems revealed, though it does make
1635   some suggestions for reducing security risks.
1636</t>
1637
1638<section title="Privacy Issues Connected to Accept Headers" anchor="privacy.issues.connected.to.accept.headers">
1639<t>
1640   Accept request-headers can reveal information about the user to all
1641   servers which are accessed. The Accept-Language header in particular
1642   can reveal information the user would consider to be of a private
1643   nature, because the understanding of particular languages is often
1644   strongly correlated to the membership of a particular ethnic group.
1645   User agents which offer the option to configure the contents of an
1646   Accept-Language header to be sent in every request are strongly
1647   encouraged to let the configuration process include a message which
1648   makes the user aware of the loss of privacy involved.
1649</t>
1650<t>
1651   An approach that limits the loss of privacy would be for a user agent
1652   to omit the sending of Accept-Language headers by default, and to ask
1653   the user whether or not to start sending Accept-Language headers to a
1654   server if it detects, by looking for any Vary response-header fields
1655   generated by the server, that such sending could improve the quality
1656   of service.
1657</t>
1658<t>
1659   Elaborate user-customized accept header fields sent in every request,
1660   in particular if these include quality values, can be used by servers
1661   as relatively reliable and long-lived user identifiers. Such user
1662   identifiers would allow content providers to do click-trail tracking,
1663   and would allow collaborating content providers to match cross-server
1664   click-trails or form submissions of individual users. Note that for
1665   many users not behind a proxy, the network address of the host
1666   running the user agent will also serve as a long-lived user
1667   identifier. In environments where proxies are used to enhance
1668   privacy, user agents ought to be conservative in offering accept
1669   header configuration options to end users. As an extreme privacy
1670   measure, proxies could filter the accept headers in relayed requests.
1671   General purpose user agents which provide a high degree of header
1672   configurability &SHOULD; warn users about the loss of privacy which can
1673   be involved.
1674</t>
1675</section>
1676
1677<section title="Content-Disposition Issues" anchor="content-disposition.issues">
1678<t>
1679   <xref target="RFC2183"/>, from which the often implemented Content-Disposition
1680   (see <xref target="content-disposition"/>) header in HTTP is derived, has a number of very
1681   serious security considerations. Content-Disposition is not part of
1682   the HTTP standard, but since it is widely implemented, we are
1683   documenting its use and risks for implementors. See <xref target="RFC2183" x:fmt="of" x:sec="5"/>
1684   for details.
1685</t>
1686</section>
1687
1688</section>
1689
1690<section title="Acknowledgments" anchor="ack">
1691</section>
1692</middle>
1693<back>
1694
1695<references title="Normative References">
1696
1697<reference anchor="ISO-8859-1">
1698  <front>
1699    <title>
1700     Information technology -- 8-bit single-byte coded graphic character sets -- Part 1: Latin alphabet No. 1
1701    </title>
1702    <author>
1703      <organization>International Organization for Standardization</organization>
1704    </author>
1705    <date year="1998"/>
1706  </front>
1707  <seriesInfo name="ISO/IEC" value="8859-1:1998"/>
1708</reference>
1709
1710<reference anchor="Part1">
1711  <front>
1712    <title abbrev="HTTP/1.1">HTTP/1.1, part 1: URIs, Connections, and Message Parsing</title>
1713    <author initials="R." surname="Fielding" fullname="Roy T. Fielding" role="editor">
1714      <organization abbrev="Day Software">Day Software</organization>
1715      <address><email>fielding@gbiv.com</email></address>
1716    </author>
1717    <author initials="J." surname="Gettys" fullname="Jim Gettys">
1718      <organization>One Laptop per Child</organization>
1719      <address><email>jg@laptop.org</email></address>
1720    </author>
1721    <author initials="J." surname="Mogul" fullname="Jeffrey C. Mogul">
1722      <organization abbrev="HP">Hewlett-Packard Company</organization>
1723      <address><email>JeffMogul@acm.org</email></address>
1724    </author>
1725    <author initials="H." surname="Frystyk" fullname="Henrik Frystyk Nielsen">
1726      <organization abbrev="Microsoft">Microsoft Corporation</organization>
1727      <address><email>henrikn@microsoft.com</email></address>
1728    </author>
1729    <author initials="L." surname="Masinter" fullname="Larry Masinter">
1730      <organization abbrev="Adobe Systems">Adobe Systems, Incorporated</organization>
1731      <address><email>LMM@acm.org</email></address>
1732    </author>
1733    <author initials="P." surname="Leach" fullname="Paul J. Leach">
1734      <organization abbrev="Microsoft">Microsoft Corporation</organization>
1735      <address><email>paulle@microsoft.com</email></address>
1736    </author>
1737    <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
1738      <organization abbrev="W3C/MIT">World Wide Web Consortium</organization>
1739      <address><email>timbl@w3.org</email></address>
1740    </author>
1741    <author initials="Y." surname="Lafon" fullname="Yves Lafon" role="editor">
1742      <organization abbrev="W3C">World Wide Web Consortium</organization>
1743      <address><email>ylafon@w3.org</email></address>
1744    </author>
1745    <author initials="J. F." surname="Reschke" fullname="Julian F. Reschke" role="editor">
1746      <organization abbrev="greenbytes">greenbytes GmbH</organization>
1747      <address><email>julian.reschke@greenbytes.de</email></address>
1748    </author>
1749    <date month="&ID-MONTH;" year="&ID-YEAR;"/>
1750  </front>
1751  <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p1-messaging-&ID-VERSION;"/>
1752  <x:source href="p1-messaging.xml" basename="p1-messaging"/>
1753</reference>
1754
1755<reference anchor="Part2">
1756  <front>
1757    <title abbrev="HTTP/1.1">HTTP/1.1, part 2: Message Semantics</title>
1758    <author initials="R." surname="Fielding" fullname="Roy T. Fielding" role="editor">
1759      <organization abbrev="Day Software">Day Software</organization>
1760      <address><email>fielding@gbiv.com</email></address>
1761    </author>
1762    <author initials="J." surname="Gettys" fullname="Jim Gettys">
1763      <organization>One Laptop per Child</organization>
1764      <address><email>jg@laptop.org</email></address>
1765    </author>
1766    <author initials="J." surname="Mogul" fullname="Jeffrey C. Mogul">
1767      <organization abbrev="HP">Hewlett-Packard Company</organization>
1768      <address><email>JeffMogul@acm.org</email></address>
1769    </author>
1770    <author initials="H." surname="Frystyk" fullname="Henrik Frystyk Nielsen">
1771      <organization abbrev="Microsoft">Microsoft Corporation</organization>
1772      <address><email>henrikn@microsoft.com</email></address>
1773    </author>
1774    <author initials="L." surname="Masinter" fullname="Larry Masinter">
1775      <organization abbrev="Adobe Systems">Adobe Systems, Incorporated</organization>
1776      <address><email>LMM@acm.org</email></address>
1777    </author>
1778    <author initials="P." surname="Leach" fullname="Paul J. Leach">
1779      <organization abbrev="Microsoft">Microsoft Corporation</organization>
1780      <address><email>paulle@microsoft.com</email></address>
1781    </author>
1782    <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
1783      <organization abbrev="W3C/MIT">World Wide Web Consortium</organization>
1784      <address><email>timbl@w3.org</email></address>
1785    </author>
1786    <author initials="Y." surname="Lafon" fullname="Yves Lafon" role="editor">
1787      <organization abbrev="W3C">World Wide Web Consortium</organization>
1788      <address><email>ylafon@w3.org</email></address>
1789    </author>
1790    <author initials="J. F." surname="Reschke" fullname="Julian F. Reschke" role="editor">
1791      <organization abbrev="greenbytes">greenbytes GmbH</organization>
1792      <address><email>julian.reschke@greenbytes.de</email></address>
1793    </author>
1794    <date month="&ID-MONTH;" year="&ID-YEAR;"/>
1795  </front>
1796  <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p2-semantics-&ID-VERSION;"/>
1797  <x:source href="p2-semantics.xml" basename="p2-semantics"/>
1798</reference>
1799
1800<reference anchor="Part4">
1801  <front>
1802    <title abbrev="HTTP/1.1">HTTP/1.1, part 4: Conditional Requests</title>
1803    <author initials="R." surname="Fielding" fullname="Roy T. Fielding" role="editor">
1804      <organization abbrev="Day Software">Day Software</organization>
1805      <address><email>fielding@gbiv.com</email></address>
1806    </author>
1807    <author initials="J." surname="Gettys" fullname="Jim Gettys">
1808      <organization>One Laptop per Child</organization>
1809      <address><email>jg@laptop.org</email></address>
1810    </author>
1811    <author initials="J." surname="Mogul" fullname="Jeffrey C. Mogul">
1812      <organization abbrev="HP">Hewlett-Packard Company</organization>
1813      <address><email>JeffMogul@acm.org</email></address>
1814    </author>
1815    <author initials="H." surname="Frystyk" fullname="Henrik Frystyk Nielsen">
1816      <organization abbrev="Microsoft">Microsoft Corporation</organization>
1817      <address><email>henrikn@microsoft.com</email></address>
1818    </author>
1819    <author initials="L." surname="Masinter" fullname="Larry Masinter">
1820      <organization abbrev="Adobe Systems">Adobe Systems, Incorporated</organization>
1821      <address><email>LMM@acm.org</email></address>
1822    </author>
1823    <author initials="P." surname="Leach" fullname="Paul J. Leach">
1824      <organization abbrev="Microsoft">Microsoft Corporation</organization>
1825      <address><email>paulle@microsoft.com</email></address>
1826    </author>
1827    <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
1828      <organization abbrev="W3C/MIT">World Wide Web Consortium</organization>
1829      <address><email>timbl@w3.org</email></address>
1830    </author>
1831    <author initials="Y." surname="Lafon" fullname="Yves Lafon" role="editor">
1832      <organization abbrev="W3C">World Wide Web Consortium</organization>
1833      <address><email>ylafon@w3.org</email></address>
1834    </author>
1835    <author initials="J. F." surname="Reschke" fullname="Julian F. Reschke" role="editor">
1836      <organization abbrev="greenbytes">greenbytes GmbH</organization>
1837      <address><email>julian.reschke@greenbytes.de</email></address>
1838    </author>
1839    <date month="&ID-MONTH;" year="&ID-YEAR;"/>
1840  </front>
1841  <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p4-conditional-&ID-VERSION;"/>
1842  <x:source href="p4-conditional.xml" basename="p4-conditional"/>
1843</reference>
1844
1845<reference anchor="Part5">
1846  <front>
1847    <title abbrev="HTTP/1.1">HTTP/1.1, part 5: Range Requests and Partial Responses</title>
1848    <author initials="R." surname="Fielding" fullname="Roy T. Fielding" role="editor">
1849      <organization abbrev="Day Software">Day Software</organization>
1850      <address><email>fielding@gbiv.com</email></address>
1851    </author>
1852    <author initials="J." surname="Gettys" fullname="Jim Gettys">
1853      <organization>One Laptop per Child</organization>
1854      <address><email>jg@laptop.org</email></address>
1855    </author>
1856    <author initials="J." surname="Mogul" fullname="Jeffrey C. Mogul">
1857      <organization abbrev="HP">Hewlett-Packard Company</organization>
1858      <address><email>JeffMogul@acm.org</email></address>
1859    </author>
1860    <author initials="H." surname="Frystyk" fullname="Henrik Frystyk Nielsen">
1861      <organization abbrev="Microsoft">Microsoft Corporation</organization>
1862      <address><email>henrikn@microsoft.com</email></address>
1863    </author>
1864    <author initials="L." surname="Masinter" fullname="Larry Masinter">
1865      <organization abbrev="Adobe Systems">Adobe Systems, Incorporated</organization>
1866      <address><email>LMM@acm.org</email></address>
1867    </author>
1868    <author initials="P." surname="Leach" fullname="Paul J. Leach">
1869      <organization abbrev="Microsoft">Microsoft Corporation</organization>
1870      <address><email>paulle@microsoft.com</email></address>
1871    </author>
1872    <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
1873      <organization abbrev="W3C/MIT">World Wide Web Consortium</organization>
1874      <address><email>timbl@w3.org</email></address>
1875    </author>
1876    <author initials="Y." surname="Lafon" fullname="Yves Lafon" role="editor">
1877      <organization abbrev="W3C">World Wide Web Consortium</organization>
1878      <address><email>ylafon@w3.org</email></address>
1879    </author>
1880    <author initials="J. F." surname="Reschke" fullname="Julian F. Reschke" role="editor">
1881      <organization abbrev="greenbytes">greenbytes GmbH</organization>
1882      <address><email>julian.reschke@greenbytes.de</email></address>
1883    </author>
1884    <date month="&ID-MONTH;" year="&ID-YEAR;"/>
1885  </front>
1886  <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p5-range-&ID-VERSION;"/>
1887  <x:source href="p5-range.xml" basename="p5-range"/>
1888</reference>
1889
1890<reference anchor="Part6">
1891  <front>
1892    <title abbrev="HTTP/1.1">HTTP/1.1, part 6: Caching</title>
1893    <author initials="R." surname="Fielding" fullname="Roy T. Fielding" role="editor">
1894      <organization abbrev="Day Software">Day Software</organization>
1895      <address><email>fielding@gbiv.com</email></address>
1896    </author>
1897    <author initials="J." surname="Gettys" fullname="Jim Gettys">
1898      <organization>One Laptop per Child</organization>
1899      <address><email>jg@laptop.org</email></address>
1900    </author>
1901    <author initials="J." surname="Mogul" fullname="Jeffrey C. Mogul">
1902      <organization abbrev="HP">Hewlett-Packard Company</organization>
1903      <address><email>JeffMogul@acm.org</email></address>
1904    </author>
1905    <author initials="H." surname="Frystyk" fullname="Henrik Frystyk Nielsen">
1906      <organization abbrev="Microsoft">Microsoft Corporation</organization>
1907      <address><email>henrikn@microsoft.com</email></address>
1908    </author>
1909    <author initials="L." surname="Masinter" fullname="Larry Masinter">
1910      <organization abbrev="Adobe Systems">Adobe Systems, Incorporated</organization>
1911      <address><email>LMM@acm.org</email></address>
1912    </author>
1913    <author initials="P." surname="Leach" fullname="Paul J. Leach">
1914      <organization abbrev="Microsoft">Microsoft Corporation</organization>
1915      <address><email>paulle@microsoft.com</email></address>
1916    </author>
1917    <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
1918      <organization abbrev="W3C/MIT">World Wide Web Consortium</organization>
1919      <address><email>timbl@w3.org</email></address>
1920    </author>
1921    <author initials="Y." surname="Lafon" fullname="Yves Lafon" role="editor">
1922      <organization abbrev="W3C">World Wide Web Consortium</organization>
1923      <address><email>ylafon@w3.org</email></address>
1924    </author>
1925    <author initials="J. F." surname="Reschke" fullname="Julian F. Reschke" role="editor">
1926      <organization abbrev="greenbytes">greenbytes GmbH</organization>
1927      <address><email>julian.reschke@greenbytes.de</email></address>
1928    </author>
1929    <date month="&ID-MONTH;" year="&ID-YEAR;"/>
1930  </front>
1931  <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p6-cache-&ID-VERSION;"/>
1932  <x:source href="p6-cache.xml" basename="p6-cache"/>
1933</reference>
1934
1935<reference anchor="RFC1766">
1936  <front>
1937    <title abbrev="Language Tag">Tags for the Identification of Languages</title>
1938    <author initials="H." surname="Alvestrand" fullname="Harald Tveit Alvestrand">
1939      <organization>UNINETT</organization>
1940      <address><email>Harald.T.Alvestrand@uninett.no</email></address>
1941    </author>
1942    <date month="March" year="1995"/>
1943  </front>
1944  <seriesInfo name="RFC" value="1766"/>
1945</reference>
1946
1947<reference anchor="RFC1864">
1948  <front>
1949    <title abbrev="Content-MD5 Header Field">The Content-MD5 Header Field</title>
1950    <author initials="J." surname="Myers" fullname="John G. Myers">
1951      <organization>Carnegie Mellon University</organization>
1952      <address><email>jgm+@cmu.edu</email></address>
1953    </author>
1954    <author initials="M." surname="Rose" fullname="Marshall T. Rose">
1955      <organization>Dover Beach Consulting, Inc.</organization>
1956      <address><email>mrose@dbc.mtview.ca.us</email></address>
1957    </author>
1958    <date month="October" year="1995"/>
1959  </front>
1960  <seriesInfo name="RFC" value="1864"/>
1961</reference>
1962
1963<reference anchor="RFC1950">
1964  <front>
1965    <title>ZLIB Compressed Data Format Specification version 3.3</title>
1966    <author initials="L.P." surname="Deutsch" fullname="L. Peter Deutsch">
1967      <organization>Aladdin Enterprises</organization>
1968      <address><email>ghost@aladdin.com</email></address>
1969    </author>
1970    <author initials="J-L." surname="Gailly" fullname="Jean-Loup Gailly">
1971      <organization/>
1972    </author>
1973    <date month="May" year="1996"/>
1974  </front>
1975  <seriesInfo name="RFC" value="1950"/>
1976  <annotation>
1977    RFC 1950 is an Informational RFC, thus it may be less stable than
1978    this specification. On the other hand, this downward reference was
1979    present since the publication of RFC 2068 in 1997 (<xref target="RFC2068"/>),
1980    therefore it is unlikely to cause problems in practice. See also
1981    <xref target="BCP97"/>.
1982  </annotation>
1983</reference>
1984
1985<reference anchor="RFC1951">
1986  <front>
1987    <title>DEFLATE Compressed Data Format Specification version 1.3</title>
1988    <author initials="P." surname="Deutsch" fullname="L. Peter Deutsch">
1989      <organization>Aladdin Enterprises</organization>
1990      <address><email>ghost@aladdin.com</email></address>
1991    </author>
1992    <date month="May" year="1996"/>
1993  </front>
1994  <seriesInfo name="RFC" value="1951"/>
1995  <annotation>
1996    RFC 1951 is an Informational RFC, thus it may be less stable than
1997    this specification. On the other hand, this downward reference was
1998    present since the publication of RFC 2068 in 1997 (<xref target="RFC2068"/>),
1999    therefore it is unlikely to cause problems in practice. See also
2000    <xref target="BCP97"/>.
2001  </annotation>
2002</reference>
2003
2004<reference anchor="RFC1952">
2005  <front>
2006    <title>GZIP file format specification version 4.3</title>
2007    <author initials="P." surname="Deutsch" fullname="L. Peter Deutsch">
2008      <organization>Aladdin Enterprises</organization>
2009      <address><email>ghost@aladdin.com</email></address>
2010    </author>
2011    <author initials="J-L." surname="Gailly" fullname="Jean-Loup Gailly">
2012      <organization/>
2013      <address><email>gzip@prep.ai.mit.edu</email></address>
2014    </author>
2015    <author initials="M." surname="Adler" fullname="Mark Adler">
2016      <organization/>
2017      <address><email>madler@alumni.caltech.edu</email></address>
2018    </author>
2019    <author initials="L.P." surname="Deutsch" fullname="L. Peter Deutsch">
2020      <organization/>
2021      <address><email>ghost@aladdin.com</email></address>
2022    </author>
2023    <author initials="G." surname="Randers-Pehrson" fullname="Glenn Randers-Pehrson">
2024      <organization/>
2025      <address><email>randeg@alumni.rpi.edu</email></address>
2026    </author>
2027    <date month="May" year="1996"/>
2028  </front>
2029  <seriesInfo name="RFC" value="1952"/>
2030  <annotation>
2031    RFC 1952 is an Informational RFC, thus it may be less stable than
2032    this specification. On the other hand, this downward reference was
2033    present since the publication of RFC 2068 in 1997 (<xref target="RFC2068"/>),
2034    therefore it is unlikely to cause problems in practice. See also
2035    <xref target="BCP97"/>.
2036  </annotation>
2037</reference>
2038
2039<reference anchor="RFC2045">
2040  <front>
2041    <title abbrev="Internet Message Bodies">Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies</title>
2042    <author initials="N." surname="Freed" fullname="Ned Freed">
2043      <organization>Innosoft International, Inc.</organization>
2044      <address><email>ned@innosoft.com</email></address>
2045    </author>
2046    <author initials="N.S." surname="Borenstein" fullname="Nathaniel S. Borenstein">
2047      <organization>First Virtual Holdings</organization>
2048      <address><email>nsb@nsb.fv.com</email></address>
2049    </author>
2050    <date month="November" year="1996"/>
2051  </front>
2052  <seriesInfo name="RFC" value="2045"/>
2053</reference>
2054
2055<reference anchor="RFC2046">
2056  <front>
2057    <title abbrev="Media Types">Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types</title>
2058    <author initials="N." surname="Freed" fullname="Ned Freed">
2059      <organization>Innosoft International, Inc.</organization>
2060      <address><email>ned@innosoft.com</email></address>
2061    </author>
2062    <author initials="N." surname="Borenstein" fullname="Nathaniel S. Borenstein">
2063      <organization>First Virtual Holdings</organization>
2064      <address><email>nsb@nsb.fv.com</email></address>
2065    </author>
2066    <date month="November" year="1996"/>
2067  </front>
2068  <seriesInfo name="RFC" value="2046"/>
2069</reference>
2070
2071<reference anchor="RFC2119">
2072  <front>
2073    <title>Key words for use in RFCs to Indicate Requirement Levels</title>
2074    <author initials="S." surname="Bradner" fullname="Scott Bradner">
2075      <organization>Harvard University</organization>
2076      <address><email>sob@harvard.edu</email></address>
2077    </author>
2078    <date month="March" year="1997"/>
2079  </front>
2080  <seriesInfo name="BCP" value="14"/>
2081  <seriesInfo name="RFC" value="2119"/>
2082</reference>
2083
2084<reference anchor='RFC4647'>
2085  <front>
2086    <title>Matching of Language Tags</title>
2087    <author initials='A.' surname='Phillips' fullname='Addison Phillips' role="editor">
2088      <organization>Yahoo! Inc.</organization>
2089      <address><email>addison@inter-locale.com</email></address>
2090    </author>
2091    <author initials='M.' surname='Davis' fullname='Mark Davis' role="editor">
2092      <organization>Google</organization>
2093      <address><email>mark.davis@macchiato.com</email></address>
2094    </author>
2095    <date year='2006' month='September' />
2096  </front>
2097  <seriesInfo name='BCP' value='47' />
2098  <seriesInfo name='RFC' value='4647' />
2099</reference>
2100
2101<reference anchor="RFC5234">
2102  <front>
2103    <title abbrev="ABNF for Syntax Specifications">Augmented BNF for Syntax Specifications: ABNF</title>
2104    <author initials="D." surname="Crocker" fullname="Dave Crocker" role="editor">
2105      <organization>Brandenburg InternetWorking</organization>
2106      <address>
2107      <postal>
2108      <street>675 Spruce Dr.</street>
2109      <city>Sunnyvale</city>
2110      <region>CA</region>
2111      <code>94086</code>
2112      <country>US</country></postal>
2113      <phone>+1.408.246.8253</phone>
2114      <email>dcrocker@bbiw.net</email></address> 
2115    </author>
2116    <author initials="P." surname="Overell" fullname="Paul Overell">
2117      <organization>THUS plc.</organization>
2118      <address>
2119      <postal>
2120      <street>1/2 Berkeley Square</street>
2121      <street>99 Berkely Street</street>
2122      <city>Glasgow</city>
2123      <code>G3 7HR</code>
2124      <country>UK</country></postal>
2125      <email>paul.overell@thus.net</email></address>
2126    </author>
2127    <date month="January" year="2008"/>
2128  </front>
2129  <seriesInfo name="STD" value="68"/>
2130  <seriesInfo name="RFC" value="5234"/>
2131</reference>
2132
2133</references>
2134
2135<references title="Informative References">
2136
2137<reference anchor="RFC1945">
2138  <front>
2139    <title abbrev="HTTP/1.0">Hypertext Transfer Protocol -- HTTP/1.0</title>
2140    <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
2141      <organization>MIT, Laboratory for Computer Science</organization>
2142      <address><email>timbl@w3.org</email></address>
2143    </author>
2144    <author initials="R.T." surname="Fielding" fullname="Roy T. Fielding">
2145      <organization>University of California, Irvine, Department of Information and Computer Science</organization>
2146      <address><email>fielding@ics.uci.edu</email></address>
2147    </author>
2148    <author initials="H.F." surname="Nielsen" fullname="Henrik Frystyk Nielsen">
2149      <organization>W3 Consortium, MIT Laboratory for Computer Science</organization>
2150      <address><email>frystyk@w3.org</email></address>
2151    </author>
2152    <date month="May" year="1996"/>
2153  </front>
2154  <seriesInfo name="RFC" value="1945"/>
2155</reference>
2156
2157<reference anchor="RFC2049">
2158  <front>
2159    <title abbrev="MIME Conformance">Multipurpose Internet Mail Extensions (MIME) Part Five: Conformance Criteria and Examples</title>
2160    <author initials="N." surname="Freed" fullname="Ned Freed">
2161      <organization>Innosoft International, Inc.</organization>
2162      <address><email>ned@innosoft.com</email></address>
2163    </author>
2164    <author initials="N.S." surname="Borenstein" fullname="Nathaniel S. Borenstein">
2165      <organization>First Virtual Holdings</organization>
2166      <address><email>nsb@nsb.fv.com</email></address>
2167    </author>
2168    <date month="November" year="1996"/>
2169  </front>
2170  <seriesInfo name="RFC" value="2049"/>
2171</reference>
2172
2173<reference anchor="RFC2068">
2174  <front>
2175    <title abbrev="HTTP/1.1">Hypertext Transfer Protocol -- HTTP/1.1</title>
2176    <author initials="R." surname="Fielding" fullname="Roy T. Fielding">
2177      <organization>University of California, Irvine, Department of Information and Computer Science</organization>
2178      <address><email>fielding@ics.uci.edu</email></address>
2179    </author>
2180    <author initials="J." surname="Gettys" fullname="Jim Gettys">
2181      <organization>MIT Laboratory for Computer Science</organization>
2182      <address><email>jg@w3.org</email></address>
2183    </author>
2184    <author initials="J." surname="Mogul" fullname="Jeffrey C. Mogul">
2185      <organization>Digital Equipment Corporation, Western Research Laboratory</organization>
2186      <address><email>mogul@wrl.dec.com</email></address>
2187    </author>
2188    <author initials="H." surname="Nielsen" fullname="Henrik Frystyk Nielsen">
2189      <organization>MIT Laboratory for Computer Science</organization>
2190      <address><email>frystyk@w3.org</email></address>
2191    </author>
2192    <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
2193      <organization>MIT Laboratory for Computer Science</organization>
2194      <address><email>timbl@w3.org</email></address>
2195    </author>
2196    <date month="January" year="1997"/>
2197  </front>
2198  <seriesInfo name="RFC" value="2068"/>
2199</reference>
2200
2201<reference anchor="RFC2076">
2202  <front>
2203    <title abbrev="Internet Message Headers">Common Internet Message Headers</title>
2204    <author initials="J." surname="Palme" fullname="Jacob Palme">
2205      <organization>Stockholm University/KTH</organization>
2206      <address><email>jpalme@dsv.su.se</email></address>
2207    </author>
2208    <date month="February" year="1997"/>
2209  </front>
2210  <seriesInfo name="RFC" value="2076"/>
2211</reference>
2212
2213<reference anchor="RFC2183">
2214  <front>
2215    <title abbrev="Content-Disposition">Communicating Presentation Information in Internet Messages: The Content-Disposition Header Field</title>
2216    <author initials="R." surname="Troost" fullname="Rens Troost">
2217      <organization>New Century Systems</organization>
2218      <address><email>rens@century.com</email></address>
2219    </author>
2220    <author initials="S." surname="Dorner" fullname="Steve Dorner">
2221      <organization>QUALCOMM Incorporated</organization>
2222      <address><email>sdorner@qualcomm.com</email></address>
2223    </author>
2224    <author initials="K." surname="Moore" fullname="Keith Moore">
2225      <organization>Department of Computer Science</organization>
2226      <address><email>moore@cs.utk.edu</email></address>
2227    </author>
2228    <date month="August" year="1997"/>
2229  </front>
2230  <seriesInfo name="RFC" value="2183"/>
2231</reference>
2232
2233<reference anchor="RFC2277">
2234  <front>
2235    <title abbrev="Charset Policy">IETF Policy on Character Sets and Languages</title>
2236    <author initials="H.T." surname="Alvestrand" fullname="Harald Tveit Alvestrand">
2237      <organization>UNINETT</organization>
2238      <address><email>Harald.T.Alvestrand@uninett.no</email></address>
2239    </author>
2240    <date month="January" year="1998"/>
2241  </front>
2242  <seriesInfo name="BCP" value="18"/>
2243  <seriesInfo name="RFC" value="2277"/>
2244</reference>
2245
2246<reference anchor="RFC2388">
2247  <front>
2248    <title abbrev="multipart/form-data">Returning Values from Forms:  multipart/form-data</title>
2249    <author initials="L." surname="Masinter" fullname="Larry Masinter">
2250      <organization>Xerox Palo Alto Research Center</organization>
2251      <address><email>masinter@parc.xerox.com</email></address>
2252    </author>
2253    <date year="1998" month="August"/>
2254  </front>
2255  <seriesInfo name="RFC" value="2388"/>
2256</reference>
2257
2258<reference anchor="RFC2557">
2259  <front>
2260    <title abbrev="MIME Encapsulation of Aggregate Documents">MIME Encapsulation of Aggregate Documents, such as HTML (MHTML)</title>
2261    <author initials="F." surname="Palme" fullname="Jacob Palme">
2262      <organization>Stockholm University and KTH</organization>
2263      <address><email>jpalme@dsv.su.se</email></address>
2264    </author>
2265    <author initials="A." surname="Hopmann" fullname="Alex Hopmann">
2266      <organization>Microsoft Corporation</organization>
2267      <address><email>alexhop@microsoft.com</email></address>
2268    </author>
2269    <author initials="N." surname="Shelness" fullname="Nick Shelness">
2270      <organization>Lotus Development Corporation</organization>
2271      <address><email>Shelness@lotus.com</email></address>
2272    </author>
2273    <author initials="E." surname="Stefferud" fullname="Einar Stefferud">
2274      <organization/>
2275      <address><email>stef@nma.com</email></address>
2276    </author>
2277    <date year="1999" month="March"/>
2278  </front>
2279  <seriesInfo name="RFC" value="2557"/>
2280</reference>
2281
2282<reference anchor="RFC2616">
2283  <front>
2284    <title>Hypertext Transfer Protocol -- HTTP/1.1</title>
2285    <author initials="R." surname="Fielding" fullname="R. Fielding">
2286      <organization>University of California, Irvine</organization>
2287      <address><email>fielding@ics.uci.edu</email></address>
2288    </author>
2289    <author initials="J." surname="Gettys" fullname="J. Gettys">
2290      <organization>W3C</organization>
2291      <address><email>jg@w3.org</email></address>
2292    </author>
2293    <author initials="J." surname="Mogul" fullname="J. Mogul">
2294      <organization>Compaq Computer Corporation</organization>
2295      <address><email>mogul@wrl.dec.com</email></address>
2296    </author>
2297    <author initials="H." surname="Frystyk" fullname="H. Frystyk">
2298      <organization>MIT Laboratory for Computer Science</organization>
2299      <address><email>frystyk@w3.org</email></address>
2300    </author>
2301    <author initials="L." surname="Masinter" fullname="L. Masinter">
2302      <organization>Xerox Corporation</organization>
2303      <address><email>masinter@parc.xerox.com</email></address>
2304    </author>
2305    <author initials="P." surname="Leach" fullname="P. Leach">
2306      <organization>Microsoft Corporation</organization>
2307      <address><email>paulle@microsoft.com</email></address>
2308    </author>
2309    <author initials="T." surname="Berners-Lee" fullname="T. Berners-Lee">
2310      <organization>W3C</organization>
2311      <address><email>timbl@w3.org</email></address>
2312    </author>
2313    <date month="June" year="1999"/>
2314  </front>
2315  <seriesInfo name="RFC" value="2616"/>
2316</reference>
2317
2318<reference anchor="RFC3629">
2319  <front>
2320    <title>UTF-8, a transformation format of ISO 10646</title>
2321    <author initials="F." surname="Yergeau" fullname="F. Yergeau">
2322      <organization>Alis Technologies</organization>
2323      <address><email>fyergeau@alis.com</email></address>
2324    </author>
2325    <date month="November" year="2003"/>
2326  </front>
2327  <seriesInfo name="RFC" value="3629"/>
2328  <seriesInfo name="STD" value="63"/>
2329</reference>
2330
2331<reference anchor='RFC3864'>
2332  <front>
2333    <title>Registration Procedures for Message Header Fields</title>
2334    <author initials='G.' surname='Klyne' fullname='G. Klyne'>
2335      <organization>Nine by Nine</organization>
2336      <address><email>GK-IETF@ninebynine.org</email></address>
2337    </author>
2338    <author initials='M.' surname='Nottingham' fullname='M. Nottingham'>
2339      <organization>BEA Systems</organization>
2340      <address><email>mnot@pobox.com</email></address>
2341    </author>
2342    <author initials='J.' surname='Mogul' fullname='J. Mogul'>
2343      <organization>HP Labs</organization>
2344      <address><email>JeffMogul@acm.org</email></address>
2345    </author>
2346    <date year='2004' month='September' />
2347  </front>
2348  <seriesInfo name='BCP' value='90' />
2349  <seriesInfo name='RFC' value='3864' />
2350</reference>
2351
2352<reference anchor="RFC4288">
2353  <front>
2354    <title>Media Type Specifications and Registration Procedures</title>
2355    <author initials="N." surname="Freed" fullname="N. Freed">
2356      <organization>Sun Microsystems</organization>
2357      <address>
2358        <email>ned.freed@mrochek.com</email>
2359      </address>
2360    </author>
2361    <author initials="J." surname="Klensin" fullname="J. Klensin">
2362      <organization/>
2363      <address>
2364        <email>klensin+ietf@jck.com</email>
2365      </address>
2366    </author>
2367    <date year="2005" month="December"/>
2368  </front>
2369  <seriesInfo name="BCP" value="13"/>
2370  <seriesInfo name="RFC" value="4288"/>
2371</reference>
2372
2373<reference anchor="RFC5322">
2374  <front>
2375    <title>Internet Message Format</title>
2376    <author initials="P." surname="Resnick" fullname="P. Resnick">
2377      <organization>Qualcomm Incorporated</organization>
2378    </author>
2379    <date year="2008" month="October"/>
2380  </front> 
2381  <seriesInfo name="RFC" value="5322"/>
2382</reference>
2383
2384<reference anchor='BCP97'>
2385  <front>
2386    <title>Handling Normative References to Standards-Track Documents</title>
2387    <author initials='J.' surname='Klensin' fullname='J. Klensin'>
2388      <organization />
2389      <address>
2390        <email>klensin+ietf@jck.com</email>
2391      </address>
2392    </author>
2393    <author initials='S.' surname='Hartman' fullname='S. Hartman'>
2394      <organization>MIT</organization>
2395      <address>
2396        <email>hartmans-ietf@mit.edu</email>
2397      </address>
2398    </author>
2399    <date year='2007' month='June' />
2400  </front>
2401  <seriesInfo name='BCP' value='97' />
2402  <seriesInfo name='RFC' value='4897' />
2403</reference>
2404
2405
2406</references>
2407
2408<section title="Differences Between HTTP Entities and RFC 2045 Entities" anchor="differences.between.http.entities.and.rfc.2045.entities">
2409<t>
2410   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
2411   allow entities to be transmitted in an open variety of
2412   representations and with extensible mechanisms. However, RFC 2045
2413   discusses mail, and HTTP has a few features that are different from
2414   those described in RFC 2045. These differences were carefully chosen
2415   to optimize performance over binary connections, to allow greater
2416   freedom in the use of new media types, to make date comparisons
2417   easier, and to acknowledge the practice of some early HTTP servers
2418   and clients.
2419</t>
2420<t>
2421   This appendix describes specific areas where HTTP differs from RFC
2422   2045. Proxies and gateways to strict MIME environments &SHOULD; be
2423   aware of these differences and provide the appropriate conversions
2424   where necessary. Proxies and gateways from MIME environments to HTTP
2425   also need to be aware of the differences because some conversions
2426   might be required.
2427</t>
2428
2429<section title="MIME-Version" anchor="mime-version">
2430  <iref primary="true" item="MIME-Version header" x:for-anchor=""/>
2431  <iref primary="true" item="Headers" subitem="MIME-Version" x:for-anchor=""/>
2432  <x:anchor-alias value="MIME-Version"/>
2433  <x:anchor-alias value="MIME-Version-v"/>
2434<t>
2435   HTTP is not a MIME-compliant protocol. However, HTTP/1.1 messages &MAY;
2436   include a single MIME-Version general-header field to indicate what
2437   version of the MIME protocol was used to construct the message. Use
2438   of the MIME-Version header field indicates that the message is in
2439   full compliance with the MIME protocol (as defined in <xref target="RFC2045"/>).
2440   Proxies/gateways are responsible for ensuring full compliance (where
2441   possible) when exporting HTTP messages to strict MIME environments.
2442</t>
2443<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="MIME-Version"/><iref primary="true" item="Grammar" subitem="MIME-Version-v"/>
2444  <x:ref>MIME-Version</x:ref>   = "MIME-Version" ":" <x:ref>OWS</x:ref> <x:ref>MIME-Version-v</x:ref>
2445  <x:ref>MIME-Version-v</x:ref> = 1*<x:ref>DIGIT</x:ref> "." 1*<x:ref>DIGIT</x:ref>
2446</artwork></figure>
2447<t>
2448   MIME version "1.0" is the default for use in HTTP/1.1. However,
2449   HTTP/1.1 message parsing and semantics are defined by this document
2450   and not the MIME specification.
2451</t>
2452</section>
2453
2454<section title="Conversion to Canonical Form" anchor="conversion.to.canonical.form">
2455<t>
2456   <xref target="RFC2045"/> requires that an Internet mail entity be converted to
2457   canonical form prior to being transferred, as described in <xref target="RFC2049" x:fmt="of" x:sec="4"/>.
2458   <xref target="canonicalization.and.text.defaults"/> of this document describes the forms
2459   allowed for subtypes of the "text" media type when transmitted over
2460   HTTP. <xref target="RFC2046"/> requires that content with a type of "text" represent
2461   line breaks as CRLF and forbids the use of CR or LF outside of line
2462   break sequences. HTTP allows CRLF, bare CR, and bare LF to indicate a
2463   line break within text content when a message is transmitted over
2464   HTTP.
2465</t>
2466<t>
2467   Where it is possible, a proxy or gateway from HTTP to a strict MIME
2468   environment &SHOULD; translate all line breaks within the text media
2469   types described in <xref target="canonicalization.and.text.defaults"/> of this document to the RFC 2049
2470   canonical form of CRLF. Note, however, that this might be complicated
2471   by the presence of a Content-Encoding and by the fact that HTTP
2472   allows the use of some character sets which do not use octets 13 and
2473   10 to represent CR and LF, as is the case for some multi-byte
2474   character sets.
2475</t>
2476<t>
2477   Implementors should note that conversion will break any cryptographic
2478   checksums applied to the original content unless the original content
2479   is already in canonical form. Therefore, the canonical form is
2480   recommended for any content that uses such checksums in HTTP.
2481</t>
2482</section>
2483
2484
2485<section title="Conversion of Date Formats" anchor="conversion.of.date.formats">
2486<t>
2487   HTTP/1.1 uses a restricted set of date formats (&full-date;) to
2488   simplify the process of date comparison. Proxies and gateways from
2489   other protocols &SHOULD; ensure that any Date header field present in a
2490   message conforms to one of the HTTP/1.1 formats and rewrite the date
2491   if necessary.
2492</t>
2493</section>
2494
2495<section title="Introduction of Content-Encoding" anchor="introduction.of.content-encoding">
2496<t>
2497   RFC 2045 does not include any concept equivalent to HTTP/1.1's
2498   Content-Encoding header field. Since this acts as a modifier on the
2499   media type, proxies and gateways from HTTP to MIME-compliant
2500   protocols &MUST; either change the value of the Content-Type header
2501   field or decode the entity-body before forwarding the message. (Some
2502   experimental applications of Content-Type for Internet mail have used
2503   a media-type parameter of ";conversions=&lt;content-coding&gt;" to perform
2504   a function equivalent to Content-Encoding. However, this parameter is
2505   not part of RFC 2045).
2506</t>
2507</section>
2508
2509<section title="No Content-Transfer-Encoding" anchor="no.content-transfer-encoding">
2510<t>
2511   HTTP does not use the Content-Transfer-Encoding field of RFC
2512   2045. Proxies and gateways from MIME-compliant protocols to HTTP &MUST;
2513   remove any Content-Transfer-Encoding
2514   prior to delivering the response message to an HTTP client.
2515</t>
2516<t>
2517   Proxies and gateways from HTTP to MIME-compliant protocols are
2518   responsible for ensuring that the message is in the correct format
2519   and encoding for safe transport on that protocol, where "safe
2520   transport" is defined by the limitations of the protocol being used.
2521   Such a proxy or gateway &SHOULD; label the data with an appropriate
2522   Content-Transfer-Encoding if doing so will improve the likelihood of
2523   safe transport over the destination protocol.
2524</t>
2525</section>
2526
2527<section title="Introduction of Transfer-Encoding" anchor="introduction.of.transfer-encoding">
2528<t>
2529   HTTP/1.1 introduces the Transfer-Encoding header field (&header-transfer-encoding;).
2530   Proxies/gateways &MUST; remove any transfer-coding prior to
2531   forwarding a message via a MIME-compliant protocol.
2532</t>
2533</section>
2534
2535<section title="MHTML and Line Length Limitations" anchor="mhtml.line.length">
2536<t>
2537   HTTP implementations which share code with MHTML <xref target="RFC2557"/> implementations
2538   need to be aware of MIME line length limitations. Since HTTP does not
2539   have this limitation, HTTP does not fold long lines. MHTML messages
2540   being transported by HTTP follow all conventions of MHTML, including
2541   line length limitations and folding, canonicalization, etc., since
2542   HTTP transports all message-bodies as payload (see <xref target="multipart.types"/>) and
2543   does not interpret the content or any MIME header lines that might be
2544   contained therein.
2545</t>
2546</section>
2547</section>
2548
2549<section title="Additional Features" anchor="additional.features">
2550<t>
2551   <xref target="RFC1945"/> and <xref target="RFC2068"/> document protocol elements used by some
2552   existing HTTP implementations, but not consistently and correctly
2553   across most HTTP/1.1 applications. Implementors are advised to be
2554   aware of these features, but cannot rely upon their presence in, or
2555   interoperability with, other HTTP/1.1 applications. Some of these
2556   describe proposed experimental features, and some describe features
2557   that experimental deployment found lacking that are now addressed in
2558   the base HTTP/1.1 specification.
2559</t>
2560<t>
2561   A number of other headers, such as Content-Disposition and Title,
2562   from SMTP and MIME are also often implemented (see <xref target="RFC2076"/>).
2563</t>
2564
2565<section title="Content-Disposition" anchor="content-disposition">
2566<iref item="Headers" subitem="Content-Disposition" primary="true" x:for-anchor=""/>
2567<iref item="Content-Disposition header" primary="true" x:for-anchor=""/>
2568  <x:anchor-alias value="content-disposition"/>
2569  <x:anchor-alias value="content-disposition-v"/>
2570  <x:anchor-alias value="disposition-type"/>
2571  <x:anchor-alias value="disposition-parm"/>
2572  <x:anchor-alias value="disp-extension-parm"/>
2573  <x:anchor-alias value="disp-extension-token"/>
2574  <x:anchor-alias value="filename-parm"/>
2575<t>
2576   The Content-Disposition response-header field has been proposed as a
2577   means for the origin server to suggest a default filename if the user
2578   requests that the content is saved to a file. This usage is derived
2579   from the definition of Content-Disposition in <xref target="RFC2183"/>.
2580</t>
2581<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="content-disposition"/><iref primary="true" item="Grammar" subitem="content-disposition-v"/><iref primary="true" item="Grammar" subitem="disposition-type"/><iref primary="true" item="Grammar" subitem="disposition-parm"/><iref primary="true" item="Grammar" subitem="filename-parm"/><iref primary="true" item="Grammar" subitem="disp-extension-token"/><iref primary="true" item="Grammar" subitem="disp-extension-parm"/>
2582  <x:ref>content-disposition</x:ref> = "Content-Disposition" ":" <x:ref>OWS</x:ref>
2583                        <x:ref>content-disposition-v</x:ref>
2584  <x:ref>content-disposition-v</x:ref> = <x:ref>disposition-type</x:ref>
2585                          *( <x:ref>OWS</x:ref> ";" <x:ref>OWS</x:ref> <x:ref>disposition-parm</x:ref> )
2586  <x:ref>disposition-type</x:ref> = "attachment" / <x:ref>disp-extension-token</x:ref>
2587  <x:ref>disposition-parm</x:ref> = <x:ref>filename-parm</x:ref> / <x:ref>disp-extension-parm</x:ref>
2588  <x:ref>filename-parm</x:ref> = "filename" "=" <x:ref>quoted-string</x:ref>
2589  <x:ref>disp-extension-token</x:ref> = <x:ref>token</x:ref>
2590  <x:ref>disp-extension-parm</x:ref> = <x:ref>token</x:ref> "=" ( <x:ref>token</x:ref> / <x:ref>quoted-string</x:ref> )
2591</artwork></figure>
2592<t>
2593   An example is
2594</t>
2595<figure><artwork type="example">
2596  Content-Disposition: attachment; filename="fname.ext"
2597</artwork></figure>
2598<t>
2599   The receiving user agent &SHOULD-NOT;  respect any directory path
2600   information present in the filename-parm parameter, which is the only
2601   parameter believed to apply to HTTP implementations at this time. The
2602   filename &SHOULD; be treated as a terminal component only.
2603</t>
2604<t>
2605   If this header is used in a response with the application/octet-stream
2606   content-type, the implied suggestion is that the user agent
2607   should not display the response, but directly enter a `save response
2608   as...' dialog.
2609</t>
2610<t>
2611   See <xref target="content-disposition.issues"/> for Content-Disposition security issues.
2612</t>
2613</section>
2614</section>
2615
2616<section title="Compatibility with Previous Versions" anchor="compatibility">
2617<section title="Changes from RFC 2068" anchor="changes.from.rfc.2068">
2618<t>
2619   Transfer-coding and message lengths all interact in ways that
2620   required fixing exactly when chunked encoding is used (to allow for
2621   transfer encoding that may not be self delimiting); it was important
2622   to straighten out exactly how message lengths are computed.
2623   (<xref target="entity.length"/>, see also <xref target="Part1"/>,
2624   <xref target="Part5"/> and <xref target="Part6"/>).
2625</t>
2626<t>
2627   Charset wildcarding is introduced to avoid explosion of character set
2628   names in accept headers. (<xref target="header.accept-charset"/>)
2629</t>
2630<t>
2631   Content-Base was deleted from the specification: it was not
2632   implemented widely, and there is no simple, safe way to introduce it
2633   without a robust extension mechanism. In addition, it is used in a
2634   similar, but not identical fashion in MHTML <xref target="RFC2557"/>.
2635</t>
2636<t>
2637   A content-coding of "identity" was introduced, to solve problems
2638   discovered in caching. (<xref target="content.codings"/>)
2639</t>
2640<t>
2641   The Alternates<iref item="Alternates header" primary="true"/><iref item="Headers" subitem="Alternate" primary="true"/>, Content-Version<iref item="Content-Version header" primary="true"/><iref item="Headers" subitem="Content-Version" primary="true"/>, Derived-From<iref item="Derived-From header" primary="true"/><iref item="Headers" subitem="Derived-From" primary="true"/>, Link<iref item="Link header" primary="true"/><iref item="Headers" subitem="Link" primary="true"/>, URI<iref item="URI header" primary="true"/><iref item="Headers" subitem="URI" primary="true"/>, Public<iref item="Public header" primary="true"/><iref item="Headers" subitem="Public" primary="true"/> and
2642   Content-Base<iref item="Content-Base header" primary="true"/><iref item="Headers" subitem="Content-Base" primary="true"/> header fields were defined in previous versions of this
2643   specification, but not commonly implemented. See <xref target="RFC2068" x:fmt="of" x:sec="19.6.2"/>.
2644</t>
2645</section>
2646
2647<section title="Changes from RFC 2616" anchor="changes.from.rfc.2616">
2648<t>
2649  Clarify contexts that charset is used in.
2650  (<xref target="character.sets"/>)
2651</t>
2652<t>
2653  Remove reference to non-existant identity transfer-coding value tokens.
2654  (<xref target="no.content-transfer-encoding"/>)
2655</t>
2656</section>
2657
2658</section>
2659
2660<section xmlns:x="http://purl.org/net/xml2rfc/ext" title="Collected ABNF" anchor="collected.abnf">
2661<figure>
2662<artwork type="abnf" name="p3-payload.parsed-abnf">
2663<x:ref>Accept</x:ref> = "Accept:" OWS Accept-v
2664<x:ref>Accept-Charset</x:ref> = "Accept-Charset:" OWS Accept-Charset-v
2665<x:ref>Accept-Charset-v</x:ref> = *( "," OWS ) ( charset / "*" ) [ OWS ";" OWS "q="
2666 qvalue ] *( OWS "," [ OWS ( charset / "*" ) [ OWS ";" OWS "q="
2667 qvalue ] ] )
2668<x:ref>Accept-Encoding</x:ref> = "Accept-Encoding:" OWS Accept-Encoding-v
2669<x:ref>Accept-Encoding-v</x:ref> = [ ( "," / ( codings [ OWS ";" OWS "q=" qvalue ] )
2670 ) *( OWS "," [ OWS codings [ OWS ";" OWS "q=" qvalue ] ] ) ]
2671<x:ref>Accept-Language</x:ref> = "Accept-Language:" OWS Accept-Language-v
2672<x:ref>Accept-Language-v</x:ref> = *( "," OWS ) language-range [ OWS ";" OWS "q="
2673 qvalue ] *( OWS "," [ OWS language-range [ OWS ";" OWS "q=" qvalue ]
2674 ] )
2675<x:ref>Accept-v</x:ref> = [ ( "," / ( media-range [ accept-params ] ) ) *( OWS "," [
2676 OWS media-range [ accept-params ] ] ) ]
2677
2678<x:ref>Content-Encoding</x:ref> = "Content-Encoding:" OWS Content-Encoding-v
2679<x:ref>Content-Encoding-v</x:ref> = *( "," OWS ) content-coding *( OWS "," [ OWS
2680 content-coding ] )
2681<x:ref>Content-Language</x:ref> = "Content-Language:" OWS Content-Language-v
2682<x:ref>Content-Language-v</x:ref> = *( "," OWS ) language-tag *( OWS "," [ OWS
2683 language-tag ] )
2684<x:ref>Content-Length</x:ref> = &lt;Content-Length, defined in [Part1], Section 8.2&gt;
2685<x:ref>Content-Location</x:ref> = "Content-Location:" OWS Content-Location-v
2686<x:ref>Content-Location-v</x:ref> = absolute-URI / partial-URI
2687<x:ref>Content-MD5</x:ref> = "Content-MD5:" OWS Content-MD5-v
2688<x:ref>Content-MD5-v</x:ref> = &lt;base64 of 128 bit MD5 digest as per [RFC1864]&gt;
2689<x:ref>Content-Range</x:ref> = &lt;Content-Range, defined in [Part5], Section 5.2&gt;
2690<x:ref>Content-Type</x:ref> = "Content-Type:" OWS Content-Type-v
2691<x:ref>Content-Type-v</x:ref> = media-type
2692
2693<x:ref>Expires</x:ref> = &lt;Expires, defined in [Part6], Section 3.3&gt;
2694
2695<x:ref>Last-Modified</x:ref> = &lt;Last-Modified, defined in [Part4], Section 6.6&gt;
2696
2697<x:ref>MIME-Version</x:ref> = "MIME-Version:" OWS MIME-Version-v
2698<x:ref>MIME-Version-v</x:ref> = 1*DIGIT "." 1*DIGIT
2699
2700<x:ref>OWS</x:ref> = &lt;OWS, defined in [Part1], Section 1.2.2&gt;
2701
2702<x:ref>absolute-URI</x:ref> = &lt;absolute-URI, defined in [Part1], Section 2.1&gt;
2703<x:ref>accept-ext</x:ref> = OWS ";" OWS token [ "=" ( token / quoted-string ) ]
2704<x:ref>accept-params</x:ref> = OWS ";" OWS "q=" qvalue *accept-ext
2705<x:ref>attribute</x:ref> = token
2706
2707<x:ref>charset</x:ref> = token
2708<x:ref>codings</x:ref> = ( content-coding / "*" )
2709<x:ref>content-coding</x:ref> = token
2710<x:ref>content-disposition</x:ref> = "Content-Disposition:" OWS
2711 content-disposition-v
2712<x:ref>content-disposition-v</x:ref> = disposition-type *( OWS ";" OWS
2713 disposition-parm )
2714
2715<x:ref>disp-extension-parm</x:ref> = token "=" ( token / quoted-string )
2716<x:ref>disp-extension-token</x:ref> = token
2717<x:ref>disposition-parm</x:ref> = filename-parm / disp-extension-parm
2718<x:ref>disposition-type</x:ref> = "attachment" / disp-extension-token
2719
2720<x:ref>entity-body</x:ref> = *OCTET
2721<x:ref>entity-header</x:ref> = Content-Encoding / Content-Language / Content-Length
2722 / Content-Location / Content-MD5 / Content-Range / Content-Type /
2723 Expires / Last-Modified / extension-header
2724<x:ref>extension-header</x:ref> = message-header
2725
2726<x:ref>filename-parm</x:ref> = "filename=" quoted-string
2727
2728<x:ref>language-range</x:ref> = &lt;language-range, defined in [RFC4647], Section 2.1&gt;
2729<x:ref>language-tag</x:ref> = primary-tag *( "-" subtag )
2730
2731<x:ref>media-range</x:ref> = ( "*/*" / ( type "/*" ) / ( type "/" subtype ) ) *( OWS
2732 ";" OWS parameter )
2733<x:ref>media-type</x:ref> = type "/" subtype *( OWS ";" OWS parameter )
2734<x:ref>message-header</x:ref> = &lt;message-header, defined in [Part1], Section 4.2&gt;
2735
2736<x:ref>parameter</x:ref> = attribute "=" value
2737<x:ref>partial-URI</x:ref> = &lt;partial-URI, defined in [Part1], Section 2.1&gt;
2738<x:ref>primary-tag</x:ref> = 1*8ALPHA
2739
2740<x:ref>quoted-string</x:ref> = &lt;quoted-string, defined in [Part1], Section 1.2.2&gt;
2741<x:ref>qvalue</x:ref> = &lt;qvalue, defined in [Part1], Section 3.5&gt;
2742
2743<x:ref>subtag</x:ref> = 1*8ALPHA
2744<x:ref>subtype</x:ref> = token
2745
2746<x:ref>token</x:ref> = &lt;token, defined in [Part1], Section 1.2.2&gt;
2747<x:ref>type</x:ref> = token
2748
2749<x:ref>value</x:ref> = token / quoted-string
2750
2751
2752</artwork>
2753</figure>
2754<figure><preamble>ABNF diagnostics:</preamble><artwork type="inline">
2755; Accept defined but not used
2756; Accept-Charset defined but not used
2757; Accept-Encoding defined but not used
2758; Accept-Language defined but not used
2759; MIME-Version defined but not used
2760; content-disposition defined but not used
2761; entity-body defined but not used
2762; entity-header defined but not used
2763</artwork></figure></section>
2764
2765<section title="Change Log (to be removed by RFC Editor before publication)" anchor="change.log">
2766
2767<section title="Since RFC2616">
2768<t>
2769  Extracted relevant partitions from <xref target="RFC2616"/>.
2770</t>
2771</section>
2772
2773<section title="Since draft-ietf-httpbis-p3-payload-00">
2774<t>
2775  Closed issues:
2776  <list style="symbols"> 
2777    <t>
2778      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/8"/>:
2779      "Media Type Registrations"
2780      (<eref target="http://purl.org/NET/http-errata#media-reg"/>)
2781    </t>
2782    <t>
2783      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/14"/>:
2784      "Clarification regarding quoting of charset values"
2785      (<eref target="http://purl.org/NET/http-errata#charactersets"/>)
2786    </t>
2787    <t>
2788      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/16"/>:
2789      "Remove 'identity' token references"
2790      (<eref target="http://purl.org/NET/http-errata#identity"/>)
2791    </t>
2792    <t>
2793      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/25"/>:
2794      "Accept-Encoding BNF"
2795    </t>
2796    <t>
2797      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/35"/>:
2798      "Normative and Informative references"
2799    </t>
2800    <t>
2801      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/46"/>:
2802      "RFC1700 references"
2803    </t>
2804    <t>
2805      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/55"/>:
2806      "Updating to RFC4288"
2807    </t>
2808    <t>
2809      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/65"/>:
2810      "Informative references"
2811    </t>
2812    <t>
2813      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/66"/>:
2814      "ISO-8859-1 Reference"
2815    </t>
2816    <t>
2817      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/68"/>:
2818      "Encoding References Normative"
2819    </t>
2820    <t>
2821      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/86"/>:
2822      "Normative up-to-date references"
2823    </t>
2824  </list>
2825</t>
2826</section>
2827
2828<section title="Since draft-ietf-httpbis-p3-payload-01">
2829<t>
2830  Ongoing work on ABNF conversion (<eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/36"/>):
2831  <list style="symbols"> 
2832    <t>
2833      Add explicit references to BNF syntax and rules imported from other parts of the specification.
2834    </t>
2835  </list>
2836</t>
2837</section>
2838
2839<section title="Since draft-ietf-httpbis-p3-payload-02" anchor="changes.since.02">
2840<t>
2841  Closed issues:
2842  <list style="symbols"> 
2843    <t>
2844      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/67"/>:
2845      "Quoting Charsets"
2846    </t>
2847    <t>
2848      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/105"/>:
2849      "Classification for Allow header"
2850    </t>
2851    <t>
2852      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/115"/>:
2853      "missing default for qvalue in description of Accept-Encoding"
2854    </t>
2855  </list>
2856</t>
2857<t>
2858  Ongoing work on IANA Message Header Registration (<eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/40"/>):
2859  <list style="symbols"> 
2860    <t>
2861      Reference RFC 3984, and update header registrations for headers defined
2862      in this document.
2863    </t>
2864  </list>
2865</t>
2866</section>
2867
2868<section title="Since draft-ietf-httpbis-p3-payload-03" anchor="changes.since.03">
2869<t>
2870  Closed issues:
2871  <list style="symbols"> 
2872    <t>
2873      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/67"/>:
2874      "Quoting Charsets"
2875    </t>
2876    <t>
2877      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/113"/>:
2878      "language tag matching (Accept-Language) vs RFC4647"
2879    </t>
2880    <t>
2881      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/121"/>:
2882      "RFC 1806 has been replaced by RFC2183"
2883    </t>
2884  </list>
2885</t>
2886<t>
2887  Other changes:
2888  <list style="symbols"> 
2889    <t>
2890      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/68"/>:
2891      "Encoding References Normative" -- rephrase the annotation and reference
2892      <xref target="BCP97"/>.
2893    </t>
2894  </list>
2895</t>
2896 </section>
2897
2898<section title="Since draft-ietf-httpbis-p3-payload-04" anchor="changes.since.04">
2899<t>
2900  Closed issues:
2901  <list style="symbols"> 
2902    <t>
2903      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/132"/>:
2904      "RFC 2822 is updated by RFC 5322"
2905    </t>
2906  </list>
2907</t>
2908<t>
2909  Ongoing work on ABNF conversion (<eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/36"/>):
2910  <list style="symbols"> 
2911    <t>
2912      Use "/" instead of "|" for alternatives.
2913    </t>
2914    <t>
2915      Introduce new ABNF rules for "bad" whitespace ("BWS"), optional
2916      whitespace ("OWS") and required whitespace ("RWS").
2917    </t>
2918    <t>
2919      Rewrite ABNFs to spell out whitespace rules, factor out
2920      header value format definitions.
2921    </t>
2922  </list>
2923</t>
2924</section>
2925
2926<section title="Since draft-ietf-httpbis-p3-payload-05" anchor="changes.since.05">
2927<t>
2928  Closed issues:
2929  <list style="symbols"> 
2930    <t>
2931      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/118"/>:
2932      "Join "Differences Between HTTP Entities and RFC 2045 Entities"?"
2933    </t>
2934  </list>
2935</t>
2936<t>
2937  Final work on ABNF conversion (<eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/36"/>):
2938  <list style="symbols"> 
2939    <t>
2940      Add appendix containing collected and expanded ABNF, reorganize ABNF introduction.
2941    </t>
2942  </list>
2943</t>
2944<t>
2945  Other changes:
2946  <list style="symbols"> 
2947    <t>
2948      Move definition of quality values into Part 1.
2949    </t>
2950  </list>
2951</t>
2952</section>
2953
2954<section title="Since draft-ietf-httpbis-p3-payload-06" anchor="changes.since.06">
2955<t>
2956  Closed issues:
2957  <list style="symbols"> 
2958    <t>
2959      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/80"/>:
2960      "Content-Location isn't special"
2961    </t>
2962  </list>
2963</t>
2964</section>
2965
2966</section>
2967
2968</back>
2969</rfc>
Note: See TracBrowser for help on using the repository browser.