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

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

fix issue list link in boilerplate

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