Ignore:
Timestamp:
28/03/12 15:54:24 (10 years ago)
Author:
julian.reschke@…
Message:

exp

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/experiment/p3-payload.html

    r1625 r1627  
    112112  font-style: normal;
    113113}
    114 div.note {
    115   margin-left: 2em;
    116 }
    117114dd {
    118115  margin-right: 2em;
     
    211208  margin-left: 2em;
    212209}
    213 table.tt {
    214   vertical-align: top;
    215 }
    216 table.full {
    217   border-style: outset;
    218   border-width: 1px;
    219 }
    220 table.headers {
    221   border-style: outset;
    222   border-width: 1px;
    223 }
    224 table.tt td {
    225   vertical-align: top;
    226 }
    227 table.full td {
    228   border-style: inset;
    229   border-width: 1px;
    230 }
    231 table.tt th {
    232   vertical-align: top;
    233 }
    234 table.full th {
    235   border-style: inset;
    236   border-width: 1px;
    237 }
    238 table.headers th {
    239   border-style: none none inset none;
    240   border-width: 1px;
    241 }
    242 table.left {
    243   margin-right: auto;
    244 }
    245 table.right {
    246   margin-left: auto;
    247 }
    248 table.center {
    249   margin-left: auto;
    250   margin-right: auto;
    251 }
    252 caption {
    253   caption-side: bottom;
    254   font-weight: bold;
    255   font-size: 9pt;
    256   margin-top: .5em;
    257 }
    258 
    259210table.header {
    260211  border-spacing: 1px;
     
    311262  margin-left: 0em;
    312263}
    313 ul.ind, ul.ind ul {
    314   list-style: none;
    315   margin-left: 1.5em;
    316   margin-right: 0em;
    317   padding-left: 0em;
    318   page-break-before: avoid;
    319 }
    320 ul.ind li {
    321   font-weight: bold;
    322   line-height: 200%;
    323   margin-left: 0em;
    324   margin-right: 0em;
    325 }
    326 ul.ind li li {
    327   font-weight: normal;
    328   line-height: 150%;
    329   margin-left: 0em;
    330   margin-right: 0em;
    331 }
    332 .avoidbreak {
    333   page-break-inside: avoid;
    334 }
    335 .bcp14 {
    336   font-style: normal;
    337   text-transform: lowercase;
    338   font-variant: small-caps;
    339 }
     264
    340265.comment {
    341266  background-color: yellow;
     
    481406      <link rel="Author" href="#rfc.authors">
    482407      <link rel="Copyright" href="#rfc.copyrightnotice">
    483       <link rel="Index" href="#rfc.index">
    484       <link rel="Chapter" title="1 Introduction" href="#rfc.section.1">
    485       <link rel="Chapter" title="2 Protocol Parameters" href="#rfc.section.2">
    486       <link rel="Chapter" title="3 Payload" href="#rfc.section.3">
    487       <link rel="Chapter" title="4 Representation" href="#rfc.section.4">
    488       <link rel="Chapter" title="5 Content Negotiation" href="#rfc.section.5">
    489       <link rel="Chapter" title="6 Header Field Definitions" href="#rfc.section.6">
    490       <link rel="Chapter" title="7 IANA Considerations" href="#rfc.section.7">
    491       <link rel="Chapter" title="8 Security Considerations" href="#rfc.section.8">
    492       <link rel="Chapter" title="9 Acknowledgments" href="#rfc.section.9">
    493       <link rel="Chapter" href="#rfc.section.10" title="10 References">
    494       <link rel="Appendix" title="A Differences between HTTP and MIME" href="#rfc.section.A">
    495       <link rel="Appendix" title="B Additional Features" href="#rfc.section.B">
    496       <link rel="Appendix" title="C Changes from RFC 2616" href="#rfc.section.C">
    497       <link rel="Appendix" title="D Collected ABNF" href="#rfc.section.D">
    498       <link rel="Appendix" title="E Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.E">
     408      <link rel="Chapter" title="1 " href="#rfc.section.1">
     409      <link rel="Chapter" href="#rfc.section.2" title="2 References">
     410      <link rel="Appendix" title="A Changes from RFC 2616" href="#rfc.section.A">
     411      <link rel="Appendix" title="B Collected ABNF" href="#rfc.section.B">
    499412      <link href="p2-semantics.html" rel="prev">
    500413      <link href="p4-conditional.html" rel="next">
     
    507420      <meta name="dct.issued" scheme="ISO8601" content="2012-03-28">
    508421      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    509       <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 3 of the seven-part specification that defines the protocol referred to as &#34;HTTP/1.1&#34; and, taken together, obsoletes RFC 2616. Part 3 defines HTTP message content, metadata, and content negotiation.">
    510       <meta name="description" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 3 of the seven-part specification that defines the protocol referred to as &#34;HTTP/1.1&#34; and, taken together, obsoletes RFC 2616. Part 3 defines HTTP message content, metadata, and content negotiation.">
     422      <meta name="dct.abstract" content="">
     423      <meta name="description" content="">
    511424   </head>
    512425   <body onload="init();">
     
    545458      </table>
    546459      <p class="title">HTTP/1.1, part 3: Message Payload and Content Negotiation<br><span class="filename">draft-ietf-httpbis-p3-payload-latest</span></p>
    547       <h1 id="rfc.abstract"><a href="#rfc.abstract">Abstract</a></h1>
    548       <p>The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information
    549          systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 3 of the
    550          seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616.
    551       </p> 
    552       <p>Part 3 defines HTTP message content, metadata, and content negotiation.</p>
    553       <h1 id="rfc.note.1"><a href="#rfc.note.1">Editorial Note (To be removed by RFC Editor)</a></h1>
    554       <p>Discussion of this draft should take place on the HTTPBIS working group mailing list (ietf-http-wg@w3.org), which is archived
    555          at &lt;<a href="http://lists.w3.org/Archives/Public/ietf-http-wg/">http://lists.w3.org/Archives/Public/ietf-http-wg/</a>&gt;.
    556       </p> 
    557       <p>The current issues list is at &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/report/3">http://tools.ietf.org/wg/httpbis/trac/report/3</a>&gt; and related documents (including fancy diffs) can be found at &lt;<a href="http://tools.ietf.org/wg/httpbis/">http://tools.ietf.org/wg/httpbis/</a>&gt;.
    558       </p> 
    559       <p>The changes in this draft are summarized in <a href="#changes.since.19" title="Since draft-ietf-httpbis-p3-payload-19">Appendix&nbsp;E.21</a>.
    560       </p>
     460      <h1 id="rfc.abstract"><a href="#rfc.abstract">Abstract</a></h1> 
    561461      <h1><a id="rfc.status" href="#rfc.status">Status of This Memo</a></h1>
    562462      <p>This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.</p>
     
    586486      <h1 class="np" id="rfc.toc"><a href="#rfc.toc">Table of Contents</a></h1>
    587487      <ul class="toc">
    588          <li>1.&nbsp;&nbsp;&nbsp;<a href="#introduction">Introduction</a><ul>
    589                <li>1.1&nbsp;&nbsp;&nbsp;<a href="#terminology">Terminology</a></li>
    590                <li>1.2&nbsp;&nbsp;&nbsp;<a href="#intro.conformance.and.error.handling">Conformance and Error Handling</a></li>
    591                <li>1.3&nbsp;&nbsp;&nbsp;<a href="#notation">Syntax Notation</a><ul>
    592                      <li>1.3.1&nbsp;&nbsp;&nbsp;<a href="#core.rules">Core Rules</a></li>
    593                      <li>1.3.2&nbsp;&nbsp;&nbsp;<a href="#abnf.dependencies">ABNF Rules defined in other Parts of the Specification</a></li>
    594                   </ul>
    595                </li>
    596             </ul>
    597          </li>
    598          <li>2.&nbsp;&nbsp;&nbsp;<a href="#protocol.parameters">Protocol Parameters</a><ul>
    599                <li>2.1&nbsp;&nbsp;&nbsp;<a href="#character.sets">Character Encodings (charset)</a></li>
    600                <li>2.2&nbsp;&nbsp;&nbsp;<a href="#content.codings">Content Codings</a><ul>
    601                      <li>2.2.1&nbsp;&nbsp;&nbsp;<a href="#content.coding.registry">Content Coding Registry</a></li>
    602                   </ul>
    603                </li>
    604                <li>2.3&nbsp;&nbsp;&nbsp;<a href="#media.types">Media Types</a><ul>
    605                      <li>2.3.1&nbsp;&nbsp;&nbsp;<a href="#canonicalization.and.text.defaults">Canonicalization and Text Defaults</a></li>
    606                      <li>2.3.2&nbsp;&nbsp;&nbsp;<a href="#multipart.types">Multipart Types</a></li>
    607                   </ul>
    608                </li>
    609                <li>2.4&nbsp;&nbsp;&nbsp;<a href="#language.tags">Language Tags</a></li>
    610             </ul>
    611          </li>
    612          <li>3.&nbsp;&nbsp;&nbsp;<a href="#payload">Payload</a><ul>
    613                <li>3.1&nbsp;&nbsp;&nbsp;<a href="#payload.header.fields">Payload Header Fields</a></li>
    614                <li>3.2&nbsp;&nbsp;&nbsp;<a href="#payload.body">Payload Body</a></li>
    615             </ul>
    616          </li>
    617          <li>4.&nbsp;&nbsp;&nbsp;<a href="#representation">Representation</a><ul>
    618                <li>4.1&nbsp;&nbsp;&nbsp;<a href="#representation.header.fields">Representation Header Fields</a></li>
    619                <li>4.2&nbsp;&nbsp;&nbsp;<a href="#representation.data">Representation Data</a></li>
    620             </ul>
    621          </li>
    622          <li>5.&nbsp;&nbsp;&nbsp;<a href="#content.negotiation">Content Negotiation</a><ul>
    623                <li>5.1&nbsp;&nbsp;&nbsp;<a href="#server-driven.negotiation">Server-driven Negotiation</a></li>
    624                <li>5.2&nbsp;&nbsp;&nbsp;<a href="#agent-driven.negotiation">Agent-driven Negotiation</a></li>
    625             </ul>
    626          </li>
    627          <li>6.&nbsp;&nbsp;&nbsp;<a href="#header.field.definitions">Header Field Definitions</a><ul>
    628                <li>6.1&nbsp;&nbsp;&nbsp;<a href="#header.accept">Accept</a></li>
    629                <li>6.2&nbsp;&nbsp;&nbsp;<a href="#header.accept-charset">Accept-Charset</a></li>
    630                <li>6.3&nbsp;&nbsp;&nbsp;<a href="#header.accept-encoding">Accept-Encoding</a></li>
    631                <li>6.4&nbsp;&nbsp;&nbsp;<a href="#header.accept-language">Accept-Language</a></li>
    632                <li>6.5&nbsp;&nbsp;&nbsp;<a href="#header.content-encoding">Content-Encoding</a></li>
    633                <li>6.6&nbsp;&nbsp;&nbsp;<a href="#header.content-language">Content-Language</a></li>
    634                <li>6.7&nbsp;&nbsp;&nbsp;<a href="#header.content-location">Content-Location</a></li>
    635                <li>6.8&nbsp;&nbsp;&nbsp;<a href="#header.content-type">Content-Type</a></li>
    636             </ul>
    637          </li>
    638          <li>7.&nbsp;&nbsp;&nbsp;<a href="#IANA.considerations">IANA Considerations</a><ul>
    639                <li>7.1&nbsp;&nbsp;&nbsp;<a href="#header.field.registration">Header Field Registration</a></li>
    640                <li>7.2&nbsp;&nbsp;&nbsp;<a href="#content.coding.registration">Content Coding Registry</a></li>
    641             </ul>
    642          </li>
    643          <li>8.&nbsp;&nbsp;&nbsp;<a href="#security.considerations">Security Considerations</a><ul>
    644                <li>8.1&nbsp;&nbsp;&nbsp;<a href="#privacy.issues.connected.to.accept.header.fields">Privacy Issues Connected to Accept Header Fields</a></li>
    645             </ul>
    646          </li>
    647          <li>9.&nbsp;&nbsp;&nbsp;<a href="#acks">Acknowledgments</a></li>
    648          <li>10.&nbsp;&nbsp;&nbsp;<a href="#rfc.references">References</a><ul>
    649                <li>10.1&nbsp;&nbsp;&nbsp;<a href="#rfc.references.1">Normative References</a></li>
    650                <li>10.2&nbsp;&nbsp;&nbsp;<a href="#rfc.references.2">Informative References</a></li>
     488         <li>1.&nbsp;&nbsp;&nbsp;<a href="#rfc.section.1"></a></li>
     489         <li>2.&nbsp;&nbsp;&nbsp;<a href="#rfc.references">References</a><ul>
     490               <li>2.1&nbsp;&nbsp;&nbsp;<a href="#rfc.references.1">Normative References</a></li>
     491               <li>2.2&nbsp;&nbsp;&nbsp;<a href="#rfc.references.2">Informative References</a></li>
    651492            </ul>
    652493         </li>
    653494         <li><a href="#rfc.authors">Authors' Addresses</a></li>
    654          <li>A.&nbsp;&nbsp;&nbsp;<a href="#differences.between.http.and.mime">Differences between HTTP and MIME</a><ul>
    655                <li>A.1&nbsp;&nbsp;&nbsp;<a href="#mime-version">MIME-Version</a></li>
    656                <li>A.2&nbsp;&nbsp;&nbsp;<a href="#conversion.to.canonical.form">Conversion to Canonical Form</a></li>
    657                <li>A.3&nbsp;&nbsp;&nbsp;<a href="#conversion.of.date.formats">Conversion of Date Formats</a></li>
    658                <li>A.4&nbsp;&nbsp;&nbsp;<a href="#introduction.of.content-encoding">Introduction of Content-Encoding</a></li>
    659                <li>A.5&nbsp;&nbsp;&nbsp;<a href="#no.content-transfer-encoding">No Content-Transfer-Encoding</a></li>
    660                <li>A.6&nbsp;&nbsp;&nbsp;<a href="#introduction.of.transfer-encoding">Introduction of Transfer-Encoding</a></li>
    661                <li>A.7&nbsp;&nbsp;&nbsp;<a href="#mhtml.line.length">MHTML and Line Length Limitations</a></li>
    662             </ul>
    663          </li>
    664          <li>B.&nbsp;&nbsp;&nbsp;<a href="#additional.features">Additional Features</a></li>
    665          <li>C.&nbsp;&nbsp;&nbsp;<a href="#changes.from.rfc.2616">Changes from RFC 2616</a></li>
    666          <li>D.&nbsp;&nbsp;&nbsp;<a href="#collected.abnf">Collected ABNF</a></li>
    667          <li>E.&nbsp;&nbsp;&nbsp;<a href="#change.log">Change Log (to be removed by RFC Editor before publication)</a><ul>
    668                <li>E.1&nbsp;&nbsp;&nbsp;<a href="#rfc.section.E.1">Since RFC 2616</a></li>
    669                <li>E.2&nbsp;&nbsp;&nbsp;<a href="#rfc.section.E.2">Since draft-ietf-httpbis-p3-payload-00</a></li>
    670                <li>E.3&nbsp;&nbsp;&nbsp;<a href="#rfc.section.E.3">Since draft-ietf-httpbis-p3-payload-01</a></li>
    671                <li>E.4&nbsp;&nbsp;&nbsp;<a href="#changes.since.02">Since draft-ietf-httpbis-p3-payload-02</a></li>
    672                <li>E.5&nbsp;&nbsp;&nbsp;<a href="#changes.since.03">Since draft-ietf-httpbis-p3-payload-03</a></li>
    673                <li>E.6&nbsp;&nbsp;&nbsp;<a href="#changes.since.04">Since draft-ietf-httpbis-p3-payload-04</a></li>
    674                <li>E.7&nbsp;&nbsp;&nbsp;<a href="#changes.since.05">Since draft-ietf-httpbis-p3-payload-05</a></li>
    675                <li>E.8&nbsp;&nbsp;&nbsp;<a href="#changes.since.06">Since draft-ietf-httpbis-p3-payload-06</a></li>
    676                <li>E.9&nbsp;&nbsp;&nbsp;<a href="#changes.since.07">Since draft-ietf-httpbis-p3-payload-07</a></li>
    677                <li>E.10&nbsp;&nbsp;&nbsp;<a href="#changes.since.08">Since draft-ietf-httpbis-p3-payload-08</a></li>
    678                <li>E.11&nbsp;&nbsp;&nbsp;<a href="#changes.since.09">Since draft-ietf-httpbis-p3-payload-09</a></li>
    679                <li>E.12&nbsp;&nbsp;&nbsp;<a href="#changes.since.10">Since draft-ietf-httpbis-p3-payload-10</a></li>
    680                <li>E.13&nbsp;&nbsp;&nbsp;<a href="#changes.since.11">Since draft-ietf-httpbis-p3-payload-11</a></li>
    681                <li>E.14&nbsp;&nbsp;&nbsp;<a href="#changes.since.12">Since draft-ietf-httpbis-p3-payload-12</a></li>
    682                <li>E.15&nbsp;&nbsp;&nbsp;<a href="#changes.since.13">Since draft-ietf-httpbis-p3-payload-13</a></li>
    683                <li>E.16&nbsp;&nbsp;&nbsp;<a href="#changes.since.14">Since draft-ietf-httpbis-p3-payload-14</a></li>
    684                <li>E.17&nbsp;&nbsp;&nbsp;<a href="#changes.since.15">Since draft-ietf-httpbis-p3-payload-15</a></li>
    685                <li>E.18&nbsp;&nbsp;&nbsp;<a href="#changes.since.16">Since draft-ietf-httpbis-p3-payload-16</a></li>
    686                <li>E.19&nbsp;&nbsp;&nbsp;<a href="#changes.since.17">Since draft-ietf-httpbis-p3-payload-17</a></li>
    687                <li>E.20&nbsp;&nbsp;&nbsp;<a href="#changes.since.18">Since draft-ietf-httpbis-p3-payload-18</a></li>
    688                <li>E.21&nbsp;&nbsp;&nbsp;<a href="#changes.since.19">Since draft-ietf-httpbis-p3-payload-19</a></li>
    689             </ul>
    690          </li>
    691          <li><a href="#rfc.index">Index</a></li>
     495         <li>A.&nbsp;&nbsp;&nbsp;<a href="#changes.from.rfc.2616">Changes from RFC 2616</a></li>
     496         <li>B.&nbsp;&nbsp;&nbsp;<a href="#collected.abnf">Collected ABNF</a></li>
    692497      </ul>
    693       <h1 id="rfc.section.1" class="np"><a href="#rfc.section.1">1.</a>&nbsp;<a id="introduction" href="#introduction">Introduction</a></h1>
    694       <p id="rfc.section.1.p.1">This document defines HTTP/1.1 message payloads (a.k.a., content), the associated metadata header fields that define how the
    695          payload is intended to be interpreted by a recipient, the request header fields that might influence content selection, and
    696          the various selection algorithms that are collectively referred to as HTTP content negotiation.
    697       </p>
    698       <p id="rfc.section.1.p.2">This document is currently disorganized in order to minimize the changes between drafts and enable reviewers to see the smaller
    699          errata changes. A future draft will reorganize the sections to better reflect the content. In particular, the sections on
    700          entities will be renamed payload and moved to the first half of the document, while the sections on content negotiation and
    701          associated request header fields will be moved to the second half. The current mess reflects how widely dispersed these topics
    702          and associated requirements had become in <a href="#RFC2616" id="rfc.xref.RFC2616.1"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>.
    703       </p>
    704       <h2 id="rfc.section.1.1"><a href="#rfc.section.1.1">1.1</a>&nbsp;<a id="terminology" href="#terminology">Terminology</a></h2>
    705       <p id="rfc.section.1.1.p.1">This specification uses a number of terms to refer to the roles played by participants in, and objects of, the HTTP communication.</p>
    706       <p id="rfc.section.1.1.p.2"> <span id="rfc.iref.c.1"></span>  <dfn>content negotiation</dfn> 
    707       </p>
    708       <ul class="empty">
    709          <li>The mechanism for selecting the appropriate representation when servicing a request. The representation in any response can
    710             be negotiated (including error responses).
    711          </li>
    712       </ul>
    713       <p id="rfc.section.1.1.p.3"> <span id="rfc.iref.s.1"></span>  <dfn>selected representation</dfn> 
    714       </p>
    715       <ul class="empty">
    716          <li>The current representation of the target resource that would have been selected in a successful response if the same request
    717             had used the method GET and excluded any conditional request header fields.
    718          </li>
    719       </ul>
    720       <h2 id="rfc.section.1.2"><a href="#rfc.section.1.2">1.2</a>&nbsp;<a id="intro.conformance.and.error.handling" href="#intro.conformance.and.error.handling">Conformance and Error Handling</a></h2>
    721       <p id="rfc.section.1.2.p.1">The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL"
    722          in this document are to be interpreted as described in <a href="#RFC2119" id="rfc.xref.RFC2119.1"><cite title="Key words for use in RFCs to Indicate Requirement Levels">[RFC2119]</cite></a>.
    723       </p>
    724       <p id="rfc.section.1.2.p.2">This document defines conformance criteria for several roles in HTTP communication, including Senders, Recipients, Clients,
    725          Servers, User-Agents, Origin Servers, Intermediaries, Proxies and Gateways. See <a href="p1-messaging.html#architecture" title="Architecture">Section 2</a> of <a href="#Part1" id="rfc.xref.Part1.1"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a> for definitions of these terms.
    726       </p>
    727       <p id="rfc.section.1.2.p.3">An implementation is considered conformant if it complies with all of the requirements associated with its role(s). Note that
    728          SHOULD-level requirements are relevant here, unless one of the documented exceptions is applicable.
    729       </p>
    730       <p id="rfc.section.1.2.p.4">This document also uses ABNF to define valid protocol elements (<a href="#notation" title="Syntax Notation">Section&nbsp;1.3</a>). In addition to the prose requirements placed upon them, Senders <em class="bcp14">MUST NOT</em> generate protocol elements that are invalid.
    731       </p>
    732       <p id="rfc.section.1.2.p.5">Unless noted otherwise, Recipients <em class="bcp14">MAY</em> take steps to recover a usable protocol element from an invalid construct. However, HTTP does not define specific error handling
    733          mechanisms, except in cases where it has direct impact on security. This is because different uses of the protocol require
    734          different error handling strategies; for example, a Web browser may wish to transparently recover from a response where the
    735          Location header field doesn't parse according to the ABNF, whereby in a systems control protocol using HTTP, this type of
    736          error recovery could lead to dangerous consequences.
    737       </p>
    738       <h2 id="rfc.section.1.3"><a href="#rfc.section.1.3">1.3</a>&nbsp;<a id="notation" href="#notation">Syntax Notation</a></h2>
    739       <p id="rfc.section.1.3.p.1">This specification uses the Augmented Backus-Naur Form (ABNF) notation of <a href="#RFC5234" id="rfc.xref.RFC5234.1"><cite title="Augmented BNF for Syntax Specifications: ABNF">[RFC5234]</cite></a> with the list rule extension defined in <a href="p1-messaging.html#notation" title="Syntax Notation">Section 1.2</a> of <a href="#Part1" id="rfc.xref.Part1.2"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>. <a href="#collected.abnf" title="Collected ABNF">Appendix&nbsp;D</a> shows the collected ABNF with the list rule expanded.
    740       </p>
    741       <p id="rfc.section.1.3.p.2">The following core rules are included by reference, as defined in <a href="#RFC5234" id="rfc.xref.RFC5234.2"><cite title="Augmented BNF for Syntax Specifications: ABNF">[RFC5234]</cite></a>, <a href="http://tools.ietf.org/html/rfc5234#appendix-B.1">Appendix B.1</a>: ALPHA (letters), CR (carriage return), CRLF (CR LF), CTL (controls), DIGIT (decimal 0-9), DQUOTE (double quote), HEXDIG
    742          (hexadecimal 0-9/A-F/a-f), LF (line feed), OCTET (any 8-bit sequence of data), SP (space), and VCHAR (any visible US-ASCII
    743          character).
    744       </p>
    745       <h3 id="rfc.section.1.3.1"><a href="#rfc.section.1.3.1">1.3.1</a>&nbsp;<a id="core.rules" href="#core.rules">Core Rules</a></h3>
    746       <p id="rfc.section.1.3.1.p.1">The core rules below are defined in <a href="#Part1" id="rfc.xref.Part1.3"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>:
    747       </p>
    748       <div id="rfc.figure.u.1"></div><pre class="inline">  <a href="#core.rules" class="smpl">OWS</a>            = &lt;OWS, defined in <a href="#Part1" id="rfc.xref.Part1.4"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#whitespace" title="Whitespace">Section 3.2.1</a>&gt;
    749   <a href="#core.rules" class="smpl">token</a>          = &lt;token, defined in <a href="#Part1" id="rfc.xref.Part1.5"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#field.components" title="Field value components">Section 3.2.4</a>&gt;
    750   <a href="#core.rules" class="smpl">word</a>           = &lt;word, defined in <a href="#Part1" id="rfc.xref.Part1.6"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#field.components" title="Field value components">Section 3.2.4</a>&gt;
    751 </pre><h3 id="rfc.section.1.3.2"><a href="#rfc.section.1.3.2">1.3.2</a>&nbsp;<a id="abnf.dependencies" href="#abnf.dependencies">ABNF Rules defined in other Parts of the Specification</a></h3>
    752       <p id="rfc.section.1.3.2.p.1">The ABNF rules below are defined in other parts:</p>
    753       <div id="rfc.figure.u.2"></div><pre class="inline">  <a href="#abnf.dependencies" class="smpl">absolute-URI</a>   = &lt;absolute-URI, defined in <a href="#Part1" id="rfc.xref.Part1.7"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#uri" title="Uniform Resource Identifiers">Section 2.7</a>&gt;
    754   <a href="#abnf.dependencies" class="smpl">partial-URI</a>    = &lt;partial-URI, defined in <a href="#Part1" id="rfc.xref.Part1.8"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#uri" title="Uniform Resource Identifiers">Section 2.7</a>&gt;
    755   <a href="#abnf.dependencies" class="smpl">qvalue</a>         = &lt;qvalue, defined in <a href="#Part1" id="rfc.xref.Part1.9"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#quality.values" title="Quality Values">Section 4.3.1</a>&gt;
    756 </pre><h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a>&nbsp;<a id="protocol.parameters" href="#protocol.parameters">Protocol Parameters</a></h1>
    757       <h2 id="rfc.section.2.1"><a href="#rfc.section.2.1">2.1</a>&nbsp;<a id="character.sets" href="#character.sets">Character Encodings (charset)</a></h2>
    758       <p id="rfc.section.2.1.p.1">HTTP uses charset names to indicate the character encoding of a textual representation.</p>
    759       <div id="rule.charset">
    760          <p id="rfc.section.2.1.p.2">  A character encoding is identified by a case-insensitive token. The complete set of tokens is defined by the IANA Character
    761             Set registry (&lt;<a href="http://www.iana.org/assignments/character-sets">http://www.iana.org/assignments/character-sets</a>&gt;).
    762          </p>
    763       </div>
    764       <div id="rfc.figure.u.3"></div><pre class="inline"><span id="rfc.iref.g.1"></span>  <a href="#rule.charset" class="smpl">charset</a> = <a href="#core.rules" class="smpl">token</a>
    765 </pre><p id="rfc.section.2.1.p.4">Although HTTP allows an arbitrary token to be used as a charset value, any token that has a predefined value within the IANA
    766          Character Set registry <em class="bcp14">MUST</em> represent the character encoding defined by that registry. Applications <em class="bcp14">SHOULD</em> limit their use of character encodings to those defined within the IANA registry.
    767       </p>
    768       <p id="rfc.section.2.1.p.5">HTTP uses charset in two contexts: within an Accept-Charset request header field (in which the charset value is an unquoted
    769          token) and as the value of a parameter in a Content-Type header field (within a request or response), in which case the parameter
    770          value of the charset parameter can be quoted.
    771       </p>
    772       <p id="rfc.section.2.1.p.6">Implementors need to be aware of IETF character set requirements <a href="#RFC3629" id="rfc.xref.RFC3629.1"><cite title="UTF-8, a transformation format of ISO 10646">[RFC3629]</cite></a>  <a href="#RFC2277" id="rfc.xref.RFC2277.1"><cite title="IETF Policy on Character Sets and Languages">[RFC2277]</cite></a>.
    773       </p>
    774       <h2 id="rfc.section.2.2"><a href="#rfc.section.2.2">2.2</a>&nbsp;<a id="content.codings" href="#content.codings">Content Codings</a></h2>
    775       <p id="rfc.section.2.2.p.1">Content coding values indicate an encoding transformation that has been or can be applied to a representation. Content codings
    776          are primarily used to allow a representation to be compressed or otherwise usefully transformed without losing the identity
    777          of its underlying media type and without loss of information. Frequently, the representation is stored in coded form, transmitted
    778          directly, and only decoded by the recipient.
    779       </p>
    780       <div id="rfc.figure.u.4"></div><pre class="inline"><span id="rfc.iref.g.2"></span>  <a href="#content.codings" class="smpl">content-coding</a>   = <a href="#core.rules" class="smpl">token</a>
    781 </pre><p id="rfc.section.2.2.p.3">All content-coding values are case-insensitive. HTTP/1.1 uses content-coding values in the Accept-Encoding (<a href="#header.accept-encoding" id="rfc.xref.header.accept-encoding.1" title="Accept-Encoding">Section&nbsp;6.3</a>) and Content-Encoding (<a href="#header.content-encoding" id="rfc.xref.header.content-encoding.1" title="Content-Encoding">Section&nbsp;6.5</a>) header fields. Although the value describes the content-coding, what is more important is that it indicates what decoding
    782          mechanism will be required to remove the encoding.
    783       </p>
    784       <p id="rfc.section.2.2.p.4">compress<span id="rfc.iref.c.2"></span><span id="rfc.iref.c.3"></span> 
    785       </p>
    786       <ul class="empty">
    787          <li>See <a href="p1-messaging.html#compress.coding" title="Compress Coding">Section 4.2.1</a> of <a href="#Part1" id="rfc.xref.Part1.10"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>.
    788          </li>
    789       </ul>
    790       <p id="rfc.section.2.2.p.5">deflate<span id="rfc.iref.d.1"></span><span id="rfc.iref.c.4"></span> 
    791       </p>
    792       <ul class="empty">
    793          <li>See <a href="p1-messaging.html#deflate.coding" title="Deflate Coding">Section 4.2.2</a> of <a href="#Part1" id="rfc.xref.Part1.11"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>.
    794          </li>
    795       </ul>
    796       <p id="rfc.section.2.2.p.6">gzip<span id="rfc.iref.g.3"></span><span id="rfc.iref.c.5"></span> 
    797       </p>
    798       <ul class="empty">
    799          <li>See <a href="p1-messaging.html#gzip.coding" title="Gzip Coding">Section 4.2.3</a> of <a href="#Part1" id="rfc.xref.Part1.12"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>.
    800          </li>
    801       </ul>
    802       <h3 id="rfc.section.2.2.1"><a href="#rfc.section.2.2.1">2.2.1</a>&nbsp;<a id="content.coding.registry" href="#content.coding.registry">Content Coding Registry</a></h3>
    803       <p id="rfc.section.2.2.1.p.1">The HTTP Content Coding Registry defines the name space for the content coding names.</p>
    804       <p id="rfc.section.2.2.1.p.2">Registrations <em class="bcp14">MUST</em> include the following fields:
    805       </p>
    806       <ul>
    807          <li>Name</li>
    808          <li>Description</li>
    809          <li>Pointer to specification text</li>
    810       </ul>
    811       <p id="rfc.section.2.2.1.p.3">Names of content codings <em class="bcp14">MUST NOT</em> overlap with names of transfer codings (<a href="p1-messaging.html#transfer.codings" title="Transfer Codings">Section 4</a> of <a href="#Part1" id="rfc.xref.Part1.13"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>), unless the encoding transformation is identical (as is the case for the compression codings defined in <a href="p1-messaging.html#compression.codings" title="Compression Codings">Section 4.2</a> of <a href="#Part1" id="rfc.xref.Part1.14"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>).
    812       </p>
    813       <p id="rfc.section.2.2.1.p.4">Values to be added to this name space require IETF Review (see <a href="http://tools.ietf.org/html/rfc5226#section-4.1">Section 4.1</a> of <a href="#RFC5226" id="rfc.xref.RFC5226.1"><cite title="Guidelines for Writing an IANA Considerations Section in RFCs">[RFC5226]</cite></a>), and <em class="bcp14">MUST</em> conform to the purpose of content coding defined in this section.
    814       </p>
    815       <p id="rfc.section.2.2.1.p.5">The registry itself is maintained at &lt;<a href="http://www.iana.org/assignments/http-parameters">http://www.iana.org/assignments/http-parameters</a>&gt;.
    816       </p>
    817       <h2 id="rfc.section.2.3"><a href="#rfc.section.2.3">2.3</a>&nbsp;<a id="media.types" href="#media.types">Media Types</a></h2>
    818       <p id="rfc.section.2.3.p.1">HTTP uses Internet Media Types <a href="#RFC2046" id="rfc.xref.RFC2046.1"><cite title="Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types">[RFC2046]</cite></a> in the Content-Type (<a href="#header.content-type" id="rfc.xref.header.content-type.1" title="Content-Type">Section&nbsp;6.8</a>) and Accept (<a href="#header.accept" id="rfc.xref.header.accept.1" title="Accept">Section&nbsp;6.1</a>) header fields in order to provide open and extensible data typing and type negotiation.
    819       </p>
    820       <div id="rfc.figure.u.5"></div><pre class="inline"><span id="rfc.iref.g.4"></span><span id="rfc.iref.g.5"></span><span id="rfc.iref.g.6"></span>  <a href="#media.types" class="smpl">media-type</a> = <a href="#media.types" class="smpl">type</a> "/" <a href="#media.types" class="smpl">subtype</a> *( <a href="#core.rules" class="smpl">OWS</a> ";" <a href="#core.rules" class="smpl">OWS</a> <a href="#rule.parameter" class="smpl">parameter</a> )
    821   <a href="#media.types" class="smpl">type</a>       = <a href="#core.rules" class="smpl">token</a>
    822   <a href="#media.types" class="smpl">subtype</a>    = <a href="#core.rules" class="smpl">token</a>
    823 </pre><div id="rule.parameter">
    824          <p id="rfc.section.2.3.p.3">      The type/subtype <em class="bcp14">MAY</em> be followed by parameters in the form of attribute/value pairs.
    825          </p>
    826       </div>
    827       <div id="rfc.figure.u.6"></div><pre class="inline"><span id="rfc.iref.g.7"></span><span id="rfc.iref.g.8"></span><span id="rfc.iref.g.9"></span>  <a href="#rule.parameter" class="smpl">parameter</a>      = <a href="#rule.parameter" class="smpl">attribute</a> "=" <a href="#rule.parameter" class="smpl">value</a>
    828   <a href="#rule.parameter" class="smpl">attribute</a>      = <a href="#core.rules" class="smpl">token</a>
    829   <a href="#rule.parameter" class="smpl">value</a>          = <a href="#core.rules" class="smpl">word</a>
    830 </pre><p id="rfc.section.2.3.p.5">The type, subtype, and parameter attribute names are case-insensitive. Parameter values might or might not be case-sensitive,
    831          depending on the semantics of the parameter name. The presence or absence of a parameter might be significant to the processing
    832          of a media-type, depending on its definition within the media type registry.
    833       </p>
    834       <p id="rfc.section.2.3.p.6">A parameter value that matches the <a href="#core.rules" class="smpl">token</a> production can be transmitted as either a token or within a quoted-string. The quoted and unquoted values are equivalent.
    835       </p>
    836       <p id="rfc.section.2.3.p.7">Note that some older HTTP applications do not recognize media type parameters. When sending data to older HTTP applications,
    837          implementations <em class="bcp14">SHOULD</em> only use media type parameters when they are required by that type/subtype definition.
    838       </p>
    839       <p id="rfc.section.2.3.p.8">Media-type values are registered with the Internet Assigned Number Authority (IANA). The media type registration process is
    840          outlined in <a href="#RFC4288" id="rfc.xref.RFC4288.1"><cite title="Media Type Specifications and Registration Procedures">[RFC4288]</cite></a>. Use of non-registered media types is discouraged.
    841       </p>
    842       <h3 id="rfc.section.2.3.1"><a href="#rfc.section.2.3.1">2.3.1</a>&nbsp;<a id="canonicalization.and.text.defaults" href="#canonicalization.and.text.defaults">Canonicalization and Text Defaults</a></h3>
    843       <p id="rfc.section.2.3.1.p.1">Internet media types are registered with a canonical form. A representation transferred via HTTP messages <em class="bcp14">MUST</em> be in the appropriate canonical form prior to its transmission except for "text" types, as defined in the next paragraph.
    844       </p>
    845       <p id="rfc.section.2.3.1.p.2">When in canonical form, media subtypes of the "text" type use CRLF as the text line break. HTTP relaxes this requirement and
    846          allows the transport of text media with plain CR or LF alone representing a line break when it is done consistently for an
    847          entire representation. HTTP applications <em class="bcp14">MUST</em> accept CRLF, bare CR, and bare LF as indicating a line break in text media received via HTTP. In addition, if the text is
    848          in a character encoding that does not use octets 13 and 10 for CR and LF respectively, as is the case for some multi-byte
    849          character encodings, HTTP allows the use of whatever octet sequences are defined by that character encoding to represent the
    850          equivalent of CR and LF for line breaks. This flexibility regarding line breaks applies only to text media in the payload
    851          body; a bare CR or LF <em class="bcp14">MUST NOT</em> be substituted for CRLF within any of the HTTP control structures (such as header fields and multipart boundaries).
    852       </p>
    853       <p id="rfc.section.2.3.1.p.3">If a representation is encoded with a content-coding, the underlying data <em class="bcp14">MUST</em> be in a form defined above prior to being encoded.
    854       </p>
    855       <h3 id="rfc.section.2.3.2"><a href="#rfc.section.2.3.2">2.3.2</a>&nbsp;<a id="multipart.types" href="#multipart.types">Multipart Types</a></h3>
    856       <p id="rfc.section.2.3.2.p.1">MIME provides for a number of "multipart" types — encapsulations of one or more representations within a single message body.
    857          All multipart types share a common syntax, as defined in <a href="http://tools.ietf.org/html/rfc2046#section-5.1.1">Section 5.1.1</a> of <a href="#RFC2046" id="rfc.xref.RFC2046.2"><cite title="Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types">[RFC2046]</cite></a>, and <em class="bcp14">MUST</em> include a boundary parameter as part of the media type value. The message body is itself a protocol element and <em class="bcp14">MUST</em> therefore use only CRLF to represent line breaks between body-parts.
    858       </p>
    859       <p id="rfc.section.2.3.2.p.2">In general, HTTP treats a multipart message body no differently than any other media type: strictly as payload. HTTP does
    860          not use the multipart boundary as an indicator of message body length.  In all other respects, an HTTP user agent <em class="bcp14">SHOULD</em> follow the same or similar behavior as a MIME user agent would upon receipt of a multipart type. The MIME header fields within
    861          each body-part of a multipart message body do not have any significance to HTTP beyond that defined by their MIME semantics.
    862       </p>
    863       <p id="rfc.section.2.3.2.p.3">If an application receives an unrecognized multipart subtype, the application <em class="bcp14">MUST</em> treat it as being equivalent to "multipart/mixed".
    864       </p>
    865       <div class="note" id="rfc.section.2.3.2.p.4">
    866          <p> <b>Note:</b> The "multipart/form-data" type has been specifically defined for carrying form data suitable for processing via the POST request
    867             method, as described in <a href="#RFC2388" id="rfc.xref.RFC2388.1"><cite title="Returning Values from Forms: multipart/form-data">[RFC2388]</cite></a>.
    868          </p>
    869       </div>
    870       <h2 id="rfc.section.2.4"><a href="#rfc.section.2.4">2.4</a>&nbsp;<a id="language.tags" href="#language.tags">Language Tags</a></h2>
    871       <p id="rfc.section.2.4.p.1">A language tag, as defined in <a href="#RFC5646" id="rfc.xref.RFC5646.1"><cite title="Tags for Identifying Languages">[RFC5646]</cite></a>, identifies a natural language spoken, written, or otherwise conveyed by human beings for communication of information to
    872          other human beings. Computer languages are explicitly excluded. HTTP uses language tags within the Accept-Language and Content-Language
    873          fields.
    874       </p>
    875       <p id="rfc.section.2.4.p.2">In summary, a language tag is composed of one or more parts: A primary language subtag followed by a possibly empty series
    876          of subtags:
    877       </p>
    878       <div id="rfc.figure.u.7"></div><pre class="inline"><span id="rfc.iref.g.10"></span>  <a href="#language.tags" class="smpl">language-tag</a> = &lt;Language-Tag, defined in <a href="#RFC5646" id="rfc.xref.RFC5646.2"><cite title="Tags for Identifying Languages">[RFC5646]</cite></a>, <a href="http://tools.ietf.org/html/rfc5646#section-2.1">Section 2.1</a>&gt;
    879 </pre><p id="rfc.section.2.4.p.4">White space is not allowed within the tag and all tags are case-insensitive. The name space of language subtags is administered
    880          by the IANA (see &lt;<a href="http://www.iana.org/assignments/language-subtag-registry">http://www.iana.org/assignments/language-subtag-registry</a>&gt;).
    881       </p>
    882       <div id="rfc.figure.u.8"></div>
    883       <p>Example tags include:</p>  <pre class="text">  en, en-US, es-419, az-Arab, x-pig-latin, man-Nkoo-GN
    884 </pre> <p id="rfc.section.2.4.p.6">See <a href="#RFC5646" id="rfc.xref.RFC5646.3"><cite title="Tags for Identifying Languages">[RFC5646]</cite></a> for further information.
    885       </p>
    886       <h1 id="rfc.section.3"><a href="#rfc.section.3">3.</a>&nbsp;<a id="payload" href="#payload">Payload</a></h1>
    887       <p id="rfc.section.3.p.1">HTTP messages <em class="bcp14">MAY</em> transfer a payload if not otherwise restricted by the request method or response status code. The payload consists of metadata,
    888          in the form of header fields, and data, in the form of the sequence of octets in the message body after any transfer-coding
    889          has been decoded.
    890       </p>
    891       <div id="rfc.iref.p.1"></div>
    892       <p id="rfc.section.3.p.2">A "<dfn>payload</dfn>" in HTTP is always a partial or complete representation of some resource. We use separate terms for payload and representation
    893          because some messages contain only the associated representation's header fields (e.g., responses to HEAD) or only some part(s)
    894          of the representation (e.g., the 206 status code).
    895       </p>
    896       <h2 id="rfc.section.3.1"><a href="#rfc.section.3.1">3.1</a>&nbsp;<a id="payload.header.fields" href="#payload.header.fields">Payload Header Fields</a></h2>
    897       <p id="rfc.section.3.1.p.1">HTTP header fields that specifically define the payload, rather than the associated representation, are referred to as "payload
    898          header fields". The following payload header fields are defined by HTTP/1.1:
    899       </p>
    900       <div id="rfc.table.u.1">
    901          <table class="tt full left" cellpadding="3" cellspacing="0">
    902             <thead>
    903                <tr>
    904                   <th>Header Field Name</th>
    905                   <th>Defined in...</th>
    906                </tr>
    907             </thead>
    908             <tbody>
    909                <tr>
    910                   <td class="left">Content-Length</td>
    911                   <td class="left"><a href="p1-messaging.html#header.content-length" title="Content-Length">Section 3.3.2</a> of <a href="#Part1" id="rfc.xref.Part1.15"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a></td>
    912                </tr>
    913                <tr>
    914                   <td class="left">Content-Range</td>
    915                   <td class="left"><a href="p5-range.html#header.content-range" title="Content-Range">Section 5.2</a> of <a href="#Part5" id="rfc.xref.Part5.1"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a></td>
    916                </tr>
    917             </tbody>
    918          </table>
    919       </div>
    920       <h2 id="rfc.section.3.2"><a href="#rfc.section.3.2">3.2</a>&nbsp;<a id="payload.body" href="#payload.body">Payload Body</a></h2>
    921       <p id="rfc.section.3.2.p.1">A payload body is only present in a message when a message body is present, as described in <a href="p1-messaging.html#message.body" title="Message Body">Section 3.3</a> of <a href="#Part1" id="rfc.xref.Part1.16"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>. The payload body is obtained from the message body by decoding any Transfer-Encoding that might have been applied to ensure
    922          safe and proper transfer of the message.
    923       </p>
    924       <div id="rfc.iref.r.1"></div>
    925       <h1 id="rfc.section.4"><a href="#rfc.section.4">4.</a>&nbsp;<a id="representation" href="#representation">Representation</a></h1>
    926       <p id="rfc.section.4.p.1">A "<dfn>representation</dfn>" is information in a format that can be readily communicated from one party to another. A resource representation is information
    927          that reflects the state of that resource, as observed at some point in the past (e.g., in a response to GET) or to be desired
    928          at some point in the future (e.g., in a PUT request).
    929       </p>
    930       <p id="rfc.section.4.p.2">Most, but not all, representations transferred via HTTP are intended to be a representation of the target resource (the resource
    931          identified by the effective request URI). The precise semantics of a representation are determined by the type of message
    932          (request or response), the request method, the response status code, and the representation metadata. For example, the above
    933          semantic is true for the representation in any 200 (OK) response to GET and for the representation in any PUT request. A 200
    934          response to PUT, in contrast, contains either a representation that describes the successful action or a representation of
    935          the target resource, with the latter indicated by a Content-Location header field with the same value as the effective request
    936          URI. Likewise, response messages with an error status code usually contain a representation that describes the error and what
    937          next steps are suggested for resolving it.
    938       </p>
    939       <h2 id="rfc.section.4.1"><a href="#rfc.section.4.1">4.1</a>&nbsp;<a id="representation.header.fields" href="#representation.header.fields">Representation Header Fields</a></h2>
    940       <p id="rfc.section.4.1.p.1">Representation header fields define metadata about the representation data enclosed in the message body or, if no message
    941          body is present, about the representation that would have been transferred in a 200 response to a simultaneous GET request
    942          with the same effective request URI.
    943       </p>
    944       <p id="rfc.section.4.1.p.2">The following header fields are defined as representation metadata:</p>
    945       <div id="rfc.table.u.2">
    946          <table class="tt full left" cellpadding="3" cellspacing="0">
    947             <thead>
    948                <tr>
    949                   <th>Header Field Name</th>
    950                   <th>Defined in...</th>
    951                </tr>
    952             </thead>
    953             <tbody>
    954                <tr>
    955                   <td class="left">Content-Encoding</td>
    956                   <td class="left"><a href="#header.content-encoding" id="rfc.xref.header.content-encoding.2" title="Content-Encoding">Section&nbsp;6.5</a></td>
    957                </tr>
    958                <tr>
    959                   <td class="left">Content-Language</td>
    960                   <td class="left"><a href="#header.content-language" id="rfc.xref.header.content-language.1" title="Content-Language">Section&nbsp;6.6</a></td>
    961                </tr>
    962                <tr>
    963                   <td class="left">Content-Location</td>
    964                   <td class="left"><a href="#header.content-location" id="rfc.xref.header.content-location.1" title="Content-Location">Section&nbsp;6.7</a></td>
    965                </tr>
    966                <tr>
    967                   <td class="left">Content-Type</td>
    968                   <td class="left"><a href="#header.content-type" id="rfc.xref.header.content-type.2" title="Content-Type">Section&nbsp;6.8</a></td>
    969                </tr>
    970                <tr>
    971                   <td class="left">Expires</td>
    972                   <td class="left"><a href="p6-cache.html#header.expires" title="Expires">Section 3.3</a> of <a href="#Part6" id="rfc.xref.Part6.1"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a></td>
    973                </tr>
    974             </tbody>
    975          </table>
    976       </div>
    977       <p id="rfc.section.4.1.p.3">Additional header fields define metadata about the selected representation, which might differ from the representation included
    978          in the message for responses to some state-changing methods. The following header fields are defined as selected representation
    979          metadata:
    980       </p>
    981       <div id="rfc.table.u.3">
    982          <table class="tt full left" cellpadding="3" cellspacing="0">
    983             <thead>
    984                <tr>
    985                   <th>Header Field Name</th>
    986                   <th>Defined in...</th>
    987                </tr>
    988             </thead>
    989             <tbody>
    990                <tr>
    991                   <td class="left">ETag</td>
    992                   <td class="left"><a href="p4-conditional.html#header.etag" title="ETag">Section 2.3</a> of <a href="#Part4" id="rfc.xref.Part4.1"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a></td>
    993                </tr>
    994                <tr>
    995                   <td class="left">Last-Modified</td>
    996                   <td class="left"><a href="p4-conditional.html#header.last-modified" title="Last-Modified">Section 2.2</a> of <a href="#Part4" id="rfc.xref.Part4.2"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a></td>
    997                </tr>
    998             </tbody>
    999          </table>
    1000       </div>
    1001       <h2 id="rfc.section.4.2"><a href="#rfc.section.4.2">4.2</a>&nbsp;<a id="representation.data" href="#representation.data">Representation Data</a></h2>
    1002       <p id="rfc.section.4.2.p.1">The representation body associated with an HTTP message is either provided as the payload body of the message or referred
    1003          to by the message semantics and the effective request URI. The representation data is in a format and encoding defined by
    1004          the representation metadata header fields.
    1005       </p>
    1006       <p id="rfc.section.4.2.p.2">The data type of the representation data is determined via the header fields Content-Type and Content-Encoding. These define
    1007          a two-layer, ordered encoding model:
    1008       </p>
    1009       <div id="rfc.figure.u.9"></div><pre class="text">  representation-data := Content-Encoding( Content-Type( bits ) )
    1010 </pre><p id="rfc.section.4.2.p.4">Content-Type specifies the media type of the underlying data, which defines both the data format and how that data <em class="bcp14">SHOULD</em> be processed by the recipient (within the scope of the request method semantics). Any HTTP/1.1 message containing a payload
    1011          body <em class="bcp14">SHOULD</em> include a Content-Type header field defining the media type of the associated representation unless that metadata is unknown
    1012          to the sender. If the Content-Type header field is not present, it indicates that the sender does not know the media type
    1013          of the representation; recipients <em class="bcp14">MAY</em> either assume that the media type is "application/octet-stream" (<a href="#RFC2046" id="rfc.xref.RFC2046.3"><cite title="Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types">[RFC2046]</cite></a>, <a href="http://tools.ietf.org/html/rfc2046#section-4.5.1">Section 4.5.1</a>) or examine the content to determine its type.
    1014       </p>
    1015       <p id="rfc.section.4.2.p.5">In practice, resource owners do not always properly configure their origin server to provide the correct Content-Type for
    1016          a given representation, with the result that some clients will examine a response body's content and override the specified
    1017          type. Clients that do so risk drawing incorrect conclusions, which might expose additional security risks (e.g., "privilege
    1018          escalation"). Furthermore, it is impossible to determine the sender's intent by examining the data format: many data formats
    1019          match multiple media types that differ only in processing semantics. Implementers are encouraged to provide a means of disabling
    1020          such "content sniffing" when it is used.
    1021       </p>
    1022       <p id="rfc.section.4.2.p.6">Content-Encoding is used to indicate any additional content codings applied to the data, usually for the purpose of data compression,
    1023          that are a property of the representation. If Content-Encoding is not present, then there is no additional encoding beyond
    1024          that defined by the Content-Type.
    1025       </p>
    1026       <h1 id="rfc.section.5"><a href="#rfc.section.5">5.</a>&nbsp;<a id="content.negotiation" href="#content.negotiation">Content Negotiation</a></h1>
    1027       <p id="rfc.section.5.p.1">HTTP responses include a representation which contains information for interpretation, whether by a human user or for further
    1028          processing. Often, the server has different ways of representing the same information; for example, in different formats,
    1029          languages, or using different character encodings.
    1030       </p>
    1031       <p id="rfc.section.5.p.2">HTTP clients and their users might have different or variable capabilities, characteristics or preferences which would influence
    1032          which representation, among those available from the server, would be best for the server to deliver. For this reason, HTTP
    1033          provides mechanisms for "content negotiation" — a process of allowing selection of a representation of a given resource, when
    1034          more than one is available.
    1035       </p>
    1036       <p id="rfc.section.5.p.3">This specification defines two patterns of content negotiation; "server-driven", where the server selects the representation
    1037          based upon the client's stated preferences, and "agent-driven" negotiation, where the server provides a list of representations
    1038          for the client to choose from, based upon their metadata. In addition, there are other patterns: some applications use an
    1039          "active content" pattern, where the server returns active content which runs on the client and, based on client available
    1040          parameters, selects additional resources to invoke. "Transparent Content Negotiation" (<a href="#RFC2295" id="rfc.xref.RFC2295.1"><cite title="Transparent Content Negotiation in HTTP">[RFC2295]</cite></a>) has also been proposed.
    1041       </p>
    1042       <p id="rfc.section.5.p.4">These patterns are all widely used, and have trade-offs in applicability and practicality. In particular, when the number
    1043          of preferences or capabilities to be expressed by a client are large (such as when many different formats are supported by
    1044          a user-agent), server-driven negotiation becomes unwieldy, and might not be appropriate. Conversely, when the number of representations
    1045          to choose from is very large, agent-driven negotiation might not be appropriate.
    1046       </p>
    1047       <p id="rfc.section.5.p.5">Note that in all cases, the supplier of representations has the responsibility for determining which representations might
    1048          be considered to be the "same information".
    1049       </p>
    1050       <h2 id="rfc.section.5.1"><a href="#rfc.section.5.1">5.1</a>&nbsp;<a id="server-driven.negotiation" href="#server-driven.negotiation">Server-driven Negotiation</a></h2>
    1051       <p id="rfc.section.5.1.p.1">If the selection of the best representation for a response is made by an algorithm located at the server, it is called server-driven
    1052          negotiation. Selection is based on the available representations of the response (the dimensions over which it can vary; e.g.,
    1053          language, content-coding, etc.) and the contents of particular header fields in the request message or on other information
    1054          pertaining to the request (such as the network address of the client).
    1055       </p>
    1056       <p id="rfc.section.5.1.p.2">Server-driven negotiation is advantageous when the algorithm for selecting from among the available representations is difficult
    1057          to describe to the user agent, or when the server desires to send its "best guess" to the client along with the first response
    1058          (hoping to avoid the round-trip delay of a subsequent request if the "best guess" is good enough for the user). In order to
    1059          improve the server's guess, the user agent <em class="bcp14">MAY</em> include request header fields (Accept, Accept-Language, Accept-Encoding, etc.) which describe its preferences for such a response.
    1060       </p>
    1061       <p id="rfc.section.5.1.p.3">Server-driven negotiation has disadvantages: </p>
    1062       <ol>
    1063          <li>It is impossible for the server to accurately determine what might be "best" for any given user, since that would require
    1064             complete knowledge of both the capabilities of the user agent and the intended use for the response (e.g., does the user want
    1065             to view it on screen or print it on paper?).
    1066          </li>
    1067          <li>Having the user agent describe its capabilities in every request can be both very inefficient (given that only a small percentage
    1068             of responses have multiple representations) and a potential violation of the user's privacy.
    1069          </li>
    1070          <li>It complicates the implementation of an origin server and the algorithms for generating responses to a request.</li>
    1071          <li>It might limit a public cache's ability to use the same response for multiple user's requests.</li>
    1072       </ol>
    1073       <p id="rfc.section.5.1.p.4">Server-driven negotiation allows the user agent to specify its preferences, but it cannot expect responses to always honor
    1074          them. For example, the origin server might not implement server-driven negotiation, or it might decide that sending a response
    1075          that doesn't conform to them is better than sending a 406 (Not Acceptable) response.
    1076       </p>
    1077       <p id="rfc.section.5.1.p.5">Many of the mechanisms for expressing preferences use quality values to declare relative preference. See <a href="p1-messaging.html#quality.values" title="Quality Values">Section 4.3.1</a> of <a href="#Part1" id="rfc.xref.Part1.17"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a> for more information.
    1078       </p>
    1079       <p id="rfc.section.5.1.p.6">HTTP/1.1 includes the following header fields for enabling server-driven negotiation through description of user agent capabilities
    1080          and user preferences: Accept (<a href="#header.accept" id="rfc.xref.header.accept.2" title="Accept">Section&nbsp;6.1</a>), Accept-Charset (<a href="#header.accept-charset" id="rfc.xref.header.accept-charset.1" title="Accept-Charset">Section&nbsp;6.2</a>), Accept-Encoding (<a href="#header.accept-encoding" id="rfc.xref.header.accept-encoding.2" title="Accept-Encoding">Section&nbsp;6.3</a>), Accept-Language (<a href="#header.accept-language" id="rfc.xref.header.accept-language.1" title="Accept-Language">Section&nbsp;6.4</a>), and User-Agent (<a href="p2-semantics.html#header.user-agent" title="User-Agent">Section 7.10</a> of <a href="#Part2" id="rfc.xref.Part2.1"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>). However, an origin server is not limited to these dimensions and <em class="bcp14">MAY</em> vary the response based on any aspect of the request, including aspects of the connection (e.g., IP address) or information
    1081          within extension header fields not defined by this specification.
    1082       </p>
    1083       <div class="note" id="rfc.section.5.1.p.7">
    1084          <p> <b>Note:</b> In practice, User-Agent based negotiation is fragile, because new clients might not be recognized.
    1085          </p>
    1086       </div>
    1087       <p id="rfc.section.5.1.p.8">The Vary header field (<a href="p6-cache.html#header.vary" title="Vary">Section 3.5</a> of <a href="#Part6" id="rfc.xref.Part6.2"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>) can be used to express the parameters the server uses to select a representation that is subject to server-driven negotiation.
    1088       </p>
    1089       <h2 id="rfc.section.5.2"><a href="#rfc.section.5.2">5.2</a>&nbsp;<a id="agent-driven.negotiation" href="#agent-driven.negotiation">Agent-driven Negotiation</a></h2>
    1090       <p id="rfc.section.5.2.p.1">With agent-driven negotiation, selection of the best representation for a response is performed by the user agent after receiving
    1091          an initial response from the origin server. Selection is based on a list of the available representations of the response
    1092          included within the header fields or body of the initial response, with each representation identified by its own URI. Selection
    1093          from among the representations can be performed automatically (if the user agent is capable of doing so) or manually by the
    1094          user selecting from a generated (possibly hypertext) menu.
    1095       </p>
    1096       <p id="rfc.section.5.2.p.2">Agent-driven negotiation is advantageous when the response would vary over commonly-used dimensions (such as type, language,
    1097          or encoding), when the origin server is unable to determine a user agent's capabilities from examining the request, and generally
    1098          when public caches are used to distribute server load and reduce network usage.
    1099       </p>
    1100       <p id="rfc.section.5.2.p.3">Agent-driven negotiation suffers from the disadvantage of needing a second request to obtain the best alternate representation.
    1101          This second request is only efficient when caching is used. In addition, this specification does not define any mechanism
    1102          for supporting automatic selection, though it also does not prevent any such mechanism from being developed as an extension
    1103          and used within HTTP/1.1.
    1104       </p>
    1105       <p id="rfc.section.5.2.p.4">This specification defines the 300 (Multiple Choices) and 406 (Not Acceptable) status codes for enabling agent-driven negotiation
    1106          when the server is unwilling or unable to provide a varying response using server-driven negotiation.
    1107       </p>
    1108       <h1 id="rfc.section.6"><a href="#rfc.section.6">6.</a>&nbsp;<a id="header.field.definitions" href="#header.field.definitions">Header Field Definitions</a></h1>
    1109       <p id="rfc.section.6.p.1">This section defines the syntax and semantics of HTTP/1.1 header fields related to the payload of messages.</p>
    1110       <div id="rfc.iref.a.1"></div>
    1111       <div id="rfc.iref.h.1"></div>
    1112       <h2 id="rfc.section.6.1"><a href="#rfc.section.6.1">6.1</a>&nbsp;<a id="header.accept" href="#header.accept">Accept</a></h2>
    1113       <p id="rfc.section.6.1.p.1">The "Accept" header field can be used by user agents to specify response media types that are acceptable. Accept header fields
    1114          can be used to indicate that the request is specifically limited to a small set of desired types, as in the case of a request
    1115          for an in-line image.
    1116       </p>
    1117       <div id="rfc.figure.u.10"></div><pre class="inline"><span id="rfc.iref.g.11"></span><span id="rfc.iref.g.12"></span><span id="rfc.iref.g.13"></span><span id="rfc.iref.g.14"></span>  <a href="#header.accept" class="smpl">Accept</a> = #( <a href="#header.accept" class="smpl">media-range</a> [ <a href="#header.accept" class="smpl">accept-params</a> ] )
    1118  
    1119   <a href="#header.accept" class="smpl">media-range</a>    = ( "*/*"
    1120                    / ( <a href="#media.types" class="smpl">type</a> "/" "*" )
    1121                    / ( <a href="#media.types" class="smpl">type</a> "/" <a href="#media.types" class="smpl">subtype</a> )
    1122                    ) *( <a href="#core.rules" class="smpl">OWS</a> ";" <a href="#core.rules" class="smpl">OWS</a> <a href="#rule.parameter" class="smpl">parameter</a> )
    1123   <a href="#header.accept" class="smpl">accept-params</a>  = <a href="#core.rules" class="smpl">OWS</a> ";" <a href="#core.rules" class="smpl">OWS</a> "q=" <a href="#abnf.dependencies" class="smpl">qvalue</a> *( <a href="#header.accept" class="smpl">accept-ext</a> )
    1124   <a href="#header.accept" class="smpl">accept-ext</a>     = <a href="#core.rules" class="smpl">OWS</a> ";" <a href="#core.rules" class="smpl">OWS</a> <a href="#core.rules" class="smpl">token</a> [ "=" <a href="#core.rules" class="smpl">word</a> ]
    1125 </pre><p id="rfc.section.6.1.p.3">The asterisk "*" character is used to group media types into ranges, with "*/*" indicating all media types and "type/*" indicating
    1126          all subtypes of that type. The media-range <em class="bcp14">MAY</em> include media type parameters that are applicable to that range.
    1127       </p>
    1128       <p id="rfc.section.6.1.p.4">Each media-range <em class="bcp14">MAY</em> be followed by one or more accept-params, beginning with the "q" parameter for indicating a relative quality factor. The first
    1129          "q" parameter (if any) separates the media-range parameter(s) from the accept-params. Quality factors allow the user or user
    1130          agent to indicate the relative degree of preference for that media-range, using the qvalue scale from 0 to 1 (<a href="p1-messaging.html#quality.values" title="Quality Values">Section 4.3.1</a> of <a href="#Part1" id="rfc.xref.Part1.18"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>). The default value is q=1.
    1131       </p>
    1132       <div class="note" id="rfc.section.6.1.p.5">
    1133          <p> <b>Note:</b> Use of the "q" parameter name to separate media type parameters from Accept extension parameters is due to historical practice.
    1134             Although this prevents any media type parameter named "q" from being used with a media range, such an event is believed to
    1135             be unlikely given the lack of any "q" parameters in the IANA media type registry and the rare usage of any media type parameters
    1136             in Accept. Future media types are discouraged from registering any parameter named "q".
    1137          </p>
    1138       </div>
    1139       <p id="rfc.section.6.1.p.6">The example</p>
    1140       <div id="rfc.figure.u.11"></div><pre class="text">  Accept: audio/*; q=0.2, audio/basic
    1141 </pre><p id="rfc.section.6.1.p.8"> <em class="bcp14">SHOULD</em> be interpreted as "I prefer audio/basic, but send me any audio type if it is the best available after an 80% mark-down in
    1142          quality".
    1143       </p>
    1144       <p id="rfc.section.6.1.p.9">A request without any Accept header field implies that the user agent will accept any media type in response. If an Accept
    1145          header field is present in a request and none of the available representations for the response have a media type that is
    1146          listed as acceptable, the origin server <em class="bcp14">MAY</em> either honor the Accept header field by sending a 406 (Not Acceptable) response or disregard the Accept header field by treating
    1147          the response as if it is not subject to content negotiation.
    1148       </p>
    1149       <p id="rfc.section.6.1.p.10">A more elaborate example is</p>
    1150       <div id="rfc.figure.u.12"></div><pre class="text">  Accept: text/plain; q=0.5, text/html,
    1151           text/x-dvi; q=0.8, text/x-c
    1152 </pre><p id="rfc.section.6.1.p.12">Verbally, this would be interpreted as "text/html and text/x-c are the preferred media types, but if they do not exist, then
    1153          send the text/x-dvi representation, and if that does not exist, send the text/plain representation".
    1154       </p>
    1155       <p id="rfc.section.6.1.p.13">Media ranges can be overridden by more specific media ranges or specific media types. If more than one media range applies
    1156          to a given type, the most specific reference has precedence. For example,
    1157       </p>
    1158       <div id="rfc.figure.u.13"></div><pre class="text">  Accept: text/*, text/plain, text/plain;format=flowed, */*
    1159 </pre><p id="rfc.section.6.1.p.15">have the following precedence: </p>
    1160       <ol>
    1161          <li>text/plain;format=flowed</li>
    1162          <li>text/plain</li>
    1163          <li>text/*</li>
    1164          <li>*/*</li>
    1165       </ol>
    1166       <p id="rfc.section.6.1.p.16">The media type quality factor associated with a given type is determined by finding the media range with the highest precedence
    1167          which matches that type. For example,
    1168       </p>
    1169       <div id="rfc.figure.u.14"></div><pre class="text">  Accept: text/*;q=0.3, text/html;q=0.7, text/html;level=1,
    1170           text/html;level=2;q=0.4, */*;q=0.5
    1171 </pre><p id="rfc.section.6.1.p.18">would cause the following values to be associated:</p>
    1172       <div id="rfc.table.u.4">
    1173          <table class="tt full left" cellpadding="3" cellspacing="0">
    1174             <thead>
    1175                <tr>
    1176                   <th>Media Type</th>
    1177                   <th>Quality Value</th>
    1178                </tr>
    1179             </thead>
    1180             <tbody>
    1181                <tr>
    1182                   <td class="left">text/html;level=1</td>
    1183                   <td class="left">1</td>
    1184                </tr>
    1185                <tr>
    1186                   <td class="left">text/html</td>
    1187                   <td class="left">0.7</td>
    1188                </tr>
    1189                <tr>
    1190                   <td class="left">text/plain</td>
    1191                   <td class="left">0.3</td>
    1192                </tr>
    1193                <tr>
    1194                   <td class="left">image/jpeg</td>
    1195                   <td class="left">0.5</td>
    1196                </tr>
    1197                <tr>
    1198                   <td class="left">text/html;level=2</td>
    1199                   <td class="left">0.4</td>
    1200                </tr>
    1201                <tr>
    1202                   <td class="left">text/html;level=3</td>
    1203                   <td class="left">0.7</td>
    1204                </tr>
    1205             </tbody>
    1206          </table>
    1207       </div>
    1208       <p id="rfc.section.6.1.p.19"> <b>Note:</b> A user agent might be provided with a default set of quality values for certain media ranges. However, unless the user agent
    1209          is a closed system which cannot interact with other rendering agents, this default set ought to be configurable by the user.
    1210       </p>
    1211       <div id="rfc.iref.a.2"></div>
    1212       <div id="rfc.iref.h.2"></div>
    1213       <h2 id="rfc.section.6.2"><a href="#rfc.section.6.2">6.2</a>&nbsp;<a id="header.accept-charset" href="#header.accept-charset">Accept-Charset</a></h2>
    1214       <p id="rfc.section.6.2.p.1">The "Accept-Charset" header field can be used by user agents to indicate what character encodings are acceptable in a response
    1215          payload. This field allows clients capable of understanding more comprehensive or special-purpose character encodings to signal
    1216          that capability to a server which is capable of representing documents in those character encodings.
    1217       </p>
    1218       <div id="rfc.figure.u.15"></div><pre class="inline"><span id="rfc.iref.g.15"></span>  <a href="#header.accept-charset" class="smpl">Accept-Charset</a> = 1#( ( <a href="#rule.charset" class="smpl">charset</a> / "*" )
    1219                          [ <a href="#core.rules" class="smpl">OWS</a> ";" <a href="#core.rules" class="smpl">OWS</a> "q=" <a href="#abnf.dependencies" class="smpl">qvalue</a> ] )
    1220 </pre><p id="rfc.section.6.2.p.3">Character encoding values (a.k.a., charsets) are described in <a href="#character.sets" title="Character Encodings (charset)">Section&nbsp;2.1</a>. Each charset <em class="bcp14">MAY</em> be given an associated quality value which represents the user's preference for that charset. The default value is q=1. An
    1221          example is
    1222       </p>
    1223       <div id="rfc.figure.u.16"></div><pre class="text">  Accept-Charset: iso-8859-5, unicode-1-1;q=0.8
    1224 </pre><p id="rfc.section.6.2.p.5">The special value "*", if present in the Accept-Charset field, matches every character encoding which is not mentioned elsewhere
    1225          in the Accept-Charset field. If no "*" is present in an Accept-Charset field, then all character encodings not explicitly
    1226          mentioned get a quality value of 0.
    1227       </p>
    1228       <p id="rfc.section.6.2.p.6">A request without any Accept-Charset header field implies that the user agent will accept any character encoding in response.
    1229          If an Accept-Charset header field is present in a request and none of the available representations for the response have
    1230          a character encoding that is listed as acceptable, the origin server <em class="bcp14">MAY</em> either honor the Accept-Charset header field by sending a 406 (Not Acceptable) response or disregard the Accept-Charset header
    1231          field by treating the response as if it is not subject to content negotiation.
    1232       </p>
    1233       <div id="rfc.iref.a.3"></div>
    1234       <div id="rfc.iref.h.3"></div>
    1235       <h2 id="rfc.section.6.3"><a href="#rfc.section.6.3">6.3</a>&nbsp;<a id="header.accept-encoding" href="#header.accept-encoding">Accept-Encoding</a></h2>
    1236       <p id="rfc.section.6.3.p.1">The "Accept-Encoding" header field can be used by user agents to indicate what response content-codings (<a href="#content.codings" title="Content Codings">Section&nbsp;2.2</a>) are acceptable in the response. An "identity" token is used as a synonym for "no encoding" in order to communicate when
    1237          no encoding is preferred.
    1238       </p>
    1239       <div id="rfc.figure.u.17"></div><pre class="inline"><span id="rfc.iref.g.16"></span><span id="rfc.iref.g.17"></span>  <a href="#header.accept-encoding" class="smpl">Accept-Encoding</a>  = #( <a href="#header.accept-encoding" class="smpl">codings</a> [ <a href="#core.rules" class="smpl">OWS</a> ";" <a href="#core.rules" class="smpl">OWS</a> "q=" <a href="#abnf.dependencies" class="smpl">qvalue</a> ] )
    1240   <a href="#header.accept-encoding" class="smpl">codings</a>          = <a href="#content.codings" class="smpl">content-coding</a> / "identity" / "*"
    1241 </pre><p id="rfc.section.6.3.p.3">Each codings value <em class="bcp14">MAY</em> be given an associated quality value which represents the preference for that encoding. The default value is q=1.
    1242       </p>
    1243       <p id="rfc.section.6.3.p.4">For example,</p>
    1244       <div id="rfc.figure.u.18"></div><pre class="text">  Accept-Encoding: compress, gzip
    1245   Accept-Encoding:
    1246   Accept-Encoding: *
    1247   Accept-Encoding: compress;q=0.5, gzip;q=1.0
    1248   Accept-Encoding: gzip;q=1.0, identity; q=0.5, *;q=0
    1249 </pre><p id="rfc.section.6.3.p.6">A server tests whether a content-coding for a given representation is acceptable, according to an Accept-Encoding field, using
    1250          these rules:
    1251       </p>
    1252       <ol>
    1253          <li>The special "*" symbol in an Accept-Encoding field matches any available content-coding not explicitly listed in the header
    1254             field.
    1255          </li>
    1256          <li>If the representation has no content-coding, then it is acceptable by default unless specifically excluded by the Accept-Encoding
    1257             field stating either "identity;q=0" or "*;q=0" without a more specific entry for "identity".
    1258          </li>
    1259          <li>If the representation's content-coding is one of the content-codings listed in the Accept-Encoding field, then it is acceptable
    1260             unless it is accompanied by a qvalue of 0. (As defined in <a href="p1-messaging.html#quality.values" title="Quality Values">Section 4.3.1</a> of <a href="#Part1" id="rfc.xref.Part1.19"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, a qvalue of 0 means "not acceptable".)
    1261          </li>
    1262          <li>If multiple content-codings are acceptable, then the acceptable content-coding with the highest non-zero qvalue is preferred.</li>
    1263       </ol>
    1264       <p id="rfc.section.6.3.p.7">An Accept-Encoding header field with a combined field-value that is empty implies that the user agent does not want any content-coding
    1265          in response. If an Accept-Encoding header field is present in a request and none of the available representations for the
    1266          response have a content-coding that is listed as acceptable, the origin server <em class="bcp14">SHOULD</em> send a response without any content-coding.
    1267       </p>
    1268       <p id="rfc.section.6.3.p.8">A request without an Accept-Encoding header field implies that the user agent will accept any content-coding in response,
    1269          but a representation without content-coding is preferred for compatibility with the widest variety of user agents.
    1270       </p>
    1271       <div class="note" id="rfc.section.6.3.p.9">
    1272          <p> <b>Note:</b> Most HTTP/1.0 applications do not recognize or obey qvalues associated with content-codings. This means that qvalues will
    1273             not work and are not permitted with x-gzip or x-compress.
    1274          </p>
    1275       </div>
    1276       <div id="rfc.iref.a.4"></div>
    1277       <div id="rfc.iref.h.4"></div>
    1278       <h2 id="rfc.section.6.4"><a href="#rfc.section.6.4">6.4</a>&nbsp;<a id="header.accept-language" href="#header.accept-language">Accept-Language</a></h2>
    1279       <p id="rfc.section.6.4.p.1">The "Accept-Language" header field can be used by user agents to indicate the set of natural languages that are preferred
    1280          in the response. Language tags are defined in <a href="#language.tags" title="Language Tags">Section&nbsp;2.4</a>.
    1281       </p>
    1282       <div id="rfc.figure.u.19"></div><pre class="inline"><span id="rfc.iref.g.18"></span><span id="rfc.iref.g.19"></span>  <a href="#header.accept-language" class="smpl">Accept-Language</a> =
    1283                     1#( <a href="#header.accept-language" class="smpl">language-range</a> [ <a href="#core.rules" class="smpl">OWS</a> ";" <a href="#core.rules" class="smpl">OWS</a> "q=" <a href="#abnf.dependencies" class="smpl">qvalue</a> ] )
    1284   <a href="#header.accept-language" class="smpl">language-range</a>  =
    1285             &lt;language-range, defined in <a href="#RFC4647" id="rfc.xref.RFC4647.1"><cite title="Matching of Language Tags">[RFC4647]</cite></a>, <a href="http://tools.ietf.org/html/rfc4647#section-2.1">Section 2.1</a>&gt;
    1286 </pre><p id="rfc.section.6.4.p.3">Each language-range can be given an associated quality value which represents an estimate of the user's preference for the
    1287          languages specified by that range. The quality value defaults to "q=1". For example,
    1288       </p>
    1289       <div id="rfc.figure.u.20"></div><pre class="text">  Accept-Language: da, en-gb;q=0.8, en;q=0.7
    1290 </pre><p id="rfc.section.6.4.p.5">would mean: "I prefer Danish, but will accept British English and other types of English". (see also <a href="http://tools.ietf.org/html/rfc4647#section-2.3">Section 2.3</a> of <a href="#RFC4647" id="rfc.xref.RFC4647.2"><cite title="Matching of Language Tags">[RFC4647]</cite></a>)
    1291       </p>
    1292       <p id="rfc.section.6.4.p.6">For matching, <a href="http://tools.ietf.org/html/rfc4647#section-3">Section 3</a> of <a href="#RFC4647" id="rfc.xref.RFC4647.3"><cite title="Matching of Language Tags">[RFC4647]</cite></a> defines several matching schemes. Implementations can offer the most appropriate matching scheme for their requirements.
    1293       </p>
    1294       <div class="note" id="rfc.section.6.4.p.7">
    1295          <p> <b>Note:</b> The "Basic Filtering" scheme (<a href="#RFC4647" id="rfc.xref.RFC4647.4"><cite title="Matching of Language Tags">[RFC4647]</cite></a>, <a href="http://tools.ietf.org/html/rfc4647#section-3.3.1">Section 3.3.1</a>) is identical to the matching scheme that was previously defined in <a href="http://tools.ietf.org/html/rfc2616#section-14.4">Section 14.4</a> of <a href="#RFC2616" id="rfc.xref.RFC2616.2"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>.
    1296          </p>
    1297       </div>
    1298       <p id="rfc.section.6.4.p.8">It might be contrary to the privacy expectations of the user to send an Accept-Language header field with the complete linguistic
    1299          preferences of the user in every request. For a discussion of this issue, see <a href="#privacy.issues.connected.to.accept.header.fields" title="Privacy Issues Connected to Accept Header Fields">Section&nbsp;8.1</a>.
    1300       </p>
    1301       <p id="rfc.section.6.4.p.9">As intelligibility is highly dependent on the individual user, it is recommended that client applications make the choice
    1302          of linguistic preference available to the user. If the choice is not made available, then the Accept-Language header field <em class="bcp14">MUST NOT</em> be given in the request.
    1303       </p>
    1304       <div class="note" id="rfc.section.6.4.p.10">
    1305          <p> <b>Note:</b> When making the choice of linguistic preference available to the user, we remind implementors of the fact that users are not
    1306             familiar with the details of language matching as described above, and ought to be provided appropriate guidance. As an example,
    1307             users might assume that on selecting "en-gb", they will be served any kind of English document if British English is not available.
    1308             A user agent might suggest in such a case to add "en" to get the best matching behavior.
    1309          </p>
    1310       </div>
    1311       <div id="rfc.iref.c.6"></div>
    1312       <div id="rfc.iref.h.5"></div>
    1313       <h2 id="rfc.section.6.5"><a href="#rfc.section.6.5">6.5</a>&nbsp;<a id="header.content-encoding" href="#header.content-encoding">Content-Encoding</a></h2>
    1314       <p id="rfc.section.6.5.p.1">The "Content-Encoding" header field indicates what content-codings have been applied to the representation beyond those inherent
    1315          in the media type, and thus what decoding mechanisms have to be applied in order to obtain the media-type referenced by the
    1316          Content-Type header field. Content-Encoding is primarily used to allow a representation to be compressed without losing the
    1317          identity of its underlying media type.
    1318       </p>
    1319       <div id="rfc.figure.u.21"></div><pre class="inline"><span id="rfc.iref.g.20"></span>  <a href="#header.content-encoding" class="smpl">Content-Encoding</a> = 1#<a href="#content.codings" class="smpl">content-coding</a>
    1320 </pre><p id="rfc.section.6.5.p.3">Content codings are defined in <a href="#content.codings" title="Content Codings">Section&nbsp;2.2</a>. An example of its use is
    1321       </p>
    1322       <div id="rfc.figure.u.22"></div><pre class="text">  Content-Encoding: gzip
    1323 </pre><p id="rfc.section.6.5.p.5">The content-coding is a characteristic of the representation. Typically, the representation body is stored with this encoding
    1324          and is only decoded before rendering or analogous usage. However, a transforming proxy <em class="bcp14">MAY</em> modify the content-coding if the new coding is known to be acceptable to the recipient, unless the "no-transform" cache-control
    1325          directive is present in the message.
    1326       </p>
    1327       <p id="rfc.section.6.5.p.6">If the media type includes an inherent encoding, such as a data format that is always compressed, then that encoding would
    1328          not be restated as a Content-Encoding even if it happens to be the same algorithm as one of the content-codings. Such a content-coding
    1329          would only be listed if, for some bizarre reason, it is applied a second time to form the representation. Likewise, an origin
    1330          server might choose to publish the same payload data as multiple representations that differ only in whether the coding is
    1331          defined as part of Content-Type or Content-Encoding, since some user agents will behave differently in their handling of each
    1332          response (e.g., open a "Save as ..." dialog instead of automatic decompression and rendering of content).
    1333       </p>
    1334       <p id="rfc.section.6.5.p.7">A representation that has a content-coding applied to it <em class="bcp14">MUST</em> include a Content-Encoding header field (<a href="#header.content-encoding" id="rfc.xref.header.content-encoding.3" title="Content-Encoding">Section&nbsp;6.5</a>) that lists the content-coding(s) applied.
    1335       </p>
    1336       <p id="rfc.section.6.5.p.8">If multiple encodings have been applied to a representation, the content codings <em class="bcp14">MUST</em> be listed in the order in which they were applied. Additional information about the encoding parameters <em class="bcp14">MAY</em> be provided by other header fields not defined by this specification.
    1337       </p>
    1338       <p id="rfc.section.6.5.p.9">If the content-coding of a representation in a request message is not acceptable to the origin server, the server <em class="bcp14">SHOULD</em> respond with a status code of 415 (Unsupported Media Type).
    1339       </p>
    1340       <div id="rfc.iref.c.7"></div>
    1341       <div id="rfc.iref.h.6"></div>
    1342       <h2 id="rfc.section.6.6"><a href="#rfc.section.6.6">6.6</a>&nbsp;<a id="header.content-language" href="#header.content-language">Content-Language</a></h2>
    1343       <p id="rfc.section.6.6.p.1">The "Content-Language" header field describes the natural language(s) of the intended audience for the representation. Note
    1344          that this might not be equivalent to all the languages used within the representation.
    1345       </p>
    1346       <div id="rfc.figure.u.23"></div><pre class="inline"><span id="rfc.iref.g.21"></span>  <a href="#header.content-language" class="smpl">Content-Language</a> = 1#<a href="#language.tags" class="smpl">language-tag</a>
    1347 </pre><p id="rfc.section.6.6.p.3">Language tags are defined in <a href="#language.tags" title="Language Tags">Section&nbsp;2.4</a>. The primary purpose of Content-Language is to allow a user to identify and differentiate representations according to the
    1348          user's own preferred language. Thus, if the body content is intended only for a Danish-literate audience, the appropriate
    1349          field is
    1350       </p>
    1351       <div id="rfc.figure.u.24"></div><pre class="text">  Content-Language: da
    1352 </pre><p id="rfc.section.6.6.p.5">If no Content-Language is specified, the default is that the content is intended for all language audiences. This might mean
    1353          that the sender does not consider it to be specific to any natural language, or that the sender does not know for which language
    1354          it is intended.
    1355       </p>
    1356       <p id="rfc.section.6.6.p.6">Multiple languages <em class="bcp14">MAY</em> be listed for content that is intended for multiple audiences. For example, a rendition of the "Treaty of Waitangi", presented
    1357          simultaneously in the original Maori and English versions, would call for
    1358       </p>
    1359       <div id="rfc.figure.u.25"></div><pre class="text">  Content-Language: mi, en
    1360 </pre><p id="rfc.section.6.6.p.8">However, just because multiple languages are present within a representation does not mean that it is intended for multiple
    1361          linguistic audiences. An example would be a beginner's language primer, such as "A First Lesson in Latin", which is clearly
    1362          intended to be used by an English-literate audience. In this case, the Content-Language would properly only include "en".
    1363       </p>
    1364       <p id="rfc.section.6.6.p.9">Content-Language <em class="bcp14">MAY</em> be applied to any media type — it is not limited to textual documents.
    1365       </p>
    1366       <div id="rfc.iref.c.8"></div>
    1367       <div id="rfc.iref.h.7"></div>
    1368       <h2 id="rfc.section.6.7"><a href="#rfc.section.6.7">6.7</a>&nbsp;<a id="header.content-location" href="#header.content-location">Content-Location</a></h2>
    1369       <p id="rfc.section.6.7.p.1">The "Content-Location" header field supplies a URI that can be used as a specific identifier for the representation in this
    1370          message. In other words, if one were to perform a GET on this URI at the time of this message's generation, then a 200 response
    1371          would contain the same representation that is enclosed as payload in this message.
    1372       </p>
    1373       <div id="rfc.figure.u.26"></div><pre class="inline"><span id="rfc.iref.g.22"></span>  <a href="#header.content-location" class="smpl">Content-Location</a> = <a href="#abnf.dependencies" class="smpl">absolute-URI</a> / <a href="#abnf.dependencies" class="smpl">partial-URI</a>
    1374 </pre><p id="rfc.section.6.7.p.3">The Content-Location value is not a replacement for the effective Request URI (<a href="p1-messaging.html#effective.request.uri" title="Effective Request URI">Section 5.5</a> of <a href="#Part1" id="rfc.xref.Part1.20"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>). It is representation metadata. It has the same syntax and semantics as the header field of the same name defined for MIME
    1375          body parts in <a href="http://tools.ietf.org/html/rfc2557#section-4">Section 4</a> of <a href="#RFC2557" id="rfc.xref.RFC2557.1"><cite title="MIME Encapsulation of Aggregate Documents, such as HTML (MHTML)">[RFC2557]</cite></a>. However, its appearance in an HTTP message has some special implications for HTTP recipients.
    1376       </p>
    1377       <p id="rfc.section.6.7.p.4">If Content-Location is included in a response message and its value is the same as the effective request URI, then the response
    1378          payload <em class="bcp14">SHOULD</em> be considered a current representation of that resource. For a GET or HEAD request, this is the same as the default semantics
    1379          when no Content-Location is provided by the server. For a state-changing request like PUT or POST, it implies that the server's
    1380          response contains the new representation of that resource, thereby distinguishing it from representations that might only
    1381          report about the action (e.g., "It worked!"). This allows authoring applications to update their local copies without the
    1382          need for a subsequent GET request.
    1383       </p>
    1384       <p id="rfc.section.6.7.p.5">If Content-Location is included in a response message and its value differs from the effective request URI, then the origin
    1385          server is informing recipients that this representation has its own, presumably more specific, identifier. For a GET or HEAD
    1386          request, this is an indication that the effective request URI identifies a resource that is subject to content negotiation
    1387          and the selected representation for this response can also be found at the identified URI. For other methods, such a Content-Location
    1388          indicates that this representation contains a report on the action's status and the same report is available (for future access
    1389          with GET) at the given URI. For example, a purchase transaction made via a POST request might include a receipt document as
    1390          the payload of the 200 response; the Content-Location value provides an identifier for retrieving a copy of that same receipt
    1391          in the future.
    1392       </p>
    1393       <p id="rfc.section.6.7.p.6">If Content-Location is included in a request message, then it <em class="bcp14">MAY</em> be interpreted by the origin server as an indication of where the user agent originally obtained the content of the enclosed
    1394          representation (prior to any subsequent modification of the content by that user agent). In other words, the user agent is
    1395          providing the same representation metadata that it received with the original representation. However, such interpretation <em class="bcp14">MUST NOT</em> be used to alter the semantics of the method requested by the client. For example, if a client makes a PUT request on a negotiated
    1396          resource and the origin server accepts that PUT (without redirection), then the new set of values for that resource is expected
    1397          to be consistent with the one representation supplied in that PUT; the Content-Location cannot be used as a form of reverse
    1398          content selection that identifies only one of the negotiated representations to be updated. If the user agent had wanted the
    1399          latter semantics, it would have applied the PUT directly to the Content-Location URI.
    1400       </p>
    1401       <p id="rfc.section.6.7.p.7">A Content-Location field received in a request message is transitory information that <em class="bcp14">SHOULD NOT</em> be saved with other representation metadata for use in later responses. The Content-Location's value might be saved for use
    1402          in other contexts, such as within source links or other metadata.
    1403       </p>
    1404       <p id="rfc.section.6.7.p.8">A cache cannot assume that a representation with a Content-Location different from the URI used to retrieve it can be used
    1405          to respond to later requests on that Content-Location URI.
    1406       </p>
    1407       <p id="rfc.section.6.7.p.9">If the Content-Location value is a partial URI, the partial URI is interpreted relative to the effective request URI.</p>
    1408       <div id="rfc.iref.c.9"></div>
    1409       <div id="rfc.iref.h.8"></div>
    1410       <h2 id="rfc.section.6.8"><a href="#rfc.section.6.8">6.8</a>&nbsp;<a id="header.content-type" href="#header.content-type">Content-Type</a></h2>
    1411       <p id="rfc.section.6.8.p.1">The "Content-Type" header field indicates the media type of the representation. In the case of responses to the HEAD method,
    1412          the media type is that which would have been sent had the request been a GET.
    1413       </p>
    1414       <div id="rfc.figure.u.27"></div><pre class="inline"><span id="rfc.iref.g.23"></span>  <a href="#header.content-type" class="smpl">Content-Type</a> = <a href="#media.types" class="smpl">media-type</a>
    1415 </pre><p id="rfc.section.6.8.p.3">Media types are defined in <a href="#media.types" title="Media Types">Section&nbsp;2.3</a>. An example of the field is
    1416       </p>
    1417       <div id="rfc.figure.u.28"></div><pre class="text">  Content-Type: text/html; charset=ISO-8859-4
    1418 </pre><p id="rfc.section.6.8.p.5">Further discussion of Content-Type is provided in <a href="#representation.data" title="Representation Data">Section&nbsp;4.2</a>.
    1419       </p>
    1420       <h1 id="rfc.section.7"><a href="#rfc.section.7">7.</a>&nbsp;<a id="IANA.considerations" href="#IANA.considerations">IANA Considerations</a></h1>
    1421       <h2 id="rfc.section.7.1"><a href="#rfc.section.7.1">7.1</a>&nbsp;<a id="header.field.registration" href="#header.field.registration">Header Field Registration</a></h2>
    1422       <p id="rfc.section.7.1.p.1">The Message Header Field Registry located at &lt;<a href="http://www.iana.org/assignments/message-headers/message-header-index.html">http://www.iana.org/assignments/message-headers/message-header-index.html</a>&gt; shall be updated with the permanent registrations below (see <a href="#RFC3864" id="rfc.xref.RFC3864.1"><cite title="Registration Procedures for Message Header Fields">[RFC3864]</cite></a>):
    1423       </p>
    1424       <div id="rfc.table.1">
    1425          <div id="iana.header.registration.table"></div>
    1426          <table class="tt full left" cellpadding="3" cellspacing="0">
    1427             <thead>
    1428                <tr>
    1429                   <th>Header Field Name</th>
    1430                   <th>Protocol</th>
    1431                   <th>Status</th>
    1432                   <th>Reference</th>
    1433                </tr>
    1434             </thead>
    1435             <tbody>
    1436                <tr>
    1437                   <td class="left">Accept</td>
    1438                   <td class="left">http</td>
    1439                   <td class="left">standard</td>
    1440                   <td class="left"> <a href="#header.accept" id="rfc.xref.header.accept.3" title="Accept">Section&nbsp;6.1</a>
    1441                   </td>
    1442                </tr>
    1443                <tr>
    1444                   <td class="left">Accept-Charset</td>
    1445                   <td class="left">http</td>
    1446                   <td class="left">standard</td>
    1447                   <td class="left"> <a href="#header.accept-charset" id="rfc.xref.header.accept-charset.2" title="Accept-Charset">Section&nbsp;6.2</a>
    1448                   </td>
    1449                </tr>
    1450                <tr>
    1451                   <td class="left">Accept-Encoding</td>
    1452                   <td class="left">http</td>
    1453                   <td class="left">standard</td>
    1454                   <td class="left"> <a href="#header.accept-encoding" id="rfc.xref.header.accept-encoding.3" title="Accept-Encoding">Section&nbsp;6.3</a>
    1455                   </td>
    1456                </tr>
    1457                <tr>
    1458                   <td class="left">Accept-Language</td>
    1459                   <td class="left">http</td>
    1460                   <td class="left">standard</td>
    1461                   <td class="left"> <a href="#header.accept-language" id="rfc.xref.header.accept-language.2" title="Accept-Language">Section&nbsp;6.4</a>
    1462                   </td>
    1463                </tr>
    1464                <tr>
    1465                   <td class="left">Content-Encoding</td>
    1466                   <td class="left">http</td>
    1467                   <td class="left">standard</td>
    1468                   <td class="left"> <a href="#header.content-encoding" id="rfc.xref.header.content-encoding.4" title="Content-Encoding">Section&nbsp;6.5</a>
    1469                   </td>
    1470                </tr>
    1471                <tr>
    1472                   <td class="left">Content-Language</td>
    1473                   <td class="left">http</td>
    1474                   <td class="left">standard</td>
    1475                   <td class="left"> <a href="#header.content-language" id="rfc.xref.header.content-language.2" title="Content-Language">Section&nbsp;6.6</a>
    1476                   </td>
    1477                </tr>
    1478                <tr>
    1479                   <td class="left">Content-Location</td>
    1480                   <td class="left">http</td>
    1481                   <td class="left">standard</td>
    1482                   <td class="left"> <a href="#header.content-location" id="rfc.xref.header.content-location.2" title="Content-Location">Section&nbsp;6.7</a>
    1483                   </td>
    1484                </tr>
    1485                <tr>
    1486                   <td class="left">Content-Type</td>
    1487                   <td class="left">http</td>
    1488                   <td class="left">standard</td>
    1489                   <td class="left"> <a href="#header.content-type" id="rfc.xref.header.content-type.3" title="Content-Type">Section&nbsp;6.8</a>
    1490                   </td>
    1491                </tr>
    1492                <tr>
    1493                   <td class="left">MIME-Version</td>
    1494                   <td class="left">http</td>
    1495                   <td class="left">standard</td>
    1496                   <td class="left"> <a href="#mime-version" id="rfc.xref.mime-version.1" title="MIME-Version">Appendix&nbsp;A.1</a>
    1497                   </td>
    1498                </tr>
    1499             </tbody>
    1500          </table>
    1501       </div>
    1502       <p id="rfc.section.7.1.p.2">The change controller is: "IETF (iesg@ietf.org) - Internet Engineering Task Force".</p>
    1503       <h2 id="rfc.section.7.2"><a href="#rfc.section.7.2">7.2</a>&nbsp;<a id="content.coding.registration" href="#content.coding.registration">Content Coding Registry</a></h2>
    1504       <p id="rfc.section.7.2.p.1">The registration procedure for HTTP Content Codings is now defined by <a href="#content.coding.registry" title="Content Coding Registry">Section&nbsp;2.2.1</a> of this document.
    1505       </p>
    1506       <p id="rfc.section.7.2.p.2">The HTTP Content Codings Registry located at &lt;<a href="http://www.iana.org/assignments/http-parameters">http://www.iana.org/assignments/http-parameters</a>&gt; shall be updated with the registration below:
    1507       </p>
    1508       <div id="rfc.table.2">
    1509          <div id="iana.content.coding.registration.table"></div>
    1510          <table class="tt full left" cellpadding="3" cellspacing="0">
    1511             <thead>
    1512                <tr>
    1513                   <th>Name</th>
    1514                   <th>Description</th>
    1515                   <th>Reference</th>
    1516                </tr>
    1517             </thead>
    1518             <tbody>
    1519                <tr>
    1520                   <td class="left">compress</td>
    1521                   <td class="left">UNIX "compress" program method</td>
    1522                   <td class="left"> <a href="p1-messaging.html#compress.coding" title="Compress Coding">Section 4.2.1</a> of <a href="#Part1" id="rfc.xref.Part1.21"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>
    1523                   </td>
    1524                </tr>
    1525                <tr>
    1526                   <td class="left">deflate</td>
    1527                   <td class="left">"deflate" compression mechanism (<a href="#RFC1951" id="rfc.xref.RFC1951.1"><cite title="DEFLATE Compressed Data Format Specification version 1.3">[RFC1951]</cite></a>) used inside the "zlib" data format (<a href="#RFC1950" id="rfc.xref.RFC1950.1"><cite title="ZLIB Compressed Data Format Specification version 3.3">[RFC1950]</cite></a>)
    1528                   </td>
    1529                   <td class="left"> <a href="p1-messaging.html#deflate.coding" title="Deflate Coding">Section 4.2.2</a> of <a href="#Part1" id="rfc.xref.Part1.22"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>
    1530                   </td>
    1531                </tr>
    1532                <tr>
    1533                   <td class="left">gzip</td>
    1534                   <td class="left">Same as GNU zip <a href="#RFC1952" id="rfc.xref.RFC1952.1"><cite title="GZIP file format specification version 4.3">[RFC1952]</cite></a></td>
    1535                   <td class="left"> <a href="p1-messaging.html#gzip.coding" title="Gzip Coding">Section 4.2.3</a> of <a href="#Part1" id="rfc.xref.Part1.23"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>
    1536                   </td>
    1537                </tr>
    1538                <tr>
    1539                   <td class="left">identity</td>
    1540                   <td class="left">reserved (synonym for "no encoding" in Accept-Encoding header field)</td>
    1541                   <td class="left"> <a href="#header.accept-encoding" id="rfc.xref.header.accept-encoding.4" title="Accept-Encoding">Section&nbsp;6.3</a>
    1542                   </td>
    1543                </tr>
    1544             </tbody>
    1545          </table>
    1546       </div>
    1547       <h1 id="rfc.section.8"><a href="#rfc.section.8">8.</a>&nbsp;<a id="security.considerations" href="#security.considerations">Security Considerations</a></h1>
    1548       <p id="rfc.section.8.p.1">This section is meant to inform application developers, information providers, and users of the security limitations in HTTP/1.1
    1549          as described by this document. The discussion does not include definitive solutions to the problems revealed, though it does
    1550          make some suggestions for reducing security risks.
    1551       </p>
    1552       <h2 id="rfc.section.8.1"><a href="#rfc.section.8.1">8.1</a>&nbsp;<a id="privacy.issues.connected.to.accept.header.fields" href="#privacy.issues.connected.to.accept.header.fields">Privacy Issues Connected to Accept Header Fields</a></h2>
    1553       <p id="rfc.section.8.1.p.1">Accept header fields can reveal information about the user to all servers which are accessed. The Accept-Language header field
    1554          in particular can reveal information the user would consider to be of a private nature, because the understanding of particular
    1555          languages is often strongly correlated to the membership of a particular ethnic group. User agents which offer the option
    1556          to configure the contents of an Accept-Language header field to be sent in every request are strongly encouraged to let the
    1557          configuration process include a message which makes the user aware of the loss of privacy involved.
    1558       </p>
    1559       <p id="rfc.section.8.1.p.2">An approach that limits the loss of privacy would be for a user agent to omit the sending of Accept-Language header fields
    1560          by default, and to ask the user whether or not to start sending Accept-Language header fields to a server if it detects, by
    1561          looking for any Vary header fields generated by the server, that such sending could improve the quality of service.
    1562       </p>
    1563       <p id="rfc.section.8.1.p.3">Elaborate user-customized accept header fields sent in every request, in particular if these include quality values, can be
    1564          used by servers as relatively reliable and long-lived user identifiers. Such user identifiers would allow content providers
    1565          to do click-trail tracking, and would allow collaborating content providers to match cross-server click-trails or form submissions
    1566          of individual users. Note that for many users not behind a proxy, the network address of the host running the user agent will
    1567          also serve as a long-lived user identifier. In environments where proxies are used to enhance privacy, user agents ought to
    1568          be conservative in offering accept header configuration options to end users. As an extreme privacy measure, proxies could
    1569          filter the accept header fields in relayed requests. General purpose user agents which provide a high degree of header configurability <em class="bcp14">SHOULD</em> warn users about the loss of privacy which can be involved.
    1570       </p>
    1571       <h1 id="rfc.section.9"><a href="#rfc.section.9">9.</a>&nbsp;<a id="acks" href="#acks">Acknowledgments</a></h1>
    1572       <p id="rfc.section.9.p.1">See <a href="p1-messaging.html#acks" title="Acknowledgments">Section 9</a> of <a href="#Part1" id="rfc.xref.Part1.24"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>.
    1573       </p>
    1574       <h1 id="rfc.references"><a id="rfc.section.10" href="#rfc.section.10">10.</a> References
     498      <h1 id="rfc.section.1" class="np"><a href="#rfc.section.1">1.</a>&nbsp;
    1575499      </h1>
    1576       <h2 id="rfc.references.1"><a href="#rfc.section.10.1" id="rfc.section.10.1">10.1</a> Normative References
     500      <div id="rfc.figure.u.1"></div><pre class="inline">foo = bar
     501</pre><h1 id="rfc.references"><a id="rfc.section.2" href="#rfc.section.2">2.</a> References
     502      </h1>
     503      <h2 id="rfc.references.1"><a href="#rfc.section.2.1" id="rfc.section.2.1">2.1</a> Normative References
    1577504      </h2>
    1578       <table>                           
     505      <table>                     
    1579506         <tr>
    1580507            <td class="reference"><b id="Part1">[Part1]</b></td>
     
    1618545         </tr>
    1619546         <tr>
    1620             <td class="reference"><b id="RFC2045">[RFC2045]</b></td>
    1621             <td class="top"><a href="mailto:ned@innosoft.com" title="Innosoft International, Inc.">Freed, N.</a> and <a href="mailto:nsb@nsb.fv.com" title="First Virtual Holdings">N. Borenstein</a>, “<a href="http://tools.ietf.org/html/rfc2045">Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies</a>”, RFC&nbsp;2045, November&nbsp;1996.
    1622             </td>
    1623          </tr>
    1624          <tr>
    1625             <td class="reference"><b id="RFC2046">[RFC2046]</b></td>
    1626             <td class="top"><a href="mailto:ned@innosoft.com" title="Innosoft International, Inc.">Freed, N.</a> and <a href="mailto:nsb@nsb.fv.com" title="First Virtual Holdings">N. Borenstein</a>, “<a href="http://tools.ietf.org/html/rfc2046">Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types</a>”, RFC&nbsp;2046, November&nbsp;1996.
    1627             </td>
    1628          </tr>
    1629          <tr>
    1630             <td class="reference"><b id="RFC2119">[RFC2119]</b></td>
    1631             <td class="top"><a href="mailto:sob@harvard.edu" title="Harvard University">Bradner, S.</a>, “<a href="http://tools.ietf.org/html/rfc2119">Key words for use in RFCs to Indicate Requirement Levels</a>”, BCP&nbsp;14, RFC&nbsp;2119, March&nbsp;1997.
    1632             </td>
    1633          </tr>
    1634          <tr>
    1635547            <td class="reference"><b id="RFC4647">[RFC4647]</b></td>
    1636548            <td class="top"><a href="mailto:addison@inter-locale.com" title="Yahoo! Inc.">Phillips, A., Ed.</a> and <a href="mailto:mark.davis@macchiato.com" title="Google">M. Davis, Ed.</a>, “<a href="http://tools.ietf.org/html/rfc4647">Matching of Language Tags</a>”, BCP&nbsp;47, RFC&nbsp;4647, September&nbsp;2006.
     
    1648560         </tr>
    1649561      </table>
    1650       <h2 id="rfc.references.2"><a href="#rfc.section.10.2" id="rfc.section.10.2">10.2</a> Informative References
     562      <h2 id="rfc.references.2"><a href="#rfc.section.2.2" id="rfc.section.2.2">2.2</a> Informative References
    1651563      </h2>
    1652       <table>                                 
     564      <table>                       
    1653565         <tr>
    1654566            <td class="reference"><b id="RFC1945">[RFC1945]</b></td>
     
    1657569         </tr>
    1658570         <tr>
    1659             <td class="reference"><b id="RFC2049">[RFC2049]</b></td>
    1660             <td class="top"><a href="mailto:ned@innosoft.com" title="Innosoft International, Inc.">Freed, N.</a> and <a href="mailto:nsb@nsb.fv.com" title="First Virtual Holdings">N. Borenstein</a>, “<a href="http://tools.ietf.org/html/rfc2049">Multipurpose Internet Mail Extensions (MIME) Part Five: Conformance Criteria and Examples</a>”, RFC&nbsp;2049, November&nbsp;1996.
    1661             </td>
    1662          </tr>
    1663          <tr>
    1664571            <td class="reference"><b id="RFC2068">[RFC2068]</b></td>
    1665572            <td class="top"><a href="mailto:fielding@ics.uci.edu" title="University of California, Irvine, Department of Information and Computer Science">Fielding, R.</a>, <a href="mailto:jg@w3.org" title="MIT Laboratory for Computer Science">Gettys, J.</a>, <a href="mailto:mogul@wrl.dec.com" title="Digital Equipment Corporation, Western Research Laboratory">Mogul, J.</a>, <a href="mailto:frystyk@w3.org" title="MIT Laboratory for Computer Science">Nielsen, H.</a>, and <a href="mailto:timbl@w3.org" title="MIT Laboratory for Computer Science">T. Berners-Lee</a>, “<a href="http://tools.ietf.org/html/rfc2068">Hypertext Transfer Protocol -- HTTP/1.1</a>”, RFC&nbsp;2068, January&nbsp;1997.
     
    1667574         </tr>
    1668575         <tr>
    1669             <td class="reference"><b id="RFC2076">[RFC2076]</b></td>
    1670             <td class="top"><a href="mailto:jpalme@dsv.su.se" title="Stockholm University/KTH">Palme, J.</a>, “<a href="http://tools.ietf.org/html/rfc2076">Common Internet Message Headers</a>”, RFC&nbsp;2076, February&nbsp;1997.
    1671             </td>
    1672          </tr>
    1673          <tr>
    1674576            <td class="reference"><b id="RFC2277">[RFC2277]</b></td>
    1675577            <td class="top"><a href="mailto:Harald.T.Alvestrand@uninett.no" title="UNINETT">Alvestrand, H.</a>, “<a href="http://tools.ietf.org/html/rfc2277">IETF Policy on Character Sets and Languages</a>”, BCP&nbsp;18, RFC&nbsp;2277, January&nbsp;1998.
     
    1687589         </tr>
    1688590         <tr>
    1689             <td class="reference"><b id="RFC2557">[RFC2557]</b></td>
    1690             <td class="top"><a href="mailto:jpalme@dsv.su.se" title="Stockholm University and KTH">Palme, F.</a>, <a href="mailto:alexhop@microsoft.com" title="Microsoft Corporation">Hopmann, A.</a>, <a href="mailto:Shelness@lotus.com" title="Lotus Development Corporation">Shelness, N.</a>, and <a href="mailto:stef@nma.com">E. Stefferud</a>, “<a href="http://tools.ietf.org/html/rfc2557">MIME Encapsulation of Aggregate Documents, such as HTML (MHTML)</a>”, RFC&nbsp;2557, March&nbsp;1999.
    1691             </td>
    1692          </tr>
    1693          <tr>
    1694591            <td class="reference"><b id="RFC2616">[RFC2616]</b></td>
    1695592            <td class="top"><a href="mailto:fielding@ics.uci.edu" title="University of California, Irvine">Fielding, R.</a>, <a href="mailto:jg@w3.org" title="W3C">Gettys, J.</a>, <a href="mailto:mogul@wrl.dec.com" title="Compaq Computer Corporation">Mogul, J.</a>, <a href="mailto:frystyk@w3.org" title="MIT Laboratory for Computer Science">Frystyk, H.</a>, <a href="mailto:masinter@parc.xerox.com" title="Xerox Corporation">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, and <a href="mailto:timbl@w3.org" title="W3C">T. Berners-Lee</a>, “<a href="http://tools.ietf.org/html/rfc2616">Hypertext Transfer Protocol -- HTTP/1.1</a>”, RFC&nbsp;2616, June&nbsp;1999.
     
    1719616            <td class="reference"><b id="RFC5322">[RFC5322]</b></td>
    1720617            <td class="top">Resnick, P., “<a href="http://tools.ietf.org/html/rfc5322">Internet Message Format</a>”, RFC&nbsp;5322, October&nbsp;2008.
    1721             </td>
    1722          </tr>
    1723          <tr>
    1724             <td class="reference"><b id="RFC6151">[RFC6151]</b></td>
    1725             <td class="top">Turner, S. and L. Chen, “<a href="http://tools.ietf.org/html/rfc6151">Updated Security Considerations for the MD5 Message-Digest and the HMAC-MD5 Algorithms</a>”, RFC&nbsp;6151, March&nbsp;2011.
    1726             </td>
    1727          </tr>
    1728          <tr>
    1729             <td class="reference"><b id="RFC6266">[RFC6266]</b></td>
    1730             <td class="top"><a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">Reschke, J.</a>, “<a href="http://tools.ietf.org/html/rfc6266">Use of the Content-Disposition Header Field in the Hypertext Transfer Protocol (HTTP)</a>”, RFC&nbsp;6266, June&nbsp;2011.
    1731618            </td>
    1732619         </tr>
     
    1744631               <span class="n hidden"><span class="family-name">Reschke</span><span class="given-name">Julian F.</span></span></span><span class="org vcardline">greenbytes GmbH</span><span class="adr"><span class="street-address vcardline">Hafenweg 16</span><span class="vcardline"><span class="locality">Muenster</span>, <span class="region">NW</span>&nbsp;<span class="postal-code">48155</span></span><span class="country-name vcardline">Germany</span></span><span class="vcardline tel">Phone: <a href="tel:+492512807760"><span class="value">+49 251 2807760</span></a></span><span class="vcardline tel"><span class="type">Fax</span>: <a href="fax:+492512807761"><span class="value">+49 251 2807761</span></a></span><span class="vcardline">Email: <a href="mailto:julian.reschke@greenbytes.de"><span class="email">julian.reschke@greenbytes.de</span></a></span><span class="vcardline">URI: <a href="http://greenbytes.de/tech/webdav/" class="url">http://greenbytes.de/tech/webdav/</a></span></address>
    1745632      </div>
    1746       <h1 id="rfc.section.A" class="np"><a href="#rfc.section.A">A.</a>&nbsp;<a id="differences.between.http.and.mime" href="#differences.between.http.and.mime">Differences between HTTP and MIME</a></h1>
    1747       <p id="rfc.section.A.p.1">HTTP/1.1 uses many of the constructs defined for Internet Mail (<a href="#RFC5322" id="rfc.xref.RFC5322.1"><cite title="Internet Message Format">[RFC5322]</cite></a>) and the Multipurpose Internet Mail Extensions (MIME <a href="#RFC2045" id="rfc.xref.RFC2045.1"><cite title="Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies">[RFC2045]</cite></a>) to allow a message body to be transmitted in an open variety of representations and with extensible mechanisms. However,
    1748          RFC 2045 discusses mail, and HTTP has a few features that are different from those described in MIME. These differences were
    1749          carefully chosen to optimize performance over binary connections, to allow greater freedom in the use of new media types,
    1750          to make date comparisons easier, and to acknowledge the practice of some early HTTP servers and clients.
    1751       </p>
    1752       <p id="rfc.section.A.p.2">This appendix describes specific areas where HTTP differs from MIME. Proxies and gateways to strict MIME environments <em class="bcp14">SHOULD</em> be aware of these differences and provide the appropriate conversions where necessary. Proxies and gateways from MIME environments
    1753          to HTTP also need to be aware of the differences because some conversions might be required.
    1754       </p>
    1755       <div id="rfc.iref.m.1"></div>
    1756       <div id="rfc.iref.h.9"></div>
    1757       <h2 id="rfc.section.A.1"><a href="#rfc.section.A.1">A.1</a>&nbsp;<a id="mime-version" href="#mime-version">MIME-Version</a></h2>
    1758       <p id="rfc.section.A.1.p.1">HTTP is not a MIME-compliant protocol. However, HTTP/1.1 messages <em class="bcp14">MAY</em> include a single MIME-Version header field to indicate what version of the MIME protocol was used to construct the message.
    1759          Use of the MIME-Version header field indicates that the message is in full conformance with the MIME protocol (as defined
    1760          in <a href="#RFC2045" id="rfc.xref.RFC2045.2"><cite title="Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies">[RFC2045]</cite></a>). Proxies/gateways are responsible for ensuring full conformance (where possible) when exporting HTTP messages to strict
    1761          MIME environments.
    1762       </p>
    1763       <div id="rfc.figure.u.29"></div><pre class="inline"><span id="rfc.iref.g.24"></span>  <a href="#mime-version" class="smpl">MIME-Version</a> = 1*<a href="#notation" class="smpl">DIGIT</a> "." 1*<a href="#notation" class="smpl">DIGIT</a>
    1764 </pre><p id="rfc.section.A.1.p.3">MIME version "1.0" is the default for use in HTTP/1.1. However, HTTP/1.1 message parsing and semantics are defined by this
    1765          document and not the MIME specification.
    1766       </p>
    1767       <h2 id="rfc.section.A.2"><a href="#rfc.section.A.2">A.2</a>&nbsp;<a id="conversion.to.canonical.form" href="#conversion.to.canonical.form">Conversion to Canonical Form</a></h2>
    1768       <p id="rfc.section.A.2.p.1">MIME requires that an Internet mail body-part be converted to canonical form prior to being transferred, as described in <a href="http://tools.ietf.org/html/rfc2049#section-4">Section 4</a> of <a href="#RFC2049" id="rfc.xref.RFC2049.1"><cite title="Multipurpose Internet Mail Extensions (MIME) Part Five: Conformance Criteria and Examples">[RFC2049]</cite></a>. <a href="#canonicalization.and.text.defaults" title="Canonicalization and Text Defaults">Section&nbsp;2.3.1</a> of this document describes the forms allowed for subtypes of the "text" media type when transmitted over HTTP. <a href="#RFC2046" id="rfc.xref.RFC2046.4"><cite title="Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types">[RFC2046]</cite></a> requires that content with a type of "text" represent line breaks as CRLF and forbids the use of CR or LF outside of line
    1769          break sequences. HTTP allows CRLF, bare CR, and bare LF to indicate a line break within text content when a message is transmitted
    1770          over HTTP.
    1771       </p>
    1772       <p id="rfc.section.A.2.p.2">Where it is possible, a proxy or gateway from HTTP to a strict MIME environment <em class="bcp14">SHOULD</em> translate all line breaks within the text media types described in <a href="#canonicalization.and.text.defaults" title="Canonicalization and Text Defaults">Section&nbsp;2.3.1</a> of this document to the RFC 2049 canonical form of CRLF. Note, however, that this might be complicated by the presence of
    1773          a Content-Encoding and by the fact that HTTP allows the use of some character encodings which do not use octets 13 and 10
    1774          to represent CR and LF, respectively, as is the case for some multi-byte character encodings.
    1775       </p>
    1776       <p id="rfc.section.A.2.p.3">Conversion will break any cryptographic checksums applied to the original content unless the original content is already in
    1777          canonical form. Therefore, the canonical form is recommended for any content that uses such checksums in HTTP.
    1778       </p>
    1779       <h2 id="rfc.section.A.3"><a href="#rfc.section.A.3">A.3</a>&nbsp;<a id="conversion.of.date.formats" href="#conversion.of.date.formats">Conversion of Date Formats</a></h2>
    1780       <p id="rfc.section.A.3.p.1">HTTP/1.1 uses a restricted set of date formats (<a href="p2-semantics.html#http.date" title="Date/Time Formats">Section 6.1</a> of <a href="#Part2" id="rfc.xref.Part2.2"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>) to simplify the process of date comparison. Proxies and gateways from other protocols <em class="bcp14">SHOULD</em> ensure that any Date header field present in a message conforms to one of the HTTP/1.1 formats and rewrite the date if necessary.
    1781       </p>
    1782       <h2 id="rfc.section.A.4"><a href="#rfc.section.A.4">A.4</a>&nbsp;<a id="introduction.of.content-encoding" href="#introduction.of.content-encoding">Introduction of Content-Encoding</a></h2>
    1783       <p id="rfc.section.A.4.p.1">MIME does not include any concept equivalent to HTTP/1.1's Content-Encoding header field. Since this acts as a modifier on
    1784          the media type, proxies and gateways from HTTP to MIME-compliant protocols <em class="bcp14">MUST</em> either change the value of the Content-Type header field or decode the representation before forwarding the message. (Some
    1785          experimental applications of Content-Type for Internet mail have used a media-type parameter of ";conversions=&lt;content-coding&gt;"
    1786          to perform a function equivalent to Content-Encoding. However, this parameter is not part of the MIME standards).
    1787       </p>
    1788       <div id="rfc.iref.c.10"></div>
    1789       <div id="rfc.iref.h.10"></div>
    1790       <h2 id="rfc.section.A.5"><a href="#rfc.section.A.5">A.5</a>&nbsp;<a id="no.content-transfer-encoding" href="#no.content-transfer-encoding">No Content-Transfer-Encoding</a></h2>
    1791       <p id="rfc.section.A.5.p.1">HTTP does not use the Content-Transfer-Encoding field of MIME. Proxies and gateways from MIME-compliant protocols to HTTP <em class="bcp14">MUST</em> remove any Content-Transfer-Encoding prior to delivering the response message to an HTTP client.
    1792       </p>
    1793       <p id="rfc.section.A.5.p.2">Proxies and gateways from HTTP to MIME-compliant protocols are responsible for ensuring that the message is in the correct
    1794          format and encoding for safe transport on that protocol, where "safe transport" is defined by the limitations of the protocol
    1795          being used. Such a proxy or gateway <em class="bcp14">SHOULD</em> label the data with an appropriate Content-Transfer-Encoding if doing so will improve the likelihood of safe transport over
    1796          the destination protocol.
    1797       </p>
    1798       <h2 id="rfc.section.A.6"><a href="#rfc.section.A.6">A.6</a>&nbsp;<a id="introduction.of.transfer-encoding" href="#introduction.of.transfer-encoding">Introduction of Transfer-Encoding</a></h2>
    1799       <p id="rfc.section.A.6.p.1">HTTP/1.1 introduces the Transfer-Encoding header field (<a href="p1-messaging.html#header.transfer-encoding" title="Transfer-Encoding">Section 3.3.1</a> of <a href="#Part1" id="rfc.xref.Part1.25"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>). Proxies/gateways <em class="bcp14">MUST</em> remove any transfer-coding prior to forwarding a message via a MIME-compliant protocol.
    1800       </p>
    1801       <h2 id="rfc.section.A.7"><a href="#rfc.section.A.7">A.7</a>&nbsp;<a id="mhtml.line.length" href="#mhtml.line.length">MHTML and Line Length Limitations</a></h2>
    1802       <p id="rfc.section.A.7.p.1">HTTP implementations which share code with MHTML <a href="#RFC2557" id="rfc.xref.RFC2557.2"><cite title="MIME Encapsulation of Aggregate Documents, such as HTML (MHTML)">[RFC2557]</cite></a> implementations need to be aware of MIME line length limitations. Since HTTP does not have this limitation, HTTP does not
    1803          fold long lines. MHTML messages being transported by HTTP follow all conventions of MHTML, including line length limitations
    1804          and folding, canonicalization, etc., since HTTP transports all message-bodies as payload (see <a href="#multipart.types" title="Multipart Types">Section&nbsp;2.3.2</a>) and does not interpret the content or any MIME header lines that might be contained therein.
    1805       </p>
    1806       <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a>&nbsp;<a id="additional.features" href="#additional.features">Additional Features</a></h1>
    1807       <p id="rfc.section.B.p.1"> <a href="#RFC1945" id="rfc.xref.RFC1945.1"><cite title="Hypertext Transfer Protocol -- HTTP/1.0">[RFC1945]</cite></a> and <a href="#RFC2068" id="rfc.xref.RFC2068.1"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a> document protocol elements used by some existing HTTP implementations, but not consistently and correctly across most HTTP/1.1
    1808          applications. Implementors are advised to be aware of these features, but cannot rely upon their presence in, or interoperability
    1809          with, other HTTP/1.1 applications. Some of these describe proposed experimental features, and some describe features that
    1810          experimental deployment found lacking that are now addressed in the base HTTP/1.1 specification.
    1811       </p>
    1812       <p id="rfc.section.B.p.2">A number of other header fields, such as Content-Disposition and Title, from SMTP and MIME are also often implemented (see <a href="#RFC6266" id="rfc.xref.RFC6266.1"><cite title="Use of the Content-Disposition Header Field in the Hypertext Transfer Protocol (HTTP)">[RFC6266]</cite></a> and <a href="#RFC2076" id="rfc.xref.RFC2076.1"><cite title="Common Internet Message Headers">[RFC2076]</cite></a>).
    1813       </p>
    1814       <h1 id="rfc.section.C"><a href="#rfc.section.C">C.</a>&nbsp;<a id="changes.from.rfc.2616" href="#changes.from.rfc.2616">Changes from RFC 2616</a></h1>
    1815       <p id="rfc.section.C.p.1">Clarify contexts that charset is used in. (<a href="#character.sets" title="Character Encodings (charset)">Section&nbsp;2.1</a>)
    1816       </p>
    1817       <p id="rfc.section.C.p.2">Registration of Content Codings now requires IETF Review (<a href="#content.coding.registry" title="Content Coding Registry">Section&nbsp;2.2.1</a>)
    1818       </p>
    1819       <p id="rfc.section.C.p.3">Remove the default character encoding for text media types; the default now is whatever the media type definition says. (<a href="#canonicalization.and.text.defaults" title="Canonicalization and Text Defaults">Section&nbsp;2.3.1</a>)
    1820       </p>
    1821       <p id="rfc.section.C.p.4">Change ABNF productions for header fields to only define the field value. (<a href="#header.field.definitions" title="Header Field Definitions">Section&nbsp;6</a>)
    1822       </p>
    1823       <p id="rfc.section.C.p.5">Remove definition of Content-MD5 header field because it was inconsistently implemented with respect to partial responses,
    1824          and also because of known deficiencies in the hash algorithm itself (see <a href="#RFC6151" id="rfc.xref.RFC6151.1"><cite title="Updated Security Considerations for the MD5 Message-Digest and the HMAC-MD5 Algorithms">[RFC6151]</cite></a> for details). (<a href="#header.field.definitions" title="Header Field Definitions">Section&nbsp;6</a>)
    1825       </p>
    1826       <p id="rfc.section.C.p.6">Remove ISO-8859-1 special-casing in Accept-Charset. (<a href="#header.accept-charset" id="rfc.xref.header.accept-charset.3" title="Accept-Charset">Section&nbsp;6.2</a>)
    1827       </p>
    1828       <p id="rfc.section.C.p.7">Remove base URI setting semantics for Content-Location due to poor implementation support, which was caused by too many broken
    1829          servers emitting bogus Content-Location header fields, and also the potentially undesirable effect of potentially breaking
    1830          relative links in content-negotiated resources. (<a href="#header.content-location" id="rfc.xref.header.content-location.3" title="Content-Location">Section&nbsp;6.7</a>)
    1831       </p>
    1832       <p id="rfc.section.C.p.8">Remove reference to non-existant identity transfer-coding value tokens. (<a href="#no.content-transfer-encoding" id="rfc.xref.no.content-transfer-encoding.1" title="No Content-Transfer-Encoding">Appendix&nbsp;A.5</a>)
    1833       </p>
    1834       <p id="rfc.section.C.p.9">Remove discussion of Content-Disposition header field, it is now defined by <a href="#RFC6266" id="rfc.xref.RFC6266.2"><cite title="Use of the Content-Disposition Header Field in the Hypertext Transfer Protocol (HTTP)">[RFC6266]</cite></a>. (<a href="#additional.features" title="Additional Features">Appendix&nbsp;B</a>)
    1835       </p>
    1836       <h1 id="rfc.section.D"><a href="#rfc.section.D">D.</a>&nbsp;<a id="collected.abnf" href="#collected.abnf">Collected ABNF</a></h1>
    1837       <div id="rfc.figure.u.30"></div> <pre class="inline"><a href="#header.accept" class="smpl">Accept</a> = [ ( "," / ( media-range [ accept-params ] ) ) *( OWS "," [
    1838  OWS media-range [ accept-params ] ] ) ]
    1839 <a href="#header.accept-charset" class="smpl">Accept-Charset</a> = *( "," OWS ) ( charset / "*" ) [ OWS ";" OWS "q="
    1840  qvalue ] *( OWS "," [ OWS ( charset / "*" ) [ OWS ";" OWS "q="
    1841  qvalue ] ] )
    1842 <a href="#header.accept-encoding" class="smpl">Accept-Encoding</a> = [ ( "," / ( codings [ OWS ";" OWS "q=" qvalue ] ) )
    1843  *( OWS "," [ OWS codings [ OWS ";" OWS "q=" qvalue ] ] ) ]
    1844 <a href="#header.accept-language" class="smpl">Accept-Language</a> = *( "," OWS ) language-range [ OWS ";" OWS "q="
    1845  qvalue ] *( OWS "," [ OWS language-range [ OWS ";" OWS "q=" qvalue ]
    1846  ] )
    1847 
    1848 <a href="#header.content-encoding" class="smpl">Content-Encoding</a> = *( "," OWS ) content-coding *( OWS "," [ OWS
    1849  content-coding ] )
    1850 <a href="#header.content-language" class="smpl">Content-Language</a> = *( "," OWS ) language-tag *( OWS "," [ OWS
    1851  language-tag ] )
    1852 <a href="#header.content-location" class="smpl">Content-Location</a> = absolute-URI / partial-URI
    1853 <a href="#header.content-type" class="smpl">Content-Type</a> = media-type
    1854 
    1855 <a href="#mime-version" class="smpl">MIME-Version</a> = 1*DIGIT "." 1*DIGIT
    1856 
    1857 <a href="#core.rules" class="smpl">OWS</a> = &lt;OWS, defined in [Part1], Section 3.2.1&gt;
    1858 
    1859 <a href="#abnf.dependencies" class="smpl">absolute-URI</a> = &lt;absolute-URI, defined in [Part1], Section 2.7&gt;
    1860 <a href="#header.accept" class="smpl">accept-ext</a> = OWS ";" OWS token [ "=" word ]
    1861 <a href="#header.accept" class="smpl">accept-params</a> = OWS ";" OWS "q=" qvalue *accept-ext
    1862 <a href="#rule.parameter" class="smpl">attribute</a> = token
    1863 
    1864 <a href="#rule.charset" class="smpl">charset</a> = token
    1865 <a href="#header.accept-encoding" class="smpl">codings</a> = content-coding / "identity" / "*"
    1866 <a href="#content.codings" class="smpl">content-coding</a> = token
    1867 
    1868 <a href="#header.accept-language" class="smpl">language-range</a> = &lt;language-range, defined in [RFC4647], Section 2.1&gt;
    1869 <a href="#language.tags" class="smpl">language-tag</a> = &lt;Language-Tag, defined in [RFC5646], Section 2.1&gt;
    1870 
    1871 <a href="#header.accept" class="smpl">media-range</a> = ( "*/*" / ( type "/*" ) / ( type "/" subtype ) ) *( OWS
    1872  ";" OWS parameter )
    1873 <a href="#media.types" class="smpl">media-type</a> = type "/" subtype *( OWS ";" OWS parameter )
    1874 
    1875 <a href="#rule.parameter" class="smpl">parameter</a> = attribute "=" value
    1876 <a href="#abnf.dependencies" class="smpl">partial-URI</a> = &lt;partial-URI, defined in [Part1], Section 2.7&gt;
    1877 
    1878 <a href="#abnf.dependencies" class="smpl">qvalue</a> = &lt;qvalue, defined in [Part1], Section 4.3.1&gt;
    1879 
    1880 <a href="#media.types" class="smpl">subtype</a> = token
    1881 
    1882 <a href="#core.rules" class="smpl">token</a> = &lt;token, defined in [Part1], Section 3.2.4&gt;
    1883 <a href="#media.types" class="smpl">type</a> = token
    1884 
    1885 <a href="#rule.parameter" class="smpl">value</a> = word
    1886 
    1887 <a href="#core.rules" class="smpl">word</a> = &lt;word, defined in [Part1], Section 3.2.4&gt;
    1888 </pre> <div id="rfc.figure.u.31"></div>
    1889       <p>ABNF diagnostics:</p><pre class="inline">; Accept defined but not used
    1890 ; Accept-Charset defined but not used
    1891 ; Accept-Encoding defined but not used
    1892 ; Accept-Language defined but not used
    1893 ; Content-Encoding defined but not used
    1894 ; Content-Language defined but not used
    1895 ; Content-Location defined but not used
    1896 ; Content-Type defined but not used
    1897 ; MIME-Version defined but not used
    1898 </pre><h1 id="rfc.section.E"><a href="#rfc.section.E">E.</a>&nbsp;<a id="change.log" href="#change.log">Change Log (to be removed by RFC Editor before publication)</a></h1>
    1899       <h2 id="rfc.section.E.1"><a href="#rfc.section.E.1">E.1</a>&nbsp;Since RFC 2616
    1900       </h2>
    1901       <p id="rfc.section.E.1.p.1">Extracted relevant partitions from <a href="#RFC2616" id="rfc.xref.RFC2616.3"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>.
    1902       </p>
    1903       <h2 id="rfc.section.E.2"><a href="#rfc.section.E.2">E.2</a>&nbsp;Since draft-ietf-httpbis-p3-payload-00
    1904       </h2>
    1905       <p id="rfc.section.E.2.p.1">Closed issues: </p>
    1906       <ul>
    1907          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/8">http://tools.ietf.org/wg/httpbis/trac/ticket/8</a>&gt;: "Media Type Registrations" (&lt;<a href="http://purl.org/NET/http-errata#media-reg">http://purl.org/NET/http-errata#media-reg</a>&gt;)
    1908          </li>
    1909          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/14">http://tools.ietf.org/wg/httpbis/trac/ticket/14</a>&gt;: "Clarification regarding quoting of charset values" (&lt;<a href="http://purl.org/NET/http-errata#charactersets">http://purl.org/NET/http-errata#charactersets</a>&gt;)
    1910          </li>
    1911          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/16">http://tools.ietf.org/wg/httpbis/trac/ticket/16</a>&gt;: "Remove 'identity' token references" (&lt;<a href="http://purl.org/NET/http-errata#identity">http://purl.org/NET/http-errata#identity</a>&gt;)
    1912          </li>
    1913          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/25">http://tools.ietf.org/wg/httpbis/trac/ticket/25</a>&gt;: "Accept-Encoding BNF"
    1914          </li>
    1915          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/35">http://tools.ietf.org/wg/httpbis/trac/ticket/35</a>&gt;: "Normative and Informative references"
    1916          </li>
    1917          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/46">http://tools.ietf.org/wg/httpbis/trac/ticket/46</a>&gt;: "RFC1700 references"
    1918          </li>
    1919          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/55">http://tools.ietf.org/wg/httpbis/trac/ticket/55</a>&gt;: "Updating to RFC4288"
    1920          </li>
    1921          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/65">http://tools.ietf.org/wg/httpbis/trac/ticket/65</a>&gt;: "Informative references"
    1922          </li>
    1923          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/66">http://tools.ietf.org/wg/httpbis/trac/ticket/66</a>&gt;: "ISO-8859-1 Reference"
    1924          </li>
    1925          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/68">http://tools.ietf.org/wg/httpbis/trac/ticket/68</a>&gt;: "Encoding References Normative"
    1926          </li>
    1927          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/86">http://tools.ietf.org/wg/httpbis/trac/ticket/86</a>&gt;: "Normative up-to-date references"
    1928          </li>
    1929       </ul>
    1930       <h2 id="rfc.section.E.3"><a href="#rfc.section.E.3">E.3</a>&nbsp;Since draft-ietf-httpbis-p3-payload-01
    1931       </h2>
    1932       <p id="rfc.section.E.3.p.1">Ongoing work on ABNF conversion (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>&gt;):
    1933       </p>
    1934       <ul>
    1935          <li>Add explicit references to BNF syntax and rules imported from other parts of the specification.</li>
    1936       </ul>
    1937       <h2 id="rfc.section.E.4"><a href="#rfc.section.E.4">E.4</a>&nbsp;<a id="changes.since.02" href="#changes.since.02">Since draft-ietf-httpbis-p3-payload-02</a></h2>
    1938       <p id="rfc.section.E.4.p.1">Closed issues: </p>
    1939       <ul>
    1940          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/67">http://tools.ietf.org/wg/httpbis/trac/ticket/67</a>&gt;: "Quoting Charsets"
    1941          </li>
    1942          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/105">http://tools.ietf.org/wg/httpbis/trac/ticket/105</a>&gt;: "Classification for Allow header"
    1943          </li>
    1944          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/115">http://tools.ietf.org/wg/httpbis/trac/ticket/115</a>&gt;: "missing default for qvalue in description of Accept-Encoding"
    1945          </li>
    1946       </ul>
    1947       <p id="rfc.section.E.4.p.2">Ongoing work on IANA Message Header Field Registration (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/40">http://tools.ietf.org/wg/httpbis/trac/ticket/40</a>&gt;):
    1948       </p>
    1949       <ul>
    1950          <li>Reference RFC 3984, and update header field registrations for headers defined in this document.</li>
    1951       </ul>
    1952       <h2 id="rfc.section.E.5"><a href="#rfc.section.E.5">E.5</a>&nbsp;<a id="changes.since.03" href="#changes.since.03">Since draft-ietf-httpbis-p3-payload-03</a></h2>
    1953       <p id="rfc.section.E.5.p.1">Closed issues: </p>
    1954       <ul>
    1955          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/67">http://tools.ietf.org/wg/httpbis/trac/ticket/67</a>&gt;: "Quoting Charsets"
    1956          </li>
    1957          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/113">http://tools.ietf.org/wg/httpbis/trac/ticket/113</a>&gt;: "language tag matching (Accept-Language) vs RFC4647"
    1958          </li>
    1959          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/121">http://tools.ietf.org/wg/httpbis/trac/ticket/121</a>&gt;: "RFC 1806 has been replaced by RFC2183"
    1960          </li>
    1961       </ul>
    1962       <p id="rfc.section.E.5.p.2">Other changes: </p>
    1963       <ul>
    1964          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/68">http://tools.ietf.org/wg/httpbis/trac/ticket/68</a>&gt;: "Encoding References Normative" — rephrase the annotation and reference BCP97.
    1965          </li>
    1966       </ul>
    1967       <h2 id="rfc.section.E.6"><a href="#rfc.section.E.6">E.6</a>&nbsp;<a id="changes.since.04" href="#changes.since.04">Since draft-ietf-httpbis-p3-payload-04</a></h2>
    1968       <p id="rfc.section.E.6.p.1">Closed issues: </p>
    1969       <ul>
    1970          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/132">http://tools.ietf.org/wg/httpbis/trac/ticket/132</a>&gt;: "RFC 2822 is updated by RFC 5322"
    1971          </li>
    1972       </ul>
    1973       <p id="rfc.section.E.6.p.2">Ongoing work on ABNF conversion (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>&gt;):
    1974       </p>
    1975       <ul>
    1976          <li>Use "/" instead of "|" for alternatives.</li>
    1977          <li>Introduce new ABNF rules for "bad" whitespace ("BWS"), optional whitespace ("OWS") and required whitespace ("RWS").</li>
    1978          <li>Rewrite ABNFs to spell out whitespace rules, factor out header field value format definitions.</li>
    1979       </ul>
    1980       <h2 id="rfc.section.E.7"><a href="#rfc.section.E.7">E.7</a>&nbsp;<a id="changes.since.05" href="#changes.since.05">Since draft-ietf-httpbis-p3-payload-05</a></h2>
    1981       <p id="rfc.section.E.7.p.1">Closed issues: </p>
    1982       <ul>
    1983          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/118">http://tools.ietf.org/wg/httpbis/trac/ticket/118</a>&gt;: "Join "Differences Between HTTP Entities and RFC 2045 Entities"?"
    1984          </li>
    1985       </ul>
    1986       <p id="rfc.section.E.7.p.2">Final work on ABNF conversion (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>&gt;):
    1987       </p>
    1988       <ul>
    1989          <li>Add appendix containing collected and expanded ABNF, reorganize ABNF introduction.</li>
    1990       </ul>
    1991       <p id="rfc.section.E.7.p.3">Other changes: </p>
    1992       <ul>
    1993          <li>Move definition of quality values into Part 1.</li>
    1994       </ul>
    1995       <h2 id="rfc.section.E.8"><a href="#rfc.section.E.8">E.8</a>&nbsp;<a id="changes.since.06" href="#changes.since.06">Since draft-ietf-httpbis-p3-payload-06</a></h2>
    1996       <p id="rfc.section.E.8.p.1">Closed issues: </p>
    1997       <ul>
    1998          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/80">http://tools.ietf.org/wg/httpbis/trac/ticket/80</a>&gt;: "Content-Location isn't special"
    1999          </li>
    2000          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/155">http://tools.ietf.org/wg/httpbis/trac/ticket/155</a>&gt;: "Content Sniffing"
    2001          </li>
    2002       </ul>
    2003       <h2 id="rfc.section.E.9"><a href="#rfc.section.E.9">E.9</a>&nbsp;<a id="changes.since.07" href="#changes.since.07">Since draft-ietf-httpbis-p3-payload-07</a></h2>
    2004       <p id="rfc.section.E.9.p.1">Closed issues: </p>
    2005       <ul>
    2006          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/13">http://tools.ietf.org/wg/httpbis/trac/ticket/13</a>&gt;: "Updated reference for language tags"
    2007          </li>
    2008          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/110">http://tools.ietf.org/wg/httpbis/trac/ticket/110</a>&gt;: "Clarify rules for determining what entities a response carries"
    2009          </li>
    2010          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/154">http://tools.ietf.org/wg/httpbis/trac/ticket/154</a>&gt;: "Content-Location base-setting problems"
    2011          </li>
    2012          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/155">http://tools.ietf.org/wg/httpbis/trac/ticket/155</a>&gt;: "Content Sniffing"
    2013          </li>
    2014          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/188">http://tools.ietf.org/wg/httpbis/trac/ticket/188</a>&gt;: "pick IANA policy (RFC5226) for Transfer Coding / Content Coding"
    2015          </li>
    2016          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/189">http://tools.ietf.org/wg/httpbis/trac/ticket/189</a>&gt;: "move definitions of gzip/deflate/compress to part 1"
    2017          </li>
    2018       </ul>
    2019       <p id="rfc.section.E.9.p.2">Partly resolved issues: </p>
    2020       <ul>
    2021          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/148">http://tools.ietf.org/wg/httpbis/trac/ticket/148</a>&gt;: "update IANA requirements wrt Transfer-Coding values" (add the IANA Considerations subsection)
    2022          </li>
    2023          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/149">http://tools.ietf.org/wg/httpbis/trac/ticket/149</a>&gt;: "update IANA requirements wrt Content-Coding values" (add the IANA Considerations subsection)
    2024          </li>
    2025       </ul>
    2026       <h2 id="rfc.section.E.10"><a href="#rfc.section.E.10">E.10</a>&nbsp;<a id="changes.since.08" href="#changes.since.08">Since draft-ietf-httpbis-p3-payload-08</a></h2>
    2027       <p id="rfc.section.E.10.p.1">Closed issues: </p>
    2028       <ul>
    2029          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/81">http://tools.ietf.org/wg/httpbis/trac/ticket/81</a>&gt;: "Content Negotiation for media types"
    2030          </li>
    2031          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/181">http://tools.ietf.org/wg/httpbis/trac/ticket/181</a>&gt;: "Accept-Language: which RFC4647 filtering?"
    2032          </li>
    2033       </ul>
    2034       <h2 id="rfc.section.E.11"><a href="#rfc.section.E.11">E.11</a>&nbsp;<a id="changes.since.09" href="#changes.since.09">Since draft-ietf-httpbis-p3-payload-09</a></h2>
    2035       <p id="rfc.section.E.11.p.1">Closed issues: </p>
    2036       <ul>
    2037          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/122">http://tools.ietf.org/wg/httpbis/trac/ticket/122</a>&gt;: "MIME-Version not listed in P1, general header fields"
    2038          </li>
    2039          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/143">http://tools.ietf.org/wg/httpbis/trac/ticket/143</a>&gt;: "IANA registry for content/transfer encodings"
    2040          </li>
    2041          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/155">http://tools.ietf.org/wg/httpbis/trac/ticket/155</a>&gt;: "Content Sniffing"
    2042          </li>
    2043          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/200">http://tools.ietf.org/wg/httpbis/trac/ticket/200</a>&gt;: "use of term "word" when talking about header structure"
    2044          </li>
    2045       </ul>
    2046       <p id="rfc.section.E.11.p.2">Partly resolved issues: </p>
    2047       <ul>
    2048          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/196">http://tools.ietf.org/wg/httpbis/trac/ticket/196</a>&gt;: "Term for the requested resource's URI"
    2049          </li>
    2050       </ul>
    2051       <h2 id="rfc.section.E.12"><a href="#rfc.section.E.12">E.12</a>&nbsp;<a id="changes.since.10" href="#changes.since.10">Since draft-ietf-httpbis-p3-payload-10</a></h2>
    2052       <p id="rfc.section.E.12.p.1">Closed issues: </p>
    2053       <ul>
    2054          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/69">http://tools.ietf.org/wg/httpbis/trac/ticket/69</a>&gt;: "Clarify 'Requested Variant'"
    2055          </li>
    2056          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/80">http://tools.ietf.org/wg/httpbis/trac/ticket/80</a>&gt;: "Content-Location isn't special"
    2057          </li>
    2058          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/90">http://tools.ietf.org/wg/httpbis/trac/ticket/90</a>&gt;: "Delimiting messages with multipart/byteranges"
    2059          </li>
    2060          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/109">http://tools.ietf.org/wg/httpbis/trac/ticket/109</a>&gt;: "Clarify entity / representation / variant terminology"
    2061          </li>
    2062          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/136">http://tools.ietf.org/wg/httpbis/trac/ticket/136</a>&gt;: "confusing req. language for Content-Location"
    2063          </li>
    2064          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/167">http://tools.ietf.org/wg/httpbis/trac/ticket/167</a>&gt;: "Content-Location on 304 responses"
    2065          </li>
    2066          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/183">http://tools.ietf.org/wg/httpbis/trac/ticket/183</a>&gt;: "'requested resource' in content-encoding definition"
    2067          </li>
    2068          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/220">http://tools.ietf.org/wg/httpbis/trac/ticket/220</a>&gt;: "consider removing the 'changes from 2068' sections"
    2069          </li>
    2070       </ul>
    2071       <p id="rfc.section.E.12.p.2">Partly resolved issues: </p>
    2072       <ul>
    2073          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/178">http://tools.ietf.org/wg/httpbis/trac/ticket/178</a>&gt;: "Content-MD5 and partial responses"
    2074          </li>
    2075       </ul>
    2076       <h2 id="rfc.section.E.13"><a href="#rfc.section.E.13">E.13</a>&nbsp;<a id="changes.since.11" href="#changes.since.11">Since draft-ietf-httpbis-p3-payload-11</a></h2>
    2077       <p id="rfc.section.E.13.p.1">Closed issues: </p>
    2078       <ul>
    2079          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/123">http://tools.ietf.org/wg/httpbis/trac/ticket/123</a>&gt;: "Factor out Content-Disposition"
    2080          </li>
    2081       </ul>
    2082       <h2 id="rfc.section.E.14"><a href="#rfc.section.E.14">E.14</a>&nbsp;<a id="changes.since.12" href="#changes.since.12">Since draft-ietf-httpbis-p3-payload-12</a></h2>
    2083       <p id="rfc.section.E.14.p.1">Closed issues: </p>
    2084       <ul>
    2085          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/224">http://tools.ietf.org/wg/httpbis/trac/ticket/224</a>&gt;: "Header Classification"
    2086          </li>
    2087          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/276">http://tools.ietf.org/wg/httpbis/trac/ticket/276</a>&gt;: "untangle ABNFs for header fields"
    2088          </li>
    2089          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/277">http://tools.ietf.org/wg/httpbis/trac/ticket/277</a>&gt;: "potentially misleading MAY in media-type def"
    2090          </li>
    2091       </ul>
    2092       <h2 id="rfc.section.E.15"><a href="#rfc.section.E.15">E.15</a>&nbsp;<a id="changes.since.13" href="#changes.since.13">Since draft-ietf-httpbis-p3-payload-13</a></h2>
    2093       <p id="rfc.section.E.15.p.1">Closed issues: </p>
    2094       <ul>
    2095          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/20">http://tools.ietf.org/wg/httpbis/trac/ticket/20</a>&gt;: "Default charsets for text media types"
    2096          </li>
    2097          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/178">http://tools.ietf.org/wg/httpbis/trac/ticket/178</a>&gt;: "Content-MD5 and partial responses"
    2098          </li>
    2099          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/276">http://tools.ietf.org/wg/httpbis/trac/ticket/276</a>&gt;: "untangle ABNFs for header fields"
    2100          </li>
    2101          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/281">http://tools.ietf.org/wg/httpbis/trac/ticket/281</a>&gt;: "confusing undefined parameter in media range example"
    2102          </li>
    2103       </ul>
    2104       <h2 id="rfc.section.E.16"><a href="#rfc.section.E.16">E.16</a>&nbsp;<a id="changes.since.14" href="#changes.since.14">Since draft-ietf-httpbis-p3-payload-14</a></h2>
    2105       <p id="rfc.section.E.16.p.1">None.</p>
    2106       <h2 id="rfc.section.E.17"><a href="#rfc.section.E.17">E.17</a>&nbsp;<a id="changes.since.15" href="#changes.since.15">Since draft-ietf-httpbis-p3-payload-15</a></h2>
    2107       <p id="rfc.section.E.17.p.1">Closed issues: </p>
    2108       <ul>
    2109          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/285">http://tools.ietf.org/wg/httpbis/trac/ticket/285</a>&gt;: "Strength of requirements on Accept re: 406"
    2110          </li>
    2111       </ul>
    2112       <h2 id="rfc.section.E.18"><a href="#rfc.section.E.18">E.18</a>&nbsp;<a id="changes.since.16" href="#changes.since.16">Since draft-ietf-httpbis-p3-payload-16</a></h2>
    2113       <p id="rfc.section.E.18.p.1">Closed issues: </p>
    2114       <ul>
    2115          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/186">http://tools.ietf.org/wg/httpbis/trac/ticket/186</a>&gt;: "Document HTTP's error-handling philosophy"
    2116          </li>
    2117       </ul>
    2118       <h2 id="rfc.section.E.19"><a href="#rfc.section.E.19">E.19</a>&nbsp;<a id="changes.since.17" href="#changes.since.17">Since draft-ietf-httpbis-p3-payload-17</a></h2>
    2119       <p id="rfc.section.E.19.p.1">Closed issues: </p>
    2120       <ul>
    2121          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/323">http://tools.ietf.org/wg/httpbis/trac/ticket/323</a>&gt;: "intended maturity level vs normative references"
    2122          </li>
    2123       </ul>
    2124       <h2 id="rfc.section.E.20"><a href="#rfc.section.E.20">E.20</a>&nbsp;<a id="changes.since.18" href="#changes.since.18">Since draft-ietf-httpbis-p3-payload-18</a></h2>
    2125       <p id="rfc.section.E.20.p.1">Closed issues: </p>
    2126       <ul>
    2127          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/330">http://tools.ietf.org/wg/httpbis/trac/ticket/330</a>&gt;: "is ETag a representation header field?"
    2128          </li>
    2129          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/338">http://tools.ietf.org/wg/httpbis/trac/ticket/338</a>&gt;: "Content-Location doesn't constrain the cardinality of representations"
    2130          </li>
    2131          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/346">http://tools.ietf.org/wg/httpbis/trac/ticket/346</a>&gt;: "make IANA policy definitions consistent"
    2132          </li>
    2133       </ul>
    2134       <h2 id="rfc.section.E.21"><a href="#rfc.section.E.21">E.21</a>&nbsp;<a id="changes.since.19" href="#changes.since.19">Since draft-ietf-httpbis-p3-payload-19</a></h2>
    2135       <p id="rfc.section.E.21.p.1">None yet.</p>
    2136       <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1>
    2137       <p class="noprint"><a href="#rfc.index.A">A</a> <a href="#rfc.index.C">C</a> <a href="#rfc.index.D">D</a> <a href="#rfc.index.G">G</a> <a href="#rfc.index.H">H</a> <a href="#rfc.index.M">M</a> <a href="#rfc.index.P">P</a> <a href="#rfc.index.R">R</a> <a href="#rfc.index.S">S</a>
    2138       </p>
    2139       <div class="print2col">
    2140          <ul class="ind">
    2141             <li><a id="rfc.index.A" href="#rfc.index.A"><b>A</b></a><ul>
    2142                   <li>Accept header field&nbsp;&nbsp;<a href="#rfc.xref.header.accept.1">2.3</a>, <a href="#rfc.xref.header.accept.2">5.1</a>, <a href="#rfc.iref.a.1"><b>6.1</b></a>, <a href="#rfc.xref.header.accept.3">7.1</a></li>
    2143                   <li>Accept-Charset header field&nbsp;&nbsp;<a href="#rfc.xref.header.accept-charset.1">5.1</a>, <a href="#rfc.iref.a.2"><b>6.2</b></a>, <a href="#rfc.xref.header.accept-charset.2">7.1</a>, <a href="#rfc.xref.header.accept-charset.3">C</a></li>
    2144                   <li>Accept-Encoding header field&nbsp;&nbsp;<a href="#rfc.xref.header.accept-encoding.1">2.2</a>, <a href="#rfc.xref.header.accept-encoding.2">5.1</a>, <a href="#rfc.iref.a.3"><b>6.3</b></a>, <a href="#rfc.xref.header.accept-encoding.3">7.1</a>, <a href="#rfc.xref.header.accept-encoding.4">7.2</a></li>
    2145                   <li>Accept-Language header field&nbsp;&nbsp;<a href="#rfc.xref.header.accept-language.1">5.1</a>, <a href="#rfc.iref.a.4"><b>6.4</b></a>, <a href="#rfc.xref.header.accept-language.2">7.1</a></li>
    2146                </ul>
    2147             </li>
    2148             <li><a id="rfc.index.C" href="#rfc.index.C"><b>C</b></a><ul>
    2149                   <li>Coding Format&nbsp;&nbsp;
    2150                      <ul>
    2151                         <li>compress&nbsp;&nbsp;<a href="#rfc.iref.c.3">2.2</a></li>
    2152                         <li>deflate&nbsp;&nbsp;<a href="#rfc.iref.c.4">2.2</a></li>
    2153                         <li>gzip&nbsp;&nbsp;<a href="#rfc.iref.c.5">2.2</a></li>
    2154                      </ul>
    2155                   </li>
    2156                   <li>compress (Coding Format)&nbsp;&nbsp;<a href="#rfc.iref.c.2">2.2</a></li>
    2157                   <li>content negotiation&nbsp;&nbsp;<a href="#rfc.iref.c.1">1.1</a></li>
    2158                   <li>Content-Encoding header field&nbsp;&nbsp;<a href="#rfc.xref.header.content-encoding.1">2.2</a>, <a href="#rfc.xref.header.content-encoding.2">4.1</a>, <a href="#rfc.iref.c.6"><b>6.5</b></a>, <a href="#rfc.xref.header.content-encoding.3">6.5</a>, <a href="#rfc.xref.header.content-encoding.4">7.1</a></li>
    2159                   <li>Content-Language header field&nbsp;&nbsp;<a href="#rfc.xref.header.content-language.1">4.1</a>, <a href="#rfc.iref.c.7"><b>6.6</b></a>, <a href="#rfc.xref.header.content-language.2">7.1</a></li>
    2160                   <li>Content-Location header field&nbsp;&nbsp;<a href="#rfc.xref.header.content-location.1">4.1</a>, <a href="#rfc.iref.c.8"><b>6.7</b></a>, <a href="#rfc.xref.header.content-location.2">7.1</a>, <a href="#rfc.xref.header.content-location.3">C</a></li>
    2161                   <li>Content-Transfer-Encoding header field&nbsp;&nbsp;<a href="#rfc.iref.c.10">A.5</a>, <a href="#rfc.xref.no.content-transfer-encoding.1">C</a></li>
    2162                   <li>Content-Type header field&nbsp;&nbsp;<a href="#rfc.xref.header.content-type.1">2.3</a>, <a href="#rfc.xref.header.content-type.2">4.1</a>, <a href="#rfc.iref.c.9"><b>6.8</b></a>, <a href="#rfc.xref.header.content-type.3">7.1</a></li>
    2163                </ul>
    2164             </li>
    2165             <li><a id="rfc.index.D" href="#rfc.index.D"><b>D</b></a><ul>
    2166                   <li>deflate (Coding Format)&nbsp;&nbsp;<a href="#rfc.iref.d.1">2.2</a></li>
    2167                </ul>
    2168             </li>
    2169             <li><a id="rfc.index.G" href="#rfc.index.G"><b>G</b></a><ul>
    2170                   <li><tt>Grammar</tt>&nbsp;&nbsp;
    2171                      <ul>
    2172                         <li><tt>Accept</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.11"><b>6.1</b></a></li>
    2173                         <li><tt>Accept-Charset</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.15"><b>6.2</b></a></li>
    2174                         <li><tt>Accept-Encoding</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.16"><b>6.3</b></a></li>
    2175                         <li><tt>accept-ext</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.14"><b>6.1</b></a></li>
    2176                         <li><tt>Accept-Language</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.18"><b>6.4</b></a></li>
    2177                         <li><tt>accept-params</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.13"><b>6.1</b></a></li>
    2178                         <li><tt>attribute</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.8"><b>2.3</b></a></li>
    2179                         <li><tt>charset</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.1"><b>2.1</b></a></li>
    2180                         <li><tt>codings</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.17"><b>6.3</b></a></li>
    2181                         <li><tt>content-coding</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.2"><b>2.2</b></a></li>
    2182                         <li><tt>Content-Encoding</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.20"><b>6.5</b></a></li>
    2183                         <li><tt>Content-Language</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.21"><b>6.6</b></a></li>
    2184                         <li><tt>Content-Location</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.22"><b>6.7</b></a></li>
    2185                         <li><tt>Content-Type</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.23"><b>6.8</b></a></li>
    2186                         <li><tt>language-range</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.19"><b>6.4</b></a></li>
    2187                         <li><tt>language-tag</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.10"><b>2.4</b></a></li>
    2188                         <li><tt>media-range</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.12"><b>6.1</b></a></li>
    2189                         <li><tt>media-type</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.4"><b>2.3</b></a></li>
    2190                         <li><tt>MIME-Version</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.24"><b>A.1</b></a></li>
    2191                         <li><tt>parameter</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.7"><b>2.3</b></a></li>
    2192                         <li><tt>subtype</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.6"><b>2.3</b></a></li>
    2193                         <li><tt>type</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.5"><b>2.3</b></a></li>
    2194                         <li><tt>value</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.9"><b>2.3</b></a></li>
    2195                      </ul>
    2196                   </li>
    2197                   <li>gzip (Coding Format)&nbsp;&nbsp;<a href="#rfc.iref.g.3">2.2</a></li>
    2198                </ul>
    2199             </li>
    2200             <li><a id="rfc.index.H" href="#rfc.index.H"><b>H</b></a><ul>
    2201                   <li>Header Fields&nbsp;&nbsp;
    2202                      <ul>
    2203                         <li>Accept&nbsp;&nbsp;<a href="#rfc.xref.header.accept.1">2.3</a>, <a href="#rfc.xref.header.accept.2">5.1</a>, <a href="#rfc.iref.h.1"><b>6.1</b></a>, <a href="#rfc.xref.header.accept.3">7.1</a></li>
    2204                         <li>Accept-Charset&nbsp;&nbsp;<a href="#rfc.xref.header.accept-charset.1">5.1</a>, <a href="#rfc.iref.h.2"><b>6.2</b></a>, <a href="#rfc.xref.header.accept-charset.2">7.1</a>, <a href="#rfc.xref.header.accept-charset.3">C</a></li>
    2205                         <li>Accept-Encoding&nbsp;&nbsp;<a href="#rfc.xref.header.accept-encoding.1">2.2</a>, <a href="#rfc.xref.header.accept-encoding.2">5.1</a>, <a href="#rfc.iref.h.3"><b>6.3</b></a>, <a href="#rfc.xref.header.accept-encoding.3">7.1</a>, <a href="#rfc.xref.header.accept-encoding.4">7.2</a></li>
    2206                         <li>Accept-Language&nbsp;&nbsp;<a href="#rfc.xref.header.accept-language.1">5.1</a>, <a href="#rfc.iref.h.4"><b>6.4</b></a>, <a href="#rfc.xref.header.accept-language.2">7.1</a></li>
    2207                         <li>Content-Encoding&nbsp;&nbsp;<a href="#rfc.xref.header.content-encoding.1">2.2</a>, <a href="#rfc.xref.header.content-encoding.2">4.1</a>, <a href="#rfc.iref.h.5"><b>6.5</b></a>, <a href="#rfc.xref.header.content-encoding.3">6.5</a>, <a href="#rfc.xref.header.content-encoding.4">7.1</a></li>
    2208                         <li>Content-Language&nbsp;&nbsp;<a href="#rfc.xref.header.content-language.1">4.1</a>, <a href="#rfc.iref.h.6"><b>6.6</b></a>, <a href="#rfc.xref.header.content-language.2">7.1</a></li>
    2209                         <li>Content-Location&nbsp;&nbsp;<a href="#rfc.xref.header.content-location.1">4.1</a>, <a href="#rfc.iref.h.7"><b>6.7</b></a>, <a href="#rfc.xref.header.content-location.2">7.1</a>, <a href="#rfc.xref.header.content-location.3">C</a></li>
    2210                         <li>Content-Transfer-Encoding&nbsp;&nbsp;<a href="#rfc.iref.h.10">A.5</a>, <a href="#rfc.xref.no.content-transfer-encoding.1">C</a></li>
    2211                         <li>Content-Type&nbsp;&nbsp;<a href="#rfc.xref.header.content-type.1">2.3</a>, <a href="#rfc.xref.header.content-type.2">4.1</a>, <a href="#rfc.iref.h.8"><b>6.8</b></a>, <a href="#rfc.xref.header.content-type.3">7.1</a></li>
    2212                         <li>MIME-Version&nbsp;&nbsp;<a href="#rfc.xref.mime-version.1">7.1</a>, <a href="#rfc.iref.h.9"><b>A.1</b></a></li>
    2213                      </ul>
    2214                   </li>
    2215                </ul>
    2216             </li>
    2217             <li><a id="rfc.index.M" href="#rfc.index.M"><b>M</b></a><ul>
    2218                   <li>MIME-Version header field&nbsp;&nbsp;<a href="#rfc.xref.mime-version.1">7.1</a>, <a href="#rfc.iref.m.1"><b>A.1</b></a></li>
    2219                </ul>
    2220             </li>
    2221             <li><a id="rfc.index.P" href="#rfc.index.P"><b>P</b></a><ul>
    2222                   <li><em>Part1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.1">1.2</a>, <a href="#rfc.xref.Part1.2">1.3</a>, <a href="#rfc.xref.Part1.3">1.3.1</a>, <a href="#rfc.xref.Part1.4">1.3.1</a>, <a href="#rfc.xref.Part1.5">1.3.1</a>, <a href="#rfc.xref.Part1.6">1.3.1</a>, <a href="#rfc.xref.Part1.7">1.3.2</a>, <a href="#rfc.xref.Part1.8">1.3.2</a>, <a href="#rfc.xref.Part1.9">1.3.2</a>, <a href="#rfc.xref.Part1.10">2.2</a>, <a href="#rfc.xref.Part1.11">2.2</a>, <a href="#rfc.xref.Part1.12">2.2</a>, <a href="#rfc.xref.Part1.13">2.2.1</a>, <a href="#rfc.xref.Part1.14">2.2.1</a>, <a href="#rfc.xref.Part1.15">3.1</a>, <a href="#rfc.xref.Part1.16">3.2</a>, <a href="#rfc.xref.Part1.17">5.1</a>, <a href="#rfc.xref.Part1.18">6.1</a>, <a href="#rfc.xref.Part1.19">6.3</a>, <a href="#rfc.xref.Part1.20">6.7</a>, <a href="#rfc.xref.Part1.21">7.2</a>, <a href="#rfc.xref.Part1.22">7.2</a>, <a href="#rfc.xref.Part1.23">7.2</a>, <a href="#rfc.xref.Part1.24">9</a>, <a href="#Part1"><b>10.1</b></a>, <a href="#rfc.xref.Part1.25">A.6</a><ul>
    2223                         <li><em>Section 1.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.2">1.3</a></li>
    2224                         <li><em>Section 2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.1">1.2</a></li>
    2225                         <li><em>Section 2.7</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.7">1.3.2</a>, <a href="#rfc.xref.Part1.8">1.3.2</a></li>
    2226                         <li><em>Section 3.2.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.4">1.3.1</a></li>
    2227                         <li><em>Section 3.2.4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.5">1.3.1</a>, <a href="#rfc.xref.Part1.6">1.3.1</a></li>
    2228                         <li><em>Section 3.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.16">3.2</a></li>
    2229                         <li><em>Section 3.3.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.25">A.6</a></li>
    2230                         <li><em>Section 3.3.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.15">3.1</a></li>
    2231                         <li><em>Section 4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.13">2.2.1</a></li>
    2232                         <li><em>Section 4.2.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.10">2.2</a>, <a href="#rfc.xref.Part1.21">7.2</a></li>
    2233                         <li><em>Section 4.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.14">2.2.1</a></li>
    2234                         <li><em>Section 4.2.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.11">2.2</a>, <a href="#rfc.xref.Part1.22">7.2</a></li>
    2235                         <li><em>Section 4.2.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.12">2.2</a>, <a href="#rfc.xref.Part1.23">7.2</a></li>
    2236                         <li><em>Section 4.3.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.9">1.3.2</a>, <a href="#rfc.xref.Part1.17">5.1</a>, <a href="#rfc.xref.Part1.18">6.1</a>, <a href="#rfc.xref.Part1.19">6.3</a></li>
    2237                         <li><em>Section 5.5</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.20">6.7</a></li>
    2238                         <li><em>Section 9</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.24">9</a></li>
    2239                      </ul>
    2240                   </li>
    2241                   <li><em>Part2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.1">5.1</a>, <a href="#Part2"><b>10.1</b></a>, <a href="#rfc.xref.Part2.2">A.3</a><ul>
    2242                         <li><em>Section 6.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.2">A.3</a></li>
    2243                         <li><em>Section 7.10</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.1">5.1</a></li>
    2244                      </ul>
    2245                   </li>
    2246                   <li><em>Part4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part4.1">4.1</a>, <a href="#rfc.xref.Part4.2">4.1</a>, <a href="#Part4"><b>10.1</b></a><ul>
    2247                         <li><em>Section 2.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part4.2">4.1</a></li>
    2248                         <li><em>Section 2.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part4.1">4.1</a></li>
    2249                      </ul>
    2250                   </li>
    2251                   <li><em>Part5</em>&nbsp;&nbsp;<a href="#rfc.xref.Part5.1">3.1</a>, <a href="#Part5"><b>10.1</b></a><ul>
    2252                         <li><em>Section 5.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part5.1">3.1</a></li>
    2253                      </ul>
    2254                   </li>
    2255                   <li><em>Part6</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.1">4.1</a>, <a href="#rfc.xref.Part6.2">5.1</a>, <a href="#Part6"><b>10.1</b></a><ul>
    2256                         <li><em>Section 3.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.1">4.1</a></li>
    2257                         <li><em>Section 3.5</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.2">5.1</a></li>
    2258                      </ul>
    2259                   </li>
    2260                   <li>payload&nbsp;&nbsp;<a href="#rfc.iref.p.1">3</a></li>
    2261                </ul>
    2262             </li>
    2263             <li><a id="rfc.index.R" href="#rfc.index.R"><b>R</b></a><ul>
    2264                   <li>representation&nbsp;&nbsp;<a href="#rfc.iref.r.1">4</a></li>
    2265                   <li><em>RFC1945</em>&nbsp;&nbsp;<a href="#RFC1945"><b>10.2</b></a>, <a href="#rfc.xref.RFC1945.1">B</a></li>
    2266                   <li><em>RFC1950</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC1950.1">7.2</a>, <a href="#RFC1950"><b>10.1</b></a></li>
    2267                   <li><em>RFC1951</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC1951.1">7.2</a>, <a href="#RFC1951"><b>10.1</b></a></li>
    2268                   <li><em>RFC1952</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC1952.1">7.2</a>, <a href="#RFC1952"><b>10.1</b></a></li>
    2269                   <li><em>RFC2045</em>&nbsp;&nbsp;<a href="#RFC2045"><b>10.1</b></a>, <a href="#rfc.xref.RFC2045.1">A</a>, <a href="#rfc.xref.RFC2045.2">A.1</a></li>
    2270                   <li><em>RFC2046</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2046.1">2.3</a>, <a href="#rfc.xref.RFC2046.2">2.3.2</a>, <a href="#rfc.xref.RFC2046.3">4.2</a>, <a href="#RFC2046"><b>10.1</b></a>, <a href="#rfc.xref.RFC2046.4">A.2</a><ul>
    2271                         <li><em>Section 4.5.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2046.3">4.2</a></li>
    2272                         <li><em>Section 5.1.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2046.2">2.3.2</a></li>
    2273                      </ul>
    2274                   </li>
    2275                   <li><em>RFC2049</em>&nbsp;&nbsp;<a href="#RFC2049"><b>10.2</b></a>, <a href="#rfc.xref.RFC2049.1">A.2</a><ul>
    2276                         <li><em>Section 4</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2049.1">A.2</a></li>
    2277                      </ul>
    2278                   </li>
    2279                   <li><em>RFC2068</em>&nbsp;&nbsp;<a href="#RFC2068"><b>10.2</b></a>, <a href="#rfc.xref.RFC2068.1">B</a></li>
    2280                   <li><em>RFC2076</em>&nbsp;&nbsp;<a href="#RFC2076"><b>10.2</b></a>, <a href="#rfc.xref.RFC2076.1">B</a></li>
    2281                   <li><em>RFC2119</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2119.1">1.2</a>, <a href="#RFC2119"><b>10.1</b></a></li>
    2282                   <li><em>RFC2277</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2277.1">2.1</a>, <a href="#RFC2277"><b>10.2</b></a></li>
    2283                   <li><em>RFC2295</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2295.1">5</a>, <a href="#RFC2295"><b>10.2</b></a></li>
    2284                   <li><em>RFC2388</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2388.1">2.3.2</a>, <a href="#RFC2388"><b>10.2</b></a></li>
    2285                   <li><em>RFC2557</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2557.1">6.7</a>, <a href="#RFC2557"><b>10.2</b></a>, <a href="#rfc.xref.RFC2557.2">A.7</a><ul>
    2286                         <li><em>Section 4</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2557.1">6.7</a></li>
    2287                      </ul>
    2288                   </li>
    2289                   <li><em>RFC2616</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2616.1">1</a>, <a href="#rfc.xref.RFC2616.2">6.4</a>, <a href="#RFC2616"><b>10.2</b></a>, <a href="#rfc.xref.RFC2616.3">E.1</a><ul>
    2290                         <li><em>Section 14.4</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2616.2">6.4</a></li>
    2291                      </ul>
    2292                   </li>
    2293                   <li><em>RFC3629</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC3629.1">2.1</a>, <a href="#RFC3629"><b>10.2</b></a></li>
    2294                   <li><em>RFC3864</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC3864.1">7.1</a>, <a href="#RFC3864"><b>10.2</b></a></li>
    2295                   <li><em>RFC4288</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC4288.1">2.3</a>, <a href="#RFC4288"><b>10.2</b></a></li>
    2296                   <li><em>RFC4647</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC4647.1">6.4</a>, <a href="#rfc.xref.RFC4647.2">6.4</a>, <a href="#rfc.xref.RFC4647.3">6.4</a>, <a href="#rfc.xref.RFC4647.4">6.4</a>, <a href="#RFC4647"><b>10.1</b></a><ul>
    2297                         <li><em>Section 2.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC4647.1">6.4</a></li>
    2298                         <li><em>Section 2.3</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC4647.2">6.4</a></li>
    2299                         <li><em>Section 3</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC4647.3">6.4</a></li>
    2300                         <li><em>Section 3.3.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC4647.4">6.4</a></li>
    2301                      </ul>
    2302                   </li>
    2303                   <li><em>RFC5226</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5226.1">2.2.1</a>, <a href="#RFC5226"><b>10.2</b></a><ul>
    2304                         <li><em>Section 4.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5226.1">2.2.1</a></li>
    2305                      </ul>
    2306                   </li>
    2307                   <li><em>RFC5234</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5234.1">1.3</a>, <a href="#rfc.xref.RFC5234.2">1.3</a>, <a href="#RFC5234"><b>10.1</b></a><ul>
    2308                         <li><em>Appendix B.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5234.2">1.3</a></li>
    2309                      </ul>
    2310                   </li>
    2311                   <li><em>RFC5322</em>&nbsp;&nbsp;<a href="#RFC5322"><b>10.2</b></a>, <a href="#rfc.xref.RFC5322.1">A</a></li>
    2312                   <li><em>RFC5646</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5646.1">2.4</a>, <a href="#rfc.xref.RFC5646.2">2.4</a>, <a href="#rfc.xref.RFC5646.3">2.4</a>, <a href="#RFC5646"><b>10.1</b></a><ul>
    2313                         <li><em>Section 2.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5646.2">2.4</a></li>
    2314                      </ul>
    2315                   </li>
    2316                   <li><em>RFC6151</em>&nbsp;&nbsp;<a href="#RFC6151"><b>10.2</b></a>, <a href="#rfc.xref.RFC6151.1">C</a></li>
    2317                   <li><em>RFC6266</em>&nbsp;&nbsp;<a href="#RFC6266"><b>10.2</b></a>, <a href="#rfc.xref.RFC6266.1">B</a>, <a href="#rfc.xref.RFC6266.2">C</a></li>
    2318                </ul>
    2319             </li>
    2320             <li><a id="rfc.index.S" href="#rfc.index.S"><b>S</b></a><ul>
    2321                   <li>selected representation&nbsp;&nbsp;<a href="#rfc.iref.s.1"><b>1.1</b></a></li>
    2322                </ul>
    2323             </li>
    2324          </ul>
    2325       </div>
    2326    </body>
     633      <h1 id="rfc.section.A" class="np"><a href="#rfc.section.A">A.</a>&nbsp;<a id="changes.from.rfc.2616" href="#changes.from.rfc.2616">Changes from RFC 2616</a></h1>
     634      <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a>&nbsp;<a id="collected.abnf" href="#collected.abnf">Collected ABNF</a></h1>
     635      <div id="rfc.figure.u.2"></div> <pre class="inline">foo = bar
     636</pre> <div id="rfc.figure.u.3"></div>
     637      <p>ABNF diagnostics:</p><pre class="inline">; bar UNDEFINED
     638; foo defined but not used
     639</pre></body>
    2327640</html>
Note: See TracChangeset for help on using the changeset viewer.