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

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

take out note about content-sniffing as discussed in HTTPbis Working Group meeting (related to #155)

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