Changeset 1627


Ignore:
Timestamp:
Mar 28, 2012, 8:54:24 AM (7 years ago)
Author:
julian.reschke@…
Message:

exp

Location:
draft-ietf-httpbis/experiment
Files:
9 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/experiment/Makefile

    r1487 r1627  
    3333          p2-semantics.iana-methods     \
    3434          p2-semantics.iana-status-codes \
    35           p3-payload.iana-headers \
    3635          p4-conditional.iana-headers \
    3736          p4-conditional.iana-status-codes \
  • draft-ietf-httpbis/experiment/httpbis.abnf

    r1581 r1627  
    135135field-value = *( field-content / obs-fold )
    136136first-byte-pos = 1*DIGIT
     137; bar UNDEFINED
     138foo = bar
    137139header-field = field-name ":" OWS field-value BWS
    138140hour = 2DIGIT
     
    285287; Warning defined but not used
    286288; chunked-body defined but not used
     289; foo defined but not used
    287290; http-URI defined but not used
    288291; https-URI defined but not used
  • draft-ietf-httpbis/experiment/p1-messaging.html

    r1625 r1627  
    757757      <p id="rfc.section.1.p.1">The Hypertext Transfer Protocol (HTTP) is an application-level request/response protocol that uses extensible semantics and
    758758         MIME-like message payloads for flexible interaction with network-based hypertext information systems. HTTP relies upon the
    759          Uniform Resource Identifier (URI) standard <a href="#RFC3986" id="rfc.xref.RFC3986.1"><cite title="Uniform Resource Identifier (URI): Generic Syntax">[RFC3986]</cite></a> to indicate the target resource (<a href="#target-resource" title="Identifying a Target Resource">Section&nbsp;5.1</a>) and relationships between resources. Messages are passed in a format similar to that used by 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> (see <a href="p3-payload.html#differences.between.http.and.mime" title="Differences between HTTP and MIME">Appendix A</a> of <a href="#Part3" id="rfc.xref.Part3.1"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a> for the differences between HTTP and MIME messages).
     759         Uniform Resource Identifier (URI) standard <a href="#RFC3986" id="rfc.xref.RFC3986.1"><cite title="Uniform Resource Identifier (URI): Generic Syntax">[RFC3986]</cite></a> to indicate the target resource (<a href="#target-resource" title="Identifying a Target Resource">Section&nbsp;5.1</a>) and relationships between resources. Messages are passed in a format similar to that used by 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> (see <a href="p3-payload.html#differences.between.http.and.mime" title="ERROR: Anchor 'differences.between.http.and.mime' not found in p3-payload.xml.">Appendix ERROR: Anchor 'differences.between.http.and.mime' in Part3 not found in source file 'p3-payload.xml'.</a> of <a href="#Part3" id="rfc.xref.Part3.1"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a> for the differences between HTTP and MIME messages).
    760760      </p>
    761761      <p id="rfc.section.1.p.2">HTTP is a generic interface protocol for information systems. It is designed to hide the details of how a service is implemented
     
    12231223                 ; see <a href="#field.parsing" title="Field Parsing">Section&nbsp;3.2.2</a>
    12241224</pre><p id="rfc.section.3.2.p.3">The field-name token labels the corresponding field-value as having the semantics defined by that header field. For example,
    1225          the Date header field is defined in <a href="p2-semantics.html#header.date" title="Date">Section 7.2</a> of <a href="#Part2" id="rfc.xref.Part2.6"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a> as containing the origination timestamp for the message in which it appears.
     1225         the Date header field is defined in <a href="p2-semantics.html#header.date" title="Date">Section 11.2</a> of <a href="#Part2" id="rfc.xref.Part2.6"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a> as containing the origination timestamp for the message in which it appears.
    12261226      </p>
    12271227      <p id="rfc.section.3.2.p.4">HTTP header fields are fully extensible: there is no limit on the introduction of new field names, each presumably defining
     
    14181418      <p id="rfc.section.3.3.1.p.6">If more than one Transfer-Encoding header field is present in a message, the multiple field-values <em class="bcp14">MUST</em> be combined into one field-value, according to the algorithm defined in <a href="#header.fields" title="Header Fields">Section&nbsp;3.2</a>, before determining the message body length.
    14191419      </p>
    1420       <p id="rfc.section.3.3.1.p.7">Unlike Content-Encoding (<a href="p3-payload.html#content.codings" title="Content Codings">Section 2.2</a> of <a href="#Part3" id="rfc.xref.Part3.2"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>), Transfer-Encoding is a property of the message, not of the payload, and thus <em class="bcp14">MAY</em> be added or removed by any implementation along the request/response chain. Additional information about the encoding parameters <em class="bcp14">MAY</em> be provided by other header fields not defined by this specification.
     1420      <p id="rfc.section.3.3.1.p.7">Unlike Content-Encoding (<a href="p3-payload.html#content.codings" title="ERROR: Anchor 'content.codings' not found in p3-payload.xml.">Appendix ERROR: Anchor 'content.codings' in Part3 not found in source file 'p3-payload.xml'.</a> of <a href="#Part3" id="rfc.xref.Part3.2"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>), Transfer-Encoding is a property of the message, not of the payload, and thus <em class="bcp14">MAY</em> be added or removed by any implementation along the request/response chain. Additional information about the encoding parameters <em class="bcp14">MAY</em> be provided by other header fields not defined by this specification.
    14211421      </p>
    14221422      <p id="rfc.section.3.3.1.p.8">Transfer-Encoding <em class="bcp14">MAY</em> be sent in a response to a HEAD request or in a 304 response to a GET request, neither of which includes a message body, to
     
    17251725      </p>
    17261726      <h3 id="rfc.section.4.3.1"><a href="#rfc.section.4.3.1">4.3.1</a>&nbsp;<a id="quality.values" href="#quality.values">Quality Values</a></h3>
    1727       <p id="rfc.section.4.3.1.p.1">Both transfer codings (TE request header field, <a href="#header.te" id="rfc.xref.header.te.3" title="TE">Section&nbsp;4.3</a>) and content negotiation (<a href="p3-payload.html#content.negotiation" title="Content Negotiation">Section 5</a> of <a href="#Part3" id="rfc.xref.Part3.3"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>) use short "floating point" numbers to indicate the relative importance ("weight") of various negotiable parameters. A weight
     1727      <p id="rfc.section.4.3.1.p.1">Both transfer codings (TE request header field, <a href="#header.te" id="rfc.xref.header.te.3" title="TE">Section&nbsp;4.3</a>) and content negotiation (<a href="p3-payload.html#content.negotiation" title="ERROR: Anchor 'content.negotiation' not found in p3-payload.xml.">Appendix ERROR: Anchor 'content.negotiation' in Part3 not found in source file 'p3-payload.xml'.</a> of <a href="#Part3" id="rfc.xref.Part3.3"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>) use short "floating point" numbers to indicate the relative importance ("weight") of various negotiable parameters. A weight
    17281728         is normalized to a real number in the range 0 through 1, where 0 is the minimum and 1 the maximum value. If a parameter has
    17291729         a quality value of 0, then content with this parameter is "not acceptable" for the client. HTTP/1.1 applications <em class="bcp14">MUST NOT</em> generate more than three digits after the decimal point. User configuration of these values <em class="bcp14">SHOULD</em> also be limited in this fashion.
     
    21872187      <p id="rfc.section.6.4.3.p.2">Requirements for HTTP/1.1 clients: </p>
    21882188      <ul>
    2189          <li>If a client will wait for a 100 (Continue) response before sending the request body, it <em class="bcp14">MUST</em> send an Expect header field (<a href="p2-semantics.html#header.expect" title="Expect">Section 7.3</a> of <a href="#Part2" id="rfc.xref.Part2.15"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>) with the "100-continue" expectation.
    2190          </li>
    2191          <li>A client <em class="bcp14">MUST NOT</em> send an Expect header field (<a href="p2-semantics.html#header.expect" title="Expect">Section 7.3</a> of <a href="#Part2" id="rfc.xref.Part2.16"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>) with the "100-continue" expectation if it does not intend to send a request body.
     2189         <li>If a client will wait for a 100 (Continue) response before sending the request body, it <em class="bcp14">MUST</em> send an Expect header field (<a href="p2-semantics.html#header.expect" title="Expect">Section 11.3</a> of <a href="#Part2" id="rfc.xref.Part2.15"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>) with the "100-continue" expectation.
     2190         </li>
     2191         <li>A client <em class="bcp14">MUST NOT</em> send an Expect header field (<a href="p2-semantics.html#header.expect" title="Expect">Section 11.3</a> of <a href="#Part2" id="rfc.xref.Part2.16"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>) with the "100-continue" expectation if it does not intend to send a request body.
    21922192         </li>
    21932193      </ul>
     
    25342534         <li>Pointer to specification text</li>
    25352535      </ul>
    2536       <p id="rfc.section.7.4.p.3">Names of transfer codings <em class="bcp14">MUST NOT</em> overlap with names of content codings (<a href="p3-payload.html#content.codings" title="Content Codings">Section 2.2</a> of <a href="#Part3" id="rfc.xref.Part3.5"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>) unless the encoding transformation is identical, as it is the case for the compression codings defined in <a href="#compression.codings" title="Compression Codings">Section&nbsp;4.2</a>.
     2536      <p id="rfc.section.7.4.p.3">Names of transfer codings <em class="bcp14">MUST NOT</em> overlap with names of content codings (<a href="p3-payload.html#content.codings" title="ERROR: Anchor 'content.codings' not found in p3-payload.xml.">Appendix ERROR: Anchor 'content.codings' in Part3 not found in source file 'p3-payload.xml'.</a> of <a href="#Part3" id="rfc.xref.Part3.5"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>) unless the encoding transformation is identical, as it is the case for the compression codings defined in <a href="#compression.codings" title="Compression Codings">Section&nbsp;4.2</a>.
    25372537      </p>
    25382538      <p id="rfc.section.7.4.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 transfer coding defined in this section.
     
    37633763                        <li><em>Section 4.6</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.20">8.6</a></li>
    37643764                        <li><em>Section 4.6.12</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.4">3.1.1</a>, <a href="#rfc.xref.Part2.19">8.6</a></li>
    3765                         <li><em>Section 7.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.6">3.2</a></li>
    3766                         <li><em>Section 7.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.15">6.4.3</a>, <a href="#rfc.xref.Part2.16">6.4.3</a></li>
     3765                        <li><em>Section 11.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.6">3.2</a></li>
     3766                        <li><em>Section 11.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.15">6.4.3</a>, <a href="#rfc.xref.Part2.16">6.4.3</a></li>
    37673767                     </ul>
    37683768                  </li>
    37693769                  <li><em>Part3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part3.1">1</a>, <a href="#rfc.xref.Part3.2">3.3.1</a>, <a href="#rfc.xref.Part3.3">4.3.1</a>, <a href="#rfc.xref.Part3.4">5.6.2</a>, <a href="#rfc.xref.Part3.5">7.4</a>, <a href="#Part3"><b>10.1</b></a><ul>
    3770                         <li><em>Section 2.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part3.2">3.3.1</a>, <a href="#rfc.xref.Part3.5">7.4</a></li>
    3771                         <li><em>Section 5</em>&nbsp;&nbsp;<a href="#rfc.xref.Part3.3">4.3.1</a></li>
    3772                         <li><em>Appendix A</em>&nbsp;&nbsp;<a href="#rfc.xref.Part3.1">1</a></li>
     3770                        <li><em>Appendix </em>&nbsp;&nbsp;<a href="#rfc.xref.Part3.1">1</a></li>
     3771                        <li><em>Appendix </em>&nbsp;&nbsp;<a href="#rfc.xref.Part3.2">3.3.1</a>, <a href="#rfc.xref.Part3.5">7.4</a></li>
     3772                        <li><em>Appendix </em>&nbsp;&nbsp;<a href="#rfc.xref.Part3.3">4.3.1</a></li>
    37733773                     </ul>
    37743774                  </li>
  • draft-ietf-httpbis/experiment/p2-semantics.html

    r1625 r1627  
    488488      <link rel="Chapter" title="5 Representation" href="#rfc.section.5">
    489489      <link rel="Chapter" title="6 Common Protocol Parameters" href="#rfc.section.6">
    490       <link rel="Chapter" title="7 Header Field Definitions" href="#rfc.section.7">
    491       <link rel="Chapter" title="8 IANA Considerations" href="#rfc.section.8">
    492       <link rel="Chapter" title="9 Security Considerations" href="#rfc.section.9">
    493       <link rel="Chapter" title="10 Acknowledgments" href="#rfc.section.10">
    494       <link rel="Chapter" href="#rfc.section.11" title="11 References">
    495       <link rel="Appendix" title="A Changes from RFC 2616" href="#rfc.section.A">
    496       <link rel="Appendix" title="B Collected ABNF" href="#rfc.section.B">
    497       <link rel="Appendix" title="C Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.C">
     490      <link rel="Chapter" title="7 Protocol Parameters" href="#rfc.section.7">
     491      <link rel="Chapter" title="8 Payload" href="#rfc.section.8">
     492      <link rel="Chapter" title="9 Representation" href="#rfc.section.9">
     493      <link rel="Chapter" title="10 Content Negotiation" href="#rfc.section.10">
     494      <link rel="Chapter" title="11 Header Field Definitions" href="#rfc.section.11">
     495      <link rel="Chapter" title="12 IANA Considerations" href="#rfc.section.12">
     496      <link rel="Chapter" title="13 Security Considerations" href="#rfc.section.13">
     497      <link rel="Chapter" title="14 Acknowledgments" href="#rfc.section.14">
     498      <link rel="Chapter" href="#rfc.section.15" title="15 References">
     499      <link rel="Appendix" title="A Differences between HTTP and MIME" href="#rfc.section.A">
     500      <link rel="Appendix" title="B Additional Features" href="#rfc.section.B">
     501      <link rel="Appendix" title="C Changes from RFC 2616" href="#rfc.section.C">
     502      <link rel="Appendix" title="D Collected ABNF" href="#rfc.section.D">
     503      <link rel="Appendix" title="E Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.E">
    498504      <link href="p1-messaging.html" rel="prev">
    499505      <link href="p3-payload.html" rel="next">
     
    506512      <meta name="dct.issued" scheme="ISO8601" content="2012-03-28">
    507513      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    508       <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 2 of the seven-part specification that defines the protocol referred to as &#34;HTTP/1.1&#34; and, taken together, obsoletes RFC 2616. Part 2 defines the semantics of HTTP messages as expressed by request methods, request header fields, response status codes, and response header fields.">
    509       <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 2 of the seven-part specification that defines the protocol referred to as &#34;HTTP/1.1&#34; and, taken together, obsoletes RFC 2616. Part 2 defines the semantics of HTTP messages as expressed by request methods, request header fields, response status codes, and response header fields.">
     514      <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 2 of the seven-part specification that defines the protocol referred to as &#34;HTTP/1.1&#34; and, taken together, obsoletes RFC 2616. Part 2 defines the semantics of HTTP messages as expressed by request methods, request header fields, response status codes, response header fields, HTTP message content, metadata, and content negotiation.">
     515      <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 2 of the seven-part specification that defines the protocol referred to as &#34;HTTP/1.1&#34; and, taken together, obsoletes RFC 2616. Part 2 defines the semantics of HTTP messages as expressed by request methods, request header fields, response status codes, response header fields, HTTP message content, metadata, and content negotiation.">
    510516   </head>
    511517   <body onload="init();">
     
    551557      </p> 
    552558      <p>Part 2 defines the semantics of HTTP messages as expressed by request methods, request header fields, response status codes,
    553          and response header fields.
     559         response header fields, HTTP message content, metadata, and content negotiation.
    554560      </p>
    555561      <h1 id="rfc.note.1"><a href="#rfc.note.1">Editorial Note (To be removed by RFC Editor)</a></h1>
     
    559565      <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;.
    560566      </p> 
    561       <p>The changes in this draft are summarized in <a href="#changes.since.19" title="Since draft-ietf-httpbis-p2-semantics-19">Appendix&nbsp;C.21</a>.
     567      <p>The changes in this draft are summarized in <a href="#changes.since.19" title="Since draft-ietf-httpbis-p2-semantics-19">Appendix&nbsp;E.40</a>.
    562568      </p>
    563569      <h1><a id="rfc.status" href="#rfc.status">Status of This Memo</a></h1>
     
    589595      <ul class="toc">
    590596         <li>1.&nbsp;&nbsp;&nbsp;<a href="#introduction">Introduction</a><ul>
    591                <li>1.1&nbsp;&nbsp;&nbsp;<a href="#intro.conformance.and.error.handling">Conformance and Error Handling</a></li>
    592                <li>1.2&nbsp;&nbsp;&nbsp;<a href="#notation">Syntax Notation</a><ul>
    593                      <li>1.2.1&nbsp;&nbsp;&nbsp;<a href="#core.rules">Core Rules</a></li>
    594                      <li>1.2.2&nbsp;&nbsp;&nbsp;<a href="#abnf.dependencies">ABNF Rules defined in other Parts of the Specification</a></li>
     597               <li>1.1&nbsp;&nbsp;&nbsp;<a href="#terminology">Terminology</a></li>
     598               <li>1.2&nbsp;&nbsp;&nbsp;<a href="#intro.conformance.and.error.handling">Conformance and Error Handling</a></li>
     599               <li>1.3&nbsp;&nbsp;&nbsp;<a href="#notation">Syntax Notation</a><ul>
     600                     <li>1.3.1&nbsp;&nbsp;&nbsp;<a href="#core.rules">Core Rules</a></li>
     601                     <li>1.3.2&nbsp;&nbsp;&nbsp;<a href="#abnf.dependencies">ABNF Rules defined in other Parts of the Specification</a></li>
    595602                  </ul>
    596603               </li>
     
    694701            </ul>
    695702         </li>
    696          <li>7.&nbsp;&nbsp;&nbsp;<a href="#header.field.definitions">Header Field Definitions</a><ul>
    697                <li>7.1&nbsp;&nbsp;&nbsp;<a href="#header.allow">Allow</a></li>
    698                <li>7.2&nbsp;&nbsp;&nbsp;<a href="#header.date">Date</a></li>
    699                <li>7.3&nbsp;&nbsp;&nbsp;<a href="#header.expect">Expect</a></li>
    700                <li>7.4&nbsp;&nbsp;&nbsp;<a href="#header.from">From</a></li>
    701                <li>7.5&nbsp;&nbsp;&nbsp;<a href="#header.location">Location</a></li>
    702                <li>7.6&nbsp;&nbsp;&nbsp;<a href="#header.max-forwards">Max-Forwards</a></li>
    703                <li>7.7&nbsp;&nbsp;&nbsp;<a href="#header.referer">Referer</a></li>
    704                <li>7.8&nbsp;&nbsp;&nbsp;<a href="#header.retry-after">Retry-After</a></li>
    705                <li>7.9&nbsp;&nbsp;&nbsp;<a href="#header.server">Server</a></li>
    706                <li>7.10&nbsp;&nbsp;&nbsp;<a href="#header.user-agent">User-Agent</a></li>
     703         <li>7.&nbsp;&nbsp;&nbsp;<a href="#protocol.parameters">Protocol Parameters</a><ul>
     704               <li>7.1&nbsp;&nbsp;&nbsp;<a href="#character.sets">Character Encodings (charset)</a></li>
     705               <li>7.2&nbsp;&nbsp;&nbsp;<a href="#content.codings">Content Codings</a><ul>
     706                     <li>7.2.1&nbsp;&nbsp;&nbsp;<a href="#content.coding.registry">Content Coding Registry</a></li>
     707                  </ul>
     708               </li>
     709               <li>7.3&nbsp;&nbsp;&nbsp;<a href="#media.types">Media Types</a><ul>
     710                     <li>7.3.1&nbsp;&nbsp;&nbsp;<a href="#canonicalization.and.text.defaults">Canonicalization and Text Defaults</a></li>
     711                     <li>7.3.2&nbsp;&nbsp;&nbsp;<a href="#multipart.types">Multipart Types</a></li>
     712                  </ul>
     713               </li>
     714               <li>7.4&nbsp;&nbsp;&nbsp;<a href="#language.tags">Language Tags</a></li>
    707715            </ul>
    708716         </li>
    709          <li>8.&nbsp;&nbsp;&nbsp;<a href="#IANA.considerations">IANA Considerations</a><ul>
    710                <li>8.1&nbsp;&nbsp;&nbsp;<a href="#method.registration">Method Registry</a></li>
    711                <li>8.2&nbsp;&nbsp;&nbsp;<a href="#status.code.registration">Status Code Registry</a></li>
    712                <li>8.3&nbsp;&nbsp;&nbsp;<a href="#header.field.registration">Header Field Registration</a></li>
     717         <li>8.&nbsp;&nbsp;&nbsp;<a href="#payload">Payload</a><ul>
     718               <li>8.1&nbsp;&nbsp;&nbsp;<a href="#payload.header.fields">Payload Header Fields</a></li>
     719               <li>8.2&nbsp;&nbsp;&nbsp;<a href="#payload.body">Payload Body</a></li>
    713720            </ul>
    714721         </li>
    715          <li>9.&nbsp;&nbsp;&nbsp;<a href="#security.considerations">Security Considerations</a><ul>
    716                <li>9.1&nbsp;&nbsp;&nbsp;<a href="#security.sensitive">Transfer of Sensitive Information</a></li>
    717                <li>9.2&nbsp;&nbsp;&nbsp;<a href="#encoding.sensitive.information.in.uris">Encoding Sensitive Information in URIs</a></li>
    718                <li>9.3&nbsp;&nbsp;&nbsp;<a href="#location.spoofing-leakage">Location Header Fields: Spoofing and Information Leakage</a></li>
    719                <li>9.4&nbsp;&nbsp;&nbsp;<a href="#rfc.section.9.4">Security Considerations for CONNECT</a></li>
     722         <li>9.&nbsp;&nbsp;&nbsp;<a href="#representation-TODO">Representation</a><ul>
     723               <li>9.1&nbsp;&nbsp;&nbsp;<a href="#representation.header.fields">Representation Header Fields</a></li>
     724               <li>9.2&nbsp;&nbsp;&nbsp;<a href="#representation.data">Representation Data</a></li>
    720725            </ul>
    721726         </li>
    722          <li>10.&nbsp;&nbsp;&nbsp;<a href="#acks">Acknowledgments</a></li>
    723          <li>11.&nbsp;&nbsp;&nbsp;<a href="#rfc.references">References</a><ul>
    724                <li>11.1&nbsp;&nbsp;&nbsp;<a href="#rfc.references.1">Normative References</a></li>
    725                <li>11.2&nbsp;&nbsp;&nbsp;<a href="#rfc.references.2">Informative References</a></li>
     727         <li>10.&nbsp;&nbsp;&nbsp;<a href="#content.negotiation">Content Negotiation</a><ul>
     728               <li>10.1&nbsp;&nbsp;&nbsp;<a href="#server-driven.negotiation">Server-driven Negotiation</a></li>
     729               <li>10.2&nbsp;&nbsp;&nbsp;<a href="#agent-driven.negotiation">Agent-driven Negotiation</a></li>
    726730            </ul>
    727731         </li>
     732         <li>11.&nbsp;&nbsp;&nbsp;<a href="#header.field.definitions">Header Field Definitions</a><ul>
     733               <li>11.1&nbsp;&nbsp;&nbsp;<a href="#header.allow">Allow</a></li>
     734               <li>11.2&nbsp;&nbsp;&nbsp;<a href="#header.date">Date</a></li>
     735               <li>11.3&nbsp;&nbsp;&nbsp;<a href="#header.expect">Expect</a></li>
     736               <li>11.4&nbsp;&nbsp;&nbsp;<a href="#header.from">From</a></li>
     737               <li>11.5&nbsp;&nbsp;&nbsp;<a href="#header.location">Location</a></li>
     738               <li>11.6&nbsp;&nbsp;&nbsp;<a href="#header.max-forwards">Max-Forwards</a></li>
     739               <li>11.7&nbsp;&nbsp;&nbsp;<a href="#header.referer">Referer</a></li>
     740               <li>11.8&nbsp;&nbsp;&nbsp;<a href="#header.retry-after">Retry-After</a></li>
     741               <li>11.9&nbsp;&nbsp;&nbsp;<a href="#header.server">Server</a></li>
     742               <li>11.10&nbsp;&nbsp;&nbsp;<a href="#header.user-agent">User-Agent</a></li>
     743               <li>11.11&nbsp;&nbsp;&nbsp;<a href="#header.accept">Accept</a></li>
     744               <li>11.12&nbsp;&nbsp;&nbsp;<a href="#header.accept-charset">Accept-Charset</a></li>
     745               <li>11.13&nbsp;&nbsp;&nbsp;<a href="#header.accept-encoding">Accept-Encoding</a></li>
     746               <li>11.14&nbsp;&nbsp;&nbsp;<a href="#header.accept-language">Accept-Language</a></li>
     747               <li>11.15&nbsp;&nbsp;&nbsp;<a href="#header.content-encoding">Content-Encoding</a></li>
     748               <li>11.16&nbsp;&nbsp;&nbsp;<a href="#header.content-language">Content-Language</a></li>
     749               <li>11.17&nbsp;&nbsp;&nbsp;<a href="#header.content-location">Content-Location</a></li>
     750               <li>11.18&nbsp;&nbsp;&nbsp;<a href="#header.content-type">Content-Type</a></li>
     751            </ul>
     752         </li>
     753         <li>12.&nbsp;&nbsp;&nbsp;<a href="#IANA.considerations">IANA Considerations</a><ul>
     754               <li>12.1&nbsp;&nbsp;&nbsp;<a href="#method.registration">Method Registry</a></li>
     755               <li>12.2&nbsp;&nbsp;&nbsp;<a href="#status.code.registration">Status Code Registry</a></li>
     756               <li>12.3&nbsp;&nbsp;&nbsp;<a href="#header.field.registration">Header Field Registration</a></li>
     757               <li>12.4&nbsp;&nbsp;&nbsp;<a href="#content.coding.registration">Content Coding Registry</a></li>
     758            </ul>
     759         </li>
     760         <li>13.&nbsp;&nbsp;&nbsp;<a href="#security.considerations">Security Considerations</a><ul>
     761               <li>13.1&nbsp;&nbsp;&nbsp;<a href="#security.sensitive">Transfer of Sensitive Information</a></li>
     762               <li>13.2&nbsp;&nbsp;&nbsp;<a href="#encoding.sensitive.information.in.uris">Encoding Sensitive Information in URIs</a></li>
     763               <li>13.3&nbsp;&nbsp;&nbsp;<a href="#location.spoofing-leakage">Location Header Fields: Spoofing and Information Leakage</a></li>
     764               <li>13.4&nbsp;&nbsp;&nbsp;<a href="#rfc.section.13.4">Security Considerations for CONNECT</a></li>
     765               <li>13.5&nbsp;&nbsp;&nbsp;<a href="#privacy.issues.connected.to.accept.header.fields">Privacy Issues Connected to Accept Header Fields</a></li>
     766            </ul>
     767         </li>
     768         <li>14.&nbsp;&nbsp;&nbsp;<a href="#acks">Acknowledgments</a></li>
     769         <li>15.&nbsp;&nbsp;&nbsp;<a href="#rfc.references">References</a><ul>
     770               <li>15.1&nbsp;&nbsp;&nbsp;<a href="#rfc.references.1">Normative References</a></li>
     771               <li>15.2&nbsp;&nbsp;&nbsp;<a href="#rfc.references.2">Informative References</a></li>
     772            </ul>
     773         </li>
    728774         <li><a href="#rfc.authors">Authors' Addresses</a></li>
    729          <li>A.&nbsp;&nbsp;&nbsp;<a href="#changes.from.rfc.2616">Changes from RFC 2616</a></li>
    730          <li>B.&nbsp;&nbsp;&nbsp;<a href="#collected.abnf">Collected ABNF</a></li>
    731          <li>C.&nbsp;&nbsp;&nbsp;<a href="#change.log">Change Log (to be removed by RFC Editor before publication)</a><ul>
    732                <li>C.1&nbsp;&nbsp;&nbsp;<a href="#rfc.section.C.1">Since RFC 2616</a></li>
    733                <li>C.2&nbsp;&nbsp;&nbsp;<a href="#rfc.section.C.2">Since draft-ietf-httpbis-p2-semantics-00</a></li>
    734                <li>C.3&nbsp;&nbsp;&nbsp;<a href="#rfc.section.C.3">Since draft-ietf-httpbis-p2-semantics-01</a></li>
    735                <li>C.4&nbsp;&nbsp;&nbsp;<a href="#changes.since.02">Since draft-ietf-httpbis-p2-semantics-02</a></li>
    736                <li>C.5&nbsp;&nbsp;&nbsp;<a href="#changes.since.03">Since draft-ietf-httpbis-p2-semantics-03</a></li>
    737                <li>C.6&nbsp;&nbsp;&nbsp;<a href="#changes.since.04">Since draft-ietf-httpbis-p2-semantics-04</a></li>
    738                <li>C.7&nbsp;&nbsp;&nbsp;<a href="#changes.since.05">Since draft-ietf-httpbis-p2-semantics-05</a></li>
    739                <li>C.8&nbsp;&nbsp;&nbsp;<a href="#changes.since.06">Since draft-ietf-httpbis-p2-semantics-06</a></li>
    740                <li>C.9&nbsp;&nbsp;&nbsp;<a href="#changes.since.07">Since draft-ietf-httpbis-p2-semantics-07</a></li>
    741                <li>C.10&nbsp;&nbsp;&nbsp;<a href="#changes.since.08">Since draft-ietf-httpbis-p2-semantics-08</a></li>
    742                <li>C.11&nbsp;&nbsp;&nbsp;<a href="#changes.since.09">Since draft-ietf-httpbis-p2-semantics-09</a></li>
    743                <li>C.12&nbsp;&nbsp;&nbsp;<a href="#changes.since.10">Since draft-ietf-httpbis-p2-semantics-10</a></li>
    744                <li>C.13&nbsp;&nbsp;&nbsp;<a href="#changes.since.11">Since draft-ietf-httpbis-p2-semantics-11</a></li>
    745                <li>C.14&nbsp;&nbsp;&nbsp;<a href="#changes.since.12">Since draft-ietf-httpbis-p2-semantics-12</a></li>
    746                <li>C.15&nbsp;&nbsp;&nbsp;<a href="#changes.since.13">Since draft-ietf-httpbis-p2-semantics-13</a></li>
    747                <li>C.16&nbsp;&nbsp;&nbsp;<a href="#changes.since.14">Since draft-ietf-httpbis-p2-semantics-14</a></li>
    748                <li>C.17&nbsp;&nbsp;&nbsp;<a href="#changes.since.15">Since draft-ietf-httpbis-p2-semantics-15</a></li>
    749                <li>C.18&nbsp;&nbsp;&nbsp;<a href="#changes.since.16">Since draft-ietf-httpbis-p2-semantics-16</a></li>
    750                <li>C.19&nbsp;&nbsp;&nbsp;<a href="#changes.since.17">Since draft-ietf-httpbis-p2-semantics-17</a></li>
    751                <li>C.20&nbsp;&nbsp;&nbsp;<a href="#changes.since.18">Since draft-ietf-httpbis-p2-semantics-18</a></li>
    752                <li>C.21&nbsp;&nbsp;&nbsp;<a href="#changes.since.19">Since draft-ietf-httpbis-p2-semantics-19</a></li>
     775         <li>A.&nbsp;&nbsp;&nbsp;<a href="#differences.between.http.and.mime">Differences between HTTP and MIME</a><ul>
     776               <li>A.1&nbsp;&nbsp;&nbsp;<a href="#mime-version">MIME-Version</a></li>
     777               <li>A.2&nbsp;&nbsp;&nbsp;<a href="#conversion.to.canonical.form">Conversion to Canonical Form</a></li>
     778               <li>A.3&nbsp;&nbsp;&nbsp;<a href="#conversion.of.date.formats">Conversion of Date Formats</a></li>
     779               <li>A.4&nbsp;&nbsp;&nbsp;<a href="#introduction.of.content-encoding">Introduction of Content-Encoding</a></li>
     780               <li>A.5&nbsp;&nbsp;&nbsp;<a href="#no.content-transfer-encoding">No Content-Transfer-Encoding</a></li>
     781               <li>A.6&nbsp;&nbsp;&nbsp;<a href="#introduction.of.transfer-encoding">Introduction of Transfer-Encoding</a></li>
     782               <li>A.7&nbsp;&nbsp;&nbsp;<a href="#mhtml.line.length">MHTML and Line Length Limitations</a></li>
     783            </ul>
     784         </li>
     785         <li>B.&nbsp;&nbsp;&nbsp;<a href="#additional.features">Additional Features</a></li>
     786         <li>C.&nbsp;&nbsp;&nbsp;<a href="#changes.from.rfc.2616">Changes from RFC 2616</a></li>
     787         <li>D.&nbsp;&nbsp;&nbsp;<a href="#collected.abnf">Collected ABNF</a></li>
     788         <li>E.&nbsp;&nbsp;&nbsp;<a href="#change.log">Change Log (to be removed by RFC Editor before publication)</a><ul>
     789               <li>E.1&nbsp;&nbsp;&nbsp;<a href="#rfc.section.E.1">Since RFC 2616</a></li>
     790               <li>E.2&nbsp;&nbsp;&nbsp;<a href="#rfc.section.E.2">Since draft-ietf-httpbis-p2-semantics-00</a></li>
     791               <li>E.3&nbsp;&nbsp;&nbsp;<a href="#rfc.section.E.3">Since draft-ietf-httpbis-p3-payload-00</a></li>
     792               <li>E.4&nbsp;&nbsp;&nbsp;<a href="#rfc.section.E.4">Since draft-ietf-httpbis-p2-semantics-01</a></li>
     793               <li>E.5&nbsp;&nbsp;&nbsp;<a href="#rfc.section.E.5">Since draft-ietf-httpbis-p3-payload-01</a></li>
     794               <li>E.6&nbsp;&nbsp;&nbsp;<a href="#changes.since.02">Since draft-ietf-httpbis-p2-semantics-02</a></li>
     795               <li>E.7&nbsp;&nbsp;&nbsp;<a href="#changes.since.3.02">Since draft-ietf-httpbis-p3-payload-02</a></li>
     796               <li>E.8&nbsp;&nbsp;&nbsp;<a href="#changes.since.03">Since draft-ietf-httpbis-p2-semantics-03</a></li>
     797               <li>E.9&nbsp;&nbsp;&nbsp;<a href="#changes.since.3.03">Since draft-ietf-httpbis-p3-payload-03</a></li>
     798               <li>E.10&nbsp;&nbsp;&nbsp;<a href="#changes.since.04">Since draft-ietf-httpbis-p2-semantics-04</a></li>
     799               <li>E.11&nbsp;&nbsp;&nbsp;<a href="#changes.since.3.04">Since draft-ietf-httpbis-p3-payload-04</a></li>
     800               <li>E.12&nbsp;&nbsp;&nbsp;<a href="#changes.since.05">Since draft-ietf-httpbis-p2-semantics-05</a></li>
     801               <li>E.13&nbsp;&nbsp;&nbsp;<a href="#changes.since.3.05">Since draft-ietf-httpbis-p3-payload-05</a></li>
     802               <li>E.14&nbsp;&nbsp;&nbsp;<a href="#changes.since.06">Since draft-ietf-httpbis-p2-semantics-06</a></li>
     803               <li>E.15&nbsp;&nbsp;&nbsp;<a href="#changes.since.3.06">Since draft-ietf-httpbis-p3-payload-06</a></li>
     804               <li>E.16&nbsp;&nbsp;&nbsp;<a href="#changes.since.07">Since draft-ietf-httpbis-p2-semantics-07</a></li>
     805               <li>E.17&nbsp;&nbsp;&nbsp;<a href="#changes.since.3-07">Since draft-ietf-httpbis-p3-payload-07</a></li>
     806               <li>E.18&nbsp;&nbsp;&nbsp;<a href="#changes.since.08">Since draft-ietf-httpbis-p2-semantics-08</a></li>
     807               <li>E.19&nbsp;&nbsp;&nbsp;<a href="#changes.since.3.08">Since draft-ietf-httpbis-p3-payload-08</a></li>
     808               <li>E.20&nbsp;&nbsp;&nbsp;<a href="#changes.since.09">Since draft-ietf-httpbis-p2-semantics-09</a></li>
     809               <li>E.21&nbsp;&nbsp;&nbsp;<a href="#changes.since.3.09">Since draft-ietf-httpbis-p3-payload-09</a></li>
     810               <li>E.22&nbsp;&nbsp;&nbsp;<a href="#changes.since.10">Since draft-ietf-httpbis-p2-semantics-10</a></li>
     811               <li>E.23&nbsp;&nbsp;&nbsp;<a href="#changes.since.3.10">Since draft-ietf-httpbis-p3-payload-10</a></li>
     812               <li>E.24&nbsp;&nbsp;&nbsp;<a href="#changes.since.11">Since draft-ietf-httpbis-p2-semantics-11</a></li>
     813               <li>E.25&nbsp;&nbsp;&nbsp;<a href="#changes.since.3.11">Since draft-ietf-httpbis-p3-payload-11</a></li>
     814               <li>E.26&nbsp;&nbsp;&nbsp;<a href="#changes.since.12">Since draft-ietf-httpbis-p2-semantics-12</a></li>
     815               <li>E.27&nbsp;&nbsp;&nbsp;<a href="#changes.since.3.12">Since draft-ietf-httpbis-p3-payload-12</a></li>
     816               <li>E.28&nbsp;&nbsp;&nbsp;<a href="#changes.since.13">Since draft-ietf-httpbis-p2-semantics-13</a></li>
     817               <li>E.29&nbsp;&nbsp;&nbsp;<a href="#changes.since.3.13">Since draft-ietf-httpbis-p3-payload-13</a></li>
     818               <li>E.30&nbsp;&nbsp;&nbsp;<a href="#changes.since.14">Since draft-ietf-httpbis-p2-semantics-14</a></li>
     819               <li>E.31&nbsp;&nbsp;&nbsp;<a href="#changes.since.3.14">Since draft-ietf-httpbis-p3-payload-14</a></li>
     820               <li>E.32&nbsp;&nbsp;&nbsp;<a href="#changes.since.15">Since draft-ietf-httpbis-p2-semantics-15</a></li>
     821               <li>E.33&nbsp;&nbsp;&nbsp;<a href="#changes.since.3.15">Since draft-ietf-httpbis-p3-payload-15</a></li>
     822               <li>E.34&nbsp;&nbsp;&nbsp;<a href="#changes.since.16">Since draft-ietf-httpbis-p2-semantics-16</a></li>
     823               <li>E.35&nbsp;&nbsp;&nbsp;<a href="#changes.since.3.16">Since draft-ietf-httpbis-p3-payload-16</a></li>
     824               <li>E.36&nbsp;&nbsp;&nbsp;<a href="#changes.since.17">Since draft-ietf-httpbis-p2-semantics-17</a></li>
     825               <li>E.37&nbsp;&nbsp;&nbsp;<a href="#changes.since.3.17">Since draft-ietf-httpbis-p3-payload-17</a></li>
     826               <li>E.38&nbsp;&nbsp;&nbsp;<a href="#changes.since.18">Since draft-ietf-httpbis-p2-semantics-18</a></li>
     827               <li>E.39&nbsp;&nbsp;&nbsp;<a href="#changes.since.3.18">Since draft-ietf-httpbis-p3-payload-18</a></li>
     828               <li>E.40&nbsp;&nbsp;&nbsp;<a href="#changes.since.19">Since draft-ietf-httpbis-p2-semantics-19</a></li>
    753829            </ul>
    754830         </li>
     
    761837         response messages that might be expected as a result of applying that method to the target resource.
    762838      </p>
    763       <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
     839      <p id="rfc.section.1.p.2">This document defines HTTP/1.1 message payloads (a.k.a., content), the associated metadata header fields that define how the
     840         payload is intended to be interpreted by a recipient, the request header fields that might influence content selection, and
     841         the various selection algorithms that are collectively referred to as HTTP content negotiation.<span class="comment" id="rfc.comment.1">[<a href="#rfc.comment.1" class="smpl">rfc.comment.1</a>: FIXME]</span>
     842      </p>
     843      <p id="rfc.section.1.p.3">This document is currently disorganized in order to minimize the changes between drafts and enable reviewers to see the smaller
    764844         errata changes. A future draft will reorganize the sections to better reflect the content. In particular, the sections will
    765845         be ordered according to the typical processing of an HTTP request message (after message parsing): resource mapping, methods,
    766          request modifying header fields, response status, status modifying header fields, and resource metadata. The current mess
    767          reflects how widely dispersed these topics 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>.
    768       </p>
    769       <h2 id="rfc.section.1.1"><a href="#rfc.section.1.1">1.1</a>&nbsp;<a id="intro.conformance.and.error.handling" href="#intro.conformance.and.error.handling">Conformance and Error Handling</a></h2>
    770       <p id="rfc.section.1.1.p.1">The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL"
     846         request modifying header fields, response status, status modifying header fields, and resource metadata. Furthermore,, the
     847         sections on entities will be renamed payload and moved to the first half of the document, while the sections on content negotiation
     848         and associated request header fields will be moved to the second half. The current mess reflects how widely dispersed these
     849         topics 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>.
     850      </p>
     851      <h2 id="rfc.section.1.1"><a href="#rfc.section.1.1">1.1</a>&nbsp;<a id="terminology" href="#terminology">Terminology</a></h2>
     852      <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>
     853      <p id="rfc.section.1.1.p.2"> <span id="rfc.iref.c.1"></span>  <dfn>content negotiation</dfn> 
     854      </p>
     855      <ul class="empty">
     856         <li>The mechanism for selecting the appropriate representation when servicing a request. The representation in any response can
     857            be negotiated (including error responses).
     858         </li>
     859      </ul>
     860      <p id="rfc.section.1.1.p.3"> <span id="rfc.iref.s.1"></span>  <dfn>selected representation</dfn> 
     861      </p>
     862      <ul class="empty">
     863         <li>The current representation of the target resource that would have been selected in a successful response if the same request
     864            had used the method GET and excluded any conditional request header fields.
     865         </li>
     866      </ul>
     867      <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>
     868      <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"
    771869         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>.
    772870      </p>
    773       <p id="rfc.section.1.1.p.2">This document defines conformance criteria for several roles in HTTP communication, including Senders, Recipients, Clients,
     871      <p id="rfc.section.1.2.p.2">This document defines conformance criteria for several roles in HTTP communication, including Senders, Recipients, Clients,
    774872         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.2"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a> for definitions of these terms.
    775873      </p>
    776       <p id="rfc.section.1.1.p.3">An implementation is considered conformant if it complies with all of the requirements associated with its role(s). Note that
     874      <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
    777875         SHOULD-level requirements are relevant here, unless one of the documented exceptions is applicable.
    778876      </p>
    779       <p id="rfc.section.1.1.p.4">This document also uses ABNF to define valid protocol elements (<a href="#notation" title="Syntax Notation">Section&nbsp;1.2</a>). In addition to the prose requirements placed upon them, Senders <em class="bcp14">MUST NOT</em> generate protocol elements that are invalid.
    780       </p>
    781       <p id="rfc.section.1.1.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
     877      <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.
     878      </p>
     879      <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
    782880         mechanisms, except in cases where it has direct impact on security. This is because different uses of the protocol require
    783881         different error handling strategies; for example, a Web browser may wish to transparently recover from a response where the
     
    785883         error recovery could lead to dangerous consequences.
    786884      </p>
    787       <h2 id="rfc.section.1.2"><a href="#rfc.section.1.2">1.2</a>&nbsp;<a id="notation" href="#notation">Syntax Notation</a></h2>
    788       <p id="rfc.section.1.2.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.3"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>. <a href="#collected.abnf" title="Collected ABNF">Appendix&nbsp;B</a> shows the collected ABNF with the list rule expanded.
    789       </p>
    790       <p id="rfc.section.1.2.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
     885      <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>
     886      <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.3"><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.
     887      </p>
     888      <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
    791889         (hexadecimal 0-9/A-F/a-f), HTAB (horizontal tab), LF (line feed), OCTET (any 8-bit sequence of data), SP (space), and VCHAR
    792890         (any visible US-ASCII character).
    793891      </p>
    794       <h3 id="rfc.section.1.2.1"><a href="#rfc.section.1.2.1">1.2.1</a>&nbsp;<a id="core.rules" href="#core.rules">Core Rules</a></h3>
    795       <p id="rfc.section.1.2.1.p.1">The core rules below are 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>:
     892      <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>
     893      <p id="rfc.section.1.3.1.p.1">The core rules below are 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>:
    796894      </p>
    797895      <div id="rfc.figure.u.1"></div><pre class="inline">  <a href="#core.rules" class="smpl">BWS</a>           = &lt;BWS, 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#whitespace" title="Whitespace">Section 3.2.1</a>&gt;
     
    801899  <a href="#core.rules" class="smpl">quoted-string</a> = &lt;quoted-string, 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#field.components" title="Field value components">Section 3.2.4</a>&gt;
    802900  <a href="#core.rules" class="smpl">token</a>         = &lt;token, defined in <a href="#Part1" id="rfc.xref.Part1.10"><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;
    803 </pre><h3 id="rfc.section.1.2.2"><a href="#rfc.section.1.2.2">1.2.2</a>&nbsp;<a id="abnf.dependencies" href="#abnf.dependencies">ABNF Rules defined in other Parts of the Specification</a></h3>
    804       <p id="rfc.section.1.2.2.p.1">The ABNF rules below are defined in other parts:</p>
     901</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>
     902      <p id="rfc.section.1.3.2.p.1">The ABNF rules below are defined in other parts:</p>
    805903      <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.11"><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;
    806904  <a href="#abnf.dependencies" class="smpl">comment</a>       = &lt;comment, defined in <a href="#Part1" id="rfc.xref.Part1.12"><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;
     
    811909      </p>
    812910      <div id="rfc.figure.u.3"></div><pre class="inline"><span id="rfc.iref.g.1"></span>  <a href="#methods" class="smpl">method</a>         = <a href="#core.rules" class="smpl">token</a>
    813 </pre><p id="rfc.section.2.p.3">The list of methods allowed by a resource can be specified in an Allow header field (<a href="#header.allow" id="rfc.xref.header.allow.1" title="Allow">Section&nbsp;7.1</a>). The status code of the response always notifies the client whether a method is currently allowed on a resource, since the
     911</pre><p id="rfc.section.2.p.3">The list of methods allowed by a resource can be specified in an Allow header field (<a href="#header.allow" id="rfc.xref.header.allow.1" title="Allow">Section&nbsp;11.1</a>). The status code of the response always notifies the client whether a method is currently allowed on a resource, since the
    814912         set of allowed methods can change dynamically. An origin server <em class="bcp14">SHOULD</em> respond with the status code 405 (Method Not Allowed) if the method is known by the origin server but not allowed for the
    815913         resource, and 501 (Not Implemented) if the method is unrecognized or not implemented by the origin server. The methods GET
     
    817915      </p>
    818916      <h2 id="rfc.section.2.1"><a href="#rfc.section.2.1">2.1</a>&nbsp;<a id="safe.and.idempotent" href="#safe.and.idempotent">Safe and Idempotent Methods</a></h2>
    819       <div id="rfc.iref.s.1"></div>
     917      <div id="rfc.iref.s.2"></div>
    820918      <h3 id="rfc.section.2.1.1"><a href="#rfc.section.2.1.1">2.1.1</a>&nbsp;<a id="safe.methods" href="#safe.methods">Safe Methods</a></h3>
    821919      <p id="rfc.section.2.1.1.p.1">Implementors need to be aware that the software represents the user in their interactions over the Internet, and need to allow
     
    891989         but might be defined by future extensions to HTTP. Content negotiation <em class="bcp14">MAY</em> be used to select the appropriate response format. If no response body is included, the response <em class="bcp14">MUST</em> include a Content-Length field with a field-value of "0".
    892990      </p>
    893       <p id="rfc.section.2.3.1.p.7">The Max-Forwards header field <em class="bcp14">MAY</em> be used to target a specific proxy in the request chain (see <a href="#header.max-forwards" id="rfc.xref.header.max-forwards.1" title="Max-Forwards">Section&nbsp;7.6</a>). If no Max-Forwards field is present in the request, then the forwarded request <em class="bcp14">MUST NOT</em> include a Max-Forwards field.
     991      <p id="rfc.section.2.3.1.p.7">The Max-Forwards header field <em class="bcp14">MAY</em> be used to target a specific proxy in the request chain (see <a href="#header.max-forwards" id="rfc.xref.header.max-forwards.1" title="Max-Forwards">Section&nbsp;11.6</a>). If no Max-Forwards field is present in the request, then the forwarded request <em class="bcp14">MUST NOT</em> include a Max-Forwards field.
    894992      </p>
    895993      <h3 id="rfc.section.2.3.2"><a href="#rfc.section.2.3.2">2.3.2</a>&nbsp;<a id="GET" href="#GET">GET</a></h3>
     
    9151013      <p id="rfc.section.2.3.2.p.6">The response to a GET request is cacheable and <em class="bcp14">MAY</em> be used to satisfy subsequent GET and HEAD requests (see <a href="#Part6" id="rfc.xref.Part6.2"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>).
    9161014      </p>
    917       <p id="rfc.section.2.3.2.p.7">See <a href="#encoding.sensitive.information.in.uris" title="Encoding Sensitive Information in URIs">Section&nbsp;9.2</a> for security considerations when used for forms.
     1015      <p id="rfc.section.2.3.2.p.7">See <a href="#encoding.sensitive.information.in.uris" title="Encoding Sensitive Information in URIs">Section&nbsp;13.2</a> for security considerations when used for forms.
    9181016      </p>
    9191017      <h3 id="rfc.section.2.3.3"><a href="#rfc.section.2.3.3">2.3.3</a>&nbsp;<a id="HEAD" href="#HEAD">HEAD</a></h3>
     
    9491047      </p>
    9501048      <p id="rfc.section.2.3.4.p.4">If a resource has been created on the origin server, the response <em class="bcp14">SHOULD</em> be 201 (Created) and contain a representation which describes the status of the request and refers to the new resource, and
    951          a Location header field (see <a href="#header.location" id="rfc.xref.header.location.1" title="Location">Section&nbsp;7.5</a>).
    952       </p>
    953       <p id="rfc.section.2.3.4.p.5">Responses to POST requests are only cacheable when they include explicit freshness information (see <a href="p6-cache.html#calculating.freshness.lifetime" title="Calculating Freshness Lifetime">Section 2.3.1</a> of <a href="#Part6" id="rfc.xref.Part6.4"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>). A cached POST response with a Content-Location header field (see <a href="p3-payload.html#header.content-location" title="Content-Location">Section 6.7</a> of <a href="#Part3" id="rfc.xref.Part3.1"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>) whose value is the effective Request URI <em class="bcp14">MAY</em> be used to satisfy subsequent GET and HEAD requests.
     1049         a Location header field (see <a href="#header.location" id="rfc.xref.header.location.1" title="Location">Section&nbsp;11.5</a>).
     1050      </p>
     1051      <p id="rfc.section.2.3.4.p.5">Responses to POST requests are only cacheable when they include explicit freshness information (see <a href="p6-cache.html#calculating.freshness.lifetime" title="Calculating Freshness Lifetime">Section 2.3.1</a> of <a href="#Part6" id="rfc.xref.Part6.4"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>). A cached POST response with a Content-Location header field (see <a href="#header.content-location" id="rfc.xref.header.content-location.1" title="Content-Location">Section&nbsp;11.17</a>) whose value is the effective Request URI <em class="bcp14">MAY</em> be used to satisfy subsequent GET and HEAD requests.
    9541052      </p>
    9551053      <p id="rfc.section.2.3.4.p.6">Note that POST caching is not widely implemented. However, the 303 (See Other) response can be used to direct the user agent
     
    10391137      <div id="rfc.iref.m.7"></div>
    10401138      <p id="rfc.section.2.3.7.p.1">The TRACE method requests a remote, application-layer loop-back of the request message. The final recipient of the request <em class="bcp14">SHOULD</em> reflect the message received back to the client as the message body of a 200 (OK) response. The final recipient is either
    1041          the origin server or the first proxy to receive a Max-Forwards value of zero (0) in the request (see <a href="#header.max-forwards" id="rfc.xref.header.max-forwards.2" title="Max-Forwards">Section&nbsp;7.6</a>). A TRACE request <em class="bcp14">MUST NOT</em> include a message body.
     1139         the origin server or the first proxy to receive a Max-Forwards value of zero (0) in the request (see <a href="#header.max-forwards" id="rfc.xref.header.max-forwards.2" title="Max-Forwards">Section&nbsp;11.6</a>). A TRACE request <em class="bcp14">MUST NOT</em> include a message body.
    10421140      </p>
    10431141      <p id="rfc.section.2.3.7.p.2">TRACE allows the client to see what is being received at the other end of the request chain and use that data for testing
     
    10481146      <p id="rfc.section.2.3.7.p.3">If the request is valid, the response <em class="bcp14">SHOULD</em> have a Content-Type of "message/http" (see <a href="p1-messaging.html#internet.media.type.message.http" title="Internet Media Type message/http">Section 7.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>) and contain a message body that encloses a copy of the entire request message. Responses to the TRACE method are not cacheable.
    10491147      </p>
    1050       <div id="rfc.iref.c.1"></div>
     1148      <div id="rfc.iref.c.2"></div>
    10511149      <div id="rfc.iref.m.8"></div>
    10521150      <h3 id="rfc.section.2.3.8"><a href="#rfc.section.2.3.8">2.3.8</a>&nbsp;<a id="CONNECT" href="#CONNECT">CONNECT</a></h3>
     
    11141212         double quotes will likely cause unnecessary confusion.
    11151213      </p>
    1116       <p id="rfc.section.3.1.p.8">Many header fields use a format including (case-insensitively) named parameters (for instance, Content-Type, defined in <a href="p3-payload.html#header.content-type" title="Content-Type">Section 6.8</a> of <a href="#Part3" id="rfc.xref.Part3.2"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>). Allowing both unquoted (token) and quoted (quoted-string) syntax for the parameter value enables recipients to use existing
     1214      <p id="rfc.section.3.1.p.8">Many header fields use a format including (case-insensitively) named parameters (for instance, Content-Type, defined in <a href="#header.content-type" id="rfc.xref.header.content-type.1" title="Content-Type">Section&nbsp;11.18</a>). Allowing both unquoted (token) and quoted (quoted-string) syntax for the parameter value enables recipients to use existing
    11171215         parser components. When allowing both forms, the meaning of a parameter value ought to be independent of the syntax used for
    1118          it (for an example, see the notes on parameter handling for media types in <a href="p3-payload.html#media.types" title="Media Types">Section 2.3</a> of <a href="#Part3" id="rfc.xref.Part3.3"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>).
     1216         it (for an example, see the notes on parameter handling for media types in <a href="#media.types" title="Media Types">Section&nbsp;7.3</a>).
    11191217      </p>
    11201218      <p id="rfc.section.3.1.p.9">Authors of specifications defining new header fields are advised to consider documenting: </p>
     
    11711269               <tr>
    11721270                  <td class="left">Accept</td>
    1173                   <td class="left"><a href="p3-payload.html#header.accept" title="Accept">Section 6.1</a> of <a href="#Part3" id="rfc.xref.Part3.4"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a></td>
     1271                  <td class="left"><a href="#header.accept" id="rfc.xref.header.accept.1" title="Accept">Section&nbsp;11.11</a></td>
    11741272               </tr>
    11751273               <tr>
    11761274                  <td class="left">Accept-Charset</td>
    1177                   <td class="left"><a href="p3-payload.html#header.accept-charset" title="Accept-Charset">Section 6.2</a> of <a href="#Part3" id="rfc.xref.Part3.5"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a></td>
     1275                  <td class="left"><a href="#header.accept-charset" id="rfc.xref.header.accept-charset.1" title="Accept-Charset">Section&nbsp;11.12</a></td>
    11781276               </tr>
    11791277               <tr>
    11801278                  <td class="left">Accept-Encoding</td>
    1181                   <td class="left"><a href="p3-payload.html#header.accept-encoding" title="Accept-Encoding">Section 6.3</a> of <a href="#Part3" id="rfc.xref.Part3.6"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a></td>
     1279                  <td class="left"><a href="#header.accept-encoding" id="rfc.xref.header.accept-encoding.1" title="Accept-Encoding">Section&nbsp;11.13</a></td>
    11821280               </tr>
    11831281               <tr>
    11841282                  <td class="left">Accept-Language</td>
    1185                   <td class="left"><a href="p3-payload.html#header.accept-language" title="Accept-Language">Section 6.4</a> of <a href="#Part3" id="rfc.xref.Part3.7"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a></td>
     1283                  <td class="left"><a href="#header.accept-language" id="rfc.xref.header.accept-language.1" title="Accept-Language">Section&nbsp;11.14</a></td>
    11861284               </tr>
    11871285               <tr>
     
    11911289               <tr>
    11921290                  <td class="left">Expect</td>
    1193                   <td class="left"><a href="#header.expect" id="rfc.xref.header.expect.1" title="Expect">Section&nbsp;7.3</a></td>
     1291                  <td class="left"><a href="#header.expect" id="rfc.xref.header.expect.1" title="Expect">Section&nbsp;11.3</a></td>
    11941292               </tr>
    11951293               <tr>
    11961294                  <td class="left">From</td>
    1197                   <td class="left"><a href="#header.from" id="rfc.xref.header.from.1" title="From">Section&nbsp;7.4</a></td>
     1295                  <td class="left"><a href="#header.from" id="rfc.xref.header.from.1" title="From">Section&nbsp;11.4</a></td>
    11981296               </tr>
    11991297               <tr>
     
    12231321               <tr>
    12241322                  <td class="left">Max-Forwards</td>
    1225                   <td class="left"><a href="#header.max-forwards" id="rfc.xref.header.max-forwards.3" title="Max-Forwards">Section&nbsp;7.6</a></td>
     1323                  <td class="left"><a href="#header.max-forwards" id="rfc.xref.header.max-forwards.3" title="Max-Forwards">Section&nbsp;11.6</a></td>
    12261324               </tr>
    12271325               <tr>
     
    12351333               <tr>
    12361334                  <td class="left">Referer</td>
    1237                   <td class="left"><a href="#header.referer" id="rfc.xref.header.referer.1" title="Referer">Section&nbsp;7.7</a></td>
     1335                  <td class="left"><a href="#header.referer" id="rfc.xref.header.referer.1" title="Referer">Section&nbsp;11.7</a></td>
    12381336               </tr>
    12391337               <tr>
     
    12431341               <tr>
    12441342                  <td class="left">User-Agent</td>
    1245                   <td class="left"><a href="#header.user-agent" id="rfc.xref.header.user-agent.1" title="User-Agent">Section&nbsp;7.10</a></td>
     1343                  <td class="left"><a href="#header.user-agent" id="rfc.xref.header.user-agent.1" title="User-Agent">Section&nbsp;11.10</a></td>
    12461344               </tr>
    12471345            </tbody>
     
    12711369               <tr>
    12721370                  <td class="left">Allow</td>
    1273                   <td class="left"><a href="#header.allow" id="rfc.xref.header.allow.2" title="Allow">Section&nbsp;7.1</a></td>
     1371                  <td class="left"><a href="#header.allow" id="rfc.xref.header.allow.2" title="Allow">Section&nbsp;11.1</a></td>
    12741372               </tr>
    12751373               <tr>
    12761374                  <td class="left">Date</td>
    1277                   <td class="left"><a href="#header.date" id="rfc.xref.header.date.1" title="Date">Section&nbsp;7.2</a></td>
     1375                  <td class="left"><a href="#header.date" id="rfc.xref.header.date.1" title="Date">Section&nbsp;11.2</a></td>
    12781376               </tr>
    12791377               <tr>
     
    12831381               <tr>
    12841382                  <td class="left">Location</td>
    1285                   <td class="left"><a href="#header.location" id="rfc.xref.header.location.2" title="Location">Section&nbsp;7.5</a></td>
     1383                  <td class="left"><a href="#header.location" id="rfc.xref.header.location.2" title="Location">Section&nbsp;11.5</a></td>
    12861384               </tr>
    12871385               <tr>
     
    12911389               <tr>
    12921390                  <td class="left">Retry-After</td>
    1293                   <td class="left"><a href="#header.retry-after" id="rfc.xref.header.retry-after.1" title="Retry-After">Section&nbsp;7.8</a></td>
     1391                  <td class="left"><a href="#header.retry-after" id="rfc.xref.header.retry-after.1" title="Retry-After">Section&nbsp;11.8</a></td>
    12941392               </tr>
    12951393               <tr>
    12961394                  <td class="left">Server</td>
    1297                   <td class="left"><a href="#header.server" id="rfc.xref.header.server.1" title="Server">Section&nbsp;7.9</a></td>
     1395                  <td class="left"><a href="#header.server" id="rfc.xref.header.server.1" title="Server">Section&nbsp;11.9</a></td>
    12981396               </tr>
    12991397               <tr>
     
    13321430      </ul>
    13331431      <p id="rfc.section.4.p.6">For most status codes the response can carry a payload, in which case a Content-Type header field indicates the payload's
    1334          media type (<a href="p3-payload.html#header.content-type" title="Content-Type">Section 6.8</a> of <a href="#Part3" id="rfc.xref.Part3.8"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>).
     1432         media type (<a href="#header.content-type" id="rfc.xref.header.content-type.2" title="Content-Type">Section&nbsp;11.18</a>).
    13351433      </p>
    13361434      <h2 id="rfc.section.4.1"><a href="#rfc.section.4.1">4.1</a>&nbsp;<a id="overview.of.status.codes" href="#overview.of.status.codes">Overview of Status Codes</a></h2>
     
    15921690         a request, then it need not forward the corresponding 100 (Continue) response(s).)
    15931691      </p>
    1594       <div id="rfc.iref.22"></div>
    1595       <div id="rfc.iref.s.2"></div>
     1692      <div id="rfc.iref.24"></div>
     1693      <div id="rfc.iref.s.3"></div>
    15961694      <h3 id="rfc.section.4.3.1"><a href="#rfc.section.4.3.1">4.3.1</a>&nbsp;<a id="status.100" href="#status.100">100 Continue</a></h3>
    15971695      <p id="rfc.section.4.3.1.p.1">The client <em class="bcp14">SHOULD</em> continue with its request. This interim response is used to inform the client that the initial part of the request has been
     
    15991697         server <em class="bcp14">MUST</em> send a final response after the request has been completed. See <a href="p1-messaging.html#use.of.the.100.status" title="Use of the 100 (Continue) Status">Section 6.4.3</a> of <a href="#Part1" id="rfc.xref.Part1.30"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a> for detailed discussion of the use and handling of this status code.
    16001698      </p>
    1601       <div id="rfc.iref.23"></div>
    1602       <div id="rfc.iref.s.3"></div>
     1699      <div id="rfc.iref.25"></div>
     1700      <div id="rfc.iref.s.4"></div>
    16031701      <h3 id="rfc.section.4.3.2"><a href="#rfc.section.4.3.2">4.3.2</a>&nbsp;<a id="status.101" href="#status.101">101 Switching Protocols</a></h3>
    16041702      <p id="rfc.section.4.3.2.p.1">The server understands and is willing to comply with the client's request, via the Upgrade message header field (<a href="p1-messaging.html#header.upgrade" title="Upgrade">Section 6.5</a> of <a href="#Part1" id="rfc.xref.Part1.31"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>), for a change in the application protocol being used on this connection. The server will switch protocols to those defined
     
    16111709      <h2 id="rfc.section.4.4"><a href="#rfc.section.4.4">4.4</a>&nbsp;<a id="status.2xx" href="#status.2xx">Successful 2xx</a></h2>
    16121710      <p id="rfc.section.4.4.p.1">This class of status code indicates that the client's request was successfully received, understood, and accepted.</p>
    1613       <div id="rfc.iref.24"></div>
    1614       <div id="rfc.iref.s.4"></div>
     1711      <div id="rfc.iref.26"></div>
     1712      <div id="rfc.iref.s.5"></div>
    16151713      <h3 id="rfc.section.4.4.1"><a href="#rfc.section.4.4.1">4.4.1</a>&nbsp;<a id="status.200" href="#status.200">200 OK</a></h3>
    16161714      <p id="rfc.section.4.4.1.p.1">The request has succeeded. The payload returned with the response is dependent on the method used in the request, for example: </p>
     
    16271725      <p id="rfc.section.4.4.1.p.2">Caches <em class="bcp14">MAY</em> use a heuristic (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 2.3.1.1</a> of <a href="#Part6" id="rfc.xref.Part6.11"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>) to determine freshness for 200 responses.
    16281726      </p>
    1629       <div id="rfc.iref.25"></div>
    1630       <div id="rfc.iref.s.5"></div>
     1727      <div id="rfc.iref.27"></div>
     1728      <div id="rfc.iref.s.6"></div>
    16311729      <h3 id="rfc.section.4.4.2"><a href="#rfc.section.4.4.2">4.4.2</a>&nbsp;<a id="status.201" href="#status.201">201 Created</a></h3>
    16321730      <p id="rfc.section.4.4.2.p.1">The request has been fulfilled and has resulted in a new resource being created.</p>
     
    16401738         just created (see <a href="p4-conditional.html#header.etag" title="ETag">Section 2.3</a> of <a href="#Part4" id="rfc.xref.Part4.9"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>).
    16411739      </p>
    1642       <div id="rfc.iref.26"></div>
    1643       <div id="rfc.iref.s.6"></div>
     1740      <div id="rfc.iref.28"></div>
     1741      <div id="rfc.iref.s.7"></div>
    16441742      <h3 id="rfc.section.4.4.3"><a href="#rfc.section.4.4.3">4.4.3</a>&nbsp;<a id="status.202" href="#status.202">202 Accepted</a></h3>
    16451743      <p id="rfc.section.4.4.3.p.1">The request has been accepted for processing, but the processing has not been completed. The request might or might not eventually
     
    16521750         user can expect the request to be fulfilled.
    16531751      </p>
    1654       <div id="rfc.iref.27"></div>
    1655       <div id="rfc.iref.s.7"></div>
     1752      <div id="rfc.iref.29"></div>
     1753      <div id="rfc.iref.s.8"></div>
    16561754      <h3 id="rfc.section.4.4.4"><a href="#rfc.section.4.4.4">4.4.4</a>&nbsp;<a id="status.203" href="#status.203">203 Non-Authoritative Information</a></h3>
    16571755      <p id="rfc.section.4.4.4.p.1">The representation in the response has been transformed or otherwise modified by a transforming proxy (<a href="p1-messaging.html#intermediaries" title="Intermediaries">Section 2.3</a> of <a href="#Part1" id="rfc.xref.Part1.32"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>). Note that the behavior of transforming intermediaries is controlled by the no-transform Cache-Control directive (<a href="p6-cache.html#header.cache-control" title="Cache-Control">Section 3.2</a> of <a href="#Part6" id="rfc.xref.Part6.12"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>).
     
    16621760      <p id="rfc.section.4.4.4.p.3">Caches <em class="bcp14">MAY</em> use a heuristic (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 2.3.1.1</a> of <a href="#Part6" id="rfc.xref.Part6.14"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>) to determine freshness for 203 responses.
    16631761      </p>
    1664       <div id="rfc.iref.28"></div>
    1665       <div id="rfc.iref.s.8"></div>
     1762      <div id="rfc.iref.30"></div>
     1763      <div id="rfc.iref.s.9"></div>
    16661764      <h3 id="rfc.section.4.4.5"><a href="#rfc.section.4.4.5">4.4.5</a>&nbsp;<a id="status.204" href="#status.204">204 No Content</a></h3>
    16671765      <p id="rfc.section.4.4.5.p.1">The 204 (No Content) status code indicates that the server has successfully fulfilled the request and that there is no additional
     
    16831781      <p id="rfc.section.4.4.5.p.5">The 204 response <em class="bcp14">MUST NOT</em> include a message body, and thus is always terminated by the first empty line after the header fields.
    16841782      </p>
    1685       <div id="rfc.iref.29"></div>
    1686       <div id="rfc.iref.s.9"></div>
     1783      <div id="rfc.iref.31"></div>
     1784      <div id="rfc.iref.s.10"></div>
    16871785      <h3 id="rfc.section.4.4.6"><a href="#rfc.section.4.4.6">4.4.6</a>&nbsp;<a id="status.205" href="#status.205">205 Reset Content</a></h3>
    16881786      <p id="rfc.section.4.4.6.p.1">The server has fulfilled the request and the user agent <em class="bcp14">SHOULD</em> reset the document view which caused the request to be sent. This response is primarily intended to allow input for actions
     
    17111809         </li>
    17121810         <li>
    1713             <p>Redirection offering a choice of matching resources for use by agent-driven content negotiation (<a href="p3-payload.html#agent-driven.negotiation" title="Agent-driven Negotiation">Section 5.2</a> of <a href="#Part3" id="rfc.xref.Part3.9"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>). This is status code 300 (Multiple Choices).
     1811            <p>Redirection offering a choice of matching resources for use by agent-driven content negotiation (<a href="#agent-driven.negotiation" title="Agent-driven Negotiation">Section&nbsp;10.2</a>). This is status code 300 (Multiple Choices).
    17141812            </p>
    17151813         </li>
     
    17281826         </p>
    17291827      </div>
    1730       <p id="rfc.section.4.5.p.4">A Location header field on a 3xx response indicates that a client <em class="bcp14">MAY</em> automatically redirect to the URI provided; see <a href="#header.location" id="rfc.xref.header.location.3" title="Location">Section&nbsp;7.5</a>.
     1828      <p id="rfc.section.4.5.p.4">A Location header field on a 3xx response indicates that a client <em class="bcp14">MAY</em> automatically redirect to the URI provided; see <a href="#header.location" id="rfc.xref.header.location.3" title="Location">Section&nbsp;11.5</a>.
    17311829      </p>
    17321830      <p id="rfc.section.4.5.p.5">Note that for methods not known to be "safe", as defined in <a href="#safe.methods" title="Safe Methods">Section&nbsp;2.1.1</a>, automatic redirection needs to done with care, since the redirect might change the conditions under which the request was
     
    17391837         </p>
    17401838      </div>
    1741       <div id="rfc.iref.30"></div>
    1742       <div id="rfc.iref.s.10"></div>
     1839      <div id="rfc.iref.32"></div>
     1840      <div id="rfc.iref.s.11"></div>
    17431841      <h3 id="rfc.section.4.5.1"><a href="#rfc.section.4.5.1">4.5.1</a>&nbsp;<a id="status.300" href="#status.300">300 Multiple Choices</a></h3>
    17441842      <p id="rfc.section.4.5.1.p.1">The target resource has more than one representation, each with its own specific location, and agent-driven negotiation information
    1745          (<a href="p3-payload.html#content.negotiation" title="Content Negotiation">Section 5</a> of <a href="#Part3" id="rfc.xref.Part3.10"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>) is being provided so that the user (or user agent) can select a preferred representation by redirecting its request to that
     1843         (<a href="#content.negotiation" title="Content Negotiation">Section&nbsp;10</a>) is being provided so that the user (or user agent) can select a preferred representation by redirecting its request to that
    17461844         location.
    17471845      </p>
     
    17541852      <p id="rfc.section.4.5.1.p.4">Caches <em class="bcp14">MAY</em> use a heuristic (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 2.3.1.1</a> of <a href="#Part6" id="rfc.xref.Part6.15"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>) to determine freshness for 300 responses.
    17551853      </p>
    1756       <div id="rfc.iref.31"></div>
    1757       <div id="rfc.iref.s.11"></div>
     1854      <div id="rfc.iref.33"></div>
     1855      <div id="rfc.iref.s.12"></div>
    17581856      <h3 id="rfc.section.4.5.2"><a href="#rfc.section.4.5.2">4.5.2</a>&nbsp;<a id="status.301" href="#status.301">301 Moved Permanently</a></h3>
    17591857      <p id="rfc.section.4.5.2.p.1">The target resource has been assigned a new permanent URI and any future references to this resource <em class="bcp14">SHOULD</em> use one of the returned URIs. Clients with link editing capabilities ought to automatically re-link references to the effective
     
    17701868         </p>
    17711869      </div>
    1772       <div id="rfc.iref.32"></div>
    1773       <div id="rfc.iref.s.12"></div>
     1870      <div id="rfc.iref.34"></div>
     1871      <div id="rfc.iref.s.13"></div>
    17741872      <h3 id="rfc.section.4.5.3"><a href="#rfc.section.4.5.3">4.5.3</a>&nbsp;<a id="status.302" href="#status.302">302 Found</a></h3>
    17751873      <p id="rfc.section.4.5.3.p.1">The target resource resides temporarily under a different URI. Since the redirection might be altered on occasion, the client <em class="bcp14">SHOULD</em> continue to use the effective request URI for future requests.
     
    17831881         </p>
    17841882      </div>
    1785       <div id="rfc.iref.33"></div>
    1786       <div id="rfc.iref.s.13"></div>
     1883      <div id="rfc.iref.35"></div>
     1884      <div id="rfc.iref.s.14"></div>
    17871885      <h3 id="rfc.section.4.5.4"><a href="#rfc.section.4.5.4">4.5.4</a>&nbsp;<a id="status.303" href="#status.303">303 See Other</a></h3>
    17881886      <p id="rfc.section.4.5.4.p.1">The 303 status code indicates that the server is redirecting the user agent to a different resource, as indicated by a URI
     
    18041902      <p id="rfc.section.4.5.4.p.4">Except for responses to a HEAD request, the representation of a 303 response <em class="bcp14">SHOULD</em> contain a short hypertext note with a hyperlink to the Location URI.
    18051903      </p>
    1806       <div id="rfc.iref.34"></div>
    1807       <div id="rfc.iref.s.14"></div>
     1904      <div id="rfc.iref.36"></div>
     1905      <div id="rfc.iref.s.15"></div>
    18081906      <h3 id="rfc.section.4.5.5"><a href="#rfc.section.4.5.5">4.5.5</a>&nbsp;<a id="status.305" href="#status.305">305 Use Proxy</a></h3>
    1809       <p id="rfc.section.4.5.5.p.1">The 305 status code was defined in a previous version of this specification (see <a href="#changes.from.rfc.2616" title="Changes from RFC 2616">Appendix&nbsp;A</a>), and is now deprecated.
    1810       </p>
    1811       <div id="rfc.iref.35"></div>
    1812       <div id="rfc.iref.s.15"></div>
     1907      <p id="rfc.section.4.5.5.p.1">The 305 status code was defined in a previous version of this specification (see <a href="#changes.from.rfc.2616" title="Changes from RFC 2616">Appendix&nbsp;C</a>), and is now deprecated.
     1908      </p>
     1909      <div id="rfc.iref.37"></div>
     1910      <div id="rfc.iref.s.16"></div>
    18131911      <h3 id="rfc.section.4.5.6"><a href="#rfc.section.4.5.6">4.5.6</a>&nbsp;<a id="status.306" href="#status.306">306 (Unused)</a></h3>
    18141912      <p id="rfc.section.4.5.6.p.1">The 306 status code was used in a previous version of the specification, is no longer used, and the code is reserved.</p>
    1815       <div id="rfc.iref.36"></div>
    1816       <div id="rfc.iref.s.16"></div>
     1913      <div id="rfc.iref.38"></div>
     1914      <div id="rfc.iref.s.17"></div>
    18171915      <h3 id="rfc.section.4.5.7"><a href="#rfc.section.4.5.7">4.5.7</a>&nbsp;<a id="status.307" href="#status.307">307 Temporary Redirect</a></h3>
    18181916      <p id="rfc.section.4.5.7.p.1">The target resource resides temporarily under a different URI. Since the redirection can change over time, the client <em class="bcp14">SHOULD</em> continue to use the effective request URI for future requests.
     
    18311929         These status codes are applicable to any request method. User agents <em class="bcp14">SHOULD</em> display any included representation to the user.
    18321930      </p>
    1833       <div id="rfc.iref.37"></div>
    1834       <div id="rfc.iref.s.17"></div>
     1931      <div id="rfc.iref.39"></div>
     1932      <div id="rfc.iref.s.18"></div>
    18351933      <h3 id="rfc.section.4.6.1"><a href="#rfc.section.4.6.1">4.6.1</a>&nbsp;<a id="status.400" href="#status.400">400 Bad Request</a></h3>
    18361934      <p id="rfc.section.4.6.1.p.1">The server cannot or will not process the request, due to a client error (e.g., malformed syntax).</p>
    1837       <div id="rfc.iref.38"></div>
    1838       <div id="rfc.iref.s.18"></div>
     1935      <div id="rfc.iref.40"></div>
     1936      <div id="rfc.iref.s.19"></div>
    18391937      <h3 id="rfc.section.4.6.2"><a href="#rfc.section.4.6.2">4.6.2</a>&nbsp;<a id="status.402" href="#status.402">402 Payment Required</a></h3>
    18401938      <p id="rfc.section.4.6.2.p.1">This code is reserved for future use.</p>
    1841       <div id="rfc.iref.39"></div>
    1842       <div id="rfc.iref.s.19"></div>
     1939      <div id="rfc.iref.41"></div>
     1940      <div id="rfc.iref.s.20"></div>
    18431941      <h3 id="rfc.section.4.6.3"><a href="#rfc.section.4.6.3">4.6.3</a>&nbsp;<a id="status.403" href="#status.403">403 Forbidden</a></h3>
    18441942      <p id="rfc.section.4.6.3.p.1">The server understood the request, but refuses to authorize it. Providing different user authentication credentials might
     
    18481946         to the client, the status code 404 (Not Found) <em class="bcp14">MAY</em> be used instead.
    18491947      </p>
    1850       <div id="rfc.iref.40"></div>
    1851       <div id="rfc.iref.s.20"></div>
     1948      <div id="rfc.iref.42"></div>
     1949      <div id="rfc.iref.s.21"></div>
    18521950      <h3 id="rfc.section.4.6.4"><a href="#rfc.section.4.6.4">4.6.4</a>&nbsp;<a id="status.404" href="#status.404">404 Not Found</a></h3>
    18531951      <p id="rfc.section.4.6.4.p.1">The server has not found anything matching the effective request URI. No indication is given of whether the condition is temporary
     
    18561954         has been refused, or when no other response is applicable.
    18571955      </p>
    1858       <div id="rfc.iref.41"></div>
    1859       <div id="rfc.iref.s.21"></div>
     1956      <div id="rfc.iref.43"></div>
     1957      <div id="rfc.iref.s.22"></div>
    18601958      <h3 id="rfc.section.4.6.5"><a href="#rfc.section.4.6.5">4.6.5</a>&nbsp;<a id="status.405" href="#status.405">405 Method Not Allowed</a></h3>
    18611959      <p id="rfc.section.4.6.5.p.1">The method specified in the request-line is not allowed for the target resource. The response <em class="bcp14">MUST</em> include an Allow header field containing a list of valid methods for the requested resource.
    18621960      </p>
    1863       <div id="rfc.iref.42"></div>
    1864       <div id="rfc.iref.s.22"></div>
     1961      <div id="rfc.iref.44"></div>
     1962      <div id="rfc.iref.s.23"></div>
    18651963      <h3 id="rfc.section.4.6.6"><a href="#rfc.section.4.6.6">4.6.6</a>&nbsp;<a id="status.406" href="#status.406">406 Not Acceptable</a></h3>
    18661964      <p id="rfc.section.4.6.6.p.1">The resource identified by the request is only capable of generating response representations which have content characteristics
    1867          not acceptable according to the Accept and Accept-* header fields sent in the request (see <a href="p3-payload.html#header.field.definitions" title="Header Field Definitions">Section 6</a> of <a href="#Part3" id="rfc.xref.Part3.11"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>).
     1965         not acceptable according to the Accept and Accept-* header fields sent in the request.
    18681966      </p>
    18691967      <p id="rfc.section.4.6.6.p.2">Unless it was a HEAD request, the response <em class="bcp14">SHOULD</em> include a representation containing a list of available representation characteristics and location(s) from which the user
     
    18791977      <p id="rfc.section.4.6.6.p.4">If the response could be unacceptable, a user agent <em class="bcp14">SHOULD</em> temporarily stop receipt of more data and query the user for a decision on further actions.
    18801978      </p>
    1881       <div id="rfc.iref.43"></div>
    1882       <div id="rfc.iref.s.23"></div>
     1979      <div id="rfc.iref.45"></div>
     1980      <div id="rfc.iref.s.24"></div>
    18831981      <h3 id="rfc.section.4.6.7"><a href="#rfc.section.4.6.7">4.6.7</a>&nbsp;<a id="status.408" href="#status.408">408 Request Timeout</a></h3>
    18841982      <p id="rfc.section.4.6.7.p.1">The client did not produce a request within the time that the server was prepared to wait. The client <em class="bcp14">MAY</em> repeat the request without modifications at any later time.
    18851983      </p>
    1886       <div id="rfc.iref.44"></div>
    1887       <div id="rfc.iref.s.24"></div>
     1984      <div id="rfc.iref.46"></div>
     1985      <div id="rfc.iref.s.25"></div>
    18881986      <h3 id="rfc.section.4.6.8"><a href="#rfc.section.4.6.8">4.6.8</a>&nbsp;<a id="status.409" href="#status.409">409 Conflict</a></h3>
    18891987      <p id="rfc.section.4.6.8.p.1">The request could not be completed due to a conflict with the current state of the resource. This code is only allowed in
     
    18971995         contain a list of the differences between the two versions.
    18981996      </p>
    1899       <div id="rfc.iref.45"></div>
    1900       <div id="rfc.iref.s.25"></div>
     1997      <div id="rfc.iref.47"></div>
     1998      <div id="rfc.iref.s.26"></div>
    19011999      <h3 id="rfc.section.4.6.9"><a href="#rfc.section.4.6.9">4.6.9</a>&nbsp;<a id="status.410" href="#status.410">410 Gone</a></h3>
    19022000      <p id="rfc.section.4.6.9.p.1">The target resource is no longer available at the server and no forwarding address is known. This condition is expected to
     
    19122010      <p id="rfc.section.4.6.9.p.3">Caches <em class="bcp14">MAY</em> use a heuristic (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 2.3.1.1</a> of <a href="#Part6" id="rfc.xref.Part6.17"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>) to determine freshness for 410 responses.
    19132011      </p>
    1914       <div id="rfc.iref.46"></div>
    1915       <div id="rfc.iref.s.26"></div>
     2012      <div id="rfc.iref.48"></div>
     2013      <div id="rfc.iref.s.27"></div>
    19162014      <h3 id="rfc.section.4.6.10"><a href="#rfc.section.4.6.10">4.6.10</a>&nbsp;<a id="status.411" href="#status.411">411 Length Required</a></h3>
    19172015      <p id="rfc.section.4.6.10.p.1">The server refuses to accept the request without a defined Content-Length. The client <em class="bcp14">MAY</em> repeat the request if it adds a valid Content-Length header field containing the length of the message body in the request
    19182016         message.
    19192017      </p>
    1920       <div id="rfc.iref.47"></div>
    1921       <div id="rfc.iref.s.27"></div>
     2018      <div id="rfc.iref.49"></div>
     2019      <div id="rfc.iref.s.28"></div>
    19222020      <h3 id="rfc.section.4.6.11"><a href="#rfc.section.4.6.11">4.6.11</a>&nbsp;<a id="status.413" href="#status.413">413 Request Representation Too Large</a></h3>
    19232021      <p id="rfc.section.4.6.11.p.1">The server is refusing to process a request because the request representation is larger than the server is willing or able
     
    19262024      <p id="rfc.section.4.6.11.p.2">If the condition is temporary, the server <em class="bcp14">SHOULD</em> include a Retry-After header field to indicate that it is temporary and after what time the client <em class="bcp14">MAY</em> try again.
    19272025      </p>
    1928       <div id="rfc.iref.48"></div>
    1929       <div id="rfc.iref.s.28"></div>
     2026      <div id="rfc.iref.50"></div>
     2027      <div id="rfc.iref.s.29"></div>
    19302028      <h3 id="rfc.section.4.6.12"><a href="#rfc.section.4.6.12">4.6.12</a>&nbsp;<a id="status.414" href="#status.414">414 URI Too Long</a></h3>
    19312029      <p id="rfc.section.4.6.12.p.1">The server is refusing to service the request because the effective request URI is longer than the server is willing to interpret.
     
    19352033         in some servers using fixed-length buffers for reading or manipulating the request-target.
    19362034      </p>
    1937       <div id="rfc.iref.49"></div>
    1938       <div id="rfc.iref.s.29"></div>
     2035      <div id="rfc.iref.51"></div>
     2036      <div id="rfc.iref.s.30"></div>
    19392037      <h3 id="rfc.section.4.6.13"><a href="#rfc.section.4.6.13">4.6.13</a>&nbsp;<a id="status.415" href="#status.415">415 Unsupported Media Type</a></h3>
    19402038      <p id="rfc.section.4.6.13.p.1">The server is refusing to service the request because the request payload is in a format not supported by this request method
    19412039         on the target resource.
    19422040      </p>
    1943       <div id="rfc.iref.50"></div>
    1944       <div id="rfc.iref.s.30"></div>
     2041      <div id="rfc.iref.52"></div>
     2042      <div id="rfc.iref.s.31"></div>
    19452043      <h3 id="rfc.section.4.6.14"><a href="#rfc.section.4.6.14">4.6.14</a>&nbsp;<a id="status.417" href="#status.417">417 Expectation Failed</a></h3>
    1946       <p id="rfc.section.4.6.14.p.1">The expectation given in an Expect header field (see <a href="#header.expect" id="rfc.xref.header.expect.2" title="Expect">Section&nbsp;7.3</a>) could not be met by this server, or, if the server is a proxy, the server has unambiguous evidence that the request could
     2044      <p id="rfc.section.4.6.14.p.1">The expectation given in an Expect header field (see <a href="#header.expect" id="rfc.xref.header.expect.2" title="Expect">Section&nbsp;11.3</a>) could not be met by this server, or, if the server is a proxy, the server has unambiguous evidence that the request could
    19472045         not be met by the next-hop server.
    19482046      </p>
    1949       <div id="rfc.iref.51"></div>
    1950       <div id="rfc.iref.s.31"></div>
     2047      <div id="rfc.iref.53"></div>
     2048      <div id="rfc.iref.s.32"></div>
    19512049      <h3 id="rfc.section.4.6.15"><a href="#rfc.section.4.6.15">4.6.15</a>&nbsp;<a id="status.426" href="#status.426">426 Upgrade Required</a></h3>
    19522050      <p id="rfc.section.4.6.15.p.1">The request can not be completed without a prior protocol upgrade. This response <em class="bcp14">MUST</em> include an Upgrade header field (<a href="p1-messaging.html#header.upgrade" title="Upgrade">Section 6.5</a> of <a href="#Part1" id="rfc.xref.Part1.34"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) specifying the required protocols.
     
    19682066         User agents <em class="bcp14">SHOULD</em> display any included representation to the user. These response codes are applicable to any request method.
    19692067      </p>
    1970       <div id="rfc.iref.52"></div>
    1971       <div id="rfc.iref.s.32"></div>
     2068      <div id="rfc.iref.54"></div>
     2069      <div id="rfc.iref.s.33"></div>
    19722070      <h3 id="rfc.section.4.7.1"><a href="#rfc.section.4.7.1">4.7.1</a>&nbsp;<a id="status.500" href="#status.500">500 Internal Server Error</a></h3>
    19732071      <p id="rfc.section.4.7.1.p.1">The server encountered an unexpected condition which prevented it from fulfilling the request.</p>
    1974       <div id="rfc.iref.53"></div>
    1975       <div id="rfc.iref.s.33"></div>
     2072      <div id="rfc.iref.55"></div>
     2073      <div id="rfc.iref.s.34"></div>
    19762074      <h3 id="rfc.section.4.7.2"><a href="#rfc.section.4.7.2">4.7.2</a>&nbsp;<a id="status.501" href="#status.501">501 Not Implemented</a></h3>
    19772075      <p id="rfc.section.4.7.2.p.1">The server does not support the functionality required to fulfill the request. This is the appropriate response when the server
    19782076         does not recognize the request method and is not capable of supporting it for any resource.
    19792077      </p>
    1980       <div id="rfc.iref.54"></div>
    1981       <div id="rfc.iref.s.34"></div>
     2078      <div id="rfc.iref.56"></div>
     2079      <div id="rfc.iref.s.35"></div>
    19822080      <h3 id="rfc.section.4.7.3"><a href="#rfc.section.4.7.3">4.7.3</a>&nbsp;<a id="status.502" href="#status.502">502 Bad Gateway</a></h3>
    19832081      <p id="rfc.section.4.7.3.p.1">The server, while acting as a gateway or proxy, received an invalid response from the upstream server it accessed in attempting
    19842082         to fulfill the request.
    19852083      </p>
    1986       <div id="rfc.iref.55"></div>
    1987       <div id="rfc.iref.s.35"></div>
     2084      <div id="rfc.iref.57"></div>
     2085      <div id="rfc.iref.s.36"></div>
    19882086      <h3 id="rfc.section.4.7.4"><a href="#rfc.section.4.7.4">4.7.4</a>&nbsp;<a id="status.503" href="#status.503">503 Service Unavailable</a></h3>
    19892087      <p id="rfc.section.4.7.4.p.1">The server is currently unable to handle the request due to a temporary overloading or maintenance of the server.</p>
    19902088      <p id="rfc.section.4.7.4.p.2">The implication is that this is a temporary condition which will be alleviated after some delay. If known, the length of the
    1991          delay <em class="bcp14">MAY</em> be indicated in a Retry-After header field (<a href="#header.retry-after" id="rfc.xref.header.retry-after.2" title="Retry-After">Section&nbsp;7.8</a>). If no Retry-After is given, the client <em class="bcp14">SHOULD</em> handle the response as it would for a 500 response.
     2089         delay <em class="bcp14">MAY</em> be indicated in a Retry-After header field (<a href="#header.retry-after" id="rfc.xref.header.retry-after.2" title="Retry-After">Section&nbsp;11.8</a>). If no Retry-After is given, the client <em class="bcp14">SHOULD</em> handle the response as it would for a 500 response.
    19922090      </p>
    19932091      <div class="note" id="rfc.section.4.7.4.p.3">
     
    19962094         </p>
    19972095      </div>
    1998       <div id="rfc.iref.56"></div>
    1999       <div id="rfc.iref.s.36"></div>
     2096      <div id="rfc.iref.58"></div>
     2097      <div id="rfc.iref.s.37"></div>
    20002098      <h3 id="rfc.section.4.7.5"><a href="#rfc.section.4.7.5">4.7.5</a>&nbsp;<a id="status.504" href="#status.504">504 Gateway Timeout</a></h3>
    20012099      <p id="rfc.section.4.7.5.p.1">The server, while acting as a gateway or proxy, did not receive a timely response from the upstream server specified by the
     
    20062104         </p>
    20072105      </div>
    2008       <div id="rfc.iref.57"></div>
    2009       <div id="rfc.iref.s.37"></div>
     2106      <div id="rfc.iref.59"></div>
     2107      <div id="rfc.iref.s.38"></div>
    20102108      <h3 id="rfc.section.4.7.6"><a href="#rfc.section.4.7.6">4.7.6</a>&nbsp;<a id="status.505" href="#status.505">505 HTTP Version Not Supported</a></h3>
    20112109      <p id="rfc.section.4.7.6.p.1">The server does not support, or refuses to support, the protocol version that was used in the request message. The server
     
    20162114      <p id="rfc.section.5.p.1">Request and Response messages <em class="bcp14">MAY</em> transfer a representation if not otherwise restricted by the request method or response status code. A representation consists
    20172115         of metadata (representation header fields) and data (representation body). When a complete or partial representation is enclosed
    2018          in an HTTP message, it is referred to as the payload of the message. HTTP representations are defined in <a href="#Part3" id="rfc.xref.Part3.12"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>.
     2116         in an HTTP message, it is referred to as the payload of the message. HTTP representations are defined in <a href="#payload" title="Payload">Section&nbsp;8</a>.
    20192117      </p>
    20202118      <p id="rfc.section.5.p.2">A representation 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.36"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>. The representation body is obtained from the message body by decoding any Transfer-Encoding that might have been applied
     
    21452243</pre><p id="rfc.section.6.2.p.5">Product tokens <em class="bcp14">SHOULD</em> be short and to the point. They <em class="bcp14">MUST NOT</em> be used for advertising or other non-essential information. Although any token octet <em class="bcp14">MAY</em> appear in a product-version, this token <em class="bcp14">SHOULD</em> only be used for a version identifier (i.e., successive versions of the same product <em class="bcp14">SHOULD</em> only differ in the product-version portion of the product value).
    21462244      </p>
    2147       <h1 id="rfc.section.7"><a href="#rfc.section.7">7.</a>&nbsp;<a id="header.field.definitions" href="#header.field.definitions">Header Field Definitions</a></h1>
    2148       <p id="rfc.section.7.p.1">This section defines the syntax and semantics of HTTP/1.1 header fields related to request and response semantics.</p>
     2245      <h1 id="rfc.section.7"><a href="#rfc.section.7">7.</a>&nbsp;<a id="protocol.parameters" href="#protocol.parameters">Protocol Parameters</a></h1>
     2246      <h2 id="rfc.section.7.1"><a href="#rfc.section.7.1">7.1</a>&nbsp;<a id="character.sets" href="#character.sets">Character Encodings (charset)</a></h2>
     2247      <p id="rfc.section.7.1.p.1">HTTP uses charset names to indicate the character encoding of a textual representation.</p>
     2248      <div id="rule.charset">
     2249         <p id="rfc.section.7.1.p.2">  A character encoding is identified by a case-insensitive token. The complete set of tokens is defined by the IANA Character
     2250            Set registry (&lt;<a href="http://www.iana.org/assignments/character-sets">http://www.iana.org/assignments/character-sets</a>&gt;).
     2251         </p>
     2252      </div>
     2253      <div id="rfc.figure.u.18"></div><pre class="inline"><span id="rfc.iref.g.24"></span>  <a href="#rule.charset" class="smpl">charset</a> = <a href="#core.rules" class="smpl">token</a>
     2254</pre><p id="rfc.section.7.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
     2255         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.
     2256      </p>
     2257      <p id="rfc.section.7.1.p.5">HTTP uses charset in two contexts: within an Accept-Charset request header field (in which the charset value is an unquoted
     2258         token) and as the value of a parameter in a Content-Type header field (within a request or response), in which case the parameter
     2259         value of the charset parameter can be quoted.
     2260      </p>
     2261      <p id="rfc.section.7.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>.
     2262      </p>
     2263      <h2 id="rfc.section.7.2"><a href="#rfc.section.7.2">7.2</a>&nbsp;<a id="content.codings" href="#content.codings">Content Codings</a></h2>
     2264      <p id="rfc.section.7.2.p.1">Content coding values indicate an encoding transformation that has been or can be applied to a representation. Content codings
     2265         are primarily used to allow a representation to be compressed or otherwise usefully transformed without losing the identity
     2266         of its underlying media type and without loss of information. Frequently, the representation is stored in coded form, transmitted
     2267         directly, and only decoded by the recipient.
     2268      </p>
     2269      <div id="rfc.figure.u.19"></div><pre class="inline"><span id="rfc.iref.g.25"></span>  <a href="#content.codings" class="smpl">content-coding</a>   = <a href="#core.rules" class="smpl">token</a>
     2270</pre><p id="rfc.section.7.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.2" title="Accept-Encoding">Section&nbsp;11.13</a>) and Content-Encoding (<a href="#header.content-encoding" id="rfc.xref.header.content-encoding.1" title="Content-Encoding">Section&nbsp;11.15</a>) header fields. Although the value describes the content-coding, what is more important is that it indicates what decoding
     2271         mechanism will be required to remove the encoding.
     2272      </p>
     2273      <p id="rfc.section.7.2.p.4">compress<span id="rfc.iref.c.3"></span><span id="rfc.iref.c.4"></span> 
     2274      </p>
     2275      <ul class="empty">
     2276         <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.38"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>.
     2277         </li>
     2278      </ul>
     2279      <p id="rfc.section.7.2.p.5">deflate<span id="rfc.iref.d.2"></span><span id="rfc.iref.c.5"></span> 
     2280      </p>
     2281      <ul class="empty">
     2282         <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.39"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>.
     2283         </li>
     2284      </ul>
     2285      <p id="rfc.section.7.2.p.6">gzip<span id="rfc.iref.g.26"></span><span id="rfc.iref.c.6"></span> 
     2286      </p>
     2287      <ul class="empty">
     2288         <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.40"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>.
     2289         </li>
     2290      </ul>
     2291      <h3 id="rfc.section.7.2.1"><a href="#rfc.section.7.2.1">7.2.1</a>&nbsp;<a id="content.coding.registry" href="#content.coding.registry">Content Coding Registry</a></h3>
     2292      <p id="rfc.section.7.2.1.p.1">The HTTP Content Coding Registry defines the name space for the content coding names.</p>
     2293      <p id="rfc.section.7.2.1.p.2">Registrations <em class="bcp14">MUST</em> include the following fields:
     2294      </p>
     2295      <ul>
     2296         <li>Name</li>
     2297         <li>Description</li>
     2298         <li>Pointer to specification text</li>
     2299      </ul>
     2300      <p id="rfc.section.7.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.41"><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.42"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>).
     2301      </p>
     2302      <p id="rfc.section.7.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.3"><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.
     2303      </p>
     2304      <p id="rfc.section.7.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;.
     2305      </p>
     2306      <h2 id="rfc.section.7.3"><a href="#rfc.section.7.3">7.3</a>&nbsp;<a id="media.types" href="#media.types">Media Types</a></h2>
     2307      <p id="rfc.section.7.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.3" title="Content-Type">Section&nbsp;11.18</a>) and Accept (<a href="#header.accept" id="rfc.xref.header.accept.2" title="Accept">Section&nbsp;11.11</a>) header fields in order to provide open and extensible data typing and type negotiation.
     2308      </p>
     2309      <div id="rfc.figure.u.20"></div><pre class="inline"><span id="rfc.iref.g.27"></span><span id="rfc.iref.g.28"></span><span id="rfc.iref.g.29"></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> )
     2310  <a href="#media.types" class="smpl">type</a>       = <a href="#core.rules" class="smpl">token</a>
     2311  <a href="#media.types" class="smpl">subtype</a>    = <a href="#core.rules" class="smpl">token</a>
     2312</pre><div id="rule.parameter">
     2313         <p id="rfc.section.7.3.p.3">      The type/subtype <em class="bcp14">MAY</em> be followed by parameters in the form of attribute/value pairs.
     2314         </p>
     2315      </div>
     2316      <div id="rfc.figure.u.21"></div><pre class="inline"><span id="rfc.iref.g.30"></span><span id="rfc.iref.g.31"></span><span id="rfc.iref.g.32"></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>
     2317  <a href="#rule.parameter" class="smpl">attribute</a>      = <a href="#core.rules" class="smpl">token</a>
     2318  <a href="#rule.parameter" class="smpl">value</a>          = word
     2319</pre><p id="rfc.section.7.3.p.5">The type, subtype, and parameter attribute names are case-insensitive. Parameter values might or might not be case-sensitive,
     2320         depending on the semantics of the parameter name. The presence or absence of a parameter might be significant to the processing
     2321         of a media-type, depending on its definition within the media type registry.
     2322      </p>
     2323      <p id="rfc.section.7.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.
     2324      </p>
     2325      <p id="rfc.section.7.3.p.7">Note that some older HTTP applications do not recognize media type parameters. When sending data to older HTTP applications,
     2326         implementations <em class="bcp14">SHOULD</em> only use media type parameters when they are required by that type/subtype definition.
     2327      </p>
     2328      <p id="rfc.section.7.3.p.8">Media-type values are registered with the Internet Assigned Number Authority (IANA). The media type registration process is
     2329         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.
     2330      </p>
     2331      <h3 id="rfc.section.7.3.1"><a href="#rfc.section.7.3.1">7.3.1</a>&nbsp;<a id="canonicalization.and.text.defaults" href="#canonicalization.and.text.defaults">Canonicalization and Text Defaults</a></h3>
     2332      <p id="rfc.section.7.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.
     2333      </p>
     2334      <p id="rfc.section.7.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
     2335         allows the transport of text media with plain CR or LF alone representing a line break when it is done consistently for an
     2336         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
     2337         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
     2338         character encodings, HTTP allows the use of whatever octet sequences are defined by that character encoding to represent the
     2339         equivalent of CR and LF for line breaks. This flexibility regarding line breaks applies only to text media in the payload
     2340         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).
     2341      </p>
     2342      <p id="rfc.section.7.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.
     2343      </p>
     2344      <h3 id="rfc.section.7.3.2"><a href="#rfc.section.7.3.2">7.3.2</a>&nbsp;<a id="multipart.types" href="#multipart.types">Multipart Types</a></h3>
     2345      <p id="rfc.section.7.3.2.p.1">MIME provides for a number of "multipart" types — encapsulations of one or more representations within a single message body.
     2346         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.
     2347      </p>
     2348      <p id="rfc.section.7.3.2.p.2">In general, HTTP treats a multipart message body no differently than any other media type: strictly as payload. HTTP does
     2349         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
     2350         each body-part of a multipart message body do not have any significance to HTTP beyond that defined by their MIME semantics.
     2351      </p>
     2352      <p id="rfc.section.7.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".
     2353      </p>
     2354      <div class="note" id="rfc.section.7.3.2.p.4">
     2355         <p> <b>Note:</b> The "multipart/form-data" type has been specifically defined for carrying form data suitable for processing via the POST request
     2356            method, as described in <a href="#RFC2388" id="rfc.xref.RFC2388.1"><cite title="Returning Values from Forms: multipart/form-data">[RFC2388]</cite></a>.
     2357         </p>
     2358      </div>
     2359      <h2 id="rfc.section.7.4"><a href="#rfc.section.7.4">7.4</a>&nbsp;<a id="language.tags" href="#language.tags">Language Tags</a></h2>
     2360      <p id="rfc.section.7.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
     2361         other human beings. Computer languages are explicitly excluded. HTTP uses language tags within the Accept-Language and Content-Language
     2362         fields.
     2363      </p>
     2364      <p id="rfc.section.7.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
     2365         of subtags:
     2366      </p>
     2367      <div id="rfc.figure.u.22"></div><pre class="inline"><span id="rfc.iref.g.33"></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;
     2368</pre><p id="rfc.section.7.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
     2369         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;).
     2370      </p>
     2371      <div id="rfc.figure.u.23"></div>
     2372      <p>Example tags include:</p>  <pre class="text">  en, en-US, es-419, az-Arab, x-pig-latin, man-Nkoo-GN
     2373</pre> <p id="rfc.section.7.4.p.6">See <a href="#RFC5646" id="rfc.xref.RFC5646.3"><cite title="Tags for Identifying Languages">[RFC5646]</cite></a> for further information.
     2374      </p>
     2375      <h1 id="rfc.section.8"><a href="#rfc.section.8">8.</a>&nbsp;<a id="payload" href="#payload">Payload</a></h1>
     2376      <p id="rfc.section.8.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,
     2377         in the form of header fields, and data, in the form of the sequence of octets in the message body after any transfer-coding
     2378         has been decoded.
     2379      </p>
     2380      <div id="rfc.iref.p.3"></div>
     2381      <p id="rfc.section.8.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
     2382         because some messages contain only the associated representation's header fields (e.g., responses to HEAD) or only some part(s)
     2383         of the representation (e.g., the 206 status code).
     2384      </p>
     2385      <h2 id="rfc.section.8.1"><a href="#rfc.section.8.1">8.1</a>&nbsp;<a id="payload.header.fields" href="#payload.header.fields">Payload Header Fields</a></h2>
     2386      <p id="rfc.section.8.1.p.1">HTTP header fields that specifically define the payload, rather than the associated representation, are referred to as "payload
     2387         header fields". The following payload header fields are defined by HTTP/1.1:
     2388      </p>
     2389      <div id="rfc.table.u.4">
     2390         <table class="tt full left" cellpadding="3" cellspacing="0">
     2391            <thead>
     2392               <tr>
     2393                  <th>Header Field Name</th>
     2394                  <th>Defined in...</th>
     2395               </tr>
     2396            </thead>
     2397            <tbody>
     2398               <tr>
     2399                  <td class="left">Content-Length</td>
     2400                  <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.43"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a></td>
     2401               </tr>
     2402               <tr>
     2403                  <td class="left">Content-Range</td>
     2404                  <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.8"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a></td>
     2405               </tr>
     2406            </tbody>
     2407         </table>
     2408      </div>
     2409      <h2 id="rfc.section.8.2"><a href="#rfc.section.8.2">8.2</a>&nbsp;<a id="payload.body" href="#payload.body">Payload Body</a></h2>
     2410      <p id="rfc.section.8.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.44"><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
     2411         safe and proper transfer of the message.
     2412      </p>
     2413      <div id="rfc.iref.r.1"></div>
     2414      <h1 id="rfc.section.9"><a href="#rfc.section.9">9.</a>&nbsp;<a id="representation-TODO" href="#representation-TODO">Representation</a></h1>
     2415      <p id="rfc.section.9.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
     2416         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
     2417         at some point in the future (e.g., in a PUT request).
     2418      </p>
     2419      <p id="rfc.section.9.p.2">Most, but not all, representations transferred via HTTP are intended to be a representation of the target resource (the resource
     2420         identified by the effective request URI). The precise semantics of a representation are determined by the type of message
     2421         (request or response), the request method, the response status code, and the representation metadata. For example, the above
     2422         semantic is true for the representation in any 200 (OK) response to GET and for the representation in any PUT request. A 200
     2423         response to PUT, in contrast, contains either a representation that describes the successful action or a representation of
     2424         the target resource, with the latter indicated by a Content-Location header field with the same value as the effective request
     2425         URI. Likewise, response messages with an error status code usually contain a representation that describes the error and what
     2426         next steps are suggested for resolving it.
     2427      </p>
     2428      <h2 id="rfc.section.9.1"><a href="#rfc.section.9.1">9.1</a>&nbsp;<a id="representation.header.fields" href="#representation.header.fields">Representation Header Fields</a></h2>
     2429      <p id="rfc.section.9.1.p.1">Representation header fields define metadata about the representation data enclosed in the message body or, if no message
     2430         body is present, about the representation that would have been transferred in a 200 response to a simultaneous GET request
     2431         with the same effective request URI.
     2432      </p>
     2433      <p id="rfc.section.9.1.p.2">The following header fields are defined as representation metadata:</p>
     2434      <div id="rfc.table.u.5">
     2435         <table class="tt full left" cellpadding="3" cellspacing="0">
     2436            <thead>
     2437               <tr>
     2438                  <th>Header Field Name</th>
     2439                  <th>Defined in...</th>
     2440               </tr>
     2441            </thead>
     2442            <tbody>
     2443               <tr>
     2444                  <td class="left">Content-Encoding</td>
     2445                  <td class="left"><a href="#header.content-encoding" id="rfc.xref.header.content-encoding.2" title="Content-Encoding">Section&nbsp;11.15</a></td>
     2446               </tr>
     2447               <tr>
     2448                  <td class="left">Content-Language</td>
     2449                  <td class="left"><a href="#header.content-language" id="rfc.xref.header.content-language.1" title="Content-Language">Section&nbsp;11.16</a></td>
     2450               </tr>
     2451               <tr>
     2452                  <td class="left">Content-Location</td>
     2453                  <td class="left"><a href="#header.content-location" id="rfc.xref.header.content-location.2" title="Content-Location">Section&nbsp;11.17</a></td>
     2454               </tr>
     2455               <tr>
     2456                  <td class="left">Content-Type</td>
     2457                  <td class="left"><a href="#header.content-type" id="rfc.xref.header.content-type.4" title="Content-Type">Section&nbsp;11.18</a></td>
     2458               </tr>
     2459               <tr>
     2460                  <td class="left">Expires</td>
     2461                  <td class="left"><a href="p6-cache.html#header.expires" title="Expires">Section 3.3</a> of <a href="#Part6" id="rfc.xref.Part6.18"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a></td>
     2462               </tr>
     2463            </tbody>
     2464         </table>
     2465      </div>
     2466      <p id="rfc.section.9.1.p.3">Additional header fields define metadata about the selected representation, which might differ from the representation included
     2467         in the message for responses to some state-changing methods. The following header fields are defined as selected representation
     2468         metadata:
     2469      </p>
     2470      <div id="rfc.table.u.6">
     2471         <table class="tt full left" cellpadding="3" cellspacing="0">
     2472            <thead>
     2473               <tr>
     2474                  <th>Header Field Name</th>
     2475                  <th>Defined in...</th>
     2476               </tr>
     2477            </thead>
     2478            <tbody>
     2479               <tr>
     2480                  <td class="left">ETag</td>
     2481                  <td class="left"><a href="p4-conditional.html#header.etag" title="ETag">Section 2.3</a> of <a href="#Part4" id="rfc.xref.Part4.11"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a></td>
     2482               </tr>
     2483               <tr>
     2484                  <td class="left">Last-Modified</td>
     2485                  <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.12"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a></td>
     2486               </tr>
     2487            </tbody>
     2488         </table>
     2489      </div>
     2490      <h2 id="rfc.section.9.2"><a href="#rfc.section.9.2">9.2</a>&nbsp;<a id="representation.data" href="#representation.data">Representation Data</a></h2>
     2491      <p id="rfc.section.9.2.p.1">The representation body associated with an HTTP message is either provided as the payload body of the message or referred
     2492         to by the message semantics and the effective request URI. The representation data is in a format and encoding defined by
     2493         the representation metadata header fields.
     2494      </p>
     2495      <p id="rfc.section.9.2.p.2">The data type of the representation data is determined via the header fields Content-Type and Content-Encoding. These define
     2496         a two-layer, ordered encoding model:
     2497      </p>
     2498      <div id="rfc.figure.u.24"></div><pre class="text">  representation-data := Content-Encoding( Content-Type( bits ) )
     2499</pre><p id="rfc.section.9.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
     2500         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
     2501         to the sender. If the Content-Type header field is not present, it indicates that the sender does not know the media type
     2502         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.
     2503      </p>
     2504      <p id="rfc.section.9.2.p.5">In practice, resource owners do not always properly configure their origin server to provide the correct Content-Type for
     2505         a given representation, with the result that some clients will examine a response body's content and override the specified
     2506         type. Clients that do so risk drawing incorrect conclusions, which might expose additional security risks (e.g., "privilege
     2507         escalation"). Furthermore, it is impossible to determine the sender's intent by examining the data format: many data formats
     2508         match multiple media types that differ only in processing semantics. Implementers are encouraged to provide a means of disabling
     2509         such "content sniffing" when it is used.
     2510      </p>
     2511      <p id="rfc.section.9.2.p.6">Content-Encoding is used to indicate any additional content codings applied to the data, usually for the purpose of data compression,
     2512         that are a property of the representation. If Content-Encoding is not present, then there is no additional encoding beyond
     2513         that defined by the Content-Type.
     2514      </p>
     2515      <h1 id="rfc.section.10"><a href="#rfc.section.10">10.</a>&nbsp;<a id="content.negotiation" href="#content.negotiation">Content Negotiation</a></h1>
     2516      <p id="rfc.section.10.p.1">HTTP responses include a representation which contains information for interpretation, whether by a human user or for further
     2517         processing. Often, the server has different ways of representing the same information; for example, in different formats,
     2518         languages, or using different character encodings.
     2519      </p>
     2520      <p id="rfc.section.10.p.2">HTTP clients and their users might have different or variable capabilities, characteristics or preferences which would influence
     2521         which representation, among those available from the server, would be best for the server to deliver. For this reason, HTTP
     2522         provides mechanisms for "content negotiation" — a process of allowing selection of a representation of a given resource, when
     2523         more than one is available.
     2524      </p>
     2525      <p id="rfc.section.10.p.3">This specification defines two patterns of content negotiation; "server-driven", where the server selects the representation
     2526         based upon the client's stated preferences, and "agent-driven" negotiation, where the server provides a list of representations
     2527         for the client to choose from, based upon their metadata. In addition, there are other patterns: some applications use an
     2528         "active content" pattern, where the server returns active content which runs on the client and, based on client available
     2529         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.
     2530      </p>
     2531      <p id="rfc.section.10.p.4">These patterns are all widely used, and have trade-offs in applicability and practicality. In particular, when the number
     2532         of preferences or capabilities to be expressed by a client are large (such as when many different formats are supported by
     2533         a user-agent), server-driven negotiation becomes unwieldy, and might not be appropriate. Conversely, when the number of representations
     2534         to choose from is very large, agent-driven negotiation might not be appropriate.
     2535      </p>
     2536      <p id="rfc.section.10.p.5">Note that in all cases, the supplier of representations has the responsibility for determining which representations might
     2537         be considered to be the "same information".
     2538      </p>
     2539      <h2 id="rfc.section.10.1"><a href="#rfc.section.10.1">10.1</a>&nbsp;<a id="server-driven.negotiation" href="#server-driven.negotiation">Server-driven Negotiation</a></h2>
     2540      <p id="rfc.section.10.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
     2541         negotiation. Selection is based on the available representations of the response (the dimensions over which it can vary; e.g.,
     2542         language, content-coding, etc.) and the contents of particular header fields in the request message or on other information
     2543         pertaining to the request (such as the network address of the client).
     2544      </p>
     2545      <p id="rfc.section.10.1.p.2">Server-driven negotiation is advantageous when the algorithm for selecting from among the available representations is difficult
     2546         to describe to the user agent, or when the server desires to send its "best guess" to the client along with the first response
     2547         (hoping to avoid the round-trip delay of a subsequent request if the "best guess" is good enough for the user). In order to
     2548         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.
     2549      </p>
     2550      <p id="rfc.section.10.1.p.3">Server-driven negotiation has disadvantages: </p>
     2551      <ol>
     2552         <li>It is impossible for the server to accurately determine what might be "best" for any given user, since that would require
     2553            complete knowledge of both the capabilities of the user agent and the intended use for the response (e.g., does the user want
     2554            to view it on screen or print it on paper?).
     2555         </li>
     2556         <li>Having the user agent describe its capabilities in every request can be both very inefficient (given that only a small percentage
     2557            of responses have multiple representations) and a potential violation of the user's privacy.
     2558         </li>
     2559         <li>It complicates the implementation of an origin server and the algorithms for generating responses to a request.</li>
     2560         <li>It might limit a public cache's ability to use the same response for multiple user's requests.</li>
     2561      </ol>
     2562      <p id="rfc.section.10.1.p.4">Server-driven negotiation allows the user agent to specify its preferences, but it cannot expect responses to always honor
     2563         them. For example, the origin server might not implement server-driven negotiation, or it might decide that sending a response
     2564         that doesn't conform to them is better than sending a 406 (Not Acceptable) response.
     2565      </p>
     2566      <p id="rfc.section.10.1.p.5">Many of the mechanisms for expressing preferences use quality values to declare relative preference. See qvalue; for more
     2567         information.
     2568      </p>
     2569      <p id="rfc.section.10.1.p.6">HTTP/1.1 includes the following header fields for enabling server-driven negotiation through description of user agent capabilities
     2570         and user preferences: Accept (<a href="#header.accept" id="rfc.xref.header.accept.3" title="Accept">Section&nbsp;11.11</a>), Accept-Charset (<a href="#header.accept-charset" id="rfc.xref.header.accept-charset.2" title="Accept-Charset">Section&nbsp;11.12</a>), Accept-Encoding (<a href="#header.accept-encoding" id="rfc.xref.header.accept-encoding.3" title="Accept-Encoding">Section&nbsp;11.13</a>), Accept-Language (<a href="#header.accept-language" id="rfc.xref.header.accept-language.2" title="Accept-Language">Section&nbsp;11.14</a>), and User-Agent (<a href="#header.user-agent" id="rfc.xref.header.user-agent.2" title="User-Agent">Section&nbsp;11.10</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
     2571         within extension header fields not defined by this specification.
     2572      </p>
     2573      <div class="note" id="rfc.section.10.1.p.7">
     2574         <p> <b>Note:</b> In practice, User-Agent based negotiation is fragile, because new clients might not be recognized.
     2575         </p>
     2576      </div>
     2577      <p id="rfc.section.10.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.19"><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.
     2578      </p>
     2579      <h2 id="rfc.section.10.2"><a href="#rfc.section.10.2">10.2</a>&nbsp;<a id="agent-driven.negotiation" href="#agent-driven.negotiation">Agent-driven Negotiation</a></h2>
     2580      <p id="rfc.section.10.2.p.1">With agent-driven negotiation, selection of the best representation for a response is performed by the user agent after receiving
     2581         an initial response from the origin server. Selection is based on a list of the available representations of the response
     2582         included within the header fields or body of the initial response, with each representation identified by its own URI. Selection
     2583         from among the representations can be performed automatically (if the user agent is capable of doing so) or manually by the
     2584         user selecting from a generated (possibly hypertext) menu.
     2585      </p>
     2586      <p id="rfc.section.10.2.p.2">Agent-driven negotiation is advantageous when the response would vary over commonly-used dimensions (such as type, language,
     2587         or encoding), when the origin server is unable to determine a user agent's capabilities from examining the request, and generally
     2588         when public caches are used to distribute server load and reduce network usage.
     2589      </p>
     2590      <p id="rfc.section.10.2.p.3">Agent-driven negotiation suffers from the disadvantage of needing a second request to obtain the best alternate representation.
     2591         This second request is only efficient when caching is used. In addition, this specification does not define any mechanism
     2592         for supporting automatic selection, though it also does not prevent any such mechanism from being developed as an extension
     2593         and used within HTTP/1.1.
     2594      </p>
     2595      <p id="rfc.section.10.2.p.4">This specification defines the 300 (Multiple Choices) and 406 (Not Acceptable) status codes for enabling agent-driven negotiation
     2596         when the server is unwilling or unable to provide a varying response using server-driven negotiation.
     2597      </p>
     2598      <h1 id="rfc.section.11"><a href="#rfc.section.11">11.</a>&nbsp;<a id="header.field.definitions" href="#header.field.definitions">Header Field Definitions</a></h1>
     2599      <p id="rfc.section.11.p.1">This section defines the syntax and semantics of HTTP/1.1 header fields related to request and response semantics, and to
     2600         the payload of messages.
     2601      </p>
    21492602      <div id="rfc.iref.a.1"></div>
    21502603      <div id="rfc.iref.h.2"></div>
    2151       <h2 id="rfc.section.7.1"><a href="#rfc.section.7.1">7.1</a>&nbsp;<a id="header.allow" href="#header.allow">Allow</a></h2>
    2152       <p id="rfc.section.7.1.p.1">The "Allow" header field lists the set of methods advertised as supported by the target resource. The purpose of this field
     2604      <h2 id="rfc.section.11.1"><a href="#rfc.section.11.1">11.1</a>&nbsp;<a id="header.allow" href="#header.allow">Allow</a></h2>
     2605      <p id="rfc.section.11.1.p.1">The "Allow" header field lists the set of methods advertised as supported by the target resource. The purpose of this field
    21532606         is strictly to inform the recipient of valid request methods associated with the resource.
    21542607      </p>
    2155       <div id="rfc.figure.u.18"></div><pre class="inline"><span id="rfc.iref.g.24"></span>  <a href="#header.allow" class="smpl">Allow</a> = #<a href="#methods" class="smpl">method</a>
    2156 </pre><p id="rfc.section.7.1.p.3">Example of use:</p>
    2157       <div id="rfc.figure.u.19"></div><pre class="text">  Allow: GET, HEAD, PUT
    2158 </pre><p id="rfc.section.7.1.p.5">The actual set of allowed methods is defined by the origin server at the time of each request.</p>
    2159       <p id="rfc.section.7.1.p.6">A proxy <em class="bcp14">MUST NOT</em> modify the Allow header field — it does not need to understand all the methods specified in order to handle them according
     2608      <div id="rfc.figure.u.25"></div><pre class="inline"><span id="rfc.iref.g.34"></span>  <a href="#header.allow" class="smpl">Allow</a> = #<a href="#methods" class="smpl">method</a>
     2609</pre><p id="rfc.section.11.1.p.3">Example of use:</p>
     2610      <div id="rfc.figure.u.26"></div><pre class="text">  Allow: GET, HEAD, PUT
     2611</pre><p id="rfc.section.11.1.p.5">The actual set of allowed methods is defined by the origin server at the time of each request.</p>
     2612      <p id="rfc.section.11.1.p.6">A proxy <em class="bcp14">MUST NOT</em> modify the Allow header field — it does not need to understand all the methods specified in order to handle them according
    21602613         to the generic message handling rules.
    21612614      </p>
    2162       <div id="rfc.iref.d.2"></div>
     2615      <div id="rfc.iref.d.3"></div>
    21632616      <div id="rfc.iref.h.3"></div>
    2164       <h2 id="rfc.section.7.2"><a href="#rfc.section.7.2">7.2</a>&nbsp;<a id="header.date" href="#header.date">Date</a></h2>
    2165       <p id="rfc.section.7.2.p.1">The "Date" header field represents the date and time at which the message was originated, having the same semantics as the
     2617      <h2 id="rfc.section.11.2"><a href="#rfc.section.11.2">11.2</a>&nbsp;<a id="header.date" href="#header.date">Date</a></h2>
     2618      <p id="rfc.section.11.2.p.1">The "Date" header field represents the date and time at which the message was originated, having the same semantics as the
    21662619         Origination Date Field (orig-date) defined in <a href="http://tools.ietf.org/html/rfc5322#section-3.6.1">Section 3.6.1</a> of <a href="#RFC5322" id="rfc.xref.RFC5322.2"><cite title="Internet Message Format">[RFC5322]</cite></a>. The field value is an HTTP-date, as defined in <a href="#http.date" title="Date/Time Formats">Section&nbsp;6.1</a>; it <em class="bcp14">MUST</em> be sent in rfc1123-date format.
    21672620      </p>
    2168       <div id="rfc.figure.u.20"></div><pre class="inline"><span id="rfc.iref.g.25"></span>  <a href="#header.date" class="smpl">Date</a> = <a href="#http.date" class="smpl">HTTP-date</a>
    2169 </pre><p id="rfc.section.7.2.p.3">An example is</p>
    2170       <div id="rfc.figure.u.21"></div><pre class="text">  Date: Tue, 15 Nov 1994 08:12:31 GMT
    2171 </pre><p id="rfc.section.7.2.p.5">Origin servers <em class="bcp14">MUST</em> include a Date header field in all responses, except in these cases:
     2621      <div id="rfc.figure.u.27"></div><pre class="inline"><span id="rfc.iref.g.35"></span>  <a href="#header.date" class="smpl">Date</a> = <a href="#http.date" class="smpl">HTTP-date</a>
     2622</pre><p id="rfc.section.11.2.p.3">An example is</p>
     2623      <div id="rfc.figure.u.28"></div><pre class="text">  Date: Tue, 15 Nov 1994 08:12:31 GMT
     2624</pre><p id="rfc.section.11.2.p.5">Origin servers <em class="bcp14">MUST</em> include a Date header field in all responses, except in these cases:
    21722625      </p>
    21732626      <ol>
     
    21802633         </li>
    21812634      </ol>
    2182       <p id="rfc.section.7.2.p.6">A received message that does not have a Date header field <em class="bcp14">MUST</em> be assigned one by the recipient if the message will be cached by that recipient.
    2183       </p>
    2184       <p id="rfc.section.7.2.p.7">Clients can use the Date header field as well; in order to keep request messages small, they are advised not to include it
     2635      <p id="rfc.section.11.2.p.6">A received message that does not have a Date header field <em class="bcp14">MUST</em> be assigned one by the recipient if the message will be cached by that recipient.
     2636      </p>
     2637      <p id="rfc.section.11.2.p.7">Clients can use the Date header field as well; in order to keep request messages small, they are advised not to include it
    21852638         when it doesn't convey any useful information (as is usually the case for requests that do not contain a payload).
    21862639      </p>
    2187       <p id="rfc.section.7.2.p.8">The HTTP-date sent in a Date header field <em class="bcp14">SHOULD NOT</em> represent a date and time subsequent to the generation of the message. It <em class="bcp14">SHOULD</em> represent the best available approximation of the date and time of message generation, unless the implementation has no means
     2640      <p id="rfc.section.11.2.p.8">The HTTP-date sent in a Date header field <em class="bcp14">SHOULD NOT</em> represent a date and time subsequent to the generation of the message. It <em class="bcp14">SHOULD</em> represent the best available approximation of the date and time of message generation, unless the implementation has no means
    21882641         of generating a reasonably accurate date and time. In theory, the date ought to represent the moment just before the payload
    21892642         is generated. In practice, the date can be generated at any time during the message origination without affecting its semantic
     
    21922645      <div id="rfc.iref.e.1"></div>
    21932646      <div id="rfc.iref.h.4"></div>
    2194       <h2 id="rfc.section.7.3"><a href="#rfc.section.7.3">7.3</a>&nbsp;<a id="header.expect" href="#header.expect">Expect</a></h2>
    2195       <p id="rfc.section.7.3.p.1">The "Expect" header field is used to indicate that particular server behaviors are required by the client.</p>
    2196       <div id="rfc.figure.u.22"></div><pre class="inline"><span id="rfc.iref.g.26"></span><span id="rfc.iref.g.27"></span><span id="rfc.iref.g.28"></span><span id="rfc.iref.g.29"></span><span id="rfc.iref.g.30"></span>  <a href="#header.expect" class="smpl">Expect</a>       = 1#<a href="#header.expect" class="smpl">expectation</a>
     2647      <h2 id="rfc.section.11.3"><a href="#rfc.section.11.3">11.3</a>&nbsp;<a id="header.expect" href="#header.expect">Expect</a></h2>
     2648      <p id="rfc.section.11.3.p.1">The "Expect" header field is used to indicate that particular server behaviors are required by the client.</p>
     2649      <div id="rfc.figure.u.29"></div><pre class="inline"><span id="rfc.iref.g.36"></span><span id="rfc.iref.g.37"></span><span id="rfc.iref.g.38"></span><span id="rfc.iref.g.39"></span><span id="rfc.iref.g.40"></span>  <a href="#header.expect" class="smpl">Expect</a>       = 1#<a href="#header.expect" class="smpl">expectation</a>
    21972650 
    21982651  <a href="#header.expect" class="smpl">expectation</a>  = <a href="#header.expect" class="smpl">expect-name</a> [ <a href="#core.rules" class="smpl">BWS</a> "=" <a href="#core.rules" class="smpl">BWS</a> <a href="#header.expect" class="smpl">expect-value</a> ]
     
    22022655  <a href="#header.expect" class="smpl">expect-name</a>  = <a href="#core.rules" class="smpl">token</a>
    22032656  <a href="#header.expect" class="smpl">expect-value</a> = <a href="#core.rules" class="smpl">token</a> / <a href="#core.rules" class="smpl">quoted-string</a>
    2204 </pre><p id="rfc.section.7.3.p.3">If all received Expect header field(s) are syntactically valid but contain an expectation that the recipient does not understand
     2657</pre><p id="rfc.section.11.3.p.3">If all received Expect header field(s) are syntactically valid but contain an expectation that the recipient does not understand
    22052658         or cannot comply with, the recipient <em class="bcp14">MUST</em> respond with a 417 (Expectation Failed) status code. A recipient of a syntactically invalid Expectation header field <em class="bcp14">MUST</em> respond with a 4xx status code other than 417.
    22062659      </p>
    2207       <p id="rfc.section.7.3.p.4">The only expectation defined by this specification is:</p>
    2208       <p id="rfc.section.7.3.p.5"><span id="rfc.iref.89"></span><span id="rfc.iref.e.2"></span> 100-continue
     2660      <p id="rfc.section.11.3.p.4">The only expectation defined by this specification is:</p>
     2661      <p id="rfc.section.11.3.p.5"><span id="rfc.iref.108"></span><span id="rfc.iref.e.2"></span> 100-continue
    22092662      </p>
    22102663      <ul class="empty">
    2211          <li>The "100-continue" expectation is defined <a href="p1-messaging.html#use.of.the.100.status" title="Use of the 100 (Continue) Status">Section 6.4.3</a> of <a href="#Part1" id="rfc.xref.Part1.38"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>. It does not support any expect-params.
    2212          </li>
    2213       </ul>
    2214       <p id="rfc.section.7.3.p.6">Comparison is case-insensitive for names (expect-name), and case-sensitive for values (expect-value).</p>
    2215       <p id="rfc.section.7.3.p.7">The Expect mechanism is hop-by-hop: the above requirements apply to any server, including proxies. However, the Expect header
     2664         <li>The "100-continue" expectation is defined <a href="p1-messaging.html#use.of.the.100.status" title="Use of the 100 (Continue) Status">Section 6.4.3</a> of <a href="#Part1" id="rfc.xref.Part1.45"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>. It does not support any expect-params.
     2665         </li>
     2666      </ul>
     2667      <p id="rfc.section.11.3.p.6">Comparison is case-insensitive for names (expect-name), and case-sensitive for values (expect-value).</p>
     2668      <p id="rfc.section.11.3.p.7">The Expect mechanism is hop-by-hop: the above requirements apply to any server, including proxies. However, the Expect header
    22162669         field itself is end-to-end; it <em class="bcp14">MUST</em> be forwarded if the request is forwarded.
    22172670      </p>
    2218       <p id="rfc.section.7.3.p.8">Many older HTTP/1.0 and HTTP/1.1 applications do not understand the Expect header field.</p>
     2671      <p id="rfc.section.11.3.p.8">Many older HTTP/1.0 and HTTP/1.1 applications do not understand the Expect header field.</p>
    22192672      <div id="rfc.iref.f.1"></div>
    22202673      <div id="rfc.iref.h.5"></div>
    2221       <h2 id="rfc.section.7.4"><a href="#rfc.section.7.4">7.4</a>&nbsp;<a id="header.from" href="#header.from">From</a></h2>
    2222       <p id="rfc.section.7.4.p.1">The "From" header field, if given, <em class="bcp14">SHOULD</em> contain an Internet e-mail address for the human user who controls the requesting user agent. The address <em class="bcp14">SHOULD</em> be machine-usable, as defined by "mailbox" in <a href="http://tools.ietf.org/html/rfc5322#section-3.4">Section 3.4</a> of <a href="#RFC5322" id="rfc.xref.RFC5322.3"><cite title="Internet Message Format">[RFC5322]</cite></a>:
    2223       </p>
    2224       <div id="rfc.figure.u.23"></div><pre class="inline"><span id="rfc.iref.g.31"></span>  <a href="#header.from" class="smpl">From</a>    = <a href="#header.from" class="smpl">mailbox</a>
     2674      <h2 id="rfc.section.11.4"><a href="#rfc.section.11.4">11.4</a>&nbsp;<a id="header.from" href="#header.from">From</a></h2>
     2675      <p id="rfc.section.11.4.p.1">The "From" header field, if given, <em class="bcp14">SHOULD</em> contain an Internet e-mail address for the human user who controls the requesting user agent. The address <em class="bcp14">SHOULD</em> be machine-usable, as defined by "mailbox" in <a href="http://tools.ietf.org/html/rfc5322#section-3.4">Section 3.4</a> of <a href="#RFC5322" id="rfc.xref.RFC5322.3"><cite title="Internet Message Format">[RFC5322]</cite></a>:
     2676      </p>
     2677      <div id="rfc.figure.u.30"></div><pre class="inline"><span id="rfc.iref.g.41"></span>  <a href="#header.from" class="smpl">From</a>    = <a href="#header.from" class="smpl">mailbox</a>
    22252678 
    22262679  <a href="#header.from" class="smpl">mailbox</a> = &lt;mailbox, defined in <a href="#RFC5322" id="rfc.xref.RFC5322.4"><cite title="Internet Message Format">[RFC5322]</cite></a>, <a href="http://tools.ietf.org/html/rfc5322#section-3.4">Section 3.4</a>&gt;
    2227 </pre><p id="rfc.section.7.4.p.3">An example is:</p>
    2228       <div id="rfc.figure.u.24"></div><pre class="text">  From: webmaster@example.org
    2229 </pre><p id="rfc.section.7.4.p.5">This header field <em class="bcp14">MAY</em> be used for logging purposes and as a means for identifying the source of invalid or unwanted requests. It <em class="bcp14">SHOULD NOT</em> be used as an insecure form of access protection. The interpretation of this field is that the request is being performed
     2680</pre><p id="rfc.section.11.4.p.3">An example is:</p>
     2681      <div id="rfc.figure.u.31"></div><pre class="text">  From: webmaster@example.org
     2682</pre><p id="rfc.section.11.4.p.5">This header field <em class="bcp14">MAY</em> be used for logging purposes and as a means for identifying the source of invalid or unwanted requests. It <em class="bcp14">SHOULD NOT</em> be used as an insecure form of access protection. The interpretation of this field is that the request is being performed
    22302683         on behalf of the person given, who accepts responsibility for the method performed. In particular, robot agents <em class="bcp14">SHOULD</em> include this header field so that the person responsible for running the robot can be contacted if problems occur on the receiving
    22312684         end.
    22322685      </p>
    2233       <p id="rfc.section.7.4.p.6">The Internet e-mail address in this field <em class="bcp14">MAY</em> be separate from the Internet host which issued the request. For example, when a request is passed through a proxy the original
     2686      <p id="rfc.section.11.4.p.6">The Internet e-mail address in this field <em class="bcp14">MAY</em> be separate from the Internet host which issued the request. For example, when a request is passed through a proxy the original
    22342687         issuer's address <em class="bcp14">SHOULD</em> be used.
    22352688      </p>
    2236       <p id="rfc.section.7.4.p.7">The client <em class="bcp14">SHOULD NOT</em> send the From header field without the user's approval, as it might conflict with the user's privacy interests or their site's
     2689      <p id="rfc.section.11.4.p.7">The client <em class="bcp14">SHOULD NOT</em> send the From header field without the user's approval, as it might conflict with the user's privacy interests or their site's
    22372690         security policy. It is strongly recommended that the user be able to disable, enable, and modify the value of this field at
    22382691         any time prior to a request.
     
    22402693      <div id="rfc.iref.l.1"></div>
    22412694      <div id="rfc.iref.h.6"></div>
    2242       <h2 id="rfc.section.7.5"><a href="#rfc.section.7.5">7.5</a>&nbsp;<a id="header.location" href="#header.location">Location</a></h2>
    2243       <p id="rfc.section.7.5.p.1">The "Location" header field <em class="bcp14">MAY</em> be sent in responses to refer to a specific resource in accordance with the semantics of the status code.
    2244       </p>
    2245       <div id="rfc.figure.u.25"></div><pre class="inline"><span id="rfc.iref.g.32"></span>  <a href="#header.location" class="smpl">Location</a> = <a href="#abnf.dependencies" class="smpl">URI-reference</a>
    2246 </pre><p id="rfc.section.7.5.p.3">For 201 (Created) responses, the Location is the URI of the new resource which was created by the request. For 3xx responses,
     2695      <h2 id="rfc.section.11.5"><a href="#rfc.section.11.5">11.5</a>&nbsp;<a id="header.location" href="#header.location">Location</a></h2>
     2696      <p id="rfc.section.11.5.p.1">The "Location" header field <em class="bcp14">MAY</em> be sent in responses to refer to a specific resource in accordance with the semantics of the status code.
     2697      </p>
     2698      <div id="rfc.figure.u.32"></div><pre class="inline"><span id="rfc.iref.g.42"></span>  <a href="#header.location" class="smpl">Location</a> = <a href="#abnf.dependencies" class="smpl">URI-reference</a>
     2699</pre><p id="rfc.section.11.5.p.3">For 201 (Created) responses, the Location is the URI of the new resource which was created by the request. For 3xx responses,
    22472700         the location <em class="bcp14">SHOULD</em> indicate the server's preferred URI for automatic redirection to the resource.
    22482701      </p>
    2249       <p id="rfc.section.7.5.p.4">The field value consists of a single URI-reference. When it has the form of a relative reference (<a href="#RFC3986" id="rfc.xref.RFC3986.1"><cite title="Uniform Resource Identifier (URI): Generic Syntax">[RFC3986]</cite></a>, <a href="http://tools.ietf.org/html/rfc3986#section-4.2">Section 4.2</a>), the final value is computed by resolving it against the effective request URI (<a href="#RFC3986" id="rfc.xref.RFC3986.2"><cite title="Uniform Resource Identifier (URI): Generic Syntax">[RFC3986]</cite></a>, <a href="http://tools.ietf.org/html/rfc3986#section-5">Section 5</a>). If the original URI, as navigated to by the user agent, did contain a fragment identifier, and the final value does not,
     2702      <p id="rfc.section.11.5.p.4">The field value consists of a single URI-reference. When it has the form of a relative reference (<a href="#RFC3986" id="rfc.xref.RFC3986.1"><cite title="Uniform Resource Identifier (URI): Generic Syntax">[RFC3986]</cite></a>, <a href="http://tools.ietf.org/html/rfc3986#section-4.2">Section 4.2</a>), the final value is computed by resolving it against the effective request URI (<a href="#RFC3986" id="rfc.xref.RFC3986.2"><cite title="Uniform Resource Identifier (URI): Generic Syntax">[RFC3986]</cite></a>, <a href="http://tools.ietf.org/html/rfc3986#section-5">Section 5</a>). If the original URI, as navigated to by the user agent, did contain a fragment identifier, and the final value does not,
    22502703         then the original URI's fragment identifier is added to the final value.
    22512704      </p>
    2252       <div id="rfc.figure.u.26"></div>
     2705      <div id="rfc.figure.u.33"></div>
    22532706      <p>For example, the original URI "http://www.example.org/~tim", combined with a field value given as:</p>  <pre class="text">  Location: /pub/WWW/People.html#tim
    22542707</pre>  <p>would result in a final value of "http://www.example.org/pub/WWW/People.html#tim"</p>
    2255       <div id="rfc.figure.u.27"></div>
     2708      <div id="rfc.figure.u.34"></div>
    22562709      <p>An original URI "http://www.example.org/index.html#larry", combined with a field value given as:</p>  <pre class="text">  Location: http://www.example.net/index.html
    22572710</pre>  <p>would result in a final value of "http://www.example.net/index.html#larry", preserving the original fragment identifier.</p>
    2258       <div class="note" id="rfc.section.7.5.p.7">
     2711      <div class="note" id="rfc.section.11.5.p.7">
    22592712         <p> <b>Note:</b> Some recipients attempt to recover from Location fields that are not valid URI references. This specification does not mandate
    2260             or define such processing, but does allow it (see <a href="#intro.conformance.and.error.handling" title="Conformance and Error Handling">Section&nbsp;1.1</a>).
     2713            or define such processing, but does allow it (see <a href="#intro.conformance.and.error.handling" title="Conformance and Error Handling">Section&nbsp;1.2</a>).
    22612714         </p>
    22622715      </div>
    2263       <p id="rfc.section.7.5.p.8">There are circumstances in which a fragment identifier in a Location URI would not be appropriate. For instance, when it appears
     2716      <p id="rfc.section.11.5.p.8">There are circumstances in which a fragment identifier in a Location URI would not be appropriate. For instance, when it appears
    22642717         in a 201 Created response, where the Location header field specifies the URI for the entire created resource.
    22652718      </p>
    2266       <div class="note" id="rfc.section.7.5.p.9">
    2267          <p> <b>Note:</b> The Content-Location header field (<a href="p3-payload.html#header.content-location" title="Content-Location">Section 6.7</a> of <a href="#Part3" id="rfc.xref.Part3.13"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>) differs from Location in that the Content-Location identifies the most specific resource corresponding to the enclosed representation.
     2719      <div class="note" id="rfc.section.11.5.p.9">
     2720         <p> <b>Note:</b> The Content-Location header field (<a href="#header.content-location" id="rfc.xref.header.content-location.3" title="Content-Location">Section&nbsp;11.17</a>) differs from Location in that the Content-Location identifies the most specific resource corresponding to the enclosed representation.
    22682721            It is therefore possible for a response to contain header fields for both Location and Content-Location.
    22692722         </p>
     
    22712724      <div id="rfc.iref.m.9"></div>
    22722725      <div id="rfc.iref.h.7"></div>
    2273       <h2 id="rfc.section.7.6"><a href="#rfc.section.7.6">7.6</a>&nbsp;<a id="header.max-forwards" href="#header.max-forwards">Max-Forwards</a></h2>
    2274       <p id="rfc.section.7.6.p.1">The "Max-Forwards" header field provides a mechanism with the TRACE (<a href="#TRACE" id="rfc.xref.TRACE.1" title="TRACE">Section&nbsp;2.3.7</a>) and OPTIONS (<a href="#OPTIONS" id="rfc.xref.OPTIONS.1" title="OPTIONS">Section&nbsp;2.3.1</a>) methods to limit the number of times that the request is forwarded by proxies. This can be useful when the client is attempting
     2726      <h2 id="rfc.section.11.6"><a href="#rfc.section.11.6">11.6</a>&nbsp;<a id="header.max-forwards" href="#header.max-forwards">Max-Forwards</a></h2>
     2727      <p id="rfc.section.11.6.p.1">The "Max-Forwards" header field provides a mechanism with the TRACE (<a href="#TRACE" id="rfc.xref.TRACE.1" title="TRACE">Section&nbsp;2.3.7</a>) and OPTIONS (<a href="#OPTIONS" id="rfc.xref.OPTIONS.1" title="OPTIONS">Section&nbsp;2.3.1</a>) methods to limit the number of times that the request is forwarded by proxies. This can be useful when the client is attempting
    22752728         to trace a request which appears to be failing or looping mid-chain.
    22762729      </p>
    2277       <div id="rfc.figure.u.28"></div><pre class="inline"><span id="rfc.iref.g.33"></span>  <a href="#header.max-forwards" class="smpl">Max-Forwards</a> = 1*<a href="#notation" class="smpl">DIGIT</a>
    2278 </pre><p id="rfc.section.7.6.p.3">The Max-Forwards value is a decimal integer indicating the remaining number of times this request message can be forwarded.</p>
    2279       <p id="rfc.section.7.6.p.4">Each recipient of a TRACE or OPTIONS request containing a Max-Forwards header field <em class="bcp14">MUST</em> check and update its value prior to forwarding the request. If the received value is zero (0), the recipient <em class="bcp14">MUST NOT</em> forward the request; instead, it <em class="bcp14">MUST</em> respond as the final recipient. If the received Max-Forwards value is greater than zero, then the forwarded message <em class="bcp14">MUST</em> contain an updated Max-Forwards field with a value decremented by one (1).
    2280       </p>
    2281       <p id="rfc.section.7.6.p.5">The Max-Forwards header field <em class="bcp14">MAY</em> be ignored for all other request methods.
    2282       </p>
    2283       <div id="rfc.iref.r.1"></div>
     2730      <div id="rfc.figure.u.35"></div><pre class="inline"><span id="rfc.iref.g.43"></span>  <a href="#header.max-forwards" class="smpl">Max-Forwards</a> = 1*<a href="#notation" class="smpl">DIGIT</a>
     2731</pre><p id="rfc.section.11.6.p.3">The Max-Forwards value is a decimal integer indicating the remaining number of times this request message can be forwarded.</p>
     2732      <p id="rfc.section.11.6.p.4">Each recipient of a TRACE or OPTIONS request containing a Max-Forwards header field <em class="bcp14">MUST</em> check and update its value prior to forwarding the request. If the received value is zero (0), the recipient <em class="bcp14">MUST NOT</em> forward the request; instead, it <em class="bcp14">MUST</em> respond as the final recipient. If the received Max-Forwards value is greater than zero, then the forwarded message <em class="bcp14">MUST</em> contain an updated Max-Forwards field with a value decremented by one (1).
     2733      </p>
     2734      <p id="rfc.section.11.6.p.5">The Max-Forwards header field <em class="bcp14">MAY</em> be ignored for all other request methods.
     2735      </p>
     2736      <div id="rfc.iref.r.2"></div>
    22842737      <div id="rfc.iref.h.8"></div>
    2285       <h2 id="rfc.section.7.7"><a href="#rfc.section.7.7">7.7</a>&nbsp;<a id="header.referer" href="#header.referer">Referer</a></h2>
    2286       <p id="rfc.section.7.7.p.1">The "Referer" [sic] header field allows the client to specify the URI of the resource from which the target URI was obtained
     2738      <h2 id="rfc.section.11.7"><a href="#rfc.section.11.7">11.7</a>&nbsp;<a id="header.referer" href="#header.referer">Referer</a></h2>
     2739      <p id="rfc.section.11.7.p.1">The "Referer" [sic] header field allows the client to specify the URI of the resource from which the target URI was obtained
    22872740         (the "referrer", although the header field is misspelled.).
    22882741      </p>
    2289       <p id="rfc.section.7.7.p.2">The Referer header field allows servers to generate lists of back-links to resources for interest, logging, optimized caching,
     2742      <p id="rfc.section.11.7.p.2">The Referer header field allows servers to generate lists of back-links to resources for interest, logging, optimized caching,
    22902743         etc. It also allows obsolete or mistyped links to be traced for maintenance. Some servers use Referer as a means of controlling
    22912744         where they allow links from (so-called "deep linking"), but legitimate requests do not always contain a Referer header field.
    22922745      </p>
    2293       <p id="rfc.section.7.7.p.3">If the target URI was obtained from a source that does not have its own URI (e.g., input from the user keyboard), the Referer
     2746      <p id="rfc.section.11.7.p.3">If the target URI was obtained from a source that does not have its own URI (e.g., input from the user keyboard), the Referer
    22942747         field <em class="bcp14">MUST</em> either be sent with the value "about:blank", or not be sent at all. Note that this requirement does not apply to sources with
    22952748         non-HTTP URIs (e.g., FTP).
    22962749      </p>
    2297       <div id="rfc.figure.u.29"></div><pre class="inline"><span id="rfc.iref.g.34"></span>  <a href="#header.referer" class="smpl">Referer</a> = <a href="#abnf.dependencies" class="smpl">absolute-URI</a> / <a href="#abnf.dependencies" class="smpl">partial-URI</a>
    2298 </pre><p id="rfc.section.7.7.p.5">Example:</p>
    2299       <div id="rfc.figure.u.30"></div><pre class="text">  Referer: http://www.example.org/hypertext/Overview.html
    2300 </pre><p id="rfc.section.7.7.p.7">If the field value is a relative URI, it <em class="bcp14">SHOULD</em> be interpreted relative to the effective request URI. The URI <em class="bcp14">MUST NOT</em> include a fragment. See <a href="#encoding.sensitive.information.in.uris" title="Encoding Sensitive Information in URIs">Section&nbsp;9.2</a> for security considerations.
    2301       </p>
    2302       <div id="rfc.iref.r.2"></div>
     2750      <div id="rfc.figure.u.36"></div><pre class="inline"><span id="rfc.iref.g.44"></span>  <a href="#header.referer" class="smpl">Referer</a> = <a href="#abnf.dependencies" class="smpl">absolute-URI</a> / <a href="#abnf.dependencies" class="smpl">partial-URI</a>
     2751</pre><p id="rfc.section.11.7.p.5">Example:</p>
     2752      <div id="rfc.figure.u.37"></div><pre class="text">  Referer: http://www.example.org/hypertext/Overview.html
     2753</pre><p id="rfc.section.11.7.p.7">If the field value is a relative URI, it <em class="bcp14">SHOULD</em> be interpreted relative to the effective request URI. The URI <em class="bcp14">MUST NOT</em> include a fragment. See <a href="#encoding.sensitive.information.in.uris" title="Encoding Sensitive Information in URIs">Section&nbsp;13.2</a> for security considerations.
     2754      </p>
     2755      <div id="rfc.iref.r.3"></div>
    23032756      <div id="rfc.iref.h.9"></div>
    2304       <h2 id="rfc.section.7.8"><a href="#rfc.section.7.8">7.8</a>&nbsp;<a id="header.retry-after" href="#header.retry-after">Retry-After</a></h2>
    2305       <p id="rfc.section.7.8.p.1">The header "Retry-After" field can be used with a 503 (Service Unavailable) response to indicate how long the service is expected
     2757      <h2 id="rfc.section.11.8"><a href="#rfc.section.11.8">11.8</a>&nbsp;<a id="header.retry-after" href="#header.retry-after">Retry-After</a></h2>
     2758      <p id="rfc.section.11.8.p.1">The header "Retry-After" field can be used with a 503 (Service Unavailable) response to indicate how long the service is expected
    23062759         to be unavailable to the requesting client. This field <em class="bcp14">MAY</em> also be used with any 3xx (Redirection) response to indicate the minimum time the user-agent is asked to wait before issuing
    23072760         the redirected request.
    23082761      </p>
    2309       <p id="rfc.section.7.8.p.2">The value of this field can be either an HTTP-date or an integer number of seconds (in decimal) after the time of the response.</p>
    2310       <div id="rfc.figure.u.31"></div><pre class="inline"><span id="rfc.iref.g.35"></span>  <a href="#header.retry-after" class="smpl">Retry-After</a> = <a href="#http.date" class="smpl">HTTP-date</a> / <a href="#rule.delta-seconds" class="smpl">delta-seconds</a>
     2762      <p id="rfc.section.11.8.p.2">The value of this field can be either an HTTP-date or an integer number of seconds (in decimal) after the time of the response.</p>
     2763      <div id="rfc.figure.u.38"></div><pre class="inline"><span id="rfc.iref.g.45"></span>  <a href="#header.retry-after" class="smpl">Retry-After</a> = <a href="#http.date" class="smpl">HTTP-date</a> / <a href="#rule.delta-seconds" class="smpl">delta-seconds</a>
    23112764</pre><div id="rule.delta-seconds">
    2312          <p id="rfc.section.7.8.p.4">  Time spans are non-negative decimal integers, representing time in seconds.</p>
     2765         <p id="rfc.section.11.8.p.4">  Time spans are non-negative decimal integers, representing time in seconds.</p>
    23132766      </div>
    2314       <div id="rfc.figure.u.32"></div><pre class="inline"><span id="rfc.iref.g.36"></span>  <a href="#rule.delta-seconds" class="smpl">delta-seconds</a>  = 1*<a href="#notation" class="smpl">DIGIT</a>
    2315 </pre><p id="rfc.section.7.8.p.6">Two examples of its use are</p>
    2316       <div id="rfc.figure.u.33"></div><pre class="text">  Retry-After: Fri, 31 Dec 1999 23:59:59 GMT
     2767      <div id="rfc.figure.u.39"></div><pre class="inline"><span id="rfc.iref.g.46"></span>  <a href="#rule.delta-seconds" class="smpl">delta-seconds</a>  = 1*<a href="#notation" class="smpl">DIGIT</a>
     2768</pre><p id="rfc.section.11.8.p.6">Two examples of its use are</p>
     2769      <div id="rfc.figure.u.40"></div><pre class="text">  Retry-After: Fri, 31 Dec 1999 23:59:59 GMT
    23172770  Retry-After: 120
    2318 </pre><p id="rfc.section.7.8.p.8">In the latter example, the delay is 2 minutes.</p>
    2319       <div id="rfc.iref.s.38"></div>
     2771</pre><p id="rfc.section.11.8.p.8">In the latter example, the delay is 2 minutes.</p>
     2772      <div id="rfc.iref.s.39"></div>
    23202773      <div id="rfc.iref.h.10"></div>
    2321       <h2 id="rfc.section.7.9"><a href="#rfc.section.7.9">7.9</a>&nbsp;<a id="header.server" href="#header.server">Server</a></h2>
    2322       <p id="rfc.section.7.9.p.1">The "Server" header field contains information about the software used by the origin server to handle the request.</p>
    2323       <p id="rfc.section.7.9.p.2">The field can contain multiple product tokens (<a href="#product.tokens" title="Product Tokens">Section&nbsp;6.2</a>) and comments (<a href="p1-messaging.html#header.fields" title="Header Fields">Section 3.2</a> of <a href="#Part1" id="rfc.xref.Part1.39"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) identifying the server and any significant subproducts. The product tokens are listed in order of their significance for
     2774      <h2 id="rfc.section.11.9"><a href="#rfc.section.11.9">11.9</a>&nbsp;<a id="header.server" href="#header.server">Server</a></h2>
     2775      <p id="rfc.section.11.9.p.1">The "Server" header field contains information about the software used by the origin server to handle the request.</p>
     2776      <p id="rfc.section.11.9.p.2">The field can contain multiple product tokens (<a href="#product.tokens" title="Product Tokens">Section&nbsp;6.2</a>) and comments (<a href="p1-messaging.html#header.fields" title="Header Fields">Section 3.2</a> of <a href="#Part1" id="rfc.xref.Part1.46"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) identifying the server and any significant subproducts. The product tokens are listed in order of their significance for
    23242777         identifying the application.
    23252778      </p>
    2326       <div id="rfc.figure.u.34"></div><pre class="inline"><span id="rfc.iref.g.37"></span>  <a href="#header.server" class="smpl">Server</a> = <a href="#product.tokens" class="smpl">product</a> *( <a href="#core.rules" class="smpl">RWS</a> ( <a href="#product.tokens" class="smpl">product</a> / <a href="#abnf.dependencies" class="smpl">comment</a> ) )
    2327 </pre><p id="rfc.section.7.9.p.4">Example:</p>
    2328       <div id="rfc.figure.u.35"></div><pre class="text">  Server: CERN/3.0 libwww/2.17
    2329 </pre><p id="rfc.section.7.9.p.6">If the response is being forwarded through a proxy, the proxy application <em class="bcp14">MUST NOT</em> modify the Server header field. Instead, it <em class="bcp14">MUST</em> include a Via field (as described in <a href="p1-messaging.html#header.via" title="Via">Section 6.2</a> of <a href="#Part1" id="rfc.xref.Part1.40"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>).
    2330       </p>
    2331       <div class="note" id="rfc.section.7.9.p.7">
     2779      <div id="rfc.figure.u.41"></div><pre class="inline"><span id="rfc.iref.g.47"></span>  <a href="#header.server" class="smpl">Server</a> = <a href="#product.tokens" class="smpl">product</a> *( <a href="#core.rules" class="smpl">RWS</a> ( <a href="#product.tokens" class="smpl">product</a> / <a href="#abnf.dependencies" class="smpl">comment</a> ) )
     2780</pre><p id="rfc.section.11.9.p.4">Example:</p>
     2781      <div id="rfc.figure.u.42"></div><pre class="text">  Server: CERN/3.0 libwww/2.17
     2782</pre><p id="rfc.section.11.9.p.6">If the response is being forwarded through a proxy, the proxy application <em class="bcp14">MUST NOT</em> modify the Server header field. Instead, it <em class="bcp14">MUST</em> include a Via field (as described in <a href="p1-messaging.html#header.via" title="Via">Section 6.2</a> of <a href="#Part1" id="rfc.xref.Part1.47"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>).
     2783      </p>
     2784      <div class="note" id="rfc.section.11.9.p.7">
    23322785         <p> <b>Note:</b> Revealing the specific software version of the server might allow the server machine to become more vulnerable to attacks
    23332786            against software that is known to contain security holes. Server implementors are encouraged to make this field a configurable
     
    23372790      <div id="rfc.iref.u.1"></div>
    23382791      <div id="rfc.iref.h.11"></div>
    2339       <h2 id="rfc.section.7.10"><a href="#rfc.section.7.10">7.10</a>&nbsp;<a id="header.user-agent" href="#header.user-agent">User-Agent</a></h2>
    2340       <p id="rfc.section.7.10.p.1">The "User-Agent" header field contains information about the user agent originating the request. User agents <em class="bcp14">SHOULD</em> include this field with requests.
    2341       </p>
    2342       <p id="rfc.section.7.10.p.2">Typically, it is used for statistical purposes, the tracing of protocol violations, and tailoring responses to avoid particular
     2792      <h2 id="rfc.section.11.10"><a href="#rfc.section.11.10">11.10</a>&nbsp;<a id="header.user-agent" href="#header.user-agent">User-Agent</a></h2>
     2793      <p id="rfc.section.11.10.p.1">The "User-Agent" header field contains information about the user agent originating the request. User agents <em class="bcp14">SHOULD</em> include this field with requests.
     2794      </p>
     2795      <p id="rfc.section.11.10.p.2">Typically, it is used for statistical purposes, the tracing of protocol violations, and tailoring responses to avoid particular
    23432796         user agent limitations.
    23442797      </p>
    2345       <p id="rfc.section.7.10.p.3">The field can contain multiple product tokens (<a href="#product.tokens" title="Product Tokens">Section&nbsp;6.2</a>) and comments (<a href="p1-messaging.html#header.fields" title="Header Fields">Section 3.2</a> of <a href="#Part1" id="rfc.xref.Part1.41"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) identifying the agent and its significant subproducts. By convention, the product tokens are listed in order of their significance
     2798      <p id="rfc.section.11.10.p.3">The field can contain multiple product tokens (<a href="#product.tokens" title="Product Tokens">Section&nbsp;6.2</a>) and comments (<a href="p1-messaging.html#header.fields" title="Header Fields">Section 3.2</a> of <a href="#Part1" id="rfc.xref.Part1.48"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) identifying the agent and its significant subproducts. By convention, the product tokens are listed in order of their significance
    23462799         for identifying the application.
    23472800      </p>
    2348       <p id="rfc.section.7.10.p.4">Because this field is usually sent on every request a user agent makes, implementations are encouraged not to include needlessly
     2801      <p id="rfc.section.11.10.p.4">Because this field is usually sent on every request a user agent makes, implementations are encouraged not to include needlessly
    23492802         fine-grained detail, and to limit (or even prohibit) the addition of subproducts by third parties. Overly long and detailed
    23502803         User-Agent field values make requests larger and can also be used to identify ("fingerprint") the user against their wishes.
    23512804      </p>
    2352       <p id="rfc.section.7.10.p.5">Likewise, implementations are encouraged not to use the product tokens of other implementations in order to declare compatibility
     2805      <p id="rfc.section.11.10.p.5">Likewise, implementations are encouraged not to use the product tokens of other implementations in order to declare compatibility
    23532806         with them, as this circumvents the purpose of the field. Finally, they are encouraged not to use comments to identify products;
    23542807         doing so makes the field value more difficult to parse.
    23552808      </p>
    2356       <div id="rfc.figure.u.36"></div><pre class="inline"><span id="rfc.iref.g.38"></span>  <a href="#header.user-agent" class="smpl">User-Agent</a> = <a href="#product.tokens" class="smpl">product</a> *( <a href="#core.rules" class="smpl">RWS</a> ( <a href="#product.tokens" class="smpl">product</a> / <a href="#abnf.dependencies" class="smpl">comment</a> ) )
    2357 </pre><p id="rfc.section.7.10.p.7">Example:</p>
    2358       <div id="rfc.figure.u.37"></div><pre class="text">  User-Agent: CERN-LineMode/2.15 libwww/2.17b3
    2359 </pre><h1 id="rfc.section.8"><a href="#rfc.section.8">8.</a>&nbsp;<a id="IANA.considerations" href="#IANA.considerations">IANA Considerations</a></h1>
    2360       <h2 id="rfc.section.8.1"><a href="#rfc.section.8.1">8.1</a>&nbsp;<a id="method.registration" href="#method.registration">Method Registry</a></h2>
    2361       <p id="rfc.section.8.1.p.1">The registration procedure for HTTP request methods is defined by <a href="#method.registry" title="Method Registry">Section&nbsp;2.2</a> of this document.
    2362       </p>
    2363       <p id="rfc.section.8.1.p.2">The HTTP Method Registry shall be created at &lt;<a href="http://www.iana.org/assignments/http-methods">http://www.iana.org/assignments/http-methods</a>&gt; and be populated with the registrations below:
     2809      <div id="rfc.figure.u.43"></div><pre class="inline"><span id="rfc.iref.g.48"></span>  <a href="#header.user-agent" class="smpl">User-Agent</a> = <a href="#product.tokens" class="smpl">product</a> *( <a href="#core.rules" class="smpl">RWS</a> ( <a href="#product.tokens" class="smpl">product</a> / <a href="#abnf.dependencies" class="smpl">comment</a> ) )
     2810</pre><p id="rfc.section.11.10.p.7">Example:</p>
     2811      <div id="rfc.figure.u.44"></div><pre class="text">  User-Agent: CERN-LineMode/2.15 libwww/2.17b3
     2812</pre><div id="rfc.iref.a.2"></div>
     2813      <div id="rfc.iref.h.12"></div>
     2814      <h2 id="rfc.section.11.11"><a href="#rfc.section.11.11">11.11</a>&nbsp;<a id="header.accept" href="#header.accept">Accept</a></h2>
     2815      <p id="rfc.section.11.11.p.1">The "Accept" header field can be used by user agents to specify response media types that are acceptable. Accept header fields
     2816         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
     2817         for an in-line image.
     2818      </p>
     2819      <div id="rfc.figure.u.45"></div><pre class="inline"><span id="rfc.iref.g.49"></span><span id="rfc.iref.g.50"></span><span id="rfc.iref.g.51"></span><span id="rfc.iref.g.52"></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> ] )
     2820 
     2821  <a href="#header.accept" class="smpl">media-range</a>    = ( "*/*"
     2822                   / ( <a href="#media.types" class="smpl">type</a> "/" "*" )
     2823                   / ( <a href="#media.types" class="smpl">type</a> "/" <a href="#media.types" class="smpl">subtype</a> )
     2824                   ) *( <a href="#core.rules" class="smpl">OWS</a> ";" <a href="#core.rules" class="smpl">OWS</a> <a href="#rule.parameter" class="smpl">parameter</a> )
     2825  <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=" qvalue *( <a href="#header.accept" class="smpl">accept-ext</a> )
     2826  <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> [ "=" word ]
     2827</pre><p id="rfc.section.11.11.p.3">The asterisk "*" character is used to group media types into ranges, with "*/*" indicating all media types and "type/*" indicating
     2828         all subtypes of that type. The media-range <em class="bcp14">MAY</em> include media type parameters that are applicable to that range.
     2829      </p>
     2830      <p id="rfc.section.11.11.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
     2831         "q" parameter (if any) separates the media-range parameter(s) from the accept-params. Quality factors allow the user or user
     2832         agent to indicate the relative degree of preference for that media-range, using the qvalue scale from 0 to 1 (qvalue;). The
     2833         default value is q=1.
     2834      </p>
     2835      <div class="note" id="rfc.section.11.11.p.5">
     2836         <p> <b>Note:</b> Use of the "q" parameter name to separate media type parameters from Accept extension parameters is due to historical practice.
     2837            Although this prevents any media type parameter named "q" from being used with a media range, such an event is believed to
     2838            be unlikely given the lack of any "q" parameters in the IANA media type registry and the rare usage of any media type parameters
     2839            in Accept. Future media types are discouraged from registering any parameter named "q".
     2840         </p>
     2841      </div>
     2842      <p id="rfc.section.11.11.p.6">The example</p>
     2843      <div id="rfc.figure.u.46"></div><pre class="text">  Accept: audio/*; q=0.2, audio/basic
     2844</pre><p id="rfc.section.11.11.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
     2845         quality".
     2846      </p>
     2847      <p id="rfc.section.11.11.p.9">A request without any Accept header field implies that the user agent will accept any media type in response. If an Accept
     2848         header field is present in a request and none of the available representations for the response have a media type that is
     2849         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
     2850         the response as if it is not subject to content negotiation.
     2851      </p>
     2852      <p id="rfc.section.11.11.p.10">A more elaborate example is</p>
     2853      <div id="rfc.figure.u.47"></div><pre class="text">  Accept: text/plain; q=0.5, text/html,
     2854          text/x-dvi; q=0.8, text/x-c
     2855</pre><p id="rfc.section.11.11.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
     2856         send the text/x-dvi representation, and if that does not exist, send the text/plain representation".
     2857      </p>
     2858      <p id="rfc.section.11.11.p.13">Media ranges can be overridden by more specific media ranges or specific media types. If more than one media range applies
     2859         to a given type, the most specific reference has precedence. For example,
     2860      </p>
     2861      <div id="rfc.figure.u.48"></div><pre class="text">  Accept: text/*, text/plain, text/plain;format=flowed, */*
     2862</pre><p id="rfc.section.11.11.p.15">have the following precedence: </p>
     2863      <ol>
     2864         <li>text/plain;format=flowed</li>
     2865         <li>text/plain</li>
     2866         <li>text/*</li>
     2867         <li>*/*</li>
     2868      </ol>
     2869      <p id="rfc.section.11.11.p.16">The media type quality factor associated with a given type is determined by finding the media range with the highest precedence
     2870         which matches that type. For example,
     2871      </p>
     2872      <div id="rfc.figure.u.49"></div><pre class="text">  Accept: text/*;q=0.3, text/html;q=0.7, text/html;level=1,
     2873          text/html;level=2;q=0.4, */*;q=0.5
     2874</pre><p id="rfc.section.11.11.p.18">would cause the following values to be associated:</p>
     2875      <div id="rfc.table.u.7">
     2876         <table class="tt full left" cellpadding="3" cellspacing="0">
     2877            <thead>
     2878               <tr>
     2879                  <th>Media Type</th>
     2880                  <th>Quality Value</th>
     2881               </tr>
     2882            </thead>
     2883            <tbody>
     2884               <tr>
     2885                  <td class="left">text/html;level=1</td>
     2886                  <td class="left">1</td>
     2887               </tr>
     2888               <tr>
     2889                  <td class="left">text/html</td>
     2890                  <td class="left">0.7</td>
     2891               </tr>
     2892               <tr>
     2893                  <td class="left">text/plain</td>
     2894                  <td class="left">0.3</td>
     2895               </tr>
     2896               <tr>
     2897                  <td class="left">image/jpeg</td>
     2898                  <td class="left">0.5</td>
     2899               </tr>
     2900               <tr>
     2901                  <td class="left">text/html;level=2</td>
     2902                  <td class="left">0.4</td>
     2903               </tr>
     2904               <tr>
     2905                  <td class="left">text/html;level=3</td>
     2906                  <td class="left">0.7</td>
     2907               </tr>
     2908            </tbody>
     2909         </table>
     2910      </div>
     2911      <p id="rfc.section.11.11.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
     2912         is a closed system which cannot interact with other rendering agents, this default set ought to be configurable by the user.
     2913      </p>
     2914      <div id="rfc.iref.a.3"></div>
     2915      <div id="rfc.iref.h.13"></div>
     2916      <h2 id="rfc.section.11.12"><a href="#rfc.section.11.12">11.12</a>&nbsp;<a id="header.accept-charset" href="#header.accept-charset">Accept-Charset</a></h2>
     2917      <p id="rfc.section.11.12.p.1">The "Accept-Charset" header field can be used by user agents to indicate what character encodings are acceptable in a response
     2918         payload. This field allows clients capable of understanding more comprehensive or special-purpose character encodings to signal
     2919         that capability to a server which is capable of representing documents in those character encodings.
     2920      </p>
     2921      <div id="rfc.figure.u.50"></div><pre class="inline"><span id="rfc.iref.g.53"></span>  <a href="#header.accept-charset" class="smpl">Accept-Charset</a> = 1#( ( <a href="#rule.charset" class="smpl">charset</a> / "*" )
     2922                         [ <a href="#core.rules" class="smpl">OWS</a> ";" <a href="#core.rules" class="smpl">OWS</a> "q=" qvalue ] )
     2923</pre><p id="rfc.section.11.12.p.3">Character encoding values (a.k.a., charsets) are described in <a href="#character.sets" title="Character Encodings (charset)">Section&nbsp;7.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
     2924         example is
     2925      </p>
     2926      <div id="rfc.figure.u.51"></div><pre class="text">  Accept-Charset: iso-8859-5, unicode-1-1;q=0.8
     2927</pre><p id="rfc.section.11.12.p.5">The special value "*", if present in the Accept-Charset field, matches every character encoding which is not mentioned elsewhere
     2928         in the Accept-Charset field. If no "*" is present in an Accept-Charset field, then all character encodings not explicitly
     2929         mentioned get a quality value of 0.
     2930      </p>
     2931      <p id="rfc.section.11.12.p.6">A request without any Accept-Charset header field implies that the user agent will accept any character encoding in response.
     2932         If an Accept-Charset header field is present in a request and none of the available representations for the response have
     2933         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
     2934         field by treating the response as if it is not subject to content negotiation.
     2935      </p>
     2936      <div id="rfc.iref.a.4"></div>
     2937      <div id="rfc.iref.h.14"></div>
     2938      <h2 id="rfc.section.11.13"><a href="#rfc.section.11.13">11.13</a>&nbsp;<a id="header.accept-encoding" href="#header.accept-encoding">Accept-Encoding</a></h2>
     2939      <p id="rfc.section.11.13.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;7.2</a>) are acceptable in the response. An "identity" token is used as a synonym for "no encoding" in order to communicate when
     2940         no encoding is preferred.
     2941      </p>
     2942      <div id="rfc.figure.u.52"></div><pre class="inline"><span id="rfc.iref.g.54"></span><span id="rfc.iref.g.55"></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=" qvalue ] )
     2943  <a href="#header.accept-encoding" class="smpl">codings</a>          = <a href="#content.codings" class="smpl">content-coding</a> / "identity" / "*"
     2944</pre><p id="rfc.section.11.13.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.
     2945      </p>
     2946      <p id="rfc.section.11.13.p.4">For example,</p>
     2947      <div id="rfc.figure.u.53"></div><pre class="text">  Accept-Encoding: compress, gzip
     2948  Accept-Encoding:
     2949  Accept-Encoding: *
     2950  Accept-Encoding: compress;q=0.5, gzip;q=1.0
     2951  Accept-Encoding: gzip;q=1.0, identity; q=0.5, *;q=0
     2952</pre><p id="rfc.section.11.13.p.6">A server tests whether a content-coding for a given representation is acceptable, according to an Accept-Encoding field, using
     2953         these rules:
     2954      </p>
     2955      <ol>
     2956         <li>The special "*" symbol in an Accept-Encoding field matches any available content-coding not explicitly listed in the header
     2957            field.
     2958         </li>
     2959         <li>If the representation has no content-coding, then it is acceptable by default unless specifically excluded by the Accept-Encoding
     2960            field stating either "identity;q=0" or "*;q=0" without a more specific entry for "identity".
     2961         </li>
     2962         <li>If the representation's content-coding is one of the content-codings listed in the Accept-Encoding field, then it is acceptable
     2963            unless it is accompanied by a qvalue of 0. (As defined in qvalue;, a qvalue of 0 means "not acceptable".)
     2964         </li>
     2965         <li>If multiple content-codings are acceptable, then the acceptable content-coding with the highest non-zero qvalue is preferred.</li>
     2966      </ol>
     2967      <p id="rfc.section.11.13.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
     2968         in response. If an Accept-Encoding header field is present in a request and none of the available representations for the
     2969         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.
     2970      </p>
     2971      <p id="rfc.section.11.13.p.8">A request without an Accept-Encoding header field implies that the user agent will accept any content-coding in response,
     2972         but a representation without content-coding is preferred for compatibility with the widest variety of user agents.
     2973      </p>
     2974      <div class="note" id="rfc.section.11.13.p.9">
     2975         <p> <b>Note:</b> Most HTTP/1.0 applications do not recognize or obey qvalues associated with content-codings. This means that qvalues will
     2976            not work and are not permitted with x-gzip or x-compress.
     2977         </p>
     2978      </div>
     2979      <div id="rfc.iref.a.5"></div>
     2980      <div id="rfc.iref.h.15"></div>
     2981      <h2 id="rfc.section.11.14"><a href="#rfc.section.11.14">11.14</a>&nbsp;<a id="header.accept-language" href="#header.accept-language">Accept-Language</a></h2>
     2982      <p id="rfc.section.11.14.p.1">The "Accept-Language" header field can be used by user agents to indicate the set of natural languages that are preferred
     2983         in the response. Language tags are defined in <a href="#language.tags" title="Language Tags">Section&nbsp;7.4</a>.
     2984      </p>
     2985      <div id="rfc.figure.u.54"></div><pre class="inline"><span id="rfc.iref.g.56"></span><span id="rfc.iref.g.57"></span>  <a href="#header.accept-language" class="smpl">Accept-Language</a> =
     2986                    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=" qvalue ] )
     2987  <a href="#header.accept-language" class="smpl">language-range</a>  =
     2988            &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;
     2989</pre><p id="rfc.section.11.14.p.3">Each language-range can be given an associated quality value which represents an estimate of the user's preference for the
     2990         languages specified by that range. The quality value defaults to "q=1". For example,
     2991      </p>
     2992      <div id="rfc.figure.u.55"></div><pre class="text">  Accept-Language: da, en-gb;q=0.8, en;q=0.7
     2993</pre><p id="rfc.section.11.14.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>)
     2994      </p>
     2995      <p id="rfc.section.11.14.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.
     2996      </p>
     2997      <div class="note" id="rfc.section.11.14.p.7">
     2998         <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.3"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>.
     2999         </p>
     3000      </div>
     3001      <p id="rfc.section.11.14.p.8">It might be contrary to the privacy expectations of the user to send an Accept-Language header field with the complete linguistic
     3002         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;13.5</a>.
     3003      </p>
     3004      <p id="rfc.section.11.14.p.9">As intelligibility is highly dependent on the individual user, it is recommended that client applications make the choice
     3005         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.
     3006      </p>
     3007      <div class="note" id="rfc.section.11.14.p.10">
     3008         <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
     3009            familiar with the details of language matching as described above, and ought to be provided appropriate guidance. As an example,
     3010            users might assume that on selecting "en-gb", they will be served any kind of English document if British English is not available.
     3011            A user agent might suggest in such a case to add "en" to get the best matching behavior.
     3012         </p>
     3013      </div>
     3014      <div id="rfc.iref.c.7"></div>
     3015      <div id="rfc.iref.h.16"></div>
     3016      <h2 id="rfc.section.11.15"><a href="#rfc.section.11.15">11.15</a>&nbsp;<a id="header.content-encoding" href="#header.content-encoding">Content-Encoding</a></h2>
     3017      <p id="rfc.section.11.15.p.1">The "Content-Encoding" header field indicates what content-codings have been applied to the representation beyond those inherent
     3018         in the media type, and thus what decoding mechanisms have to be applied in order to obtain the media-type referenced by the
     3019         Content-Type header field. Content-Encoding is primarily used to allow a representation to be compressed without losing the
     3020         identity of its underlying media type.
     3021      </p>
     3022      <div id="rfc.figure.u.56"></div><pre class="inline"><span id="rfc.iref.g.58"></span>  <a href="#header.content-encoding" class="smpl">Content-Encoding</a> = 1#<a href="#content.codings" class="smpl">content-coding</a>
     3023</pre><p id="rfc.section.11.15.p.3">Content codings are defined in <a href="#content.codings" title="Content Codings">Section&nbsp;7.2</a>. An example of its use is
     3024      </p>
     3025      <div id="rfc.figure.u.57"></div><pre class="text">  Content-Encoding: gzip
     3026</pre><p id="rfc.section.11.15.p.5">The content-coding is a characteristic of the representation. Typically, the representation body is stored with this encoding
     3027         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
     3028         directive is present in the message.
     3029      </p>
     3030      <p id="rfc.section.11.15.p.6">If the media type includes an inherent encoding, such as a data format that is always compressed, then that encoding would
     3031         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
     3032         would only be listed if, for some bizarre reason, it is applied a second time to form the representation. Likewise, an origin
     3033         server might choose to publish the same payload data as multiple representations that differ only in whether the coding is
     3034         defined as part of Content-Type or Content-Encoding, since some user agents will behave differently in their handling of each
     3035         response (e.g., open a "Save as ..." dialog instead of automatic decompression and rendering of content).
     3036      </p>
     3037      <p id="rfc.section.11.15.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;11.15</a>) that lists the content-coding(s) applied.
     3038      </p>
     3039      <p id="rfc.section.11.15.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.
     3040      </p>
     3041      <p id="rfc.section.11.15.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).
     3042      </p>
     3043      <div id="rfc.iref.c.8"></div>
     3044      <div id="rfc.iref.h.17"></div>
     3045      <h2 id="rfc.section.11.16"><a href="#rfc.section.11.16">11.16</a>&nbsp;<a id="header.content-language" href="#header.content-language">Content-Language</a></h2>
     3046      <p id="rfc.section.11.16.p.1">The "Content-Language" header field describes the natural language(s) of the intended audience for the representation. Note
     3047         that this might not be equivalent to all the languages used within the representation.
     3048      </p>
     3049      <div id="rfc.figure.u.58"></div><pre class="inline"><span id="rfc.iref.g.59"></span>  <a href="#header.content-language" class="smpl">Content-Language</a> = 1#<a href="#language.tags" class="smpl">language-tag</a>
     3050</pre><p id="rfc.section.11.16.p.3">Language tags are defined in <a href="#language.tags" title="Language Tags">Section&nbsp;7.4</a>. The primary purpose of Content-Language is to allow a user to identify and differentiate representations according to the
     3051         user's own preferred language. Thus, if the body content is intended only for a Danish-literate audience, the appropriate
     3052         field is
     3053      </p>
     3054      <div id="rfc.figure.u.59"></div><pre class="text">  Content-Language: da
     3055</pre><p id="rfc.section.11.16.p.5">If no Content-Language is specified, the default is that the content is intended for all language audiences. This might mean
     3056         that the sender does not consider it to be specific to any natural language, or that the sender does not know for which language
     3057         it is intended.
     3058      </p>
     3059      <p id="rfc.section.11.16.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
     3060         simultaneously in the original Maori and English versions, would call for
     3061      </p>
     3062      <div id="rfc.figure.u.60"></div><pre class="text">  Content-Language: mi, en
     3063</pre><p id="rfc.section.11.16.p.8">However, just because multiple languages are present within a representation does not mean that it is intended for multiple
     3064         linguistic audiences. An example would be a beginner's language primer, such as "A First Lesson in Latin", which is clearly
     3065         intended to be used by an English-literate audience. In this case, the Content-Language would properly only include "en".
     3066      </p>
     3067      <p id="rfc.section.11.16.p.9">Content-Language <em class="bcp14">MAY</em> be applied to any media type — it is not limited to textual documents.
     3068      </p>
     3069      <div id="rfc.iref.c.9"></div>
     3070      <div id="rfc.iref.h.18"></div>
     3071      <h2 id="rfc.section.11.17"><a href="#rfc.section.11.17">11.17</a>&nbsp;<a id="header.content-location" href="#header.content-location">Content-Location</a></h2>
     3072      <p id="rfc.section.11.17.p.1">The "Content-Location" header field supplies a URI that can be used as a specific identifier for the representation in this
     3073         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
     3074         would contain the same representation that is enclosed as payload in this message.
     3075      </p>
     3076      <div id="rfc.figure.u.61"></div><pre class="inline"><span id="rfc.iref.g.60"></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>
     3077</pre><p id="rfc.section.11.17.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.49"><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
     3078         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.
     3079      </p>
     3080      <p id="rfc.section.11.17.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
     3081         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
     3082         when no Content-Location is provided by the server. For a state-changing request like PUT or POST, it implies that the server's
     3083         response contains the new representation of that resource, thereby distinguishing it from representations that might only
     3084         report about the action (e.g., "It worked!"). This allows authoring applications to update their local copies without the
     3085         need for a subsequent GET request.
     3086      </p>
     3087      <p id="rfc.section.11.17.p.5">If Content-Location is included in a response message and its value differs from the effective request URI, then the origin
     3088         server is informing recipients that this representation has its own, presumably more specific, identifier. For a GET or HEAD
     3089         request, this is an indication that the effective request URI identifies a resource that is subject to content negotiation
     3090         and the selected representation for this response can also be found at the identified URI. For other methods, such a Content-Location
     3091         indicates that this representation contains a report on the action's status and the same report is available (for future access
     3092         with GET) at the given URI. For example, a purchase transaction made via a POST request might include a receipt document as
     3093         the payload of the 200 response; the Content-Location value provides an identifier for retrieving a copy of that same receipt
     3094         in the future.
     3095      </p>
     3096      <p id="rfc.section.11.17.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
     3097         representation (prior to any subsequent modification of the content by that user agent). In other words, the user agent is
     3098         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
     3099         resource and the origin server accepts that PUT (without redirection), then the new set of values for that resource is expected
     3100         to be consistent with the one representation supplied in that PUT; the Content-Location cannot be used as a form of reverse
     3101         content selection that identifies only one of the negotiated representations to be updated. If the user agent had wanted the
     3102         latter semantics, it would have applied the PUT directly to the Content-Location URI.
     3103      </p>
     3104      <p id="rfc.section.11.17.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
     3105         in other contexts, such as within source links or other metadata.
     3106      </p>
     3107      <p id="rfc.section.11.17.p.8">A cache cannot assume that a representation with a Content-Location different from the URI used to retrieve it can be used
     3108         to respond to later requests on that Content-Location URI.
     3109      </p>
     3110      <p id="rfc.section.11.17.p.9">If the Content-Location value is a partial URI, the partial URI is interpreted relative to the effective request URI.</p>
     3111      <div id="rfc.iref.c.10"></div>
     3112      <div id="rfc.iref.h.19"></div>
     3113      <h2 id="rfc.section.11.18"><a href="#rfc.section.11.18">11.18</a>&nbsp;<a id="header.content-type" href="#header.content-type">Content-Type</a></h2>
     3114      <p id="rfc.section.11.18.p.1">The "Content-Type" header field indicates the media type of the representation. In the case of responses to the HEAD method,
     3115         the media type is that which would have been sent had the request been a GET.
     3116      </p>
     3117      <div id="rfc.figure.u.62"></div><pre class="inline"><span id="rfc.iref.g.61"></span>  <a href="#header.content-type" class="smpl">Content-Type</a> = <a href="#media.types" class="smpl">media-type</a>
     3118</pre><p id="rfc.section.11.18.p.3">Media types are defined in <a href="#media.types" title="Media Types">Section&nbsp;7.3</a>. An example of the field is
     3119      </p>
     3120      <div id="rfc.figure.u.63"></div><pre class="text">  Content-Type: text/html; charset=ISO-8859-4
     3121</pre><p id="rfc.section.11.18.p.5">Further discussion of Content-Type is provided in <a href="#representation.data" title="Representation Data">Section&nbsp;9.2</a>.
     3122      </p>
     3123      <h1 id="rfc.section.12"><a href="#rfc.section.12">12.</a>&nbsp;<a id="IANA.considerations" href="#IANA.considerations">IANA Considerations</a></h1>
     3124      <h2 id="rfc.section.12.1"><a href="#rfc.section.12.1">12.1</a>&nbsp;<a id="method.registration" href="#method.registration">Method Registry</a></h2>
     3125      <p id="rfc.section.12.1.p.1">The registration procedure for HTTP request methods is defined by <a href="#method.registry" title="Method Registry">Section&nbsp;2.2</a> of this document.
     3126      </p>
     3127      <p id="rfc.section.12.1.p.2">The HTTP Method Registry shall be created at &lt;<a href="http://www.iana.org/assignments/http-methods">http://www.iana.org/assignments/http-methods</a>&gt; and be populated with the registrations below:
    23643128      </p>
    23653129      <div id="rfc.table.1">
     
    24253189         </table>
    24263190      </div>
    2427       <h2 id="rfc.section.8.2"><a href="#rfc.section.8.2">8.2</a>&nbsp;<a id="status.code.registration" href="#status.code.registration">Status Code Registry</a></h2>
    2428       <p id="rfc.section.8.2.p.1">The registration procedure for HTTP Status Codes — previously defined in <a href="http://tools.ietf.org/html/rfc2817#section-7.1">Section 7.1</a> of <a href="#RFC2817" id="rfc.xref.RFC2817.1"><cite title="Upgrading to TLS Within HTTP/1.1">[RFC2817]</cite></a> — is now defined by <a href="#status.code.registry" title="Status Code Registry">Section&nbsp;4.2</a> of this document.
    2429       </p>
    2430       <p id="rfc.section.8.2.p.2">The HTTP Status Code Registry located at &lt;<a href="http://www.iana.org/assignments/http-status-codes">http://www.iana.org/assignments/http-status-codes</a>&gt; shall be updated with the registrations below:
     3191      <h2 id="rfc.section.12.2"><a href="#rfc.section.12.2">12.2</a>&nbsp;<a id="status.code.registration" href="#status.code.registration">Status Code Registry</a></h2>
     3192      <p id="rfc.section.12.2.p.1">The registration procedure for HTTP Status Codes — previously defined in <a href="http://tools.ietf.org/html/rfc2817#section-7.1">Section 7.1</a> of <a href="#RFC2817" id="rfc.xref.RFC2817.1"><cite title="Upgrading to TLS Within HTTP/1.1">[RFC2817]</cite></a> — is now defined by <a href="#status.code.registry" title="Status Code Registry">Section&nbsp;4.2</a> of this document.
     3193      </p>
     3194      <p id="rfc.section.12.2.p.2">The HTTP Status Code Registry located at &lt;<a href="http://www.iana.org/assignments/http-status-codes">http://www.iana.org/assignments/http-status-codes</a>&gt; shall be updated with the registrations below:
    24313195      </p>
    24323196      <div id="rfc.table.2">
     
    26603424         </table>
    26613425      </div>
    2662       <h2 id="rfc.section.8.3"><a href="#rfc.section.8.3">8.3</a>&nbsp;<a id="header.field.registration" href="#header.field.registration">Header Field Registration</a></h2>
    2663       <p id="rfc.section.8.3.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.3"><cite title="Registration Procedures for Message Header Fields">[RFC3864]</cite></a>):
     3426      <h2 id="rfc.section.12.3"><a href="#rfc.section.12.3">12.3</a>&nbsp;<a id="header.field.registration" href="#header.field.registration">Header Field Registration</a></h2>
     3427      <p id="rfc.section.12.3.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.3"><cite title="Registration Procedures for Message Header Fields">[RFC3864]</cite></a>):
    26643428      </p>
    26653429      <div id="rfc.table.3">
     
    26763440            <tbody>
    26773441               <tr>
     3442                  <td class="left">Accept</td>
     3443                  <td class="left">http</td>
     3444                  <td class="left">standard</td>
     3445                  <td class="left"> <a href="#header.accept" id="rfc.xref.header.accept.4" title="Accept">Section&nbsp;11.11</a>
     3446                  </td>
     3447               </tr>
     3448               <tr>
     3449                  <td class="left">Accept-Charset</td>
     3450                  <td class="left">http</td>
     3451                  <td class="left">standard</td>
     3452                  <td class="left"> <a href="#header.accept-charset" id="rfc.xref.header.accept-charset.3" title="Accept-Charset">Section&nbsp;11.12</a>
     3453                  </td>
     3454               </tr>
     3455               <tr>
     3456                  <td class="left">Accept-Encoding</td>
     3457                  <td class="left">http</td>
     3458                  <td class="left">standard</td>
     3459                  <td class="left"> <a href="#header.accept-encoding" id="rfc.xref.header.accept-encoding.4" title="Accept-Encoding">Section&nbsp;11.13</a>
     3460                  </td>
     3461               </tr>
     3462               <tr>
     3463                  <td class="left">Accept-Language</td>
     3464                  <td class="left">http</td>
     3465                  <td class="left">standard</td>
     3466                  <td class="left"> <a href="#header.accept-language" id="rfc.xref.header.accept-language.3" title="Accept-Language">Section&nbsp;11.14</a>
     3467                  </td>
     3468               </tr>
     3469               <tr>
    26783470                  <td class="left">Allow</td>
    26793471                  <td class="left">http</td>
    26803472                  <td class="left">standard</td>
    2681                   <td class="left"> <a href="#header.allow" id="rfc.xref.header.allow.3" title="Allow">Section&nbsp;7.1</a>
     3473                  <td class="left"> <a href="#header.allow" id="rfc.xref.header.allow.3" title="Allow">Section&nbsp;11.1</a>
     3474                  </td>
     3475               </tr>
     3476               <tr>
     3477                  <td class="left">Content-Encoding</td>
     3478                  <td class="left">http</td>
     3479                  <td class="left">standard</td>
     3480                  <td class="left"> <a href="#header.content-encoding" id="rfc.xref.header.content-encoding.4" title="Content-Encoding">Section&nbsp;11.15</a>
     3481                  </td>
     3482               </tr>
     3483               <tr>
     3484                  <td class="left">Content-Language</td>
     3485                  <td class="left">http</td>
     3486                  <td class="left">standard</td>
     3487                  <td class="left"> <a href="#header.content-language" id="rfc.xref.header.content-language.2" title="Content-Language">Section&nbsp;11.16</a>
     3488                  </td>
     3489               </tr>
     3490               <tr>
     3491                  <td class="left">Content-Location</td>
     3492                  <td class="left">http</td>
     3493                  <td class="left">standard</td>
     3494                  <td class="left"> <a href="#header.content-location" id="rfc.xref.header.content-location.4" title="Content-Location">Section&nbsp;11.17</a>
     3495                  </td>
     3496               </tr>
     3497               <tr>
     3498                  <td class="left">Content-Type</td>
     3499                  <td class="left">http</td>
     3500                  <td class="left">standard</td>
     3501                  <td class="left"> <a href="#header.content-type" id="rfc.xref.header.content-type.5" title="Content-Type">Section&nbsp;11.18</a>
    26823502                  </td>
    26833503               </tr>
     
    26863506                  <td class="left">http</td>
    26873507                  <td class="left">standard</td>
    2688                   <td class="left"> <a href="#header.date" id="rfc.xref.header.date.2" title="Date">Section&nbsp;7.2</a>
     3508                  <td class="left"> <a href="#header.date" id="rfc.xref.header.date.2" title="Date">Section&nbsp;11.2</a>
    26893509                  </td>
    26903510               </tr>
     
    26933513                  <td class="left">http</td>
    26943514                  <td class="left">standard</td>
    2695                   <td class="left"> <a href="#header.expect" id="rfc.xref.header.expect.3" title="Expect">Section&nbsp;7.3</a>
     3515                  <td class="left"> <a href="#header.expect" id="rfc.xref.header.expect.3" title="Expect">Section&nbsp;11.3</a>
    26963516                  </td>
    26973517               </tr>
     
    27003520                  <td class="left">http</td>
    27013521                  <td class="left">standard</td>
    2702                   <td class="left"> <a href="#header.from" id="rfc.xref.header.from.2" title="From">Section&nbsp;7.4</a>
     3522                  <td class="left"> <a href="#header.from" id="rfc.xref.header.from.2" title="From">Section&nbsp;11.4</a>
    27033523                  </td>
    27043524               </tr>
     
    27073527                  <td class="left">http</td>
    27083528                  <td class="left">standard</td>
    2709                   <td class="left"> <a href="#header.location" id="rfc.xref.header.location.4" title="Location">Section&nbsp;7.5</a>
     3529                  <td class="left"> <a href="#header.location" id="rfc.xref.header.location.4" title="Location">Section&nbsp;11.5</a>
     3530                  </td>
     3531               </tr>
     3532               <tr>
     3533                  <td class="left">MIME-Version</td>
     3534                  <td class="left">http</td>
     3535                  <td class="left">standard</td>
     3536                  <td class="left"> <a href="#mime-version" id="rfc.xref.mime-version.1" title="MIME-Version">Appendix&nbsp;A.1</a>
    27103537                  </td>
    27113538               </tr>
     
    27143541                  <td class="left">http</td>
    27153542                  <td class="left">standard</td>
    2716                   <td class="left"> <a href="#header.max-forwards" id="rfc.xref.header.max-forwards.4" title="Max-Forwards">Section&nbsp;7.6</a>
     3543                  <td class="left"> <a href="#header.max-forwards" id="rfc.xref.header.max-forwards.4" title="Max-Forwards">Section&nbsp;11.6</a>
    27173544                  </td>
    27183545               </tr>
     
    27213548                  <td class="left">http</td>
    27223549                  <td class="left">standard</td>
    2723                   <td class="left"> <a href="#header.referer" id="rfc.xref.header.referer.2" title="Referer">Section&nbsp;7.7</a>
     3550                  <td class="left"> <a href="#header.referer" id="rfc.xref.header.referer.2" title="Referer">Section&nbsp;11.7</a>
    27243551                  </td>
    27253552               </tr>
     
    27283555                  <td class="left">http</td>
    27293556                  <td class="left">standard</td>
    2730                   <td class="left"> <a href="#header.retry-after" id="rfc.xref.header.retry-after.3" title="Retry-After">Section&nbsp;7.8</a>
     3557                  <td class="left"> <a href="#header.retry-after" id="rfc.xref.header.retry-after.3" title="Retry-After">Section&nbsp;11.8</a>
    27313558                  </td>
    27323559               </tr>
     
    27353562                  <td class="left">http</td>
    27363563                  <td class="left">standard</td>
    2737                   <td class="left"> <a href="#header.server" id="rfc.xref.header.server.2" title="Server">Section&nbsp;7.9</a>
     3564                  <td class="left"> <a href="#header.server" id="rfc.xref.header.server.2" title="Server">Section&nbsp;11.9</a>
    27383565                  </td>
    27393566               </tr>
     
    27423569                  <td class="left">http</td>
    27433570                  <td class="left">standard</td>
    2744                   <td class="left"> <a href="#header.user-agent" id="rfc.xref.header.user-agent.2" title="User-Agent">Section&nbsp;7.10</a>
     3571                  <td class="left"> <a href="#header.user-agent" id="rfc.xref.header.user-agent.3" title="User-Agent">Section&nbsp;11.10</a>
    27453572                  </td>
    27463573               </tr>
     
    27483575         </table>
    27493576      </div>
    2750       <p id="rfc.section.8.3.p.2">The change controller is: "IETF (iesg@ietf.org) - Internet Engineering Task Force".</p>
    2751       <h1 id="rfc.section.9"><a href="#rfc.section.9">9.</a>&nbsp;<a id="security.considerations" href="#security.considerations">Security Considerations</a></h1>
    2752       <p id="rfc.section.9.p.1">This section is meant to inform application developers, information providers, and users of the security limitations in HTTP/1.1
     3577      <p id="rfc.section.12.3.p.2">The change controller is: "IETF (iesg@ietf.org) - Internet Engineering Task Force".</p>
     3578      <h2 id="rfc.section.12.4"><a href="#rfc.section.12.4">12.4</a>&nbsp;<a id="content.coding.registration" href="#content.coding.registration">Content Coding Registry</a></h2>
     3579      <p id="rfc.section.12.4.p.1">The registration procedure for HTTP Content Codings is now defined by <a href="#content.coding.registry" title="Content Coding Registry">Section&nbsp;7.2.1</a> of this document.
     3580      </p>
     3581      <p id="rfc.section.12.4.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:
     3582      </p>
     3583      <div id="rfc.table.4">
     3584         <div id="iana.content.coding.registration.table"></div>
     3585         <table class="tt full left" cellpadding="3" cellspacing="0">
     3586            <thead>
     3587               <tr>
     3588                  <th>Name</th>
     3589                  <th>Description</th>
     3590                  <th>Reference</th>
     3591               </tr>
     3592            </thead>
     3593            <tbody>
     3594               <tr>
     3595                  <td class="left">compress</td>
     3596                  <td class="left">UNIX "compress" program method</td>
     3597                  <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.50"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>
     3598                  </td>
     3599               </tr>
     3600               <tr>
     3601                  <td class="left">deflate</td>
     3602                  <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>)
     3603                  </td>
     3604                  <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.51"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>
     3605                  </td>
     3606               </tr>
     3607               <tr>
     3608                  <td class="left">gzip</td>
     3609                  <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>
     3610                  <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.52"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>
     3611                  </td>
     3612               </tr>
     3613               <tr>
     3614                  <td class="left">identity</td>
     3615                  <td class="left">reserved (synonym for "no encoding" in Accept-Encoding header field)</td>
     3616                  <td class="left"> <a href="#header.accept-encoding" id="rfc.xref.header.accept-encoding.5" title="Accept-Encoding">Section&nbsp;11.13</a>
     3617                  </td>
     3618               </tr>
     3619            </tbody>
     3620         </table>
     3621      </div>
     3622      <h1 id="rfc.section.13"><a href="#rfc.section.13">13.</a>&nbsp;<a id="security.considerations" href="#security.considerations">Security Considerations</a></h1>
     3623      <p id="rfc.section.13.p.1">This section is meant to inform application developers, information providers, and users of the security limitations in HTTP/1.1
    27533624         as described by this document. The discussion does not include definitive solutions to the problems revealed, though it does
    27543625         make some suggestions for reducing security risks.
    27553626      </p>
    2756       <h2 id="rfc.section.9.1"><a href="#rfc.section.9.1">9.1</a>&nbsp;<a id="security.sensitive" href="#security.sensitive">Transfer of Sensitive Information</a></h2>
    2757       <p id="rfc.section.9.1.p.1">Like any generic data transfer protocol, HTTP cannot regulate the content of the data that is transferred, nor is there any
     3627      <h2 id="rfc.section.13.1"><a href="#rfc.section.13.1">13.1</a>&nbsp;<a id="security.sensitive" href="#security.sensitive">Transfer of Sensitive Information</a></h2>
     3628      <p id="rfc.section.13.1.p.1">Like any generic data transfer protocol, HTTP cannot regulate the content of the data that is transferred, nor is there any
    27583629         a priori method of determining the sensitivity of any particular piece of information within the context of any given request.
    27593630         Therefore, applications <em class="bcp14">SHOULD</em> supply as much control over this information as possible to the provider of that information. Four header fields are worth
    27603631         special mention in this context: Server, Via, Referer and From.
    27613632      </p>
    2762       <p id="rfc.section.9.1.p.2">Revealing the specific software version of the server might allow the server machine to become more vulnerable to attacks
     3633      <p id="rfc.section.13.1.p.2">Revealing the specific software version of the server might allow the server machine to become more vulnerable to attacks
    27633634         against software that is known to contain security holes. Implementors <em class="bcp14">SHOULD</em> make the Server header field a configurable option.
    27643635      </p>
    2765       <p id="rfc.section.9.1.p.3">Proxies which serve as a portal through a network firewall <em class="bcp14">SHOULD</em> take special precautions regarding the transfer of header information that identifies the hosts behind the firewall. In particular,
     3636      <p id="rfc.section.13.1.p.3">Proxies which serve as a portal through a network firewall <em class="bcp14">SHOULD</em> take special precautions regarding the transfer of header information that identifies the hosts behind the firewall. In particular,
    27663637         they <em class="bcp14">SHOULD</em> remove, or replace with sanitized versions, any Via fields generated behind the firewall.
    27673638      </p>
    2768       <p id="rfc.section.9.1.p.4">The Referer header field allows reading patterns to be studied and reverse links drawn. Although it can be very useful, its
     3639      <p id="rfc.section.13.1.p.4">The Referer header field allows reading patterns to be studied and reverse links drawn. Although it can be very useful, its
    27693640         power can be abused if user details are not separated from the information contained in the Referer. Even when the personal
    27703641         information has been removed, the Referer header field might indicate a private document's URI whose publication would be
    27713642         inappropriate.
    27723643      </p>
    2773       <p id="rfc.section.9.1.p.5">The information sent in the From field might conflict with the user's privacy interests or their site's security policy, and
     3644      <p id="rfc.section.13.1.p.5">The information sent in the From field might conflict with the user's privacy interests or their site's security policy, and
    27743645         hence it <em class="bcp14">SHOULD NOT</em> be transmitted without the user being able to disable, enable, and modify the contents of the field. The user <em class="bcp14">MUST</em> be able to set the contents of this field within a user preference or application defaults configuration.
    27753646      </p>
    2776       <p id="rfc.section.9.1.p.6">We suggest, though do not require, that a convenient toggle interface be provided for the user to enable or disable the sending
     3647      <p id="rfc.section.13.1.p.6">We suggest, though do not require, that a convenient toggle interface be provided for the user to enable or disable the sending
    27773648         of From and Referer information.
    27783649      </p>
    2779       <p id="rfc.section.9.1.p.7">The User-Agent (<a href="#header.user-agent" id="rfc.xref.header.user-agent.3" title="User-Agent">Section&nbsp;7.10</a>) or Server (<a href="#header.server" id="rfc.xref.header.server.3" title="Server">Section&nbsp;7.9</a>) header fields can sometimes be used to determine that a specific client or server has a particular security hole which might
     3650      <p id="rfc.section.13.1.p.7">The User-Agent (<a href="#header.user-agent" id="rfc.xref.header.user-agent.4" title="User-Agent">Section&nbsp;11.10</a>) or Server (<a href="#header.server" id="rfc.xref.header.server.3" title="Server">Section&nbsp;11.9</a>) header fields can sometimes be used to determine that a specific client or server has a particular security hole which might
    27803651         be exploited. Unfortunately, this same information is often used for other valuable purposes for which HTTP currently has
    27813652         no better mechanism.
    27823653      </p>
    2783       <p id="rfc.section.9.1.p.8">Furthermore, the User-Agent header field may contain enough entropy to be used, possibly in conjunction with other material,
     3654      <p id="rfc.section.13.1.p.8">Furthermore, the User-Agent header field may contain enough entropy to be used, possibly in conjunction with other material,
    27843655         to uniquely identify the user.
    27853656      </p>
    2786       <p id="rfc.section.9.1.p.9">Some request methods, like TRACE (<a href="#TRACE" id="rfc.xref.TRACE.3" title="TRACE">Section&nbsp;2.3.7</a>), expose information that was sent in request header fields within the body of their response. Clients <em class="bcp14">SHOULD</em> be careful with sensitive information, like Cookies, Authorization credentials, and other header fields that might be used
     3657      <p id="rfc.section.13.1.p.9">Some request methods, like TRACE (<a href="#TRACE" id="rfc.xref.TRACE.3" title="TRACE">Section&nbsp;2.3.7</a>), expose information that was sent in request header fields within the body of their response. Clients <em class="bcp14">SHOULD</em> be careful with sensitive information, like Cookies, Authorization credentials, and other header fields that might be used
    27873658         to collect data from the client.
    27883659      </p>
    2789       <h2 id="rfc.section.9.2"><a href="#rfc.section.9.2">9.2</a>&nbsp;<a id="encoding.sensitive.information.in.uris" href="#encoding.sensitive.information.in.uris">Encoding Sensitive Information in URIs</a></h2>
    2790       <p id="rfc.section.9.2.p.1">Because the source of a link might be private information or might reveal an otherwise private information source, it is strongly
     3660      <h2 id="rfc.section.13.2"><a href="#rfc.section.13.2">13.2</a>&nbsp;<a id="encoding.sensitive.information.in.uris" href="#encoding.sensitive.information.in.uris">Encoding Sensitive Information in URIs</a></h2>
     3661      <p id="rfc.section.13.2.p.1">Because the source of a link might be private information or might reveal an otherwise private information source, it is strongly
    27913662         recommended that the user be able to select whether or not the Referer field is sent. For example, a browser client could
    27923663         have a toggle switch for browsing openly/anonymously, which would respectively enable/disable the sending of Referer and From
    27933664         information.
    27943665      </p>
    2795       <p id="rfc.section.9.2.p.2">Clients <em class="bcp14">SHOULD NOT</em> include a Referer header field in a (non-secure) HTTP request if the referring page was transferred with a secure protocol.
    2796       </p>
    2797       <p id="rfc.section.9.2.p.3">Authors of services <em class="bcp14">SHOULD NOT</em> use GET-based forms for the submission of sensitive data because that data will be placed in the request-target. Many existing
     3666      <p id="rfc.section.13.2.p.2">Clients <em class="bcp14">SHOULD NOT</em> include a Referer header field in a (non-secure) HTTP request if the referring page was transferred with a secure protocol.
     3667      </p>
     3668      <p id="rfc.section.13.2.p.3">Authors of services <em class="bcp14">SHOULD NOT</em> use GET-based forms for the submission of sensitive data because that data will be placed in the request-target. Many existing
    27983669         servers, proxies, and user agents log or display the request-target in places where it might be visible to third parties.
    27993670         Such services can use POST-based form submission instead.
    28003671      </p>
    2801       <h2 id="rfc.section.9.3"><a href="#rfc.section.9.3">9.3</a>&nbsp;<a id="location.spoofing-leakage" href="#location.spoofing-leakage">Location Header Fields: Spoofing and Information Leakage</a></h2>
    2802       <p id="rfc.section.9.3.p.1">If a single server supports multiple organizations that do not trust one another, then it <em class="bcp14">MUST</em> check the values of Location and Content-Location header fields in responses that are generated under control of said organizations
     3672      <h2 id="rfc.section.13.3"><a href="#rfc.section.13.3">13.3</a>&nbsp;<a id="location.spoofing-leakage" href="#location.spoofing-leakage">Location Header Fields: Spoofing and Information Leakage</a></h2>
     3673      <p id="rfc.section.13.3.p.1">If a single server supports multiple organizations that do not trust one another, then it <em class="bcp14">MUST</em> check the values of Location and Content-Location header fields in responses that are generated under control of said organizations
    28033674         to make sure that they do not attempt to invalidate resources over which they have no authority.
    28043675      </p>
    2805       <p id="rfc.section.9.3.p.2">Furthermore, appending the fragment identifier from one URI to another one obtained from a Location header field might leak
     3676      <p id="rfc.section.13.3.p.2">Furthermore, appending the fragment identifier from one URI to another one obtained from a Location header field might leak
    28063677         confidential information to the target server — although the fragment identifier is not transmitted in the final request,
    28073678         it might be visible to the user agent through other means, such as scripting.
    28083679      </p>
    2809       <h2 id="rfc.section.9.4"><a href="#rfc.section.9.4">9.4</a>&nbsp;Security Considerations for CONNECT
     3680      <h2 id="rfc.section.13.4"><a href="#rfc.section.13.4">13.4</a>&nbsp;Security Considerations for CONNECT
    28103681      </h2>
    2811       <p id="rfc.section.9.4.p.1">Since tunneled data is opaque to the proxy, there are additional risks to tunneling to other well-known or reserved ports.
     3682      <p id="rfc.section.13.4.p.1">Since tunneled data is opaque to the proxy, there are additional risks to tunneling to other well-known or reserved ports.
    28123683         A HTTP client CONNECTing to port 25 could relay spam via SMTP, for example. As such, proxies <em class="bcp14">SHOULD</em> restrict CONNECT access to a small number of known ports.
    28133684      </p>
    2814       <h1 id="rfc.section.10"><a href="#rfc.section.10">10.</a>&nbsp;<a id="acks" href="#acks">Acknowledgments</a></h1>
    2815       <p id="rfc.section.10.p.1">See <a href="p1-messaging.html#acks" title="Acknowledgments">Section 9</a> of <a href="#Part1" id="rfc.xref.Part1.42"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>.
    2816       </p>
    2817       <h1 id="rfc.references"><a id="rfc.section.11" href="#rfc.section.11">11.</a> References
     3685      <h2 id="rfc.section.13.5"><a href="#rfc.section.13.5">13.5</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>
     3686      <p id="rfc.section.13.5.p.1">Accept header fields can reveal information about the user to all servers which are accessed. The Accept-Language header field
     3687         in particular can reveal information the user would consider to be of a private nature, because the understanding of particular
     3688         languages is often strongly correlated to the membership of a particular ethnic group. User agents which offer the option
     3689         to configure the contents of an Accept-Language header field to be sent in every request are strongly encouraged to let the
     3690         configuration process include a message which makes the user aware of the loss of privacy involved.
     3691      </p>
     3692      <p id="rfc.section.13.5.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
     3693         by default, and to ask the user whether or not to start sending Accept-Language header fields to a server if it detects, by
     3694         looking for any Vary header fields generated by the server, that such sending could improve the quality of service.
     3695      </p>
     3696      <p id="rfc.section.13.5.p.3">Elaborate user-customized accept header fields sent in every request, in particular if these include quality values, can be
     3697         used by servers as relatively reliable and long-lived user identifiers. Such user identifiers would allow content providers
     3698         to do click-trail tracking, and would allow collaborating content providers to match cross-server click-trails or form submissions
     3699         of individual users. Note that for many users not behind a proxy, the network address of the host running the user agent will
     3700         also serve as a long-lived user identifier. In environments where proxies are used to enhance privacy, user agents ought to
     3701         be conservative in offering accept header configuration options to end users. As an extreme privacy measure, proxies could
     3702         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.
     3703      </p>
     3704      <h1 id="rfc.section.14"><a href="#rfc.section.14">14.</a>&nbsp;<a id="acks" href="#acks">Acknowledgments</a></h1>
     3705      <p id="rfc.section.14.p.1">See <a href="p1-messaging.html#acks" title="Acknowledgments">Section 9</a> of <a href="#Part1" id="rfc.xref.Part1.53"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>.
     3706      </p>
     3707      <h1 id="rfc.references"><a id="rfc.section.15" href="#rfc.section.15">15.</a> References
    28183708      </h1>
    2819       <h2 id="rfc.references.1"><a href="#rfc.section.11.1" id="rfc.section.11.1">11.1</a> Normative References
     3709      <h2 id="rfc.references.1"><a href="#rfc.section.15.1" id="rfc.section.15.1">15.1</a> Normative References
    28203710      </h2>
    2821       <table>                 
     3711      <table>                                 
    28223712         <tr>
    28233713            <td class="reference"><b id="Part1">[Part1]</b></td>
    28243714            <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p1-messaging-latest">HTTP/1.1, part 1: URIs, Connections, and Message Parsing</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p1-messaging-latest (work in progress), March&nbsp;2012.
    2825             </td>
    2826          </tr>
    2827          <tr>
    2828             <td class="reference"><b id="Part3">[Part3]</b></td>
    2829             <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p3-payload-latest">HTTP/1.1, part 3: Message Payload and Content Negotiation</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p3-payload-latest (work in progress), March&nbsp;2012.
    28303715            </td>
    28313716         </tr>
     
    28513736         </tr>
    28523737         <tr>
     3738            <td class="reference"><b id="RFC1950">[RFC1950]</b></td>
     3739            <td class="top"><a href="mailto:ghost@aladdin.com" title="Aladdin Enterprises">Deutsch, L.</a> and J-L. Gailly, “<a href="http://tools.ietf.org/html/rfc1950">ZLIB Compressed Data Format Specification version 3.3</a>”, RFC&nbsp;1950, May&nbsp;1996.
     3740            </td>
     3741         </tr>
     3742         <tr>
     3743            <td class="reference"><b id="RFC1951">[RFC1951]</b></td>
     3744            <td class="top"><a href="mailto:ghost@aladdin.com" title="Aladdin Enterprises">Deutsch, P.</a>, “<a href="http://tools.ietf.org/html/rfc1951">DEFLATE Compressed Data Format Specification version 1.3</a>”, RFC&nbsp;1951, May&nbsp;1996.
     3745            </td>
     3746         </tr>
     3747         <tr>
     3748            <td class="reference"><b id="RFC1952">[RFC1952]</b></td>
     3749            <td class="top"><a href="mailto:ghost@aladdin.com" title="Aladdin Enterprises">Deutsch, P.</a>, <a href="mailto:gzip@prep.ai.mit.edu">Gailly, J-L.</a>, <a href="mailto:madler@alumni.caltech.edu">Adler, M.</a>, <a href="mailto:ghost@aladdin.com">Deutsch, L.</a>, and <a href="mailto:randeg@alumni.rpi.edu">G. Randers-Pehrson</a>, “<a href="http://tools.ietf.org/html/rfc1952">GZIP file format specification version 4.3</a>”, RFC&nbsp;1952, May&nbsp;1996.
     3750            </td>
     3751         </tr>
     3752         <tr>
     3753            <td class="reference"><b id="RFC2045">[RFC2045]</b></td>
     3754            <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.
     3755            </td>
     3756         </tr>
     3757         <tr>
     3758            <td class="reference"><b id="RFC2046">[RFC2046]</b></td>
     3759            <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.
     3760            </td>
     3761         </tr>
     3762         <tr>
    28533763            <td class="reference"><b id="RFC2119">[RFC2119]</b></td>
    28543764            <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.
     3765            </td>
     3766         </tr>
     3767         <tr>
     3768            <td class="reference"><b id="RFC2295">[RFC2295]</b></td>
     3769            <td class="top"><a href="mailto:koen@win.tue.nl" title="Technische Universiteit Eindhoven">Holtman, K.</a> and <a href="mailto:mutz@hpl.hp.com" title="Hewlett-Packard Company">A. Mutz</a>, “<a href="http://tools.ietf.org/html/rfc2295">Transparent Content Negotiation in HTTP</a>”, RFC&nbsp;2295, March&nbsp;1998.
    28553770            </td>
    28563771         </tr>
     
    28613776         </tr>
    28623777         <tr>
     3778            <td class="reference"><b id="RFC4288">[RFC4288]</b></td>
     3779            <td class="top"><a href="mailto:ned.freed@mrochek.com" title="Sun Microsystems">Freed, N.</a> and <a href="mailto:klensin+ietf@jck.com">J. Klensin</a>, “<a href="http://tools.ietf.org/html/rfc4288">Media Type Specifications and Registration Procedures</a>”, BCP&nbsp;13, RFC&nbsp;4288, December&nbsp;2005.
     3780            </td>
     3781         </tr>
     3782         <tr>
     3783            <td class="reference"><b id="RFC4647">[RFC4647]</b></td>
     3784            <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.
     3785            </td>
     3786         </tr>
     3787         <tr>
    28633788            <td class="reference"><b id="RFC5234">[RFC5234]</b></td>
    28643789            <td class="top"><a href="mailto:dcrocker@bbiw.net" title="Brandenburg InternetWorking">Crocker, D., Ed.</a> and <a href="mailto:paul.overell@thus.net" title="THUS plc.">P. Overell</a>, “<a href="http://tools.ietf.org/html/rfc5234">Augmented BNF for Syntax Specifications: ABNF</a>”, STD&nbsp;68, RFC&nbsp;5234, January&nbsp;2008.
    28653790            </td>
    28663791         </tr>
     3792         <tr>
     3793            <td class="reference"><b id="RFC5646">[RFC5646]</b></td>
     3794            <td class="top"><a href="mailto:addison@inter-locale.com" title="Lab126">Phillips, A., Ed.</a> and <a href="mailto:mark.davis@google.com" title="Google">M. Davis, Ed.</a>, “<a href="http://tools.ietf.org/html/rfc5646">Tags for Identifying Languages</a>”, BCP&nbsp;47, RFC&nbsp;5646, September&nbsp;2009.
     3795            </td>
     3796         </tr>
    28673797      </table>
    2868       <h2 id="rfc.references.2"><a href="#rfc.section.11.2" id="rfc.section.11.2">11.2</a> Informative References
     3798      <h2 id="rfc.references.2"><a href="#rfc.section.15.2" id="rfc.section.15.2">15.2</a> Informative References
    28693799      </h2>
    2870       <table>                     
     3800      <table>                                     
    28713801         <tr>
    28723802            <td class="reference"><b id="RFC1123">[RFC1123]</b></td>
     
    28803810         </tr>
    28813811         <tr>
     3812            <td class="reference"><b id="RFC2049">[RFC2049]</b></td>
     3813            <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.
     3814            </td>
     3815         </tr>
     3816         <tr>
    28823817            <td class="reference"><b id="RFC2068">[RFC2068]</b></td>
    28833818            <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.
     3819            </td>
     3820         </tr>
     3821         <tr>
     3822            <td class="reference"><b id="RFC2076">[RFC2076]</b></td>
     3823            <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.
     3824            </td>
     3825         </tr>
     3826         <tr>
     3827            <td class="reference"><b id="RFC2277">[RFC2277]</b></td>
     3828            <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.
     3829            </td>
     3830         </tr>
     3831         <tr>
     3832            <td class="reference"><b id="RFC2388">[RFC2388]</b></td>
     3833            <td class="top"><a href="mailto:masinter@parc.xerox.com" title="Xerox Palo Alto Research Center">Masinter, L.</a>, “<a href="http://tools.ietf.org/html/rfc2388">Returning Values from Forms: multipart/form-data</a>”, RFC&nbsp;2388, August&nbsp;1998.
     3834            </td>
     3835         </tr>
     3836         <tr>
     3837            <td class="reference"><b id="RFC2557">[RFC2557]</b></td>
     3838            <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.
    28843839            </td>
    28853840         </tr>
     
    28923847            <td class="reference"><b id="RFC2817">[RFC2817]</b></td>
    28933848            <td class="top"><a href="mailto:rohit@4K-associates.com" title="4K Associates / UC Irvine">Khare, R.</a> and <a href="mailto:lawrence@agranat.com" title="Agranat Systems, Inc.">S. Lawrence</a>, “<a href="http://tools.ietf.org/html/rfc2817">Upgrading to TLS Within HTTP/1.1</a>”, RFC&nbsp;2817, May&nbsp;2000.
     3849            </td>
     3850         </tr>
     3851         <tr>
     3852            <td class="reference"><b id="RFC3629">[RFC3629]</b></td>
     3853            <td class="top"><a href="mailto:fyergeau@alis.com" title="Alis Technologies">Yergeau, F.</a>, “<a href="http://tools.ietf.org/html/rfc3629">UTF-8, a transformation format of ISO 10646</a>”, STD&nbsp;63, RFC&nbsp;3629, November&nbsp;2003.
    28943854            </td>
    28953855         </tr>
     
    29203880         </tr>
    29213881         <tr>
     3882            <td class="reference"><b id="RFC6151">[RFC6151]</b></td>
     3883            <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.
     3884            </td>
     3885         </tr>
     3886         <tr>
     3887            <td class="reference"><b id="RFC6266">[RFC6266]</b></td>
     3888            <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.
     3889            </td>
     3890         </tr>
     3891         <tr>
    29223892            <td class="reference"><b id="draft-reschke-http-status-308">[draft-reschke-http-status-308]</b></td>
    29233893            <td class="top"><a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">Reschke, J.</a>, “<a href="http://tools.ietf.org/html/draft-reschke-http-status-308-07">The Hypertext Transfer Protocol (HTTP) Status Code 308 (Permanent Redirect)</a>”, Internet-Draft&nbsp;draft-reschke-http-status-308-07 (work in progress), March&nbsp;2012.
     
    29373907               <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>
    29383908      </div>
    2939       <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>
    2940       <p id="rfc.section.A.p.1">Clarify definition of POST. (<a href="#POST" id="rfc.xref.POST.2" title="POST">Section&nbsp;2.3.4</a>)
    2941       </p>
    2942       <p id="rfc.section.A.p.2">Remove requirement to handle all Content-* header fields; ban use of Content-Range with PUT. (<a href="#PUT" id="rfc.xref.PUT.2" title="PUT">Section&nbsp;2.3.5</a>)
    2943       </p>
    2944       <p id="rfc.section.A.p.3">Take over definition of CONNECT method from <a href="#RFC2817" id="rfc.xref.RFC2817.2"><cite title="Upgrading to TLS Within HTTP/1.1">[RFC2817]</cite></a>. (<a href="#CONNECT" id="rfc.xref.CONNECT.2" title="CONNECT">Section&nbsp;2.3.8</a>)
    2945       </p>
    2946       <p id="rfc.section.A.p.4">This document takes over the Status Code Registry, previously defined in <a href="http://tools.ietf.org/html/rfc2817#section-7.1">Section 7.1</a> of <a href="#RFC2817" id="rfc.xref.RFC2817.3"><cite title="Upgrading to TLS Within HTTP/1.1">[RFC2817]</cite></a>. (<a href="#status.code.registry" title="Status Code Registry">Section&nbsp;4.2</a>)
    2947       </p>
    2948       <p id="rfc.section.A.p.5">Broadened the definition of 203 (Non-Authoritative Information) to include cases of payload transformations as well. (<a href="#status.203" id="rfc.xref.status.203.3" title="203 Non-Authoritative Information">Section&nbsp;4.4.4</a>)
    2949       </p>
    2950       <p id="rfc.section.A.p.6">Status codes 301, 302, and 307: removed the normative requirements on both response payloads and user interaction. (<a href="#status.3xx" title="Redirection 3xx">Section&nbsp;4.5</a>)
    2951       </p>
    2952       <p id="rfc.section.A.p.7">Failed to consider that there are many other request methods that are safe to automatically redirect, and further that the
     3909      <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>
     3910      <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.5"><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,
     3911         RFC 2045 discusses mail, and HTTP has a few features that are different from those described in MIME. These differences were
     3912         carefully chosen to optimize performance over binary connections, to allow greater freedom in the use of new media types,
     3913         to make date comparisons easier, and to acknowledge the practice of some early HTTP servers and clients.
     3914      </p>
     3915      <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
     3916         to HTTP also need to be aware of the differences because some conversions might be required.
     3917      </p>
     3918      <div id="rfc.iref.m.10"></div>
     3919      <div id="rfc.iref.h.20"></div>
     3920      <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>
     3921      <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.
     3922         Use of the MIME-Version header field indicates that the message is in full conformance with the MIME protocol (as defined
     3923         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
     3924         MIME environments.
     3925      </p>
     3926      <div id="rfc.figure.u.64"></div><pre class="inline"><span id="rfc.iref.g.62"></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>
     3927</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
     3928         document and not the MIME specification.
     3929      </p>
     3930      <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>
     3931      <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;7.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
     3932         break sequences. HTTP allows CRLF, bare CR, and bare LF to indicate a line break within text content when a message is transmitted
     3933         over HTTP.
     3934      </p>
     3935      <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;7.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
     3936         a Content-Encoding and by the fact that HTTP allows the use of some character encodings which do not use octets 13 and 10
     3937         to represent CR and LF, respectively, as is the case for some multi-byte character encodings.
     3938      </p>
     3939      <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
     3940         canonical form. Therefore, the canonical form is recommended for any content that uses such checksums in HTTP.
     3941      </p>
     3942      <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>
     3943      <p id="rfc.section.A.3.p.1">HTTP/1.1 uses a restricted set of date formats (<a href="#http.date" title="Date/Time Formats">Section&nbsp;6.1</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.
     3944      </p>
     3945      <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>
     3946      <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
     3947         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
     3948         experimental applications of Content-Type for Internet mail have used a media-type parameter of ";conversions=&lt;content-coding&gt;"
     3949         to perform a function equivalent to Content-Encoding. However, this parameter is not part of the MIME standards).
     3950      </p>
     3951      <div id="rfc.iref.c.11"></div>
     3952      <div id="rfc.iref.h.21"></div>
     3953      <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>
     3954      <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.
     3955      </p>
     3956      <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
     3957         format and encoding for safe transport on that protocol, where "safe transport" is defined by the limitations of the protocol
     3958         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
     3959         the destination protocol.
     3960      </p>
     3961      <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>
     3962      <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.54"><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.
     3963      </p>
     3964      <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>
     3965      <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
     3966         fold long lines. MHTML messages being transported by HTTP follow all conventions of MHTML, including line length limitations
     3967         and folding, canonicalization, etc., since HTTP transports all message-bodies as payload (see <a href="#multipart.types" title="Multipart Types">Section&nbsp;7.3.2</a>) and does not interpret the content or any MIME header lines that might be contained therein.
     3968      </p>
     3969      <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a>&nbsp;<a id="additional.features" href="#additional.features">Additional Features</a></h1>
     3970      <p id="rfc.section.B.p.1"> <a href="#RFC1945" id="rfc.xref.RFC1945.2"><cite title="Hypertext Transfer Protocol -- HTTP/1.0">[RFC1945]</cite></a> and <a href="#RFC2068" id="rfc.xref.RFC2068.3"><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
     3971         applications. Implementors are advised to be aware of these features, but cannot rely upon their presence in, or interoperability
     3972         with, other HTTP/1.1 applications. Some of these describe proposed experimental features, and some describe features that
     3973         experimental deployment found lacking that are now addressed in the base HTTP/1.1 specification.
     3974      </p>
     3975      <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>).
     3976      </p>
     3977      <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>
     3978      <p id="rfc.section.C.p.1">Clarify definition of POST. (<a href="#POST" id="rfc.xref.POST.2" title="POST">Section&nbsp;2.3.4</a>)
     3979      </p>
     3980      <p id="rfc.section.C.p.2">Remove requirement to handle all Content-* header fields; ban use of Content-Range with PUT. (<a href="#PUT" id="rfc.xref.PUT.2" title="PUT">Section&nbsp;2.3.5</a>)
     3981      </p>
     3982      <p id="rfc.section.C.p.3">Take over definition of CONNECT method from <a href="#RFC2817" id="rfc.xref.RFC2817.2"><cite title="Upgrading to TLS Within HTTP/1.1">[RFC2817]</cite></a>. (<a href="#CONNECT" id="rfc.xref.CONNECT.2" title="CONNECT">Section&nbsp;2.3.8</a>)
     3983      </p>
     3984      <p id="rfc.section.C.p.4">This document takes over the Status Code Registry, previously defined in <a href="http://tools.ietf.org/html/rfc2817#section-7.1">Section 7.1</a> of <a href="#RFC2817" id="rfc.xref.RFC2817.3"><cite title="Upgrading to TLS Within HTTP/1.1">[RFC2817]</cite></a>. (<a href="#status.code.registry" title="Status Code Registry">Section&nbsp;4.2</a>)
     3985      </p>
     3986      <p id="rfc.section.C.p.5">Broadened the definition of 203 (Non-Authoritative Information) to include cases of payload transformations as well. (<a href="#status.203" id="rfc.xref.status.203.3" title="203 Non-Authoritative Information">Section&nbsp;4.4.4</a>)
     3987      </p>
     3988      <p id="rfc.section.C.p.6">Status codes 301, 302, and 307: removed the normative requirements on both response payloads and user interaction. (<a href="#status.3xx" title="Redirection 3xx">Section&nbsp;4.5</a>)
     3989      </p>
     3990      <p id="rfc.section.C.p.7">Failed to consider that there are many other request methods that are safe to automatically redirect, and further that the
    29533991         user agent is able to make that determination based on the request method semantics. Furthermore, allow user agents to rewrite
    29543992         the method from POST to GET for status codes 301 and 302. (Sections <a href="#status.301" id="rfc.xref.status.301.3" title="301 Moved Permanently">4.5.2</a>, <a href="#status.302" id="rfc.xref.status.302.3" title="302 Found">4.5.3</a> and <a href="#status.307" id="rfc.xref.status.307.3" title="307 Temporary Redirect">4.5.7</a>)
    29553993      </p>
    2956       <p id="rfc.section.A.p.8">Deprecate 305 Use Proxy status code, because user agents did not implement it. It used to indicate that the target resource
     3994      <p id="rfc.section.C.p.8">Deprecate 305 Use Proxy status code, because user agents did not implement it. It used to indicate that the target resource
    29573995         needs to be accessed through the proxy given by the Location field. The Location field gave the URI of the proxy. The recipient
    29583996         was expected to repeat this single request via the proxy. (<a href="#status.305" id="rfc.xref.status.305.3" title="305 Use Proxy">Section&nbsp;4.5.5</a>)
    29593997      </p>
    2960       <p id="rfc.section.A.p.9">Define status 426 (Upgrade Required) (this was incorporated from <a href="#RFC2817" id="rfc.xref.RFC2817.4"><cite title="Upgrading to TLS Within HTTP/1.1">[RFC2817]</cite></a>). (<a href="#status.426" id="rfc.xref.status.426.3" title="426 Upgrade Required">Section&nbsp;4.6.15</a>)
    2961       </p>
    2962       <p id="rfc.section.A.p.10">Change ABNF productions for header fields to only define the field value. (<a href="#header.field.definitions" title="Header Field Definitions">Section&nbsp;7</a>)
    2963       </p>
    2964       <p id="rfc.section.A.p.11">Reclassify "Allow" as response header field, removing the option to specify it in a PUT request. Relax the server requirement
    2965          on the contents of the Allow header field and remove requirement on clients to always trust the header field value. (<a href="#header.allow" id="rfc.xref.header.allow.4" title="Allow">Section&nbsp;7.1</a>)
    2966       </p>
    2967       <p id="rfc.section.A.p.12">The ABNF for the Expect header field has been both fixed (allowing parameters for value-less expectations as well) and simplified
    2968          (allowing trailing semicolons after "100-continue" when they were invalid before). (<a href="#header.expect" id="rfc.xref.header.expect.4" title="Expect">Section&nbsp;7.3</a>)
    2969       </p>
    2970       <p id="rfc.section.A.p.13">Correct syntax of Location header field to allow URI references (including relative references and fragments), as referred
     3998      <p id="rfc.section.C.p.9">Define status 426 (Upgrade Required) (this was incorporated from <a href="#RFC2817" id="rfc.xref.RFC2817.4"><cite title="Upgrading to TLS Within HTTP/1.1">[RFC2817]</cite></a>). (<a href="#status.426" id="rfc.xref.status.426.3" title="426 Upgrade Required">Section&nbsp;4.6.15</a>)
     3999      </p>
     4000      <p id="rfc.section.C.p.10">Change ABNF productions for header fields to only define the field value. (<a href="#header.field.definitions" title="Header Field Definitions">Section&nbsp;11</a>)
     4001      </p>
     4002      <p id="rfc.section.C.p.11">Reclassify "Allow" as response header field, removing the option to specify it in a PUT request. Relax the server requirement
     4003         on the contents of the Allow header field and remove requirement on clients to always trust the header field value. (<a href="#header.allow" id="rfc.xref.header.allow.4" title="Allow">Section&nbsp;11.1</a>)
     4004      </p>
     4005      <p id="rfc.section.C.p.12">The ABNF for the Expect header field has been both fixed (allowing parameters for value-less expectations as well) and simplified
     4006         (allowing trailing semicolons after "100-continue" when they were invalid before). (<a href="#header.expect" id="rfc.xref.header.expect.4" title="Expect">Section&nbsp;11.3</a>)
     4007      </p>
     4008      <p id="rfc.section.C.p.13">Correct syntax of Location header field to allow URI references (including relative references and fragments), as referred
    29714009         symbol "absoluteURI" wasn't what was expected, and add some clarifications as to when use of fragments would not be appropriate.
    2972          (<a href="#header.location" id="rfc.xref.header.location.5" title="Location">Section&nbsp;7.5</a>)
    2973       </p>
    2974       <p id="rfc.section.A.p.14">Restrict Max-Forwards header field to OPTIONS and TRACE (previously, extension methods could have used it as well). (<a href="#header.max-forwards" id="rfc.xref.header.max-forwards.5" title="Max-Forwards">Section&nbsp;7.6</a>)
    2975       </p>
    2976       <p id="rfc.section.A.p.15">Allow Referer field value of "about:blank" as alternative to not specifying it. (<a href="#header.referer" id="rfc.xref.header.referer.3" title="Referer">Section&nbsp;7.7</a>)
    2977       </p>
    2978       <p id="rfc.section.A.p.16">In the description of the Server header field, the Via field was described as a SHOULD. The requirement was and is stated
    2979          correctly in the description of the Via header field in <a href="p1-messaging.html#header.via" title="Via">Section 6.2</a> of <a href="#Part1" id="rfc.xref.Part1.43"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>. (<a href="#header.server" id="rfc.xref.header.server.4" title="Server">Section&nbsp;7.9</a>)
    2980       </p>
    2981       <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a>&nbsp;<a id="collected.abnf" href="#collected.abnf">Collected ABNF</a></h1>
    2982       <div id="rfc.figure.u.38"></div> <pre class="inline"><a href="#header.allow" class="smpl">Allow</a> = [ ( "," / method ) *( OWS "," [ OWS method ] ) ]
     4010         (<a href="#header.location" id="rfc.xref.header.location.5" title="Location">Section&nbsp;11.5</a>)
     4011      </p>
     4012      <p id="rfc.section.C.p.14">Restrict Max-Forwards header field to OPTIONS and TRACE (previously, extension methods could have used it as well). (<a href="#header.max-forwards" id="rfc.xref.header.max-forwards.5" title="Max-Forwards">Section&nbsp;11.6</a>)
     4013      </p>
     4014      <p id="rfc.section.C.p.15">Allow Referer field value of "about:blank" as alternative to not specifying it. (<a href="#header.referer" id="rfc.xref.header.referer.3" title="Referer">Section&nbsp;11.7</a>)
     4015      </p>
     4016      <p id="rfc.section.C.p.16">In the description of the Server header field, the Via field was described as a SHOULD. The requirement was and is stated
     4017         correctly in the description of the Via header field in <a href="p1-messaging.html#header.via" title="Via">Section 6.2</a> of <a href="#Part1" id="rfc.xref.Part1.55"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>. (<a href="#header.server" id="rfc.xref.header.server.4" title="Server">Section&nbsp;11.9</a>)
     4018      </p>
     4019      <p id="rfc.section.C.p.17">Clarify contexts that charset is used in. (<a href="#character.sets" title="Character Encodings (charset)">Section&nbsp;7.1</a>)
     4020      </p>
     4021      <p id="rfc.section.C.p.18">Registration of Content Codings now requires IETF Review (<a href="#content.coding.registry" title="Content Coding Registry">Section&nbsp;7.2.1</a>)
     4022      </p>
     4023      <p id="rfc.section.C.p.19">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;7.3.1</a>)
     4024      </p>
     4025      <p id="rfc.section.C.p.20">Change ABNF productions for header fields to only define the field value. (<a href="#header.field.definitions" title="Header Field Definitions">Section&nbsp;11</a>)
     4026      </p>
     4027      <p id="rfc.section.C.p.21">Remove definition of Content-MD5 header field because it was inconsistently implemented with respect to partial responses,
     4028         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;11</a>)
     4029      </p>
     4030      <p id="rfc.section.C.p.22">Remove ISO-8859-1 special-casing in Accept-Charset. (<a href="#header.accept-charset" id="rfc.xref.header.accept-charset.4" title="Accept-Charset">Section&nbsp;11.12</a>)
     4031      </p>
     4032      <p id="rfc.section.C.p.23">Remove base URI setting semantics for Content-Location due to poor implementation support, which was caused by too many broken
     4033         servers emitting bogus Content-Location header fields, and also the potentially undesirable effect of potentially breaking
     4034         relative links in content-negotiated resources. (<a href="#header.content-location" id="rfc.xref.header.content-location.5" title="Content-Location">Section&nbsp;11.17</a>)
     4035      </p>
     4036      <p id="rfc.section.C.p.24">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>)
     4037      </p>
     4038      <p id="rfc.section.C.p.25">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>)
     4039      </p>
     4040      <h1 id="rfc.section.D"><a href="#rfc.section.D">D.</a>&nbsp;<a id="collected.abnf" href="#collected.abnf">Collected ABNF</a></h1>
     4041      <div id="rfc.figure.u.65"></div> <pre class="inline"><a href="#header.accept" class="smpl">Accept</a> = [ ( "," / ( media-range [ accept-params ] ) ) *( OWS "," [
     4042 OWS media-range [ accept-params ] ] ) ]
     4043<a href="#header.accept-charset" class="smpl">Accept-Charset</a> = *( "," OWS ) ( charset / "*" ) [ OWS ";" OWS "q="
     4044 qvalue ] *( OWS "," [ OWS ( charset / "*" ) [ OWS ";" OWS "q="
     4045 qvalue ] ] )
     4046<a href="#header.accept-encoding" class="smpl">Accept-Encoding</a> = [ ( "," / ( codings [ OWS ";" OWS "q=" qvalue ] ) )
     4047 *( OWS "," [ OWS codings [ OWS ";" OWS "q=" qvalue ] ] ) ]
     4048<a href="#header.accept-language" class="smpl">Accept-Language</a> = *( "," OWS ) language-range [ OWS ";" OWS "q="
     4049 qvalue ] *( OWS "," [ OWS language-range [ OWS ";" OWS "q=" qvalue ]
     4050 ] )
     4051<a href="#header.allow" class="smpl">Allow</a> = [ ( "," / method ) *( OWS "," [ OWS method ] ) ]
    29834052
    29844053<a href="#core.rules" class="smpl">BWS</a> = &lt;BWS, defined in [Part1], Section 3.2.1&gt;
    29854054
     4055<a href="#header.content-encoding" class="smpl">Content-Encoding</a> = *( "," OWS ) content-coding *( OWS "," [ OWS
     4056 content-coding ] )
     4057<a href="#header.content-language" class="smpl">Content-Language</a> = *( "," OWS ) language-tag *( OWS "," [ OWS
     4058 language-tag ] )
     4059<a href="#header.content-location" class="smpl">Content-Location</a> = absolute-URI / partial-URI
     4060<a href="#header.content-type" class="smpl">Content-Type</a> = media-type
     4061
    29864062<a href="#header.date" class="smpl">Date</a> = HTTP-date
    29874063
     
    29964072<a href="#header.location" class="smpl">Location</a> = URI-reference
    29974073
     4074<a href="#mime-version" class="smpl">MIME-Version</a> = 1*DIGIT "." 1*DIGIT
     4075
    29984076<a href="#header.max-forwards" class="smpl">Max-Forwards</a> = 1*DIGIT
    29994077
     
    30014079
    30024080<a href="#core.rules" class="smpl">RWS</a> = &lt;RWS, defined in [Part1], Section 3.2.1&gt;
     4081
    30034082<a href="#header.referer" class="smpl">Referer</a> = absolute-URI / partial-URI
    30044083<a href="#header.retry-after" class="smpl">Retry-After</a> = HTTP-date / delta-seconds
     
    30074086
    30084087<a href="#abnf.dependencies" class="smpl">URI-reference</a> = &lt;URI-reference, defined in [Part1], Section 2.7&gt;
     4088
    30094089<a href="#header.user-agent" class="smpl">User-Agent</a> = product *( RWS ( product / comment ) )
    30104090
    30114091<a href="#abnf.dependencies" class="smpl">absolute-URI</a> = &lt;absolute-URI, defined in [Part1], Section 2.7&gt;
     4092
     4093<a href="#header.accept" class="smpl">accept-ext</a> = OWS ";" OWS token [ "=" word ]
     4094<a href="#header.accept" class="smpl">accept-params</a> = OWS ";" OWS "q=" qvalue *accept-ext
     4095
    30124096<a href="#obsolete.date.formats" class="smpl">asctime-date</a> = day-name SP date3 SP time-of-day SP year
     4097<a href="#rule.parameter" class="smpl">attribute</a> = token
     4098
     4099<a href="#rule.charset" class="smpl">charset</a> = token
     4100
     4101<a href="#header.accept-encoding" class="smpl">codings</a> = content-coding / "identity" / "*"
    30134102
    30144103<a href="#abnf.dependencies" class="smpl">comment</a> = &lt;comment, defined in [Part1], Section 3.2.4&gt;
     4104<a href="#content.codings" class="smpl">content-coding</a> = token
    30154105
    30164106<a href="#obsolete.date.formats" class="smpl">date1</a> = day SP month SP year
     4107
    30174108<a href="#obsolete.date.formats" class="smpl">date2</a> = day "-" month "-" 2DIGIT
     4109
    30184110<a href="#obsolete.date.formats" class="smpl">date3</a> = month SP ( 2DIGIT / ( SP DIGIT ) )
    30194111<a href="#preferred.date.format" class="smpl">day</a> = 2DIGIT
     
    30354127
    30364128<a href="#header.expect" class="smpl">expect-name</a> = token
     4129
    30374130<a href="#header.expect" class="smpl">expect-param</a> = expect-name [ BWS "=" BWS expect-value ]
     4131
    30384132<a href="#header.expect" class="smpl">expect-value</a> = token / quoted-string
    30394133<a href="#header.expect" class="smpl">expectation</a> = expect-name [ BWS "=" BWS expect-value ] *( OWS ";" [
     
    30424136<a href="#preferred.date.format" class="smpl">hour</a> = 2DIGIT
    30434137
     4138<a href="#header.accept-language" class="smpl">language-range</a> = &lt;language-range, defined in [RFC4647], Section 2.1&gt;
     4139
     4140<a href="#language.tags" class="smpl">language-tag</a> = &lt;Language-Tag, defined in [RFC5646], Section 2.1&gt;
     4141
    30444142<a href="#header.from" class="smpl">mailbox</a> = &lt;mailbox, defined in [RFC5322], Section 3.4&gt;
     4143
     4144<a href="#header.accept" class="smpl">media-range</a> = ( "*/*" / ( type "/*" ) / ( type "/" subtype ) ) *( OWS
     4145 ";" OWS parameter )
     4146<a href="#media.types" class="smpl">media-type</a> = type "/" subtype *( OWS ";" OWS parameter )
    30454147<a href="#methods" class="smpl">method</a> = token
    30464148<a href="#preferred.date.format" class="smpl">minute</a> = 2DIGIT
     
    30594161
    30604162<a href="#obsolete.date.formats" class="smpl">obs-date</a> = rfc850-date / asctime-date
     4163
    30614164<a href="#core.rules" class="smpl">obs-text</a> = &lt;obs-text, defined in [Part1], Section 3.2.4&gt;
    30624165
     4166<a href="#rule.parameter" class="smpl">parameter</a> = attribute "=" value
     4167
    30634168<a href="#abnf.dependencies" class="smpl">partial-URI</a> = &lt;partial-URI, defined in [Part1], Section 2.7&gt;
     4169
    30644170<a href="#product.tokens" class="smpl">product</a> = token [ "/" product-version ]
    30654171<a href="#product.tokens" class="smpl">product-version</a> = token
     
    30684174
    30694175<a href="#status.code.and.reason.phrase" class="smpl">reason-phrase</a> = *( HTAB / SP / VCHAR / obs-text )
     4176
    30704177<a href="#preferred.date.format" class="smpl">rfc1123-date</a> = day-name "," SP date1 SP time-of-day SP GMT
     4178
    30714179<a href="#obsolete.date.formats" class="smpl">rfc850-date</a> = day-name-l "," SP date2 SP time-of-day SP GMT
    30724180
    30734181<a href="#preferred.date.format" class="smpl">second</a> = 2DIGIT
     4182
    30744183<a href="#status.code.and.reason.phrase" class="smpl">status-code</a> = 3DIGIT
    30754184
     4185<a href="#media.types" class="smpl">subtype</a> = token
     4186
    30764187<a href="#preferred.date.format" class="smpl">time-of-day</a> = hour ":" minute ":" second
     4188
    30774189<a href="#core.rules" class="smpl">token</a> = &lt;token, defined in [Part1], Section 3.2.4&gt;
    30784190
     4191<a href="#media.types" class="smpl">type</a> = token
     4192
     4193<a href="#rule.parameter" class="smpl">value</a> = word
     4194
    30794195<a href="#preferred.date.format" class="smpl">year</a> = 4DIGIT
    3080 </pre> <div id="rfc.figure.u.39"></div>
    3081       <p>ABNF diagnostics:</p><pre class="inline">; Allow defined but not used
     4196</pre> <div id="rfc.figure.u.66"></div>
     4197      <p>ABNF diagnostics:</p><pre class="inline">; qvalue UNDEFINED
     4198; word UNDEFINED
     4199; Accept defined but not used
     4200; Accept-Charset defined but not used
     4201; Accept-Encoding defined but not used
     4202; Accept-Language defined but not used
     4203; Allow defined but not used
     4204; Content-Encoding defined but not used
     4205; Content-Language defined but not used
     4206; Content-Location defined but not used
     4207; Content-Type defined but not used
    30824208; Date defined but not used
    30834209; Expect defined but not used
    30844210; From defined but not used
    30854211; Location defined but not used
     4212; MIME-Version defined but not used
    30864213; Max-Forwards defined but not used
    30874214; Referer defined but not used
     
    30914218; reason-phrase defined but not used
    30924219; status-code defined but not used
    3093 </pre><h1 id="rfc.section.C"><a href="#rfc.section.C">C.</a>&nbsp;<a id="change.log" href="#change.log">Change Log (to be removed by RFC Editor before publication)</a></h1>
    3094       <h2 id="rfc.section.C.1"><a href="#rfc.section.C.1">C.1</a>&nbsp;Since RFC 2616
     4220</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>
     4221      <h2 id="rfc.section.E.1"><a href="#rfc.section.E.1">E.1</a>&nbsp;Since RFC 2616
    30954222      </h2>
    3096       <p id="rfc.section.C.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>.
    3097       </p>
    3098       <h2 id="rfc.section.C.2"><a href="#rfc.section.C.2">C.2</a>&nbsp;Since draft-ietf-httpbis-p2-semantics-00
     4223      <p id="rfc.section.E.1.p.1">Extracted relevant partitions from <a href="#RFC2616" id="rfc.xref.RFC2616.4"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>.
     4224      </p>
     4225      <h2 id="rfc.section.E.2"><a href="#rfc.section.E.2">E.2</a>&nbsp;Since draft-ietf-httpbis-p2-semantics-00
    30994226      </h2>
    3100       <p id="rfc.section.C.2.p.1">Closed issues: </p>
     4227      <p id="rfc.section.E.2.p.1">Closed issues: </p>
    31014228      <ul>
    31024229         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/5">http://tools.ietf.org/wg/httpbis/trac/ticket/5</a>&gt;: "Via is a MUST" (&lt;<a href="http://purl.org/NET/http-errata#via-must">http://purl.org/NET/http-errata#via-must</a>&gt;)
     
    31174244         </li>
    31184245      </ul>
    3119       <p id="rfc.section.C.2.p.2">Other changes: </p>
    3120       <ul>
    3121          <li>Move definitions of 304 and 412 condition codes to <a href="#Part4" id="rfc.xref.Part4.11"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>
    3122          </li>
    3123       </ul>
    3124       <h2 id="rfc.section.C.3"><a href="#rfc.section.C.3">C.3</a>&nbsp;Since draft-ietf-httpbis-p2-semantics-01
     4246      <p id="rfc.section.E.2.p.2">Other changes: </p>
     4247      <ul>
     4248         <li>Move definitions of 304 and 412 condition codes to <a href="#Part4" id="rfc.xref.Part4.13"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>
     4249         </li>
     4250      </ul>
     4251      <h2 id="rfc.section.E.3"><a href="#rfc.section.E.3">E.3</a>&nbsp;Since draft-ietf-httpbis-p3-payload-00
    31254252      </h2>
    3126       <p id="rfc.section.C.3.p.1">Closed issues: </p>
     4253      <p id="rfc.section.E.3.p.1">Closed issues: </p>
     4254      <ul>
     4255         <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;)
     4256         </li>
     4257         <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;)
     4258         </li>
     4259         <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;)
     4260         </li>
     4261         <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"
     4262         </li>
     4263         <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"
     4264         </li>
     4265         <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"
     4266         </li>
     4267         <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"
     4268         </li>
     4269         <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"
     4270         </li>
     4271         <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"
     4272         </li>
     4273         <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"
     4274         </li>
     4275         <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"
     4276         </li>
     4277      </ul>
     4278      <h2 id="rfc.section.E.4"><a href="#rfc.section.E.4">E.4</a>&nbsp;Since draft-ietf-httpbis-p2-semantics-01
     4279      </h2>
     4280      <p id="rfc.section.E.4.p.1">Closed issues: </p>
    31274281      <ul>
    31284282         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/21">http://tools.ietf.org/wg/httpbis/trac/ticket/21</a>&gt;: "PUT side effects"
     
    31314285         </li>
    31324286      </ul>
    3133       <p id="rfc.section.C.3.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;):
     4287      <p id="rfc.section.E.4.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;):
    31344288      </p>
    31354289      <ul>
     
    31384292         <li>Copy definition of delta-seconds from Part6 instead of referencing it.</li>
    31394293      </ul>
    3140       <h2 id="rfc.section.C.4"><a href="#rfc.section.C.4">C.4</a>&nbsp;<a id="changes.since.02" href="#changes.since.02">Since draft-ietf-httpbis-p2-semantics-02</a></h2>
    3141       <p id="rfc.section.C.4.p.1">Closed issues: </p>
     4294      <h2 id="rfc.section.E.5"><a href="#rfc.section.E.5">E.5</a>&nbsp;Since draft-ietf-httpbis-p3-payload-01
     4295      </h2>
     4296      <p id="rfc.section.E.5.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;):
     4297      </p>
     4298      <ul>
     4299         <li>Add explicit references to BNF syntax and rules imported from other parts of the specification.</li>
     4300      </ul>
     4301      <h2 id="rfc.section.E.6"><a href="#rfc.section.E.6">E.6</a>&nbsp;<a id="changes.since.02" href="#changes.since.02">Since draft-ietf-httpbis-p2-semantics-02</a></h2>
     4302      <p id="rfc.section.E.6.p.1">Closed issues: </p>
    31424303      <ul>
    31434304         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/24">http://tools.ietf.org/wg/httpbis/trac/ticket/24</a>&gt;: "Requiring Allow in 405 responses"
     
    31564317         </li>
    31574318      </ul>
    3158       <p id="rfc.section.C.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;):
     4319      <p id="rfc.section.E.6.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;):
    31594320      </p>
    31604321      <ul>
    31614322         <li>Reference RFC 3984, and update header field registrations for headers defined in this document.</li>
    31624323      </ul>
    3163       <p id="rfc.section.C.4.p.3">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;):
     4324      <p id="rfc.section.E.6.p.3">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;):
    31644325      </p>
    31654326      <ul>
    31664327         <li>Replace string literals when the string really is case-sensitive (method).</li>
    31674328      </ul>
    3168       <h2 id="rfc.section.C.5"><a href="#rfc.section.C.5">C.5</a>&nbsp;<a id="changes.since.03" href="#changes.since.03">Since draft-ietf-httpbis-p2-semantics-03</a></h2>
    3169       <p id="rfc.section.C.5.p.1">Closed issues: </p>
     4329      <h2 id="rfc.section.E.7"><a href="#rfc.section.E.7">E.7</a>&nbsp;<a id="changes.since.3.02" href="#changes.since.3.02">Since draft-ietf-httpbis-p3-payload-02</a></h2>
     4330      <p id="rfc.section.E.7.p.1">Closed issues: </p>
     4331      <ul>
     4332         <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"
     4333         </li>
     4334         <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"
     4335         </li>
     4336         <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"
     4337         </li>
     4338      </ul>
     4339      <p id="rfc.section.E.7.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;):
     4340      </p>
     4341      <ul>
     4342         <li>Reference RFC 3984, and update header field registrations for headers defined in this document.</li>
     4343      </ul>
     4344      <h2 id="rfc.section.E.8"><a href="#rfc.section.E.8">E.8</a>&nbsp;<a id="changes.since.03" href="#changes.since.03">Since draft-ietf-httpbis-p2-semantics-03</a></h2>
     4345      <p id="rfc.section.E.8.p.1">Closed issues: </p>
    31704346      <ul>
    31714347         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/98">http://tools.ietf.org/wg/httpbis/trac/ticket/98</a>&gt;: "OPTIONS request bodies"
     
    31764352         </li>
    31774353      </ul>
    3178       <p id="rfc.section.C.5.p.2">Ongoing work on Method Registry (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/72">http://tools.ietf.org/wg/httpbis/trac/ticket/72</a>&gt;):
     4354      <p id="rfc.section.E.8.p.2">Ongoing work on Method Registry (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/72">http://tools.ietf.org/wg/httpbis/trac/ticket/72</a>&gt;):
    31794355      </p>
    31804356      <ul>
    31814357         <li>Added initial proposal for registration process, plus initial content (non-HTTP/1.1 methods to be added by a separate specification).</li>
    31824358      </ul>
    3183       <h2 id="rfc.section.C.6"><a href="#rfc.section.C.6">C.6</a>&nbsp;<a id="changes.since.04" href="#changes.since.04">Since draft-ietf-httpbis-p2-semantics-04</a></h2>
    3184       <p id="rfc.section.C.6.p.1">Closed issues: </p>
     4359      <h2 id="rfc.section.E.9"><a href="#rfc.section.E.9">E.9</a>&nbsp;<a id="changes.since.3.03" href="#changes.since.3.03">Since draft-ietf-httpbis-p3-payload-03</a></h2>
     4360      <p id="rfc.section.E.9.p.1">Closed issues: </p>
     4361      <ul>
     4362         <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"
     4363         </li>
     4364         <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"
     4365         </li>
     4366         <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"
     4367         </li>
     4368      </ul>
     4369      <p id="rfc.section.E.9.p.2">Other changes: </p>
     4370      <ul>
     4371         <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.
     4372         </li>
     4373      </ul>
     4374      <h2 id="rfc.section.E.10"><a href="#rfc.section.E.10">E.10</a>&nbsp;<a id="changes.since.04" href="#changes.since.04">Since draft-ietf-httpbis-p2-semantics-04</a></h2>
     4375      <p id="rfc.section.E.10.p.1">Closed issues: </p>
    31854376      <ul>
    31864377         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/103">http://tools.ietf.org/wg/httpbis/trac/ticket/103</a>&gt;: "Content-*"
     
    31894380         </li>
    31904381      </ul>
    3191       <p id="rfc.section.C.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;):
     4382      <p id="rfc.section.E.10.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;):
    31924383      </p>
    31934384      <ul>
     
    31964387         <li>Rewrite ABNFs to spell out whitespace rules, factor out header field value format definitions.</li>
    31974388      </ul>
    3198       <h2 id="rfc.section.C.7"><a href="#rfc.section.C.7">C.7</a>&nbsp;<a id="changes.since.05" href="#changes.since.05">Since draft-ietf-httpbis-p2-semantics-05</a></h2>
    3199       <p id="rfc.section.C.7.p.1">Closed issues: </p>
     4389      <h2 id="rfc.section.E.11"><a href="#rfc.section.E.11">E.11</a>&nbsp;<a id="changes.since.3.04" href="#changes.since.3.04">Since draft-ietf-httpbis-p3-payload-04</a></h2>
     4390      <p id="rfc.section.E.11.p.1">Closed issues: </p>
     4391      <ul>
     4392         <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"
     4393         </li>
     4394      </ul>
     4395      <p id="rfc.section.E.11.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;):
     4396      </p>
     4397      <ul>
     4398         <li>Use "/" instead of "|" for alternatives.</li>
     4399         <li>Introduce new ABNF rules for "bad" whitespace ("BWS"), optional whitespace ("OWS") and required whitespace ("RWS").</li>
     4400         <li>Rewrite ABNFs to spell out whitespace rules, factor out header field value format definitions.</li>
     4401      </ul>
     4402      <h2 id="rfc.section.E.12"><a href="#rfc.section.E.12">E.12</a>&nbsp;<a id="changes.since.05" href="#changes.since.05">Since draft-ietf-httpbis-p2-semantics-05</a></h2>
     4403      <p id="rfc.section.E.12.p.1">Closed issues: </p>
    32004404      <ul>
    32014405         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/94">http://tools.ietf.org/wg/httpbis/trac/ticket/94</a>&gt;: "reason-phrase BNF"
    32024406         </li>
    32034407      </ul>
    3204       <p id="rfc.section.C.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;):
     4408      <p id="rfc.section.E.12.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;):
    32054409      </p>
    32064410      <ul>
    32074411         <li>Add appendix containing collected and expanded ABNF, reorganize ABNF introduction.</li>
    32084412      </ul>
    3209       <h2 id="rfc.section.C.8"><a href="#rfc.section.C.8">C.8</a>&nbsp;<a id="changes.since.06" href="#changes.since.06">Since draft-ietf-httpbis-p2-semantics-06</a></h2>
    3210       <p id="rfc.section.C.8.p.1">Closed issues: </p>
     4413      <h2 id="rfc.section.E.13"><a href="#rfc.section.E.13">E.13</a>&nbsp;<a id="changes.since.3.05" href="#changes.since.3.05">Since draft-ietf-httpbis-p3-payload-05</a></h2>
     4414      <p id="rfc.section.E.13.p.1">Closed issues: </p>
     4415      <ul>
     4416         <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"?"
     4417         </li>
     4418      </ul>
     4419      <p id="rfc.section.E.13.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;):
     4420      </p>
     4421      <ul>
     4422         <li>Add appendix containing collected and expanded ABNF, reorganize ABNF introduction.</li>
     4423      </ul>
     4424      <p id="rfc.section.E.13.p.3">Other changes: </p>
     4425      <ul>
     4426         <li>Move definition of quality values into Part 1.</li>
     4427      </ul>
     4428      <h2 id="rfc.section.E.14"><a href="#rfc.section.E.14">E.14</a>&nbsp;<a id="changes.since.06" href="#changes.since.06">Since draft-ietf-httpbis-p2-semantics-06</a></h2>
     4429      <p id="rfc.section.E.14.p.1">Closed issues: </p>
    32114430      <ul>
    32124431         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/144">http://tools.ietf.org/wg/httpbis/trac/ticket/144</a>&gt;: "Clarify when Referer is sent"
     
    32174436         </li>
    32184437      </ul>
    3219       <h2 id="rfc.section.C.9"><a href="#rfc.section.C.9">C.9</a>&nbsp;<a id="changes.since.07" href="#changes.since.07">Since draft-ietf-httpbis-p2-semantics-07</a></h2>
    3220       <p id="rfc.section.C.9.p.1">Closed issues: </p>
     4438      <h2 id="rfc.section.E.15"><a href="#rfc.section.E.15">E.15</a>&nbsp;<a id="changes.since.3.06" href="#changes.since.3.06">Since draft-ietf-httpbis-p3-payload-06</a></h2>
     4439      <p id="rfc.section.E.15.p.1">Closed issues: </p>
     4440      <ul>
     4441         <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"
     4442         </li>
     4443         <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"
     4444         </li>
     4445      </ul>
     4446      <h2 id="rfc.section.E.16"><a href="#rfc.section.E.16">E.16</a>&nbsp;<a id="changes.since.07" href="#changes.since.07">Since draft-ietf-httpbis-p2-semantics-07</a></h2>
     4447      <p id="rfc.section.E.16.p.1">Closed issues: </p>
    32214448      <ul>
    32224449         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/27">http://tools.ietf.org/wg/httpbis/trac/ticket/27</a>&gt;: "Idempotency"
     
    32374464         </li>
    32384465      </ul>
    3239       <p id="rfc.section.C.9.p.2">Partly resolved issues: </p>
     4466      <p id="rfc.section.E.16.p.2">Partly resolved issues: </p>
    32404467      <ul>
    32414468         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/171">http://tools.ietf.org/wg/httpbis/trac/ticket/171</a>&gt;: "Are OPTIONS and TRACE safe?"
    32424469         </li>
    32434470      </ul>
    3244       <h2 id="rfc.section.C.10"><a href="#rfc.section.C.10">C.10</a>&nbsp;<a id="changes.since.08" href="#changes.since.08">Since draft-ietf-httpbis-p2-semantics-08</a></h2>
    3245       <p id="rfc.section.C.10.p.1">Closed issues: </p>
     4471      <h2 id="rfc.section.E.17"><a href="#rfc.section.E.17">E.17</a>&nbsp;<a id="changes.since.3-07" href="#changes.since.3-07">Since draft-ietf-httpbis-p3-payload-07</a></h2>
     4472      <p id="rfc.section.E.17.p.1">Closed issues: </p>
     4473      <ul>
     4474         <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"
     4475         </li>
     4476         <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"
     4477         </li>
     4478         <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"
     4479         </li>
     4480         <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"
     4481         </li>
     4482         <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"
     4483         </li>
     4484         <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"
     4485         </li>
     4486      </ul>
     4487      <p id="rfc.section.E.17.p.2">Partly resolved issues: </p>
     4488      <ul>
     4489         <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)
     4490         </li>
     4491         <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)
     4492         </li>
     4493      </ul>
     4494      <h2 id="rfc.section.E.18"><a href="#rfc.section.E.18">E.18</a>&nbsp;<a id="changes.since.08" href="#changes.since.08">Since draft-ietf-httpbis-p2-semantics-08</a></h2>
     4495      <p id="rfc.section.E.18.p.1">Closed issues: </p>
    32464496      <ul>
    32474497         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/10">http://tools.ietf.org/wg/httpbis/trac/ticket/10</a>&gt;: "Safe Methods vs Redirection" (we missed the introduction to the 3xx status codes when fixing this previously)
    32484498         </li>
    32494499      </ul>
    3250       <h2 id="rfc.section.C.11"><a href="#rfc.section.C.11">C.11</a>&nbsp;<a id="changes.since.09" href="#changes.since.09">Since draft-ietf-httpbis-p2-semantics-09</a></h2>
    3251       <p id="rfc.section.C.11.p.1">Closed issues: </p>
     4500      <h2 id="rfc.section.E.19"><a href="#rfc.section.E.19">E.19</a>&nbsp;<a id="changes.since.3.08" href="#changes.since.3.08">Since draft-ietf-httpbis-p3-payload-08</a></h2>
     4501      <p id="rfc.section.E.19.p.1">Closed issues: </p>
     4502      <ul>
     4503         <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"
     4504         </li>
     4505         <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?"
     4506         </li>
     4507      </ul>
     4508      <h2 id="rfc.section.E.20"><a href="#rfc.section.E.20">E.20</a>&nbsp;<a id="changes.since.09" href="#changes.since.09">Since draft-ietf-httpbis-p2-semantics-09</a></h2>
     4509      <p id="rfc.section.E.20.p.1">Closed issues: </p>
    32524510      <ul>
    32534511         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/43">http://tools.ietf.org/wg/httpbis/trac/ticket/43</a>&gt;: "Fragment combination / precedence during redirects"
    32544512         </li>
    32554513      </ul>
    3256       <p id="rfc.section.C.11.p.2">Partly resolved issues: </p>
     4514      <p id="rfc.section.E.20.p.2">Partly resolved issues: </p>
    32574515      <ul>
    32584516         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/185">http://tools.ietf.org/wg/httpbis/trac/ticket/185</a>&gt;: "Location header payload handling"
     
    32614519         </li>
    32624520      </ul>
    3263       <h2 id="rfc.section.C.12"><a href="#rfc.section.C.12">C.12</a>&nbsp;<a id="changes.since.10" href="#changes.since.10">Since draft-ietf-httpbis-p2-semantics-10</a></h2>
    3264       <p id="rfc.section.C.12.p.1">Closed issues: </p>
     4521      <h2 id="rfc.section.E.21"><a href="#rfc.section.E.21">E.21</a>&nbsp;<a id="changes.since.3.09" href="#changes.since.3.09">Since draft-ietf-httpbis-p3-payload-09</a></h2>
     4522      <p id="rfc.section.E.21.p.1">Closed issues: </p>
     4523      <ul>
     4524         <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"
     4525         </li>
     4526         <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"
     4527         </li>
     4528         <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"
     4529         </li>
     4530         <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"
     4531         </li>
     4532      </ul>
     4533      <p id="rfc.section.E.21.p.2">Partly resolved issues: </p>
     4534      <ul>
     4535         <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"
     4536         </li>
     4537      </ul>
     4538      <h2 id="rfc.section.E.22"><a href="#rfc.section.E.22">E.22</a>&nbsp;<a id="changes.since.10" href="#changes.since.10">Since draft-ietf-httpbis-p2-semantics-10</a></h2>
     4539      <p id="rfc.section.E.22.p.1">Closed issues: </p>
    32654540      <ul>
    32664541         <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'"
     
    32774552         </li>
    32784553      </ul>
    3279       <h2 id="rfc.section.C.13"><a href="#rfc.section.C.13">C.13</a>&nbsp;<a id="changes.since.11" href="#changes.since.11">Since draft-ietf-httpbis-p2-semantics-11</a></h2>
    3280       <p id="rfc.section.C.13.p.1">Closed issues: </p>
     4554      <h2 id="rfc.section.E.23"><a href="#rfc.section.E.23">E.23</a>&nbsp;<a id="changes.since.3.10" href="#changes.since.3.10">Since draft-ietf-httpbis-p3-payload-10</a></h2>
     4555      <p id="rfc.section.E.23.p.1">Closed issues: </p>
     4556      <ul>
     4557         <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'"
     4558         </li>
     4559         <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"
     4560         </li>
     4561         <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"
     4562         </li>
     4563         <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"
     4564         </li>
     4565         <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"
     4566         </li>
     4567         <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"
     4568         </li>
     4569         <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"
     4570         </li>
     4571         <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"
     4572         </li>
     4573      </ul>
     4574      <p id="rfc.section.E.23.p.2">Partly resolved issues: </p>
     4575      <ul>
     4576         <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"
     4577         </li>
     4578      </ul>
     4579      <h2 id="rfc.section.E.24"><a href="#rfc.section.E.24">E.24</a>&nbsp;<a id="changes.since.11" href="#changes.since.11">Since draft-ietf-httpbis-p2-semantics-11</a></h2>
     4580      <p id="rfc.section.E.24.p.1">Closed issues: </p>
    32814581      <ul>
    32824582         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/229">http://tools.ietf.org/wg/httpbis/trac/ticket/229</a>&gt;: "Considerations for new status codes"
     
    32874587         </li>
    32884588      </ul>
    3289       <h2 id="rfc.section.C.14"><a href="#rfc.section.C.14">C.14</a>&nbsp;<a id="changes.since.12" href="#changes.since.12">Since draft-ietf-httpbis-p2-semantics-12</a></h2>
    3290       <p id="rfc.section.C.14.p.1">Closed issues: </p>
     4589      <h2 id="rfc.section.E.25"><a href="#rfc.section.E.25">E.25</a>&nbsp;<a id="changes.since.3.11" href="#changes.since.3.11">Since draft-ietf-httpbis-p3-payload-11</a></h2>
     4590      <p id="rfc.section.E.25.p.1">Closed issues: </p>
     4591      <ul>
     4592         <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"
     4593         </li>
     4594      </ul>
     4595      <h2 id="rfc.section.E.26"><a href="#rfc.section.E.26">E.26</a>&nbsp;<a id="changes.since.12" href="#changes.since.12">Since draft-ietf-httpbis-p2-semantics-12</a></h2>
     4596      <p id="rfc.section.E.26.p.1">Closed issues: </p>
    32914597      <ul>
    32924598         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/43">http://tools.ietf.org/wg/httpbis/trac/ticket/43</a>&gt;: "Fragment combination / precedence during redirects" (added warning about having a fragid on the redirect may cause inconvenience
     
    33304636         </li>
    33314637      </ul>
    3332       <h2 id="rfc.section.C.15"><a href="#rfc.section.C.15">C.15</a>&nbsp;<a id="changes.since.13" href="#changes.since.13">Since draft-ietf-httpbis-p2-semantics-13</a></h2>
    3333       <p id="rfc.section.C.15.p.1">Closed issues: </p>
    3334       <ul>
     4638      <h2 id="rfc.section.E.27"><a href="#rfc.section.E.27">E.27</a>&nbsp;<a id="changes.since.3.12" href="#changes.since.3.12">Since draft-ietf-httpbis-p3-payload-12</a></h2>
     4639      <p id="rfc.section.E.27.p.1">Closed issues: </p>
     4640      <ul>
     4641         <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"
     4642         </li>
    33354643         <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"
    33364644         </li>
     4645         <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"
     4646         </li>
     4647      </ul>
     4648      <h2 id="rfc.section.E.28"><a href="#rfc.section.E.28">E.28</a>&nbsp;<a id="changes.since.13" href="#changes.since.13">Since draft-ietf-httpbis-p2-semantics-13</a></h2>
     4649      <p id="rfc.section.E.28.p.1">Closed issues: </p>
     4650      <ul>
     4651         <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"
     4652         </li>
    33374653         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/251">http://tools.ietf.org/wg/httpbis/trac/ticket/251</a>&gt;: "message body in CONNECT request"
    33384654         </li>
    33394655      </ul>
    3340       <h2 id="rfc.section.C.16"><a href="#rfc.section.C.16">C.16</a>&nbsp;<a id="changes.since.14" href="#changes.since.14">Since draft-ietf-httpbis-p2-semantics-14</a></h2>
    3341       <p id="rfc.section.C.16.p.1">Closed issues: </p>
     4656      <h2 id="rfc.section.E.29"><a href="#rfc.section.E.29">E.29</a>&nbsp;<a id="changes.since.3.13" href="#changes.since.3.13">Since draft-ietf-httpbis-p3-payload-13</a></h2>
     4657      <p id="rfc.section.E.29.p.1">Closed issues: </p>
     4658      <ul>
     4659         <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"
     4660         </li>
     4661         <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"
     4662         </li>
     4663         <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"
     4664         </li>
     4665         <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"
     4666         </li>
     4667      </ul>
     4668      <h2 id="rfc.section.E.30"><a href="#rfc.section.E.30">E.30</a>&nbsp;<a id="changes.since.14" href="#changes.since.14">Since draft-ietf-httpbis-p2-semantics-14</a></h2>
     4669      <p id="rfc.section.E.30.p.1">Closed issues: </p>
    33424670      <ul>
    33434671         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/255">http://tools.ietf.org/wg/httpbis/trac/ticket/255</a>&gt;: "Clarify status code for rate limiting"
     
    33504678         </li>
    33514679      </ul>
    3352       <h2 id="rfc.section.C.17"><a href="#rfc.section.C.17">C.17</a>&nbsp;<a id="changes.since.15" href="#changes.since.15">Since draft-ietf-httpbis-p2-semantics-15</a></h2>
    3353       <p id="rfc.section.C.17.p.1">Closed issues: </p>
     4680      <h2 id="rfc.section.E.31"><a href="#rfc.section.E.31">E.31</a>&nbsp;<a id="changes.since.3.14" href="#changes.since.3.14">Since draft-ietf-httpbis-p3-payload-14</a></h2>
     4681      <p id="rfc.section.E.31.p.1">None.</p>
     4682      <h2 id="rfc.section.E.32"><a href="#rfc.section.E.32">E.32</a>&nbsp;<a id="changes.since.15" href="#changes.since.15">Since draft-ietf-httpbis-p2-semantics-15</a></h2>
     4683      <p id="rfc.section.E.32.p.1">Closed issues: </p>
    33544684      <ul>
    33554685         <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"
     
    33584688         </li>
    33594689      </ul>
    3360       <h2 id="rfc.section.C.18"><a href="#rfc.section.C.18">C.18</a>&nbsp;<a id="changes.since.16" href="#changes.since.16">Since draft-ietf-httpbis-p2-semantics-16</a></h2>
    3361       <p id="rfc.section.C.18.p.1">Closed issues: </p>
     4690      <h2 id="rfc.section.E.33"><a href="#rfc.section.E.33">E.33</a>&nbsp;<a id="changes.since.3.15" href="#changes.since.3.15">Since draft-ietf-httpbis-p3-payload-15</a></h2>
     4691      <p id="rfc.section.E.33.p.1">Closed issues: </p>
     4692      <ul>
     4693         <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"
     4694         </li>
     4695      </ul>
     4696      <h2 id="rfc.section.E.34"><a href="#rfc.section.E.34">E.34</a>&nbsp;<a id="changes.since.16" href="#changes.since.16">Since draft-ietf-httpbis-p2-semantics-16</a></h2>
     4697      <p id="rfc.section.E.34.p.1">Closed issues: </p>
    33624698      <ul>
    33634699         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/160">http://tools.ietf.org/wg/httpbis/trac/ticket/160</a>&gt;: "Redirects and non-GET methods"
     
    33704706         </li>
    33714707      </ul>
    3372       <h2 id="rfc.section.C.19"><a href="#rfc.section.C.19">C.19</a>&nbsp;<a id="changes.since.17" href="#changes.since.17">Since draft-ietf-httpbis-p2-semantics-17</a></h2>
    3373       <p id="rfc.section.C.19.p.1">Closed issues: </p>
     4708      <h2 id="rfc.section.E.35"><a href="#rfc.section.E.35">E.35</a>&nbsp;<a id="changes.since.3.16" href="#changes.since.3.16">Since draft-ietf-httpbis-p3-payload-16</a></h2>
     4709      <p id="rfc.section.E.35.p.1">Closed issues: </p>
     4710      <ul>
     4711         <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"
     4712         </li>
     4713      </ul>
     4714      <h2 id="rfc.section.E.36"><a href="#rfc.section.E.36">E.36</a>&nbsp;<a id="changes.since.17" href="#changes.since.17">Since draft-ietf-httpbis-p2-semantics-17</a></h2>
     4715      <p id="rfc.section.E.36.p.1">Closed issues: </p>
    33744716      <ul>
    33754717         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/185">http://tools.ietf.org/wg/httpbis/trac/ticket/185</a>&gt;: "Location header payload handling"
     
    33864728         </li>
    33874729      </ul>
    3388       <h2 id="rfc.section.C.20"><a href="#rfc.section.C.20">C.20</a>&nbsp;<a id="changes.since.18" href="#changes.since.18">Since draft-ietf-httpbis-p2-semantics-18</a></h2>
    3389       <p id="rfc.section.C.20.p.1">Closed issues: </p>
     4730      <h2 id="rfc.section.E.37"><a href="#rfc.section.E.37">E.37</a>&nbsp;<a id="changes.since.3.17" href="#changes.since.3.17">Since draft-ietf-httpbis-p3-payload-17</a></h2>
     4731      <p id="rfc.section.E.37.p.1">Closed issues: </p>
     4732      <ul>
     4733         <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"
     4734         </li>
     4735      </ul>
     4736      <h2 id="rfc.section.E.38"><a href="#rfc.section.E.38">E.38</a>&nbsp;<a id="changes.since.18" href="#changes.since.18">Since draft-ietf-httpbis-p2-semantics-18</a></h2>
     4737      <p id="rfc.section.E.38.p.1">Closed issues: </p>
    33904738      <ul>
    33914739         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/227">http://tools.ietf.org/wg/httpbis/trac/ticket/227</a>&gt;: "Combining HEAD responses"
     
    34084756         </li>
    34094757      </ul>
    3410       <h2 id="rfc.section.C.21"><a href="#rfc.section.C.21">C.21</a>&nbsp;<a id="changes.since.19" href="#changes.since.19">Since draft-ietf-httpbis-p2-semantics-19</a></h2>
    3411       <p id="rfc.section.C.21.p.1">Closed issues: </p>
     4758      <h2 id="rfc.section.E.39"><a href="#rfc.section.E.39">E.39</a>&nbsp;<a id="changes.since.3.18" href="#changes.since.3.18">Since draft-ietf-httpbis-p3-payload-18</a></h2>
     4759      <p id="rfc.section.E.39.p.1">Closed issues: </p>
     4760      <ul>
     4761         <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?"
     4762         </li>
     4763         <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"
     4764         </li>
     4765         <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"
     4766         </li>
     4767      </ul>
     4768      <h2 id="rfc.section.E.40"><a href="#rfc.section.E.40">E.40</a>&nbsp;<a id="changes.since.19" href="#changes.since.19">Since draft-ietf-httpbis-p2-semantics-19</a></h2>
     4769      <p id="rfc.section.E.40.p.1">Closed issues: </p>
    34124770      <ul>
    34134771         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/312">http://tools.ietf.org/wg/httpbis/trac/ticket/312</a>&gt;: "should there be a permanent variant of 307"
     
    34204778         <ul class="ind">
    34214779            <li><a id="rfc.index.1" href="#rfc.index.1"><b>1</b></a><ul>
    3422                   <li>100 Continue (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.100.1">4.1</a>, <a href="#rfc.iref.22"><b>4.3.1</b></a>, <a href="#rfc.xref.status.100.2">8.2</a></li>
    3423                   <li>100-continue (expect value)&nbsp;&nbsp;<a href="#rfc.iref.89"><b>7.3</b></a></li>
    3424                   <li>101 Switching Protocols (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.101.1">4.1</a>, <a href="#rfc.iref.23"><b>4.3.2</b></a>, <a href="#rfc.xref.status.101.2">8.2</a></li>
     4780                  <li>100 Continue (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.100.1">4.1</a>, <a href="#rfc.iref.24"><b>4.3.1</b></a>, <a href="#rfc.xref.status.100.2">12.2</a></li>
     4781                  <li>100-continue (expect value)&nbsp;&nbsp;<a href="#rfc.iref.108"><b>11.3</b></a></li>
     4782                  <li>101 Switching Protocols (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.101.1">4.1</a>, <a href="#rfc.iref.25"><b>4.3.2</b></a>, <a href="#rfc.xref.status.101.2">12.2</a></li>
    34254783               </ul>
    34264784            </li>
    34274785            <li><a id="rfc.index.2" href="#rfc.index.2"><b>2</b></a><ul>
    3428                   <li>200 OK (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.200.1">4.1</a>, <a href="#rfc.iref.24"><b>4.4.1</b></a>, <a href="#rfc.xref.status.200.2">8.2</a></li>
    3429                   <li>201 Created (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.201.1">4.1</a>, <a href="#rfc.iref.25"><b>4.4.2</b></a>, <a href="#rfc.xref.status.201.2">8.2</a></li>
    3430                   <li>202 Accepted (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.202.1">4.1</a>, <a href="#rfc.iref.26"><b>4.4.3</b></a>, <a href="#rfc.xref.status.202.2">8.2</a></li>
    3431                   <li>203 Non-Authoritative Information (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.203.1">4.1</a>, <a href="#rfc.iref.27"><b>4.4.4</b></a>, <a href="#rfc.xref.status.203.2">8.2</a>, <a href="#rfc.xref.status.203.3">A</a></li>
    3432                   <li>204 No Content (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.204.1">4.1</a>, <a href="#rfc.iref.28"><b>4.4.5</b></a>, <a href="#rfc.xref.status.204.2">8.2</a></li>
    3433                   <li>205 Reset Content (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.205.1">4.1</a>, <a href="#rfc.iref.29"><b>4.4.6</b></a>, <a href="#rfc.xref.status.205.2">8.2</a></li>
     4786                  <li>200 OK (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.200.1">4.1</a>, <a href="#rfc.iref.26"><b>4.4.1</b></a>, <a href="#rfc.xref.status.200.2">12.2</a></li>
     4787                  <li>201 Created (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.201.1">4.1</a>, <a href="#rfc.iref.27"><b>4.4.2</b></a>, <a href="#rfc.xref.status.201.2">12.2</a></li>
     4788                  <li>202 Accepted (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.202.1">4.1</a>, <a href="#rfc.iref.28"><b>4.4.3</b></a>, <a href="#rfc.xref.status.202.2">12.2</a></li>
     4789                  <li>203 Non-Authoritative Information (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.203.1">4.1</a>, <a href="#rfc.iref.29"><b>4.4.4</b></a>, <a href="#rfc.xref.status.203.2">12.2</a>, <a href="#rfc.xref.status.203.3">C</a></li>
     4790                  <li>204 No Content (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.204.1">4.1</a>, <a href="#rfc.iref.30"><b>4.4.5</b></a>, <a href="#rfc.xref.status.204.2">12.2</a></li>
     4791                  <li>205 Reset Content (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.205.1">4.1</a>, <a href="#rfc.iref.31"><b>4.4.6</b></a>, <a href="#rfc.xref.status.205.2">12.2</a></li>
    34344792               </ul>
    34354793            </li>
    34364794            <li><a id="rfc.index.3" href="#rfc.index.3"><b>3</b></a><ul>
    3437                   <li>300 Multiple Choices (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.300.1">4.1</a>, <a href="#rfc.iref.30"><b>4.5.1</b></a>, <a href="#rfc.xref.status.300.2">8.2</a></li>
    3438                   <li>301 Moved Permanently (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.301.1">4.1</a>, <a href="#rfc.iref.31"><b>4.5.2</b></a>, <a href="#rfc.xref.status.301.2">8.2</a>, <a href="#rfc.xref.status.301.3">A</a></li>
    3439                   <li>302 Found (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.302.1">4.1</a>, <a href="#rfc.iref.32"><b>4.5.3</b></a>, <a href="#rfc.xref.status.302.2">8.2</a>, <a href="#rfc.xref.status.302.3">A</a></li>
    3440                   <li>303 See Other (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.303.1">4.1</a>, <a href="#rfc.iref.33"><b>4.5.4</b></a>, <a href="#rfc.xref.status.303.2">8.2</a></li>
    3441                   <li>305 Use Proxy (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.305.1">4.1</a>, <a href="#rfc.iref.34"><b>4.5.5</b></a>, <a href="#rfc.xref.status.305.2">8.2</a>, <a href="#rfc.xref.status.305.3">A</a></li>
    3442                   <li>306 (Unused) (status code)&nbsp;&nbsp;<a href="#rfc.iref.35"><b>4.5.6</b></a>, <a href="#rfc.xref.status.306.1">8.2</a></li>
    3443                   <li>307 Temporary Redirect (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.307.1">4.1</a>, <a href="#rfc.iref.36"><b>4.5.7</b></a>, <a href="#rfc.xref.status.307.2">8.2</a>, <a href="#rfc.xref.status.307.3">A</a></li>
     4795                  <li>300 Multiple Choices (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.300.1">4.1</a>, <a href="#rfc.iref.32"><b>4.5.1</b></a>, <a href="#rfc.xref.status.300.2">12.2</a></li>
     4796                  <li>301 Moved Permanently (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.301.1">4.1</a>, <a href="#rfc.iref.33"><b>4.5.2</b></a>, <a href="#rfc.xref.status.301.2">12.2</a>, <a href="#rfc.xref.status.301.3">C</a></li>
     4797                  <li>302 Found (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.302.1">4.1</a>, <a href="#rfc.iref.34"><b>4.5.3</b></a>, <a href="#rfc.xref.status.302.2">12.2</a>, <a href="#rfc.xref.status.302.3">C</a></li>
     4798                  <li>303 See Other (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.303.1">4.1</a>, <a href="#rfc.iref.35"><b>4.5.4</b></a>, <a href="#rfc.xref.status.303.2">12.2</a></li>
     4799                  <li>305 Use Proxy (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.305.1">4.1</a>, <a href="#rfc.iref.36"><b>4.5.5</b></a>, <a href="#rfc.xref.status.305.2">12.2</a>, <a href="#rfc.xref.status.305.3">C</a></li>
     4800                  <li>306 (Unused) (status code)&nbsp;&nbsp;<a href="#rfc.iref.37"><b>4.5.6</b></a>, <a href="#rfc.xref.status.306.1">12.2</a></li>
     4801                  <li>307 Temporary Redirect (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.307.1">4.1</a>, <a href="#rfc.iref.38"><b>4.5.7</b></a>, <a href="#rfc.xref.status.307.2">12.2</a>, <a href="#rfc.xref.status.307.3">C</a></li>
    34444802               </ul>
    34454803            </li>
    34464804            <li><a id="rfc.index.4" href="#rfc.index.4"><b>4</b></a><ul>
    3447                   <li>400 Bad Request (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.400.1">4.1</a>, <a href="#rfc.iref.37"><b>4.6.1</b></a>, <a href="#rfc.xref.status.400.2">8.2</a></li>
    3448                   <li>402 Payment Required (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.402.1">4.1</a>, <a href="#rfc.iref.38"><b>4.6.2</b></a>, <a href="#rfc.xref.status.402.2">8.2</a></li>
    3449                   <li>403 Forbidden (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.403.1">4.1</a>, <a href="#rfc.iref.39"><b>4.6.3</b></a>, <a href="#rfc.xref.status.403.2">8.2</a></li>
    3450                   <li>404 Not Found (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.404.1">4.1</a>, <a href="#rfc.iref.40"><b>4.6.4</b></a>, <a href="#rfc.xref.status.404.2">8.2</a></li>
    3451                   <li>405 Method Not Allowed (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.405.1">4.1</a>, <a href="#rfc.iref.41"><b>4.6.5</b></a>, <a href="#rfc.xref.status.405.2">8.2</a></li>
    3452                   <li>406 Not Acceptable (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.406.1">4.1</a>, <a href="#rfc.iref.42"><b>4.6.6</b></a>, <a href="#rfc.xref.status.406.2">8.2</a></li>
    3453                   <li>408 Request Timeout (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.408.1">4.1</a>, <a href="#rfc.iref.43"><b>4.6.7</b></a>, <a href="#rfc.xref.status.408.2">8.2</a></li>
    3454                   <li>409 Conflict (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.409.1">4.1</a>, <a href="#rfc.iref.44"><b>4.6.8</b></a>, <a href="#rfc.xref.status.409.2">8.2</a></li>
    3455                   <li>410 Gone (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.410.1">4.1</a>, <a href="#rfc.iref.45"><b>4.6.9</b></a>, <a href="#rfc.xref.status.410.2">8.2</a></li>
    3456                   <li>411 Length Required (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.411.1">4.1</a>, <a href="#rfc.iref.46"><b>4.6.10</b></a>, <a href="#rfc.xref.status.411.2">8.2</a></li>
    3457                   <li>413 Request Representation Too Large (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.413.1">4.1</a>, <a href="#rfc.iref.47"><b>4.6.11</b></a>, <a href="#rfc.xref.status.413.2">8.2</a></li>
    3458                   <li>414 URI Too Long (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.414.1">4.1</a>, <a href="#rfc.iref.48"><b>4.6.12</b></a>, <a href="#rfc.xref.status.414.2">8.2</a></li>
    3459                   <li>415 Unsupported Media Type (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.415.1">4.1</a>, <a href="#rfc.iref.49"><b>4.6.13</b></a>, <a href="#rfc.xref.status.415.2">8.2</a></li>
    3460                   <li>417 Expectation Failed (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.417.1">4.1</a>, <a href="#rfc.iref.50"><b>4.6.14</b></a>, <a href="#rfc.xref.status.417.2">8.2</a></li>
    3461                   <li>426 Upgrade Required (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.426.1">4.1</a>, <a href="#rfc.iref.51"><b>4.6.15</b></a>, <a href="#rfc.xref.status.426.2">8.2</a>, <a href="#rfc.xref.status.426.3">A</a></li>
     4805                  <li>400 Bad Request (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.400.1">4.1</a>, <a href="#rfc.iref.39"><b>4.6.1</b></a>, <a href="#rfc.xref.status.400.2">12.2</a></li>
     4806                  <li>402 Payment Required (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.402.1">4.1</a>, <a href="#rfc.iref.40"><b>4.6.2</b></a>, <a href="#rfc.xref.status.402.2">12.2</a></li>
     4807                  <li>403 Forbidden (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.403.1">4.1</a>, <a href="#rfc.iref.41"><b>4.6.3</b></a>, <a href="#rfc.xref.status.403.2">12.2</a></li>
     4808                  <li>404 Not Found (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.404.1">4.1</a>, <a href="#rfc.iref.42"><b>4.6.4</b></a>, <a href="#rfc.xref.status.404.2">12.2</a></li>
     4809                  <li>405 Method Not Allowed (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.405.1">4.1</a>, <a href="#rfc.iref.43"><b>4.6.5</b></a>, <a href="#rfc.xref.status.405.2">12.2</a></li>
     4810                  <li>406 Not Acceptable (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.406.1">4.1</a>, <a href="#rfc.iref.44"><b>4.6.6</b></a>, <a href="#rfc.xref.status.406.2">12.2</a></li>
     4811                  <li>408 Request Timeout (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.408.1">4.1</a>, <a href="#rfc.iref.45"><b>4.6.7</b></a>, <a href="#rfc.xref.status.408.2">12.2</a></li>
     4812                  <li>409 Conflict (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.409.1">4.1</a>, <a href="#rfc.iref.46"><b>4.6.8</b></a>, <a href="#rfc.xref.status.409.2">12.2</a></li>
     4813                  <li>410 Gone (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.410.1">4.1</a>, <a href="#rfc.iref.47"><b>4.6.9</b></a>, <a href="#rfc.xref.status.410.2">12.2</a></li>
     4814                  <li>411 Length Required (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.411.1">4.1</a>, <a href="#rfc.iref.48"><b>4.6.10</b></a>, <a href="#rfc.xref.status.411.2">12.2</a></li>
     4815                  <li>413 Request Representation Too Large (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.413.1">4.1</a>, <a href="#rfc.iref.49"><b>4.6.11</b></a>, <a href="#rfc.xref.status.413.2">12.2</a></li>
     4816                  <li>414 URI Too Long (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.414.1">4.1</a>, <a href="#rfc.iref.50"><b>4.6.12</b></a>, <a href="#rfc.xref.status.414.2">12.2</a></li>
     4817                  <li>415 Unsupported Media Type (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.415.1">4.1</a>, <a href="#rfc.iref.51"><b>4.6.13</b></a>, <a href="#rfc.xref.status.415.2">12.2</a></li>
     4818                  <li>417 Expectation Failed (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.417.1">4.1</a>, <a href="#rfc.iref.52"><b>4.6.14</b></a>, <a href="#rfc.xref.status.417.2">12.2</a></li>
     4819                  <li>426 Upgrade Required (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.426.1">4.1</a>, <a href="#rfc.iref.53"><b>4.6.15</b></a>, <a href="#rfc.xref.status.426.2">12.2</a>, <a href="#rfc.xref.status.426.3">C</a></li>
    34624820               </ul>
    34634821            </li>
    34644822            <li><a id="rfc.index.5" href="#rfc.index.5"><b>5</b></a><ul>
    3465                   <li>500 Internal Server Error (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.500.1">4.1</a>, <a href="#rfc.iref.52"><b>4.7.1</b></a>, <a href="#rfc.xref.status.500.2">8.2</a></li>
    3466                   <li>501 Not Implemented (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.501.1">4.1</a>, <a href="#rfc.iref.53"><b>4.7.2</b></a>, <a href="#rfc.xref.status.501.2">8.2</a></li>
    3467                   <li>502 Bad Gateway (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.502.1">4.1</a>, <a href="#rfc.iref.54"><b>4.7.3</b></a>, <a href="#rfc.xref.status.502.2">8.2</a></li>
    3468                   <li>503 Service Unavailable (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.503.1">4.1</a>, <a href="#rfc.iref.55"><b>4.7.4</b></a>, <a href="#rfc.xref.status.503.2">8.2</a></li>
    3469                   <li>504 Gateway Timeout (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.504.1">4.1</a>, <a href="#rfc.iref.56"><b>4.7.5</b></a>, <a href="#rfc.xref.status.504.2">8.2</a></li>
    3470                   <li>505 HTTP Version Not Supported (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.505.1">4.1</a>, <a href="#rfc.iref.57"><b>4.7.6</b></a>, <a href="#rfc.xref.status.505.2">8.2</a></li>
     4823                  <li>500 Internal Server Error (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.500.1">4.1</a>, <a href="#rfc.iref.54"><b>4.7.1</b></a>, <a href="#rfc.xref.status.500.2">12.2</a></li>
     4824                  <li>501 Not Implemented (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.501.1">4.1</a>, <a href="#rfc.iref.55"><b>4.7.2</b></a>, <a href="#rfc.xref.status.501.2">12.2</a></li>
     4825                  <li>502 Bad Gateway (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.502.1">4.1</a>, <a href="#rfc.iref.56"><b>4.7.3</b></a>, <a href="#rfc.xref.status.502.2">12.2</a></li>
     4826                  <li>503 Service Unavailable (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.503.1">4.1</a>, <a href="#rfc.iref.57"><b>4.7.4</b></a>, <a href="#rfc.xref.status.503.2">12.2</a></li>
     4827                  <li>504 Gateway Timeout (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.504.1">4.1</a>, <a href="#rfc.iref.58"><b>4.7.5</b></a>, <a href="#rfc.xref.status.504.2">12.2</a></li>
     4828                  <li>505 HTTP Version Not Supported (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.505.1">4.1</a>, <a href="#rfc.iref.59"><b>4.7.6</b></a>, <a href="#rfc.xref.status.505.2">12.2</a></li>
    34714829               </ul>
    34724830            </li>
    34734831            <li><a id="rfc.index.A" href="#rfc.index.A"><b>A</b></a><ul>
    3474                   <li>Allow header field&nbsp;&nbsp;<a href="#rfc.xref.header.allow.1">2</a>, <a href="#rfc.xref.header.allow.2">3.3</a>, <a href="#rfc.iref.a.1"><b>7.1</b></a>, <a href="#rfc.xref.header.allow.3">8.3</a>, <a href="#rfc.xref.header.allow.4">A</a></li>
     4832                  <li>Accept header field&nbsp;&nbsp;<a href="#rfc.xref.header.accept.1">3.2</a>, <a href="#rfc.xref.header.accept.2">7.3</a>, <a href="#rfc.xref.header.accept.3">10.1</a>, <a href="#rfc.iref.a.2"><b>11.11</b></a>, <a href="#rfc.xref.header.accept.4">12.3</a></li>
     4833                  <li>Accept-Charset header field&nbsp;&nbsp;<a href="#rfc.xref.header.accept-charset.1">3.2</a>, <a href="#rfc.xref.header.accept-charset.2">10.1</a>, <a href="#rfc.iref.a.3"><b>11.12</b></a>, <a href="#rfc.xref.header.accept-charset.3">12.3</a>, <a href="#rfc.xref.header.accept-charset.4">C</a></li>
     4834                  <li>Accept-Encoding header field&nbsp;&nbsp;<a href="#rfc.xref.header.accept-encoding.1">3.2</a>, <a href="#rfc.xref.header.accept-encoding.2">7.2</a>, <a href="#rfc.xref.header.accept-encoding.3">10.1</a>, <a href="#rfc.iref.a.4"><b>11.13</b></a>, <a href="#rfc.xref.header.accept-encoding.4">12.3</a>, <a href="#rfc.xref.header.accept-encoding.5">12.4</a></li>
     4835                  <li>Accept-Language header field&nbsp;&nbsp;<a href="#rfc.xref.header.accept-language.1">3.2</a>, <a href="#rfc.xref.header.accept-language.2">10.1</a>, <a href="#rfc.iref.a.5"><b>11.14</b></a>, <a href="#rfc.xref.header.accept-language.3">12.3</a></li>
     4836                  <li>Allow header field&nbsp;&nbsp;<a href="#rfc.xref.header.allow.1">2</a>, <a href="#rfc.xref.header.allow.2">3.3</a>, <a href="#rfc.iref.a.1"><b>11.1</b></a>, <a href="#rfc.xref.header.allow.3">12.3</a>, <a href="#rfc.xref.header.allow.4">C</a></li>
    34754837               </ul>
    34764838            </li>
    34774839            <li><a id="rfc.index.C" href="#rfc.index.C"><b>C</b></a><ul>
    3478                   <li>CONNECT method&nbsp;&nbsp;<a href="#rfc.iref.c.1"><b>2.3.8</b></a>, <a href="#rfc.xref.CONNECT.1">8.1</a>, <a href="#rfc.xref.CONNECT.2">A</a></li>
     4840                  <li>Coding Format&nbsp;&nbsp;
     4841                     <ul>
     4842                        <li>compress&nbsp;&nbsp;<a href="#rfc.iref.c.4">7.2</a></li>
     4843                        <li>deflate&nbsp;&nbsp;<a href="#rfc.iref.c.5">7.2</a></li>
     4844                        <li>gzip&nbsp;&nbsp;<a href="#rfc.iref.c.6">7.2</a></li>
     4845                     </ul>
     4846                  </li>
     4847                  <li>compress (Coding Format)&nbsp;&nbsp;<a href="#rfc.iref.c.3">7.2</a></li>
     4848                  <li>CONNECT method&nbsp;&nbsp;<a href="#rfc.iref.c.2"><b>2.3.8</b></a>, <a href="#rfc.xref.CONNECT.1">12.1</a>, <a href="#rfc.xref.CONNECT.2">C</a></li>
     4849                  <li>content negotiation&nbsp;&nbsp;<a href="#rfc.iref.c.1">1.1</a></li>
     4850                  <li>Content-Encoding header field&nbsp;&nbsp;<a href="#rfc.xref.header.content-encoding.1">7.2</a>, <a href="#rfc.xref.header.content-encoding.2">9.1</a>, <a href="#rfc.iref.c.7"><b>11.15</b></a>, <a href="#rfc.xref.header.content-encoding.3">11.15</a>, <a href="#rfc.xref.header.content-encoding.4">12.3</a></li>
     4851                  <li>Content-Language header field&nbsp;&nbsp;<a href="#rfc.xref.header.content-language.1">9.1</a>, <a href="#rfc.iref.c.8"><b>11.16</b></a>, <a href="#rfc.xref.header.content-language.2">12.3</a></li>
     4852                  <li>Content-Location header field&nbsp;&nbsp;<a href="#rfc.xref.header.content-location.1">2.3.4</a>, <a href="#rfc.xref.header.content-location.2">9.1</a>, <a href="#rfc.xref.header.content-location.3">11.5</a>, <a href="#rfc.iref.c.9"><b>11.17</b></a>, <a href="#rfc.xref.header.content-location.4">12.3</a>, <a href="#rfc.xref.header.content-location.5">C</a></li>
     4853                  <li>Content-Transfer-Encoding header field&nbsp;&nbsp;<a href="#rfc.iref.c.11">A.5</a>, <a href="#rfc.xref.no.content-transfer-encoding.1">C</a></li>
     4854                  <li>Content-Type header field&nbsp;&nbsp;<a href="#rfc.xref.header.content-type.1">3.1</a>, <a href="#rfc.xref.header.content-type.2">4</a>, <a href="#rfc.xref.header.content-type.3">7.3</a>, <a href="#rfc.xref.header.content-type.4">9.1</a>, <a href="#rfc.iref.c.10"><b>11.18</b></a>, <a href="#rfc.xref.header.content-type.5">12.3</a></li>
    34794855               </ul>
    34804856            </li>
    34814857            <li><a id="rfc.index.D" href="#rfc.index.D"><b>D</b></a><ul>
    3482                   <li>Date header field&nbsp;&nbsp;<a href="#rfc.xref.header.date.1">3.3</a>, <a href="#rfc.iref.d.2"><b>7.2</b></a>, <a href="#rfc.xref.header.date.2">8.3</a></li>
    3483                   <li>DELETE method&nbsp;&nbsp;<a href="#rfc.iref.d.1"><b>2.3.6</b></a>, <a href="#rfc.xref.DELETE.1">8.1</a></li>
    3484                   <li><em>draft-reschke-http-status-308</em>&nbsp;&nbsp;<a href="#rfc.xref.draft-reschke-http-status-308.1">4.5.7</a>, <a href="#draft-reschke-http-status-308"><b>11.2</b></a></li>
     4858                  <li>Date header field&nbsp;&nbsp;<a href="#rfc.xref.header.date.1">3.3</a>, <a href="#rfc.iref.d.3"><b>11.2</b></a>, <a href="#rfc.xref.header.date.2">12.3</a></li>
     4859                  <li>deflate (Coding Format)&nbsp;&nbsp;<a href="#rfc.iref.d.2">7.2</a></li>
     4860                  <li>DELETE method&nbsp;&nbsp;<a href="#rfc.iref.d.1"><b>2.3.6</b></a>, <a href="#rfc.xref.DELETE.1">12.1</a></li>
     4861                  <li><em>draft-reschke-http-status-308</em>&nbsp;&nbsp;<a href="#rfc.xref.draft-reschke-http-status-308.1">4.5.7</a>, <a href="#draft-reschke-http-status-308"><b>15.2</b></a></li>
    34854862               </ul>
    34864863            </li>
    34874864            <li><a id="rfc.index.E" href="#rfc.index.E"><b>E</b></a><ul>
    3488                   <li>Expect header field&nbsp;&nbsp;<a href="#rfc.xref.header.expect.1">3.2</a>, <a href="#rfc.xref.header.expect.2">4.6.14</a>, <a href="#rfc.iref.e.1"><b>7.3</b></a>, <a href="#rfc.xref.header.expect.3">8.3</a>, <a href="#rfc.xref.header.expect.4">A</a></li>
     4865                  <li>Expect header field&nbsp;&nbsp;<a href="#rfc.xref.header.expect.1">3.2</a>, <a href="#rfc.xref.header.expect.2">4.6.14</a>, <a href="#rfc.iref.e.1"><b>11.3</b></a>, <a href="#rfc.xref.header.expect.3">12.3</a>, <a href="#rfc.xref.header.expect.4">C</a></li>
    34894866                  <li>Expect Values&nbsp;&nbsp;
    34904867                     <ul>
    3491                         <li>100-continue&nbsp;&nbsp;<a href="#rfc.iref.e.2"><b>7.3</b></a></li>
     4868                        <li>100-continue&nbsp;&nbsp;<a href="#rfc.iref.e.2"><b>11.3</b></a></li>
    34924869                     </ul>
    34934870                  </li>
     
    34954872            </li>
    34964873            <li><a id="rfc.index.F" href="#rfc.index.F"><b>F</b></a><ul>
    3497                   <li>From header field&nbsp;&nbsp;<a href="#rfc.xref.header.from.1">3.2</a>, <a href="#rfc.iref.f.1"><b>7.4</b></a>, <a href="#rfc.xref.header.from.2">8.3</a></li>
     4874                  <li>From header field&nbsp;&nbsp;<a href="#rfc.xref.header.from.1">3.2</a>, <a href="#rfc.iref.f.1"><b>11.4</b></a>, <a href="#rfc.xref.header.from.2">12.3</a></li>
    34984875               </ul>
    34994876            </li>
    35004877            <li><a id="rfc.index.G" href="#rfc.index.G"><b>G</b></a><ul>
    3501                   <li>GET method&nbsp;&nbsp;<a href="#rfc.iref.g.2"><b>2.3.2</b></a>, <a href="#rfc.xref.GET.1">8.1</a></li>
     4878                  <li>GET method&nbsp;&nbsp;<a href="#rfc.iref.g.2"><b>2.3.2</b></a>, <a href="#rfc.xref.GET.1">12.1</a></li>
    35024879                  <li><tt>Grammar</tt>&nbsp;&nbsp;
    35034880                     <ul>
    3504                         <li><tt>Allow</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.24"><b>7.1</b></a></li>
     4881                        <li><tt>Accept</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.49"><b>11.11</b></a></li>
     4882                        <li><tt>Accept-Charset</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.53"><b>11.12</b></a></li>
     4883                        <li><tt>Accept-Encoding</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.54"><b>11.13</b></a></li>
     4884                        <li><tt>accept-ext</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.52"><b>11.11</b></a></li>
     4885                        <li><tt>Accept-Language</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.56"><b>11.14</b></a></li>
     4886                        <li><tt>accept-params</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.51"><b>11.11</b></a></li>
     4887                        <li><tt>Allow</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.34"><b>11.1</b></a></li>
    35054888                        <li><tt>asctime-date</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.21"><b>6.1</b></a></li>
    3506                         <li><tt>Date</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.25"><b>7.2</b></a></li>
     4889                        <li><tt>attribute</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.31"><b>7.3</b></a></li>
     4890                        <li><tt>charset</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.24"><b>7.1</b></a></li>
     4891                        <li><tt>codings</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.55"><b>11.13</b></a></li>
     4892                        <li><tt>content-coding</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.25"><b>7.2</b></a></li>
     4893                        <li><tt>Content-Encoding</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.58"><b>11.15</b></a></li>
     4894                        <li><tt>Content-Language</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.59"><b>11.16</b></a></li>
     4895                        <li><tt>Content-Location</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.60"><b>11.17</b></a></li>
     4896                        <li><tt>Content-Type</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.61"><b>11.18</b></a></li>
     4897                        <li><tt>Date</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.35"><b>11.2</b></a></li>
    35074898                        <li><tt>date1</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.8"><b>6.1</b></a></li>
    35084899                        <li><tt>day</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.15"><b>6.1</b></a></li>
    35094900                        <li><tt>day-name</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.13"><b>6.1</b></a></li>
    35104901                        <li><tt>day-name-l</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.14"><b>6.1</b></a></li>
    3511                         <li><tt>delta-seconds</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.36"><b>7.8</b></a></li>
    3512                         <li><tt>Expect</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.26"><b>7.3</b></a></li>
    3513                         <li><tt>expect-name</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.30"><b>7.3</b></a></li>
    3514                         <li><tt>expect-param</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.28"><b>7.3</b></a></li>
    3515                         <li><tt>expect-value</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.29"><b>7.3</b></a></li>
    3516                         <li><tt>expectation</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.27"><b>7.3</b></a></li>
     4902                        <li><tt>delta-seconds</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.46"><b>11.8</b></a></li>
     4903                        <li><tt>Expect</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.36"><b>11.3</b></a></li>
     4904                        <li><tt>expect-name</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.40"><b>11.3</b></a></li>
     4905                        <li><tt>expect-param</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.38"><b>11.3</b></a></li>
     4906                        <li><tt>expect-value</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.39"><b>11.3</b></a></li>
     4907                        <li><tt>expectation</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.37"><b>11.3</b></a></li>
    35174908                        <li><tt>extension-code</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.4"><b>4</b></a></li>
    3518                         <li><tt>From</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.31"><b>7.4</b></a></li>
     4909                        <li><tt>From</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.41"><b>11.4</b></a></li>
    35194910                        <li><tt>GMT</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.18"><b>6.1</b></a></li>
    35204911                        <li><tt>hour</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.10"><b>6.1</b></a></li>
    35214912                        <li><tt>HTTP-date</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.6"><b>6.1</b></a></li>
    3522                         <li><tt>Location</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.32"><b>7.5</b></a></li>
    3523                         <li><tt>Max-Forwards</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.33"><b>7.6</b></a></li>
     4913                        <li><tt>language-range</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.57"><b>11.14</b></a></li>
     4914                        <li><tt>language-tag</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.33"><b>7.4</b></a></li>
     4915                        <li><tt>Location</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.42"><b>11.5</b></a></li>
     4916                        <li><tt>Max-Forwards</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.43"><b>11.6</b></a></li>
     4917                        <li><tt>media-range</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.50"><b>11.11</b></a></li>
     4918                        <li><tt>media-type</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.27"><b>7.3</b></a></li>
    35244919                        <li><tt>method</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.1"><b>2</b></a></li>
     4920                        <li><tt>MIME-Version</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.62"><b>A.1</b></a></li>
    35254921                        <li><tt>minute</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.11"><b>6.1</b></a></li>
    35264922                        <li><tt>month</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.16"><b>6.1</b></a></li>
    35274923                        <li><tt>obs-date</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.19"><b>6.1</b></a></li>
     4924                        <li><tt>parameter</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.30"><b>7.3</b></a></li>
    35284925                        <li><tt>product</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.22"><b>6.2</b></a></li>
    35294926                        <li><tt>product-version</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.23"><b>6.2</b></a></li>
    35304927                        <li><tt>reason-phrase</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.5"><b>4</b></a></li>
    3531                         <li><tt>Referer</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.34"><b>7.7</b></a></li>
    3532                         <li><tt>Retry-After</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.35"><b>7.8</b></a></li>
     4928                        <li><tt>Referer</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.44"><b>11.7</b></a></li>
     4929                        <li><tt>Retry-After</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.45"><b>11.8</b></a></li>
    35334930                        <li><tt>rfc1123-date</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.7"><b>6.1</b></a></li>
    35344931                        <li><tt>rfc850-date</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.20"><b>6.1</b></a></li>
    35354932                        <li><tt>second</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.12"><b>6.1</b></a></li>
    3536                         <li><tt>Server</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.37"><b>7.9</b></a></li>
     4933                        <li><tt>Server</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.47"><b>11.9</b></a></li>
    35374934                        <li><tt>status-code</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.3"><b>4</b></a></li>
     4935                        <li><tt>subtype</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.29"><b>7.3</b></a></li>
    35384936                        <li><tt>time-of-day</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.9"><b>6.1</b></a></li>
    3539                         <li><tt>User-Agent</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.38"><b>7.10</b></a></li>
     4937                        <li><tt>type</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.28"><b>7.3</b></a></li>
     4938                        <li><tt>User-Agent</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.48"><b>11.10</b></a></li>
     4939                        <li><tt>value</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.32"><b>7.3</b></a></li>
    35404940                        <li><tt>year</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.17"><b>6.1</b></a></li>
    35414941                     </ul>
    35424942                  </li>
     4943                  <li>gzip (Coding Format)&nbsp;&nbsp;<a href="#rfc.iref.g.26">7.2</a></li>
    35434944               </ul>
    35444945            </li>
    35454946            <li><a id="rfc.index.H" href="#rfc.index.H"><b>H</b></a><ul>
    3546                   <li>HEAD method&nbsp;&nbsp;<a href="#rfc.iref.h.1"><b>2.3.3</b></a>, <a href="#rfc.xref.HEAD.1">8.1</a></li>
     4947                  <li>HEAD method&nbsp;&nbsp;<a href="#rfc.iref.h.1"><b>2.3.3</b></a>, <a href="#rfc.xref.HEAD.1">12.1</a></li>
    35474948                  <li>Header Fields&nbsp;&nbsp;
    35484949                     <ul>
    3549                         <li>Allow&nbsp;&nbsp;<a href="#rfc.xref.header.allow.1">2</a>, <a href="#rfc.xref.header.allow.2">3.3</a>, <a href="#rfc.iref.h.2"><b>7.1</b></a>, <a href="#rfc.xref.header.allow.3">8.3</a>, <a href="#rfc.xref.header.allow.4">A</a></li>
    3550                         <li>Date&nbsp;&nbsp;<a href="#rfc.xref.header.date.1">3.3</a>, <a href="#rfc.iref.h.3"><b>7.2</b></a>, <a href="#rfc.xref.header.date.2">8.3</a></li>
    3551                         <li>Expect&nbsp;&nbsp;<a href="#rfc.xref.header.expect.1">3.2</a>, <a href="#rfc.xref.header.expect.2">4.6.14</a>, <a href="#rfc.iref.h.4"><b>7.3</b></a>, <a href="#rfc.xref.header.expect.3">8.3</a>, <a href="#rfc.xref.header.expect.4">A</a></li>
    3552                         <li>From&nbsp;&nbsp;<a href="#rfc.xref.header.from.1">3.2</a>, <a href="#rfc.iref.h.5"><b>7.4</b></a>, <a href="#rfc.xref.header.from.2">8.3</a></li>
    3553                         <li>Location&nbsp;&nbsp;<a href="#rfc.xref.header.location.1">2.3.4</a>, <a href="#rfc.xref.header.location.2">3.3</a>, <a href="#rfc.xref.header.location.3">4.5</a>, <a href="#rfc.iref.h.6"><b>7.5</b></a>, <a href="#rfc.xref.header.location.4">8.3</a>, <a href="#rfc.xref.header.location.5">A</a></li>
    3554                         <li>Max-Forwards&nbsp;&nbsp;<a href="#rfc.xref.header.max-forwards.1">2.3.1</a>, <a href="#rfc.xref.header.max-forwards.2">2.3.7</a>, <a href="#rfc.xref.header.max-forwards.3">3.2</a>, <a href="#rfc.iref.h.7"><b>7.6</b></a>, <a href="#rfc.xref.header.max-forwards.4">8.3</a>, <a href="#rfc.xref.header.max-forwards.5">A</a></li>
    3555                         <li>Referer&nbsp;&nbsp;<a href="#rfc.xref.header.referer.1">3.2</a>, <a href="#rfc.iref.h.8"><b>7.7</b></a>, <a href="#rfc.xref.header.referer.2">8.3</a>, <a href="#rfc.xref.header.referer.3">A</a></li>
    3556                         <li>Retry-After&nbsp;&nbsp;<a href="#rfc.xref.header.retry-after.1">3.3</a>, <a href="#rfc.xref.header.retry-after.2">4.7.4</a>, <a href="#rfc.iref.h.9"><b>7.8</b></a>, <a href="#rfc.xref.header.retry-after.3">8.3</a></li>
    3557                         <li>Server&nbsp;&nbsp;<a href="#rfc.xref.header.server.1">3.3</a>, <a href="#rfc.iref.h.10"><b>7.9</b></a>, <a href="#rfc.xref.header.server.2">8.3</a>, <a href="#rfc.xref.header.server.3">9.1</a>, <a href="#rfc.xref.header.server.4">A</a></li>
    3558                         <li>User-Agent&nbsp;&nbsp;<a href="#rfc.xref.header.user-agent.1">3.2</a>, <a href="#rfc.iref.h.11"><b>7.10</b></a>, <a href="#rfc.xref.header.user-agent.2">8.3</a>, <a href="#rfc.xref.header.user-agent.3">9.1</a></li>
     4950                        <li>Accept&nbsp;&nbsp;<a href="#rfc.xref.header.accept.1">3.2</a>, <a href="#rfc.xref.header.accept.2">7.3</a>, <a href="#rfc.xref.header.accept.3">10.1</a>, <a href="#rfc.iref.h.12"><b>11.11</b></a>, <a href="#rfc.xref.header.accept.4">12.3</a></li>
     4951                        <li>Accept-Charset&nbsp;&nbsp;<a href="#rfc.xref.header.accept-charset.1">3.2</a>, <a href="#rfc.xref.header.accept-charset.2">10.1</a>, <a href="#rfc.iref.h.13"><b>11.12</b></a>, <a href="#rfc.xref.header.accept-charset.3">12.3</a>, <a href="#rfc.xref.header.accept-charset.4">C</a></li>
     4952                        <li>Accept-Encoding&nbsp;&nbsp;<a href="#rfc.xref.header.accept-encoding.1">3.2</a>, <a href="#rfc.xref.header.accept-encoding.2">7.2</a>, <a href="#rfc.xref.header.accept-encoding.3">10.1</a>, <a href="#rfc.iref.h.14"><b>11.13</b></a>, <a href="#rfc.xref.header.accept-encoding.4">12.3</a>, <a href="#rfc.xref.header.accept-encoding.5">12.4</a></li>
     4953                        <li>Accept-Language&nbsp;&nbsp;<a href="#rfc.xref.header.accept-language.1">3.2</a>, <a href="#rfc.xref.header.accept-language.2">10.1</a>, <a href="#rfc.iref.h.15"><b>11.14</b></a>, <a href="#rfc.xref.header.accept-language.3">12.3</a></li>
     4954                        <li>Allow&nbsp;&nbsp;<a href="#rfc.xref.header.allow.1">2</a>, <a href="#rfc.xref.header.allow.2">3.3</a>, <a href="#rfc.iref.h.2"><b>11.1</b></a>, <a href="#rfc.xref.header.allow.3">12.3</a>, <a href="#rfc.xref.header.allow.4">C</a></li>
     4955                        <li>Content-Encoding&nbsp;&nbsp;<a href="#rfc.xref.header.content-encoding.1">7.2</a>, <a href="#rfc.xref.header.content-encoding.2">9.1</a>, <a href="#rfc.iref.h.16"><b>11.15</b></a>, <a href="#rfc.xref.header.content-encoding.3">11.15</a>, <a href="#rfc.xref.header.content-encoding.4">12.3</a></li>
     4956                        <li>Content-Language&nbsp;&nbsp;<a href="#rfc.xref.header.content-language.1">9.1</a>, <a href="#rfc.iref.h.17"><b>11.16</b></a>, <a href="#rfc.xref.header.content-language.2">12.3</a></li>
     4957                        <li>Content-Location&nbsp;&nbsp;<a href="#rfc.xref.header.content-location.1">2.3.4</a>, <a href="#rfc.xref.header.content-location.2">9.1</a>, <a href="#rfc.xref.header.content-location.3">11.5</a>, <a href="#rfc.iref.h.18"><b>11.17</b></a>, <a href="#rfc.xref.header.content-location.4">12.3</a>, <a href="#rfc.xref.header.content-location.5">C</a></li>
     4958                        <li>Content-Transfer-Encoding&nbsp;&nbsp;<a href="#rfc.iref.h.21">A.5</a>, <a href="#rfc.xref.no.content-transfer-encoding.1">C</a></li>
     4959                        <li>Content-Type&nbsp;&nbsp;<a href="#rfc.xref.header.content-type.1">3.1</a>, <a href="#rfc.xref.header.content-type.2">4</a>, <a href="#rfc.xref.header.content-type.3">7.3</a>, <a href="#rfc.xref.header.content-type.4">9.1</a>, <a href="#rfc.iref.h.19"><b>11.18</b></a>, <a href="#rfc.xref.header.content-type.5">12.3</a></li>
     4960                        <li>Date&nbsp;&nbsp;<a href="#rfc.xref.header.date.1">3.3</a>, <a href="#rfc.iref.h.3"><b>11.2</b></a>, <a href="#rfc.xref.header.date.2">12.3</a></li>
     4961                        <li>Expect&nbsp;&nbsp;<a href="#rfc.xref.header.expect.1">3.2</a>, <a href="#rfc.xref.header.expect.2">4.6.14</a>, <a href="#rfc.iref.h.4"><b>11.3</b></a>, <a href="#rfc.xref.header.expect.3">12.3</a>, <a href="#rfc.xref.header.expect.4">C</a></li>
     4962                        <li>From&nbsp;&nbsp;<a href="#rfc.xref.header.from.1">3.2</a>, <a href="#rfc.iref.h.5"><b>11.4</b></a>, <a href="#rfc.xref.header.from.2">12.3</a></li>
     4963                        <li>Location&nbsp;&nbsp;<a href="#rfc.xref.header.location.1">2.3.4</a>, <a href="#rfc.xref.header.location.2">3.3</a>, <a href="#rfc.xref.header.location.3">4.5</a>, <a href="#rfc.iref.h.6"><b>11.5</b></a>, <a href="#rfc.xref.header.location.4">12.3</a>, <a href="#rfc.xref.header.location.5">C</a></li>
     4964                        <li>Max-Forwards&nbsp;&nbsp;<a href="#rfc.xref.header.max-forwards.1">2.3.1</a>, <a href="#rfc.xref.header.max-forwards.2">2.3.7</a>, <a href="#rfc.xref.header.max-forwards.3">3.2</a>, <a href="#rfc.iref.h.7"><b>11.6</b></a>, <a href="#rfc.xref.header.max-forwards.4">12.3</a>, <a href="#rfc.xref.header.max-forwards.5">C</a></li>
     4965                        <li>MIME-Version&nbsp;&nbsp;<a href="#rfc.xref.mime-version.1">12.3</a>, <a href="#rfc.iref.h.20"><b>A.1</b></a></li>
     4966                        <li>Referer&nbsp;&nbsp;<a href="#rfc.xref.header.referer.1">3.2</a>, <a href="#rfc.iref.h.8"><b>11.7</b></a>, <a href="#rfc.xref.header.referer.2">12.3</a>, <a href="#rfc.xref.header.referer.3">C</a></li>
     4967                        <li>Retry-After&nbsp;&nbsp;<a href="#rfc.xref.header.retry-after.1">3.3</a>, <a href="#rfc.xref.header.retry-after.2">4.7.4</a>, <a href="#rfc.iref.h.9"><b>11.8</b></a>, <a href="#rfc.xref.header.retry-after.3">12.3</a></li>
     4968                        <li>Server&nbsp;&nbsp;<a href="#rfc.xref.header.server.1">3.3</a>, <a href="#rfc.iref.h.10"><b>11.9</b></a>, <a href="#rfc.xref.header.server.2">12.3</a>, <a href="#rfc.xref.header.server.3">13.1</a>, <a href="#rfc.xref.header.server.4">C</a></li>
     4969                        <li>User-Agent&nbsp;&nbsp;<a href="#rfc.xref.header.user-agent.1">3.2</a>, <a href="#rfc.xref.header.user-agent.2">10.1</a>, <a href="#rfc.iref.h.11"><b>11.10</b></a>, <a href="#rfc.xref.header.user-agent.3">12.3</a>, <a href="#rfc.xref.header.user-agent.4">13.1</a></li>
    35594970                     </ul>
    35604971                  </li>
     
    35664977            </li>
    35674978            <li><a id="rfc.index.L" href="#rfc.index.L"><b>L</b></a><ul>
    3568                   <li>Location header field&nbsp;&nbsp;<a href="#rfc.xref.header.location.1">2.3.4</a>, <a href="#rfc.xref.header.location.2">3.3</a>, <a href="#rfc.xref.header.location.3">4.5</a>, <a href="#rfc.iref.l.1"><b>7.5</b></a>, <a href="#rfc.xref.header.location.4">8.3</a>, <a href="#rfc.xref.header.location.5">A</a></li>
     4979                  <li>Location header field&nbsp;&nbsp;<a href="#rfc.xref.header.location.1">2.3.4</a>, <a href="#rfc.xref.header.location.2">3.3</a>, <a href="#rfc.xref.header.location.3">4.5</a>, <a href="#rfc.iref.l.1"><b>11.5</b></a>, <a href="#rfc.xref.header.location.4">12.3</a>, <a href="#rfc.xref.header.location.5">C</a></li>
    35694980               </ul>
    35704981            </li>
    35714982            <li><a id="rfc.index.M" href="#rfc.index.M"><b>M</b></a><ul>
    3572                   <li>Max-Forwards header field&nbsp;&nbsp;<a href="#rfc.xref.header.max-forwards.1">2.3.1</a>, <a href="#rfc.xref.header.max-forwards.2">2.3.7</a>, <a href="#rfc.xref.header.max-forwards.3">3.2</a>, <a href="#rfc.iref.m.9"><b>7.6</b></a>, <a href="#rfc.xref.header.max-forwards.4">8.3</a>, <a href="#rfc.xref.header.max-forwards.5">A</a></li>
     4983                  <li>Max-Forwards header field&nbsp;&nbsp;<a href="#rfc.xref.header.max-forwards.1">2.3.1</a>, <a href="#rfc.xref.header.max-forwards.2">2.3.7</a>, <a href="#rfc.xref.header.max-forwards.3">3.2</a>, <a href="#rfc.iref.m.9"><b>11.6</b></a>, <a href="#rfc.xref.header.max-forwards.4">12.3</a>, <a href="#rfc.xref.header.max-forwards.5">C</a></li>
    35734984                  <li>Methods&nbsp;&nbsp;
    35744985                     <ul>
    3575                         <li>CONNECT&nbsp;&nbsp;<a href="#rfc.iref.m.8"><b>2.3.8</b></a>, <a href="#rfc.xref.CONNECT.1">8.1</a>, <a href="#rfc.xref.CONNECT.2">A</a></li>
    3576                         <li>DELETE&nbsp;&nbsp;<a href="#rfc.iref.m.6"><b>2.3.6</b></a>, <a href="#rfc.xref.DELETE.1">8.1</a></li>
    3577                         <li>GET&nbsp;&nbsp;<a href="#rfc.iref.m.2"><b>2.3.2</b></a>, <a href="#rfc.xref.GET.1">8.1</a></li>
    3578                         <li>HEAD&nbsp;&nbsp;<a href="#rfc.iref.m.3"><b>2.3.3</b></a>, <a href="#rfc.xref.HEAD.1">8.1</a></li>
    3579                         <li>OPTIONS&nbsp;&nbsp;<a href="#rfc.iref.m.1"><b>2.3.1</b></a>, <a href="#rfc.xref.OPTIONS.1">7.6</a>, <a href="#rfc.xref.OPTIONS.2">8.1</a></li>
    3580                         <li>POST&nbsp;&nbsp;<a href="#rfc.iref.m.4"><b>2.3.4</b></a>, <a href="#rfc.xref.POST.1">8.1</a>, <a href="#rfc.xref.POST.2">A</a></li>
    3581                         <li>PUT&nbsp;&nbsp;<a href="#rfc.iref.m.5"><b>2.3.5</b></a>, <a href="#rfc.xref.PUT.1">8.1</a>, <a href="#rfc.xref.PUT.2">A</a></li>
    3582                         <li>TRACE&nbsp;&nbsp;<a href="#rfc.iref.m.7"><b>2.3.7</b></a>, <a href="#rfc.xref.TRACE.1">7.6</a>, <a href="#rfc.xref.TRACE.2">8.1</a>, <a href="#rfc.xref.TRACE.3">9.1</a></li>
     4986                        <li>CONNECT&nbsp;&nbsp;<a href="#rfc.iref.m.8"><b>2.3.8</b></a>, <a href="#rfc.xref.CONNECT.1">12.1</a>, <a href="#rfc.xref.CONNECT.2">C</a></li>
     4987                        <li>DELETE&nbsp;&nbsp;<a href="#rfc.iref.m.6"><b>2.3.6</b></a>, <a href="#rfc.xref.DELETE.1">12.1</a></li>
     4988                        <li>GET&nbsp;&nbsp;<a href="#rfc.iref.m.2"><b>2.3.2</b></a>, <a href="#rfc.xref.GET.1">12.1</a></li>
     4989                        <li>HEAD&nbsp;&nbsp;<a href="#rfc.iref.m.3"><b>2.3.3</b></a>, <a href="#rfc.xref.HEAD.1">12.1</a></li>
     4990                        <li>OPTIONS&nbsp;&nbsp;<a href="#rfc.iref.m.1"><b>2.3.1</b></a>, <a href="#rfc.xref.OPTIONS.1">11.6</a>, <a href="#rfc.xref.OPTIONS.2">12.1</a></li>
     4991                        <li>POST&nbsp;&nbsp;<a href="#rfc.iref.m.4"><b>2.3.4</b></a>, <a href="#rfc.xref.POST.1">12.1</a>, <a href="#rfc.xref.POST.2">C</a></li>
     4992                        <li>PUT&nbsp;&nbsp;<a href="#rfc.iref.m.5"><b>2.3.5</b></a>, <a href="#rfc.xref.PUT.1">12.1</a>, <a href="#rfc.xref.PUT.2">C</a></li>
     4993                        <li>TRACE&nbsp;&nbsp;<a href="#rfc.iref.m.7"><b>2.3.7</b></a>, <a href="#rfc.xref.TRACE.1">11.6</a>, <a href="#rfc.xref.TRACE.2">12.1</a>, <a href="#rfc.xref.TRACE.3">13.1</a></li>
    35834994                     </ul>
    35844995                  </li>
     4996                  <li>MIME-Version header field&nbsp;&nbsp;<a href="#rfc.xref.mime-version.1">12.3</a>, <a href="#rfc.iref.m.10"><b>A.1</b></a></li>
    35854997               </ul>
    35864998            </li>
    35874999            <li><a id="rfc.index.O" href="#rfc.index.O"><b>O</b></a><ul>
    3588                   <li>OPTIONS method&nbsp;&nbsp;<a href="#rfc.iref.o.1"><b>2.3.1</b></a>, <a href="#rfc.xref.OPTIONS.1">7.6</a>, <a href="#rfc.xref.OPTIONS.2">8.1</a></li>
     5000                  <li>OPTIONS method&nbsp;&nbsp;<a href="#rfc.iref.o.1"><b>2.3.1</b></a>, <a href="#rfc.xref.OPTIONS.1">11.6</a>, <a href="#rfc.xref.OPTIONS.2">12.1</a></li>
    35895001               </ul>
    35905002            </li>
    35915003            <li><a id="rfc.index.P" href="#rfc.index.P"><b>P</b></a><ul>
    3592                   <li><em>Part1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.1">1</a>, <a href="#rfc.xref.Part1.2">1.1</a>, <a href="#rfc.xref.Part1.3">1.2</a>, <a href="#rfc.xref.Part1.4">1.2.1</a>, <a href="#rfc.xref.Part1.5">1.2.1</a>, <a href="#rfc.xref.Part1.6">1.2.1</a>, <a href="#rfc.xref.Part1.7">1.2.1</a>, <a href="#rfc.xref.Part1.8">1.2.1</a>, <a href="#rfc.xref.Part1.9">1.2.1</a>, <a href="#rfc.xref.Part1.10">1.2.1</a>, <a href="#rfc.xref.Part1.11">1.2.2</a>, <a href="#rfc.xref.Part1.12">1.2.2</a>, <a href="#rfc.xref.Part1.13">1.2.2</a>, <a href="#rfc.xref.Part1.14">1.2.2</a>, <a href="#rfc.xref.Part1.15">2</a>, <a href="#rfc.xref.Part1.16">2.2.1</a>, <a href="#rfc.xref.Part1.17">2.3.1</a>, <a href="#rfc.xref.Part1.18">2.3.7</a>, <a href="#rfc.xref.Part1.19">2.3.7</a>, <a href="#rfc.xref.Part1.20">2.3.8</a>, <a href="#rfc.xref.Part1.21">3</a>, <a href="#rfc.xref.Part1.22">3.1</a>, <a href="#rfc.xref.Part1.23">3.1</a>, <a href="#rfc.xref.Part1.24">3.1</a>, <a href="#rfc.xref.Part1.25">3.1</a>, <a href="#rfc.xref.Part1.26">3.1</a>, <a href="#rfc.xref.Part1.27">3.2</a>, <a href="#rfc.xref.Part1.28">3.2</a>, <a href="#rfc.xref.Part1.29">3.3</a>, <a href="#rfc.xref.Part1.30">4.3.1</a>, <a href="#rfc.xref.Part1.31">4.3.2</a>, <a href="#rfc.xref.Part1.32">4.4.4</a>, <a href="#rfc.xref.Part1.33">4.4.6</a>, <a href="#rfc.xref.Part1.34">4.6.15</a>, <a href="#rfc.xref.Part1.35">4.7.6</a>, <a href="#rfc.xref.Part1.36">5</a>, <a href="#rfc.xref.Part1.37">5.1</a>, <a href="#rfc.xref.Part1.38">7.3</a>, <a href="#rfc.xref.Part1.39">7.9</a>, <a href="#rfc.xref.Part1.40">7.9</a>, <a href="#rfc.xref.Part1.41">7.10</a>, <a href="#rfc.xref.Part1.42">10</a>, <a href="#Part1"><b>11.1</b></a>, <a href="#rfc.xref.Part1.43">A</a><ul>
    3593                         <li><em>Section 1.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.3">1.2</a></li>
    3594                         <li><em>Section 2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.2">1.1</a></li>
     5004                  <li><em>Part1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.1">1</a>, <a href="#rfc.xref.Part1.2">1.2</a>, <a href="#rfc.xref.Part1.3">1.3</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.1</a>, <a href="#rfc.xref.Part1.8">1.3.1</a>, <a href="#rfc.xref.Part1.9">1.3.1</a>, <a href="#rfc.xref.Part1.10">1.3.1</a>, <a href="#rfc.xref.Part1.11">1.3.2</a>, <a href="#rfc.xref.Part1.12">1.3.2</a>, <a href="#rfc.xref.Part1.13">1.3.2</a>, <a href="#rfc.xref.Part1.14">1.3.2</a>, <a href="#rfc.xref.Part1.15">2</a>, <a href="#rfc.xref.Part1.16">2.2.1</a>, <a href="#rfc.xref.Part1.17">2.3.1</a>, <a href="#rfc.xref.Part1.18">2.3.7</a>, <a href="#rfc.xref.Part1.19">2.3.7</a>, <a href="#rfc.xref.Part1.20">2.3.8</a>, <a href="#rfc.xref.Part1.21">3</a>, <a href="#rfc.xref.Part1.22">3.1</a>, <a href="#rfc.xref.Part1.23">3.1</a>, <a href="#rfc.xref.Part1.24">3.1</a>, <a href="#rfc.xref.Part1.25">3.1</a>, <a href="#rfc.xref.Part1.26">3.1</a>, <a href="#rfc.xref.Part1.27">3.2</a>, <a href="#rfc.xref.Part1.28">3.2</a>, <a href="#rfc.xref.Part1.29">3.3</a>, <a href="#rfc.xref.Part1.30">4.3.1</a>, <a href="#rfc.xref.Part1.31">4.3.2</a>, <a href="#rfc.xref.Part1.32">4.4.4</a>, <a href="#rfc.xref.Part1.33">4.4.6</a>, <a href="#rfc.xref.Part1.34">4.6.15</a>, <a href="#rfc.xref.Part1.35">4.7.6</a>, <a href="#rfc.xref.Part1.36">5</a>, <a href="#rfc.xref.Part1.37">5.1</a>, <a href="#rfc.xref.Part1.38">7.2</a>, <a href="#rfc.xref.Part1.39">7.2</a>, <a href="#rfc.xref.Part1.40">7.2</a>, <a href="#rfc.xref.Part1.41">7.2.1</a>, <a href="#rfc.xref.Part1.42">7.2.1</a>, <a href="#rfc.xref.Part1.43">8.1</a>, <a href="#rfc.xref.Part1.44">8.2</a>, <a href="#rfc.xref.Part1.45">11.3</a>, <a href="#rfc.xref.Part1.46">11.9</a>, <a href="#rfc.xref.Part1.47">11.9</a>, <a href="#rfc.xref.Part1.48">11.10</a>, <a href="#rfc.xref.Part1.49">11.17</a>, <a href="#rfc.xref.Part1.50">12.4</a>, <a href="#rfc.xref.Part1.51">12.4</a>, <a href="#rfc.xref.Part1.52">12.4</a>, <a href="#rfc.xref.Part1.53">14</a>, <a href="#Part1"><b>15.1</b></a>, <a href="#rfc.xref.Part1.54">A.6</a>, <a href="#rfc.xref.Part1.55">C</a><ul>
     5005                        <li><em>Section 1.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.3">1.3</a></li>
     5006                        <li><em>Section 2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.2">1.2</a></li>
    35955007                        <li><em>Section 2.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.32">4.4.4</a></li>
    35965008                        <li><em>Section 2.6</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.35">4.7.6</a></li>
    3597                         <li><em>Section 2.7</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.11">1.2.2</a>, <a href="#rfc.xref.Part1.13">1.2.2</a>, <a href="#rfc.xref.Part1.14">1.2.2</a></li>
    3598                         <li><em>Section 3.2.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.5">1.2.1</a>, <a href="#rfc.xref.Part1.6">1.2.1</a>, <a href="#rfc.xref.Part1.7">1.2.1</a></li>
    3599                         <li><em>Section 3.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.21">3</a>, <a href="#rfc.xref.Part1.24">3.1</a>, <a href="#rfc.xref.Part1.39">7.9</a>, <a href="#rfc.xref.Part1.41">7.10</a></li>
    3600                         <li><em>Section 3.2.4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.8">1.2.1</a>, <a href="#rfc.xref.Part1.9">1.2.1</a>, <a href="#rfc.xref.Part1.10">1.2.1</a>, <a href="#rfc.xref.Part1.12">1.2.2</a>, <a href="#rfc.xref.Part1.23">3.1</a></li>
     5009                        <li><em>Section 2.7</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.11">1.3.2</a>, <a href="#rfc.xref.Part1.13">1.3.2</a>, <a href="#rfc.xref.Part1.14">1.3.2</a></li>
     5010                        <li><em>Section 3.2.1</em>&nbsp;&nbsp;<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.1</a></li>
     5011                        <li><em>Section 3.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.21">3</a>, <a href="#rfc.xref.Part1.24">3.1</a>, <a href="#rfc.xref.Part1.46">11.9</a>, <a href="#rfc.xref.Part1.48">11.10</a></li>
     5012                        <li><em>Section 3.2.4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.8">1.3.1</a>, <a href="#rfc.xref.Part1.9">1.3.1</a>, <a href="#rfc.xref.Part1.10">1.3.1</a>, <a href="#rfc.xref.Part1.12">1.3.2</a>, <a href="#rfc.xref.Part1.23">3.1</a></li>
    36015013                        <li><em>Section 3.2.5</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.22">3.1</a></li>
    3602                         <li><em>Section 3.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.16">2.2.1</a>, <a href="#rfc.xref.Part1.33">4.4.6</a>, <a href="#rfc.xref.Part1.36">5</a></li>
     5014                        <li><em>Section 3.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.16">2.2.1</a>, <a href="#rfc.xref.Part1.33">4.4.6</a>, <a href="#rfc.xref.Part1.36">5</a>, <a href="#rfc.xref.Part1.44">8.2</a></li>
     5015                        <li><em>Section 3.3.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.54">A.6</a></li>
     5016                        <li><em>Section 3.3.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.43">8.1</a></li>
     5017                        <li><em>Section 4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.41">7.2.1</a></li>
    36035018                        <li><em>Section 4.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.26">3.1</a></li>
     5019                        <li><em>Section 4.2.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.38">7.2</a>, <a href="#rfc.xref.Part1.50">12.4</a></li>
     5020                        <li><em>Section 4.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.42">7.2.1</a></li>
     5021                        <li><em>Section 4.2.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.39">7.2</a>, <a href="#rfc.xref.Part1.51">12.4</a></li>
     5022                        <li><em>Section 4.2.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.40">7.2</a>, <a href="#rfc.xref.Part1.52">12.4</a></li>
    36045023                        <li><em>Section 4.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.28">3.2</a></li>
    36055024                        <li><em>Section 5.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.17">2.3.1</a>, <a href="#rfc.xref.Part1.20">2.3.8</a></li>
    36065025                        <li><em>Section 5.4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.27">3.2</a></li>
    3607                         <li><em>Section 5.5</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.15">2</a>, <a href="#rfc.xref.Part1.29">3.3</a>, <a href="#rfc.xref.Part1.37">5.1</a></li>
     5026                        <li><em>Section 5.5</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.15">2</a>, <a href="#rfc.xref.Part1.29">3.3</a>, <a href="#rfc.xref.Part1.37">5.1</a>, <a href="#rfc.xref.Part1.49">11.17</a></li>
    36085027                        <li><em>Section 6.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.25">3.1</a></li>
    3609                         <li><em>Section 6.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.18">2.3.7</a>, <a href="#rfc.xref.Part1.40">7.9</a>, <a href="#rfc.xref.Part1.43">A</a></li>
    3610                         <li><em>Section 6.4.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.30">4.3.1</a>, <a href="#rfc.xref.Part1.38">7.3</a></li>
     5028                        <li><em>Section 6.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.18">2.3.7</a>, <a href="#rfc.xref.Part1.47">11.9</a>, <a href="#rfc.xref.Part1.55">C</a></li>
     5029                        <li><em>Section 6.4.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.30">4.3.1</a>, <a href="#rfc.xref.Part1.45">11.3</a></li>
    36115030                        <li><em>Section 6.5</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.31">4.3.2</a>, <a href="#rfc.xref.Part1.34">4.6.15</a></li>
    36125031                        <li><em>Section 7.3.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.19">2.3.7</a></li>
    3613                         <li><em>Section 9</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.42">10</a></li>
     5032                        <li><em>Section 9</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.53">14</a></li>
    36145033                     </ul>
    36155034                  </li>
    3616                   <li><em>Part3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part3.1">2.3.4</a>, <a href="#rfc.xref.Part3.2">3.1</a>, <a href="#rfc.xref.Part3.3">3.1</a>, <a href="#rfc.xref.Part3.4">3.2</a>, <a href="#rfc.xref.Part3.5">3.2</a>, <a href="#rfc.xref.Part3.6">3.2</a>, <a href="#rfc.xref.Part3.7">3.2</a>, <a href="#rfc.xref.Part3.8">4</a>, <a href="#rfc.xref.Part3.9">4.5</a>, <a href="#rfc.xref.Part3.10">4.5.1</a>, <a href="#rfc.xref.Part3.11">4.6.6</a>, <a href="#rfc.xref.Part3.12">5</a>, <a href="#rfc.xref.Part3.13">7.5</a>, <a href="#Part3"><b>11.1</b></a><ul>
    3617                         <li><em>Section 2.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part3.3">3.1</a></li>
    3618                         <li><em>Section 5</em>&nbsp;&nbsp;<a href="#rfc.xref.Part3.10">4.5.1</a></li>
    3619                         <li><em>Section 5.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part3.9">4.5</a></li>
    3620                         <li><em>Section 6.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part3.4">3.2</a></li>
    3621                         <li><em>Section 6</em>&nbsp;&nbsp;<a href="#rfc.xref.Part3.11">4.6.6</a></li>
    3622                         <li><em>Section 6.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part3.5">3.2</a></li>
    3623                         <li><em>Section 6.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part3.6">3.2</a></li>
    3624                         <li><em>Section 6.4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part3.7">3.2</a></li>
    3625                         <li><em>Section 6.7</em>&nbsp;&nbsp;<a href="#rfc.xref.Part3.1">2.3.4</a>, <a href="#rfc.xref.Part3.13">7.5</a></li>
    3626                         <li><em>Section 6.8</em>&nbsp;&nbsp;<a href="#rfc.xref.Part3.2">3.1</a>, <a href="#rfc.xref.Part3.8">4</a></li>
    3627                      </ul>
    3628                   </li>
    3629                   <li><em>Part4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part4.1">3.2</a>, <a href="#rfc.xref.Part4.2">3.2</a>, <a href="#rfc.xref.Part4.3">3.2</a>, <a href="#rfc.xref.Part4.4">3.2</a>, <a href="#rfc.xref.Part4.5">3.3</a>, <a href="#rfc.xref.Part4.6">4.1</a>, <a href="#rfc.xref.Part4.7">4.1</a>, <a href="#rfc.xref.Part4.8">4.1</a>, <a href="#rfc.xref.Part4.9">4.4.2</a>, <a href="#rfc.xref.Part4.10">4.5</a>, <a href="#Part4"><b>11.1</b></a>, <a href="#rfc.xref.Part4.11">C.2</a><ul>
    3630                         <li><em>Section 2.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part4.5">3.3</a>, <a href="#rfc.xref.Part4.9">4.4.2</a></li>
     5035                  <li><em>Part4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part4.1">3.2</a>, <a href="#rfc.xref.Part4.2">3.2</a>, <a href="#rfc.xref.Part4.3">3.2</a>, <a href="#rfc.xref.Part4.4">3.2</a>, <a href="#rfc.xref.Part4.5">3.3</a>, <a href="#rfc.xref.Part4.6">4.1</a>, <a href="#rfc.xref.Part4.7">4.1</a>, <a href="#rfc.xref.Part4.8">4.1</a>, <a href="#rfc.xref.Part4.9">4.4.2</a>, <a href="#rfc.xref.Part4.10">4.5</a>, <a href="#rfc.xref.Part4.11">9.1</a>, <a href="#rfc.xref.Part4.12">9.1</a>, <a href="#Part4"><b>15.1</b></a>, <a href="#rfc.xref.Part4.13">E.2</a><ul>
     5036                        <li><em>Section 2.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part4.12">9.1</a></li>
     5037                        <li><em>Section 2.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part4.5">3.3</a>, <a href="#rfc.xref.Part4.9">4.4.2</a>, <a href="#rfc.xref.Part4.11">9.1</a></li>
    36315038                        <li><em>Section 3.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part4.1">3.2</a></li>
    36325039                        <li><em>Section 3.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part4.3">3.2</a></li>
     
    36385045                     </ul>
    36395046                  </li>
    3640                   <li><em>Part5</em>&nbsp;&nbsp;<a href="#rfc.xref.Part5.1">2.3.2</a>, <a href="#rfc.xref.Part5.2">3.2</a>, <a href="#rfc.xref.Part5.3">3.2</a>, <a href="#rfc.xref.Part5.4">3.3</a>, <a href="#rfc.xref.Part5.5">4.1</a>, <a href="#rfc.xref.Part5.6">4.1</a>, <a href="#rfc.xref.Part5.7">4.1</a>, <a href="#Part5"><b>11.1</b></a><ul>
     5047                  <li><em>Part5</em>&nbsp;&nbsp;<a href="#rfc.xref.Part5.1">2.3.2</a>, <a href="#rfc.xref.Part5.2">3.2</a>, <a href="#rfc.xref.Part5.3">3.2</a>, <a href="#rfc.xref.Part5.4">3.3</a>, <a href="#rfc.xref.Part5.5">4.1</a>, <a href="#rfc.xref.Part5.6">4.1</a>, <a href="#rfc.xref.Part5.7">4.1</a>, <a href="#rfc.xref.Part5.8">8.1</a>, <a href="#Part5"><b>15.1</b></a><ul>
    36415048                        <li><em>Section 3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part5.5">4.1</a></li>
    36425049                        <li><em>Section 3.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part5.6">4.1</a></li>
    36435050                        <li><em>Section 3.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part5.7">4.1</a></li>
    36445051                        <li><em>Section 5.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part5.4">3.3</a></li>
     5052                        <li><em>Section 5.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part5.8">8.1</a></li>
    36455053                        <li><em>Section 5.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part5.2">3.2</a></li>
    36465054                        <li><em>Section 5.4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part5.1">2.3.2</a>, <a href="#rfc.xref.Part5.3">3.2</a></li>
    36475055                     </ul>
    36485056                  </li>
    3649                   <li><em>Part6</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.1">2.2.1</a>, <a href="#rfc.xref.Part6.2">2.3.2</a>, <a href="#rfc.xref.Part6.3">2.3.3</a>, <a href="#rfc.xref.Part6.4">2.3.4</a>, <a href="#rfc.xref.Part6.5">2.3.5</a>, <a href="#rfc.xref.Part6.6">2.3.6</a>, <a href="#rfc.xref.Part6.7">3.1</a>, <a href="#rfc.xref.Part6.8">3.3</a>, <a href="#rfc.xref.Part6.9">3.3</a>, <a href="#rfc.xref.Part6.10">4.2.1</a>, <a href="#rfc.xref.Part6.11">4.4.1</a>, <a href="#rfc.xref.Part6.12">4.4.4</a>, <a href="#rfc.xref.Part6.13">4.4.4</a>, <a href="#rfc.xref.Part6.14">4.4.4</a>, <a href="#rfc.xref.Part6.15">4.5.1</a>, <a href="#rfc.xref.Part6.16">4.5.2</a>, <a href="#rfc.xref.Part6.17">4.6.9</a>, <a href="#Part6"><b>11.1</b></a><ul>
     5057                  <li><em>Part6</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.1">2.2.1</a>, <a href="#rfc.xref.Part6.2">2.3.2</a>, <a href="#rfc.xref.Part6.3">2.3.3</a>, <a href="#rfc.xref.Part6.4">2.3.4</a>, <a href="#rfc.xref.Part6.5">2.3.5</a>, <a href="#rfc.xref.Part6.6">2.3.6</a>, <a href="#rfc.xref.Part6.7">3.1</a>, <a href="#rfc.xref.Part6.8">3.3</a>, <a href="#rfc.xref.Part6.9">3.3</a>, <a href="#rfc.xref.Part6.10">4.2.1</a>, <a href="#rfc.xref.Part6.11">4.4.1</a>, <a href="#rfc.xref.Part6.12">4.4.4</a>, <a href="#rfc.xref.Part6.13">4.4.4</a>, <a href="#rfc.xref.Part6.14">4.4.4</a>, <a href="#rfc.xref.Part6.15">4.5.1</a>, <a href="#rfc.xref.Part6.16">4.5.2</a>, <a href="#rfc.xref.Part6.17">4.6.9</a>, <a href="#rfc.xref.Part6.18">9.1</a>, <a href="#rfc.xref.Part6.19">10.1</a>, <a href="#Part6"><b>15.1</b></a><ul>
    36505058                        <li><em>Section 2.3.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.4">2.3.4</a></li>
    36515059                        <li><em>Section 2.3.1.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.11">4.4.1</a>, <a href="#rfc.xref.Part6.14">4.4.4</a>, <a href="#rfc.xref.Part6.15">4.5.1</a>, <a href="#rfc.xref.Part6.16">4.5.2</a>, <a href="#rfc.xref.Part6.17">4.6.9</a></li>
     
    36545062                        <li><em>Section 3.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.8">3.3</a></li>
    36555063                        <li><em>Section 3.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.12">4.4.4</a></li>
    3656                         <li><em>Section 3.5</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.9">3.3</a></li>
     5064                        <li><em>Section 3.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.18">9.1</a></li>
     5065                        <li><em>Section 3.5</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.9">3.3</a>, <a href="#rfc.xref.Part6.19">10.1</a></li>
    36575066                        <li><em>Section 3.6</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.13">4.4.4</a></li>
    36585067                     </ul>
    36595068                  </li>
    3660                   <li><em>Part7</em>&nbsp;&nbsp;<a href="#rfc.xref.Part7.1">3.2</a>, <a href="#rfc.xref.Part7.2">3.2</a>, <a href="#rfc.xref.Part7.3">3.3</a>, <a href="#rfc.xref.Part7.4">3.3</a>, <a href="#rfc.xref.Part7.5">4.1</a>, <a href="#rfc.xref.Part7.6">4.1</a>, <a href="#rfc.xref.Part7.7">4.1</a>, <a href="#Part7"><b>11.1</b></a><ul>
     5069                  <li><em>Part7</em>&nbsp;&nbsp;<a href="#rfc.xref.Part7.1">3.2</a>, <a href="#rfc.xref.Part7.2">3.2</a>, <a href="#rfc.xref.Part7.3">3.3</a>, <a href="#rfc.xref.Part7.4">3.3</a>, <a href="#rfc.xref.Part7.5">4.1</a>, <a href="#rfc.xref.Part7.6">4.1</a>, <a href="#rfc.xref.Part7.7">4.1</a>, <a href="#Part7"><b>15.1</b></a><ul>
    36615070                        <li><em>Section 3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part7.5">4.1</a></li>
    36625071                        <li><em>Section 3.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part7.6">4.1</a></li>
     
    36685077                     </ul>
    36695078                  </li>
    3670                   <li>POST method&nbsp;&nbsp;<a href="#rfc.iref.p.1"><b>2.3.4</b></a>, <a href="#rfc.xref.POST.1">8.1</a>, <a href="#rfc.xref.POST.2">A</a></li>
    3671                   <li>PUT method&nbsp;&nbsp;<a href="#rfc.iref.p.2"><b>2.3.5</b></a>, <a href="#rfc.xref.PUT.1">8.1</a>, <a href="#rfc.xref.PUT.2">A</a></li>
     5079                  <li>payload&nbsp;&nbsp;<a href="#rfc.iref.p.3">8</a></li>
     5080                  <li>POST method&nbsp;&nbsp;<a href="#rfc.iref.p.1"><b>2.3.4</b></a>, <a href="#rfc.xref.POST.1">12.1</a>, <a href="#rfc.xref.POST.2">C</a></li>
     5081                  <li>PUT method&nbsp;&nbsp;<a href="#rfc.iref.p.2"><b>2.3.5</b></a>, <a href="#rfc.xref.PUT.1">12.1</a>, <a href="#rfc.xref.PUT.2">C</a></li>
    36725082               </ul>
    36735083            </li>
    36745084            <li><a id="rfc.index.R" href="#rfc.index.R"><b>R</b></a><ul>
    3675                   <li>Referer header field&nbsp;&nbsp;<a href="#rfc.xref.header.referer.1">3.2</a>, <a href="#rfc.iref.r.1"><b>7.7</b></a>, <a href="#rfc.xref.header.referer.2">8.3</a>, <a href="#rfc.xref.header.referer.3">A</a></li>
    3676                   <li>Retry-After header field&nbsp;&nbsp;<a href="#rfc.xref.header.retry-after.1">3.3</a>, <a href="#rfc.xref.header.retry-after.2">4.7.4</a>, <a href="#rfc.iref.r.2"><b>7.8</b></a>, <a href="#rfc.xref.header.retry-after.3">8.3</a></li>
    3677                   <li><em>RFC1123</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC1123.1">6.1</a>, <a href="#rfc.xref.RFC1123.2">6.1</a>, <a href="#RFC1123"><b>11.2</b></a><ul>
     5085                  <li>Referer header field&nbsp;&nbsp;<a href="#rfc.xref.header.referer.1">3.2</a>, <a href="#rfc.iref.r.2"><b>11.7</b></a>, <a href="#rfc.xref.header.referer.2">12.3</a>, <a href="#rfc.xref.header.referer.3">C</a></li>
     5086                  <li>representation&nbsp;&nbsp;<a href="#rfc.iref.r.1">9</a></li>
     5087                  <li>Retry-After header field&nbsp;&nbsp;<a href="#rfc.xref.header.retry-after.1">3.3</a>, <a href="#rfc.xref.header.retry-after.2">4.7.4</a>, <a href="#rfc.iref.r.3"><b>11.8</b></a>, <a href="#rfc.xref.header.retry-after.3">12.3</a></li>
     5088                  <li><em>RFC1123</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC1123.1">6.1</a>, <a href="#rfc.xref.RFC1123.2">6.1</a>, <a href="#RFC1123"><b>15.2</b></a><ul>
    36785089                        <li><em>Section 5.2.14</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC1123.2">6.1</a></li>
    36795090                     </ul>
    36805091                  </li>
    3681                   <li><em>RFC1945</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC1945.1">4.5</a>, <a href="#RFC1945"><b>11.2</b></a><ul>