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

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

editorial: enhance readability of header introductions

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