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

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

Tune strength of requirements on Accept re: 406 (see #285)

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