Ignore:
Timestamp:
Mar 30, 2012, 7:44:42 AM (7 years ago)
Author:
julian.reschke@…
Message:

Step 3 of p2/p3-merge (see #351)

Location:
draft-ietf-httpbis/latest
Files:
4 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p2-semantics.html

    r1640 r1641  
    589589      <ul class="toc">
    590590         <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>
     591               <li>1.1&nbsp;&nbsp;&nbsp;<a href="#terminology">Terminology</a></li>
     592               <li>1.2&nbsp;&nbsp;&nbsp;<a href="#intro.conformance.and.error.handling">Conformance and Error Handling</a></li>
     593               <li>1.3&nbsp;&nbsp;&nbsp;<a href="#notation">Syntax Notation</a><ul>
     594                     <li>1.3.1&nbsp;&nbsp;&nbsp;<a href="#core.rules">Core Rules</a></li>
     595                     <li>1.3.2&nbsp;&nbsp;&nbsp;<a href="#abnf.dependencies">ABNF Rules defined in other Parts of the Specification</a></li>
    595596                  </ul>
    596597               </li>
     
    771772         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>.
    772773      </p>
    773       <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>
    774       <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"
     774      <h2 id="rfc.section.1.1"><a href="#rfc.section.1.1">1.1</a>&nbsp;<a id="terminology" href="#terminology">Terminology</a></h2>
     775      <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>
     776      <p id="rfc.section.1.1.p.2"> <span id="rfc.iref.c.1"></span>  <dfn>content negotiation</dfn> 
     777      </p>
     778      <ul class="empty">
     779         <li>The mechanism for selecting the appropriate representation when servicing a request. The representation in any response can
     780            be negotiated (including error responses).
     781         </li>
     782      </ul>
     783      <p id="rfc.section.1.1.p.3"> <span id="rfc.iref.s.1"></span>  <dfn>selected representation</dfn> 
     784      </p>
     785      <ul class="empty">
     786         <li>The current representation of the target resource that would have been selected in a successful response if the same request
     787            had used the method GET and excluded any conditional request header fields.
     788         </li>
     789      </ul>
     790      <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>
     791      <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"
    775792         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>.
    776793      </p>
    777       <p id="rfc.section.1.1.p.2">This document defines conformance criteria for several roles in HTTP communication, including Senders, Recipients, Clients,
     794      <p id="rfc.section.1.2.p.2">This document defines conformance criteria for several roles in HTTP communication, including Senders, Recipients, Clients,
    778795         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.
    779796      </p>
    780       <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
     797      <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
    781798         SHOULD-level requirements are relevant here, unless one of the documented exceptions is applicable.
    782799      </p>
    783       <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.
    784       </p>
    785       <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
     800      <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.
     801      </p>
     802      <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
    786803         mechanisms, except in cases where it has direct impact on security. This is because different uses of the protocol require
    787804         different error handling strategies; for example, a Web browser may wish to transparently recover from a response where the
     
    789806         error recovery could lead to dangerous consequences.
    790807      </p>
    791       <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>
    792       <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.
    793       </p>
    794       <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
     808      <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>
     809      <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;B</a> shows the collected ABNF with the list rule expanded.
     810      </p>
     811      <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
    795812         (hexadecimal 0-9/A-F/a-f), HTAB (horizontal tab), LF (line feed), OCTET (any 8-bit sequence of data), SP (space), and VCHAR
    796813         (any visible US-ASCII character).
    797814      </p>
    798       <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>
    799       <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>:
     815      <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>
     816      <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>:
    800817      </p>
    801818      <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;
     
    805822  <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;
    806823  <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;
    807 </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>
    808       <p id="rfc.section.1.2.2.p.1">The ABNF rules below are defined in other parts:</p>
     824</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>
     825      <p id="rfc.section.1.3.2.p.1">The ABNF rules below are defined in other parts:</p>
    809826      <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;
    810827  <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;
     
    821838      </p>
    822839      <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>
    823       <div id="rfc.iref.s.1"></div>
     840      <div id="rfc.iref.s.2"></div>
    824841      <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>
    825842      <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
     
    10521069      <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.
    10531070      </p>
    1054       <div id="rfc.iref.c.1"></div>
     1071      <div id="rfc.iref.c.2"></div>
    10551072      <div id="rfc.iref.m.8"></div>
    10561073      <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>
     
    15911608         a request, then it need not forward the corresponding 100 (Continue) response(s).)
    15921609      </p>
    1593       <div id="rfc.iref.19"></div>
    1594       <div id="rfc.iref.s.2"></div>
     1610      <div id="rfc.iref.21"></div>
     1611      <div id="rfc.iref.s.3"></div>
    15951612      <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>
    15961613      <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
     
    15981615         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.
    15991616      </p>
    1600       <div id="rfc.iref.20"></div>
    1601       <div id="rfc.iref.s.3"></div>
     1617      <div id="rfc.iref.22"></div>
     1618      <div id="rfc.iref.s.4"></div>
    16021619      <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>
    16031620      <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
     
    16101627      <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>
    16111628      <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>
    1612       <div id="rfc.iref.21"></div>
    1613       <div id="rfc.iref.s.4"></div>
     1629      <div id="rfc.iref.23"></div>
     1630      <div id="rfc.iref.s.5"></div>
    16141631      <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>
    16151632      <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>
     
    16261643      <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.
    16271644      </p>
    1628       <div id="rfc.iref.22"></div>
    1629       <div id="rfc.iref.s.5"></div>
     1645      <div id="rfc.iref.24"></div>
     1646      <div id="rfc.iref.s.6"></div>
    16301647      <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>
    16311648      <p id="rfc.section.4.4.2.p.1">The request has been fulfilled and has resulted in a new resource being created.</p>
     
    16391656         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>).
    16401657      </p>
    1641       <div id="rfc.iref.23"></div>
    1642       <div id="rfc.iref.s.6"></div>
     1658      <div id="rfc.iref.25"></div>
     1659      <div id="rfc.iref.s.7"></div>
    16431660      <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>
    16441661      <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
     
    16511668         user can expect the request to be fulfilled.
    16521669      </p>
    1653       <div id="rfc.iref.24"></div>
    1654       <div id="rfc.iref.s.7"></div>
     1670      <div id="rfc.iref.26"></div>
     1671      <div id="rfc.iref.s.8"></div>
    16551672      <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>
    16561673      <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>).
     
    16611678      <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.
    16621679      </p>
    1663       <div id="rfc.iref.25"></div>
    1664       <div id="rfc.iref.s.8"></div>
     1680      <div id="rfc.iref.27"></div>
     1681      <div id="rfc.iref.s.9"></div>
    16651682      <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>
    16661683      <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
     
    16821699      <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.
    16831700      </p>
    1684       <div id="rfc.iref.26"></div>
    1685       <div id="rfc.iref.s.9"></div>
     1701      <div id="rfc.iref.28"></div>
     1702      <div id="rfc.iref.s.10"></div>
    16861703      <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>
    16871704      <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
     
    17381755         </p>
    17391756      </div>
    1740       <div id="rfc.iref.27"></div>
    1741       <div id="rfc.iref.s.10"></div>
     1757      <div id="rfc.iref.29"></div>
     1758      <div id="rfc.iref.s.11"></div>
    17421759      <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>
    17431760      <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
     
    17531770      <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.
    17541771      </p>
    1755       <div id="rfc.iref.28"></div>
    1756       <div id="rfc.iref.s.11"></div>
     1772      <div id="rfc.iref.30"></div>
     1773      <div id="rfc.iref.s.12"></div>
    17571774      <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>
    17581775      <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
     
    17691786         </p>
    17701787      </div>
    1771       <div id="rfc.iref.29"></div>
    1772       <div id="rfc.iref.s.12"></div>
     1788      <div id="rfc.iref.31"></div>
     1789      <div id="rfc.iref.s.13"></div>
    17731790      <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>
    17741791      <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.
     
    17821799         </p>
    17831800      </div>
    1784       <div id="rfc.iref.30"></div>
    1785       <div id="rfc.iref.s.13"></div>
     1801      <div id="rfc.iref.32"></div>
     1802      <div id="rfc.iref.s.14"></div>
    17861803      <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>
    17871804      <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
     
    18031820      <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.
    18041821      </p>
    1805       <div id="rfc.iref.31"></div>
    1806       <div id="rfc.iref.s.14"></div>
     1822      <div id="rfc.iref.33"></div>
     1823      <div id="rfc.iref.s.15"></div>
    18071824      <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>
    18081825      <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.
    18091826      </p>
    1810       <div id="rfc.iref.32"></div>
    1811       <div id="rfc.iref.s.15"></div>
     1827      <div id="rfc.iref.34"></div>
     1828      <div id="rfc.iref.s.16"></div>
    18121829      <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>
    18131830      <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>
    1814       <div id="rfc.iref.33"></div>
    1815       <div id="rfc.iref.s.16"></div>
     1831      <div id="rfc.iref.35"></div>
     1832      <div id="rfc.iref.s.17"></div>
    18161833      <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>
    18171834      <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.
     
    18301847         These status codes are applicable to any request method. User agents <em class="bcp14">SHOULD</em> display any included representation to the user.
    18311848      </p>
    1832       <div id="rfc.iref.34"></div>
    1833       <div id="rfc.iref.s.17"></div>
     1849      <div id="rfc.iref.36"></div>
     1850      <div id="rfc.iref.s.18"></div>
    18341851      <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>
    18351852      <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>
    1836       <div id="rfc.iref.35"></div>
    1837       <div id="rfc.iref.s.18"></div>
     1853      <div id="rfc.iref.37"></div>
     1854      <div id="rfc.iref.s.19"></div>
    18381855      <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>
    18391856      <p id="rfc.section.4.6.2.p.1">This code is reserved for future use.</p>
    1840       <div id="rfc.iref.36"></div>
    1841       <div id="rfc.iref.s.19"></div>
     1857      <div id="rfc.iref.38"></div>
     1858      <div id="rfc.iref.s.20"></div>
    18421859      <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>
    18431860      <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
     
    18471864         to the client, the status code 404 (Not Found) <em class="bcp14">MAY</em> be used instead.
    18481865      </p>
    1849       <div id="rfc.iref.37"></div>
    1850       <div id="rfc.iref.s.20"></div>
     1866      <div id="rfc.iref.39"></div>
     1867      <div id="rfc.iref.s.21"></div>
    18511868      <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>
    18521869      <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
     
    18551872         has been refused, or when no other response is applicable.
    18561873      </p>
    1857       <div id="rfc.iref.38"></div>
    1858       <div id="rfc.iref.s.21"></div>
     1874      <div id="rfc.iref.40"></div>
     1875      <div id="rfc.iref.s.22"></div>
    18591876      <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>
    18601877      <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.
    18611878      </p>
    1862       <div id="rfc.iref.39"></div>
    1863       <div id="rfc.iref.s.22"></div>
     1879      <div id="rfc.iref.41"></div>
     1880      <div id="rfc.iref.s.23"></div>
    18641881      <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>
    18651882      <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
     
    18781895      <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.
    18791896      </p>
    1880       <div id="rfc.iref.40"></div>
    1881       <div id="rfc.iref.s.23"></div>
     1897      <div id="rfc.iref.42"></div>
     1898      <div id="rfc.iref.s.24"></div>
    18821899      <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>
    18831900      <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.
    18841901      </p>
    1885       <div id="rfc.iref.41"></div>
    1886       <div id="rfc.iref.s.24"></div>
     1902      <div id="rfc.iref.43"></div>
     1903      <div id="rfc.iref.s.25"></div>
    18871904      <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>
    18881905      <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
     
    18961913         contain a list of the differences between the two versions.
    18971914      </p>
    1898       <div id="rfc.iref.42"></div>
    1899       <div id="rfc.iref.s.25"></div>
     1915      <div id="rfc.iref.44"></div>
     1916      <div id="rfc.iref.s.26"></div>
    19001917      <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>
    19011918      <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
     
    19111928      <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.
    19121929      </p>
    1913       <div id="rfc.iref.43"></div>
    1914       <div id="rfc.iref.s.26"></div>
     1930      <div id="rfc.iref.45"></div>
     1931      <div id="rfc.iref.s.27"></div>
    19151932      <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>
    19161933      <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
    19171934         message.
    19181935      </p>
    1919       <div id="rfc.iref.44"></div>
    1920       <div id="rfc.iref.s.27"></div>
     1936      <div id="rfc.iref.46"></div>
     1937      <div id="rfc.iref.s.28"></div>
    19211938      <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>
    19221939      <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
     
    19251942      <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.
    19261943      </p>
    1927       <div id="rfc.iref.45"></div>
    1928       <div id="rfc.iref.s.28"></div>
     1944      <div id="rfc.iref.47"></div>
     1945      <div id="rfc.iref.s.29"></div>
    19291946      <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>
    19301947      <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.
     
    19341951         in some servers using fixed-length buffers for reading or manipulating the request-target.
    19351952      </p>
    1936       <div id="rfc.iref.46"></div>
    1937       <div id="rfc.iref.s.29"></div>
     1953      <div id="rfc.iref.48"></div>
     1954      <div id="rfc.iref.s.30"></div>
    19381955      <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>
    19391956      <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
    19401957         on the target resource.
    19411958      </p>
    1942       <div id="rfc.iref.47"></div>
    1943       <div id="rfc.iref.s.30"></div>
     1959      <div id="rfc.iref.49"></div>
     1960      <div id="rfc.iref.s.31"></div>
    19441961      <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>
    19451962      <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
    19461963         not be met by the next-hop server.
    19471964      </p>
    1948       <div id="rfc.iref.48"></div>
    1949       <div id="rfc.iref.s.31"></div>
     1965      <div id="rfc.iref.50"></div>
     1966      <div id="rfc.iref.s.32"></div>
    19501967      <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>
    19511968      <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.
     
    19671984         User agents <em class="bcp14">SHOULD</em> display any included representation to the user. These response codes are applicable to any request method.
    19681985      </p>
    1969       <div id="rfc.iref.49"></div>
    1970       <div id="rfc.iref.s.32"></div>
     1986      <div id="rfc.iref.51"></div>
     1987      <div id="rfc.iref.s.33"></div>
    19711988      <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>
    19721989      <p id="rfc.section.4.7.1.p.1">The server encountered an unexpected condition which prevented it from fulfilling the request.</p>
    1973       <div id="rfc.iref.50"></div>
    1974       <div id="rfc.iref.s.33"></div>
     1990      <div id="rfc.iref.52"></div>
     1991      <div id="rfc.iref.s.34"></div>
    19751992      <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>
    19761993      <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
    19771994         does not recognize the request method and is not capable of supporting it for any resource.
    19781995      </p>
    1979       <div id="rfc.iref.51"></div>
    1980       <div id="rfc.iref.s.34"></div>
     1996      <div id="rfc.iref.53"></div>
     1997      <div id="rfc.iref.s.35"></div>
    19811998      <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>
    19821999      <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
    19832000         to fulfill the request.
    19842001      </p>
    1985       <div id="rfc.iref.52"></div>
    1986       <div id="rfc.iref.s.35"></div>
     2002      <div id="rfc.iref.54"></div>
     2003      <div id="rfc.iref.s.36"></div>
    19872004      <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>
    19882005      <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>
     
    19952012         </p>
    19962013      </div>
    1997       <div id="rfc.iref.53"></div>
    1998       <div id="rfc.iref.s.36"></div>
     2014      <div id="rfc.iref.55"></div>
     2015      <div id="rfc.iref.s.37"></div>
    19992016      <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>
    20002017      <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
     
    20052022         </p>
    20062023      </div>
    2007       <div id="rfc.iref.54"></div>
    2008       <div id="rfc.iref.s.37"></div>
     2024      <div id="rfc.iref.56"></div>
     2025      <div id="rfc.iref.s.38"></div>
    20092026      <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>
    20102027      <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
     
    22052222      </p>
    22062223      <p id="rfc.section.7.3.p.4">The only expectation defined by this specification is:</p>
    2207       <p id="rfc.section.7.3.p.5"><span id="rfc.iref.86"></span><span id="rfc.iref.e.2"></span> 100-continue
     2224      <p id="rfc.section.7.3.p.5"><span id="rfc.iref.88"></span><span id="rfc.iref.e.2"></span> 100-continue
    22082225      </p>
    22092226      <ul class="empty">
     
    22572274      <div class="note" id="rfc.section.7.5.p.7">
    22582275         <p> <b>Note:</b> Some recipients attempt to recover from Location fields that are not valid URI references. This specification does not mandate
    2259             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>).
     2276            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>).
    22602277         </p>
    22612278      </div>
     
    23162333  Retry-After: 120
    23172334</pre><p id="rfc.section.7.8.p.8">In the latter example, the delay is 2 minutes.</p>
    2318       <div id="rfc.iref.s.38"></div>
     2335      <div id="rfc.iref.s.39"></div>
    23192336      <div id="rfc.iref.h.10"></div>
    23202337      <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>
     
    35013518         <ul class="ind">
    35023519            <li><a id="rfc.index.1" href="#rfc.index.1"><b>1</b></a><ul>
    3503                   <li>100 Continue (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.100.1">4.1</a>, <a href="#rfc.iref.19"><b>4.3.1</b></a>, <a href="#rfc.xref.status.100.2">8.2</a></li>
    3504                   <li>100-continue (expect value)&nbsp;&nbsp;<a href="#rfc.iref.86"><b>7.3</b></a></li>
    3505                   <li>101 Switching Protocols (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.101.1">4.1</a>, <a href="#rfc.iref.20"><b>4.3.2</b></a>, <a href="#rfc.xref.status.101.2">8.2</a></li>
     3520                  <li>100 Continue (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.100.1">4.1</a>, <a href="#rfc.iref.21"><b>4.3.1</b></a>, <a href="#rfc.xref.status.100.2">8.2</a></li>
     3521                  <li>100-continue (expect value)&nbsp;&nbsp;<a href="#rfc.iref.88"><b>7.3</b></a></li>
     3522                  <li>101 Switching Protocols (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.101.1">4.1</a>, <a href="#rfc.iref.22"><b>4.3.2</b></a>, <a href="#rfc.xref.status.101.2">8.2</a></li>
    35063523               </ul>
    35073524            </li>
    35083525            <li><a id="rfc.index.2" href="#rfc.index.2"><b>2</b></a><ul>
    3509                   <li>200 OK (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.200.1">4.1</a>, <a href="#rfc.iref.21"><b>4.4.1</b></a>, <a href="#rfc.xref.status.200.2">8.2</a></li>
    3510                   <li>201 Created (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.201.1">4.1</a>, <a href="#rfc.iref.22"><b>4.4.2</b></a>, <a href="#rfc.xref.status.201.2">8.2</a></li>
    3511                   <li>202 Accepted (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.202.1">4.1</a>, <a href="#rfc.iref.23"><b>4.4.3</b></a>, <a href="#rfc.xref.status.202.2">8.2</a></li>
    3512                   <li>203 Non-Authoritative Information (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.203.1">4.1</a>, <a href="#rfc.iref.24"><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>
    3513                   <li>204 No Content (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.204.1">4.1</a>, <a href="#rfc.iref.25"><b>4.4.5</b></a>, <a href="#rfc.xref.status.204.2">8.2</a></li>
    3514                   <li>205 Reset Content (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.205.1">4.1</a>, <a href="#rfc.iref.26"><b>4.4.6</b></a>, <a href="#rfc.xref.status.205.2">8.2</a></li>
     3526                  <li>200 OK (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.200.1">4.1</a>, <a href="#rfc.iref.23"><b>4.4.1</b></a>, <a href="#rfc.xref.status.200.2">8.2</a></li>
     3527                  <li>201 Created (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.201.1">4.1</a>, <a href="#rfc.iref.24"><b>4.4.2</b></a>, <a href="#rfc.xref.status.201.2">8.2</a></li>
     3528                  <li>202 Accepted (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.202.1">4.1</a>, <a href="#rfc.iref.25"><b>4.4.3</b></a>, <a href="#rfc.xref.status.202.2">8.2</a></li>
     3529                  <li>203 Non-Authoritative Information (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.203.1">4.1</a>, <a href="#rfc.iref.26"><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>
     3530                  <li>204 No Content (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.204.1">4.1</a>, <a href="#rfc.iref.27"><b>4.4.5</b></a>, <a href="#rfc.xref.status.204.2">8.2</a></li>
     3531                  <li>205 Reset Content (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.205.1">4.1</a>, <a href="#rfc.iref.28"><b>4.4.6</b></a>, <a href="#rfc.xref.status.205.2">8.2</a></li>
    35153532               </ul>
    35163533            </li>
    35173534            <li><a id="rfc.index.3" href="#rfc.index.3"><b>3</b></a><ul>
    3518                   <li>300 Multiple Choices (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.300.1">4.1</a>, <a href="#rfc.iref.27"><b>4.5.1</b></a>, <a href="#rfc.xref.status.300.2">8.2</a></li>
    3519                   <li>301 Moved Permanently (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.301.1">4.1</a>, <a href="#rfc.iref.28"><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>
    3520                   <li>302 Found (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.302.1">4.1</a>, <a href="#rfc.iref.29"><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>
    3521                   <li>303 See Other (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.303.1">4.1</a>, <a href="#rfc.iref.30"><b>4.5.4</b></a>, <a href="#rfc.xref.status.303.2">8.2</a></li>
    3522                   <li>305 Use Proxy (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.305.1">4.1</a>, <a href="#rfc.iref.31"><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>
    3523                   <li>306 (Unused) (status code)&nbsp;&nbsp;<a href="#rfc.iref.32"><b>4.5.6</b></a>, <a href="#rfc.xref.status.306.1">8.2</a></li>
    3524                   <li>307 Temporary Redirect (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.307.1">4.1</a>, <a href="#rfc.iref.33"><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>
     3535                  <li>300 Multiple Choices (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.300.1">4.1</a>, <a href="#rfc.iref.29"><b>4.5.1</b></a>, <a href="#rfc.xref.status.300.2">8.2</a></li>
     3536                  <li>301 Moved Permanently (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.301.1">4.1</a>, <a href="#rfc.iref.30"><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>
     3537                  <li>302 Found (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.302.1">4.1</a>, <a href="#rfc.iref.31"><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>
     3538                  <li>303 See Other (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.303.1">4.1</a>, <a href="#rfc.iref.32"><b>4.5.4</b></a>, <a href="#rfc.xref.status.303.2">8.2</a></li>
     3539                  <li>305 Use Proxy (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.305.1">4.1</a>, <a href="#rfc.iref.33"><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>
     3540                  <li>306 (Unused) (status code)&nbsp;&nbsp;<a href="#rfc.iref.34"><b>4.5.6</b></a>, <a href="#rfc.xref.status.306.1">8.2</a></li>
     3541                  <li>307 Temporary Redirect (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.307.1">4.1</a>, <a href="#rfc.iref.35"><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>
    35253542               </ul>
    35263543            </li>
    35273544            <li><a id="rfc.index.4" href="#rfc.index.4"><b>4</b></a><ul>
    3528                   <li>400 Bad Request (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.400.1">4.1</a>, <a href="#rfc.iref.34"><b>4.6.1</b></a>, <a href="#rfc.xref.status.400.2">8.2</a></li>
    3529                   <li>402 Payment Required (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.402.1">4.1</a>, <a href="#rfc.iref.35"><b>4.6.2</b></a>, <a href="#rfc.xref.status.402.2">8.2</a></li>
    3530                   <li>403 Forbidden (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.403.1">4.1</a>, <a href="#rfc.iref.36"><b>4.6.3</b></a>, <a href="#rfc.xref.status.403.2">8.2</a></li>
    3531                   <li>404 Not Found (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.404.1">4.1</a>, <a href="#rfc.iref.37"><b>4.6.4</b></a>, <a href="#rfc.xref.status.404.2">8.2</a></li>
    3532                   <li>405 Method Not Allowed (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.405.1">4.1</a>, <a href="#rfc.iref.38"><b>4.6.5</b></a>, <a href="#rfc.xref.status.405.2">8.2</a></li>
    3533                   <li>406 Not Acceptable (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.406.1">4.1</a>, <a href="#rfc.iref.39"><b>4.6.6</b></a>, <a href="#rfc.xref.status.406.2">8.2</a></li>
    3534                   <li>408 Request Timeout (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.408.1">4.1</a>, <a href="#rfc.iref.40"><b>4.6.7</b></a>, <a href="#rfc.xref.status.408.2">8.2</a></li>
    3535                   <li>409 Conflict (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.409.1">4.1</a>, <a href="#rfc.iref.41"><b>4.6.8</b></a>, <a href="#rfc.xref.status.409.2">8.2</a></li>
    3536                   <li>410 Gone (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.410.1">4.1</a>, <a href="#rfc.iref.42"><b>4.6.9</b></a>, <a href="#rfc.xref.status.410.2">8.2</a></li>
    3537                   <li>411 Length Required (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.411.1">4.1</a>, <a href="#rfc.iref.43"><b>4.6.10</b></a>, <a href="#rfc.xref.status.411.2">8.2</a></li>
    3538                   <li>413 Request Representation Too Large (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.413.1">4.1</a>, <a href="#rfc.iref.44"><b>4.6.11</b></a>, <a href="#rfc.xref.status.413.2">8.2</a></li>
    3539                   <li>414 URI Too Long (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.414.1">4.1</a>, <a href="#rfc.iref.45"><b>4.6.12</b></a>, <a href="#rfc.xref.status.414.2">8.2</a></li>
    3540                   <li>415 Unsupported Media Type (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.415.1">4.1</a>, <a href="#rfc.iref.46"><b>4.6.13</b></a>, <a href="#rfc.xref.status.415.2">8.2</a></li>
    3541                   <li>417 Expectation Failed (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.417.1">4.1</a>, <a href="#rfc.iref.47"><b>4.6.14</b></a>, <a href="#rfc.xref.status.417.2">8.2</a></li>
    3542                   <li>426 Upgrade Required (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.426.1">4.1</a>, <a href="#rfc.iref.48"><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>
     3545                  <li>400 Bad Request (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.400.1">4.1</a>, <a href="#rfc.iref.36"><b>4.6.1</b></a>, <a href="#rfc.xref.status.400.2">8.2</a></li>
     3546                  <li>402 Payment Required (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.402.1">4.1</a>, <a href="#rfc.iref.37"><b>4.6.2</b></a>, <a href="#rfc.xref.status.402.2">8.2</a></li>
     3547                  <li>403 Forbidden (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.403.1">4.1</a>, <a href="#rfc.iref.38"><b>4.6.3</b></a>, <a href="#rfc.xref.status.403.2">8.2</a></li>
     3548                  <li>404 Not Found (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.404.1">4.1</a>, <a href="#rfc.iref.39"><b>4.6.4</b></a>, <a href="#rfc.xref.status.404.2">8.2</a></li>
     3549                  <li>405 Method Not Allowed (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.405.1">4.1</a>, <a href="#rfc.iref.40"><b>4.6.5</b></a>, <a href="#rfc.xref.status.405.2">8.2</a></li>
     3550                  <li>406 Not Acceptable (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.406.1">4.1</a>, <a href="#rfc.iref.41"><b>4.6.6</b></a>, <a href="#rfc.xref.status.406.2">8.2</a></li>
     3551                  <li>408 Request Timeout (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.408.1">4.1</a>, <a href="#rfc.iref.42"><b>4.6.7</b></a>, <a href="#rfc.xref.status.408.2">8.2</a></li>
     3552                  <li>409 Conflict (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.409.1">4.1</a>, <a href="#rfc.iref.43"><b>4.6.8</b></a>, <a href="#rfc.xref.status.409.2">8.2</a></li>
     3553                  <li>410 Gone (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.410.1">4.1</a>, <a href="#rfc.iref.44"><b>4.6.9</b></a>, <a href="#rfc.xref.status.410.2">8.2</a></li>
     3554                  <li>411 Length Required (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.411.1">4.1</a>, <a href="#rfc.iref.45"><b>4.6.10</b></a>, <a href="#rfc.xref.status.411.2">8.2</a></li>
     3555                  <li>413 Request Representation Too Large (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.413.1">4.1</a>, <a href="#rfc.iref.46"><b>4.6.11</b></a>, <a href="#rfc.xref.status.413.2">8.2</a></li>
     3556                  <li>414 URI Too Long (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.414.1">4.1</a>, <a href="#rfc.iref.47"><b>4.6.12</b></a>, <a href="#rfc.xref.status.414.2">8.2</a></li>
     3557                  <li>415 Unsupported Media Type (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.415.1">4.1</a>, <a href="#rfc.iref.48"><b>4.6.13</b></a>, <a href="#rfc.xref.status.415.2">8.2</a></li>
     3558                  <li>417 Expectation Failed (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.417.1">4.1</a>, <a href="#rfc.iref.49"><b>4.6.14</b></a>, <a href="#rfc.xref.status.417.2">8.2</a></li>
     3559                  <li>426 Upgrade Required (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.426.1">4.1</a>, <a href="#rfc.iref.50"><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>
    35433560               </ul>
    35443561            </li>
    35453562            <li><a id="rfc.index.5" href="#rfc.index.5"><b>5</b></a><ul>
    3546                   <li>500 Internal Server Error (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.500.1">4.1</a>, <a href="#rfc.iref.49"><b>4.7.1</b></a>, <a href="#rfc.xref.status.500.2">8.2</a></li>
    3547                   <li>501 Not Implemented (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.501.1">4.1</a>, <a href="#rfc.iref.50"><b>4.7.2</b></a>, <a href="#rfc.xref.status.501.2">8.2</a></li>
    3548                   <li>502 Bad Gateway (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.502.1">4.1</a>, <a href="#rfc.iref.51"><b>4.7.3</b></a>, <a href="#rfc.xref.status.502.2">8.2</a></li>
    3549                   <li>503 Service Unavailable (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.503.1">4.1</a>, <a href="#rfc.iref.52"><b>4.7.4</b></a>, <a href="#rfc.xref.status.503.2">8.2</a></li>
    3550                   <li>504 Gateway Timeout (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.504.1">4.1</a>, <a href="#rfc.iref.53"><b>4.7.5</b></a>, <a href="#rfc.xref.status.504.2">8.2</a></li>
    3551                   <li>505 HTTP Version Not Supported (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.505.1">4.1</a>, <a href="#rfc.iref.54"><b>4.7.6</b></a>, <a href="#rfc.xref.status.505.2">8.2</a></li>
     3563                  <li>500 Internal Server Error (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.500.1">4.1</a>, <a href="#rfc.iref.51"><b>4.7.1</b></a>, <a href="#rfc.xref.status.500.2">8.2</a></li>
     3564                  <li>501 Not Implemented (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.501.1">4.1</a>, <a href="#rfc.iref.52"><b>4.7.2</b></a>, <a href="#rfc.xref.status.501.2">8.2</a></li>
     3565                  <li>502 Bad Gateway (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.502.1">4.1</a>, <a href="#rfc.iref.53"><b>4.7.3</b></a>, <a href="#rfc.xref.status.502.2">8.2</a></li>
     3566                  <li>503 Service Unavailable (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.503.1">4.1</a>, <a href="#rfc.iref.54"><b>4.7.4</b></a>, <a href="#rfc.xref.status.503.2">8.2</a></li>
     3567                  <li>504 Gateway Timeout (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.504.1">4.1</a>, <a href="#rfc.iref.55"><b>4.7.5</b></a>, <a href="#rfc.xref.status.504.2">8.2</a></li>
     3568                  <li>505 HTTP Version Not Supported (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.505.1">4.1</a>, <a href="#rfc.iref.56"><b>4.7.6</b></a>, <a href="#rfc.xref.status.505.2">8.2</a></li>
    35523569               </ul>
    35533570            </li>
     
    35573574            </li>
    35583575            <li><a id="rfc.index.C" href="#rfc.index.C"><b>C</b></a><ul>
    3559                   <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>
     3576                  <li>CONNECT method&nbsp;&nbsp;<a href="#rfc.iref.c.2"><b>2.3.8</b></a>, <a href="#rfc.xref.CONNECT.1">8.1</a>, <a href="#rfc.xref.CONNECT.2">A</a></li>
     3577                  <li>content negotiation&nbsp;&nbsp;<a href="#rfc.iref.c.1">1.1</a></li>
    35603578               </ul>
    35613579            </li>
     
    36683686            </li>
    36693687            <li><a id="rfc.index.P" href="#rfc.index.P"><b>P</b></a><ul>
    3670                   <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>
    3671                         <li><em>Section 1.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.3">1.2</a></li>
    3672                         <li><em>Section 2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.2">1.1</a></li>
     3688                  <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.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>
     3689                        <li><em>Section 1.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.3">1.3</a></li>
     3690                        <li><em>Section 2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.2">1.2</a></li>
    36733691                        <li><em>Section 2.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.32">4.4.4</a></li>
    36743692                        <li><em>Section 2.6</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.35">4.7.6</a></li>
    3675                         <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>
    3676                         <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>
     3693                        <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>
     3694                        <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>
    36773695                        <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>
    3678                         <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>
     3696                        <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>
    36793697                        <li><em>Section 3.2.5</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.22">3.1</a></li>
    36803698                        <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>
     
    37733791                  </li>
    37743792                  <li><em>RFC2076</em>&nbsp;&nbsp;<a href="#RFC2076"><b>11.2</b></a></li>
    3775                   <li><em>RFC2119</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2119.1">1.1</a>, <a href="#RFC2119"><b>11.1</b></a></li>
     3793                  <li><em>RFC2119</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2119.1">1.2</a>, <a href="#RFC2119"><b>11.1</b></a></li>
    37763794                  <li><em>RFC2277</em>&nbsp;&nbsp;<a href="#RFC2277"><b>11.2</b></a></li>
    37773795                  <li><em>RFC2295</em>&nbsp;&nbsp;<a href="#RFC2295"><b>11.2</b></a></li>
     
    38023820                     </ul>
    38033821                  </li>
    3804                   <li><em>RFC5234</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5234.1">1.2</a>, <a href="#rfc.xref.RFC5234.2">1.2</a>, <a href="#rfc.xref.RFC5234.3">3.1</a>, <a href="#RFC5234"><b>11.1</b></a><ul>
    3805                         <li><em>Appendix B.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5234.2">1.2</a></li>
     3822                  <li><em>RFC5234</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5234.1">1.3</a>, <a href="#rfc.xref.RFC5234.2">1.3</a>, <a href="#rfc.xref.RFC5234.3">3.1</a>, <a href="#RFC5234"><b>11.1</b></a><ul>
     3823                        <li><em>Appendix B.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5234.2">1.3</a></li>
    38063824                     </ul>
    38073825                  </li>
     
    38203838            </li>
    38213839            <li><a id="rfc.index.S" href="#rfc.index.S"><b>S</b></a><ul>
    3822                   <li>Safe Methods&nbsp;&nbsp;<a href="#rfc.iref.s.1"><b>2.1.1</b></a></li>
    3823                   <li>Server header field&nbsp;&nbsp;<a href="#rfc.xref.header.server.1">3.3</a>, <a href="#rfc.iref.s.38"><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>
     3840                  <li>Safe Methods&nbsp;&nbsp;<a href="#rfc.iref.s.2"><b>2.1.1</b></a></li>
     3841                  <li>selected representation&nbsp;&nbsp;<a href="#rfc.iref.s.1"><b>1.1</b></a></li>
     3842                  <li>Server header field&nbsp;&nbsp;<a href="#rfc.xref.header.server.1">3.3</a>, <a href="#rfc.iref.s.39"><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>
    38243843                  <li>Status Codes&nbsp;&nbsp;
    38253844                     <ul>
    3826                         <li>100 Continue&nbsp;&nbsp;<a href="#rfc.xref.status.100.1">4.1</a>, <a href="#rfc.iref.s.2"><b>4.3.1</b></a>, <a href="#rfc.xref.status.100.2">8.2</a></li>
    3827                         <li>101 Switching Protocols&nbsp;&nbsp;<a href="#rfc.xref.status.101.1">4.1</a>, <a href="#rfc.iref.s.3"><b>4.3.2</b></a>, <a href="#rfc.xref.status.101.2">8.2</a></li>
    3828                         <li>200 OK&nbsp;&nbsp;<a href="#rfc.xref.status.200.1">4.1</a>, <a href="#rfc.iref.s.4"><b>4.4.1</b></a>, <a href="#rfc.xref.status.200.2">8.2</a></li>
    3829                         <li>201 Created&nbsp;&nbsp;<a href="#rfc.xref.status.201.1">4.1</a>, <a href="#rfc.iref.s.5"><b>4.4.2</b></a>, <a href="#rfc.xref.status.201.2">8.2</a></li>
    3830                         <li>202 Accepted&nbsp;&nbsp;<a href="#rfc.xref.status.202.1">4.1</a>, <a href="#rfc.iref.s.6"><b>4.4.3</b></a>, <a href="#rfc.xref.status.202.2">8.2</a></li>
    3831                         <li>203 Non-Authoritative Information&nbsp;&nbsp;<a href="#rfc.xref.status.203.1">4.1</a>, <a href="#rfc.iref.s.7"><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>
    3832                         <li>204 No Content&nbsp;&nbsp;<a href="#rfc.xref.status.204.1">4.1</a>, <a href="#rfc.iref.s.8"><b>4.4.5</b></a>, <a href="#rfc.xref.status.204.2">8.2</a></li>
    3833                         <li>205 Reset Content&nbsp;&nbsp;<a href="#rfc.xref.status.205.1">4.1</a>, <a href="#rfc.iref.s.9"><b>4.4.6</b></a>, <a href="#rfc.xref.status.205.2">8.2</a></li>
    3834                         <li>300 Multiple Choices&nbsp;&nbsp;<a href="#rfc.xref.status.300.1">4.1</a>, <a href="#rfc.iref.s.10"><b>4.5.1</b></a>, <a href="#rfc.xref.status.300.2">8.2</a></li>
    3835                         <li>301 Moved Permanently&nbsp;&nbsp;<a href="#rfc.xref.status.301.1">4.1</a>, <a href="#rfc.iref.s.11"><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>
    3836                         <li>302 Found&nbsp;&nbsp;<a href="#rfc.xref.status.302.1">4.1</a>, <a href="#rfc.iref.s.12"><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>
    3837                         <li>303 See Other&nbsp;&nbsp;<a href="#rfc.xref.status.303.1">4.1</a>, <a href="#rfc.iref.s.13"><b>4.5.4</b></a>, <a href="#rfc.xref.status.303.2">8.2</a></li>
    3838                         <li>305 Use Proxy&nbsp;&nbsp;<a href="#rfc.xref.status.305.1">4.1</a>, <a href="#rfc.iref.s.14"><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>
    3839                         <li>306 (Unused)&nbsp;&nbsp;<a href="#rfc.iref.s.15"><b>4.5.6</b></a>, <a href="#rfc.xref.status.306.1">8.2</a></li>
    3840                         <li>307 Temporary Redirect&nbsp;&nbsp;<a href="#rfc.xref.status.307.1">4.1</a>, <a href="#rfc.iref.s.16"><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>
    3841                         <li>400 Bad Request&nbsp;&nbsp;<a href="#rfc.xref.status.400.1">4.1</a>, <a href="#rfc.iref.s.17"><b>4.6.1</b></a>, <a href="#rfc.xref.status.400.2">8.2</a></li>
    3842                         <li>402 Payment Required&nbsp;&nbsp;<a href="#rfc.xref.status.402.1">4.1</a>, <a href="#rfc.iref.s.18"><b>4.6.2</b></a>, <a href="#rfc.xref.status.402.2">8.2</a></li>
    3843                         <li>403 Forbidden&nbsp;&nbsp;<a href="#rfc.xref.status.403.1">4.1</a>, <a href="#rfc.iref.s.19"><b>4.6.3</b></a>, <a href="#rfc.xref.status.403.2">8.2</a></li>
    3844                         <li>404 Not Found&nbsp;&nbsp;<a href="#rfc.xref.status.404.1">4.1</a>, <a href="#rfc.iref.s.20"><b>4.6.4</b></a>, <a href="#rfc.xref.status.404.2">8.2</a></li>
    3845                         <li>405 Method Not Allowed&nbsp;&nbsp;<a href="#rfc.xref.status.405.1">4.1</a>, <a href="#rfc.iref.s.21"><b>4.6.5</b></a>, <a href="#rfc.xref.status.405.2">8.2</a></li>
    3846                         <li>406 Not Acceptable&nbsp;&nbsp;<a href="#rfc.xref.status.406.1">4.1</a>, <a href="#rfc.iref.s.22"><b>4.6.6</b></a>, <a href="#rfc.xref.status.406.2">8.2</a></li>
    3847                         <li>408 Request Timeout&nbsp;&nbsp;<a href="#rfc.xref.status.408.1">4.1</a>, <a href="#rfc.iref.s.23"><b>4.6.7</b></a>, <a href="#rfc.xref.status.408.2">8.2</a></li>
    3848                         <li>409 Conflict&nbsp;&nbsp;<a href="#rfc.xref.status.409.1">4.1</a>, <a href="#rfc.iref.s.24"><b>4.6.8</b></a>, <a href="#rfc.xref.status.409.2">8.2</a></li>
    3849                         <li>410 Gone&nbsp;&nbsp;<a href="#rfc.xref.status.410.1">4.1</a>, <a href="#rfc.iref.s.25"><b>4.6.9</b></a>, <a href="#rfc.xref.status.410.2">8.2</a></li>
    3850                         <li>411 Length Required&nbsp;&nbsp;<a href="#rfc.xref.status.411.1">4.1</a>, <a href="#rfc.iref.s.26"><b>4.6.10</b></a>, <a href="#rfc.xref.status.411.2">8.2</a></li>
    3851                         <li>413 Request Representation Too Large&nbsp;&nbsp;<a href="#rfc.xref.status.413.1">4.1</a>, <a href="#rfc.iref.s.27"><b>4.6.11</b></a>, <a href="#rfc.xref.status.413.2">8.2</a></li>
    3852                         <li>414 URI Too Long&nbsp;&nbsp;<a href="#rfc.xref.status.414.1">4.1</a>, <a href="#rfc.iref.s.28"><b>4.6.12</b></a>, <a href="#rfc.xref.status.414.2">8.2</a></li>
    3853                         <li>415 Unsupported Media Type&nbsp;&nbsp;<a href="#rfc.xref.status.415.1">4.1</a>, <a href="#rfc.iref.s.29"><b>4.6.13</b></a>, <a href="#rfc.xref.status.415.2">8.2</a></li>
    3854                         <li>417 Expectation Failed&nbsp;&nbsp;<a href="#rfc.xref.status.417.1">4.1</a>, <a href="#rfc.iref.s.30"><b>4.6.14</b></a>, <a href="#rfc.xref.status.417.2">8.2</a></li>
    3855                         <li>426 Upgrade Required&nbsp;&nbsp;<a href="#rfc.xref.status.426.1">4.1</a>, <a href="#rfc.iref.s.31"><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>
    3856                         <li>500 Internal Server Error&nbsp;&nbsp;<a href="#rfc.xref.status.500.1">4.1</a>, <a href="#rfc.iref.s.32"><b>4.7.1</b></a>, <a href="#rfc.xref.status.500.2">8.2</a></li>
    3857                         <li>501 Not Implemented&nbsp;&nbsp;<a href="#rfc.xref.status.501.1">4.1</a>, <a href="#rfc.iref.s.33"><b>4.7.2</b></a>, <a href="#rfc.xref.status.501.2">8.2</a></li>
    3858                         <li>502 Bad Gateway&nbsp;&nbsp;<a href="#rfc.xref.status.502.1">4.1</a>, <a href="#rfc.iref.s.34"><b>4.7.3</b></a>, <a href="#rfc.xref.status.502.2">8.2</a></li>
    3859                         <li>503 Service Unavailable&nbsp;&nbsp;<a href="#rfc.xref.status.503.1">4.1</a>, <a href="#rfc.iref.s.35"><b>4.7.4</b></a>, <a href="#rfc.xref.status.503.2">8.2</a></li>
    3860                         <li>504 Gateway Timeout&nbsp;&nbsp;<a href="#rfc.xref.status.504.1">4.1</a>, <a href="#rfc.iref.s.36"><b>4.7.5</b></a>, <a href="#rfc.xref.status.504.2">8.2</a></li>
    3861                         <li>505 HTTP Version Not Supported&nbsp;&nbsp;<a href="#rfc.xref.status.505.1">4.1</a>, <a href="#rfc.iref.s.37"><b>4.7.6</b></a>, <a href="#rfc.xref.status.505.2">8.2</a></li>
     3845                        <li>100 Continue&nbsp;&nbsp;<a href="#rfc.xref.status.100.1">4.1</a>, <a href="#rfc.iref.s.3"><b>4.3.1</b></a>, <a href="#rfc.xref.status.100.2">8.2</a></li>
     3846                        <li>101 Switching Protocols&nbsp;&nbsp;<a href="#rfc.xref.status.101.1">4.1</a>, <a href="#rfc.iref.s.4"><b>4.3.2</b></a>, <a href="#rfc.xref.status.101.2">8.2</a></li>
     3847                        <li>200 OK&nbsp;&nbsp;<a href="#rfc.xref.status.200.1">4.1</a>, <a href="#rfc.iref.s.5"><b>4.4.1</b></a>, <a href="#rfc.xref.status.200.2">8.2</a></li>
     3848                        <li>201 Created&nbsp;&nbsp;<a href="#rfc.xref.status.201.1">4.1</a>, <a href="#rfc.iref.s.6"><b>4.4.2</b></a>, <a href="#rfc.xref.status.201.2">8.2</a></li>
     3849                        <li>202 Accepted&nbsp;&nbsp;<a href="#rfc.xref.status.202.1">4.1</a>, <a href="#rfc.iref.s.7"><b>4.4.3</b></a>, <a href="#rfc.xref.status.202.2">8.2</a></li>
     3850                        <li>203 Non-Authoritative Information&nbsp;&nbsp;<a href="#rfc.xref.status.203.1">4.1</a>, <a href="#rfc.iref.s.8"><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>
     3851                        <li>204 No Content&nbsp;&nbsp;<a href="#rfc.xref.status.204.1">4.1</a>, <a href="#rfc.iref.s.9"><b>4.4.5</b></a>, <a href="#rfc.xref.status.204.2">8.2</a></li>
     3852                        <li>205 Reset Content&nbsp;&nbsp;<a href="#rfc.xref.status.205.1">4.1</a>, <a href="#rfc.iref.s.10"><b>4.4.6</b></a>, <a href="#rfc.xref.status.205.2">8.2</a></li>
     3853                        <li>300 Multiple Choices&nbsp;&nbsp;<a href="#rfc.xref.status.300.1">4.1</a>, <a href="#rfc.iref.s.11"><b>4.5.1</b></a>, <a href="#rfc.xref.status.300.2">8.2</a></li>
     3854                        <li>301 Moved Permanently&nbsp;&nbsp;<a href="#rfc.xref.status.301.1">4.1</a>, <a href="#rfc.iref.s.12"><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>
     3855                        <li>302 Found&nbsp;&nbsp;<a href="#rfc.xref.status.302.1">4.1</a>, <a href="#rfc.iref.s.13"><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>
     3856                        <li>303 See Other&nbsp;&nbsp;<a href="#rfc.xref.status.303.1">4.1</a>, <a href="#rfc.iref.s.14"><b>4.5.4</b></a>, <a href="#rfc.xref.status.303.2">8.2</a></li>
     3857                        <li>305 Use Proxy&nbsp;&nbsp;<a href="#rfc.xref.status.305.1">4.1</a>, <a href="#rfc.iref.s.15"><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>
     3858                        <li>306 (Unused)&nbsp;&nbsp;<a href="#rfc.iref.s.16"><b>4.5.6</b></a>, <a href="#rfc.xref.status.306.1">8.2</a></li>
     3859                        <li>307 Temporary Redirect&nbsp;&nbsp;<a href="#rfc.xref.status.307.1">4.1</a>, <a href="#rfc.iref.s.17"><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>
     3860                        <li>400 Bad Request&nbsp;&nbsp;<a href="#rfc.xref.status.400.1">4.1</a>, <a href="#rfc.iref.s.18"><b>4.6.1</b></a>, <a href="#rfc.xref.status.400.2">8.2</a></li>
     3861                        <li>402 Payment Required&nbsp;&nbsp;<a href="#rfc.xref.status.402.1">4.1</a>, <a href="#rfc.iref.s.19"><b>4.6.2</b></a>, <a href="#rfc.xref.status.402.2">8.2</a></li>
     3862                        <li>403 Forbidden&nbsp;&nbsp;<a href="#rfc.xref.status.403.1">4.1</a>, <a href="#rfc.iref.s.20"><b>4.6.3</b></a>, <a href="#rfc.xref.status.403.2">8.2</a></li>
     3863                        <li>404 Not Found&nbsp;&nbsp;<a href="#rfc.xref.status.404.1">4.1</a>, <a href="#rfc.iref.s.21"><b>4.6.4</b></a>, <a href="#rfc.xref.status.404.2">8.2</a></li>
     3864                        <li>405 Method Not Allowed&nbsp;&nbsp;<a href="#rfc.xref.status.405.1">4.1</a>, <a href="#rfc.iref.s.22"><b>4.6.5</b></a>, <a href="#rfc.xref.status.405.2">8.2</a></li>
     3865                        <li>406 Not Acceptable&nbsp;&nbsp;<a href="#rfc.xref.status.406.1">4.1</a>, <a href="#rfc.iref.s.23"><b>4.6.6</b></a>, <a href="#rfc.xref.status.406.2">8.2</a></li>
     3866                        <li>408 Request Timeout&nbsp;&nbsp;<a href="#rfc.xref.status.408.1">4.1</a>, <a href="#rfc.iref.s.24"><b>4.6.7</b></a>, <a href="#rfc.xref.status.408.2">8.2</a></li>
     3867                        <li>409 Conflict&nbsp;&nbsp;<a href="#rfc.xref.status.409.1">4.1</a>, <a href="#rfc.iref.s.25"><b>4.6.8</b></a>, <a href="#rfc.xref.status.409.2">8.2</a></li>
     3868                        <li>410 Gone&nbsp;&nbsp;<a href="#rfc.xref.status.410.1">4.1</a>, <a href="#rfc.iref.s.26"><b>4.6.9</b></a>, <a href="#rfc.xref.status.410.2">8.2</a></li>
     3869                        <li>411 Length Required&nbsp;&nbsp;<a href="#rfc.xref.status.411.1">4.1</a>, <a href="#rfc.iref.s.27"><b>4.6.10</b></a>, <a href="#rfc.xref.status.411.2">8.2</a></li>
     3870                        <li>413 Request Representation Too Large&nbsp;&nbsp;<a href="#rfc.xref.status.413.1">4.1</a>, <a href="#rfc.iref.s.28"><b>4.6.11</b></a>, <a href="#rfc.xref.status.413.2">8.2</a></li>
     3871                        <li>414 URI Too Long&nbsp;&nbsp;<a href="#rfc.xref.status.414.1">4.1</a>, <a href="#rfc.iref.s.29"><b>4.6.12</b></a>, <a href="#rfc.xref.status.414.2">8.2</a></li>
     3872                        <li>415 Unsupported Media Type&nbsp;&nbsp;<a href="#rfc.xref.status.415.1">4.1</a>, <a href="#rfc.iref.s.30"><b>4.6.13</b></a>, <a href="#rfc.xref.status.415.2">8.2</a></li>
     3873                        <li>417 Expectation Failed&nbsp;&nbsp;<a href="#rfc.xref.status.417.1">4.1</a>, <a href="#rfc.iref.s.31"><b>4.6.14</b></a>, <a href="#rfc.xref.status.417.2">8.2</a></li>
     3874                        <li>426 Upgrade Required&nbsp;&nbsp;<a href="#rfc.xref.status.426.1">4.1</a>, <a href="#rfc.iref.s.32"><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>
     3875                        <li>500 Internal Server Error&nbsp;&nbsp;<a href="#rfc.xref.status.500.1">4.1</a>, <a href="#rfc.iref.s.33"><b>4.7.1</b></a>, <a href="#rfc.xref.status.500.2">8.2</a></li>
     3876                        <li>501 Not Implemented&nbsp;&nbsp;<a href="#rfc.xref.status.501.1">4.1</a>, <a href="#rfc.iref.s.34"><b>4.7.2</b></a>, <a href="#rfc.xref.status.501.2">8.2</a></li>
     3877                        <li>502 Bad Gateway&nbsp;&nbsp;<a href="#rfc.xref.status.502.1">4.1</a>, <a href="#rfc.iref.s.35"><b>4.7.3</b></a>, <a href="#rfc.xref.status.502.2">8.2</a></li>
     3878                        <li>503 Service Unavailable&nbsp;&nbsp;<a href="#rfc.xref.status.503.1">4.1</a>, <a href="#rfc.iref.s.36"><b>4.7.4</b></a>, <a href="#rfc.xref.status.503.2">8.2</a></li>
     3879                        <li>504 Gateway Timeout&nbsp;&nbsp;<a href="#rfc.xref.status.504.1">4.1</a>, <a href="#rfc.iref.s.37"><b>4.7.5</b></a>, <a href="#rfc.xref.status.504.2">8.2</a></li>
     3880                        <li>505 HTTP Version Not Supported&nbsp;&nbsp;<a href="#rfc.xref.status.505.1">4.1</a>, <a href="#rfc.iref.s.38"><b>4.7.6</b></a>, <a href="#rfc.xref.status.505.2">8.2</a></li>
    38623881                     </ul>
    38633882                  </li>
  • draft-ietf-httpbis/latest/p2-semantics.xml

    r1640 r1641  
    253253</t>
    254254
     255<section title="Terminology" anchor="terminology">
     256<t>
     257   This specification uses a number of terms to refer to the roles
     258   played by participants in, and objects of, the HTTP communication.
     259</t>
     260<t>
     261  <iref item="content negotiation"/>
     262  <x:dfn>content negotiation</x:dfn>
     263  <list>
     264    <t>
     265      The mechanism for selecting the appropriate representation when
     266      servicing a request. The representation in any response
     267      can be negotiated (including error responses).
     268    </t>
     269  </list>
     270</t>
     271<t>
     272  <iref primary="true" item="selected representation"/>
     273  <x:dfn>selected representation</x:dfn>
     274  <list>
     275    <t>
     276      The current representation of the target resource that would have been
     277      selected in a successful response if the same request had used the
     278      method GET and excluded any conditional request header fields.
     279    </t>
     280  </list>
     281</t>
     282</section>
     283
    255284<section title="Conformance and Error Handling" anchor="intro.conformance.and.error.handling">
    256285<t>
  • draft-ietf-httpbis/latest/p3-payload.html

    r1640 r1641  
    573573      <ul class="toc">
    574574         <li>1.&nbsp;&nbsp;&nbsp;<a href="#introduction">Introduction</a><ul>
    575                <li>1.1&nbsp;&nbsp;&nbsp;<a href="#terminology">Terminology</a></li>
    576                <li>1.2&nbsp;&nbsp;&nbsp;<a href="#intro.conformance.and.error.handling">Conformance and Error Handling</a></li>
    577                <li>1.3&nbsp;&nbsp;&nbsp;<a href="#notation">Syntax Notation</a><ul>
    578                      <li>1.3.1&nbsp;&nbsp;&nbsp;<a href="#core.rules">Core Rules</a></li>
    579                      <li>1.3.2&nbsp;&nbsp;&nbsp;<a href="#abnf.dependencies">ABNF Rules defined in other Parts of the Specification</a></li>
     575               <li>1.1&nbsp;&nbsp;&nbsp;<a href="#notation">Syntax Notation</a><ul>
     576                     <li>1.1.1&nbsp;&nbsp;&nbsp;<a href="#core.rules">Core Rules</a></li>
     577                     <li>1.1.2&nbsp;&nbsp;&nbsp;<a href="#abnf.dependencies">ABNF Rules defined in other Parts of the Specification</a></li>
    580578                  </ul>
    581579               </li>
     
    676674      <h1 id="rfc.section.1" class="np"><a href="#rfc.section.1">1.</a>&nbsp;<a id="introduction" href="#introduction">Introduction</a></h1>
    677675      <p id="rfc.section.1.p.1">This part is now obsolete. Please see HTTPbis, Part 2.</p>
    678       <h2 id="rfc.section.1.1"><a href="#rfc.section.1.1">1.1</a>&nbsp;<a id="terminology" href="#terminology">Terminology</a></h2>
    679       <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>
    680       <p id="rfc.section.1.1.p.2"> <span id="rfc.iref.c.1"></span>  <dfn>content negotiation</dfn> 
    681       </p>
    682       <ul class="empty">
    683          <li>The mechanism for selecting the appropriate representation when servicing a request. The representation in any response can
    684             be negotiated (including error responses).
    685          </li>
    686       </ul>
    687       <p id="rfc.section.1.1.p.3"> <span id="rfc.iref.s.1"></span>  <dfn>selected representation</dfn> 
    688       </p>
    689       <ul class="empty">
    690          <li>The current representation of the target resource that would have been selected in a successful response if the same request
    691             had used the method GET and excluded any conditional request header fields.
    692          </li>
    693       </ul>
    694       <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>
    695       <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"
    696          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>.
    697       </p>
    698       <p id="rfc.section.1.2.p.2">This document defines conformance criteria for several roles in HTTP communication, including Senders, Recipients, Clients,
    699          Servers, User-Agents, Origin Servers, Intermediaries, Proxies and Gateways. See <a href="p1-messaging.html#architecture" title="Architecture">Section 2</a> of <a href="#Part1" id="rfc.xref.Part1.1"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a> for definitions of these terms.
    700       </p>
    701       <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
    702          SHOULD-level requirements are relevant here, unless one of the documented exceptions is applicable.
    703       </p>
    704       <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.
    705       </p>
    706       <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
    707          mechanisms, except in cases where it has direct impact on security. This is because different uses of the protocol require
    708          different error handling strategies; for example, a Web browser may wish to transparently recover from a response where the
    709          Location header field doesn't parse according to the ABNF, whereby in a systems control protocol using HTTP, this type of
    710          error recovery could lead to dangerous consequences.
    711       </p>
    712       <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>
    713       <p id="rfc.section.1.3.p.1">This specification uses the Augmented Backus-Naur Form (ABNF) notation of <a href="#RFC5234" id="rfc.xref.RFC5234.1"><cite title="Augmented BNF for Syntax Specifications: ABNF">[RFC5234]</cite></a> with the list rule extension defined in <a href="p1-messaging.html#notation" title="Syntax Notation">Section 1.2</a> of <a href="#Part1" id="rfc.xref.Part1.2"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>.
    714       </p>
    715       <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
     676      <h2 id="rfc.section.1.1"><a href="#rfc.section.1.1">1.1</a>&nbsp;<a id="notation" href="#notation">Syntax Notation</a></h2>
     677      <p id="rfc.section.1.1.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.1"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>.
     678      </p>
     679      <p id="rfc.section.1.1.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
    716680         (hexadecimal 0-9/A-F/a-f), LF (line feed), OCTET (any 8-bit sequence of data), SP (space), and VCHAR (any visible US-ASCII
    717681         character).
    718682      </p>
    719       <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>
    720       <p id="rfc.section.1.3.1.p.1">The core rules below are defined in <a href="#Part1" id="rfc.xref.Part1.3"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>:
    721       </p>
    722       <div id="rfc.figure.u.1"></div><pre class="inline">  <a href="#core.rules" class="smpl">OWS</a>            = &lt;OWS, defined in <a href="#Part1" id="rfc.xref.Part1.4"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#whitespace" title="Whitespace">Section 3.2.1</a>&gt;
    723   <a href="#core.rules" class="smpl">token</a>          = &lt;token, defined in <a href="#Part1" id="rfc.xref.Part1.5"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#field.components" title="Field value components">Section 3.2.4</a>&gt;
    724   <a href="#core.rules" class="smpl">word</a>           = &lt;word, defined in <a href="#Part1" id="rfc.xref.Part1.6"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#field.components" title="Field value components">Section 3.2.4</a>&gt;
    725 </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>
    726       <p id="rfc.section.1.3.2.p.1">The ABNF rules below are defined in other parts:</p>
    727       <div id="rfc.figure.u.2"></div><pre class="inline">  <a href="#abnf.dependencies" class="smpl">absolute-URI</a>   = &lt;absolute-URI, defined in <a href="#Part1" id="rfc.xref.Part1.7"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#uri" title="Uniform Resource Identifiers">Section 2.7</a>&gt;
    728   <a href="#abnf.dependencies" class="smpl">partial-URI</a>    = &lt;partial-URI, defined in <a href="#Part1" id="rfc.xref.Part1.8"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#uri" title="Uniform Resource Identifiers">Section 2.7</a>&gt;
    729   <a href="#abnf.dependencies" class="smpl">qvalue</a>         = &lt;qvalue, defined in <a href="#Part1" id="rfc.xref.Part1.9"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#quality.values" title="Quality Values">Section 4.3.1</a>&gt;
     683      <h3 id="rfc.section.1.1.1"><a href="#rfc.section.1.1.1">1.1.1</a>&nbsp;<a id="core.rules" href="#core.rules">Core Rules</a></h3>
     684      <p id="rfc.section.1.1.1.p.1">The core rules below are defined in <a href="#Part1" id="rfc.xref.Part1.2"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>:
     685      </p>
     686      <div id="rfc.figure.u.1"></div><pre class="inline">  <a href="#core.rules" class="smpl">OWS</a>            = &lt;OWS, defined in <a href="#Part1" id="rfc.xref.Part1.3"><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;
     687  <a href="#core.rules" class="smpl">token</a>          = &lt;token, defined in <a href="#Part1" id="rfc.xref.Part1.4"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#field.components" title="Field value components">Section 3.2.4</a>&gt;
     688  <a href="#core.rules" class="smpl">word</a>           = &lt;word, defined in <a href="#Part1" id="rfc.xref.Part1.5"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#field.components" title="Field value components">Section 3.2.4</a>&gt;
     689</pre><h3 id="rfc.section.1.1.2"><a href="#rfc.section.1.1.2">1.1.2</a>&nbsp;<a id="abnf.dependencies" href="#abnf.dependencies">ABNF Rules defined in other Parts of the Specification</a></h3>
     690      <p id="rfc.section.1.1.2.p.1">The ABNF rules below are defined in other parts:</p>
     691      <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.6"><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;
     692  <a href="#abnf.dependencies" class="smpl">partial-URI</a>    = &lt;partial-URI, defined in <a href="#Part1" id="rfc.xref.Part1.7"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#uri" title="Uniform Resource Identifiers">Section 2.7</a>&gt;
     693  <a href="#abnf.dependencies" class="smpl">qvalue</a>         = &lt;qvalue, defined in <a href="#Part1" id="rfc.xref.Part1.8"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#quality.values" title="Quality Values">Section 4.3.1</a>&gt;
    730694</pre><h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a>&nbsp;<a id="protocol.parameters" href="#protocol.parameters">Protocol Parameters</a></h1>
    731695      <h2 id="rfc.section.2.1"><a href="#rfc.section.2.1">2.1</a>&nbsp;<a id="character.sets" href="#character.sets">Character Encodings (charset)</a></h2>
     
    756720         mechanism will be required to remove the encoding.
    757721      </p>
    758       <p id="rfc.section.2.2.p.4">compress<span id="rfc.iref.c.2"></span><span id="rfc.iref.c.3"></span> 
     722      <p id="rfc.section.2.2.p.4">compress<span id="rfc.iref.c.1"></span><span id="rfc.iref.c.2"></span> 
    759723      </p>
    760724      <ul class="empty">
    761          <li>See <a href="p1-messaging.html#compress.coding" title="Compress Coding">Section 4.2.1</a> of <a href="#Part1" id="rfc.xref.Part1.10"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>.
    762          </li>
    763       </ul>
    764       <p id="rfc.section.2.2.p.5">deflate<span id="rfc.iref.d.1"></span><span id="rfc.iref.c.4"></span> 
     725         <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.9"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>.
     726         </li>
     727      </ul>
     728      <p id="rfc.section.2.2.p.5">deflate<span id="rfc.iref.d.1"></span><span id="rfc.iref.c.3"></span> 
    765729      </p>
    766730      <ul class="empty">
    767          <li>See <a href="p1-messaging.html#deflate.coding" title="Deflate Coding">Section 4.2.2</a> of <a href="#Part1" id="rfc.xref.Part1.11"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>.
    768          </li>
    769       </ul>
    770       <p id="rfc.section.2.2.p.6">gzip<span id="rfc.iref.g.3"></span><span id="rfc.iref.c.5"></span> 
     731         <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.10"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>.
     732         </li>
     733      </ul>
     734      <p id="rfc.section.2.2.p.6">gzip<span id="rfc.iref.g.3"></span><span id="rfc.iref.c.4"></span> 
    771735      </p>
    772736      <ul class="empty">
    773          <li>See <a href="p1-messaging.html#gzip.coding" title="Gzip Coding">Section 4.2.3</a> of <a href="#Part1" id="rfc.xref.Part1.12"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>.
     737         <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.11"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>.
    774738         </li>
    775739      </ul>
     
    783747         <li>Pointer to specification text</li>
    784748      </ul>
    785       <p id="rfc.section.2.2.1.p.3">Names of content codings <em class="bcp14">MUST NOT</em> overlap with names of transfer codings (<a href="p1-messaging.html#transfer.codings" title="Transfer Codings">Section 4</a> of <a href="#Part1" id="rfc.xref.Part1.13"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>), unless the encoding transformation is identical (as is the case for the compression codings defined in <a href="p1-messaging.html#compression.codings" title="Compression Codings">Section 4.2</a> of <a href="#Part1" id="rfc.xref.Part1.14"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>).
     749      <p id="rfc.section.2.2.1.p.3">Names of content codings <em class="bcp14">MUST NOT</em> overlap with names of transfer codings (<a href="p1-messaging.html#transfer.codings" title="Transfer Codings">Section 4</a> of <a href="#Part1" id="rfc.xref.Part1.12"><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.13"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>).
    786750      </p>
    787751      <p id="rfc.section.2.2.1.p.4">Values to be added to this name space require IETF Review (see <a href="http://tools.ietf.org/html/rfc5226#section-4.1">Section 4.1</a> of <a href="#RFC5226" id="rfc.xref.RFC5226.1"><cite title="Guidelines for Writing an IANA Considerations Section in RFCs">[RFC5226]</cite></a>), and <em class="bcp14">MUST</em> conform to the purpose of content coding defined in this section.
     
    883847               <tr>
    884848                  <td class="left">Content-Length</td>
    885                   <td class="left"><a href="p1-messaging.html#header.content-length" title="Content-Length">Section 3.3.2</a> of <a href="#Part1" id="rfc.xref.Part1.15"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a></td>
     849                  <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.14"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a></td>
    886850               </tr>
    887851               <tr>
     
    893857      </div>
    894858      <h2 id="rfc.section.3.2"><a href="#rfc.section.3.2">3.2</a>&nbsp;<a id="payload.body" href="#payload.body">Payload Body</a></h2>
    895       <p id="rfc.section.3.2.p.1">A payload body is only present in a message when a message body is present, as described in <a href="p1-messaging.html#message.body" title="Message Body">Section 3.3</a> of <a href="#Part1" id="rfc.xref.Part1.16"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>. The payload body is obtained from the message body by decoding any Transfer-Encoding that might have been applied to ensure
     859      <p id="rfc.section.3.2.p.1">A payload body is only present in a message when a message body is present, as described in <a href="p1-messaging.html#message.body" title="Message Body">Section 3.3</a> of <a href="#Part1" id="rfc.xref.Part1.15"><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
    896860         safe and proper transfer of the message.
    897861      </p>
     
    10491013         that doesn't conform to them is better than sending a 406 (Not Acceptable) response.
    10501014      </p>
    1051       <p id="rfc.section.5.1.p.5">Many of the mechanisms for expressing preferences use quality values to declare relative preference. See <a href="p1-messaging.html#quality.values" title="Quality Values">Section 4.3.1</a> of <a href="#Part1" id="rfc.xref.Part1.17"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a> for more information.
     1015      <p id="rfc.section.5.1.p.5">Many of the mechanisms for expressing preferences use quality values to declare relative preference. See <a href="p1-messaging.html#quality.values" title="Quality Values">Section 4.3.1</a> of <a href="#Part1" id="rfc.xref.Part1.16"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a> for more information.
    10521016      </p>
    10531017      <p id="rfc.section.5.1.p.6">HTTP/1.1 includes the following header fields for enabling server-driven negotiation through description of user agent capabilities
     
    11021066      <p id="rfc.section.6.1.p.4">Each media-range <em class="bcp14">MAY</em> be followed by one or more accept-params, beginning with the "q" parameter for indicating a relative quality factor. The first
    11031067         "q" parameter (if any) separates the media-range parameter(s) from the accept-params. Quality factors allow the user or user
    1104          agent to indicate the relative degree of preference for that media-range, using the qvalue scale from 0 to 1 (<a href="p1-messaging.html#quality.values" title="Quality Values">Section 4.3.1</a> of <a href="#Part1" id="rfc.xref.Part1.18"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>). The default value is q=1.
     1068         agent to indicate the relative degree of preference for that media-range, using the qvalue scale from 0 to 1 (<a href="p1-messaging.html#quality.values" title="Quality Values">Section 4.3.1</a> of <a href="#Part1" id="rfc.xref.Part1.17"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>). The default value is q=1.
    11051069      </p>
    11061070      <div class="note" id="rfc.section.6.1.p.5">
     
    12321196         </li>
    12331197         <li>If the representation's content-coding is one of the content-codings listed in the Accept-Encoding field, then it is acceptable
    1234             unless it is accompanied by a qvalue of 0. (As defined in <a href="p1-messaging.html#quality.values" title="Quality Values">Section 4.3.1</a> of <a href="#Part1" id="rfc.xref.Part1.19"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, a qvalue of 0 means "not acceptable".)
     1198            unless it is accompanied by a qvalue of 0. (As defined in <a href="p1-messaging.html#quality.values" title="Quality Values">Section 4.3.1</a> of <a href="#Part1" id="rfc.xref.Part1.18"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, a qvalue of 0 means "not acceptable".)
    12351199         </li>
    12361200         <li>If multiple content-codings are acceptable, then the acceptable content-coding with the highest non-zero qvalue is preferred.</li>
     
    12831247         </p>
    12841248      </div>
    1285       <div id="rfc.iref.c.6"></div>
     1249      <div id="rfc.iref.c.5"></div>
    12861250      <div id="rfc.iref.h.5"></div>
    12871251      <h2 id="rfc.section.6.5"><a href="#rfc.section.6.5">6.5</a>&nbsp;<a id="header.content-encoding" href="#header.content-encoding">Content-Encoding</a></h2>
     
    13121276      <p id="rfc.section.6.5.p.9">If the content-coding of a representation in a request message is not acceptable to the origin server, the server <em class="bcp14">SHOULD</em> respond with a status code of 415 (Unsupported Media Type).
    13131277      </p>
    1314       <div id="rfc.iref.c.7"></div>
     1278      <div id="rfc.iref.c.6"></div>
    13151279      <div id="rfc.iref.h.6"></div>
    13161280      <h2 id="rfc.section.6.6"><a href="#rfc.section.6.6">6.6</a>&nbsp;<a id="header.content-language" href="#header.content-language">Content-Language</a></h2>
     
    13381302      <p id="rfc.section.6.6.p.9">Content-Language <em class="bcp14">MAY</em> be applied to any media type — it is not limited to textual documents.
    13391303      </p>
    1340       <div id="rfc.iref.c.8"></div>
     1304      <div id="rfc.iref.c.7"></div>
    13411305      <div id="rfc.iref.h.7"></div>
    13421306      <h2 id="rfc.section.6.7"><a href="#rfc.section.6.7">6.7</a>&nbsp;<a id="header.content-location" href="#header.content-location">Content-Location</a></h2>
     
    13461310      </p>
    13471311      <div id="rfc.figure.u.26"></div><pre class="inline"><span id="rfc.iref.g.22"></span>  <a href="#header.content-location" class="smpl">Content-Location</a> = <a href="#abnf.dependencies" class="smpl">absolute-URI</a> / <a href="#abnf.dependencies" class="smpl">partial-URI</a>
    1348 </pre><p id="rfc.section.6.7.p.3">The Content-Location value is not a replacement for the effective Request URI (<a href="p1-messaging.html#effective.request.uri" title="Effective Request URI">Section 5.5</a> of <a href="#Part1" id="rfc.xref.Part1.20"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>). It is representation metadata. It has the same syntax and semantics as the header field of the same name defined for MIME
     1312</pre><p id="rfc.section.6.7.p.3">The Content-Location value is not a replacement for the effective Request URI (<a href="p1-messaging.html#effective.request.uri" title="Effective Request URI">Section 5.5</a> of <a href="#Part1" id="rfc.xref.Part1.19"><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
    13491313         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.
    13501314      </p>
     
    13801344      </p>
    13811345      <p id="rfc.section.6.7.p.9">If the Content-Location value is a partial URI, the partial URI is interpreted relative to the effective request URI.</p>
    1382       <div id="rfc.iref.c.9"></div>
     1346      <div id="rfc.iref.c.8"></div>
    13831347      <div id="rfc.iref.h.8"></div>
    13841348      <h2 id="rfc.section.6.8"><a href="#rfc.section.6.8">6.8</a>&nbsp;<a id="header.content-type" href="#header.content-type">Content-Type</a></h2>
     
    14121376                  <td class="left">compress</td>
    14131377                  <td class="left">UNIX "compress" program method</td>
    1414                   <td class="left"> <a href="p1-messaging.html#compress.coding" title="Compress Coding">Section 4.2.1</a> of <a href="#Part1" id="rfc.xref.Part1.21"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>
     1378                  <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.20"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>
    14151379                  </td>
    14161380               </tr>
     
    14191383                  <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>)
    14201384                  </td>
    1421                   <td class="left"> <a href="p1-messaging.html#deflate.coding" title="Deflate Coding">Section 4.2.2</a> of <a href="#Part1" id="rfc.xref.Part1.22"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>
     1385                  <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.21"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>
    14221386                  </td>
    14231387               </tr>
     
    14251389                  <td class="left">gzip</td>
    14261390                  <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>
    1427                   <td class="left"> <a href="p1-messaging.html#gzip.coding" title="Gzip Coding">Section 4.2.3</a> of <a href="#Part1" id="rfc.xref.Part1.23"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>
     1391                  <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.22"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>
    14281392                  </td>
    14291393               </tr>
     
    14651429      <h2 id="rfc.references.1"><a href="#rfc.section.9.1" id="rfc.section.9.1">9.1</a> Normative References
    14661430      </h2>
    1467       <table>                           
     1431      <table>                         
    14681432         <tr>
    14691433            <td class="reference"><b id="Part1">[Part1]</b></td>
     
    15141478            <td class="reference"><b id="RFC2046">[RFC2046]</b></td>
    15151479            <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.
    1516             </td>
    1517          </tr>
    1518          <tr>
    1519             <td class="reference"><b id="RFC2119">[RFC2119]</b></td>
    1520             <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.
    15211480            </td>
    15221481         </tr>
     
    16701629         to perform a function equivalent to Content-Encoding. However, this parameter is not part of the MIME standards).
    16711630      </p>
    1672       <div id="rfc.iref.c.10"></div>
     1631      <div id="rfc.iref.c.9"></div>
    16731632      <div id="rfc.iref.h.10"></div>
    16741633      <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>
     
    16811640      </p>
    16821641      <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>
    1683       <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.24"><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.
     1642      <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.23"><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.
    16841643      </p>
    16851644      <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>
     
    19571916      <p id="rfc.section.D.21.p.1">None yet.</p>
    19581917      <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1>
    1959       <p class="noprint"><a href="#rfc.index.A">A</a> <a href="#rfc.index.C">C</a> <a href="#rfc.index.D">D</a> <a href="#rfc.index.G">G</a> <a href="#rfc.index.H">H</a> <a href="#rfc.index.M">M</a> <a href="#rfc.index.P">P</a> <a href="#rfc.index.R">R</a> <a href="#rfc.index.S">S</a>
     1918      <p class="noprint"><a href="#rfc.index.A">A</a> <a href="#rfc.index.C">C</a> <a href="#rfc.index.D">D</a> <a href="#rfc.index.G">G</a> <a href="#rfc.index.H">H</a> <a href="#rfc.index.M">M</a> <a href="#rfc.index.P">P</a> <a href="#rfc.index.R">R</a>
    19601919      </p>
    19611920      <div class="print2col">
     
    19711930                  <li>Coding Format&nbsp;&nbsp;
    19721931                     <ul>
    1973                         <li>compress&nbsp;&nbsp;<a href="#rfc.iref.c.3">2.2</a></li>
    1974                         <li>deflate&nbsp;&nbsp;<a href="#rfc.iref.c.4">2.2</a></li>
    1975                         <li>gzip&nbsp;&nbsp;<a href="#rfc.iref.c.5">2.2</a></li>
     1932                        <li>compress&nbsp;&nbsp;<a href="#rfc.iref.c.2">2.2</a></li>
     1933                        <li>deflate&nbsp;&nbsp;<a href="#rfc.iref.c.3">2.2</a></li>
     1934                        <li>gzip&nbsp;&nbsp;<a href="#rfc.iref.c.4">2.2</a></li>
    19761935                     </ul>
    19771936                  </li>
    1978                   <li>compress (Coding Format)&nbsp;&nbsp;<a href="#rfc.iref.c.2">2.2</a></li>
    1979                   <li>content negotiation&nbsp;&nbsp;<a href="#rfc.iref.c.1">1.1</a></li>
    1980                   <li>Content-Encoding header field&nbsp;&nbsp;<a href="#rfc.xref.header.content-encoding.1">2.2</a>, <a href="#rfc.xref.header.content-encoding.2">4.1</a>, <a href="#rfc.iref.c.6"><b>6.5</b></a>, <a href="#rfc.xref.header.content-encoding.3">6.5</a></li>
    1981                   <li>Content-Language header field&nbsp;&nbsp;<a href="#rfc.xref.header.content-language.1">4.1</a>, <a href="#rfc.iref.c.7"><b>6.6</b></a></li>
    1982                   <li>Content-Location header field&nbsp;&nbsp;<a href="#rfc.xref.header.content-location.1">4.1</a>, <a href="#rfc.iref.c.8"><b>6.7</b></a>, <a href="#rfc.xref.header.content-location.2">C</a></li>
    1983                   <li>Content-Transfer-Encoding header field&nbsp;&nbsp;<a href="#rfc.iref.c.10">A.5</a>, <a href="#rfc.xref.no.content-transfer-encoding.1">C</a></li>
    1984                   <li>Content-Type header field&nbsp;&nbsp;<a href="#rfc.xref.header.content-type.1">2.3</a>, <a href="#rfc.xref.header.content-type.2">4.1</a>, <a href="#rfc.iref.c.9"><b>6.8</b></a></li>
     1937                  <li>compress (Coding Format)&nbsp;&nbsp;<a href="#rfc.iref.c.1">2.2</a></li>
     1938                  <li>Content-Encoding header field&nbsp;&nbsp;<a href="#rfc.xref.header.content-encoding.1">2.2</a>, <a href="#rfc.xref.header.content-encoding.2">4.1</a>, <a href="#rfc.iref.c.5"><b>6.5</b></a>, <a href="#rfc.xref.header.content-encoding.3">6.5</a></li>
     1939                  <li>Content-Language header field&nbsp;&nbsp;<a href="#rfc.xref.header.content-language.1">4.1</a>, <a href="#rfc.iref.c.6"><b>6.6</b></a></li>
     1940                  <li>Content-Location header field&nbsp;&nbsp;<a href="#rfc.xref.header.content-location.1">4.1</a>, <a href="#rfc.iref.c.7"><b>6.7</b></a>, <a href="#rfc.xref.header.content-location.2">C</a></li>
     1941                  <li>Content-Transfer-Encoding header field&nbsp;&nbsp;<a href="#rfc.iref.c.9">A.5</a>, <a href="#rfc.xref.no.content-transfer-encoding.1">C</a></li>
     1942                  <li>Content-Type header field&nbsp;&nbsp;<a href="#rfc.xref.header.content-type.1">2.3</a>, <a href="#rfc.xref.header.content-type.2">4.1</a>, <a href="#rfc.iref.c.8"><b>6.8</b></a></li>
    19851943               </ul>
    19861944            </li>
     
    20422000            </li>
    20432001            <li><a id="rfc.index.P" href="#rfc.index.P"><b>P</b></a><ul>
    2044                   <li><em>Part1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.1">1.2</a>, <a href="#rfc.xref.Part1.2">1.3</a>, <a href="#rfc.xref.Part1.3">1.3.1</a>, <a href="#rfc.xref.Part1.4">1.3.1</a>, <a href="#rfc.xref.Part1.5">1.3.1</a>, <a href="#rfc.xref.Part1.6">1.3.1</a>, <a href="#rfc.xref.Part1.7">1.3.2</a>, <a href="#rfc.xref.Part1.8">1.3.2</a>, <a href="#rfc.xref.Part1.9">1.3.2</a>, <a href="#rfc.xref.Part1.10">2.2</a>, <a href="#rfc.xref.Part1.11">2.2</a>, <a href="#rfc.xref.Part1.12">2.2</a>, <a href="#rfc.xref.Part1.13">2.2.1</a>, <a href="#rfc.xref.Part1.14">2.2.1</a>, <a href="#rfc.xref.Part1.15">3.1</a>, <a href="#rfc.xref.Part1.16">3.2</a>, <a href="#rfc.xref.Part1.17">5.1</a>, <a href="#rfc.xref.Part1.18">6.1</a>, <a href="#rfc.xref.Part1.19">6.3</a>, <a href="#rfc.xref.Part1.20">6.7</a>, <a href="#rfc.xref.Part1.21">7.1</a>, <a href="#rfc.xref.Part1.22">7.1</a>, <a href="#rfc.xref.Part1.23">7.1</a>, <a href="#Part1"><b>9.1</b></a>, <a href="#rfc.xref.Part1.24">A.6</a><ul>
    2045                         <li><em>Section 1.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.2">1.3</a></li>
    2046                         <li><em>Section 2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.1">1.2</a></li>
    2047                         <li><em>Section 2.7</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.7">1.3.2</a>, <a href="#rfc.xref.Part1.8">1.3.2</a></li>
    2048                         <li><em>Section 3.2.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.4">1.3.1</a></li>
    2049                         <li><em>Section 3.2.4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.5">1.3.1</a>, <a href="#rfc.xref.Part1.6">1.3.1</a></li>
    2050                         <li><em>Section 3.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.16">3.2</a></li>
    2051                         <li><em>Section 3.3.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.24">A.6</a></li>
    2052                         <li><em>Section 3.3.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.15">3.1</a></li>
    2053                         <li><em>Section 4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.13">2.2.1</a></li>
    2054                         <li><em>Section 4.2.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.10">2.2</a>, <a href="#rfc.xref.Part1.21">7.1</a></li>
    2055                         <li><em>Section 4.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.14">2.2.1</a></li>
    2056                         <li><em>Section 4.2.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.11">2.2</a>, <a href="#rfc.xref.Part1.22">7.1</a></li>
    2057                         <li><em>Section 4.2.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.12">2.2</a>, <a href="#rfc.xref.Part1.23">7.1</a></li>
    2058                         <li><em>Section 4.3.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.9">1.3.2</a>, <a href="#rfc.xref.Part1.17">5.1</a>, <a href="#rfc.xref.Part1.18">6.1</a>, <a href="#rfc.xref.Part1.19">6.3</a></li>
    2059                         <li><em>Section 5.5</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.20">6.7</a></li>
     2002                  <li><em>Part1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.1">1.1</a>, <a href="#rfc.xref.Part1.2">1.1.1</a>, <a href="#rfc.xref.Part1.3">1.1.1</a>, <a href="#rfc.xref.Part1.4">1.1.1</a>, <a href="#rfc.xref.Part1.5">1.1.1</a>, <a href="#rfc.xref.Part1.6">1.1.2</a>, <a href="#rfc.xref.Part1.7">1.1.2</a>, <a href="#rfc.xref.Part1.8">1.1.2</a>, <a href="#rfc.xref.Part1.9">2.2</a>, <a href="#rfc.xref.Part1.10">2.2</a>, <a href="#rfc.xref.Part1.11">2.2</a>, <a href="#rfc.xref.Part1.12">2.2.1</a>, <a href="#rfc.xref.Part1.13">2.2.1</a>, <a href="#rfc.xref.Part1.14">3.1</a>, <a href="#rfc.xref.Part1.15">3.2</a>, <a href="#rfc.xref.Part1.16">5.1</a>, <a href="#rfc.xref.Part1.17">6.1</a>, <a href="#rfc.xref.Part1.18">6.3</a>, <a href="#rfc.xref.Part1.19">6.7</a>, <a href="#rfc.xref.Part1.20">7.1</a>, <a href="#rfc.xref.Part1.21">7.1</a>, <a href="#rfc.xref.Part1.22">7.1</a>, <a href="#Part1"><b>9.1</b></a>, <a href="#rfc.xref.Part1.23">A.6</a><ul>
     2003                        <li><em>Section 1.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.1">1.1</a></li>
     2004                        <li><em>Section 2.7</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.6">1.1.2</a>, <a href="#rfc.xref.Part1.7">1.1.2</a></li>
     2005                        <li><em>Section 3.2.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.3">1.1.1</a></li>
     2006                        <li><em>Section 3.2.4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.4">1.1.1</a>, <a href="#rfc.xref.Part1.5">1.1.1</a></li>
     2007                        <li><em>Section 3.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.15">3.2</a></li>
     2008                        <li><em>Section 3.3.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.23">A.6</a></li>
     2009                        <li><em>Section 3.3.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.14">3.1</a></li>
     2010                        <li><em>Section 4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.12">2.2.1</a></li>
     2011                        <li><em>Section 4.2.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.9">2.2</a>, <a href="#rfc.xref.Part1.20">7.1</a></li>
     2012                        <li><em>Section 4.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.13">2.2.1</a></li>
     2013                        <li><em>Section 4.2.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.10">2.2</a>, <a href="#rfc.xref.Part1.21">7.1</a></li>
     2014                        <li><em>Section 4.2.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.11">2.2</a>, <a href="#rfc.xref.Part1.22">7.1</a></li>
     2015                        <li><em>Section 4.3.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.8">1.1.2</a>, <a href="#rfc.xref.Part1.16">5.1</a>, <a href="#rfc.xref.Part1.17">6.1</a>, <a href="#rfc.xref.Part1.18">6.3</a></li>
     2016                        <li><em>Section 5.5</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.19">6.7</a></li>
    20602017                     </ul>
    20612018                  </li>
     
    21002057                  <li><em>RFC2068</em>&nbsp;&nbsp;<a href="#RFC2068"><b>9.2</b></a>, <a href="#rfc.xref.RFC2068.1">B</a></li>
    21012058                  <li><em>RFC2076</em>&nbsp;&nbsp;<a href="#RFC2076"><b>9.2</b></a>, <a href="#rfc.xref.RFC2076.1">B</a></li>
    2102                   <li><em>RFC2119</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2119.1">1.2</a>, <a href="#RFC2119"><b>9.1</b></a></li>
    21032059                  <li><em>RFC2277</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2277.1">2.1</a>, <a href="#RFC2277"><b>9.2</b></a></li>
    21042060                  <li><em>RFC2295</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2295.1">5</a>, <a href="#RFC2295"><b>9.2</b></a></li>
     
    21252081                     </ul>
    21262082                  </li>
    2127                   <li><em>RFC5234</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5234.1">1.3</a>, <a href="#rfc.xref.RFC5234.2">1.3</a>, <a href="#RFC5234"><b>9.1</b></a><ul>
    2128                         <li><em>Appendix B.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5234.2">1.3</a></li>
     2083                  <li><em>RFC5234</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5234.1">1.1</a>, <a href="#rfc.xref.RFC5234.2">1.1</a>, <a href="#RFC5234"><b>9.1</b></a><ul>
     2084                        <li><em>Appendix B.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5234.2">1.1</a></li>
    21292085                     </ul>
    21302086                  </li>
     
    21382094               </ul>
    21392095            </li>
    2140             <li><a id="rfc.index.S" href="#rfc.index.S"><b>S</b></a><ul>
    2141                   <li>selected representation&nbsp;&nbsp;<a href="#rfc.iref.s.1"><b>1.1</b></a></li>
    2142                </ul>
    2143             </li>
    21442096         </ul>
    21452097      </div>
  • draft-ietf-httpbis/latest/p3-payload.xml

    r1640 r1641  
    127127</t>
    128128
    129 <section title="Terminology" anchor="terminology">
    130 <t>
    131    This specification uses a number of terms to refer to the roles
    132    played by participants in, and objects of, the HTTP communication.
    133 </t>
    134 <t>
    135   <iref item="content negotiation"/>
    136   <x:dfn>content negotiation</x:dfn>
    137   <list>
    138     <t>
    139       The mechanism for selecting the appropriate representation when
    140       servicing a request. The representation in any response
    141       can be negotiated (including error responses).
    142     </t>
    143   </list>
    144 </t>
    145 <t>
    146   <iref primary="true" item="selected representation"/>
    147   <x:dfn>selected representation</x:dfn>
    148   <list>
    149     <t>
    150       The current representation of the target resource that would have been
    151       selected in a successful response if the same request had used the
    152       method GET and excluded any conditional request header fields.
    153     </t>
    154   </list>
    155 </t>
    156 </section>
    157 
    158 <section title="Conformance and Error Handling" anchor="intro.conformance.and.error.handling">
    159 <t>
    160    The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
    161    "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
    162    document are to be interpreted as described in <xref target="RFC2119"/>.
    163 </t>
    164 <t>
    165    This document defines conformance criteria for several roles in HTTP
    166    communication, including Senders, Recipients, Clients, Servers, User-Agents,
    167    Origin Servers, Intermediaries, Proxies and Gateways. See &architecture;
    168    for definitions of these terms.
    169 </t>
    170 <t>
    171    An implementation is considered conformant if it complies with all of the
    172    requirements associated with its role(s). Note that SHOULD-level requirements
    173    are relevant here, unless one of the documented exceptions is applicable.
    174 </t>
    175 <t>
    176    This document also uses ABNF to define valid protocol elements
    177    (<xref target="notation"/>). In addition to the prose requirements placed
    178    upon them, Senders &MUST-NOT; generate protocol elements that are invalid.
    179 </t>
    180 <t>
    181    Unless noted otherwise, Recipients &MAY; take steps to recover a usable
    182    protocol element from an invalid construct. However, HTTP does not define
    183    specific error handling mechanisms, except in cases where it has direct
    184    impact on security. This is because different uses of the protocol require
    185    different error handling strategies; for example, a Web browser may wish to
    186    transparently recover from a response where the Location header field
    187    doesn't parse according to the ABNF, whereby in a systems control protocol
    188    using HTTP, this type of error recovery could lead to dangerous consequences.
    189 </t>
    190 </section>
    191 
    192129<section title="Syntax Notation" anchor="notation">
    193130  <x:anchor-alias value="ALPHA"/>
     
    16771614</reference>
    16781615
    1679 <reference anchor="RFC2119">
    1680   <front>
    1681     <title>Key words for use in RFCs to Indicate Requirement Levels</title>
    1682     <author initials="S." surname="Bradner" fullname="Scott Bradner">
    1683       <organization>Harvard University</organization>
    1684       <address><email>sob@harvard.edu</email></address>
    1685     </author>
    1686     <date month="March" year="1997"/>
    1687   </front>
    1688   <seriesInfo name="BCP" value="14"/>
    1689   <seriesInfo name="RFC" value="2119"/>
    1690 </reference>
    1691 
    16921616<reference anchor='RFC4647'>
    16931617  <front>
Note: See TracChangeset for help on using the changeset viewer.