Changeset 424


Ignore:
Timestamp:
Nov 21, 2008, 9:39:20 AM (11 years ago)
Author:
julian.reschke@…
Message:

reorganize ABNF introductions to match Part1 (related to #36)

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

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p1-messaging.html

    r423 r424  
    737737      <div id="rule.CRLF">
    738738         <p id="rfc.section.1.2.2.p.1">  HTTP/1.1 defines the sequence CR LF as the end-of-line marker for all protocol elements except the entity-body (see <a href="#tolerant.applications" title="Tolerant Applications">Appendix&nbsp;A</a> for tolerant applications). The end-of-line marker within an entity-body is defined by its associated media type, as described
    739             in <a href="p3-payload.html#media.types" title="Media Types">Section 3.3</a> of <a href="#Part3" id="rfc.xref.Part3.2"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>.
     739            in <a href="p3-payload.html#media.types" title="Media Types">Section 2.3</a> of <a href="#Part3" id="rfc.xref.Part3.2"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>.
    740740         </p>
    741741      </div>
     
    786786</pre><h3 id="rfc.section.1.2.3"><a href="#rfc.section.1.2.3">1.2.3</a>&nbsp;<a id="abnf.dependencies" href="#abnf.dependencies">ABNF Rules defined in other Parts of the Specification</a></h3>
    787787      <p id="rfc.section.1.2.3.p.1">The ABNF rules below are defined in other parts:</p>
    788       <div id="rfc.figure.u.9"></div><pre class="inline">  <a href="#abnf.dependencies" class="smpl">request-header</a>  = &lt;request-header, defined in <a href="#Part2" id="rfc.xref.Part2.1"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>, <a href="p2-semantics.html#request.header.fields" title="Request Header Fields">Section 4</a>&gt;
    789   <a href="#abnf.dependencies" class="smpl">response-header</a> = &lt;response-header, defined in <a href="#Part2" id="rfc.xref.Part2.2"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>, <a href="p2-semantics.html#response.header.fields" title="Response Header Fields">Section 6</a>&gt;
    790 </pre><div id="rfc.figure.u.10"></div><pre class="inline">  <a href="#abnf.dependencies" class="smpl">accept-params</a>   = &lt;accept-params, defined in <a href="#Part3" id="rfc.xref.Part3.3"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="p3-payload.html#header.accept" title="Accept">Section 6.1</a>&gt;
    791   <a href="#abnf.dependencies" class="smpl">entity-body</a>     = &lt;entity-body, defined in <a href="#Part3" id="rfc.xref.Part3.4"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="p3-payload.html#entity.body" title="Entity Body">Section 4.2</a>&gt;
    792   <a href="#abnf.dependencies" class="smpl">entity-header</a>   = &lt;entity-header, defined in <a href="#Part3" id="rfc.xref.Part3.5"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="p3-payload.html#entity.header.fields" title="Entity Header Fields">Section 4.1</a>&gt;
    793 </pre><div id="rfc.figure.u.11"></div><pre class="inline">  <a href="#abnf.dependencies" class="smpl">Cache-Control</a>   = &lt;Cache-Control, defined in <a href="#Part6" id="rfc.xref.Part6.1"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>, <a href="p6-cache.html#header.pragma" title="Pragma">Section 16.4</a>&gt;
    794   <a href="#abnf.dependencies" class="smpl">Pragma</a>          = &lt;Pragma, defined in <a href="#Part6" id="rfc.xref.Part6.2"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>, <a href="p6-cache.html#header.pragma" title="Pragma">Section 16.4</a>&gt;
    795   <a href="#abnf.dependencies" class="smpl">Warning</a>         = &lt;Warning, defined in <a href="#Part6" id="rfc.xref.Part6.3"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>, <a href="p6-cache.html#header.warning" title="Warning">Section 16.6</a>&gt;
     788      <div id="rfc.figure.u.9"></div><pre class="inline">  <a href="#abnf.dependencies" class="smpl">request-header</a>  = &lt;request-header, defined in <a href="#Part2" id="rfc.xref.Part2.1"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>, <a href="p2-semantics.html#request.header.fields" title="Request Header Fields">Section 3</a>&gt;
     789  <a href="#abnf.dependencies" class="smpl">response-header</a> = &lt;response-header, defined in <a href="#Part2" id="rfc.xref.Part2.2"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>, <a href="p2-semantics.html#response.header.fields" title="Response Header Fields">Section 5</a>&gt;
     790</pre><div id="rfc.figure.u.10"></div><pre class="inline">  <a href="#abnf.dependencies" class="smpl">accept-params</a>   = &lt;accept-params, defined in <a href="#Part3" id="rfc.xref.Part3.3"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="p3-payload.html#header.accept" title="Accept">Section 5.1</a>&gt;
     791  <a href="#abnf.dependencies" class="smpl">entity-body</a>     = &lt;entity-body, defined in <a href="#Part3" id="rfc.xref.Part3.4"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="p3-payload.html#entity.body" title="Entity Body">Section 3.2</a>&gt;
     792  <a href="#abnf.dependencies" class="smpl">entity-header</a>   = &lt;entity-header, defined in <a href="#Part3" id="rfc.xref.Part3.5"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="p3-payload.html#entity.header.fields" title="Entity Header Fields">Section 3.1</a>&gt;
     793</pre><div id="rfc.figure.u.11"></div><pre class="inline">  <a href="#abnf.dependencies" class="smpl">Cache-Control</a>   = &lt;Cache-Control, defined in <a href="#Part6" id="rfc.xref.Part6.1"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>, <a href="p6-cache.html#header.pragma" title="Pragma">Section 15.4</a>&gt;
     794  <a href="#abnf.dependencies" class="smpl">Pragma</a>          = &lt;Pragma, defined in <a href="#Part6" id="rfc.xref.Part6.2"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>, <a href="p6-cache.html#header.pragma" title="Pragma">Section 15.4</a>&gt;
     795  <a href="#abnf.dependencies" class="smpl">Warning</a>         = &lt;Warning, defined in <a href="#Part6" id="rfc.xref.Part6.3"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>, <a href="p6-cache.html#header.warning" title="Warning">Section 15.6</a>&gt;
    796796</pre><h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a>&nbsp;<a id="architecture" href="#architecture">HTTP architecture</a></h1>
    797797      <p id="rfc.section.2.p.1">HTTP was created with a specific architecture in mind, the World Wide Web, and has evolved over time to support the scalability
     
    10521052      </p>
    10531053      <p id="rfc.section.3.3.p.8">The Internet Assigned Numbers Authority (IANA) acts as a registry for transfer-coding value tokens. Initially, the registry
    1054          contains the following tokens: "chunked" (<a href="#chunked.transfer.encoding" title="Chunked Transfer Coding">Section&nbsp;3.3.1</a>), "gzip", "compress", and "deflate" (<a href="p3-payload.html#content.codings" title="Content Codings">Section 3.2</a> of <a href="#Part3" id="rfc.xref.Part3.6"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>).
    1055       </p>
    1056       <p id="rfc.section.3.3.p.9">New transfer-coding value tokens <em class="bcp14">SHOULD</em> be registered in the same way as new content-coding value tokens (<a href="p3-payload.html#content.codings" title="Content Codings">Section 3.2</a> of <a href="#Part3" id="rfc.xref.Part3.7"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>).
     1054         contains the following tokens: "chunked" (<a href="#chunked.transfer.encoding" title="Chunked Transfer Coding">Section&nbsp;3.3.1</a>), "gzip", "compress", and "deflate" (<a href="p3-payload.html#content.codings" title="Content Codings">Section 2.2</a> of <a href="#Part3" id="rfc.xref.Part3.6"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>).
     1055      </p>
     1056      <p id="rfc.section.3.3.p.9">New transfer-coding value tokens <em class="bcp14">SHOULD</em> be registered in the same way as new content-coding value tokens (<a href="p3-payload.html#content.codings" title="Content Codings">Section 2.2</a> of <a href="#Part3" id="rfc.xref.Part3.7"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>).
    10571057      </p>
    10581058      <p id="rfc.section.3.3.p.10">A server which receives an entity-body with a transfer-coding it does not understand <em class="bcp14">SHOULD</em> return 501 (Not Implemented), and close the connection. A server <em class="bcp14">MUST NOT</em> send transfer-codings to an HTTP/1.0 client.
     
    12121212      <p id="rfc.section.4.3.p.4">The rules for when a message-body is allowed in a message differ for requests and responses.</p>
    12131213      <p id="rfc.section.4.3.p.5">The presence of a message-body in a request is signaled by the inclusion of a Content-Length or Transfer-Encoding header field
    1214          in the request's message-headers. A message-body <em class="bcp14">MUST NOT</em> be included in a request if the specification of the request method (<a href="p2-semantics.html#method" title="Method">Section 3</a> of <a href="#Part2" id="rfc.xref.Part2.3"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>) explicitly disallows an entity-body in requests. When a request message contains both a message-body of non-zero length
     1214         in the request's message-headers. A message-body <em class="bcp14">MUST NOT</em> be included in a request if the specification of the request method (<a href="p2-semantics.html#method" title="Method">Section 2</a> of <a href="#Part2" id="rfc.xref.Part2.3"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>) explicitly disallows an entity-body in requests. When a request message contains both a message-body of non-zero length
    12151215         and a method that does not define any semantics for that request message-body, then an origin server <em class="bcp14">SHOULD</em> either ignore the message-body or respond with an appropriate error message (e.g., 413). A proxy or gateway, when presented
    12161216         the same request, <em class="bcp14">SHOULD</em> either forward the request inbound with the message-body or ignore the message-body when determining a response.
     
    12731273         to the entity being transferred. These header fields apply only to the message being transmitted.
    12741274      </p>
    1275       <div id="rfc.figure.u.32"></div><pre class="inline"><span id="rfc.iref.g.71"></span>  <a href="#general.header.fields" class="smpl">general-header</a> = <a href="#abnf.dependencies" class="smpl">Cache-Control</a>            ; <a href="#Part6" id="rfc.xref.Part6.5"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>, <a href="p6-cache.html#header.cache-control" title="Cache-Control">Section 16.2</a>
     1275      <div id="rfc.figure.u.32"></div><pre class="inline"><span id="rfc.iref.g.71"></span>  <a href="#general.header.fields" class="smpl">general-header</a> = <a href="#abnf.dependencies" class="smpl">Cache-Control</a>            ; <a href="#Part6" id="rfc.xref.Part6.5"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>, <a href="p6-cache.html#header.cache-control" title="Cache-Control">Section 15.2</a>
    12761276                 / <a href="#header.connection" class="smpl">Connection</a>               ; <a href="#header.connection" id="rfc.xref.header.connection.1" title="Connection">Section&nbsp;8.1</a>
    12771277                 / <a href="#header.date" class="smpl">Date</a>                     ; <a href="#header.date" id="rfc.xref.header.date.1" title="Date">Section&nbsp;8.3</a>
    1278                  / <a href="#abnf.dependencies" class="smpl">Pragma</a>                   ; <a href="#Part6" id="rfc.xref.Part6.6"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>, <a href="p6-cache.html#header.pragma" title="Pragma">Section 16.4</a>
     1278                 / <a href="#abnf.dependencies" class="smpl">Pragma</a>                   ; <a href="#Part6" id="rfc.xref.Part6.6"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>, <a href="p6-cache.html#header.pragma" title="Pragma">Section 15.4</a>
    12791279                 / <a href="#header.trailer" class="smpl">Trailer</a>                  ; <a href="#header.trailer" id="rfc.xref.header.trailer.2" title="Trailer">Section&nbsp;8.6</a>
    12801280                 / <a href="#header.transfer-encoding" class="smpl">Transfer-Encoding</a>        ; <a href="#header.transfer-encoding" id="rfc.xref.header.transfer-encoding.4" title="Transfer-Encoding">Section&nbsp;8.7</a>
    12811281                 / <a href="#header.upgrade" class="smpl">Upgrade</a>                  ; <a href="#header.upgrade" id="rfc.xref.header.upgrade.1" title="Upgrade">Section&nbsp;8.8</a>
    12821282                 / <a href="#header.via" class="smpl">Via</a>                      ; <a href="#header.via" id="rfc.xref.header.via.1" title="Via">Section&nbsp;8.9</a>
    1283                  / <a href="#abnf.dependencies" class="smpl">Warning</a>                  ; <a href="#Part6" id="rfc.xref.Part6.7"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>, <a href="p6-cache.html#header.warning" title="Warning">Section 16.6</a>
     1283                 / <a href="#abnf.dependencies" class="smpl">Warning</a>                  ; <a href="#Part6" id="rfc.xref.Part6.7"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>, <a href="p6-cache.html#header.warning" title="Warning">Section 15.6</a>
    12841284</pre><p id="rfc.section.4.5.p.3">General-header field names can be extended reliably only in combination with a change in the protocol version. However, new
    12851285         or experimental header fields may be given the semantics of general header fields if all parties in the communication recognize
     
    12921292      <div id="rfc.figure.u.33"></div><pre class="inline"><span id="rfc.iref.g.72"></span>  <a href="#request" class="smpl">Request</a>       = <a href="#request-line" class="smpl">Request-Line</a>              ; <a href="#request-line" title="Request-Line">Section&nbsp;5.1</a>
    12931293                  *(( <a href="#general.header.fields" class="smpl">general-header</a>        ; <a href="#general.header.fields" title="General Header Fields">Section&nbsp;4.5</a>
    1294                    / <a href="#abnf.dependencies" class="smpl">request-header</a>         ; <a href="#Part2" id="rfc.xref.Part2.4"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>, <a href="p2-semantics.html#request.header.fields" title="Request Header Fields">Section 4</a>
    1295                    / <a href="#abnf.dependencies" class="smpl">entity-header</a> ) <a href="#core.rules" class="smpl">CRLF</a>)  ; <a href="#Part3" id="rfc.xref.Part3.8"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="p3-payload.html#entity.header.fields" title="Entity Header Fields">Section 4.1</a>
     1294                   / <a href="#abnf.dependencies" class="smpl">request-header</a>         ; <a href="#Part2" id="rfc.xref.Part2.4"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>, <a href="p2-semantics.html#request.header.fields" title="Request Header Fields">Section 3</a>
     1295                   / <a href="#abnf.dependencies" class="smpl">entity-header</a> ) <a href="#core.rules" class="smpl">CRLF</a>)  ; <a href="#Part3" id="rfc.xref.Part3.8"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="p3-payload.html#entity.header.fields" title="Entity Header Fields">Section 3.1</a>
    12961296                  <a href="#core.rules" class="smpl">CRLF</a>
    12971297                  [ <a href="#message.body" class="smpl">message-body</a> ]          ; <a href="#message.body" title="Message Body">Section&nbsp;4.3</a>
     
    13241324</pre><p id="rfc.section.5.1.2.p.7">To allow for transition to absolute-URIs in all requests in future versions of HTTP, all HTTP/1.1 servers <em class="bcp14">MUST</em> accept the absolute-URI form in requests, even though HTTP/1.1 clients will only generate them in requests to proxies.
    13251325      </p>
    1326       <p id="rfc.section.5.1.2.p.8">The authority form is only used by the CONNECT method (<a href="p2-semantics.html#CONNECT" title="CONNECT">Section 8.9</a> of <a href="#Part2" id="rfc.xref.Part2.5"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>).
     1326      <p id="rfc.section.5.1.2.p.8">The authority form is only used by the CONNECT method (<a href="p2-semantics.html#CONNECT" title="CONNECT">Section 7.9</a> of <a href="#Part2" id="rfc.xref.Part2.5"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>).
    13271327      </p>
    13281328      <p id="rfc.section.5.1.2.p.9">The most common form of request-target is that used to identify a resource on an origin server or gateway. In this case the
     
    13571357      </dl>
    13581358      <p id="rfc.section.5.1.2.p.18">HTTP does not place a pre-defined limit on the length of a request-target. A server <em class="bcp14">MUST</em> be prepared to receive URIs of unbounded length and respond with the 414 (Request-target too Long) status if the received
    1359          request-target would be longer than the server wishes to handle (see <a href="p2-semantics.html#status.414" title="414 Request-target Too Long">Section 9.4.15</a> of <a href="#Part2" id="rfc.xref.Part2.6"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>).
     1359         request-target would be longer than the server wishes to handle (see <a href="p2-semantics.html#status.414" title="414 Request-target Too Long">Section 8.4.15</a> of <a href="#Part2" id="rfc.xref.Part2.6"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>).
    13601360      </p>
    13611361      <p id="rfc.section.5.1.2.p.19">Various ad-hoc limitations on request-target length are found in practice. It is <em class="bcp14">RECOMMENDED</em> that all HTTP senders and recipients support request-target lengths of 8000 or more OCTETs.
     
    13861386      <div id="rfc.figure.u.42"></div><pre class="inline"><span id="rfc.iref.g.77"></span>  <a href="#response" class="smpl">Response</a>      = <a href="#status-line" class="smpl">Status-Line</a>               ; <a href="#status-line" title="Status-Line">Section&nbsp;6.1</a>
    13871387                  *(( <a href="#general.header.fields" class="smpl">general-header</a>        ; <a href="#general.header.fields" title="General Header Fields">Section&nbsp;4.5</a>
    1388                    / <a href="#abnf.dependencies" class="smpl">response-header</a>        ; <a href="#Part2" id="rfc.xref.Part2.7"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>, <a href="p2-semantics.html#response.header.fields" title="Response Header Fields">Section 6</a>
    1389                    / <a href="#abnf.dependencies" class="smpl">entity-header</a> ) <a href="#core.rules" class="smpl">CRLF</a>)  ; <a href="#Part3" id="rfc.xref.Part3.9"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="p3-payload.html#entity.header.fields" title="Entity Header Fields">Section 4.1</a>
     1388                   / <a href="#abnf.dependencies" class="smpl">response-header</a>        ; <a href="#Part2" id="rfc.xref.Part2.7"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>, <a href="p2-semantics.html#response.header.fields" title="Response Header Fields">Section 5</a>
     1389                   / <a href="#abnf.dependencies" class="smpl">entity-header</a> ) <a href="#core.rules" class="smpl">CRLF</a>)  ; <a href="#Part3" id="rfc.xref.Part3.9"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="p3-payload.html#entity.header.fields" title="Entity Header Fields">Section 3.1</a>
    13901390                  <a href="#core.rules" class="smpl">CRLF</a>
    13911391                  [ <a href="#message.body" class="smpl">message-body</a> ]          ; <a href="#message.body" title="Message Body">Section&nbsp;4.3</a>
     
    13981398</pre><h3 id="rfc.section.6.1.1"><a href="#rfc.section.6.1.1">6.1.1</a>&nbsp;<a id="status.code.and.reason.phrase" href="#status.code.and.reason.phrase">Status Code and Reason Phrase</a></h3>
    13991399      <p id="rfc.section.6.1.1.p.1">The Status-Code element is a 3-digit integer result code of the attempt to understand and satisfy the request. These codes
    1400          are fully defined in <a href="p2-semantics.html#status.codes" title="Status Code Definitions">Section 9</a> of <a href="#Part2" id="rfc.xref.Part2.8"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>. The Reason Phrase exists for the sole purpose of providing a textual description associated with the numeric status code,
     1400         are fully defined in <a href="p2-semantics.html#status.codes" title="Status Code Definitions">Section 8</a> of <a href="#Part2" id="rfc.xref.Part2.8"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>. The Reason Phrase exists for the sole purpose of providing a textual description associated with the numeric status code,
    14011401         out of deference to earlier Internet application protocols that were more frequently used with interactive text clients. A
    14021402         client <em class="bcp14">SHOULD</em> ignore the content of the Reason Phrase.
     
    14681468      <p id="rfc.section.7.1.2.2.p.2">Clients which assume persistent connections and pipeline immediately after connection establishment <em class="bcp14">SHOULD</em> be prepared to retry their connection if the first pipelined attempt fails. If a client does such a retry, it <em class="bcp14">MUST NOT</em> pipeline before it knows the connection is persistent. Clients <em class="bcp14">MUST</em> also be prepared to resend their requests if the server closes the connection before sending all of the corresponding responses.
    14691469      </p>
    1470       <p id="rfc.section.7.1.2.2.p.3">Clients <em class="bcp14">SHOULD NOT</em> pipeline requests using non-idempotent methods or non-idempotent sequences of methods (see <a href="p2-semantics.html#idempotent.methods" title="Idempotent Methods">Section 8.1.2</a> of <a href="#Part2" id="rfc.xref.Part2.9"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>). Otherwise, a premature termination of the transport connection could lead to indeterminate results. A client wishing to
     1470      <p id="rfc.section.7.1.2.2.p.3">Clients <em class="bcp14">SHOULD NOT</em> pipeline requests using non-idempotent methods or non-idempotent sequences of methods (see <a href="p2-semantics.html#idempotent.methods" title="Idempotent Methods">Section 7.1.2</a> of <a href="#Part2" id="rfc.xref.Part2.9"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>). Otherwise, a premature termination of the transport connection could lead to indeterminate results. A client wishing to
    14711471         send a non-idempotent request <em class="bcp14">SHOULD</em> wait to send that request until it has received the response status for the previous request.
    14721472      </p>
     
    14931493      </p>
    14941494      <p id="rfc.section.7.1.4.p.4">This means that clients, servers, and proxies <em class="bcp14">MUST</em> be able to recover from asynchronous close events. Client software <em class="bcp14">SHOULD</em> reopen the transport connection and retransmit the aborted sequence of requests without user interaction so long as the request
    1495          sequence is idempotent (see <a href="p2-semantics.html#idempotent.methods" title="Idempotent Methods">Section 8.1.2</a> of <a href="#Part2" id="rfc.xref.Part2.10"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>). Non-idempotent methods or sequences <em class="bcp14">MUST NOT</em> be automatically retried, although user agents <em class="bcp14">MAY</em> offer a human operator the choice of retrying the request(s). Confirmation by user-agent software with semantic understanding
     1495         sequence is idempotent (see <a href="p2-semantics.html#idempotent.methods" title="Idempotent Methods">Section 7.1.2</a> of <a href="#Part2" id="rfc.xref.Part2.10"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>). Non-idempotent methods or sequences <em class="bcp14">MUST NOT</em> be automatically retried, although user agents <em class="bcp14">MAY</em> offer a human operator the choice of retrying the request(s). Confirmation by user-agent software with semantic understanding
    14961496         of the application <em class="bcp14">MAY</em> substitute for user confirmation. The automatic retry <em class="bcp14">SHOULD NOT</em> be repeated if the second sequence of requests fails.
    14971497      </p>
     
    15111511      </p>
    15121512      <h3 id="rfc.section.7.2.3"><a href="#rfc.section.7.2.3">7.2.3</a>&nbsp;<a id="use.of.the.100.status" href="#use.of.the.100.status">Use of the 100 (Continue) Status</a></h3>
    1513       <p id="rfc.section.7.2.3.p.1">The purpose of the 100 (Continue) status (see <a href="p2-semantics.html#status.100" title="100 Continue">Section 9.1.1</a> of <a href="#Part2" id="rfc.xref.Part2.11"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>) is to allow a client that is sending a request message with a request body to determine if the origin server is willing
     1513      <p id="rfc.section.7.2.3.p.1">The purpose of the 100 (Continue) status (see <a href="p2-semantics.html#status.100" title="100 Continue">Section 8.1.1</a> of <a href="#Part2" id="rfc.xref.Part2.11"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>) is to allow a client that is sending a request message with a request body to determine if the origin server is willing
    15141514         to accept the request (based on the request headers) before the client sends the request body. In some cases, it might either
    15151515         be inappropriate or highly inefficient for the client to send the body if the server will reject the message without looking
     
    15181518      <p id="rfc.section.7.2.3.p.2">Requirements for HTTP/1.1 clients: </p>
    15191519      <ul>
    1520          <li>If a client will wait for a 100 (Continue) response before sending the request body, it <em class="bcp14">MUST</em> send an Expect request-header field (<a href="p2-semantics.html#header.expect" title="Expect">Section 10.2</a> of <a href="#Part2" id="rfc.xref.Part2.12"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>) with the "100-continue" expectation.
    1521          </li>
    1522          <li>A client <em class="bcp14">MUST NOT</em> send an Expect request-header field (<a href="p2-semantics.html#header.expect" title="Expect">Section 10.2</a> of <a href="#Part2" id="rfc.xref.Part2.13"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>) with the "100-continue" expectation if it does not intend to send a request body.
     1520         <li>If a client will wait for a 100 (Continue) response before sending the request body, it <em class="bcp14">MUST</em> send an Expect request-header field (<a href="p2-semantics.html#header.expect" title="Expect">Section 9.2</a> of <a href="#Part2" id="rfc.xref.Part2.12"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>) with the "100-continue" expectation.
     1521         </li>
     1522         <li>A client <em class="bcp14">MUST NOT</em> send an Expect request-header field (<a href="p2-semantics.html#header.expect" title="Expect">Section 9.2</a> of <a href="#Part2" id="rfc.xref.Part2.13"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>) with the "100-continue" expectation if it does not intend to send a request body.
    15231523         </li>
    15241524      </ul>
     
    15641564         <li>A proxy <em class="bcp14">MUST NOT</em> forward a 100 (Continue) response if the request message was received from an HTTP/1.0 (or earlier) client and did not include
    15651565            an Expect request-header field with the "100-continue" expectation. This requirement overrides the general rule for forwarding
    1566             of 1xx responses (see <a href="p2-semantics.html#status.1xx" title="Informational 1xx">Section 9.1</a> of <a href="#Part2" id="rfc.xref.Part2.14"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>).
     1566            of 1xx responses (see <a href="p2-semantics.html#status.1xx" title="Informational 1xx">Section 8.1</a> of <a href="#Part2" id="rfc.xref.Part2.14"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>).
    15671567         </li>
    15681568      </ul>
     
    17361736         <li>
    17371737            <p>If the transfer-coding being tested is one of the transfer-codings listed in the TE field, then it is acceptable unless it
    1738                is accompanied by a qvalue of 0. (As defined in <a href="p3-payload.html#quality.values" title="Quality Values">Section 3.4</a> of <a href="#Part3" id="rfc.xref.Part3.10"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, a qvalue of 0 means "not acceptable.")
     1738               is accompanied by a qvalue of 0. (As defined in <a href="p3-payload.html#quality.values" title="Quality Values">Section 2.4</a> of <a href="#Part3" id="rfc.xref.Part3.10"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, a qvalue of 0 means "not acceptable.")
    17391739            </p>
    17401740         </li>
     
    25172517      </p>
    25182518      <dl class="empty">
    2519          <dd>The mechanism for selecting the appropriate representation when servicing a request, as described in <a href="p3-payload.html#content.negotiation" title="Content Negotiation">Section 5</a> of <a href="#Part3" id="rfc.xref.Part3.13"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>. The representation of entities in any response can be negotiated (including error responses).
     2519         <dd>The mechanism for selecting the appropriate representation when servicing a request, as described in <a href="p3-payload.html#content.negotiation" title="Content Negotiation">Section 4</a> of <a href="#Part3" id="rfc.xref.Part3.13"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>. The representation of entities in any response can be negotiated (including error responses).
    25202520         </dd>
    25212521      </dl>
     
    25242524      <dl class="empty">
    25252525         <dd>The information transferred as the payload of a request or response. An entity consists of metainformation in the form of
    2526             entity-header fields and content in the form of an entity-body, as described in <a href="p3-payload.html#entity" title="Entity">Section 4</a> of <a href="#Part3" id="rfc.xref.Part3.14"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>.
     2526            entity-header fields and content in the form of an entity-body, as described in <a href="p3-payload.html#entity" title="Entity">Section 3</a> of <a href="#Part3" id="rfc.xref.Part3.14"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>.
    25272527         </dd>
    25282528      </dl>
     
    25852585      </p>
    25862586      <dl class="empty">
    2587          <dd>An entity included with a response that is subject to content negotiation, as described in <a href="p3-payload.html#content.negotiation" title="Content Negotiation">Section 5</a> of <a href="#Part3" id="rfc.xref.Part3.15"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>. There may exist multiple representations associated with a particular response status.
     2587         <dd>An entity included with a response that is subject to content negotiation, as described in <a href="p3-payload.html#content.negotiation" title="Content Negotiation">Section 4</a> of <a href="#Part3" id="rfc.xref.Part3.15"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>. There may exist multiple representations associated with a particular response status.
    25882588         </dd>
    25892589      </dl>
     
    26262626      <h1 id="rfc.section.D"><a href="#rfc.section.D">D.</a>&nbsp;<a id="collected.abnf" href="#collected.abnf">Collected ABNF</a></h1>
    26272627      <div id="rfc.figure.u.64"></div> <pre class="inline">BWS = OWS
    2628 Cache-Control = &lt;Cache-Control, defined in [Part6], Section 16.4&gt;
     2628Cache-Control = &lt;Cache-Control, defined in [Part6], Section 15.4&gt;
    26292629Chunked-Body = *chunk last-chunk trailer-part CRLF
    26302630Connection = "Connection:" OWS Connection-v
     
    26442644Method = token
    26452645OWS = *( [ obs-fold ] WSP )
    2646 Pragma = &lt;Pragma, defined in [Part6], Section 16.4&gt;
     2646Pragma = &lt;Pragma, defined in [Part6], Section 15.4&gt;
    26472647RWS = 1*( [ obs-fold ] WSP )
    26482648Reason-Phrase = *( WSP / VCHAR / obs-text )
     
    26692669 ] *( OWS "," [ OWS received-protocol RWS received-by [ RWS comment ]
    26702670 ] )
    2671 Warning = &lt;Warning, defined in [Part6], Section 16.6&gt;
     2671Warning = &lt;Warning, defined in [Part6], Section 15.6&gt;
    26722672absolute-URI = &lt;absolute-URI, defined in [RFC3986], Section 4.3&gt;
    2673 accept-params = &lt;accept-params, defined in [Part3], Section 6.1&gt;
     2673accept-params = &lt;accept-params, defined in [Part3], Section 5.1&gt;
    26742674asctime-date = wkday SP date3 SP time SP 4DIGIT
    26752675attribute = token
     
    26872687date2 = 2DIGIT "-" month "-" 2DIGIT
    26882688date3 = month SP ( 2DIGIT / ( SP DIGIT ) )
    2689 entity-body = &lt;entity-body, defined in [Part3], Section 4.2&gt;
    2690 entity-header = &lt;entity-header, defined in [Part3], Section 4.1&gt;
     2689entity-body = &lt;entity-body, defined in [Part3], Section 3.2&gt;
     2690entity-header = &lt;entity-header, defined in [Part3], Section 3.1&gt;
    26912691field-content = *( WSP / VCHAR / obs-text )
    26922692field-name = token
     
    27322732received-protocol = [ protocol-name "/" ] protocol-version
    27332733relative-part = &lt;relative-part, defined in [RFC3986], Section 4.2&gt;
    2734 request-header = &lt;request-header, defined in [Part2], Section 4&gt;
     2734request-header = &lt;request-header, defined in [Part2], Section 3&gt;
    27352735request-target = "*" / absolute-URI / ( path-absolute [ "?" query ] )
    27362736 / authority
    2737 response-header = &lt;response-header, defined in [Part2], Section 6&gt;
     2737response-header = &lt;response-header, defined in [Part2], Section 5&gt;
    27382738rfc1123-date = wkday "," SP date1 SP time SP GMT
    27392739rfc850-date = weekday "," SP date2 SP time SP GMT
     
    31713171                  <li class="indline1"><em>Pad1995</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Pad1995.1">7.1.1</a>, <a class="iref" href="#Pad1995"><b>12.2</b></a></li>
    31723172                  <li class="indline1"><em>Part2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part2.1">1.2.3</a>, <a class="iref" href="#rfc.xref.Part2.2">1.2.3</a>, <a class="iref" href="#rfc.xref.Part2.3">4.3</a>, <a class="iref" href="#rfc.xref.Part2.4">5</a>, <a class="iref" href="#rfc.xref.Part2.5">5.1.2</a>, <a class="iref" href="#rfc.xref.Part2.6">5.1.2</a>, <a class="iref" href="#rfc.xref.Part2.7">6</a>, <a class="iref" href="#rfc.xref.Part2.8">6.1.1</a>, <a class="iref" href="#rfc.xref.Part2.9">7.1.2.2</a>, <a class="iref" href="#rfc.xref.Part2.10">7.1.4</a>, <a class="iref" href="#rfc.xref.Part2.11">7.2.3</a>, <a class="iref" href="#rfc.xref.Part2.12">7.2.3</a>, <a class="iref" href="#rfc.xref.Part2.13">7.2.3</a>, <a class="iref" href="#rfc.xref.Part2.14">7.2.3</a>, <a class="iref" href="#Part2"><b>12.1</b></a><ul class="ind">
    3173                         <li class="indline1"><em>Section 3</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part2.3">4.3</a></li>
    3174                         <li class="indline1"><em>Section 4</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part2.1">1.2.3</a>, <a class="iref" href="#rfc.xref.Part2.4">5</a></li>
    3175                         <li class="indline1"><em>Section 6</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part2.2">1.2.3</a>, <a class="iref" href="#rfc.xref.Part2.7">6</a></li>
    3176                         <li class="indline1"><em>Section 8.1.2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part2.9">7.1.2.2</a>, <a class="iref" href="#rfc.xref.Part2.10">7.1.4</a></li>
    3177                         <li class="indline1"><em>Section 8.9</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part2.5">5.1.2</a></li>
    3178                         <li class="indline1"><em>Section 9</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part2.8">6.1.1</a></li>
    3179                         <li class="indline1"><em>Section 9.1.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part2.11">7.2.3</a></li>
    3180                         <li class="indline1"><em>Section 9.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part2.14">7.2.3</a></li>
    3181                         <li class="indline1"><em>Section 9.4.15</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part2.6">5.1.2</a></li>
    3182                         <li class="indline1"><em>Section 10.2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part2.12">7.2.3</a>, <a class="iref" href="#rfc.xref.Part2.13">7.2.3</a></li>
     3173                        <li class="indline1"><em>Section 2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part2.3">4.3</a></li>
     3174                        <li class="indline1"><em>Section 3</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part2.1">1.2.3</a>, <a class="iref" href="#rfc.xref.Part2.4">5</a></li>
     3175                        <li class="indline1"><em>Section 5</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part2.2">1.2.3</a>, <a class="iref" href="#rfc.xref.Part2.7">6</a></li>
     3176                        <li class="indline1"><em>Section 7.1.2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part2.9">7.1.2.2</a>, <a class="iref" href="#rfc.xref.Part2.10">7.1.4</a></li>
     3177                        <li class="indline1"><em>Section 7.9</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part2.5">5.1.2</a></li>
     3178                        <li class="indline1"><em>Section 8</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part2.8">6.1.1</a></li>
     3179                        <li class="indline1"><em>Section 8.1.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part2.11">7.2.3</a></li>
     3180                        <li class="indline1"><em>Section 8.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part2.14">7.2.3</a></li>
     3181                        <li class="indline1"><em>Section 8.4.15</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part2.6">5.1.2</a></li>
     3182                        <li class="indline1"><em>Section 9.2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part2.12">7.2.3</a>, <a class="iref" href="#rfc.xref.Part2.13">7.2.3</a></li>
    31833183                     </ul>
    31843184                  </li>
    31853185                  <li class="indline1"><em>Part3</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.1">1</a>, <a class="iref" href="#rfc.xref.Part3.2">1.2.2</a>, <a class="iref" href="#rfc.xref.Part3.3">1.2.3</a>, <a class="iref" href="#rfc.xref.Part3.4">1.2.3</a>, <a class="iref" href="#rfc.xref.Part3.5">1.2.3</a>, <a class="iref" href="#rfc.xref.Part3.6">3.3</a>, <a class="iref" href="#rfc.xref.Part3.7">3.3</a>, <a class="iref" href="#rfc.xref.Part3.8">5</a>, <a class="iref" href="#rfc.xref.Part3.9">6</a>, <a class="iref" href="#rfc.xref.Part3.10">8.5</a>, <a class="iref" href="#Part3"><b>12.1</b></a>, <a class="iref" href="#rfc.xref.Part3.11">A</a>, <a class="iref" href="#rfc.xref.Part3.12">B.3</a>, <a class="iref" href="#rfc.xref.Part3.13">C</a>, <a class="iref" href="#rfc.xref.Part3.14">C</a>, <a class="iref" href="#rfc.xref.Part3.15">C</a><ul class="ind">
    3186                         <li class="indline1"><em>Section 3.2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.6">3.3</a>, <a class="iref" href="#rfc.xref.Part3.7">3.3</a></li>
    3187                         <li class="indline1"><em>Section 3.3</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.2">1.2.2</a></li>
    3188                         <li class="indline1"><em>Section 3.4</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.10">8.5</a></li>
    3189                         <li class="indline1"><em>Section 4.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.5">1.2.3</a>, <a class="iref" href="#rfc.xref.Part3.8">5</a>, <a class="iref" href="#rfc.xref.Part3.9">6</a></li>
    3190                         <li class="indline1"><em>Section 4</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.14">C</a></li>
    3191                         <li class="indline1"><em>Section 4.2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.4">1.2.3</a></li>
    3192                         <li class="indline1"><em>Section 5</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.13">C</a>, <a class="iref" href="#rfc.xref.Part3.15">C</a></li>
    3193                         <li class="indline1"><em>Section 6.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.3">1.2.3</a></li>
     3186                        <li class="indline1"><em>Section 2.2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.6">3.3</a>, <a class="iref" href="#rfc.xref.Part3.7">3.3</a></li>
     3187                        <li class="indline1"><em>Section 2.3</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.2">1.2.2</a></li>
     3188                        <li class="indline1"><em>Section 2.4</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.10">8.5</a></li>
     3189                        <li class="indline1"><em>Section 3.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.5">1.2.3</a>, <a class="iref" href="#rfc.xref.Part3.8">5</a>, <a class="iref" href="#rfc.xref.Part3.9">6</a></li>
     3190                        <li class="indline1"><em>Section 3</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.14">C</a></li>
     3191                        <li class="indline1"><em>Section 3.2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.4">1.2.3</a></li>
     3192                        <li class="indline1"><em>Section 4</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.13">C</a>, <a class="iref" href="#rfc.xref.Part3.15">C</a></li>
     3193                        <li class="indline1"><em>Section 5.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.3">1.2.3</a></li>
    31943194                        <li class="indline1"><em>Appendix A</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.1">1</a></li>
    31953195                     </ul>
     
    31983198                  <li class="indline1"><em>Part6</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part6.1">1.2.3</a>, <a class="iref" href="#rfc.xref.Part6.2">1.2.3</a>, <a class="iref" href="#rfc.xref.Part6.3">1.2.3</a>, <a class="iref" href="#rfc.xref.Part6.4">2.2</a>, <a class="iref" href="#rfc.xref.Part6.5">4.5</a>, <a class="iref" href="#rfc.xref.Part6.6">4.5</a>, <a class="iref" href="#rfc.xref.Part6.7">4.5</a>, <a class="iref" href="#Part6"><b>12.1</b></a>, <a class="iref" href="#rfc.xref.Part6.8">B.3</a>, <a class="iref" href="#rfc.xref.Part6.9">C</a><ul class="ind">
    31993199                        <li class="indline1"><em>Section 1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part6.4">2.2</a>, <a class="iref" href="#rfc.xref.Part6.9">C</a></li>
    3200                         <li class="indline1"><em>Section 16.2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part6.5">4.5</a></li>
    3201                         <li class="indline1"><em>Section 16.4</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part6.1">1.2.3</a>, <a class="iref" href="#rfc.xref.Part6.2">1.2.3</a>, <a class="iref" href="#rfc.xref.Part6.6">4.5</a></li>
    3202                         <li class="indline1"><em>Section 16.6</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part6.3">1.2.3</a>, <a class="iref" href="#rfc.xref.Part6.7">4.5</a></li>
     3200                        <li class="indline1"><em>Section 15.2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part6.5">4.5</a></li>
     3201                        <li class="indline1"><em>Section 15.4</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part6.1">1.2.3</a>, <a class="iref" href="#rfc.xref.Part6.2">1.2.3</a>, <a class="iref" href="#rfc.xref.Part6.6">4.5</a></li>
     3202                        <li class="indline1"><em>Section 15.6</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part6.3">1.2.3</a>, <a class="iref" href="#rfc.xref.Part6.7">4.5</a></li>
    32033203                     </ul>
    32043204                  </li>
  • draft-ietf-httpbis/latest/p1-messaging.xml

    r423 r424  
    44004400   <figure>
    44014401      <artwork type="abnf" name="p1-messaging.parsed-abnf">BWS = OWS&#xD;
    4402 Cache-Control = &lt;Cache-Control, defined in [Part6], Section 16.4&gt;&#xD;
     4402Cache-Control = &lt;Cache-Control, defined in [Part6], Section 15.4&gt;&#xD;
    44034403Chunked-Body = *chunk last-chunk trailer-part CRLF&#xD;
    44044404Connection = "Connection:" OWS Connection-v&#xD;
     
    44184418Method = token&#xD;
    44194419OWS = *( [ obs-fold ] WSP )&#xD;
    4420 Pragma = &lt;Pragma, defined in [Part6], Section 16.4&gt;&#xD;
     4420Pragma = &lt;Pragma, defined in [Part6], Section 15.4&gt;&#xD;
    44214421RWS = 1*( [ obs-fold ] WSP )&#xD;
    44224422Reason-Phrase = *( WSP / VCHAR / obs-text )&#xD;
     
    44434443 ] *( OWS "," [ OWS received-protocol RWS received-by [ RWS comment ]&#xD;
    44444444 ] )&#xD;
    4445 Warning = &lt;Warning, defined in [Part6], Section 16.6&gt;&#xD;
     4445Warning = &lt;Warning, defined in [Part6], Section 15.6&gt;&#xD;
    44464446absolute-URI = &lt;absolute-URI, defined in [RFC3986], Section 4.3&gt;&#xD;
    4447 accept-params = &lt;accept-params, defined in [Part3], Section 6.1&gt;&#xD;
     4447accept-params = &lt;accept-params, defined in [Part3], Section 5.1&gt;&#xD;
    44484448asctime-date = wkday SP date3 SP time SP 4DIGIT&#xD;
    44494449attribute = token&#xD;
     
    44614461date2 = 2DIGIT "-" month "-" 2DIGIT&#xD;
    44624462date3 = month SP ( 2DIGIT / ( SP DIGIT ) )&#xD;
    4463 entity-body = &lt;entity-body, defined in [Part3], Section 4.2&gt;&#xD;
    4464 entity-header = &lt;entity-header, defined in [Part3], Section 4.1&gt;&#xD;
     4463entity-body = &lt;entity-body, defined in [Part3], Section 3.2&gt;&#xD;
     4464entity-header = &lt;entity-header, defined in [Part3], Section 3.1&gt;&#xD;
    44654465field-content = *( WSP / VCHAR / obs-text )&#xD;
    44664466field-name = token&#xD;
     
    45064506received-protocol = [ protocol-name "/" ] protocol-version&#xD;
    45074507relative-part = &lt;relative-part, defined in [RFC3986], Section 4.2&gt;&#xD;
    4508 request-header = &lt;request-header, defined in [Part2], Section 4&gt;&#xD;
     4508request-header = &lt;request-header, defined in [Part2], Section 3&gt;&#xD;
    45094509request-target = "*" / absolute-URI / ( path-absolute [ "?" query ] )&#xD;
    45104510 / authority&#xD;
    4511 response-header = &lt;response-header, defined in [Part2], Section 6&gt;&#xD;
     4511response-header = &lt;response-header, defined in [Part2], Section 5&gt;&#xD;
    45124512rfc1123-date = wkday "," SP date1 SP time SP GMT&#xD;
    45134513rfc850-date = weekday "," SP date2 SP time SP GMT&#xD;
  • draft-ietf-httpbis/latest/p2-semantics.html

    r423 r424  
    365365      <link rel="Index" href="#rfc.index">
    366366      <link rel="Chapter" title="1 Introduction" href="#rfc.section.1">
    367       <link rel="Chapter" title="2 Notational Conventions and Generic Grammar" href="#rfc.section.2">
    368       <link rel="Chapter" title="3 Method" href="#rfc.section.3">
    369       <link rel="Chapter" title="4 Request Header Fields" href="#rfc.section.4">
    370       <link rel="Chapter" title="5 Status Code and Reason Phrase" href="#rfc.section.5">
    371       <link rel="Chapter" title="6 Response Header Fields" href="#rfc.section.6">
    372       <link rel="Chapter" title="7 Entity" href="#rfc.section.7">
    373       <link rel="Chapter" title="8 Method Definitions" href="#rfc.section.8">
    374       <link rel="Chapter" title="9 Status Code Definitions" href="#rfc.section.9">
    375       <link rel="Chapter" title="10 Header Field Definitions" href="#rfc.section.10">
    376       <link rel="Chapter" title="11 IANA Considerations" href="#rfc.section.11">
    377       <link rel="Chapter" title="12 Security Considerations" href="#rfc.section.12">
    378       <link rel="Chapter" title="13 Acknowledgments" href="#rfc.section.13">
    379       <link rel="Chapter" href="#rfc.section.14" title="14 References">
     367      <link rel="Chapter" title="2 Method" href="#rfc.section.2">
     368      <link rel="Chapter" title="3 Request Header Fields" href="#rfc.section.3">
     369      <link rel="Chapter" title="4 Status Code and Reason Phrase" href="#rfc.section.4">
     370      <link rel="Chapter" title="5 Response Header Fields" href="#rfc.section.5">
     371      <link rel="Chapter" title="6 Entity" href="#rfc.section.6">
     372      <link rel="Chapter" title="7 Method Definitions" href="#rfc.section.7">
     373      <link rel="Chapter" title="8 Status Code Definitions" href="#rfc.section.8">
     374      <link rel="Chapter" title="9 Header Field Definitions" href="#rfc.section.9">
     375      <link rel="Chapter" title="10 IANA Considerations" href="#rfc.section.10">
     376      <link rel="Chapter" title="11 Security Considerations" href="#rfc.section.11">
     377      <link rel="Chapter" title="12 Acknowledgments" href="#rfc.section.12">
     378      <link rel="Chapter" href="#rfc.section.13" title="13 References">
    380379      <link rel="Appendix" title="A Compatibility with Previous Versions" href="#rfc.section.A">
    381380      <link rel="Appendix" title="B Collected ABNF" href="#rfc.section.B">
     
    517516         <li class="tocline0">1.&nbsp;&nbsp;&nbsp;<a href="#introduction">Introduction</a><ul class="toc">
    518517               <li class="tocline1">1.1&nbsp;&nbsp;&nbsp;<a href="#intro.requirements">Requirements</a></li>
    519             </ul>
    520          </li>
    521          <li class="tocline0">2.&nbsp;&nbsp;&nbsp;<a href="#notation">Notational Conventions and Generic Grammar</a></li>
    522          <li class="tocline0">3.&nbsp;&nbsp;&nbsp;<a href="#method">Method</a><ul class="toc">
    523                <li class="tocline1">3.1&nbsp;&nbsp;&nbsp;<a href="#method.registry">Method Registry</a></li>
    524             </ul>
    525          </li>
    526          <li class="tocline0">4.&nbsp;&nbsp;&nbsp;<a href="#request.header.fields">Request Header Fields</a></li>
    527          <li class="tocline0">5.&nbsp;&nbsp;&nbsp;<a href="#status.code.and.reason.phrase">Status Code and Reason Phrase</a><ul class="toc">
    528                <li class="tocline1">5.1&nbsp;&nbsp;&nbsp;<a href="#status.code.registry">Status Code Registry</a></li>
    529             </ul>
    530          </li>
    531          <li class="tocline0">6.&nbsp;&nbsp;&nbsp;<a href="#response.header.fields">Response Header Fields</a></li>
    532          <li class="tocline0">7.&nbsp;&nbsp;&nbsp;<a href="#entity">Entity</a></li>
    533          <li class="tocline0">8.&nbsp;&nbsp;&nbsp;<a href="#method.definitions">Method Definitions</a><ul class="toc">
    534                <li class="tocline1">8.1&nbsp;&nbsp;&nbsp;<a href="#safe.and.idempotent">Safe and Idempotent Methods</a><ul class="toc">
    535                      <li class="tocline1">8.1.1&nbsp;&nbsp;&nbsp;<a href="#safe.methods">Safe Methods</a></li>
    536                      <li class="tocline1">8.1.2&nbsp;&nbsp;&nbsp;<a href="#idempotent.methods">Idempotent Methods</a></li>
    537                   </ul>
    538                </li>
    539                <li class="tocline1">8.2&nbsp;&nbsp;&nbsp;<a href="#OPTIONS">OPTIONS</a></li>
    540                <li class="tocline1">8.3&nbsp;&nbsp;&nbsp;<a href="#GET">GET</a></li>
    541                <li class="tocline1">8.4&nbsp;&nbsp;&nbsp;<a href="#HEAD">HEAD</a></li>
    542                <li class="tocline1">8.5&nbsp;&nbsp;&nbsp;<a href="#POST">POST</a></li>
    543                <li class="tocline1">8.6&nbsp;&nbsp;&nbsp;<a href="#PUT">PUT</a></li>
    544                <li class="tocline1">8.7&nbsp;&nbsp;&nbsp;<a href="#DELETE">DELETE</a></li>
    545                <li class="tocline1">8.8&nbsp;&nbsp;&nbsp;<a href="#TRACE">TRACE</a></li>
    546                <li class="tocline1">8.9&nbsp;&nbsp;&nbsp;<a href="#CONNECT">CONNECT</a></li>
    547             </ul>
    548          </li>
    549          <li class="tocline0">9.&nbsp;&nbsp;&nbsp;<a href="#status.codes">Status Code Definitions</a><ul class="toc">
    550                <li class="tocline1">9.1&nbsp;&nbsp;&nbsp;<a href="#status.1xx">Informational 1xx</a><ul class="toc">
    551                      <li class="tocline1">9.1.1&nbsp;&nbsp;&nbsp;<a href="#status.100">100 Continue</a></li>
    552                      <li class="tocline1">9.1.2&nbsp;&nbsp;&nbsp;<a href="#status.101">101 Switching Protocols</a></li>
    553                   </ul>
    554                </li>
    555                <li class="tocline1">9.2&nbsp;&nbsp;&nbsp;<a href="#status.2xx">Successful 2xx</a><ul class="toc">
    556                      <li class="tocline1">9.2.1&nbsp;&nbsp;&nbsp;<a href="#status.200">200 OK</a></li>
    557                      <li class="tocline1">9.2.2&nbsp;&nbsp;&nbsp;<a href="#status.201">201 Created</a></li>
    558                      <li class="tocline1">9.2.3&nbsp;&nbsp;&nbsp;<a href="#status.202">202 Accepted</a></li>
    559                      <li class="tocline1">9.2.4&nbsp;&nbsp;&nbsp;<a href="#status.203">203 Non-Authoritative Information</a></li>
    560                      <li class="tocline1">9.2.5&nbsp;&nbsp;&nbsp;<a href="#status.204">204 No Content</a></li>
    561                      <li class="tocline1">9.2.6&nbsp;&nbsp;&nbsp;<a href="#status.205">205 Reset Content</a></li>
    562                      <li class="tocline1">9.2.7&nbsp;&nbsp;&nbsp;<a href="#status.206">206 Partial Content</a></li>
    563                   </ul>
    564                </li>
    565                <li class="tocline1">9.3&nbsp;&nbsp;&nbsp;<a href="#status.3xx">Redirection 3xx</a><ul class="toc">
    566                      <li class="tocline1">9.3.1&nbsp;&nbsp;&nbsp;<a href="#status.300">300 Multiple Choices</a></li>
    567                      <li class="tocline1">9.3.2&nbsp;&nbsp;&nbsp;<a href="#status.301">301 Moved Permanently</a></li>
    568                      <li class="tocline1">9.3.3&nbsp;&nbsp;&nbsp;<a href="#status.302">302 Found</a></li>
    569                      <li class="tocline1">9.3.4&nbsp;&nbsp;&nbsp;<a href="#status.303">303 See Other</a></li>
    570                      <li class="tocline1">9.3.5&nbsp;&nbsp;&nbsp;<a href="#status.304">304 Not Modified</a></li>
    571                      <li class="tocline1">9.3.6&nbsp;&nbsp;&nbsp;<a href="#status.305">305 Use Proxy</a></li>
    572                      <li class="tocline1">9.3.7&nbsp;&nbsp;&nbsp;<a href="#status.306">306 (Unused)</a></li>
    573                      <li class="tocline1">9.3.8&nbsp;&nbsp;&nbsp;<a href="#status.307">307 Temporary Redirect</a></li>
    574                   </ul>
    575                </li>
    576                <li class="tocline1">9.4&nbsp;&nbsp;&nbsp;<a href="#status.4xx">Client Error 4xx</a><ul class="toc">
    577                      <li class="tocline1">9.4.1&nbsp;&nbsp;&nbsp;<a href="#status.400">400 Bad Request</a></li>
    578                      <li class="tocline1">9.4.2&nbsp;&nbsp;&nbsp;<a href="#status.401">401 Unauthorized</a></li>
    579                      <li class="tocline1">9.4.3&nbsp;&nbsp;&nbsp;<a href="#status.402">402 Payment Required</a></li>
    580                      <li class="tocline1">9.4.4&nbsp;&nbsp;&nbsp;<a href="#status.403">403 Forbidden</a></li>
    581                      <li class="tocline1">9.4.5&nbsp;&nbsp;&nbsp;<a href="#status.404">404 Not Found</a></li>
    582                      <li class="tocline1">9.4.6&nbsp;&nbsp;&nbsp;<a href="#status.405">405 Method Not Allowed</a></li>
    583                      <li class="tocline1">9.4.7&nbsp;&nbsp;&nbsp;<a href="#status.406">406 Not Acceptable</a></li>
    584                      <li class="tocline1">9.4.8&nbsp;&nbsp;&nbsp;<a href="#status.407">407 Proxy Authentication Required</a></li>
    585                      <li class="tocline1">9.4.9&nbsp;&nbsp;&nbsp;<a href="#status.408">408 Request Timeout</a></li>
    586                      <li class="tocline1">9.4.10&nbsp;&nbsp;&nbsp;<a href="#status.409">409 Conflict</a></li>
    587                      <li class="tocline1">9.4.11&nbsp;&nbsp;&nbsp;<a href="#status.410">410 Gone</a></li>
    588                      <li class="tocline1">9.4.12&nbsp;&nbsp;&nbsp;<a href="#status.411">411 Length Required</a></li>
    589                      <li class="tocline1">9.4.13&nbsp;&nbsp;&nbsp;<a href="#status.412">412 Precondition Failed</a></li>
    590                      <li class="tocline1">9.4.14&nbsp;&nbsp;&nbsp;<a href="#status.413">413 Request Entity Too Large</a></li>
    591                      <li class="tocline1">9.4.15&nbsp;&nbsp;&nbsp;<a href="#status.414">414 Request-target Too Long</a></li>
    592                      <li class="tocline1">9.4.16&nbsp;&nbsp;&nbsp;<a href="#status.415">415 Unsupported Media Type</a></li>
    593                      <li class="tocline1">9.4.17&nbsp;&nbsp;&nbsp;<a href="#status.416">416 Requested Range Not Satisfiable</a></li>
    594                      <li class="tocline1">9.4.18&nbsp;&nbsp;&nbsp;<a href="#status.417">417 Expectation Failed</a></li>
    595                   </ul>
    596                </li>
    597                <li class="tocline1">9.5&nbsp;&nbsp;&nbsp;<a href="#status.5xx">Server Error 5xx</a><ul class="toc">
    598                      <li class="tocline1">9.5.1&nbsp;&nbsp;&nbsp;<a href="#status.500">500 Internal Server Error</a></li>
    599                      <li class="tocline1">9.5.2&nbsp;&nbsp;&nbsp;<a href="#status.501">501 Not Implemented</a></li>
    600                      <li class="tocline1">9.5.3&nbsp;&nbsp;&nbsp;<a href="#status.502">502 Bad Gateway</a></li>
    601                      <li class="tocline1">9.5.4&nbsp;&nbsp;&nbsp;<a href="#status.503">503 Service Unavailable</a></li>
    602                      <li class="tocline1">9.5.5&nbsp;&nbsp;&nbsp;<a href="#status.504">504 Gateway Timeout</a></li>
    603                      <li class="tocline1">9.5.6&nbsp;&nbsp;&nbsp;<a href="#status.505">505 HTTP Version Not Supported</a></li>
     518               <li class="tocline1">1.2&nbsp;&nbsp;&nbsp;<a href="#notation">Syntax Notation</a><ul class="toc">
     519                     <li class="tocline1">1.2.1&nbsp;&nbsp;&nbsp;<a href="#core.rules">Core Rules</a></li>
     520                     <li class="tocline1">1.2.2&nbsp;&nbsp;&nbsp;<a href="#abnf.dependencies">ABNF Rules defined in other Parts of the Specification</a></li>
    604521                  </ul>
    605522               </li>
    606523            </ul>
    607524         </li>
    608          <li class="tocline0">10.&nbsp;&nbsp;&nbsp;<a href="#header.fields">Header Field Definitions</a><ul class="toc">
    609                <li class="tocline1">10.1&nbsp;&nbsp;&nbsp;<a href="#header.allow">Allow</a></li>
    610                <li class="tocline1">10.2&nbsp;&nbsp;&nbsp;<a href="#header.expect">Expect</a></li>
    611                <li class="tocline1">10.3&nbsp;&nbsp;&nbsp;<a href="#header.from">From</a></li>
    612                <li class="tocline1">10.4&nbsp;&nbsp;&nbsp;<a href="#header.location">Location</a></li>
    613                <li class="tocline1">10.5&nbsp;&nbsp;&nbsp;<a href="#header.max-forwards">Max-Forwards</a></li>
    614                <li class="tocline1">10.6&nbsp;&nbsp;&nbsp;<a href="#header.referer">Referer</a></li>
    615                <li class="tocline1">10.7&nbsp;&nbsp;&nbsp;<a href="#header.retry-after">Retry-After</a></li>
    616                <li class="tocline1">10.8&nbsp;&nbsp;&nbsp;<a href="#header.server">Server</a></li>
    617                <li class="tocline1">10.9&nbsp;&nbsp;&nbsp;<a href="#header.user-agent">User-Agent</a></li>
     525         <li class="tocline0">2.&nbsp;&nbsp;&nbsp;<a href="#method">Method</a><ul class="toc">
     526               <li class="tocline1">2.1&nbsp;&nbsp;&nbsp;<a href="#method.registry">Method Registry</a></li>
    618527            </ul>
    619528         </li>
    620          <li class="tocline0">11.&nbsp;&nbsp;&nbsp;<a href="#IANA.considerations">IANA Considerations</a><ul class="toc">
    621                <li class="tocline1">11.1&nbsp;&nbsp;&nbsp;<a href="#method.registration">Method Registry</a></li>
    622                <li class="tocline1">11.2&nbsp;&nbsp;&nbsp;<a href="#status.code.registration">Status Code Registry</a></li>
    623                <li class="tocline1">11.3&nbsp;&nbsp;&nbsp;<a href="#message.header.registration">Message Header Registration</a></li>
     529         <li class="tocline0">3.&nbsp;&nbsp;&nbsp;<a href="#request.header.fields">Request Header Fields</a></li>
     530         <li class="tocline0">4.&nbsp;&nbsp;&nbsp;<a href="#status.code.and.reason.phrase">Status Code and Reason Phrase</a><ul class="toc">
     531               <li class="tocline1">4.1&nbsp;&nbsp;&nbsp;<a href="#status.code.registry">Status Code Registry</a></li>
    624532            </ul>
    625533         </li>
    626          <li class="tocline0">12.&nbsp;&nbsp;&nbsp;<a href="#security.considerations">Security Considerations</a><ul class="toc">
    627                <li class="tocline1">12.1&nbsp;&nbsp;&nbsp;<a href="#security.sensitive">Transfer of Sensitive Information</a></li>
    628                <li class="tocline1">12.2&nbsp;&nbsp;&nbsp;<a href="#encoding.sensitive.information.in.uris">Encoding Sensitive Information in URIs</a></li>
    629                <li class="tocline1">12.3&nbsp;&nbsp;&nbsp;<a href="#location.spoofing">Location Headers and Spoofing</a></li>
     534         <li class="tocline0">5.&nbsp;&nbsp;&nbsp;<a href="#response.header.fields">Response Header Fields</a></li>
     535         <li class="tocline0">6.&nbsp;&nbsp;&nbsp;<a href="#entity">Entity</a></li>
     536         <li class="tocline0">7.&nbsp;&nbsp;&nbsp;<a href="#method.definitions">Method Definitions</a><ul class="toc">
     537               <li class="tocline1">7.1&nbsp;&nbsp;&nbsp;<a href="#safe.and.idempotent">Safe and Idempotent Methods</a><ul class="toc">
     538                     <li class="tocline1">7.1.1&nbsp;&nbsp;&nbsp;<a href="#safe.methods">Safe Methods</a></li>
     539                     <li class="tocline1">7.1.2&nbsp;&nbsp;&nbsp;<a href="#idempotent.methods">Idempotent Methods</a></li>
     540                  </ul>
     541               </li>
     542               <li class="tocline1">7.2&nbsp;&nbsp;&nbsp;<a href="#OPTIONS">OPTIONS</a></li>
     543               <li class="tocline1">7.3&nbsp;&nbsp;&nbsp;<a href="#GET">GET</a></li>
     544               <li class="tocline1">7.4&nbsp;&nbsp;&nbsp;<a href="#HEAD">HEAD</a></li>
     545               <li class="tocline1">7.5&nbsp;&nbsp;&nbsp;<a href="#POST">POST</a></li>
     546               <li class="tocline1">7.6&nbsp;&nbsp;&nbsp;<a href="#PUT">PUT</a></li>
     547               <li class="tocline1">7.7&nbsp;&nbsp;&nbsp;<a href="#DELETE">DELETE</a></li>
     548               <li class="tocline1">7.8&nbsp;&nbsp;&nbsp;<a href="#TRACE">TRACE</a></li>
     549               <li class="tocline1">7.9&nbsp;&nbsp;&nbsp;<a href="#CONNECT">CONNECT</a></li>
    630550            </ul>
    631551         </li>
    632          <li class="tocline0">13.&nbsp;&nbsp;&nbsp;<a href="#ack">Acknowledgments</a></li>
    633          <li class="tocline0">14.&nbsp;&nbsp;&nbsp;<a href="#rfc.references">References</a><ul class="toc">
    634                <li class="tocline1">14.1&nbsp;&nbsp;&nbsp;<a href="#rfc.references.1">Normative References</a></li>
    635                <li class="tocline1">14.2&nbsp;&nbsp;&nbsp;<a href="#rfc.references.2">Informative References</a></li>
     552         <li class="tocline0">8.&nbsp;&nbsp;&nbsp;<a href="#status.codes">Status Code Definitions</a><ul class="toc">
     553               <li class="tocline1">8.1&nbsp;&nbsp;&nbsp;<a href="#status.1xx">Informational 1xx</a><ul class="toc">
     554                     <li class="tocline1">8.1.1&nbsp;&nbsp;&nbsp;<a href="#status.100">100 Continue</a></li>
     555                     <li class="tocline1">8.1.2&nbsp;&nbsp;&nbsp;<a href="#status.101">101 Switching Protocols</a></li>
     556                  </ul>
     557               </li>
     558               <li class="tocline1">8.2&nbsp;&nbsp;&nbsp;<a href="#status.2xx">Successful 2xx</a><ul class="toc">
     559                     <li class="tocline1">8.2.1&nbsp;&nbsp;&nbsp;<a href="#status.200">200 OK</a></li>
     560                     <li class="tocline1">8.2.2&nbsp;&nbsp;&nbsp;<a href="#status.201">201 Created</a></li>
     561                     <li class="tocline1">8.2.3&nbsp;&nbsp;&nbsp;<a href="#status.202">202 Accepted</a></li>
     562                     <li class="tocline1">8.2.4&nbsp;&nbsp;&nbsp;<a href="#status.203">203 Non-Authoritative Information</a></li>
     563                     <li class="tocline1">8.2.5&nbsp;&nbsp;&nbsp;<a href="#status.204">204 No Content</a></li>
     564                     <li class="tocline1">8.2.6&nbsp;&nbsp;&nbsp;<a href="#status.205">205 Reset Content</a></li>
     565                     <li class="tocline1">8.2.7&nbsp;&nbsp;&nbsp;<a href="#status.206">206 Partial Content</a></li>
     566                  </ul>
     567               </li>
     568               <li class="tocline1">8.3&nbsp;&nbsp;&nbsp;<a href="#status.3xx">Redirection 3xx</a><ul class="toc">
     569                     <li class="tocline1">8.3.1&nbsp;&nbsp;&nbsp;<a href="#status.300">300 Multiple Choices</a></li>
     570                     <li class="tocline1">8.3.2&nbsp;&nbsp;&nbsp;<a href="#status.301">301 Moved Permanently</a></li>
     571                     <li class="tocline1">8.3.3&nbsp;&nbsp;&nbsp;<a href="#status.302">302 Found</a></li>
     572                     <li class="tocline1">8.3.4&nbsp;&nbsp;&nbsp;<a href="#status.303">303 See Other</a></li>
     573                     <li class="tocline1">8.3.5&nbsp;&nbsp;&nbsp;<a href="#status.304">304 Not Modified</a></li>
     574                     <li class="tocline1">8.3.6&nbsp;&nbsp;&nbsp;<a href="#status.305">305 Use Proxy</a></li>
     575                     <li class="tocline1">8.3.7&nbsp;&nbsp;&nbsp;<a href="#status.306">306 (Unused)</a></li>
     576                     <li class="tocline1">8.3.8&nbsp;&nbsp;&nbsp;<a href="#status.307">307 Temporary Redirect</a></li>
     577                  </ul>
     578               </li>
     579               <li class="tocline1">8.4&nbsp;&nbsp;&nbsp;<a href="#status.4xx">Client Error 4xx</a><ul class="toc">
     580                     <li class="tocline1">8.4.1&nbsp;&nbsp;&nbsp;<a href="#status.400">400 Bad Request</a></li>
     581                     <li class="tocline1">8.4.2&nbsp;&nbsp;&nbsp;<a href="#status.401">401 Unauthorized</a></li>
     582                     <li class="tocline1">8.4.3&nbsp;&nbsp;&nbsp;<a href="#status.402">402 Payment Required</a></li>
     583                     <li class="tocline1">8.4.4&nbsp;&nbsp;&nbsp;<a href="#status.403">403 Forbidden</a></li>
     584                     <li class="tocline1">8.4.5&nbsp;&nbsp;&nbsp;<a href="#status.404">404 Not Found</a></li>
     585                     <li class="tocline1">8.4.6&nbsp;&nbsp;&nbsp;<a href="#status.405">405 Method Not Allowed</a></li>
     586                     <li class="tocline1">8.4.7&nbsp;&nbsp;&nbsp;<a href="#status.406">406 Not Acceptable</a></li>
     587                     <li class="tocline1">8.4.8&nbsp;&nbsp;&nbsp;<a href="#status.407">407 Proxy Authentication Required</a></li>
     588                     <li class="tocline1">8.4.9&nbsp;&nbsp;&nbsp;<a href="#status.408">408 Request Timeout</a></li>
     589                     <li class="tocline1">8.4.10&nbsp;&nbsp;&nbsp;<a href="#status.409">409 Conflict</a></li>
     590                     <li class="tocline1">8.4.11&nbsp;&nbsp;&nbsp;<a href="#status.410">410 Gone</a></li>
     591                     <li class="tocline1">8.4.12&nbsp;&nbsp;&nbsp;<a href="#status.411">411 Length Required</a></li>
     592                     <li class="tocline1">8.4.13&nbsp;&nbsp;&nbsp;<a href="#status.412">412 Precondition Failed</a></li>
     593                     <li class="tocline1">8.4.14&nbsp;&nbsp;&nbsp;<a href="#status.413">413 Request Entity Too Large</a></li>
     594                     <li class="tocline1">8.4.15&nbsp;&nbsp;&nbsp;<a href="#status.414">414 Request-target Too Long</a></li>
     595                     <li class="tocline1">8.4.16&nbsp;&nbsp;&nbsp;<a href="#status.415">415 Unsupported Media Type</a></li>
     596                     <li class="tocline1">8.4.17&nbsp;&nbsp;&nbsp;<a href="#status.416">416 Requested Range Not Satisfiable</a></li>
     597                     <li class="tocline1">8.4.18&nbsp;&nbsp;&nbsp;<a href="#status.417">417 Expectation Failed</a></li>
     598                  </ul>
     599               </li>
     600               <li class="tocline1">8.5&nbsp;&nbsp;&nbsp;<a href="#status.5xx">Server Error 5xx</a><ul class="toc">
     601                     <li class="tocline1">8.5.1&nbsp;&nbsp;&nbsp;<a href="#status.500">500 Internal Server Error</a></li>
     602                     <li class="tocline1">8.5.2&nbsp;&nbsp;&nbsp;<a href="#status.501">501 Not Implemented</a></li>
     603                     <li class="tocline1">8.5.3&nbsp;&nbsp;&nbsp;<a href="#status.502">502 Bad Gateway</a></li>
     604                     <li class="tocline1">8.5.4&nbsp;&nbsp;&nbsp;<a href="#status.503">503 Service Unavailable</a></li>
     605                     <li class="tocline1">8.5.5&nbsp;&nbsp;&nbsp;<a href="#status.504">504 Gateway Timeout</a></li>
     606                     <li class="tocline1">8.5.6&nbsp;&nbsp;&nbsp;<a href="#status.505">505 HTTP Version Not Supported</a></li>
     607                  </ul>
     608               </li>
     609            </ul>
     610         </li>
     611         <li class="tocline0">9.&nbsp;&nbsp;&nbsp;<a href="#header.fields">Header Field Definitions</a><ul class="toc">
     612               <li class="tocline1">9.1&nbsp;&nbsp;&nbsp;<a href="#header.allow">Allow</a></li>
     613               <li class="tocline1">9.2&nbsp;&nbsp;&nbsp;<a href="#header.expect">Expect</a></li>
     614               <li class="tocline1">9.3&nbsp;&nbsp;&nbsp;<a href="#header.from">From</a></li>
     615               <li class="tocline1">9.4&nbsp;&nbsp;&nbsp;<a href="#header.location">Location</a></li>
     616               <li class="tocline1">9.5&nbsp;&nbsp;&nbsp;<a href="#header.max-forwards">Max-Forwards</a></li>
     617               <li class="tocline1">9.6&nbsp;&nbsp;&nbsp;<a href="#header.referer">Referer</a></li>
     618               <li class="tocline1">9.7&nbsp;&nbsp;&nbsp;<a href="#header.retry-after">Retry-After</a></li>
     619               <li class="tocline1">9.8&nbsp;&nbsp;&nbsp;<a href="#header.server">Server</a></li>
     620               <li class="tocline1">9.9&nbsp;&nbsp;&nbsp;<a href="#header.user-agent">User-Agent</a></li>
     621            </ul>
     622         </li>
     623         <li class="tocline0">10.&nbsp;&nbsp;&nbsp;<a href="#IANA.considerations">IANA Considerations</a><ul class="toc">
     624               <li class="tocline1">10.1&nbsp;&nbsp;&nbsp;<a href="#method.registration">Method Registry</a></li>
     625               <li class="tocline1">10.2&nbsp;&nbsp;&nbsp;<a href="#status.code.registration">Status Code Registry</a></li>
     626               <li class="tocline1">10.3&nbsp;&nbsp;&nbsp;<a href="#message.header.registration">Message Header Registration</a></li>
     627            </ul>
     628         </li>
     629         <li class="tocline0">11.&nbsp;&nbsp;&nbsp;<a href="#security.considerations">Security Considerations</a><ul class="toc">
     630               <li class="tocline1">11.1&nbsp;&nbsp;&nbsp;<a href="#security.sensitive">Transfer of Sensitive Information</a></li>
     631               <li class="tocline1">11.2&nbsp;&nbsp;&nbsp;<a href="#encoding.sensitive.information.in.uris">Encoding Sensitive Information in URIs</a></li>
     632               <li class="tocline1">11.3&nbsp;&nbsp;&nbsp;<a href="#location.spoofing">Location Headers and Spoofing</a></li>
     633            </ul>
     634         </li>
     635         <li class="tocline0">12.&nbsp;&nbsp;&nbsp;<a href="#ack">Acknowledgments</a></li>
     636         <li class="tocline0">13.&nbsp;&nbsp;&nbsp;<a href="#rfc.references">References</a><ul class="toc">
     637               <li class="tocline1">13.1&nbsp;&nbsp;&nbsp;<a href="#rfc.references.1">Normative References</a></li>
     638               <li class="tocline1">13.2&nbsp;&nbsp;&nbsp;<a href="#rfc.references.2">Informative References</a></li>
    636639            </ul>
    637640         </li>
     
    674677      <p id="rfc.section.1.1.p.2">An implementation is not compliant if it fails to satisfy one or more of the <em class="bcp14">MUST</em> or <em class="bcp14">REQUIRED</em> level requirements for the protocols it implements. An implementation that satisfies all the <em class="bcp14">MUST</em> or <em class="bcp14">REQUIRED</em> level and all the <em class="bcp14">SHOULD</em> level requirements for its protocols is said to be "unconditionally compliant"; one that satisfies all the <em class="bcp14">MUST</em> level requirements but not all the <em class="bcp14">SHOULD</em> level requirements for its protocols is said to be "conditionally compliant."
    675678      </p>
    676       <h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a>&nbsp;<a id="notation" href="#notation">Notational Conventions and Generic Grammar</a></h1>
    677       <p id="rfc.section.2.p.1">This specification uses the ABNF syntax defined in <a href="p1-messaging.html#notation.abnf" title="ABNF Extension: #rule">Section 1.2.1</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> and the core rules defined in <a href="p1-messaging.html#basic.rules" title="Basic Rules">Section 1.2.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>:
    678       </p>
    679       <div id="rfc.figure.u.1"></div><pre class="inline">  <a href="#notation" class="smpl">CR</a>            = &lt;CR, 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#basic.rules" title="Basic Rules">Section 1.2.2</a>&gt;
    680   <a href="#notation" class="smpl">DIGIT</a>         = &lt;DIGIT, 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#basic.rules" title="Basic Rules">Section 1.2.2</a>&gt;
    681   <a href="#notation" class="smpl">LF</a>            = &lt;LF, 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#basic.rules" title="Basic Rules">Section 1.2.2</a>&gt;
    682   <a href="#notation" class="smpl">VCHAR</a>         = &lt;VCHAR, 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#basic.rules" title="Basic Rules">Section 1.2.2</a>&gt;
    683   <a href="#notation" class="smpl">WSP</a>           = &lt;WSP, 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#basic.rules" title="Basic Rules">Section 1.2.2</a>&gt;
    684 </pre><div id="rfc.figure.u.2"></div><pre class="inline">  <a href="#notation" class="smpl">comment</a>       = &lt;comment, 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#basic.rules" title="Basic Rules">Section 1.2.2</a>&gt;
    685   <a href="#notation" class="smpl">quoted-string</a> = &lt;quoted-string, 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#basic.rules" title="Basic Rules">Section 1.2.2</a>&gt;
    686   <a href="#notation" class="smpl">token</a>         = &lt;token, 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#basic.rules" title="Basic Rules">Section 1.2.2</a>&gt;
    687   <a href="#notation" class="smpl">OWS</a>           = &lt;OWS, 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#basic.rules" title="Basic Rules">Section 1.2.2</a>&gt;
    688   <a href="#notation" class="smpl">RWS</a>           = &lt;RWS, defined in <a href="#Part1" id="rfc.xref.Part1.13"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#basic.rules" title="Basic Rules">Section 1.2.2</a>&gt;
    689   <a href="#notation" class="smpl">obs-text</a>      = &lt;obs-text, defined in <a href="#Part1" id="rfc.xref.Part1.14"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#basic.rules" title="Basic Rules">Section 1.2.2</a>&gt;
    690 </pre><div id="abnf.dependencies">
    691          <p id="rfc.section.2.p.4">                                                  The ABNF rules below are defined in other parts:</p>
    692       </div>
     679      <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>
     680      <p id="rfc.section.1.2.p.1">This specification uses the ABNF syntax 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>.
     681      </p>
     682      <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>
     683      <p id="rfc.section.1.2.1.p.1">The core rules below are defined in <a href="p1-messaging.html#basic.rules" title="Basic Rules">Section 1.2.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>:
     684      </p>
     685      <div id="rfc.figure.u.1"></div><pre class="inline">  <a href="#core.rules" class="smpl">CR</a>            = &lt;CR, 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#basic.rules" title="Basic Rules">Section 1.2.2</a>&gt;
     686  <a href="#core.rules" class="smpl">DIGIT</a>         = &lt;DIGIT, 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#basic.rules" title="Basic Rules">Section 1.2.2</a>&gt;
     687  <a href="#core.rules" class="smpl">LF</a>            = &lt;LF, 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#basic.rules" title="Basic Rules">Section 1.2.2</a>&gt;
     688  <a href="#core.rules" class="smpl">VCHAR</a>         = &lt;VCHAR, 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#basic.rules" title="Basic Rules">Section 1.2.2</a>&gt;
     689  <a href="#core.rules" class="smpl">WSP</a>           = &lt;WSP, 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#basic.rules" title="Basic Rules">Section 1.2.2</a>&gt;
     690</pre><div id="rfc.figure.u.2"></div><pre class="inline">  <a href="#core.rules" class="smpl">comment</a>       = &lt;comment, 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#basic.rules" title="Basic Rules">Section 1.2.2</a>&gt;
     691  <a href="#core.rules" class="smpl">quoted-string</a> = &lt;quoted-string, 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#basic.rules" title="Basic Rules">Section 1.2.2</a>&gt;
     692  <a href="#core.rules" class="smpl">token</a>         = &lt;token, 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#basic.rules" title="Basic Rules">Section 1.2.2</a>&gt;
     693  <a href="#core.rules" class="smpl">OWS</a>           = &lt;OWS, 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#basic.rules" title="Basic Rules">Section 1.2.2</a>&gt;
     694  <a href="#core.rules" class="smpl">RWS</a>           = &lt;RWS, defined in <a href="#Part1" id="rfc.xref.Part1.13"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#basic.rules" title="Basic Rules">Section 1.2.2</a>&gt;
     695  <a href="#core.rules" class="smpl">obs-text</a>      = &lt;obs-text, defined in <a href="#Part1" id="rfc.xref.Part1.14"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#basic.rules" title="Basic Rules">Section 1.2.2</a>&gt;
     696</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>
     697      <p id="rfc.section.1.2.2.p.1">The ABNF rules below are defined in other parts:</p>
    693698      <div id="rfc.figure.u.3"></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.15"><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.1</a>&gt;
    694699  <a href="#abnf.dependencies" class="smpl">fragment</a>      = &lt;fragment, defined in <a href="#Part1" id="rfc.xref.Part1.16"><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.1</a>&gt;
     
    698703  <a href="#abnf.dependencies" class="smpl">product</a>       = &lt;product, defined in <a href="#Part1" id="rfc.xref.Part1.20"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#product.tokens" title="Product Tokens">Section 3.4</a>&gt;
    699704  <a href="#abnf.dependencies" class="smpl">TE</a>            = &lt;TE, defined in <a href="#Part1" id="rfc.xref.Part1.21"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#header.upgrade" title="Upgrade">Section 8.8</a>&gt;
    700 </pre><div id="rfc.figure.u.4"></div><pre class="inline">  <a href="#abnf.dependencies" class="smpl">Accept</a>        = &lt;Accept, defined in <a href="#Part3" id="rfc.xref.Part3.1"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="p3-payload.html#header.accept" title="Accept">Section 6.1</a>&gt;
     705</pre><div id="rfc.figure.u.4"></div><pre class="inline">  <a href="#abnf.dependencies" class="smpl">Accept</a>        = &lt;Accept, defined in <a href="#Part3" id="rfc.xref.Part3.1"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="p3-payload.html#header.accept" title="Accept">Section 5.1</a>&gt;
    701706  <a href="#abnf.dependencies" class="smpl">Accept-Charset</a> =
    702              &lt;Accept-Charset, defined in <a href="#Part3" id="rfc.xref.Part3.2"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="p3-payload.html#header.accept-charset" title="Accept-Charset">Section 6.2</a>&gt;
     707             &lt;Accept-Charset, defined in <a href="#Part3" id="rfc.xref.Part3.2"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="p3-payload.html#header.accept-charset" title="Accept-Charset">Section 5.2</a>&gt;
    703708  <a href="#abnf.dependencies" class="smpl">Accept-Encoding</a> =
    704              &lt;Accept-Encoding, defined in <a href="#Part3" id="rfc.xref.Part3.3"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="p3-payload.html#header.accept-encoding" title="Accept-Encoding">Section 6.3</a>&gt;
     709             &lt;Accept-Encoding, defined in <a href="#Part3" id="rfc.xref.Part3.3"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="p3-payload.html#header.accept-encoding" title="Accept-Encoding">Section 5.3</a>&gt;
    705710  <a href="#abnf.dependencies" class="smpl">Accept-Language</a> =
    706              &lt;Accept-Language, defined in <a href="#Part3" id="rfc.xref.Part3.4"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="p3-payload.html#header.accept-language" title="Accept-Language">Section 6.4</a>&gt;
    707 </pre><div id="rfc.figure.u.5"></div><pre class="inline">  <a href="#abnf.dependencies" class="smpl">ETag</a>          = &lt;ETag, defined in <a href="#Part4" id="rfc.xref.Part4.1"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>, <a href="p4-conditional.html#header.etag" title="ETag">Section 7.1</a>&gt;
    708   <a href="#abnf.dependencies" class="smpl">If-Match</a>      = &lt;If-Match, defined in <a href="#Part4" id="rfc.xref.Part4.2"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>, <a href="p4-conditional.html#header.if-match" title="If-Match">Section 7.2</a>&gt;
     711             &lt;Accept-Language, defined in <a href="#Part3" id="rfc.xref.Part3.4"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="p3-payload.html#header.accept-language" title="Accept-Language">Section 5.4</a>&gt;
     712</pre><div id="rfc.figure.u.5"></div><pre class="inline">  <a href="#abnf.dependencies" class="smpl">ETag</a>          = &lt;ETag, defined in <a href="#Part4" id="rfc.xref.Part4.1"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>, <a href="p4-conditional.html#header.etag" title="ETag">Section 6.1</a>&gt;
     713  <a href="#abnf.dependencies" class="smpl">If-Match</a>      = &lt;If-Match, defined in <a href="#Part4" id="rfc.xref.Part4.2"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>, <a href="p4-conditional.html#header.if-match" title="If-Match">Section 6.2</a>&gt;
    709714  <a href="#abnf.dependencies" class="smpl">If-Modified-Since</a> =
    710              &lt;If-Modified-Since, defined in <a href="#Part4" id="rfc.xref.Part4.3"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>, <a href="p4-conditional.html#header.if-modified-since" title="If-Modified-Since">Section 7.3</a>&gt;
    711   <a href="#abnf.dependencies" class="smpl">If-None-Match</a> = &lt;If-None-Match, defined in <a href="#Part4" id="rfc.xref.Part4.4"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>, <a href="p4-conditional.html#header.if-none-match" title="If-None-Match">Section 7.4</a>&gt;
     715             &lt;If-Modified-Since, defined in <a href="#Part4" id="rfc.xref.Part4.3"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>, <a href="p4-conditional.html#header.if-modified-since" title="If-Modified-Since">Section 6.3</a>&gt;
     716  <a href="#abnf.dependencies" class="smpl">If-None-Match</a> = &lt;If-None-Match, defined in <a href="#Part4" id="rfc.xref.Part4.4"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>, <a href="p4-conditional.html#header.if-none-match" title="If-None-Match">Section 6.4</a>&gt;
    712717  <a href="#abnf.dependencies" class="smpl">If-Unmodified-Since</a> =
    713              &lt;If-Unmodified-Since, defined in <a href="#Part4" id="rfc.xref.Part4.5"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>, <a href="p4-conditional.html#header.if-unmodified-since" title="If-Unmodified-Since">Section 7.5</a>&gt;
    714 </pre><div id="rfc.figure.u.6"></div><pre class="inline">  <a href="#abnf.dependencies" class="smpl">Accept-Ranges</a> = &lt;Accept-Ranges, defined in <a href="#Part5" id="rfc.xref.Part5.1"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>, <a href="p5-range.html#header.accept-ranges" title="Accept-Ranges">Section 6.1</a>&gt;
    715   <a href="#abnf.dependencies" class="smpl">If-Range</a>      = &lt;If-Range, defined in <a href="#Part5" id="rfc.xref.Part5.2"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>, <a href="p5-range.html#header.if-range" title="If-Range">Section 6.3</a>&gt;
    716   <a href="#abnf.dependencies" class="smpl">Range</a>         = &lt;Range, defined in <a href="#Part5" id="rfc.xref.Part5.3"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>, <a href="p5-range.html#header.range" title="Range">Section 6.4</a>&gt;
    717 </pre><div id="rfc.figure.u.7"></div><pre class="inline">  <a href="#abnf.dependencies" class="smpl">Age</a>           = &lt;Age, defined in <a href="#Part6" id="rfc.xref.Part6.1"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>, <a href="p6-cache.html#header.age" title="Age">Section 16.1</a>&gt;
    718   <a href="#abnf.dependencies" class="smpl">Vary</a>          = &lt;Vary, defined in <a href="#Part6" id="rfc.xref.Part6.2"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>, <a href="p6-cache.html#header.vary" title="Vary">Section 16.5</a>&gt;
    719 </pre><div id="rfc.figure.u.8"></div><pre class="inline">  <a href="#abnf.dependencies" class="smpl">Authorization</a> = &lt;Authorization, defined in <a href="#Part7" id="rfc.xref.Part7.1"><cite title="HTTP/1.1, part 7: Authentication">[Part7]</cite></a>, <a href="p7-auth.html#header.authorization" title="Authorization">Section 4.1</a>&gt;
     718             &lt;If-Unmodified-Since, defined in <a href="#Part4" id="rfc.xref.Part4.5"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>, <a href="p4-conditional.html#header.if-unmodified-since" title="If-Unmodified-Since">Section 6.5</a>&gt;
     719</pre><div id="rfc.figure.u.6"></div><pre class="inline">  <a href="#abnf.dependencies" class="smpl">Accept-Ranges</a> = &lt;Accept-Ranges, defined in <a href="#Part5" id="rfc.xref.Part5.1"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>, <a href="p5-range.html#header.accept-ranges" title="Accept-Ranges">Section 5.1</a>&gt;
     720  <a href="#abnf.dependencies" class="smpl">If-Range</a>      = &lt;If-Range, defined in <a href="#Part5" id="rfc.xref.Part5.2"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>, <a href="p5-range.html#header.if-range" title="If-Range">Section 5.3</a>&gt;
     721  <a href="#abnf.dependencies" class="smpl">Range</a>         = &lt;Range, defined in <a href="#Part5" id="rfc.xref.Part5.3"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>, <a href="p5-range.html#header.range" title="Range">Section 5.4</a>&gt;
     722</pre><div id="rfc.figure.u.7"></div><pre class="inline">  <a href="#abnf.dependencies" class="smpl">Age</a>           = &lt;Age, defined in <a href="#Part6" id="rfc.xref.Part6.1"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>, <a href="p6-cache.html#header.age" title="Age">Section 15.1</a>&gt;
     723  <a href="#abnf.dependencies" class="smpl">Vary</a>          = &lt;Vary, defined in <a href="#Part6" id="rfc.xref.Part6.2"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>, <a href="p6-cache.html#header.vary" title="Vary">Section 15.5</a>&gt;
     724</pre><div id="rfc.figure.u.8"></div><pre class="inline">  <a href="#abnf.dependencies" class="smpl">Authorization</a> = &lt;Authorization, defined in <a href="#Part7" id="rfc.xref.Part7.1"><cite title="HTTP/1.1, part 7: Authentication">[Part7]</cite></a>, <a href="p7-auth.html#header.authorization" title="Authorization">Section 3.1</a>&gt;
    720725  <a href="#abnf.dependencies" class="smpl">Proxy-Authenticate</a> =
    721              &lt;Proxy-Authenticate, defined in <a href="#Part7" id="rfc.xref.Part7.2"><cite title="HTTP/1.1, part 7: Authentication">[Part7]</cite></a>, <a href="p7-auth.html#header.proxy-authenticate" title="Proxy-Authenticate">Section 4.2</a>&gt;
     726             &lt;Proxy-Authenticate, defined in <a href="#Part7" id="rfc.xref.Part7.2"><cite title="HTTP/1.1, part 7: Authentication">[Part7]</cite></a>, <a href="p7-auth.html#header.proxy-authenticate" title="Proxy-Authenticate">Section 3.2</a>&gt;
    722727  <a href="#abnf.dependencies" class="smpl">Proxy-Authorization</a> =
    723              &lt;Proxy-Authorization, defined in <a href="#Part7" id="rfc.xref.Part7.3"><cite title="HTTP/1.1, part 7: Authentication">[Part7]</cite></a>, <a href="p7-auth.html#header.proxy-authorization" title="Proxy-Authorization">Section 4.3</a>&gt;
     728             &lt;Proxy-Authorization, defined in <a href="#Part7" id="rfc.xref.Part7.3"><cite title="HTTP/1.1, part 7: Authentication">[Part7]</cite></a>, <a href="p7-auth.html#header.proxy-authorization" title="Proxy-Authorization">Section 3.3</a>&gt;
    724729  <a href="#abnf.dependencies" class="smpl">WWW-Authenticate</a> =
    725              &lt;WWW-Authenticate, defined in <a href="#Part7" id="rfc.xref.Part7.4"><cite title="HTTP/1.1, part 7: Authentication">[Part7]</cite></a>, <a href="p7-auth.html#header.www-authenticate" title="WWW-Authenticate">Section 4.4</a>&gt;
    726 </pre><h1 id="rfc.section.3"><a href="#rfc.section.3">3.</a>&nbsp;<a id="method" href="#method">Method</a></h1>
    727       <p id="rfc.section.3.p.1">The Method token indicates the method to be performed on the resource identified by the request-target. The method is case-sensitive.</p>
    728       <div id="rfc.figure.u.9"></div><pre class="inline"><span id="rfc.iref.g.1"></span><span id="rfc.iref.g.2"></span>  <a href="#method" class="smpl">Method</a>         = %x4F.50.54.49.4F.4E.53   ; "OPTIONS", <a href="#OPTIONS" id="rfc.xref.OPTIONS.1" title="OPTIONS">Section&nbsp;8.2</a>
    729                  / %x47.45.54               ; "GET", <a href="#GET" id="rfc.xref.GET.1" title="GET">Section&nbsp;8.3</a>
    730                  / %x48.45.41.44            ; "HEAD", <a href="#HEAD" id="rfc.xref.HEAD.1" title="HEAD">Section&nbsp;8.4</a>
    731                  / %x50.4F.53.54            ; "POST", <a href="#POST" id="rfc.xref.POST.1" title="POST">Section&nbsp;8.5</a>
    732                  / %x50.55.54               ; "PUT", <a href="#PUT" id="rfc.xref.PUT.1" title="PUT">Section&nbsp;8.6</a>
    733                  / %x44.45.4C.45.54.45      ; "DELETE", <a href="#DELETE" id="rfc.xref.DELETE.1" title="DELETE">Section&nbsp;8.7</a>
    734                  / %x54.52.41.43.45         ; "TRACE", <a href="#TRACE" id="rfc.xref.TRACE.1" title="TRACE">Section&nbsp;8.8</a>
    735                  / %x43.4F.4E.4E.45.43.54   ; "CONNECT", <a href="#CONNECT" id="rfc.xref.CONNECT.1" title="CONNECT">Section&nbsp;8.9</a>
     730             &lt;WWW-Authenticate, defined in <a href="#Part7" id="rfc.xref.Part7.4"><cite title="HTTP/1.1, part 7: Authentication">[Part7]</cite></a>, <a href="p7-auth.html#header.www-authenticate" title="WWW-Authenticate">Section 3.4</a>&gt;
     731</pre><h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a>&nbsp;<a id="method" href="#method">Method</a></h1>
     732      <p id="rfc.section.2.p.1">The Method token indicates the method to be performed on the resource identified by the request-target. The method is case-sensitive.</p>
     733      <div id="rfc.figure.u.9"></div><pre class="inline"><span id="rfc.iref.g.1"></span><span id="rfc.iref.g.2"></span>  <a href="#method" class="smpl">Method</a>         = %x4F.50.54.49.4F.4E.53   ; "OPTIONS", <a href="#OPTIONS" id="rfc.xref.OPTIONS.1" title="OPTIONS">Section&nbsp;7.2</a>
     734                 / %x47.45.54               ; "GET", <a href="#GET" id="rfc.xref.GET.1" title="GET">Section&nbsp;7.3</a>
     735                 / %x48.45.41.44            ; "HEAD", <a href="#HEAD" id="rfc.xref.HEAD.1" title="HEAD">Section&nbsp;7.4</a>
     736                 / %x50.4F.53.54            ; "POST", <a href="#POST" id="rfc.xref.POST.1" title="POST">Section&nbsp;7.5</a>
     737                 / %x50.55.54               ; "PUT", <a href="#PUT" id="rfc.xref.PUT.1" title="PUT">Section&nbsp;7.6</a>
     738                 / %x44.45.4C.45.54.45      ; "DELETE", <a href="#DELETE" id="rfc.xref.DELETE.1" title="DELETE">Section&nbsp;7.7</a>
     739                 / %x54.52.41.43.45         ; "TRACE", <a href="#TRACE" id="rfc.xref.TRACE.1" title="TRACE">Section&nbsp;7.8</a>
     740                 / %x43.4F.4E.4E.45.43.54   ; "CONNECT", <a href="#CONNECT" id="rfc.xref.CONNECT.1" title="CONNECT">Section&nbsp;7.9</a>
    736741                 / <a href="#method" class="smpl">extension-method</a>
    737   <a href="#method" class="smpl">extension-method</a> = <a href="#notation" class="smpl">token</a>
    738 </pre><p id="rfc.section.3.p.3">The list of methods allowed by a resource can be specified in an Allow header field (<a href="#header.allow" id="rfc.xref.header.allow.1" title="Allow">Section&nbsp;10.1</a>). The return code of the response always notifies the client whether a method is currently allowed on a resource, since the
     742  <a href="#method" class="smpl">extension-method</a> = <a href="#core.rules" class="smpl">token</a>
     743</pre><p id="rfc.section.2.p.3">The list of methods allowed by a resource can be specified in an Allow header field (<a href="#header.allow" id="rfc.xref.header.allow.1" title="Allow">Section&nbsp;9.1</a>). The return code of the response always notifies the client whether a method is currently allowed on a resource, since the
    739744         set of allowed methods can change dynamically. An origin server <em class="bcp14">SHOULD</em> return the status code 405 (Method Not Allowed) if the method is known by the origin server but not allowed for the requested
    740745         resource, and 501 (Not Implemented) if the method is unrecognized or not implemented by the origin server. The methods GET
    741          and HEAD <em class="bcp14">MUST</em> be supported by all general-purpose servers. All other methods are <em class="bcp14">OPTIONAL</em>; however, if the above methods are implemented, they <em class="bcp14">MUST</em> be implemented with the same semantics as those specified in <a href="#method.definitions" title="Method Definitions">Section&nbsp;8</a>.
    742       </p>
    743       <h2 id="rfc.section.3.1"><a href="#rfc.section.3.1">3.1</a>&nbsp;<a id="method.registry" href="#method.registry">Method Registry</a></h2>
    744       <p id="rfc.section.3.1.p.1">The HTTP Method Registry defines the name space for the Method token in the Request line of an HTTP request.</p>
    745       <p id="rfc.section.3.1.p.2">Registrations <em class="bcp14">MUST</em> include the following fields:
     746         and HEAD <em class="bcp14">MUST</em> be supported by all general-purpose servers. All other methods are <em class="bcp14">OPTIONAL</em>; however, if the above methods are implemented, they <em class="bcp14">MUST</em> be implemented with the same semantics as those specified in <a href="#method.definitions" title="Method Definitions">Section&nbsp;7</a>.
     747      </p>
     748      <h2 id="rfc.section.2.1"><a href="#rfc.section.2.1">2.1</a>&nbsp;<a id="method.registry" href="#method.registry">Method Registry</a></h2>
     749      <p id="rfc.section.2.1.p.1">The HTTP Method Registry defines the name space for the Method token in the Request line of an HTTP request.</p>
     750      <p id="rfc.section.2.1.p.2">Registrations <em class="bcp14">MUST</em> include the following fields:
    746751      </p>
    747752      <ul>
    748          <li>Method Name (see <a href="#method" title="Method">Section&nbsp;3</a>)
    749          </li>
    750          <li>Safe ("yes" or "no", see <a href="#safe.methods" title="Safe Methods">Section&nbsp;8.1.1</a>)
     753         <li>Method Name (see <a href="#method" title="Method">Section&nbsp;2</a>)
     754         </li>
     755         <li>Safe ("yes" or "no", see <a href="#safe.methods" title="Safe Methods">Section&nbsp;7.1.1</a>)
    751756         </li>
    752757         <li>Pointer to specification text</li>
    753758      </ul>
    754       <p id="rfc.section.3.1.p.3">Values to be added to this name space are subject to IETF review (<a href="#RFC5226" id="rfc.xref.RFC5226.1"><cite title="Guidelines for Writing an IANA Considerations Section in RFCs">[RFC5226]</cite></a>, <a href="http://tools.ietf.org/html/rfc5226#section-4.1">Section 4.1</a>). Any document registering new method names should be traceable through statuses of either 'Obsoletes' or 'Updates' to this
     759      <p id="rfc.section.2.1.p.3">Values to be added to this name space are subject to IETF review (<a href="#RFC5226" id="rfc.xref.RFC5226.1"><cite title="Guidelines for Writing an IANA Considerations Section in RFCs">[RFC5226]</cite></a>, <a href="http://tools.ietf.org/html/rfc5226#section-4.1">Section 4.1</a>). Any document registering new method names should be traceable through statuses of either 'Obsoletes' or 'Updates' to this
    755760         document.
    756761      </p>
    757       <p id="rfc.section.3.1.p.4">The registry itself is maintained at &lt;<a href="http://www.iana.org/assignments/http-methods">http://www.iana.org/assignments/http-methods</a>&gt;.
    758       </p>
    759       <h1 id="rfc.section.4"><a href="#rfc.section.4">4.</a>&nbsp;<a id="request.header.fields" href="#request.header.fields">Request Header Fields</a></h1>
    760       <p id="rfc.section.4.p.1">The request-header fields allow the client to pass additional information about the request, and about the client itself,
     762      <p id="rfc.section.2.1.p.4">The registry itself is maintained at &lt;<a href="http://www.iana.org/assignments/http-methods">http://www.iana.org/assignments/http-methods</a>&gt;.
     763      </p>
     764      <h1 id="rfc.section.3"><a href="#rfc.section.3">3.</a>&nbsp;<a id="request.header.fields" href="#request.header.fields">Request Header Fields</a></h1>
     765      <p id="rfc.section.3.p.1">The request-header fields allow the client to pass additional information about the request, and about the client itself,
    761766         to the server. These fields act as request modifiers, with semantics equivalent to the parameters on a programming language
    762767         method invocation.
    763768      </p>
    764       <div id="rfc.figure.u.10"></div><pre class="inline"><span id="rfc.iref.g.3"></span>  <a href="#request.header.fields" class="smpl">request-header</a> = <a href="#abnf.dependencies" class="smpl">Accept</a>                   ; <a href="#Part3" id="rfc.xref.Part3.5"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="p3-payload.html#header.accept" title="Accept">Section 6.1</a>
    765                  / <a href="#abnf.dependencies" class="smpl">Accept-Charset</a>           ; <a href="#Part3" id="rfc.xref.Part3.6"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="p3-payload.html#header.accept-charset" title="Accept-Charset">Section 6.2</a>
    766                  / <a href="#abnf.dependencies" class="smpl">Accept-Encoding</a>          ; <a href="#Part3" id="rfc.xref.Part3.7"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="p3-payload.html#header.accept-encoding" title="Accept-Encoding">Section 6.3</a>
    767                  / <a href="#abnf.dependencies" class="smpl">Accept-Language</a>          ; <a href="#Part3" id="rfc.xref.Part3.8"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="p3-payload.html#header.accept-language" title="Accept-Language">Section 6.4</a>
    768                  / <a href="#abnf.dependencies" class="smpl">Authorization</a>            ; <a href="#Part7" id="rfc.xref.Part7.5"><cite title="HTTP/1.1, part 7: Authentication">[Part7]</cite></a>, <a href="p7-auth.html#header.authorization" title="Authorization">Section 4.1</a>
    769                  / <a href="#header.expect" class="smpl">Expect</a>                   ; <a href="#header.expect" id="rfc.xref.header.expect.1" title="Expect">Section&nbsp;10.2</a>
    770                  / <a href="#header.from" class="smpl">From</a>                     ; <a href="#header.from" id="rfc.xref.header.from.1" title="From">Section&nbsp;10.3</a>
     769      <div id="rfc.figure.u.10"></div><pre class="inline"><span id="rfc.iref.g.3"></span>  <a href="#request.header.fields" class="smpl">request-header</a> = <a href="#abnf.dependencies" class="smpl">Accept</a>                   ; <a href="#Part3" id="rfc.xref.Part3.5"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="p3-payload.html#header.accept" title="Accept">Section 5.1</a>
     770                 / <a href="#abnf.dependencies" class="smpl">Accept-Charset</a>           ; <a href="#Part3" id="rfc.xref.Part3.6"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="p3-payload.html#header.accept-charset" title="Accept-Charset">Section 5.2</a>
     771                 / <a href="#abnf.dependencies" class="smpl">Accept-Encoding</a>          ; <a href="#Part3" id="rfc.xref.Part3.7"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="p3-payload.html#header.accept-encoding" title="Accept-Encoding">Section 5.3</a>
     772                 / <a href="#abnf.dependencies" class="smpl">Accept-Language</a>          ; <a href="#Part3" id="rfc.xref.Part3.8"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="p3-payload.html#header.accept-language" title="Accept-Language">Section 5.4</a>
     773                 / <a href="#abnf.dependencies" class="smpl">Authorization</a>            ; <a href="#Part7" id="rfc.xref.Part7.5"><cite title="HTTP/1.1, part 7: Authentication">[Part7]</cite></a>, <a href="p7-auth.html#header.authorization" title="Authorization">Section 3.1</a>
     774                 / <a href="#header.expect" class="smpl">Expect</a>                   ; <a href="#header.expect" id="rfc.xref.header.expect.1" title="Expect">Section&nbsp;9.2</a>
     775                 / <a href="#header.from" class="smpl">From</a>                     ; <a href="#header.from" id="rfc.xref.header.from.1" title="From">Section&nbsp;9.3</a>
    771776                 / <a href="#abnf.dependencies" class="smpl">Host</a>                     ; <a href="#Part1" id="rfc.xref.Part1.22"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#header.host" title="Host">Section 8.4</a>
    772                  / <a href="#abnf.dependencies" class="smpl">If-Match</a>                 ; <a href="#Part4" id="rfc.xref.Part4.6"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>, <a href="p4-conditional.html#header.if-match" title="If-Match">Section 7.2</a>
    773                  / <a href="#abnf.dependencies" class="smpl">If-Modified-Since</a>        ; <a href="#Part4" id="rfc.xref.Part4.7"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>, <a href="p4-conditional.html#header.if-modified-since" title="If-Modified-Since">Section 7.3</a>
    774                  / <a href="#abnf.dependencies" class="smpl">If-None-Match</a>            ; <a href="#Part4" id="rfc.xref.Part4.8"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>, <a href="p4-conditional.html#header.if-none-match" title="If-None-Match">Section 7.4</a>
    775                  / <a href="#abnf.dependencies" class="smpl">If-Range</a>                 ; <a href="#Part5" id="rfc.xref.Part5.4"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>, <a href="p5-range.html#header.if-range" title="If-Range">Section 6.3</a>
    776                  / <a href="#abnf.dependencies" class="smpl">If-Unmodified-Since</a>      ; <a href="#Part4" id="rfc.xref.Part4.9"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>, <a href="p4-conditional.html#header.if-unmodified-since" title="If-Unmodified-Since">Section 7.5</a>
    777                  / <a href="#header.max-forwards" class="smpl">Max-Forwards</a>             ; <a href="#header.max-forwards" id="rfc.xref.header.max-forwards.1" title="Max-Forwards">Section&nbsp;10.5</a>
    778                  / <a href="#abnf.dependencies" class="smpl">Proxy-Authorization</a>      ; <a href="#Part7" id="rfc.xref.Part7.6"><cite title="HTTP/1.1, part 7: Authentication">[Part7]</cite></a>, <a href="p7-auth.html#header.proxy-authorization" title="Proxy-Authorization">Section 4.3</a>
    779                  / <a href="#abnf.dependencies" class="smpl">Range</a>                    ; <a href="#Part5" id="rfc.xref.Part5.5"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>, <a href="p5-range.html#header.range" title="Range">Section 6.4</a>
    780                  / <a href="#header.referer" class="smpl">Referer</a>                  ; <a href="#header.referer" id="rfc.xref.header.referer.1" title="Referer">Section&nbsp;10.6</a>
     777                 / <a href="#abnf.dependencies" class="smpl">If-Match</a>                 ; <a href="#Part4" id="rfc.xref.Part4.6"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>, <a href="p4-conditional.html#header.if-match" title="If-Match">Section 6.2</a>
     778                 / <a href="#abnf.dependencies" class="smpl">If-Modified-Since</a>        ; <a href="#Part4" id="rfc.xref.Part4.7"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>, <a href="p4-conditional.html#header.if-modified-since" title="If-Modified-Since">Section 6.3</a>
     779                 / <a href="#abnf.dependencies" class="smpl">If-None-Match</a>            ; <a href="#Part4" id="rfc.xref.Part4.8"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>, <a href="p4-conditional.html#header.if-none-match" title="If-None-Match">Section 6.4</a>
     780                 / <a href="#abnf.dependencies" class="smpl">If-Range</a>                 ; <a href="#Part5" id="rfc.xref.Part5.4"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>, <a href="p5-range.html#header.if-range" title="If-Range">Section 5.3</a>
     781                 / <a href="#abnf.dependencies" class="smpl">If-Unmodified-Since</a>      ; <a href="#Part4" id="rfc.xref.Part4.9"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>, <a href="p4-conditional.html#header.if-unmodified-since" title="If-Unmodified-Since">Section 6.5</a>
     782                 / <a href="#header.max-forwards" class="smpl">Max-Forwards</a>             ; <a href="#header.max-forwards" id="rfc.xref.header.max-forwards.1" title="Max-Forwards">Section&nbsp;9.5</a>
     783                 / <a href="#abnf.dependencies" class="smpl">Proxy-Authorization</a>      ; <a href="#Part7" id="rfc.xref.Part7.6"><cite title="HTTP/1.1, part 7: Authentication">[Part7]</cite></a>, <a href="p7-auth.html#header.proxy-authorization" title="Proxy-Authorization">Section 3.3</a>
     784                 / <a href="#abnf.dependencies" class="smpl">Range</a>                    ; <a href="#Part5" id="rfc.xref.Part5.5"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>, <a href="p5-range.html#header.range" title="Range">Section 5.4</a>
     785                 / <a href="#header.referer" class="smpl">Referer</a>                  ; <a href="#header.referer" id="rfc.xref.header.referer.1" title="Referer">Section&nbsp;9.6</a>
    781786                 / <a href="#abnf.dependencies" class="smpl">TE</a>                       ; <a href="#Part1" id="rfc.xref.Part1.23"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#header.upgrade" title="Upgrade">Section 8.8</a>
    782                  / <a href="#header.user-agent" class="smpl">User-Agent</a>               ; <a href="#header.user-agent" id="rfc.xref.header.user-agent.1" title="User-Agent">Section&nbsp;10.9</a>
    783 </pre><p id="rfc.section.4.p.3">Request-header field names can be extended reliably only in combination with a change in the protocol version. However, new
     787                 / <a href="#header.user-agent" class="smpl">User-Agent</a>               ; <a href="#header.user-agent" id="rfc.xref.header.user-agent.1" title="User-Agent">Section&nbsp;9.9</a>
     788</pre><p id="rfc.section.3.p.3">Request-header field names can be extended reliably only in combination with a change in the protocol version. However, new
    784789         or experimental header fields <em class="bcp14">MAY</em> be given the semantics of request-header fields if all parties in the communication recognize them to be request-header fields.
    785790         Unrecognized header fields are treated as entity-header fields.
    786791      </p>
    787       <h1 id="rfc.section.5"><a href="#rfc.section.5">5.</a>&nbsp;<a id="status.code.and.reason.phrase" href="#status.code.and.reason.phrase">Status Code and Reason Phrase</a></h1>
    788       <p id="rfc.section.5.p.1">The Status-Code element is a 3-digit integer result code of the attempt to understand and satisfy the request. The status
    789          codes listed below are defined in <a href="#status.codes" title="Status Code Definitions">Section&nbsp;9</a>. The Reason-Phrase is intended to give a short textual description of the Status-Code. The Status-Code is intended for use
     792      <h1 id="rfc.section.4"><a href="#rfc.section.4">4.</a>&nbsp;<a id="status.code.and.reason.phrase" href="#status.code.and.reason.phrase">Status Code and Reason Phrase</a></h1>
     793      <p id="rfc.section.4.p.1">The Status-Code element is a 3-digit integer result code of the attempt to understand and satisfy the request. The status
     794         codes listed below are defined in <a href="#status.codes" title="Status Code Definitions">Section&nbsp;8</a>. The Reason-Phrase is intended to give a short textual description of the Status-Code. The Status-Code is intended for use
    790795         by automata and the Reason-Phrase is intended for the human user. The client is not required to examine or display the Reason-Phrase.
    791796      </p>
    792       <p id="rfc.section.5.p.2">The individual values of the numeric status codes defined for HTTP/1.1, and an example set of corresponding Reason-Phrase's,
     797      <p id="rfc.section.4.p.2">The individual values of the numeric status codes defined for HTTP/1.1, and an example set of corresponding Reason-Phrase's,
    793798         are presented below. The reason phrases listed here are only recommendations -- they <em class="bcp14">MAY</em> be replaced by local equivalents without affecting the protocol.
    794799      </p>
    795800      <div id="rfc.figure.u.11"></div><pre class="inline"><span id="rfc.iref.g.4"></span><span id="rfc.iref.g.5"></span><span id="rfc.iref.g.6"></span>  <a href="#status.code.and.reason.phrase" class="smpl">Status-Code</a>    =
    796          "100"  ; <a href="#status.100" id="rfc.xref.status.100.1" title="100 Continue">Section&nbsp;9.1.1</a>: Continue
    797        / "101"  ; <a href="#status.101" id="rfc.xref.status.101.1" title="101 Switching Protocols">Section&nbsp;9.1.2</a>: Switching Protocols
    798        / "200"  ; <a href="#status.200" id="rfc.xref.status.200.1" title="200 OK">Section&nbsp;9.2.1</a>: OK
    799        / "201"  ; <a href="#status.201" id="rfc.xref.status.201.1" title="201 Created">Section&nbsp;9.2.2</a>: Created
    800        / "202"  ; <a href="#status.202" id="rfc.xref.status.202.1" title="202 Accepted">Section&nbsp;9.2.3</a>: Accepted
    801        / "203"  ; <a href="#status.203" id="rfc.xref.status.203.1" title="203 Non-Authoritative Information">Section&nbsp;9.2.4</a>: Non-Authoritative Information
    802        / "204"  ; <a href="#status.204" id="rfc.xref.status.204.1" title="204 No Content">Section&nbsp;9.2.5</a>: No Content
    803        / "205"  ; <a href="#status.205" id="rfc.xref.status.205.1" title="205 Reset Content">Section&nbsp;9.2.6</a>: Reset Content
    804        / "206"  ; <a href="#status.206" id="rfc.xref.status.206.1" title="206 Partial Content">Section&nbsp;9.2.7</a>: Partial Content
    805        / "300"  ; <a href="#status.300" id="rfc.xref.status.300.1" title="300 Multiple Choices">Section&nbsp;9.3.1</a>: Multiple Choices
    806        / "301"  ; <a href="#status.301" id="rfc.xref.status.301.1" title="301 Moved Permanently">Section&nbsp;9.3.2</a>: Moved Permanently
    807        / "302"  ; <a href="#status.302" id="rfc.xref.status.302.1" title="302 Found">Section&nbsp;9.3.3</a>: Found
    808        / "303"  ; <a href="#status.303" id="rfc.xref.status.303.1" title="303 See Other">Section&nbsp;9.3.4</a>: See Other
    809        / "304"  ; <a href="#status.304" id="rfc.xref.status.304.1" title="304 Not Modified">Section&nbsp;9.3.5</a>: Not Modified
    810        / "305"  ; <a href="#status.305" id="rfc.xref.status.305.1" title="305 Use Proxy">Section&nbsp;9.3.6</a>: Use Proxy
    811        / "307"  ; <a href="#status.307" id="rfc.xref.status.307.1" title="307 Temporary Redirect">Section&nbsp;9.3.8</a>: Temporary Redirect
    812        / "400"  ; <a href="#status.400" id="rfc.xref.status.400.1" title="400 Bad Request">Section&nbsp;9.4.1</a>: Bad Request
    813        / "401"  ; <a href="#status.401" id="rfc.xref.status.401.1" title="401 Unauthorized">Section&nbsp;9.4.2</a>: Unauthorized
    814        / "402"  ; <a href="#status.402" id="rfc.xref.status.402.1" title="402 Payment Required">Section&nbsp;9.4.3</a>: Payment Required
    815        / "403"  ; <a href="#status.403" id="rfc.xref.status.403.1" title="403 Forbidden">Section&nbsp;9.4.4</a>: Forbidden
    816        / "404"  ; <a href="#status.404" id="rfc.xref.status.404.1" title="404 Not Found">Section&nbsp;9.4.5</a>: Not Found
    817        / "405"  ; <a href="#status.405" id="rfc.xref.status.405.1" title="405 Method Not Allowed">Section&nbsp;9.4.6</a>: Method Not Allowed
    818        / "406"  ; <a href="#status.406" id="rfc.xref.status.406.1" title="406 Not Acceptable">Section&nbsp;9.4.7</a>: Not Acceptable
    819        / "407"  ; <a href="#status.407" id="rfc.xref.status.407.1" title="407 Proxy Authentication Required">Section&nbsp;9.4.8</a>: Proxy Authentication Required
    820        / "408"  ; <a href="#status.408" id="rfc.xref.status.408.1" title="408 Request Timeout">Section&nbsp;9.4.9</a>: Request Time-out
    821        / "409"  ; <a href="#status.409" id="rfc.xref.status.409.1" title="409 Conflict">Section&nbsp;9.4.10</a>: Conflict
    822        / "410"  ; <a href="#status.410" id="rfc.xref.status.410.1" title="410 Gone">Section&nbsp;9.4.11</a>: Gone
    823        / "411"  ; <a href="#status.411" id="rfc.xref.status.411.1" title="411 Length Required">Section&nbsp;9.4.12</a>: Length Required
    824        / "412"  ; <a href="#status.412" id="rfc.xref.status.412.1" title="412 Precondition Failed">Section&nbsp;9.4.13</a>: Precondition Failed
    825        / "413"  ; <a href="#status.413" id="rfc.xref.status.413.1" title="413 Request Entity Too Large">Section&nbsp;9.4.14</a>: Request Entity Too Large
    826        / "414"  ; <a href="#status.414" id="rfc.xref.status.414.1" title="414 Request-target Too Long">Section&nbsp;9.4.15</a>: Request-target Too Long
    827        / "415"  ; <a href="#status.415" id="rfc.xref.status.415.1" title="415 Unsupported Media Type">Section&nbsp;9.4.16</a>: Unsupported Media Type
    828        / "416"  ; <a href="#status.416" id="rfc.xref.status.416.1" title="416 Requested Range Not Satisfiable">Section&nbsp;9.4.17</a>: Requested range not satisfiable
    829        / "417"  ; <a href="#status.417" id="rfc.xref.status.417.1" title="417 Expectation Failed">Section&nbsp;9.4.18</a>: Expectation Failed
    830        / "500"  ; <a href="#status.500" id="rfc.xref.status.500.1" title="500 Internal Server Error">Section&nbsp;9.5.1</a>: Internal Server Error
    831        / "501"  ; <a href="#status.501" id="rfc.xref.status.501.1" title="501 Not Implemented">Section&nbsp;9.5.2</a>: Not Implemented
    832        / "502"  ; <a href="#status.502" id="rfc.xref.status.502.1" title="502 Bad Gateway">Section&nbsp;9.5.3</a>: Bad Gateway
    833        / "503"  ; <a href="#status.503" id="rfc.xref.status.503.1" title="503 Service Unavailable">Section&nbsp;9.5.4</a>: Service Unavailable
    834        / "504"  ; <a href="#status.504" id="rfc.xref.status.504.1" title="504 Gateway Timeout">Section&nbsp;9.5.5</a>: Gateway Time-out
    835        / "505"  ; <a href="#status.505" id="rfc.xref.status.505.1" title="505 HTTP Version Not Supported">Section&nbsp;9.5.6</a>: HTTP Version not supported
     801         "100"  ; <a href="#status.100" id="rfc.xref.status.100.1" title="100 Continue">Section&nbsp;8.1.1</a>: Continue
     802       / "101"  ; <a href="#status.101" id="rfc.xref.status.101.1" title="101 Switching Protocols">Section&nbsp;8.1.2</a>: Switching Protocols
     803       / "200"  ; <a href="#status.200" id="rfc.xref.status.200.1" title="200 OK">Section&nbsp;8.2.1</a>: OK
     804       / "201"  ; <a href="#status.201" id="rfc.xref.status.201.1" title="201 Created">Section&nbsp;8.2.2</a>: Created
     805       / "202"  ; <a href="#status.202" id="rfc.xref.status.202.1" title="202 Accepted">Section&nbsp;8.2.3</a>: Accepted
     806       / "203"  ; <a href="#status.203" id="rfc.xref.status.203.1" title="203 Non-Authoritative Information">Section&nbsp;8.2.4</a>: Non-Authoritative Information
     807       / "204"  ; <a href="#status.204" id="rfc.xref.status.204.1" title="204 No Content">Section&nbsp;8.2.5</a>: No Content
     808       / "205"  ; <a href="#status.205" id="rfc.xref.status.205.1" title="205 Reset Content">Section&nbsp;8.2.6</a>: Reset Content
     809       / "206"  ; <a href="#status.206" id="rfc.xref.status.206.1" title="206 Partial Content">Section&nbsp;8.2.7</a>: Partial Content
     810       / "300"  ; <a href="#status.300" id="rfc.xref.status.300.1" title="300 Multiple Choices">Section&nbsp;8.3.1</a>: Multiple Choices
     811       / "301"  ; <a href="#status.301" id="rfc.xref.status.301.1" title="301 Moved Permanently">Section&nbsp;8.3.2</a>: Moved Permanently
     812       / "302"  ; <a href="#status.302" id="rfc.xref.status.302.1" title="302 Found">Section&nbsp;8.3.3</a>: Found
     813       / "303"  ; <a href="#status.303" id="rfc.xref.status.303.1" title="303 See Other">Section&nbsp;8.3.4</a>: See Other
     814       / "304"  ; <a href="#status.304" id="rfc.xref.status.304.1" title="304 Not Modified">Section&nbsp;8.3.5</a>: Not Modified
     815       / "305"  ; <a href="#status.305" id="rfc.xref.status.305.1" title="305 Use Proxy">Section&nbsp;8.3.6</a>: Use Proxy
     816       / "307"  ; <a href="#status.307" id="rfc.xref.status.307.1" title="307 Temporary Redirect">Section&nbsp;8.3.8</a>: Temporary Redirect
     817       / "400"  ; <a href="#status.400" id="rfc.xref.status.400.1" title="400 Bad Request">Section&nbsp;8.4.1</a>: Bad Request
     818       / "401"  ; <a href="#status.401" id="rfc.xref.status.401.1" title="401 Unauthorized">Section&nbsp;8.4.2</a>: Unauthorized
     819       / "402"  ; <a href="#status.402" id="rfc.xref.status.402.1" title="402 Payment Required">Section&nbsp;8.4.3</a>: Payment Required
     820       / "403"  ; <a href="#status.403" id="rfc.xref.status.403.1" title="403 Forbidden">Section&nbsp;8.4.4</a>: Forbidden
     821       / "404"  ; <a href="#status.404" id="rfc.xref.status.404.1" title="404 Not Found">Section&nbsp;8.4.5</a>: Not Found
     822       / "405"  ; <a href="#status.405" id="rfc.xref.status.405.1" title="405 Method Not Allowed">Section&nbsp;8.4.6</a>: Method Not Allowed
     823       / "406"  ; <a href="#status.406" id="rfc.xref.status.406.1" title="406 Not Acceptable">Section&nbsp;8.4.7</a>: Not Acceptable
     824       / "407"  ; <a href="#status.407" id="rfc.xref.status.407.1" title="407 Proxy Authentication Required">Section&nbsp;8.4.8</a>: Proxy Authentication Required
     825       / "408"  ; <a href="#status.408" id="rfc.xref.status.408.1" title="408 Request Timeout">Section&nbsp;8.4.9</a>: Request Time-out
     826       / "409"  ; <a href="#status.409" id="rfc.xref.status.409.1" title="409 Conflict">Section&nbsp;8.4.10</a>: Conflict
     827       / "410"  ; <a href="#status.410" id="rfc.xref.status.410.1" title="410 Gone">Section&nbsp;8.4.11</a>: Gone
     828       / "411"  ; <a href="#status.411" id="rfc.xref.status.411.1" title="411 Length Required">Section&nbsp;8.4.12</a>: Length Required
     829       / "412"  ; <a href="#status.412" id="rfc.xref.status.412.1" title="412 Precondition Failed">Section&nbsp;8.4.13</a>: Precondition Failed
     830       / "413"  ; <a href="#status.413" id="rfc.xref.status.413.1" title="413 Request Entity Too Large">Section&nbsp;8.4.14</a>: Request Entity Too Large
     831       / "414"  ; <a href="#status.414" id="rfc.xref.status.414.1" title="414 Request-target Too Long">Section&nbsp;8.4.15</a>: Request-target Too Long
     832       / "415"  ; <a href="#status.415" id="rfc.xref.status.415.1" title="415 Unsupported Media Type">Section&nbsp;8.4.16</a>: Unsupported Media Type
     833       / "416"  ; <a href="#status.416" id="rfc.xref.status.416.1" title="416 Requested Range Not Satisfiable">Section&nbsp;8.4.17</a>: Requested range not satisfiable
     834       / "417"  ; <a href="#status.417" id="rfc.xref.status.417.1" title="417 Expectation Failed">Section&nbsp;8.4.18</a>: Expectation Failed
     835       / "500"  ; <a href="#status.500" id="rfc.xref.status.500.1" title="500 Internal Server Error">Section&nbsp;8.5.1</a>: Internal Server Error
     836       / "501"  ; <a href="#status.501" id="rfc.xref.status.501.1" title="501 Not Implemented">Section&nbsp;8.5.2</a>: Not Implemented
     837       / "502"  ; <a href="#status.502" id="rfc.xref.status.502.1" title="502 Bad Gateway">Section&nbsp;8.5.3</a>: Bad Gateway
     838       / "503"  ; <a href="#status.503" id="rfc.xref.status.503.1" title="503 Service Unavailable">Section&nbsp;8.5.4</a>: Service Unavailable
     839       / "504"  ; <a href="#status.504" id="rfc.xref.status.504.1" title="504 Gateway Timeout">Section&nbsp;8.5.5</a>: Gateway Time-out
     840       / "505"  ; <a href="#status.505" id="rfc.xref.status.505.1" title="505 HTTP Version Not Supported">Section&nbsp;8.5.6</a>: HTTP Version not supported
    836841       / <a href="#request.header.fields" class="smpl">extension-code</a>
    837842
    838   <a href="#request.header.fields" class="smpl">extension-code</a> = 3<a href="#notation" class="smpl">DIGIT</a>
    839   <a href="#status.code.and.reason.phrase" class="smpl">Reason-Phrase</a>  = *( <a href="#notation" class="smpl">WSP</a> / <a href="#notation" class="smpl">VCHAR</a> / <a href="#notation" class="smpl">obs-text</a> )
    840 </pre><p id="rfc.section.5.p.4">HTTP status codes are extensible. HTTP applications are not required to understand the meaning of all registered status codes,
     843  <a href="#request.header.fields" class="smpl">extension-code</a> = 3<a href="#core.rules" class="smpl">DIGIT</a>
     844  <a href="#status.code.and.reason.phrase" class="smpl">Reason-Phrase</a>  = *( <a href="#core.rules" class="smpl">WSP</a> / <a href="#core.rules" class="smpl">VCHAR</a> / <a href="#core.rules" class="smpl">obs-text</a> )
     845</pre><p id="rfc.section.4.p.4">HTTP status codes are extensible. HTTP applications are not required to understand the meaning of all registered status codes,
    841846         though such understanding is obviously desirable. However, applications <em class="bcp14">MUST</em> understand the class of any status code, as indicated by the first digit, and treat any unrecognized response as being equivalent
    842847         to the x00 status code of that class, with the exception that an unrecognized response <em class="bcp14">MUST NOT</em> be cached. For example, if an unrecognized status code of 431 is received by the client, it can safely assume that there was
     
    844849         which will explain the unusual status.
    845850      </p>
    846       <h2 id="rfc.section.5.1"><a href="#rfc.section.5.1">5.1</a>&nbsp;<a id="status.code.registry" href="#status.code.registry">Status Code Registry</a></h2>
    847       <p id="rfc.section.5.1.p.1">The HTTP Status Code Registry defines the name space for the Status-Code token in the Status line of an HTTP response.</p>
    848       <p id="rfc.section.5.1.p.2">Values to be added to this name space are subject to IETF review (<a href="#RFC5226" id="rfc.xref.RFC5226.2"><cite title="Guidelines for Writing an IANA Considerations Section in RFCs">[RFC5226]</cite></a>, <a href="http://tools.ietf.org/html/rfc5226#section-4.1">Section 4.1</a>). Any document registering new status codes should be traceable through statuses of either 'Obsoletes' or 'Updates' to this
     851      <h2 id="rfc.section.4.1"><a href="#rfc.section.4.1">4.1</a>&nbsp;<a id="status.code.registry" href="#status.code.registry">Status Code Registry</a></h2>
     852      <p id="rfc.section.4.1.p.1">The HTTP Status Code Registry defines the name space for the Status-Code token in the Status line of an HTTP response.</p>
     853      <p id="rfc.section.4.1.p.2">Values to be added to this name space are subject to IETF review (<a href="#RFC5226" id="rfc.xref.RFC5226.2"><cite title="Guidelines for Writing an IANA Considerations Section in RFCs">[RFC5226]</cite></a>, <a href="http://tools.ietf.org/html/rfc5226#section-4.1">Section 4.1</a>). Any document registering new status codes should be traceable through statuses of either 'Obsoletes' or 'Updates' to this
    849854         document.
    850855      </p>
    851       <p id="rfc.section.5.1.p.3">The registry itself is maintained at &lt;<a href="http://www.iana.org/assignments/http-status-codes">http://www.iana.org/assignments/http-status-codes</a>&gt;.
    852       </p>
    853       <h1 id="rfc.section.6"><a href="#rfc.section.6">6.</a>&nbsp;<a id="response.header.fields" href="#response.header.fields">Response Header Fields</a></h1>
    854       <p id="rfc.section.6.p.1">The response-header fields allow the server to pass additional information about the response which cannot be placed in the
     856      <p id="rfc.section.4.1.p.3">The registry itself is maintained at &lt;<a href="http://www.iana.org/assignments/http-status-codes">http://www.iana.org/assignments/http-status-codes</a>&gt;.
     857      </p>
     858      <h1 id="rfc.section.5"><a href="#rfc.section.5">5.</a>&nbsp;<a id="response.header.fields" href="#response.header.fields">Response Header Fields</a></h1>
     859      <p id="rfc.section.5.p.1">The response-header fields allow the server to pass additional information about the response which cannot be placed in the
    855860         Status-Line. These header fields give information about the server and about further access to the resource identified by
    856861         the request-target.
    857862      </p>
    858       <div id="rfc.figure.u.12"></div><pre class="inline"><span id="rfc.iref.g.7"></span>  <a href="#response.header.fields" class="smpl">response-header</a> = <a href="#abnf.dependencies" class="smpl">Accept-Ranges</a>           ; <a href="#Part5" id="rfc.xref.Part5.6"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>, <a href="p5-range.html#header.accept-ranges" title="Accept-Ranges">Section 6.1</a>
    859                   / <a href="#abnf.dependencies" class="smpl">Age</a>                     ; <a href="#Part6" id="rfc.xref.Part6.3"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>, <a href="p6-cache.html#header.age" title="Age">Section 16.1</a>
    860                   / <a href="#header.allow" class="smpl">Allow</a>                   ; <a href="#header.allow" id="rfc.xref.header.allow.2" title="Allow">Section&nbsp;10.1</a>
    861                   / <a href="#abnf.dependencies" class="smpl">ETag</a>                    ; <a href="#Part4" id="rfc.xref.Part4.10"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>, <a href="p4-conditional.html#header.etag" title="ETag">Section 7.1</a>
    862                   / <a href="#header.location" class="smpl">Location</a>                ; <a href="#header.location" id="rfc.xref.header.location.1" title="Location">Section&nbsp;10.4</a>
    863                   / <a href="#abnf.dependencies" class="smpl">Proxy-Authenticate</a>      ; <a href="#Part7" id="rfc.xref.Part7.7"><cite title="HTTP/1.1, part 7: Authentication">[Part7]</cite></a>, <a href="p7-auth.html#header.proxy-authenticate" title="Proxy-Authenticate">Section 4.2</a>
    864                   / <a href="#header.retry-after" class="smpl">Retry-After</a>             ; <a href="#header.retry-after" id="rfc.xref.header.retry-after.1" title="Retry-After">Section&nbsp;10.7</a>
    865                   / <a href="#header.server" class="smpl">Server</a>                  ; <a href="#header.server" id="rfc.xref.header.server.1" title="Server">Section&nbsp;10.8</a>
    866                   / <a href="#abnf.dependencies" class="smpl">Vary</a>                    ; <a href="#Part6" id="rfc.xref.Part6.4"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>, <a href="p6-cache.html#header.vary" title="Vary">Section 16.5</a>
    867                   / <a href="#abnf.dependencies" class="smpl">WWW-Authenticate</a>        ; <a href="#Part7" id="rfc.xref.Part7.8"><cite title="HTTP/1.1, part 7: Authentication">[Part7]</cite></a>, <a href="p7-auth.html#header.www-authenticate" title="WWW-Authenticate">Section 4.4</a>
    868 </pre><p id="rfc.section.6.p.3">Response-header field names can be extended reliably only in combination with a change in the protocol version. However, new
     863      <div id="rfc.figure.u.12"></div><pre class="inline"><span id="rfc.iref.g.7"></span>  <a href="#response.header.fields" class="smpl">response-header</a> = <a href="#abnf.dependencies" class="smpl">Accept-Ranges</a>           ; <a href="#Part5" id="rfc.xref.Part5.6"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>, <a href="p5-range.html#header.accept-ranges" title="Accept-Ranges">Section 5.1</a>
     864                  / <a href="#abnf.dependencies" class="smpl">Age</a>                     ; <a href="#Part6" id="rfc.xref.Part6.3"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>, <a href="p6-cache.html#header.age" title="Age">Section 15.1</a>
     865                  / <a href="#header.allow" class="smpl">Allow</a>                   ; <a href="#header.allow" id="rfc.xref.header.allow.2" title="Allow">Section&nbsp;9.1</a>
     866                  / <a href="#abnf.dependencies" class="smpl">ETag</a>                    ; <a href="#Part4" id="rfc.xref.Part4.10"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>, <a href="p4-conditional.html#header.etag" title="ETag">Section 6.1</a>
     867                  / <a href="#header.location" class="smpl">Location</a>                ; <a href="#header.location" id="rfc.xref.header.location.1" title="Location">Section&nbsp;9.4</a>
     868                  / <a href="#abnf.dependencies" class="smpl">Proxy-Authenticate</a>      ; <a href="#Part7" id="rfc.xref.Part7.7"><cite title="HTTP/1.1, part 7: Authentication">[Part7]</cite></a>, <a href="p7-auth.html#header.proxy-authenticate" title="Proxy-Authenticate">Section 3.2</a>
     869                  / <a href="#header.retry-after" class="smpl">Retry-After</a>             ; <a href="#header.retry-after" id="rfc.xref.header.retry-after.1" title="Retry-After">Section&nbsp;9.7</a>
     870                  / <a href="#header.server" class="smpl">Server</a>                  ; <a href="#header.server" id="rfc.xref.header.server.1" title="Server">Section&nbsp;9.8</a>
     871                  / <a href="#abnf.dependencies" class="smpl">Vary</a>                    ; <a href="#Part6" id="rfc.xref.Part6.4"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>, <a href="p6-cache.html#header.vary" title="Vary">Section 15.5</a>
     872                  / <a href="#abnf.dependencies" class="smpl">WWW-Authenticate</a>        ; <a href="#Part7" id="rfc.xref.Part7.8"><cite title="HTTP/1.1, part 7: Authentication">[Part7]</cite></a>, <a href="p7-auth.html#header.www-authenticate" title="WWW-Authenticate">Section 3.4</a>
     873</pre><p id="rfc.section.5.p.3">Response-header field names can be extended reliably only in combination with a change in the protocol version. However, new
    869874         or experimental header fields <em class="bcp14">MAY</em> be given the semantics of response-header fields if all parties in the communication recognize them to be response-header
    870875         fields. Unrecognized header fields are treated as entity-header fields.
    871876      </p>
    872       <h1 id="rfc.section.7"><a href="#rfc.section.7">7.</a>&nbsp;<a id="entity" href="#entity">Entity</a></h1>
    873       <p id="rfc.section.7.p.1">Request and Response messages <em class="bcp14">MAY</em> transfer an entity if not otherwise restricted by the request method or response status code. An entity consists of entity-header
     877      <h1 id="rfc.section.6"><a href="#rfc.section.6">6.</a>&nbsp;<a id="entity" href="#entity">Entity</a></h1>
     878      <p id="rfc.section.6.p.1">Request and Response messages <em class="bcp14">MAY</em> transfer an entity if not otherwise restricted by the request method or response status code. An entity consists of entity-header
    874879         fields and an entity-body, although some responses will only include the entity-headers. HTTP entity-body and entity-header
    875880         fields are defined in <a href="#Part3" id="rfc.xref.Part3.9"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>.
    876881      </p>
    877       <p id="rfc.section.7.p.2">An entity-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 4.3</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>. The entity-body is obtained from the message-body by decoding any Transfer-Encoding that might have been applied to ensure
     882      <p id="rfc.section.6.p.2">An entity-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 4.3</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>. The entity-body is obtained from the message-body by decoding any Transfer-Encoding that might have been applied to ensure
    878883         safe and proper transfer of the message.
    879884      </p>
    880       <h1 id="rfc.section.8"><a href="#rfc.section.8">8.</a>&nbsp;<a id="method.definitions" href="#method.definitions">Method Definitions</a></h1>
    881       <p id="rfc.section.8.p.1">The set of common methods for HTTP/1.1 is defined below. Although this set can be expanded, additional methods cannot be assumed
     885      <h1 id="rfc.section.7"><a href="#rfc.section.7">7.</a>&nbsp;<a id="method.definitions" href="#method.definitions">Method Definitions</a></h1>
     886      <p id="rfc.section.7.p.1">The set of common methods for HTTP/1.1 is defined below. Although this set can be expanded, additional methods cannot be assumed
    882887         to share the same semantics for separately extended clients and servers.
    883888      </p>
    884       <h2 id="rfc.section.8.1"><a href="#rfc.section.8.1">8.1</a>&nbsp;<a id="safe.and.idempotent" href="#safe.and.idempotent">Safe and Idempotent Methods</a></h2>
     889      <h2 id="rfc.section.7.1"><a href="#rfc.section.7.1">7.1</a>&nbsp;<a id="safe.and.idempotent" href="#safe.and.idempotent">Safe and Idempotent Methods</a></h2>
    885890      <div id="rfc.iref.s.1"></div>
    886       <h3 id="rfc.section.8.1.1"><a href="#rfc.section.8.1.1">8.1.1</a>&nbsp;<a id="safe.methods" href="#safe.methods">Safe Methods</a></h3>
    887       <p id="rfc.section.8.1.1.p.1">Implementors should be aware that the software represents the user in their interactions over the Internet, and should be
     891      <h3 id="rfc.section.7.1.1"><a href="#rfc.section.7.1.1">7.1.1</a>&nbsp;<a id="safe.methods" href="#safe.methods">Safe Methods</a></h3>
     892      <p id="rfc.section.7.1.1.p.1">Implementors should be aware that the software represents the user in their interactions over the Internet, and should be
    888893         careful to allow the user to be aware of any actions they might take which may have an unexpected significance to themselves
    889894         or others.
    890895      </p>
    891       <p id="rfc.section.8.1.1.p.2">In particular, the convention has been established that the GET and HEAD methods <em class="bcp14">SHOULD NOT</em> have the significance of taking an action other than retrieval. These methods ought to be considered "<dfn id="safe">safe</dfn>". This allows user agents to represent other methods, such as POST, PUT and DELETE, in a special way, so that the user is
     896      <p id="rfc.section.7.1.1.p.2">In particular, the convention has been established that the GET and HEAD methods <em class="bcp14">SHOULD NOT</em> have the significance of taking an action other than retrieval. These methods ought to be considered "<dfn id="safe">safe</dfn>". This allows user agents to represent other methods, such as POST, PUT and DELETE, in a special way, so that the user is
    892897         made aware of the fact that a possibly unsafe action is being requested.
    893898      </p>
    894       <p id="rfc.section.8.1.1.p.3">Naturally, it is not possible to ensure that the server does not generate side-effects as a result of performing a GET request;
     899      <p id="rfc.section.7.1.1.p.3">Naturally, it is not possible to ensure that the server does not generate side-effects as a result of performing a GET request;
    895900         in fact, some dynamic resources consider that a feature. The important distinction here is that the user did not request the
    896901         side-effects, so therefore cannot be held accountable for them.
    897902      </p>
    898903      <div id="rfc.iref.i.1"></div>
    899       <h3 id="rfc.section.8.1.2"><a href="#rfc.section.8.1.2">8.1.2</a>&nbsp;<a id="idempotent.methods" href="#idempotent.methods">Idempotent Methods</a></h3>
    900       <p id="rfc.section.8.1.2.p.1">Methods can also have the property of "idempotence" in that (aside from error or expiration issues) the side-effects of N
     904      <h3 id="rfc.section.7.1.2"><a href="#rfc.section.7.1.2">7.1.2</a>&nbsp;<a id="idempotent.methods" href="#idempotent.methods">Idempotent Methods</a></h3>
     905      <p id="rfc.section.7.1.2.p.1">Methods can also have the property of "idempotence" in that (aside from error or expiration issues) the side-effects of N
    901906         &gt; 0 identical requests is the same as for a single request. The methods GET, HEAD, PUT and DELETE share this property. Also,
    902907         the methods OPTIONS and TRACE <em class="bcp14">SHOULD NOT</em> have side effects, and so are inherently idempotent.
    903908      </p>
    904       <p id="rfc.section.8.1.2.p.2">However, it is possible that a sequence of several requests is non-idempotent, even if all of the methods executed in that
     909      <p id="rfc.section.7.1.2.p.2">However, it is possible that a sequence of several requests is non-idempotent, even if all of the methods executed in that
    905910         sequence are idempotent. (A sequence is idempotent if a single execution of the entire sequence always yields a result that
    906911         is not changed by a reexecution of all, or part, of that sequence.) For example, a sequence is non-idempotent if its result
    907912         depends on a value that is later modified in the same sequence.
    908913      </p>
    909       <p id="rfc.section.8.1.2.p.3">A sequence that never has side effects is idempotent, by definition (provided that no concurrent operations are being executed
     914      <p id="rfc.section.7.1.2.p.3">A sequence that never has side effects is idempotent, by definition (provided that no concurrent operations are being executed
    910915         on the same set of resources).
    911916      </p>
    912       <h2 id="rfc.section.8.2"><a href="#rfc.section.8.2">8.2</a>&nbsp;<a id="OPTIONS" href="#OPTIONS">OPTIONS</a></h2>
     917      <h2 id="rfc.section.7.2"><a href="#rfc.section.7.2">7.2</a>&nbsp;<a id="OPTIONS" href="#OPTIONS">OPTIONS</a></h2>
    913918      <div id="rfc.iref.o.1"></div>
    914919      <div id="rfc.iref.m.1"></div>
    915       <p id="rfc.section.8.2.p.1">The OPTIONS method represents a request for information about the communication options available on the request/response
     920      <p id="rfc.section.7.2.p.1">The OPTIONS method represents a request for information about the communication options available on the request/response
    916921         chain identified by the request-target. This method allows the client to determine the options and/or requirements associated
    917922         with a resource, or the capabilities of a server, without implying a resource action or initiating a resource retrieval.
    918923      </p>
    919       <p id="rfc.section.8.2.p.2">Responses to this method are not cacheable.</p>
    920       <p id="rfc.section.8.2.p.3">If the OPTIONS request includes an entity-body (as indicated by the presence of Content-Length or Transfer-Encoding), then
     924      <p id="rfc.section.7.2.p.2">Responses to this method are not cacheable.</p>
     925      <p id="rfc.section.7.2.p.3">If the OPTIONS request includes an entity-body (as indicated by the presence of Content-Length or Transfer-Encoding), then
    921926         the media type <em class="bcp14">MUST</em> be indicated by a Content-Type field. Although this specification does not define any use for such a body, future extensions
    922927         to HTTP might use the OPTIONS body to make more detailed queries on the server.
    923928      </p>
    924       <p id="rfc.section.8.2.p.4">If the request-target is an asterisk ("*"), the OPTIONS request is intended to apply to the server in general rather than
     929      <p id="rfc.section.7.2.p.4">If the request-target is an asterisk ("*"), the OPTIONS request is intended to apply to the server in general rather than
    925930         to a specific resource. Since a server's communication options typically depend on the resource, the "*" request is only useful
    926931         as a "ping" or "no-op" type of method; it does nothing beyond allowing the client to test the capabilities of the server.
    927932         For example, this can be used to test a proxy for HTTP/1.1 compliance (or lack thereof).
    928933      </p>
    929       <p id="rfc.section.8.2.p.5">If the request-target is not an asterisk, the OPTIONS request applies only to the options that are available when communicating
     934      <p id="rfc.section.7.2.p.5">If the request-target is not an asterisk, the OPTIONS request applies only to the options that are available when communicating
    930935         with that resource.
    931936      </p>
    932       <p id="rfc.section.8.2.p.6">A 200 response <em class="bcp14">SHOULD</em> include any header fields that indicate optional features implemented by the server and applicable to that resource (e.g.,
     937      <p id="rfc.section.7.2.p.6">A 200 response <em class="bcp14">SHOULD</em> include any header fields that indicate optional features implemented by the server and applicable to that resource (e.g.,
    933938         Allow), possibly including extensions not defined by this specification. The response body, if any, <em class="bcp14">SHOULD</em> also include information about the communication options. The format for such a body is not defined by this specification,
    934939         but might be defined by future extensions to HTTP. Content negotiation <em class="bcp14">MAY</em> be used to select the appropriate response format. If no response body is included, the response <em class="bcp14">MUST</em> include a Content-Length field with a field-value of "0".
    935940      </p>
    936       <p id="rfc.section.8.2.p.7">The Max-Forwards request-header field <em class="bcp14">MAY</em> be used to target a specific proxy in the request chain. When a proxy receives an OPTIONS request on an absolute-URI for which
     941      <p id="rfc.section.7.2.p.7">The Max-Forwards request-header field <em class="bcp14">MAY</em> be used to target a specific proxy in the request chain. When a proxy receives an OPTIONS request on an absolute-URI for which
    937942         request forwarding is permitted, the proxy <em class="bcp14">MUST</em> check for a Max-Forwards field. If the Max-Forwards field-value is zero ("0"), the proxy <em class="bcp14">MUST NOT</em> forward the message; instead, the proxy <em class="bcp14">SHOULD</em> respond with its own communication options. If the Max-Forwards field-value is an integer greater than zero, the proxy <em class="bcp14">MUST</em> decrement the field-value when it forwards the request. If no Max-Forwards field is present in the request, then the forwarded
    938943         request <em class="bcp14">MUST NOT</em> include a Max-Forwards field.
    939944      </p>
    940       <h2 id="rfc.section.8.3"><a href="#rfc.section.8.3">8.3</a>&nbsp;<a id="GET" href="#GET">GET</a></h2>
     945      <h2 id="rfc.section.7.3"><a href="#rfc.section.7.3">7.3</a>&nbsp;<a id="GET" href="#GET">GET</a></h2>
    941946      <div id="rfc.iref.g.8"></div>
    942947      <div id="rfc.iref.m.2"></div>
    943       <p id="rfc.section.8.3.p.1">The GET method means retrieve whatever information (in the form of an entity) is identified by the request-target. If the
     948      <p id="rfc.section.7.3.p.1">The GET method means retrieve whatever information (in the form of an entity) is identified by the request-target. If the
    944949         request-target refers to a data-producing process, it is the produced data which shall be returned as the entity in the response
    945950         and not the source text of the process, unless that text happens to be the output of the process.
    946951      </p>
    947       <p id="rfc.section.8.3.p.2">The semantics of the GET method change to a "conditional GET" if the request message includes an If-Modified-Since, If-Unmodified-Since,
     952      <p id="rfc.section.7.3.p.2">The semantics of the GET method change to a "conditional GET" if the request message includes an If-Modified-Since, If-Unmodified-Since,
    948953         If-Match, If-None-Match, or If-Range header field. A conditional GET method requests that the entity be transferred only under
    949954         the circumstances described by the conditional header field(s). The conditional GET method is intended to reduce unnecessary
     
    951956         held by the client.
    952957      </p>
    953       <p id="rfc.section.8.3.p.3">The semantics of the GET method change to a "partial GET" if the request message includes a Range header field. A partial
    954          GET requests that only part of the entity be transferred, as described in <a href="p5-range.html#header.range" title="Range">Section 6.4</a> of <a href="#Part5" id="rfc.xref.Part5.7"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>. The partial GET method is intended to reduce unnecessary network usage by allowing partially-retrieved entities to be completed
     958      <p id="rfc.section.7.3.p.3">The semantics of the GET method change to a "partial GET" if the request message includes a Range header field. A partial
     959         GET requests that only part of the entity be transferred, as described in <a href="p5-range.html#header.range" title="Range">Section 5.4</a> of <a href="#Part5" id="rfc.xref.Part5.7"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>. The partial GET method is intended to reduce unnecessary network usage by allowing partially-retrieved entities to be completed
    955960         without transferring data already held by the client.
    956961      </p>
    957       <p id="rfc.section.8.3.p.4">The response to a GET request is cacheable if and only if it meets the requirements for HTTP caching described in <a href="#Part6" id="rfc.xref.Part6.5"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>.
    958       </p>
    959       <p id="rfc.section.8.3.p.5">See <a href="#encoding.sensitive.information.in.uris" title="Encoding Sensitive Information in URIs">Section&nbsp;12.2</a> for security considerations when used for forms.
    960       </p>
    961       <h2 id="rfc.section.8.4"><a href="#rfc.section.8.4">8.4</a>&nbsp;<a id="HEAD" href="#HEAD">HEAD</a></h2>
     962      <p id="rfc.section.7.3.p.4">The response to a GET request is cacheable if and only if it meets the requirements for HTTP caching described in <a href="#Part6" id="rfc.xref.Part6.5"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>.
     963      </p>
     964      <p id="rfc.section.7.3.p.5">See <a href="#encoding.sensitive.information.in.uris" title="Encoding Sensitive Information in URIs">Section&nbsp;11.2</a> for security considerations when used for forms.
     965      </p>
     966      <h2 id="rfc.section.7.4"><a href="#rfc.section.7.4">7.4</a>&nbsp;<a id="HEAD" href="#HEAD">HEAD</a></h2>
    962967      <div id="rfc.iref.h.1"></div>
    963968      <div id="rfc.iref.m.3"></div>
    964       <p id="rfc.section.8.4.p.1">The HEAD method is identical to GET except that the server <em class="bcp14">MUST NOT</em> return a message-body in the response. The metainformation contained in the HTTP headers in response to a HEAD request <em class="bcp14">SHOULD</em> be identical to the information sent in response to a GET request. This method can be used for obtaining metainformation about
     969      <p id="rfc.section.7.4.p.1">The HEAD method is identical to GET except that the server <em class="bcp14">MUST NOT</em> return a message-body in the response. The metainformation contained in the HTTP headers in response to a HEAD request <em class="bcp14">SHOULD</em> be identical to the information sent in response to a GET request. This method can be used for obtaining metainformation about
    965970         the entity implied by the request without transferring the entity-body itself. This method is often used for testing hypertext
    966971         links for validity, accessibility, and recent modification.
    967972      </p>
    968       <p id="rfc.section.8.4.p.2">The response to a HEAD request <em class="bcp14">MAY</em> be cacheable in the sense that the information contained in the response <em class="bcp14">MAY</em> be used to update a previously cached entity from that resource. If the new field values indicate that the cached entity differs
     973      <p id="rfc.section.7.4.p.2">The response to a HEAD request <em class="bcp14">MAY</em> be cacheable in the sense that the information contained in the response <em class="bcp14">MAY</em> be used to update a previously cached entity from that resource. If the new field values indicate that the cached entity differs
    969974         from the current entity (as would be indicated by a change in Content-Length, Content-MD5, ETag or Last-Modified), then the
    970975         cache <em class="bcp14">MUST</em> treat the cache entry as stale.
     
    972977      <div id="rfc.iref.p.1"></div>
    973978      <div id="rfc.iref.m.4"></div>
    974       <h2 id="rfc.section.8.5"><a href="#rfc.section.8.5">8.5</a>&nbsp;<a id="POST" href="#POST">POST</a></h2>
    975       <p id="rfc.section.8.5.p.1">The POST method is used to request that the origin server accept the entity enclosed in the request as data to be processed
     979      <h2 id="rfc.section.7.5"><a href="#rfc.section.7.5">7.5</a>&nbsp;<a id="POST" href="#POST">POST</a></h2>
     980      <p id="rfc.section.7.5.p.1">The POST method is used to request that the origin server accept the entity enclosed in the request as data to be processed
    976981         by the resource identified by the request-target in the Request-Line. POST is designed to allow a uniform method to cover
    977982         the following functions:
     
    983988         <li>Extending a database through an append operation.</li>
    984989      </ul>
    985       <p id="rfc.section.8.5.p.2">The actual function performed by the POST method is determined by the server and is usually dependent on the request-target.</p>
    986       <p id="rfc.section.8.5.p.3">The action performed by the POST method might not result in a resource that can be identified by a URI. In this case, either
     990      <p id="rfc.section.7.5.p.2">The actual function performed by the POST method is determined by the server and is usually dependent on the request-target.</p>
     991      <p id="rfc.section.7.5.p.3">The action performed by the POST method might not result in a resource that can be identified by a URI. In this case, either
    987992         200 (OK) or 204 (No Content) is the appropriate response status, depending on whether or not the response includes an entity
    988993         that describes the result.
    989994      </p>
    990       <p id="rfc.section.8.5.p.4">If a resource has been created on the origin server, the response <em class="bcp14">SHOULD</em> be 201 (Created) and contain an entity which describes the status of the request and refers to the new resource, and a Location
    991          header (see <a href="#header.location" id="rfc.xref.header.location.2" title="Location">Section&nbsp;10.4</a>).
    992       </p>
    993       <p id="rfc.section.8.5.p.5">Responses to this method are not cacheable, unless the response includes appropriate Cache-Control or Expires header fields.
     995      <p id="rfc.section.7.5.p.4">If a resource has been created on the origin server, the response <em class="bcp14">SHOULD</em> be 201 (Created) and contain an entity which describes the status of the request and refers to the new resource, and a Location
     996         header (see <a href="#header.location" id="rfc.xref.header.location.2" title="Location">Section&nbsp;9.4</a>).
     997      </p>
     998      <p id="rfc.section.7.5.p.5">Responses to this method are not cacheable, unless the response includes appropriate Cache-Control or Expires header fields.
    994999         However, the 303 (See Other) response can be used to direct the user agent to retrieve a cacheable resource.
    9951000      </p>
    9961001      <div id="rfc.iref.p.2"></div>
    9971002      <div id="rfc.iref.m.5"></div>
    998       <h2 id="rfc.section.8.6"><a href="#rfc.section.8.6">8.6</a>&nbsp;<a id="PUT" href="#PUT">PUT</a></h2>
    999       <p id="rfc.section.8.6.p.1">The PUT method requests that the enclosed entity be stored at the supplied request-target. If the request-target refers to
     1003      <h2 id="rfc.section.7.6"><a href="#rfc.section.7.6">7.6</a>&nbsp;<a id="PUT" href="#PUT">PUT</a></h2>
     1004      <p id="rfc.section.7.6.p.1">The PUT method requests that the enclosed entity be stored at the supplied request-target. If the request-target refers to
    10001005         an already existing resource, the enclosed entity <em class="bcp14">SHOULD</em> be considered as a modified version of the one residing on the origin server. If the request-target does not point to an existing
    10011006         resource, and that URI is capable of being defined as a new resource by the requesting user agent, the origin server can create
     
    10041009         an appropriate error response <em class="bcp14">SHOULD</em> be given that reflects the nature of the problem. The recipient of the entity <em class="bcp14">MUST NOT</em> ignore any Content-* headers (headers starting with the prefix 'Content-') that it does not understand or implement and <em class="bcp14">MUST</em> return a 501 (Not Implemented) response in such cases.
    10051010      </p>
    1006       <p id="rfc.section.8.6.p.2">If the request passes through a cache and the request-target identifies one or more currently cached entities, those entries <em class="bcp14">SHOULD</em> be treated as stale. Responses to this method are not cacheable.
    1007       </p>
    1008       <p id="rfc.section.8.6.p.3">The fundamental difference between the POST and PUT requests is reflected in the different meaning of the request-target.
     1011      <p id="rfc.section.7.6.p.2">If the request passes through a cache and the request-target identifies one or more currently cached entities, those entries <em class="bcp14">SHOULD</em> be treated as stale. Responses to this method are not cacheable.
     1012      </p>
     1013      <p id="rfc.section.7.6.p.3">The fundamental difference between the POST and PUT requests is reflected in the different meaning of the request-target.
    10091014         The URI in a POST request identifies the resource that will handle the enclosed entity. That resource might be a data-accepting
    10101015         process, a gateway to some other protocol, or a separate entity that accepts annotations. In contrast, the URI in a PUT request
     
    10121017         it <em class="bcp14">MUST</em> send a 301 (Moved Permanently) response; the user agent <em class="bcp14">MAY</em> then make its own decision regarding whether or not to redirect the request.
    10131018      </p>
    1014       <p id="rfc.section.8.6.p.4">A single resource <em class="bcp14">MAY</em> be identified by many different URIs. For example, an article might have a URI for identifying "the current version" which
     1019      <p id="rfc.section.7.6.p.4">A single resource <em class="bcp14">MAY</em> be identified by many different URIs. For example, an article might have a URI for identifying "the current version" which
    10151020         is separate from the URI identifying each particular version. In this case, a PUT request on a general URI might result in
    10161021         several other URIs being defined by the origin server.
    10171022      </p>
    1018       <p id="rfc.section.8.6.p.5">HTTP/1.1 does not define how a PUT method affects the state of an origin server.</p>
    1019       <p id="rfc.section.8.6.p.6">Unless otherwise specified for a particular entity-header, the entity-headers in the PUT request <em class="bcp14">SHOULD</em> be applied to the resource created or modified by the PUT.
     1023      <p id="rfc.section.7.6.p.5">HTTP/1.1 does not define how a PUT method affects the state of an origin server.</p>
     1024      <p id="rfc.section.7.6.p.6">Unless otherwise specified for a particular entity-header, the entity-headers in the PUT request <em class="bcp14">SHOULD</em> be applied to the resource created or modified by the PUT.
    10201025      </p>
    10211026      <div id="rfc.iref.d.1"></div>
    10221027      <div id="rfc.iref.m.6"></div>
    1023       <h2 id="rfc.section.8.7"><a href="#rfc.section.8.7">8.7</a>&nbsp;<a id="DELETE" href="#DELETE">DELETE</a></h2>
    1024       <p id="rfc.section.8.7.p.1">The DELETE method requests that the origin server delete the resource identified by the request-target. This method <em class="bcp14">MAY</em> be overridden by human intervention (or other means) on the origin server. The client cannot be guaranteed that the operation
     1028      <h2 id="rfc.section.7.7"><a href="#rfc.section.7.7">7.7</a>&nbsp;<a id="DELETE" href="#DELETE">DELETE</a></h2>
     1029      <p id="rfc.section.7.7.p.1">The DELETE method requests that the origin server delete the resource identified by the request-target. This method <em class="bcp14">MAY</em> be overridden by human intervention (or other means) on the origin server. The client cannot be guaranteed that the operation
    10251030         has been carried out, even if the status code returned from the origin server indicates that the action has been completed
    10261031         successfully. However, the server <em class="bcp14">SHOULD NOT</em> indicate success unless, at the time the response is given, it intends to delete the resource or move it to an inaccessible
    10271032         location.
    10281033      </p>
    1029       <p id="rfc.section.8.7.p.2">A successful response <em class="bcp14">SHOULD</em> be 200 (OK) if the response includes an entity describing the status, 202 (Accepted) if the action has not yet been enacted,
     1034      <p id="rfc.section.7.7.p.2">A successful response <em class="bcp14">SHOULD</em> be 200 (OK) if the response includes an entity describing the status, 202 (Accepted) if the action has not yet been enacted,
    10301035         or 204 (No Content) if the action has been enacted but the response does not include an entity.
    10311036      </p>
    1032       <p id="rfc.section.8.7.p.3">If the request passes through a cache and the request-target identifies one or more currently cached entities, those entries <em class="bcp14">SHOULD</em> be treated as stale. Responses to this method are not cacheable.
    1033       </p>
    1034       <h2 id="rfc.section.8.8"><a href="#rfc.section.8.8">8.8</a>&nbsp;<a id="TRACE" href="#TRACE">TRACE</a></h2>
     1037      <p id="rfc.section.7.7.p.3">If the request passes through a cache and the request-target identifies one or more currently cached entities, those entries <em class="bcp14">SHOULD</em> be treated as stale. Responses to this method are not cacheable.
     1038      </p>
     1039      <h2 id="rfc.section.7.8"><a href="#rfc.section.7.8">7.8</a>&nbsp;<a id="TRACE" href="#TRACE">TRACE</a></h2>
    10351040      <div id="rfc.iref.t.1"></div>
    10361041      <div id="rfc.iref.m.7"></div>
    1037       <p id="rfc.section.8.8.p.1">The TRACE method is used to invoke a remote, application-layer loop-back of the request message. The final recipient of the
     1042      <p id="rfc.section.7.8.p.1">The TRACE method is used to invoke a remote, application-layer loop-back of the request message. The final recipient of the
    10381043         request <em class="bcp14">SHOULD</em> reflect the message received back to the client as the entity-body of a 200 (OK) response. The final recipient is either the
    1039          origin server or the first proxy or gateway to receive a Max-Forwards value of zero (0) in the request (see <a href="#header.max-forwards" id="rfc.xref.header.max-forwards.2" title="Max-Forwards">Section&nbsp;10.5</a>). A TRACE request <em class="bcp14">MUST NOT</em> include an entity.
    1040       </p>
    1041       <p id="rfc.section.8.8.p.2">TRACE allows the client to see what is being received at the other end of the request chain and use that data for testing
     1044         origin server or the first proxy or gateway to receive a Max-Forwards value of zero (0) in the request (see <a href="#header.max-forwards" id="rfc.xref.header.max-forwards.2" title="Max-Forwards">Section&nbsp;9.5</a>). A TRACE request <em class="bcp14">MUST NOT</em> include an entity.
     1045      </p>
     1046      <p id="rfc.section.7.8.p.2">TRACE allows the client to see what is being received at the other end of the request chain and use that data for testing
    10421047         or diagnostic information. The value of the Via header field (<a href="p1-messaging.html#header.via" title="Via">Section 8.9</a> of <a href="#Part1" id="rfc.xref.Part1.25"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) is of particular interest, since it acts as a trace of the request chain. Use of the Max-Forwards header field allows the
    10431048         client to limit the length of the request chain, which is useful for testing a chain of proxies forwarding messages in an
    10441049         infinite loop.
    10451050      </p>
    1046       <p id="rfc.section.8.8.p.3">If the request is valid, the response <em class="bcp14">SHOULD</em> contain the entire request message in the entity-body, with a Content-Type of "message/http" (see <a href="p1-messaging.html#internet.media.type.message.http" title="Internet Media Type message/http">Section 9.3.1</a> of <a href="#Part1" id="rfc.xref.Part1.26"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>). Responses to this method <em class="bcp14">MUST NOT</em> be cached.
     1051      <p id="rfc.section.7.8.p.3">If the request is valid, the response <em class="bcp14">SHOULD</em> contain the entire request message in the entity-body, with a Content-Type of "message/http" (see <a href="p1-messaging.html#internet.media.type.message.http" title="Internet Media Type message/http">Section 9.3.1</a> of <a href="#Part1" id="rfc.xref.Part1.26"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>). Responses to this method <em class="bcp14">MUST NOT</em> be cached.
    10471052      </p>
    10481053      <div id="rfc.iref.c.1"></div>
    10491054      <div id="rfc.iref.m.8"></div>
    1050       <h2 id="rfc.section.8.9"><a href="#rfc.section.8.9">8.9</a>&nbsp;<a id="CONNECT" href="#CONNECT">CONNECT</a></h2>
    1051       <p id="rfc.section.8.9.p.1">This specification reserves the method name CONNECT for use with a proxy that can dynamically switch to being a tunnel (e.g.
     1055      <h2 id="rfc.section.7.9"><a href="#rfc.section.7.9">7.9</a>&nbsp;<a id="CONNECT" href="#CONNECT">CONNECT</a></h2>
     1056      <p id="rfc.section.7.9.p.1">This specification reserves the method name CONNECT for use with a proxy that can dynamically switch to being a tunnel (e.g.
    10521057         SSL tunneling <a href="#RFC2817" id="rfc.xref.RFC2817.1"><cite title="Upgrading to TLS Within HTTP/1.1">[RFC2817]</cite></a>).
    10531058      </p>
    1054       <h1 id="rfc.section.9"><a href="#rfc.section.9">9.</a>&nbsp;<a id="status.codes" href="#status.codes">Status Code Definitions</a></h1>
    1055       <p id="rfc.section.9.p.1">Each Status-Code is described below, including a description of which method(s) it can follow and any metainformation required
     1059      <h1 id="rfc.section.8"><a href="#rfc.section.8">8.</a>&nbsp;<a id="status.codes" href="#status.codes">Status Code Definitions</a></h1>
     1060      <p id="rfc.section.8.p.1">Each Status-Code is described below, including a description of which method(s) it can follow and any metainformation required
    10561061         in the response.
    10571062      </p>
    1058       <h2 id="rfc.section.9.1"><a href="#rfc.section.9.1">9.1</a>&nbsp;<a id="status.1xx" href="#status.1xx">Informational 1xx</a></h2>
    1059       <p id="rfc.section.9.1.p.1">This class of status code indicates a provisional response, consisting only of the Status-Line and optional headers, and is
     1063      <h2 id="rfc.section.8.1"><a href="#rfc.section.8.1">8.1</a>&nbsp;<a id="status.1xx" href="#status.1xx">Informational 1xx</a></h2>
     1064      <p id="rfc.section.8.1.p.1">This class of status code indicates a provisional response, consisting only of the Status-Line and optional headers, and is
    10601065         terminated by an empty line. There are no required headers for this class of status code. Since HTTP/1.0 did not define any
    10611066         1xx status codes, servers <em class="bcp14">MUST NOT</em> send a 1xx response to an HTTP/1.0 client except under experimental conditions.
    10621067      </p>
    1063       <p id="rfc.section.9.1.p.2">A client <em class="bcp14">MUST</em> be prepared to accept one or more 1xx status responses prior to a regular response, even if the client does not expect a 100
     1068      <p id="rfc.section.8.1.p.2">A client <em class="bcp14">MUST</em> be prepared to accept one or more 1xx status responses prior to a regular response, even if the client does not expect a 100
    10641069         (Continue) status message. Unexpected 1xx status responses <em class="bcp14">MAY</em> be ignored by a user agent.
    10651070      </p>
    1066       <p id="rfc.section.9.1.p.3">Proxies <em class="bcp14">MUST</em> forward 1xx responses, unless the connection between the proxy and its client has been closed, or unless the proxy itself
     1071      <p id="rfc.section.8.1.p.3">Proxies <em class="bcp14">MUST</em> forward 1xx responses, unless the connection between the proxy and its client has been closed, or unless the proxy itself
    10671072         requested the generation of the 1xx response. (For example, if a proxy adds a "Expect: 100-continue" field when it forwards
    10681073         a request, then it need not forward the corresponding 100 (Continue) response(s).)
     
    10701075      <div id="rfc.iref.25"></div>
    10711076      <div id="rfc.iref.s.2"></div>
    1072       <h3 id="rfc.section.9.1.1"><a href="#rfc.section.9.1.1">9.1.1</a>&nbsp;<a id="status.100" href="#status.100">100 Continue</a></h3>
    1073       <p id="rfc.section.9.1.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
     1077      <h3 id="rfc.section.8.1.1"><a href="#rfc.section.8.1.1">8.1.1</a>&nbsp;<a id="status.100" href="#status.100">100 Continue</a></h3>
     1078      <p id="rfc.section.8.1.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
    10741079         received and has not yet been rejected by the server. The client <em class="bcp14">SHOULD</em> continue by sending the remainder of the request or, if the request has already been completed, ignore this response. The
    10751080         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 7.2.3</a> of <a href="#Part1" id="rfc.xref.Part1.27"><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.
     
    10771082      <div id="rfc.iref.26"></div>
    10781083      <div id="rfc.iref.s.3"></div>
    1079       <h3 id="rfc.section.9.1.2"><a href="#rfc.section.9.1.2">9.1.2</a>&nbsp;<a id="status.101" href="#status.101">101 Switching Protocols</a></h3>
    1080       <p id="rfc.section.9.1.2.p.1">The server understands and is willing to comply with the client's request, via the Upgrade message header field (<a href="p5-range.html#header.range" title="Range">Section 6.4</a> of <a href="#Part5" id="rfc.xref.Part5.8"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>), for a change in the application protocol being used on this connection. The server will switch protocols to those defined
     1084      <h3 id="rfc.section.8.1.2"><a href="#rfc.section.8.1.2">8.1.2</a>&nbsp;<a id="status.101" href="#status.101">101 Switching Protocols</a></h3>
     1085      <p id="rfc.section.8.1.2.p.1">The server understands and is willing to comply with the client's request, via the Upgrade message header field (<a href="p5-range.html#header.range" title="Range">Section 5.4</a> of <a href="#Part5" id="rfc.xref.Part5.8"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>), for a change in the application protocol being used on this connection. The server will switch protocols to those defined
    10811086         by the response's Upgrade header field immediately after the empty line which terminates the 101 response.
    10821087      </p>
    1083       <p id="rfc.section.9.1.2.p.2">The protocol <em class="bcp14">SHOULD</em> be switched only when it is advantageous to do so. For example, switching to a newer version of HTTP is advantageous over
     1088      <p id="rfc.section.8.1.2.p.2">The protocol <em class="bcp14">SHOULD</em> be switched only when it is advantageous to do so. For example, switching to a newer version of HTTP is advantageous over
    10841089         older versions, and switching to a real-time, synchronous protocol might be advantageous when delivering resources that use
    10851090         such features.
    10861091      </p>
    1087       <h2 id="rfc.section.9.2"><a href="#rfc.section.9.2">9.2</a>&nbsp;<a id="status.2xx" href="#status.2xx">Successful 2xx</a></h2>
    1088       <p id="rfc.section.9.2.p.1">This class of status code indicates that the client's request was successfully received, understood, and accepted.</p>
     1092      <h2 id="rfc.section.8.2"><a href="#rfc.section.8.2">8.2</a>&nbsp;<a id="status.2xx" href="#status.2xx">Successful 2xx</a></h2>
     1093      <p id="rfc.section.8.2.p.1">This class of status code indicates that the client's request was successfully received, understood, and accepted.</p>
    10891094      <div id="rfc.iref.27"></div>
    10901095      <div id="rfc.iref.s.4"></div>
    1091       <h3 id="rfc.section.9.2.1"><a href="#rfc.section.9.2.1">9.2.1</a>&nbsp;<a id="status.200" href="#status.200">200 OK</a></h3>
    1092       <p id="rfc.section.9.2.1.p.1">The request has succeeded. The information returned with the response is dependent on the method used in the request, for
     1096      <h3 id="rfc.section.8.2.1"><a href="#rfc.section.8.2.1">8.2.1</a>&nbsp;<a id="status.200" href="#status.200">200 OK</a></h3>
     1097      <p id="rfc.section.8.2.1.p.1">The request has succeeded. The information returned with the response is dependent on the method used in the request, for
    10931098         example:
    10941099      </p>
     
    11051110      <div id="rfc.iref.28"></div>
    11061111      <div id="rfc.iref.s.5"></div>
    1107       <h3 id="rfc.section.9.2.2"><a href="#rfc.section.9.2.2">9.2.2</a>&nbsp;<a id="status.201" href="#status.201">201 Created</a></h3>
    1108       <p id="rfc.section.9.2.2.p.1">The request has been fulfilled and resulted in a new resource being created. The newly created resource can be referenced
     1112      <h3 id="rfc.section.8.2.2"><a href="#rfc.section.8.2.2">8.2.2</a>&nbsp;<a id="status.201" href="#status.201">201 Created</a></h3>
     1113      <p id="rfc.section.8.2.2.p.1">The request has been fulfilled and resulted in a new resource being created. The newly created resource can be referenced
    11091114         by the URI(s) returned in the entity of the response, with the most specific URI for the resource given by a Location header
    11101115         field. The response <em class="bcp14">SHOULD</em> include an entity containing a list of resource characteristics and location(s) from which the user or user agent can choose
     
    11121117         server <em class="bcp14">MUST</em> create the resource before returning the 201 status code. If the action cannot be carried out immediately, the server <em class="bcp14">SHOULD</em> respond with 202 (Accepted) response instead.
    11131118      </p>
    1114       <p id="rfc.section.9.2.2.p.2">A 201 response <em class="bcp14">MAY</em> contain an ETag response header field indicating the current value of the entity tag for the requested variant just created,
    1115          see <a href="p4-conditional.html#header.etag" title="ETag">Section 7.1</a> of <a href="#Part4" id="rfc.xref.Part4.11"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>.
     1119      <p id="rfc.section.8.2.2.p.2">A 201 response <em class="bcp14">MAY</em> contain an ETag response header field indicating the current value of the entity tag for the requested variant just created,
     1120         see <a href="p4-conditional.html#header.etag" title="ETag">Section 6.1</a> of <a href="#Part4" id="rfc.xref.Part4.11"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>.
    11161121      </p>
    11171122      <div id="rfc.iref.29"></div>
    11181123      <div id="rfc.iref.s.6"></div>
    1119       <h3 id="rfc.section.9.2.3"><a href="#rfc.section.9.2.3">9.2.3</a>&nbsp;<a id="status.202" href="#status.202">202 Accepted</a></h3>
    1120       <p id="rfc.section.9.2.3.p.1">The request has been accepted for processing, but the processing has not been completed. The request might or might not eventually
     1124      <h3 id="rfc.section.8.2.3"><a href="#rfc.section.8.2.3">8.2.3</a>&nbsp;<a id="status.202" href="#status.202">202 Accepted</a></h3>
     1125      <p id="rfc.section.8.2.3.p.1">The request has been accepted for processing, but the processing has not been completed. The request might or might not eventually
    11211126         be acted upon, as it might be disallowed when processing actually takes place. There is no facility for re-sending a status
    11221127         code from an asynchronous operation such as this.
    11231128      </p>
    1124       <p id="rfc.section.9.2.3.p.2">The 202 response is intentionally non-committal. Its purpose is to allow a server to accept a request for some other process
     1129      <p id="rfc.section.8.2.3.p.2">The 202 response is intentionally non-committal. Its purpose is to allow a server to accept a request for some other process
    11251130         (perhaps a batch-oriented process that is only run once per day) without requiring that the user agent's connection to the
    11261131         server persist until the process is completed. The entity returned with this response <em class="bcp14">SHOULD</em> include an indication of the request's current status and either a pointer to a status monitor or some estimate of when the
     
    11291134      <div id="rfc.iref.30"></div>
    11301135      <div id="rfc.iref.s.7"></div>
    1131       <h3 id="rfc.section.9.2.4"><a href="#rfc.section.9.2.4">9.2.4</a>&nbsp;<a id="status.203" href="#status.203">203 Non-Authoritative Information</a></h3>
    1132       <p id="rfc.section.9.2.4.p.1">The returned metainformation in the entity-header is not the definitive set as available from the origin server, but is gathered
     1136      <h3 id="rfc.section.8.2.4"><a href="#rfc.section.8.2.4">8.2.4</a>&nbsp;<a id="status.203" href="#status.203">203 Non-Authoritative Information</a></h3>
     1137      <p id="rfc.section.8.2.4.p.1">The returned metainformation in the entity-header is not the definitive set as available from the origin server, but is gathered
    11331138         from a local or a third-party copy. The set presented <em class="bcp14">MAY</em> be a subset or superset of the original version. For example, including local annotation information about the resource might
    11341139         result in a superset of the metainformation known by the origin server. Use of this response code is not required and is only
     
    11371142      <div id="rfc.iref.31"></div>
    11381143      <div id="rfc.iref.s.8"></div>
    1139       <h3 id="rfc.section.9.2.5"><a href="#rfc.section.9.2.5">9.2.5</a>&nbsp;<a id="status.204" href="#status.204">204 No Content</a></h3>
    1140       <p id="rfc.section.9.2.5.p.1">The server has fulfilled the request but does not need to return an entity-body, and might want to return updated metainformation.
     1144      <h3 id="rfc.section.8.2.5"><a href="#rfc.section.8.2.5">8.2.5</a>&nbsp;<a id="status.204" href="#status.204">204 No Content</a></h3>
     1145      <p id="rfc.section.8.2.5.p.1">The server has fulfilled the request but does not need to return an entity-body, and might want to return updated metainformation.
    11411146         The response <em class="bcp14">MAY</em> include new or updated metainformation in the form of entity-headers, which if present <em class="bcp14">SHOULD</em> be associated with the requested variant.
    11421147      </p>
    1143       <p id="rfc.section.9.2.5.p.2">If the client is a user agent, it <em class="bcp14">SHOULD NOT</em> change its document view from that which caused the request to be sent. This response is primarily intended to allow input
     1148      <p id="rfc.section.8.2.5.p.2">If the client is a user agent, it <em class="bcp14">SHOULD NOT</em> change its document view from that which caused the request to be sent. This response is primarily intended to allow input
    11441149         for actions to take place without causing a change to the user agent's active document view, although any new or updated metainformation <em class="bcp14">SHOULD</em> be applied to the document currently in the user agent's active view.
    11451150      </p>
    1146       <p id="rfc.section.9.2.5.p.3">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.
     1151      <p id="rfc.section.8.2.5.p.3">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.
    11471152      </p>
    11481153      <div id="rfc.iref.32"></div>
    11491154      <div id="rfc.iref.s.9"></div>
    1150       <h3 id="rfc.section.9.2.6"><a href="#rfc.section.9.2.6">9.2.6</a>&nbsp;<a id="status.205" href="#status.205">205 Reset Content</a></h3>
    1151       <p id="rfc.section.9.2.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
     1155      <h3 id="rfc.section.8.2.6"><a href="#rfc.section.8.2.6">8.2.6</a>&nbsp;<a id="status.205" href="#status.205">205 Reset Content</a></h3>
     1156      <p id="rfc.section.8.2.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
    11521157         to take place via user input, followed by a clearing of the form in which the input is given so that the user can easily initiate
    11531158         another input action. The response <em class="bcp14">MUST NOT</em> include an entity.
     
    11551160      <div id="rfc.iref.33"></div>
    11561161      <div id="rfc.iref.s.10"></div>
    1157       <h3 id="rfc.section.9.2.7"><a href="#rfc.section.9.2.7">9.2.7</a>&nbsp;<a id="status.206" href="#status.206">206 Partial Content</a></h3>
    1158       <p id="rfc.section.9.2.7.p.1">The server has fulfilled the partial GET request for the resource and the enclosed entity is a partial representation as defined
     1162      <h3 id="rfc.section.8.2.7"><a href="#rfc.section.8.2.7">8.2.7</a>&nbsp;<a id="status.206" href="#status.206">206 Partial Content</a></h3>
     1163      <p id="rfc.section.8.2.7.p.1">The server has fulfilled the partial GET request for the resource and the enclosed entity is a partial representation as defined
    11591164         in <a href="#Part5" id="rfc.xref.Part5.9"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>.
    11601165      </p>
    1161       <h2 id="rfc.section.9.3"><a href="#rfc.section.9.3">9.3</a>&nbsp;<a id="status.3xx" href="#status.3xx">Redirection 3xx</a></h2>
    1162       <p id="rfc.section.9.3.p.1">This class of status code indicates that further action needs to be taken by the user agent in order to fulfill the request.
     1166      <h2 id="rfc.section.8.3"><a href="#rfc.section.8.3">8.3</a>&nbsp;<a id="status.3xx" href="#status.3xx">Redirection 3xx</a></h2>
     1167      <p id="rfc.section.8.3.p.1">This class of status code indicates that further action needs to be taken by the user agent in order to fulfill the request.
    11631168         The action required <em class="bcp14">MAY</em> be carried out by the user agent without interaction with the user if and only if the method used in the second request is
    11641169         GET or HEAD. A client <em class="bcp14">SHOULD</em> detect infinite redirection loops, since such loops generate network traffic for each redirection.
     
    11711176      <div id="rfc.iref.34"></div>
    11721177      <div id="rfc.iref.s.11"></div>
    1173       <h3 id="rfc.section.9.3.1"><a href="#rfc.section.9.3.1">9.3.1</a>&nbsp;<a id="status.300" href="#status.300">300 Multiple Choices</a></h3>
    1174       <p id="rfc.section.9.3.1.p.1">The requested resource corresponds to any one of a set of representations, each with its own specific location, and agent-driven
    1175          negotiation information (<a href="p3-payload.html#content.negotiation" title="Content Negotiation">Section 5</a> of <a href="#Part3" id="rfc.xref.Part3.10"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>) is being provided so that the user (or user agent) can select a preferred representation and redirect its request to that
     1178      <h3 id="rfc.section.8.3.1"><a href="#rfc.section.8.3.1">8.3.1</a>&nbsp;<a id="status.300" href="#status.300">300 Multiple Choices</a></h3>
     1179      <p id="rfc.section.8.3.1.p.1">The requested resource corresponds to any one of a set of representations, each with its own specific location, and agent-driven
     1180         negotiation information (<a href="p3-payload.html#content.negotiation" title="Content Negotiation">Section 4</a> of <a href="#Part3" id="rfc.xref.Part3.10"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>) is being provided so that the user (or user agent) can select a preferred representation and redirect its request to that
    11761181         location.
    11771182      </p>
    1178       <p id="rfc.section.9.3.1.p.2">Unless it was a HEAD request, the response <em class="bcp14">SHOULD</em> include an entity containing a list of resource characteristics and location(s) from which the user or user agent can choose
     1183      <p id="rfc.section.8.3.1.p.2">Unless it was a HEAD request, the response <em class="bcp14">SHOULD</em> include an entity containing a list of resource characteristics and location(s) from which the user or user agent can choose
    11791184         the one most appropriate. The entity format is specified by the media type given in the Content-Type header field. Depending
    11801185         upon the format and the capabilities of the user agent, selection of the most appropriate choice <em class="bcp14">MAY</em> be performed automatically. However, this specification does not define any standard for such automatic selection.
    11811186      </p>
    1182       <p id="rfc.section.9.3.1.p.3">If the server has a preferred choice of representation, it <em class="bcp14">SHOULD</em> include the specific URI for that representation in the Location field; user agents <em class="bcp14">MAY</em> use the Location field value for automatic redirection. This response is cacheable unless indicated otherwise.
     1187      <p id="rfc.section.8.3.1.p.3">If the server has a preferred choice of representation, it <em class="bcp14">SHOULD</em> include the specific URI for that representation in the Location field; user agents <em class="bcp14">MAY</em> use the Location field value for automatic redirection. This response is cacheable unless indicated otherwise.
    11831188      </p>
    11841189      <div id="rfc.iref.35"></div>
    11851190      <div id="rfc.iref.s.12"></div>
    1186       <h3 id="rfc.section.9.3.2"><a href="#rfc.section.9.3.2">9.3.2</a>&nbsp;<a id="status.301" href="#status.301">301 Moved Permanently</a></h3>
    1187       <p id="rfc.section.9.3.2.p.1">The requested 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 request-target
     1191      <h3 id="rfc.section.8.3.2"><a href="#rfc.section.8.3.2">8.3.2</a>&nbsp;<a id="status.301" href="#status.301">301 Moved Permanently</a></h3>
     1192      <p id="rfc.section.8.3.2.p.1">The requested 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 request-target
    11881193         to one or more of the new references returned by the server, where possible. This response is cacheable unless indicated otherwise.
    11891194      </p>
    1190       <p id="rfc.section.9.3.2.p.2">The new permanent URI <em class="bcp14">SHOULD</em> be given by the Location field in the response. Unless the request method was HEAD, the entity of the response <em class="bcp14">SHOULD</em> contain a short hypertext note with a hyperlink to the new URI(s).
    1191       </p>
    1192       <p id="rfc.section.9.3.2.p.3">If the 301 status code is received in response to a request method that is known to be "safe", as defined in <a href="#safe.methods" title="Safe Methods">Section&nbsp;8.1.1</a>, then the request <em class="bcp14">MAY</em> be automatically redirected by the user agent without confirmation. Otherwise, the user agent <em class="bcp14">MUST NOT</em> automatically redirect the request unless it can be confirmed by the user, since this might change the conditions under which
     1195      <p id="rfc.section.8.3.2.p.2">The new permanent URI <em class="bcp14">SHOULD</em> be given by the Location field in the response. Unless the request method was HEAD, the entity of the response <em class="bcp14">SHOULD</em> contain a short hypertext note with a hyperlink to the new URI(s).
     1196      </p>
     1197      <p id="rfc.section.8.3.2.p.3">If the 301 status code is received in response to a request method that is known to be "safe", as defined in <a href="#safe.methods" title="Safe Methods">Section&nbsp;7.1.1</a>, then the request <em class="bcp14">MAY</em> be automatically redirected by the user agent without confirmation. Otherwise, the user agent <em class="bcp14">MUST NOT</em> automatically redirect the request unless it can be confirmed by the user, since this might change the conditions under which
    11931198         the request was issued.
    11941199      </p>
     
    12001205      <div id="rfc.iref.36"></div>
    12011206      <div id="rfc.iref.s.13"></div>
    1202       <h3 id="rfc.section.9.3.3"><a href="#rfc.section.9.3.3">9.3.3</a>&nbsp;<a id="status.302" href="#status.302">302 Found</a></h3>
    1203       <p id="rfc.section.9.3.3.p.1">The requested resource resides temporarily under a different URI. Since the redirection might be altered on occasion, the
     1207      <h3 id="rfc.section.8.3.3"><a href="#rfc.section.8.3.3">8.3.3</a>&nbsp;<a id="status.302" href="#status.302">302 Found</a></h3>
     1208      <p id="rfc.section.8.3.3.p.1">The requested resource resides temporarily under a different URI. Since the redirection might be altered on occasion, the
    12041209         client <em class="bcp14">SHOULD</em> continue to use the request-target for future requests. This response is only cacheable if indicated by a Cache-Control or
    12051210         Expires header field.
    12061211      </p>
    1207       <p id="rfc.section.9.3.3.p.2">The temporary URI <em class="bcp14">SHOULD</em> be given by the Location field in the response. Unless the request method was HEAD, the entity of the response <em class="bcp14">SHOULD</em> contain a short hypertext note with a hyperlink to the new URI(s).
    1208       </p>
    1209       <p id="rfc.section.9.3.3.p.3">If the 302 status code is received in response to a request method that is known to be "safe", as defined in <a href="#safe.methods" title="Safe Methods">Section&nbsp;8.1.1</a>, then the request <em class="bcp14">MAY</em> be automatically redirected by the user agent without confirmation. Otherwise, the user agent <em class="bcp14">MUST NOT</em> automatically redirect the request unless it can be confirmed by the user, since this might change the conditions under which
     1212      <p id="rfc.section.8.3.3.p.2">The temporary URI <em class="bcp14">SHOULD</em> be given by the Location field in the response. Unless the request method was HEAD, the entity of the response <em class="bcp14">SHOULD</em> contain a short hypertext note with a hyperlink to the new URI(s).
     1213      </p>
     1214      <p id="rfc.section.8.3.3.p.3">If the 302 status code is received in response to a request method that is known to be "safe", as defined in <a href="#safe.methods" title="Safe Methods">Section&nbsp;7.1.1</a>, then the request <em class="bcp14">MAY</em> be automatically redirected by the user agent without confirmation. Otherwise, the user agent <em class="bcp14">MUST NOT</em> automatically redirect the request unless it can be confirmed by the user, since this might change the conditions under which
    12101215         the request was issued.
    12111216      </p>
     
    12191224      <div id="rfc.iref.37"></div>
    12201225      <div id="rfc.iref.s.14"></div>
    1221       <h3 id="rfc.section.9.3.4"><a href="#rfc.section.9.3.4">9.3.4</a>&nbsp;<a id="status.303" href="#status.303">303 See Other</a></h3>
    1222       <p id="rfc.section.9.3.4.p.1">The server directs the user agent to a different resource, indicated by a URI in the Location header field, that provides
     1226      <h3 id="rfc.section.8.3.4"><a href="#rfc.section.8.3.4">8.3.4</a>&nbsp;<a id="status.303" href="#status.303">303 See Other</a></h3>
     1227      <p id="rfc.section.8.3.4.p.1">The server directs the user agent to a different resource, indicated by a URI in the Location header field, that provides
    12231228         an indirect response to the original request. The user agent <em class="bcp14">MAY</em> perform a GET request on the URI in the Location field in order to obtain a representation corresponding to the response,
    12241229         be redirected again, or end with an error status. The Location URI is not a substitute reference for the originally requested
    12251230         resource.
    12261231      </p>
    1227       <p id="rfc.section.9.3.4.p.2">The 303 status is generally applicable to any HTTP method. It is primarily used to allow the output of a POST action to redirect
     1232      <p id="rfc.section.8.3.4.p.2">The 303 status is generally applicable to any HTTP method. It is primarily used to allow the output of a POST action to redirect
    12281233         the user agent to a selected resource, since doing so provides the information corresponding to the POST response in a form
    12291234         that can be separately identified, bookmarked, and cached independent of the original request.
    12301235      </p>
    1231       <p id="rfc.section.9.3.4.p.3">A 303 response to a GET request indicates that the requested resource does not have a representation of its own that can be
     1236      <p id="rfc.section.8.3.4.p.3">A 303 response to a GET request indicates that the requested resource does not have a representation of its own that can be
    12321237         transferred by the server over HTTP. The Location URI indicates a resource that is descriptive of the requested resource such
    12331238         that the follow-on representation may be useful without implying that it adequately represents the previously requested resource.
     
    12351240         description are outside the scope of HTTP and thus entirely determined by the resource owner(s).
    12361241      </p>
    1237       <p id="rfc.section.9.3.4.p.4">A 303 response <em class="bcp14">SHOULD NOT</em> be cached unless it is indicated as cacheable by Cache-Control or Expires header fields. Except for responses to a HEAD request,
     1242      <p id="rfc.section.8.3.4.p.4">A 303 response <em class="bcp14">SHOULD NOT</em> be cached unless it is indicated as cacheable by Cache-Control or Expires header fields. Except for responses to a HEAD request,
    12381243         the entity of a 303 response <em class="bcp14">SHOULD</em> contain a short hypertext note with a hyperlink to the Location URI.
    12391244      </p>
    12401245      <div id="rfc.iref.38"></div>
    12411246      <div id="rfc.iref.s.15"></div>
    1242       <h3 id="rfc.section.9.3.5"><a href="#rfc.section.9.3.5">9.3.5</a>&nbsp;<a id="status.304" href="#status.304">304 Not Modified</a></h3>
    1243       <p id="rfc.section.9.3.5.p.1">The response to the request has not been modified since the conditions indicated by the client's conditional GET request,
     1247      <h3 id="rfc.section.8.3.5"><a href="#rfc.section.8.3.5">8.3.5</a>&nbsp;<a id="status.304" href="#status.304">304 Not Modified</a></h3>
     1248      <p id="rfc.section.8.3.5.p.1">The response to the request has not been modified since the conditions indicated by the client's conditional GET request,
    12441249         as defined in <a href="#Part4" id="rfc.xref.Part4.12"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>.
    12451250      </p>
    12461251      <div id="rfc.iref.39"></div>
    12471252      <div id="rfc.iref.s.16"></div>
    1248       <h3 id="rfc.section.9.3.6"><a href="#rfc.section.9.3.6">9.3.6</a>&nbsp;<a id="status.305" href="#status.305">305 Use Proxy</a></h3>
    1249       <p id="rfc.section.9.3.6.p.1">The 305 status was defined in a previous version of this specification (see <a href="#changes.from.rfc.2616" title="Changes from RFC 2616">Appendix&nbsp;A.2</a>), and is now deprecated.
     1253      <h3 id="rfc.section.8.3.6"><a href="#rfc.section.8.3.6">8.3.6</a>&nbsp;<a id="status.305" href="#status.305">305 Use Proxy</a></h3>
     1254      <p id="rfc.section.8.3.6.p.1">The 305 status was defined in a previous version of this specification (see <a href="#changes.from.rfc.2616" title="Changes from RFC 2616">Appendix&nbsp;A.2</a>), and is now deprecated.
    12501255      </p>
    12511256      <div id="rfc.iref.40"></div>
    12521257      <div id="rfc.iref.s.17"></div>
    1253       <h3 id="rfc.section.9.3.7"><a href="#rfc.section.9.3.7">9.3.7</a>&nbsp;<a id="status.306" href="#status.306">306 (Unused)</a></h3>
    1254       <p id="rfc.section.9.3.7.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>
     1258      <h3 id="rfc.section.8.3.7"><a href="#rfc.section.8.3.7">8.3.7</a>&nbsp;<a id="status.306" href="#status.306">306 (Unused)</a></h3>
     1259      <p id="rfc.section.8.3.7.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>
    12551260      <div id="rfc.iref.41"></div>
    12561261      <div id="rfc.iref.s.18"></div>
    1257       <h3 id="rfc.section.9.3.8"><a href="#rfc.section.9.3.8">9.3.8</a>&nbsp;<a id="status.307" href="#status.307">307 Temporary Redirect</a></h3>
    1258       <p id="rfc.section.9.3.8.p.1">The requested resource resides temporarily under a different URI. Since the redirection <em class="bcp14">MAY</em> be altered on occasion, the client <em class="bcp14">SHOULD</em> continue to use the request-target for future requests. This response is only cacheable if indicated by a Cache-Control or
     1262      <h3 id="rfc.section.8.3.8"><a href="#rfc.section.8.3.8">8.3.8</a>&nbsp;<a id="status.307" href="#status.307">307 Temporary Redirect</a></h3>
     1263      <p id="rfc.section.8.3.8.p.1">The requested resource resides temporarily under a different URI. Since the redirection <em class="bcp14">MAY</em> be altered on occasion, the client <em class="bcp14">SHOULD</em> continue to use the request-target for future requests. This response is only cacheable if indicated by a Cache-Control or
    12591264         Expires header field.
    12601265      </p>
    1261       <p id="rfc.section.9.3.8.p.2">The temporary URI <em class="bcp14">SHOULD</em> be given by the Location field in the response. Unless the request method was HEAD, the entity of the response <em class="bcp14">SHOULD</em> contain a short hypertext note with a hyperlink to the new URI(s) , since many pre-HTTP/1.1 user agents do not understand
     1266      <p id="rfc.section.8.3.8.p.2">The temporary URI <em class="bcp14">SHOULD</em> be given by the Location field in the response. Unless the request method was HEAD, the entity of the response <em class="bcp14">SHOULD</em> contain a short hypertext note with a hyperlink to the new URI(s) , since many pre-HTTP/1.1 user agents do not understand
    12621267         the 307 status. Therefore, the note <em class="bcp14">SHOULD</em> contain the information necessary for a user to repeat the original request on the new URI.
    12631268      </p>
    1264       <p id="rfc.section.9.3.8.p.3">If the 307 status code is received in response to a request method that is known to be "safe", as defined in <a href="#safe.methods" title="Safe Methods">Section&nbsp;8.1.1</a>, then the request <em class="bcp14">MAY</em> be automatically redirected by the user agent without confirmation. Otherwise, the user agent <em class="bcp14">MUST NOT</em> automatically redirect the request unless it can be confirmed by the user, since this might change the conditions under which
     1269      <p id="rfc.section.8.3.8.p.3">If the 307 status code is received in response to a request method that is known to be "safe", as defined in <a href="#safe.methods" title="Safe Methods">Section&nbsp;7.1.1</a>, then the request <em class="bcp14">MAY</em> be automatically redirected by the user agent without confirmation. Otherwise, the user agent <em class="bcp14">MUST NOT</em> automatically redirect the request unless it can be confirmed by the user, since this might change the conditions under which
    12651270         the request was issued.
    12661271      </p>
    1267       <h2 id="rfc.section.9.4"><a href="#rfc.section.9.4">9.4</a>&nbsp;<a id="status.4xx" href="#status.4xx">Client Error 4xx</a></h2>
    1268       <p id="rfc.section.9.4.p.1">The 4xx class of status code is intended for cases in which the client seems to have erred. Except when responding to a HEAD
     1272      <h2 id="rfc.section.8.4"><a href="#rfc.section.8.4">8.4</a>&nbsp;<a id="status.4xx" href="#status.4xx">Client Error 4xx</a></h2>
     1273      <p id="rfc.section.8.4.p.1">The 4xx class of status code is intended for cases in which the client seems to have erred. Except when responding to a HEAD
    12691274         request, the server <em class="bcp14">SHOULD</em> include an entity containing an explanation of the error situation, and whether it is a temporary or permanent condition.
    12701275         These status codes are applicable to any request method. User agents <em class="bcp14">SHOULD</em> display any included entity to the user.
    12711276      </p>
    1272       <p id="rfc.section.9.4.p.2">If the client is sending data, a server implementation using TCP <em class="bcp14">SHOULD</em> be careful to ensure that the client acknowledges receipt of the packet(s) containing the response, before the server closes
     1277      <p id="rfc.section.8.4.p.2">If the client is sending data, a server implementation using TCP <em class="bcp14">SHOULD</em> be careful to ensure that the client acknowledges receipt of the packet(s) containing the response, before the server closes
    12731278         the input connection. If the client continues sending data to the server after the close, the server's TCP stack will send
    12741279         a reset packet to the client, which may erase the client's unacknowledged input buffers before they can be read and interpreted
     
    12771282      <div id="rfc.iref.42"></div>
    12781283      <div id="rfc.iref.s.19"></div>
    1279       <h3 id="rfc.section.9.4.1"><a href="#rfc.section.9.4.1">9.4.1</a>&nbsp;<a id="status.400" href="#status.400">400 Bad Request</a></h3>
    1280       <p id="rfc.section.9.4.1.p.1">The request could not be understood by the server due to malformed syntax. The client <em class="bcp14">SHOULD NOT</em> repeat the request without modifications.
     1284      <h3 id="rfc.section.8.4.1"><a href="#rfc.section.8.4.1">8.4.1</a>&nbsp;<a id="status.400" href="#status.400">400 Bad Request</a></h3>
     1285      <p id="rfc.section.8.4.1.p.1">The request could not be understood by the server due to malformed syntax. The client <em class="bcp14">SHOULD NOT</em> repeat the request without modifications.
    12811286      </p>
    12821287      <div id="rfc.iref.43"></div>
    12831288      <div id="rfc.iref.s.20"></div>
    1284       <h3 id="rfc.section.9.4.2"><a href="#rfc.section.9.4.2">9.4.2</a>&nbsp;<a id="status.401" href="#status.401">401 Unauthorized</a></h3>
    1285       <p id="rfc.section.9.4.2.p.1">The request requires user authentication (see <a href="#Part7" id="rfc.xref.Part7.9"><cite title="HTTP/1.1, part 7: Authentication">[Part7]</cite></a>).
     1289      <h3 id="rfc.section.8.4.2"><a href="#rfc.section.8.4.2">8.4.2</a>&nbsp;<a id="status.401" href="#status.401">401 Unauthorized</a></h3>
     1290      <p id="rfc.section.8.4.2.p.1">The request requires user authentication (see <a href="#Part7" id="rfc.xref.Part7.9"><cite title="HTTP/1.1, part 7: Authentication">[Part7]</cite></a>).
    12861291      </p>
    12871292      <div id="rfc.iref.44"></div>
    12881293      <div id="rfc.iref.s.21"></div>
    1289       <h3 id="rfc.section.9.4.3"><a href="#rfc.section.9.4.3">9.4.3</a>&nbsp;<a id="status.402" href="#status.402">402 Payment Required</a></h3>
    1290       <p id="rfc.section.9.4.3.p.1">This code is reserved for future use.</p>
     1294      <h3 id="rfc.section.8.4.3"><a href="#rfc.section.8.4.3">8.4.3</a>&nbsp;<a id="status.402" href="#status.402">402 Payment Required</a></h3>
     1295      <p id="rfc.section.8.4.3.p.1">This code is reserved for future use.</p>
    12911296      <div id="rfc.iref.45"></div>
    12921297      <div id="rfc.iref.s.22"></div>
    1293       <h3 id="rfc.section.9.4.4"><a href="#rfc.section.9.4.4">9.4.4</a>&nbsp;<a id="status.403" href="#status.403">403 Forbidden</a></h3>
    1294       <p id="rfc.section.9.4.4.p.1">The server understood the request, but is refusing to fulfill it. Authorization will not help and the request <em class="bcp14">SHOULD NOT</em> be repeated. If the request method was not HEAD and the server wishes to make public why the request has not been fulfilled,
     1298      <h3 id="rfc.section.8.4.4"><a href="#rfc.section.8.4.4">8.4.4</a>&nbsp;<a id="status.403" href="#status.403">403 Forbidden</a></h3>
     1299      <p id="rfc.section.8.4.4.p.1">The server understood the request, but is refusing to fulfill it. Authorization will not help and the request <em class="bcp14">SHOULD NOT</em> be repeated. If the request method was not HEAD and the server wishes to make public why the request has not been fulfilled,
    12951300         it <em class="bcp14">SHOULD</em> describe the reason for the refusal in the entity. If the server does not wish to make this information available to the client,
    12961301         the status code 404 (Not Found) can be used instead.
     
    12981303      <div id="rfc.iref.46"></div>
    12991304      <div id="rfc.iref.s.23"></div>
    1300       <h3 id="rfc.section.9.4.5"><a href="#rfc.section.9.4.5">9.4.5</a>&nbsp;<a id="status.404" href="#status.404">404 Not Found</a></h3>
    1301       <p id="rfc.section.9.4.5.p.1">The server has not found anything matching the request-target. No indication is given of whether the condition is temporary
     1305      <h3 id="rfc.section.8.4.5"><a href="#rfc.section.8.4.5">8.4.5</a>&nbsp;<a id="status.404" href="#status.404">404 Not Found</a></h3>
     1306      <p id="rfc.section.8.4.5.p.1">The server has not found anything matching the request-target. No indication is given of whether the condition is temporary
    13021307         or permanent. The 410 (Gone) status code <em class="bcp14">SHOULD</em> be used if the server knows, through some internally configurable mechanism, that an old resource is permanently unavailable
    13031308         and has no forwarding address. This status code is commonly used when the server does not wish to reveal exactly why the request
     
    13061311      <div id="rfc.iref.47"></div>
    13071312      <div id="rfc.iref.s.24"></div>
    1308       <h3 id="rfc.section.9.4.6"><a href="#rfc.section.9.4.6">9.4.6</a>&nbsp;<a id="status.405" href="#status.405">405 Method Not Allowed</a></h3>
    1309       <p id="rfc.section.9.4.6.p.1">The method specified in the Request-Line is not allowed for the resource identified by the request-target. The response <em class="bcp14">MUST</em> include an Allow header containing a list of valid methods for the requested resource.
     1313      <h3 id="rfc.section.8.4.6"><a href="#rfc.section.8.4.6">8.4.6</a>&nbsp;<a id="status.405" href="#status.405">405 Method Not Allowed</a></h3>
     1314      <p id="rfc.section.8.4.6.p.1">The method specified in the Request-Line is not allowed for the resource identified by the request-target. The response <em class="bcp14">MUST</em> include an Allow header containing a list of valid methods for the requested resource.
    13101315      </p>
    13111316      <div id="rfc.iref.48"></div>
    13121317      <div id="rfc.iref.s.25"></div>
    1313       <h3 id="rfc.section.9.4.7"><a href="#rfc.section.9.4.7">9.4.7</a>&nbsp;<a id="status.406" href="#status.406">406 Not Acceptable</a></h3>
    1314       <p id="rfc.section.9.4.7.p.1">The resource identified by the request is only capable of generating response entities which have content characteristics
     1318      <h3 id="rfc.section.8.4.7"><a href="#rfc.section.8.4.7">8.4.7</a>&nbsp;<a id="status.406" href="#status.406">406 Not Acceptable</a></h3>
     1319      <p id="rfc.section.8.4.7.p.1">The resource identified by the request is only capable of generating response entities which have content characteristics
    13151320         not acceptable according to the accept headers sent in the request.
    13161321      </p>
    1317       <p id="rfc.section.9.4.7.p.2">Unless it was a HEAD request, the response <em class="bcp14">SHOULD</em> include an entity containing a list of available entity characteristics and location(s) from which the user or user agent
     1322      <p id="rfc.section.8.4.7.p.2">Unless it was a HEAD request, the response <em class="bcp14">SHOULD</em> include an entity containing a list of available entity characteristics and location(s) from which the user or user agent
    13181323         can choose the one most appropriate. The entity format is specified by the media type given in the Content-Type header field.
    13191324         Depending upon the format and the capabilities of the user agent, selection of the most appropriate choice <em class="bcp14">MAY</em> be performed automatically. However, this specification does not define any standard for such automatic selection.
     
    13251330         </dd>
    13261331      </dl>
    1327       <p id="rfc.section.9.4.7.p.3">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.
     1332      <p id="rfc.section.8.4.7.p.3">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.
    13281333      </p>
    13291334      <div id="rfc.iref.49"></div>
    13301335      <div id="rfc.iref.s.26"></div>
    1331       <h3 id="rfc.section.9.4.8"><a href="#rfc.section.9.4.8">9.4.8</a>&nbsp;<a id="status.407" href="#status.407">407 Proxy Authentication Required</a></h3>
    1332       <p id="rfc.section.9.4.8.p.1">This code is similar to 401 (Unauthorized), but indicates that the client must first authenticate itself with the proxy (see <a href="#Part7" id="rfc.xref.Part7.10"><cite title="HTTP/1.1, part 7: Authentication">[Part7]</cite></a>).
     1336      <h3 id="rfc.section.8.4.8"><a href="#rfc.section.8.4.8">8.4.8</a>&nbsp;<a id="status.407" href="#status.407">407 Proxy Authentication Required</a></h3>
     1337      <p id="rfc.section.8.4.8.p.1">This code is similar to 401 (Unauthorized), but indicates that the client must first authenticate itself with the proxy (see <a href="#Part7" id="rfc.xref.Part7.10"><cite title="HTTP/1.1, part 7: Authentication">[Part7]</cite></a>).
    13331338      </p>
    13341339      <div id="rfc.iref.50"></div>
    13351340      <div id="rfc.iref.s.27"></div>
    1336       <h3 id="rfc.section.9.4.9"><a href="#rfc.section.9.4.9">9.4.9</a>&nbsp;<a id="status.408" href="#status.408">408 Request Timeout</a></h3>
    1337       <p id="rfc.section.9.4.9.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.
     1341      <h3 id="rfc.section.8.4.9"><a href="#rfc.section.8.4.9">8.4.9</a>&nbsp;<a id="status.408" href="#status.408">408 Request Timeout</a></h3>
     1342      <p id="rfc.section.8.4.9.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.
    13381343      </p>
    13391344      <div id="rfc.iref.51"></div>
    13401345      <div id="rfc.iref.s.28"></div>
    1341       <h3 id="rfc.section.9.4.10"><a href="#rfc.section.9.4.10">9.4.10</a>&nbsp;<a id="status.409" href="#status.409">409 Conflict</a></h3>
    1342       <p id="rfc.section.9.4.10.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
     1346      <h3 id="rfc.section.8.4.10"><a href="#rfc.section.8.4.10">8.4.10</a>&nbsp;<a id="status.409" href="#status.409">409 Conflict</a></h3>
     1347      <p id="rfc.section.8.4.10.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
    13431348         situations where it is expected that the user might be able to resolve the conflict and resubmit the request. The response
    13441349         body <em class="bcp14">SHOULD</em> include enough information for the user to recognize the source of the conflict. Ideally, the response entity would include
    13451350         enough information for the user or user agent to fix the problem; however, that might not be possible and is not required.
    13461351      </p>
    1347       <p id="rfc.section.9.4.10.p.2">Conflicts are most likely to occur in response to a PUT request. For example, if versioning were being used and the entity
     1352      <p id="rfc.section.8.4.10.p.2">Conflicts are most likely to occur in response to a PUT request. For example, if versioning were being used and the entity
    13481353         being PUT included changes to a resource which conflict with those made by an earlier (third-party) request, the server might
    13491354         use the 409 response to indicate that it can't complete the request. In this case, the response entity would likely contain
     
    13521357      <div id="rfc.iref.52"></div>
    13531358      <div id="rfc.iref.s.29"></div>
    1354       <h3 id="rfc.section.9.4.11"><a href="#rfc.section.9.4.11">9.4.11</a>&nbsp;<a id="status.410" href="#status.410">410 Gone</a></h3>
    1355       <p id="rfc.section.9.4.11.p.1">The requested resource is no longer available at the server and no forwarding address is known. This condition is expected
     1359      <h3 id="rfc.section.8.4.11"><a href="#rfc.section.8.4.11">8.4.11</a>&nbsp;<a id="status.410" href="#status.410">410 Gone</a></h3>
     1360      <p id="rfc.section.8.4.11.p.1">The requested resource is no longer available at the server and no forwarding address is known. This condition is expected
    13561361         to be considered permanent. Clients with link editing capabilities <em class="bcp14">SHOULD</em> delete references to the request-target after user approval. If the server does not know, or has no facility to determine,
    13571362         whether or not the condition is permanent, the status code 404 (Not Found) <em class="bcp14">SHOULD</em> be used instead. This response is cacheable unless indicated otherwise.
    13581363      </p>
    1359       <p id="rfc.section.9.4.11.p.2">The 410 response is primarily intended to assist the task of web maintenance by notifying the recipient that the resource
     1364      <p id="rfc.section.8.4.11.p.2">The 410 response is primarily intended to assist the task of web maintenance by notifying the recipient that the resource
    13601365         is intentionally unavailable and that the server owners desire that remote links to that resource be removed. Such an event
    13611366         is common for limited-time, promotional services and for resources belonging to individuals no longer working at the server's
     
    13651370      <div id="rfc.iref.53"></div>
    13661371      <div id="rfc.iref.s.30"></div>
    1367       <h3 id="rfc.section.9.4.12"><a href="#rfc.section.9.4.12">9.4.12</a>&nbsp;<a id="status.411" href="#status.411">411 Length Required</a></h3>
    1368       <p id="rfc.section.9.4.12.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
     1372      <h3 id="rfc.section.8.4.12"><a href="#rfc.section.8.4.12">8.4.12</a>&nbsp;<a id="status.411" href="#status.411">411 Length Required</a></h3>
     1373      <p id="rfc.section.8.4.12.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
    13691374         message.
    13701375      </p>
    13711376      <div id="rfc.iref.54"></div>
    13721377      <div id="rfc.iref.s.31"></div>
    1373       <h3 id="rfc.section.9.4.13"><a href="#rfc.section.9.4.13">9.4.13</a>&nbsp;<a id="status.412" href="#status.412">412 Precondition Failed</a></h3>
    1374       <p id="rfc.section.9.4.13.p.1">The precondition given in one or more of the request-header fields evaluated to false when it was tested on the server, as
     1378      <h3 id="rfc.section.8.4.13"><a href="#rfc.section.8.4.13">8.4.13</a>&nbsp;<a id="status.412" href="#status.412">412 Precondition Failed</a></h3>
     1379      <p id="rfc.section.8.4.13.p.1">The precondition given in one or more of the request-header fields evaluated to false when it was tested on the server, as
    13751380         defined in <a href="#Part4" id="rfc.xref.Part4.13"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>.
    13761381      </p>
    13771382      <div id="rfc.iref.55"></div>
    13781383      <div id="rfc.iref.s.32"></div>
    1379       <h3 id="rfc.section.9.4.14"><a href="#rfc.section.9.4.14">9.4.14</a>&nbsp;<a id="status.413" href="#status.413">413 Request Entity Too Large</a></h3>
    1380       <p id="rfc.section.9.4.14.p.1">The server is refusing to process a request because the request entity is larger than the server is willing or able to process.
     1384      <h3 id="rfc.section.8.4.14"><a href="#rfc.section.8.4.14">8.4.14</a>&nbsp;<a id="status.413" href="#status.413">413 Request Entity Too Large</a></h3>
     1385      <p id="rfc.section.8.4.14.p.1">The server is refusing to process a request because the request entity is larger than the server is willing or able to process.
    13811386         The server <em class="bcp14">MAY</em> close the connection to prevent the client from continuing the request.
    13821387      </p>
    1383       <p id="rfc.section.9.4.14.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.
     1388      <p id="rfc.section.8.4.14.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.
    13841389      </p>
    13851390      <div id="rfc.iref.56"></div>
    13861391      <div id="rfc.iref.s.33"></div>
    1387       <h3 id="rfc.section.9.4.15"><a href="#rfc.section.9.4.15">9.4.15</a>&nbsp;<a id="status.414" href="#status.414">414 Request-target Too Long</a></h3>
    1388       <p id="rfc.section.9.4.15.p.1">The server is refusing to service the request because the request-target is longer than the server is willing to interpret.
     1392      <h3 id="rfc.section.8.4.15"><a href="#rfc.section.8.4.15">8.4.15</a>&nbsp;<a id="status.414" href="#status.414">414 Request-target Too Long</a></h3>
     1393      <p id="rfc.section.8.4.15.p.1">The server is refusing to service the request because the request-target is longer than the server is willing to interpret.
    13891394         This rare condition is only likely to occur when a client has improperly converted a POST request to a GET request with long
    13901395         query information, when the client has descended into a URI "black hole" of redirection (e.g., a redirected URI prefix that
     
    13941399      <div id="rfc.iref.57"></div>
    13951400      <div id="rfc.iref.s.34"></div>
    1396       <h3 id="rfc.section.9.4.16"><a href="#rfc.section.9.4.16">9.4.16</a>&nbsp;<a id="status.415" href="#status.415">415 Unsupported Media Type</a></h3>
    1397       <p id="rfc.section.9.4.16.p.1">The server is refusing to service the request because the entity of the request is in a format not supported by the requested
     1401      <h3 id="rfc.section.8.4.16"><a href="#rfc.section.8.4.16">8.4.16</a>&nbsp;<a id="status.415" href="#status.415">415 Unsupported Media Type</a></h3>
     1402      <p id="rfc.section.8.4.16.p.1">The server is refusing to service the request because the entity of the request is in a format not supported by the requested
    13981403         resource for the requested method.
    13991404      </p>
    14001405      <div id="rfc.iref.58"></div>
    14011406      <div id="rfc.iref.s.35"></div>
    1402       <h3 id="rfc.section.9.4.17"><a href="#rfc.section.9.4.17">9.4.17</a>&nbsp;<a id="status.416" href="#status.416">416 Requested Range Not Satisfiable</a></h3>
    1403       <p id="rfc.section.9.4.17.p.1">The request included a Range request-header field (<a href="p5-range.html#header.range" title="Range">Section 6.4</a> of <a href="#Part5" id="rfc.xref.Part5.10"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>) and none of the range-specifier values in this field overlap the current extent of the selected resource.
     1407      <h3 id="rfc.section.8.4.17"><a href="#rfc.section.8.4.17">8.4.17</a>&nbsp;<a id="status.416" href="#status.416">416 Requested Range Not Satisfiable</a></h3>
     1408      <p id="rfc.section.8.4.17.p.1">The request included a Range request-header field (<a href="p5-range.html#header.range" title="Range">Section 5.4</a> of <a href="#Part5" id="rfc.xref.Part5.10"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>) and none of the range-specifier values in this field overlap the current extent of the selected resource.
    14041409      </p>
    14051410      <div id="rfc.iref.59"></div>
    14061411      <div id="rfc.iref.s.36"></div>
    1407       <h3 id="rfc.section.9.4.18"><a href="#rfc.section.9.4.18">9.4.18</a>&nbsp;<a id="status.417" href="#status.417">417 Expectation Failed</a></h3>
    1408       <p id="rfc.section.9.4.18.p.1">The expectation given in an Expect request-header field (see <a href="#header.expect" id="rfc.xref.header.expect.2" title="Expect">Section&nbsp;10.2</a>) could not be met by this server, or, if the server is a proxy, the server has unambiguous evidence that the request could
     1412      <h3 id="rfc.section.8.4.18"><a href="#rfc.section.8.4.18">8.4.18</a>&nbsp;<a id="status.417" href="#status.417">417 Expectation Failed</a></h3>
     1413      <p id="rfc.section.8.4.18.p.1">The expectation given in an Expect request-header field (see <a href="#header.expect" id="rfc.xref.header.expect.2" title="Expect">Section&nbsp;9.2</a>) could not be met by this server, or, if the server is a proxy, the server has unambiguous evidence that the request could
    14091414         not be met by the next-hop server.
    14101415      </p>
    1411       <h2 id="rfc.section.9.5"><a href="#rfc.section.9.5">9.5</a>&nbsp;<a id="status.5xx" href="#status.5xx">Server Error 5xx</a></h2>
    1412       <p id="rfc.section.9.5.p.1">Response status codes beginning with the digit "5" indicate cases in which the server is aware that it has erred or is incapable
     1416      <h2 id="rfc.section.8.5"><a href="#rfc.section.8.5">8.5</a>&nbsp;<a id="status.5xx" href="#status.5xx">Server Error 5xx</a></h2>
     1417      <p id="rfc.section.8.5.p.1">Response status codes beginning with the digit "5" indicate cases in which the server is aware that it has erred or is incapable
    14131418         of performing the request. Except when responding to a HEAD request, the server <em class="bcp14">SHOULD</em> include an entity containing an explanation of the error situation, and whether it is a temporary or permanent condition.
    14141419         User agents <em class="bcp14">SHOULD</em> display any included entity to the user. These response codes are applicable to any request method.
     
    14161421      <div id="rfc.iref.60"></div>
    14171422      <div id="rfc.iref.s.37"></div>
    1418       <h3 id="rfc.section.9.5.1"><a href="#rfc.section.9.5.1">9.5.1</a>&nbsp;<a id="status.500" href="#status.500">500 Internal Server Error</a></h3>
    1419       <p id="rfc.section.9.5.1.p.1">The server encountered an unexpected condition which prevented it from fulfilling the request.</p>
     1423      <h3 id="rfc.section.8.5.1"><a href="#rfc.section.8.5.1">8.5.1</a>&nbsp;<a id="status.500" href="#status.500">500 Internal Server Error</a></h3>
     1424      <p id="rfc.section.8.5.1.p.1">The server encountered an unexpected condition which prevented it from fulfilling the request.</p>
    14201425      <div id="rfc.iref.61"></div>
    14211426      <div id="rfc.iref.s.38"></div>
    1422       <h3 id="rfc.section.9.5.2"><a href="#rfc.section.9.5.2">9.5.2</a>&nbsp;<a id="status.501" href="#status.501">501 Not Implemented</a></h3>
    1423       <p id="rfc.section.9.5.2.p.1">The server does not support the functionality required to fulfill the request. This is the appropriate response when the server
     1427      <h3 id="rfc.section.8.5.2"><a href="#rfc.section.8.5.2">8.5.2</a>&nbsp;<a id="status.501" href="#status.501">501 Not Implemented</a></h3>
     1428      <p id="rfc.section.8.5.2.p.1">The server does not support the functionality required to fulfill the request. This is the appropriate response when the server
    14241429         does not recognize the request method and is not capable of supporting it for any resource.
    14251430      </p>
    14261431      <div id="rfc.iref.62"></div>
    14271432      <div id="rfc.iref.s.39"></div>
    1428       <h3 id="rfc.section.9.5.3"><a href="#rfc.section.9.5.3">9.5.3</a>&nbsp;<a id="status.502" href="#status.502">502 Bad Gateway</a></h3>
    1429       <p id="rfc.section.9.5.3.p.1">The server, while acting as a gateway or proxy, received an invalid response from the upstream server it accessed in attempting
     1433      <h3 id="rfc.section.8.5.3"><a href="#rfc.section.8.5.3">8.5.3</a>&nbsp;<a id="status.502" href="#status.502">502 Bad Gateway</a></h3>
     1434      <p id="rfc.section.8.5.3.p.1">The server, while acting as a gateway or proxy, received an invalid response from the upstream server it accessed in attempting
    14301435         to fulfill the request.
    14311436      </p>
    14321437      <div id="rfc.iref.63"></div>
    14331438      <div id="rfc.iref.s.40"></div>
    1434       <h3 id="rfc.section.9.5.4"><a href="#rfc.section.9.5.4">9.5.4</a>&nbsp;<a id="status.503" href="#status.503">503 Service Unavailable</a></h3>
    1435       <p id="rfc.section.9.5.4.p.1">The server is currently unable to handle the request due to a temporary overloading or maintenance of the server. The implication
     1439      <h3 id="rfc.section.8.5.4"><a href="#rfc.section.8.5.4">8.5.4</a>&nbsp;<a id="status.503" href="#status.503">503 Service Unavailable</a></h3>
     1440      <p id="rfc.section.8.5.4.p.1">The server is currently unable to handle the request due to a temporary overloading or maintenance of the server. The implication
    14361441         is that this is a temporary condition which will be alleviated after some delay. If known, the length of the delay <em class="bcp14">MAY</em> be indicated in a Retry-After header. If no Retry-After is given, the client <em class="bcp14">SHOULD</em> handle the response as it would for a 500 response.
    14371442      </p>
     
    14431448      <div id="rfc.iref.64"></div>
    14441449      <div id="rfc.iref.s.41"></div>
    1445       <h3 id="rfc.section.9.5.5"><a href="#rfc.section.9.5.5">9.5.5</a>&nbsp;<a id="status.504" href="#status.504">504 Gateway Timeout</a></h3>
    1446       <p id="rfc.section.9.5.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
     1450      <h3 id="rfc.section.8.5.5"><a href="#rfc.section.8.5.5">8.5.5</a>&nbsp;<a id="status.504" href="#status.504">504 Gateway Timeout</a></h3>
     1451      <p id="rfc.section.8.5.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
    14471452         URI (e.g. HTTP, FTP, LDAP) or some other auxiliary server (e.g. DNS) it needed to access in attempting to complete the request.
    14481453      </p>
     
    14531458      <div id="rfc.iref.65"></div>
    14541459      <div id="rfc.iref.s.42"></div>
    1455       <h3 id="rfc.section.9.5.6"><a href="#rfc.section.9.5.6">9.5.6</a>&nbsp;<a id="status.505" href="#status.505">505 HTTP Version Not Supported</a></h3>
    1456       <p id="rfc.section.9.5.6.p.1">The server does not support, or refuses to support, the protocol version that was used in the request message. The server
     1460      <h3 id="rfc.section.8.5.6"><a href="#rfc.section.8.5.6">8.5.6</a>&nbsp;<a id="status.505" href="#status.505">505 HTTP Version Not Supported</a></h3>
     1461      <p id="rfc.section.8.5.6.p.1">The server does not support, or refuses to support, the protocol version that was used in the request message. The server
    14571462         is indicating that it is unable or unwilling to complete the request using the same major version as the client, as described
    14581463         in <a href="p1-messaging.html#http.version" title="HTTP Version">Section 3.1</a> of <a href="#Part1" id="rfc.xref.Part1.28"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, other than with this error message. The response <em class="bcp14">SHOULD</em> contain an entity describing why that version is not supported and what other protocols are supported by that server.
    14591464      </p>
    1460       <h1 id="rfc.section.10"><a href="#rfc.section.10">10.</a>&nbsp;<a id="header.fields" href="#header.fields">Header Field Definitions</a></h1>
    1461       <p id="rfc.section.10.p.1">This section defines the syntax and semantics of HTTP/1.1 header fields related to request and response semantics.</p>
    1462       <p id="rfc.section.10.p.2">For entity-header fields, both sender and recipient refer to either the client or the server, depending on who sends and who
     1465      <h1 id="rfc.section.9"><a href="#rfc.section.9">9.</a>&nbsp;<a id="header.fields" href="#header.fields">Header Field Definitions</a></h1>
     1466      <p id="rfc.section.9.p.1">This section defines the syntax and semantics of HTTP/1.1 header fields related to request and response semantics.</p>
     1467      <p id="rfc.section.9.p.2">For entity-header fields, both sender and recipient refer to either the client or the server, depending on who sends and who
    14631468         receives the entity.
    14641469      </p>
    14651470      <div id="rfc.iref.a.1"></div>
    14661471      <div id="rfc.iref.h.2"></div>
    1467       <h2 id="rfc.section.10.1"><a href="#rfc.section.10.1">10.1</a>&nbsp;<a id="header.allow" href="#header.allow">Allow</a></h2>
    1468       <p id="rfc.section.10.1.p.1">The response-header field "Allow" lists the set of methods advertised as supported by the resource identified by the request-target.
     1472      <h2 id="rfc.section.9.1"><a href="#rfc.section.9.1">9.1</a>&nbsp;<a id="header.allow" href="#header.allow">Allow</a></h2>
     1473      <p id="rfc.section.9.1.p.1">The response-header field "Allow" lists the set of methods advertised as supported by the resource identified by the request-target.
    14691474         The purpose of this field is strictly to inform the recipient of valid methods associated with the resource. An Allow header
    14701475         field <em class="bcp14">MUST</em> be present in a 405 (Method Not Allowed) response.
    14711476      </p>
    1472       <div id="rfc.figure.u.13"></div><pre class="inline"><span id="rfc.iref.g.9"></span><span id="rfc.iref.g.10"></span>  <a href="#header.allow" class="smpl">Allow</a>   = "Allow" ":" <a href="#notation" class="smpl">OWS</a> <a href="#header.allow" class="smpl">Allow-v</a>
     1477      <div id="rfc.figure.u.13"></div><pre class="inline"><span id="rfc.iref.g.9"></span><span id="rfc.iref.g.10"></span>  <a href="#header.allow" class="smpl">Allow</a>   = "Allow" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.allow" class="smpl">Allow-v</a>
    14731478  <a href="#header.allow" class="smpl">Allow-v</a> = #<a href="#method" class="smpl">Method</a>
    1474 </pre><p id="rfc.section.10.1.p.3">Example of use:</p>
     1479</pre><p id="rfc.section.9.1.p.3">Example of use:</p>
    14751480      <div id="rfc.figure.u.14"></div><pre class="text">  Allow: GET, HEAD, PUT
    1476 </pre><p id="rfc.section.10.1.p.5">The actual set of allowed methods is defined by the origin server at the time of each request.</p>
    1477       <p id="rfc.section.10.1.p.6">A proxy <em class="bcp14">MUST NOT</em> modify the Allow header field even if it does not understand all the methods specified, since the user agent might have other
     1481</pre><p id="rfc.section.9.1.p.5">The actual set of allowed methods is defined by the origin server at the time of each request.</p>
     1482      <p id="rfc.section.9.1.p.6">A proxy <em class="bcp14">MUST NOT</em> modify the Allow header field even if it does not understand all the methods specified, since the user agent might have other
    14781483         means of communicating with the origin server.
    14791484      </p>
    14801485      <div id="rfc.iref.e.1"></div>
    14811486      <div id="rfc.iref.h.3"></div>
    1482       <h2 id="rfc.section.10.2"><a href="#rfc.section.10.2">10.2</a>&nbsp;<a id="header.expect" href="#header.expect">Expect</a></h2>
    1483       <p id="rfc.section.10.2.p.1">The request-header field "Expect" is used to indicate that particular server behaviors are required by the client.</p>
    1484       <div id="rfc.figure.u.15"></div><pre class="inline"><span id="rfc.iref.g.11"></span><span id="rfc.iref.g.12"></span><span id="rfc.iref.g.13"></span><span id="rfc.iref.g.14"></span><span id="rfc.iref.g.15"></span>  <a href="#header.expect" class="smpl">Expect</a>       = "Expect" ":" <a href="#notation" class="smpl">OWS</a> <a href="#header.expect" class="smpl">Expect-v</a>
     1487      <h2 id="rfc.section.9.2"><a href="#rfc.section.9.2">9.2</a>&nbsp;<a id="header.expect" href="#header.expect">Expect</a></h2>
     1488      <p id="rfc.section.9.2.p.1">The request-header field "Expect" is used to indicate that particular server behaviors are required by the client.</p>
     1489      <div id="rfc.figure.u.15"></div><pre class="inline"><span id="rfc.iref.g.11"></span><span id="rfc.iref.g.12"></span><span id="rfc.iref.g.13"></span><span id="rfc.iref.g.14"></span><span id="rfc.iref.g.15"></span>  <a href="#header.expect" class="smpl">Expect</a>       = "Expect" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.expect" class="smpl">Expect-v</a>
    14851490  <a href="#header.expect" class="smpl">Expect-v</a>     = 1#<a href="#header.expect" class="smpl">expectation</a>
    14861491 
    14871492  <a href="#header.expect" class="smpl">expectation</a>  = "100-continue" / <a href="#header.expect" class="smpl">expectation-extension</a>
    1488   <a href="#header.expect" class="smpl">expectation-extension</a> = <a href="#notation" class="smpl">token</a> [ "=" ( <a href="#notation" class="smpl">token</a> / <a href="#notation" class="smpl">quoted-string</a> )
     1493  <a href="#header.expect" class="smpl">expectation-extension</a> = <a href="#core.rules" class="smpl">token</a> [ "=" ( <a href="#core.rules" class="smpl">token</a> / <a href="#core.rules" class="smpl">quoted-string</a> )
    14891494                           *<a href="#header.expect" class="smpl">expect-params</a> ]
    1490   <a href="#header.expect" class="smpl">expect-params</a> = ";" <a href="#notation" class="smpl">token</a> [ "=" ( <a href="#notation" class="smpl">token</a> / <a href="#notation" class="smpl">quoted-string</a> ) ]
    1491 </pre><p id="rfc.section.10.2.p.3">A server that does not understand or is unable to comply with any of the expectation values in the Expect field of a request <em class="bcp14">MUST</em> respond with appropriate error status. The server <em class="bcp14">MUST</em> respond with a 417 (Expectation Failed) status if any of the expectations cannot be met or, if there are other problems with
     1495  <a href="#header.expect" class="smpl">expect-params</a> = ";" <a href="#core.rules" class="smpl">token</a> [ "=" ( <a href="#core.rules" class="smpl">token</a> / <a href="#core.rules" class="smpl">quoted-string</a> ) ]
     1496</pre><p id="rfc.section.9.2.p.3">A server that does not understand or is unable to comply with any of the expectation values in the Expect field of a request <em class="bcp14">MUST</em> respond with appropriate error status. The server <em class="bcp14">MUST</em> respond with a 417 (Expectation Failed) status if any of the expectations cannot be met or, if there are other problems with
    14921497         the request, some other 4xx status.
    14931498      </p>
    1494       <p id="rfc.section.10.2.p.4">This header field is defined with extensible syntax to allow for future extensions. If a server receives a request containing
     1499      <p id="rfc.section.9.2.p.4">This header field is defined with extensible syntax to allow for future extensions. If a server receives a request containing
    14951500         an Expect field that includes an expectation-extension that it does not support, it <em class="bcp14">MUST</em> respond with a 417 (Expectation Failed) status.
    14961501      </p>
    1497       <p id="rfc.section.10.2.p.5">Comparison of expectation values is case-insensitive for unquoted tokens (including the 100-continue token), and is case-sensitive
     1502      <p id="rfc.section.9.2.p.5">Comparison of expectation values is case-insensitive for unquoted tokens (including the 100-continue token), and is case-sensitive
    14981503         for quoted-string expectation-extensions.
    14991504      </p>
    1500       <p id="rfc.section.10.2.p.6">The Expect mechanism is hop-by-hop: that is, an HTTP/1.1 proxy <em class="bcp14">MUST</em> return a 417 (Expectation Failed) status if it receives a request with an expectation that it cannot meet. However, the Expect
     1505      <p id="rfc.section.9.2.p.6">The Expect mechanism is hop-by-hop: that is, an HTTP/1.1 proxy <em class="bcp14">MUST</em> return a 417 (Expectation Failed) status if it receives a request with an expectation that it cannot meet. However, the Expect
    15011506         request-header itself is end-to-end; it <em class="bcp14">MUST</em> be forwarded if the request is forwarded.
    15021507      </p>
    1503       <p id="rfc.section.10.2.p.7">Many older HTTP/1.0 and HTTP/1.1 applications do not understand the Expect header.</p>
    1504       <p id="rfc.section.10.2.p.8">See <a href="p1-messaging.html#use.of.the.100.status" title="Use of the 100 (Continue) Status">Section 7.2.3</a> of <a href="#Part1" id="rfc.xref.Part1.29"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a> for the use of the 100 (Continue) status.
     1508      <p id="rfc.section.9.2.p.7">Many older HTTP/1.0 and HTTP/1.1 applications do not understand the Expect header.</p>
     1509      <p id="rfc.section.9.2.p.8">See <a href="p1-messaging.html#use.of.the.100.status" title="Use of the 100 (Continue) Status">Section 7.2.3</a> of <a href="#Part1" id="rfc.xref.Part1.29"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a> for the use of the 100 (Continue) status.
    15051510      </p>
    15061511      <div id="rfc.iref.f.1"></div>
    15071512      <div id="rfc.iref.h.4"></div>
    1508       <h2 id="rfc.section.10.3"><a href="#rfc.section.10.3">10.3</a>&nbsp;<a id="header.from" href="#header.from">From</a></h2>
    1509       <p id="rfc.section.10.3.p.1">The request-header field "From", if given, <em class="bcp14">SHOULD</em> contain an Internet e-mail address for the human user who controls the requesting user agent. The address <em class="bcp14">SHOULD</em> be machine-usable, as defined by "mailbox" in <a href="http://tools.ietf.org/html/rfc5322#section-3.4">Section 3.4</a> of <a href="#RFC5322" id="rfc.xref.RFC5322.1"><cite title="Internet Message Format">[RFC5322]</cite></a>:
    1510       </p>
    1511       <div id="rfc.figure.u.16"></div><pre class="inline"><span id="rfc.iref.g.16"></span><span id="rfc.iref.g.17"></span>  <a href="#header.from" class="smpl">From</a>    = "From" ":" <a href="#notation" class="smpl">OWS</a> <a href="#header.from" class="smpl">From-v</a>
     1513      <h2 id="rfc.section.9.3"><a href="#rfc.section.9.3">9.3</a>&nbsp;<a id="header.from" href="#header.from">From</a></h2>
     1514      <p id="rfc.section.9.3.p.1">The request-header field "From", if given, <em class="bcp14">SHOULD</em> contain an Internet e-mail address for the human user who controls the requesting user agent. The address <em class="bcp14">SHOULD</em> be machine-usable, as defined by "mailbox" in <a href="http://tools.ietf.org/html/rfc5322#section-3.4">Section 3.4</a> of <a href="#RFC5322" id="rfc.xref.RFC5322.1"><cite title="Internet Message Format">[RFC5322]</cite></a>:
     1515      </p>
     1516      <div id="rfc.figure.u.16"></div><pre class="inline"><span id="rfc.iref.g.16"></span><span id="rfc.iref.g.17"></span>  <a href="#header.from" class="smpl">From</a>    = "From" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.from" class="smpl">From-v</a>
    15121517  <a href="#header.from" class="smpl">From-v</a>  = <a href="#header.from" class="smpl">mailbox</a>
    15131518 
    15141519  <a href="#header.from" class="smpl">mailbox</a> = &lt;mailbox, defined in <a href="#RFC5322" id="rfc.xref.RFC5322.2"><cite title="Internet Message Format">[RFC5322]</cite></a>, <a href="http://tools.ietf.org/html/rfc5322#section-3.4">Section 3.4</a>&gt;
    1515 </pre><p id="rfc.section.10.3.p.3">An example is:</p>
     1520</pre><p id="rfc.section.9.3.p.3">An example is:</p>
    15161521      <div id="rfc.figure.u.17"></div><pre class="text">  From: webmaster@example.org
    1517 </pre><p id="rfc.section.10.3.p.5">This header field <em class="bcp14">MAY</em> be used for logging purposes and as a means for identifying the source of invalid or unwanted requests. It <em class="bcp14">SHOULD NOT</em> be used as an insecure form of access protection. The interpretation of this field is that the request is being performed
     1522</pre><p id="rfc.section.9.3.p.5">This header field <em class="bcp14">MAY</em> be used for logging purposes and as a means for identifying the source of invalid or unwanted requests. It <em class="bcp14">SHOULD NOT</em> be used as an insecure form of access protection. The interpretation of this field is that the request is being performed
    15181523         on behalf of the person given, who accepts responsibility for the method performed. In particular, robot agents <em class="bcp14">SHOULD</em> include this header so that the person responsible for running the robot can be contacted if problems occur on the receiving
    15191524         end.
    15201525      </p>
    1521       <p id="rfc.section.10.3.p.6">The Internet e-mail address in this field <em class="bcp14">MAY</em> be separate from the Internet host which issued the request. For example, when a request is passed through a proxy the original
     1526      <p id="rfc.section.9.3.p.6">The Internet e-mail address in this field <em class="bcp14">MAY</em> be separate from the Internet host which issued the request. For example, when a request is passed through a proxy the original
    15221527         issuer's address <em class="bcp14">SHOULD</em> be used.
    15231528      </p>
    1524       <p id="rfc.section.10.3.p.7">The client <em class="bcp14">SHOULD NOT</em> send the From header field without the user's approval, as it might conflict with the user's privacy interests or their site's
     1529      <p id="rfc.section.9.3.p.7">The client <em class="bcp14">SHOULD NOT</em> send the From header field without the user's approval, as it might conflict with the user's privacy interests or their site's
    15251530         security policy. It is strongly recommended that the user be able to disable, enable, and modify the value of this field at
    15261531         any time prior to a request.
     
    15281533      <div id="rfc.iref.l.1"></div>
    15291534      <div id="rfc.iref.h.5"></div>
    1530       <h2 id="rfc.section.10.4"><a href="#rfc.section.10.4">10.4</a>&nbsp;<a id="header.location" href="#header.location">Location</a></h2>
    1531       <p id="rfc.section.10.4.p.1">The response-header field "Location" is used for the identification of a new resource or to redirect the recipient to a location
     1535      <h2 id="rfc.section.9.4"><a href="#rfc.section.9.4">9.4</a>&nbsp;<a id="header.location" href="#header.location">Location</a></h2>
     1536      <p id="rfc.section.9.4.p.1">The response-header field "Location" is used for the identification of a new resource or to redirect the recipient to a location
    15321537         other than the request-target for completion of the request. For 201 (Created) responses, the Location is that of the new
    15331538         resource which was created by the request. For 3xx responses, the location <em class="bcp14">SHOULD</em> indicate the server's preferred URI for automatic redirection to the resource. The field value consists of a single absolute
    15341539         URI.
    15351540      </p>
    1536       <div id="rfc.figure.u.18"></div><pre class="inline"><span id="rfc.iref.g.18"></span><span id="rfc.iref.g.19"></span>  <a href="#header.location" class="smpl">Location</a>       = "Location" ":" <a href="#notation" class="smpl">OWS</a> <a href="#header.location" class="smpl">Location-v</a>
     1541      <div id="rfc.figure.u.18"></div><pre class="inline"><span id="rfc.iref.g.18"></span><span id="rfc.iref.g.19"></span>  <a href="#header.location" class="smpl">Location</a>       = "Location" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.location" class="smpl">Location-v</a>
    15371542  <a href="#header.location" class="smpl">Location-v</a>     = <a href="#abnf.dependencies" class="smpl">absolute-URI</a> [ "#" <a href="#abnf.dependencies" class="smpl">fragment</a> ]
    1538 </pre><p id="rfc.section.10.4.p.3">An example is:</p>
     1543</pre><p id="rfc.section.9.4.p.3">An example is:</p>
    15391544      <div id="rfc.figure.u.19"></div><pre class="text">  Location: http://www.example.org/pub/WWW/People.html
    1540 </pre><p id="rfc.section.10.4.p.5"> </p>
     1545</pre><p id="rfc.section.9.4.p.5"> </p>
    15411546      <dl class="empty">
    1542          <dd> <b>Note:</b> The Content-Location header field (<a href="p3-payload.html#header.content-location" title="Content-Location">Section 6.7</a> of <a href="#Part3" id="rfc.xref.Part3.11"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>) differs from Location in that the Content-Location identifies the original location of the entity enclosed in the response.
     1547         <dd> <b>Note:</b> The Content-Location header field (<a href="p3-payload.html#header.content-location" title="Content-Location">Section 5.7</a> of <a href="#Part3" id="rfc.xref.Part3.11"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>) differs from Location in that the Content-Location identifies the original location of the entity enclosed in the response.
    15431548            It is therefore possible for a response to contain header fields for both Location and Content-Location.
    15441549         </dd>
    15451550      </dl>
    1546       <p id="rfc.section.10.4.p.6">There are circumstances in which a fragment identifier in a Location URL would not be appropriate: </p>
     1551      <p id="rfc.section.9.4.p.6">There are circumstances in which a fragment identifier in a Location URL would not be appropriate: </p>
    15471552      <ul>
    15481553         <li>With a 201 Created response, because in this usage the Location header specifies the URL for the entire created resource.</li>
     
    15541559      <div id="rfc.iref.m.9"></div>
    15551560      <div id="rfc.iref.h.6"></div>
    1556       <h2 id="rfc.section.10.5"><a href="#rfc.section.10.5">10.5</a>&nbsp;<a id="header.max-forwards" href="#header.max-forwards">Max-Forwards</a></h2>
    1557       <p id="rfc.section.10.5.p.1">The request-header "Max-Forwards" field provides a mechanism with the TRACE (<a href="#TRACE" id="rfc.xref.TRACE.2" title="TRACE">Section&nbsp;8.8</a>) and OPTIONS (<a href="#OPTIONS" id="rfc.xref.OPTIONS.2" title="OPTIONS">Section&nbsp;8.2</a>) methods to limit the number of proxies or gateways that can forward the request to the next inbound server. This can be
     1561      <h2 id="rfc.section.9.5"><a href="#rfc.section.9.5">9.5</a>&nbsp;<a id="header.max-forwards" href="#header.max-forwards">Max-Forwards</a></h2>
     1562      <p id="rfc.section.9.5.p.1">The request-header "Max-Forwards" field provides a mechanism with the TRACE (<a href="#TRACE" id="rfc.xref.TRACE.2" title="TRACE">Section&nbsp;7.8</a>) and OPTIONS (<a href="#OPTIONS" id="rfc.xref.OPTIONS.2" title="OPTIONS">Section&nbsp;7.2</a>) methods to limit the number of proxies or gateways that can forward the request to the next inbound server. This can be
    15581563         useful when the client is attempting to trace a request chain which appears to be failing or looping in mid-chain.
    15591564      </p>
    1560       <div id="rfc.figure.u.20"></div><pre class="inline"><span id="rfc.iref.g.20"></span><span id="rfc.iref.g.21"></span>  <a href="#header.max-forwards" class="smpl">Max-Forwards</a>   = "Max-Forwards" ":" <a href="#notation" class="smpl">OWS</a> <a href="#header.max-forwards" class="smpl">Max-Forwards-v</a>
    1561   <a href="#header.max-forwards" class="smpl">Max-Forwards-v</a> = 1*<a href="#notation" class="smpl">DIGIT</a>
    1562 </pre><p id="rfc.section.10.5.p.3">The Max-Forwards value is a decimal integer indicating the remaining number of times this request message may be forwarded.</p>
    1563       <p id="rfc.section.10.5.p.4">Each proxy or gateway recipient of a TRACE or OPTIONS request containing a Max-Forwards header field <em class="bcp14">MUST</em> check and update its value prior to forwarding the request. If the received value is zero (0), the recipient <em class="bcp14">MUST NOT</em> forward the request; instead, it <em class="bcp14">MUST</em> respond as the final recipient. If the received Max-Forwards value is greater than zero, then the forwarded message <em class="bcp14">MUST</em> contain an updated Max-Forwards field with a value decremented by one (1).
    1564       </p>
    1565       <p id="rfc.section.10.5.p.5">The Max-Forwards header field <em class="bcp14">MAY</em> be ignored for all other methods defined by this specification and for any extension methods for which it is not explicitly
     1565      <div id="rfc.figure.u.20"></div><pre class="inline"><span id="rfc.iref.g.20"></span><span id="rfc.iref.g.21"></span>  <a href="#header.max-forwards" class="smpl">Max-Forwards</a>   = "Max-Forwards" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.max-forwards" class="smpl">Max-Forwards-v</a>
     1566  <a href="#header.max-forwards" class="smpl">Max-Forwards-v</a> = 1*<a href="#core.rules" class="smpl">DIGIT</a>
     1567</pre><p id="rfc.section.9.5.p.3">The Max-Forwards value is a decimal integer indicating the remaining number of times this request message may be forwarded.</p>
     1568      <p id="rfc.section.9.5.p.4">Each proxy or gateway recipient of a TRACE or OPTIONS request containing a Max-Forwards header field <em class="bcp14">MUST</em> check and update its value prior to forwarding the request. If the received value is zero (0), the recipient <em class="bcp14">MUST NOT</em> forward the request; instead, it <em class="bcp14">MUST</em> respond as the final recipient. If the received Max-Forwards value is greater than zero, then the forwarded message <em class="bcp14">MUST</em> contain an updated Max-Forwards field with a value decremented by one (1).
     1569      </p>
     1570      <p id="rfc.section.9.5.p.5">The Max-Forwards header field <em class="bcp14">MAY</em> be ignored for all other methods defined by this specification and for any extension methods for which it is not explicitly
    15661571         referred to as part of that method definition.
    15671572      </p>
    15681573      <div id="rfc.iref.r.1"></div>
    15691574      <div id="rfc.iref.h.7"></div>
    1570       <h2 id="rfc.section.10.6"><a href="#rfc.section.10.6">10.6</a>&nbsp;<a id="header.referer" href="#header.referer">Referer</a></h2>
    1571       <p id="rfc.section.10.6.p.1">The request-header field "Referer" [sic] allows the client to specify, for the server's benefit, the address (URI) of the
     1575      <h2 id="rfc.section.9.6"><a href="#rfc.section.9.6">9.6</a>&nbsp;<a id="header.referer" href="#header.referer">Referer</a></h2>
     1576      <p id="rfc.section.9.6.p.1">The request-header field "Referer" [sic] allows the client to specify, for the server's benefit, the address (URI) of the
    15721577         resource from which the request-target was obtained (the "referrer", although the header field is misspelled.) The Referer
    15731578         request-header allows a server to generate lists of back-links to resources for interest, logging, optimized caching, etc.
    15741579         It also allows obsolete or mistyped links to be traced for maintenance. The Referer field <em class="bcp14">MUST NOT</em> be sent if the request-target was obtained from a source that does not have its own URI, such as input from the user keyboard.
    15751580      </p>
    1576       <div id="rfc.figure.u.21"></div><pre class="inline"><span id="rfc.iref.g.22"></span><span id="rfc.iref.g.23"></span>  <a href="#header.referer" class="smpl">Referer</a>        = "Referer" ":" <a href="#notation" class="smpl">OWS</a> <a href="#header.referer" class="smpl">Referer-v</a>
     1581      <div id="rfc.figure.u.21"></div><pre class="inline"><span id="rfc.iref.g.22"></span><span id="rfc.iref.g.23"></span>  <a href="#header.referer" class="smpl">Referer</a>        = "Referer" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.referer" class="smpl">Referer-v</a>
    15771582  <a href="#header.referer" class="smpl">Referer-v</a>      = <a href="#abnf.dependencies" class="smpl">absolute-URI</a> / <a href="#abnf.dependencies" class="smpl">partial-URI</a>
    1578 </pre><p id="rfc.section.10.6.p.3">Example:</p>
     1583</pre><p id="rfc.section.9.6.p.3">Example:</p>
    15791584      <div id="rfc.figure.u.22"></div><pre class="text">  Referer: http://www.example.org/hypertext/Overview.html
    1580 </pre><p id="rfc.section.10.6.p.5">If the field value is a relative URI, it <em class="bcp14">SHOULD</em> be interpreted relative to the request-target. The URI <em class="bcp14">MUST NOT</em> include a fragment. See <a href="#encoding.sensitive.information.in.uris" title="Encoding Sensitive Information in URIs">Section&nbsp;12.2</a> for security considerations.
     1585</pre><p id="rfc.section.9.6.p.5">If the field value is a relative URI, it <em class="bcp14">SHOULD</em> be interpreted relative to the request-target. The URI <em class="bcp14">MUST NOT</em> include a fragment. See <a href="#encoding.sensitive.information.in.uris" title="Encoding Sensitive Information in URIs">Section&nbsp;11.2</a> for security considerations.
    15811586      </p>
    15821587      <div id="rfc.iref.r.2"></div>
    15831588      <div id="rfc.iref.h.8"></div>
    1584       <h2 id="rfc.section.10.7"><a href="#rfc.section.10.7">10.7</a>&nbsp;<a id="header.retry-after" href="#header.retry-after">Retry-After</a></h2>
    1585       <p id="rfc.section.10.7.p.1">The response-header "Retry-After" field can be used with a 503 (Service Unavailable) response to indicate how long the service
     1589      <h2 id="rfc.section.9.7"><a href="#rfc.section.9.7">9.7</a>&nbsp;<a id="header.retry-after" href="#header.retry-after">Retry-After</a></h2>
     1590      <p id="rfc.section.9.7.p.1">The response-header "Retry-After" field can be used with a 503 (Service Unavailable) response to indicate how long the service
    15861591         is expected to be unavailable to the requesting client. This field <em class="bcp14">MAY</em> also be used with any 3xx (Redirection) response to indicate the minimum time the user-agent is asked wait before issuing
    15871592         the redirected request. The value of this field can be either an HTTP-date or an integer number of seconds (in decimal) after
    15881593         the time of the response.
    15891594      </p>
    1590       <div id="rfc.figure.u.23"></div><pre class="inline"><span id="rfc.iref.g.24"></span><span id="rfc.iref.g.25"></span>  <a href="#header.retry-after" class="smpl">Retry-After</a>   = "Retry-After" ":" <a href="#notation" class="smpl">OWS</a> <a href="#header.retry-after" class="smpl">Retry-After-v</a>
     1595      <div id="rfc.figure.u.23"></div><pre class="inline"><span id="rfc.iref.g.24"></span><span id="rfc.iref.g.25"></span>  <a href="#header.retry-after" class="smpl">Retry-After</a>   = "Retry-After" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.retry-after" class="smpl">Retry-After-v</a>
    15911596  <a href="#header.retry-after" class="smpl">Retry-After-v</a> = <a href="#abnf.dependencies" class="smpl">HTTP-date</a> / <a href="#rule.delta-seconds" class="smpl">delta-seconds</a>
    15921597</pre><div id="rule.delta-seconds">
    1593          <p id="rfc.section.10.7.p.3">  Time spans are non-negative decimal integers, representing time in seconds.</p>
     1598         <p id="rfc.section.9.7.p.3">  Time spans are non-negative decimal integers, representing time in seconds.</p>
    15941599      </div>
    1595       <div id="rfc.figure.u.24"></div><pre class="inline"><span id="rfc.iref.g.26"></span>  <a href="#rule.delta-seconds" class="smpl">delta-seconds</a>  = 1*<a href="#notation" class="smpl">DIGIT</a>
    1596 </pre><p id="rfc.section.10.7.p.5">Two examples of its use are</p>
     1600      <div id="rfc.figure.u.24"></div><pre class="inline"><span id="rfc.iref.g.26"></span>  <a href="#rule.delta-seconds" class="smpl">delta-seconds</a>  = 1*<a href="#core.rules" class="smpl">DIGIT</a>
     1601</pre><p id="rfc.section.9.7.p.5">Two examples of its use are</p>
    15971602      <div id="rfc.figure.u.25"></div><pre class="text">  Retry-After: Fri, 31 Dec 1999 23:59:59 GMT
    15981603  Retry-After: 120
    1599 </pre><p id="rfc.section.10.7.p.7">In the latter example, the delay is 2 minutes.</p>
     1604</pre><p id="rfc.section.9.7.p.7">In the latter example, the delay is 2 minutes.</p>
    16001605      <div id="rfc.iref.s.43"></div>
    16011606      <div id="rfc.iref.h.9"></div>
    1602       <h2 id="rfc.section.10.8"><a href="#rfc.section.10.8">10.8</a>&nbsp;<a id="header.server" href="#header.server">Server</a></h2>
    1603       <p id="rfc.section.10.8.p.1">The response-header field "Server" contains information about the software used by the origin server to handle the request.
     1607      <h2 id="rfc.section.9.8"><a href="#rfc.section.9.8">9.8</a>&nbsp;<a id="header.server" href="#header.server">Server</a></h2>
     1608      <p id="rfc.section.9.8.p.1">The response-header field "Server" contains information about the software used by the origin server to handle the request.
    16041609         The field can contain multiple product tokens (<a href="p1-messaging.html#product.tokens" title="Product Tokens">Section 3.4</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>) and comments identifying the server and any significant subproducts. The product tokens are listed in order of their significance
    16051610         for identifying the application.
    16061611      </p>
    1607       <div id="rfc.figure.u.26"></div><pre class="inline"><span id="rfc.iref.g.27"></span><span id="rfc.iref.g.28"></span>  <a href="#header.server" class="smpl">Server</a>         = "Server" ":" <a href="#notation" class="smpl">OWS</a> <a href="#header.server" class="smpl">Server-v</a>
     1612      <div id="rfc.figure.u.26"></div><pre class="inline"><span id="rfc.iref.g.27"></span><span id="rfc.iref.g.28"></span>  <a href="#header.server" class="smpl">Server</a>         = "Server" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.server" class="smpl">Server-v</a>
    16081613  <a href="#header.server" class="smpl">Server-v</a>       = <a href="#abnf.dependencies" class="smpl">product</a>
    1609                    *( <a href="#notation" class="smpl">RWS</a> ( <a href="#abnf.dependencies" class="smpl">product</a> / <a href="#notation" class="smpl">comment</a> ) )
    1610 </pre><p id="rfc.section.10.8.p.3">Example:</p>
     1614                   *( <a href="#core.rules" class="smpl">RWS</a> ( <a href="#abnf.dependencies" class="smpl">product</a> / <a href="#core.rules" class="smpl">comment</a> ) )
     1615</pre><p id="rfc.section.9.8.p.3">Example:</p>
    16111616      <div id="rfc.figure.u.27"></div><pre class="text">  Server: CERN/3.0 libwww/2.17
    1612 </pre><p id="rfc.section.10.8.p.5">If the response is being forwarded through a proxy, the proxy application <em class="bcp14">MUST NOT</em> modify the Server response-header. Instead, it <em class="bcp14">MUST</em> include a Via field (as described in <a href="p1-messaging.html#header.via" title="Via">Section 8.9</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>).
     1617</pre><p id="rfc.section.9.8.p.5">If the response is being forwarded through a proxy, the proxy application <em class="bcp14">MUST NOT</em> modify the Server response-header. Instead, it <em class="bcp14">MUST</em> include a Via field (as described in <a href="p1-messaging.html#header.via" title="Via">Section 8.9</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>).
    16131618      </p>
    16141619      <dl class="empty">
     
    16201625      <div id="rfc.iref.u.1"></div>
    16211626      <div id="rfc.iref.h.10"></div>
    1622       <h2 id="rfc.section.10.9"><a href="#rfc.section.10.9">10.9</a>&nbsp;<a id="header.user-agent" href="#header.user-agent">User-Agent</a></h2>
    1623       <p id="rfc.section.10.9.p.1">The request-header field "User-Agent" contains information about the user agent originating the request. This is for statistical
     1627      <h2 id="rfc.section.9.9"><a href="#rfc.section.9.9">9.9</a>&nbsp;<a id="header.user-agent" href="#header.user-agent">User-Agent</a></h2>
     1628      <p id="rfc.section.9.9.p.1">The request-header field "User-Agent" contains information about the user agent originating the request. This is for statistical
    16241629         purposes, the tracing of protocol violations, and automated recognition of user agents for the sake of tailoring responses
    16251630         to avoid particular user agent limitations. User agents <em class="bcp14">SHOULD</em> include this field with requests. The field can contain multiple product tokens (<a href="p1-messaging.html#product.tokens" title="Product Tokens">Section 3.4</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>) and comments identifying the agent and any subproducts which form a significant part of the user agent. By convention, the
    16261631         product tokens are listed in order of their significance for identifying the application.
    16271632      </p>
    1628       <div id="rfc.figure.u.28"></div><pre class="inline"><span id="rfc.iref.g.29"></span><span id="rfc.iref.g.30"></span>  <a href="#header.user-agent" class="smpl">User-Agent</a>     = "User-Agent" ":" <a href="#notation" class="smpl">OWS</a> <a href="#header.user-agent" class="smpl">User-Agent-v</a>
     1633      <div id="rfc.figure.u.28"></div><pre class="inline"><span id="rfc.iref.g.29"></span><span id="rfc.iref.g.30"></span>  <a href="#header.user-agent" class="smpl">User-Agent</a>     = "User-Agent" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.user-agent" class="smpl">User-Agent-v</a>
    16291634  <a href="#header.user-agent" class="smpl">User-Agent-v</a>   = <a href="#abnf.dependencies" class="smpl">product</a>
    1630                    *( <a href="#notation" class="smpl">RWS</a> ( <a href="#abnf.dependencies" class="smpl">product</a> / <a href="#notation" class="smpl">comment</a> ) )
    1631 </pre><p id="rfc.section.10.9.p.3">Example:</p>
     1635                   *( <a href="#core.rules" class="smpl">RWS</a> ( <a href="#abnf.dependencies" class="smpl">product</a> / <a href="#core.rules" class="smpl">comment</a> ) )
     1636</pre><p id="rfc.section.9.9.p.3">Example:</p>
    16321637      <div id="rfc.figure.u.29"></div><pre class="text">  User-Agent: CERN-LineMode/2.15 libwww/2.17b3
    1633 </pre><h1 id="rfc.section.11"><a href="#rfc.section.11">11.</a>&nbsp;<a id="IANA.considerations" href="#IANA.considerations">IANA Considerations</a></h1>
    1634       <h2 id="rfc.section.11.1"><a href="#rfc.section.11.1">11.1</a>&nbsp;<a id="method.registration" href="#method.registration">Method Registry</a></h2>
    1635       <p id="rfc.section.11.1.p.1">The registration procedure for HTTP Methods is defined by <a href="#method.registry" title="Method Registry">Section&nbsp;3.1</a> of this document.
    1636       </p>
    1637       <p id="rfc.section.11.1.p.2">The HTTP Method Registry located at &lt;<a href="http://www.iana.org/assignments/http-methods">http://www.iana.org/assignments/http-methods</a>&gt; should be populated with the registrations below:
     1638</pre><h1 id="rfc.section.10"><a href="#rfc.section.10">10.</a>&nbsp;<a id="IANA.considerations" href="#IANA.considerations">IANA Considerations</a></h1>
     1639      <h2 id="rfc.section.10.1"><a href="#rfc.section.10.1">10.1</a>&nbsp;<a id="method.registration" href="#method.registration">Method Registry</a></h2>
     1640      <p id="rfc.section.10.1.p.1">The registration procedure for HTTP Methods is defined by <a href="#method.registry" title="Method Registry">Section&nbsp;2.1</a> of this document.
     1641      </p>
     1642      <p id="rfc.section.10.1.p.2">The HTTP Method Registry located at &lt;<a href="http://www.iana.org/assignments/http-methods">http://www.iana.org/assignments/http-methods</a>&gt; should be populated with the registrations below:
    16381643      </p>
    16391644      <div id="rfc.table.1">
     
    16511656                  <td>CONNECT</td>
    16521657                  <td>no</td>
    1653                   <td> <a href="#CONNECT" id="rfc.xref.CONNECT.2" title="CONNECT">Section&nbsp;8.9</a>
     1658                  <td> <a href="#CONNECT" id="rfc.xref.CONNECT.2" title="CONNECT">Section&nbsp;7.9</a>
    16541659                  </td>
    16551660               </tr>
     
    16571662                  <td>DELETE</td>
    16581663                  <td>no</td>
    1659                   <td> <a href="#DELETE" id="rfc.xref.DELETE.2" title="DELETE">Section&nbsp;8.7</a>
     1664                  <td> <a href="#DELETE" id="rfc.xref.DELETE.2" title="DELETE">Section&nbsp;7.7</a>
    16601665                  </td>
    16611666               </tr>
     
    16631668                  <td>GET</td>
    16641669                  <td>yes</td>
    1665                   <td> <a href="#GET" id="rfc.xref.GET.2" title="GET">Section&nbsp;8.3</a>
     1670                  <td> <a href="#GET" id="rfc.xref.GET.2" title="GET">Section&nbsp;7.3</a>
    16661671                  </td>
    16671672               </tr>
     
    16691674                  <td>HEAD</td>
    16701675                  <td>yes</td>
    1671                   <td> <a href="#HEAD" id="rfc.xref.HEAD.2" title="HEAD">Section&nbsp;8.4</a>
     1676                  <td> <a href="#HEAD" id="rfc.xref.HEAD.2" title="HEAD">Section&nbsp;7.4</a>
    16721677                  </td>
    16731678               </tr>
     
    16751680                  <td>OPTIONS</td>
    16761681                  <td>yes</td>
    1677                   <td> <a href="#OPTIONS" id="rfc.xref.OPTIONS.3" title="OPTIONS">Section&nbsp;8.2</a>
     1682                  <td> <a href="#OPTIONS" id="rfc.xref.OPTIONS.3" title="OPTIONS">Section&nbsp;7.2</a>
    16781683                  </td>
    16791684               </tr>
     
    16811686                  <td>POST</td>
    16821687                  <td>no</td>
    1683                   <td> <a href="#POST" id="rfc.xref.POST.2" title="POST">Section&nbsp;8.5</a>
     1688                  <td> <a href="#POST" id="rfc.xref.POST.2" title="POST">Section&nbsp;7.5</a>
    16841689                  </td>
    16851690               </tr>
     
    16871692                  <td>PUT</td>
    16881693                  <td>no</td>
    1689                   <td> <a href="#PUT" id="rfc.xref.PUT.2" title="PUT">Section&nbsp;8.6</a>
     1694                  <td> <a href="#PUT" id="rfc.xref.PUT.2" title="PUT">Section&nbsp;7.6</a>
    16901695                  </td>
    16911696               </tr>
     
    16931698                  <td>TRACE</td>
    16941699                  <td>yes</td>
    1695                   <td> <a href="#TRACE" id="rfc.xref.TRACE.3" title="TRACE">Section&nbsp;8.8</a>
     1700                  <td> <a href="#TRACE" id="rfc.xref.TRACE.3" title="TRACE">Section&nbsp;7.8</a>
    16961701                  </td>
    16971702               </tr>
     
    16991704         </table>
    17001705      </div>
    1701       <h2 id="rfc.section.11.2"><a href="#rfc.section.11.2">11.2</a>&nbsp;<a id="status.code.registration" href="#status.code.registration">Status Code Registry</a></h2>
    1702       <p id="rfc.section.11.2.p.1">The registration procedure for HTTP Status Codes -- previously defined in <a href="http://tools.ietf.org/html/rfc2817#section-7.1">Section 7.1</a> of <a href="#RFC2817" id="rfc.xref.RFC2817.2"><cite title="Upgrading to TLS Within HTTP/1.1">[RFC2817]</cite></a> -- is now defined by <a href="#status.code.registry" title="Status Code Registry">Section&nbsp;5.1</a> of this document.
    1703       </p>
    1704       <p id="rfc.section.11.2.p.2">The HTTP Status Code Registry located at &lt;<a href="http://www.iana.org/assignments/http-status-codes">http://www.iana.org/assignments/http-status-codes</a>&gt; should be updated with the registrations below:
     1706      <h2 id="rfc.section.10.2"><a href="#rfc.section.10.2">10.2</a>&nbsp;<a id="status.code.registration" href="#status.code.registration">Status Code Registry</a></h2>
     1707      <p id="rfc.section.10.2.p.1">The registration procedure for HTTP Status Codes -- previously defined in <a href="http://tools.ietf.org/html/rfc2817#section-7.1">Section 7.1</a> of <a href="#RFC2817" id="rfc.xref.RFC2817.2"><cite title="Upgrading to TLS Within HTTP/1.1">[RFC2817]</cite></a> -- is now defined by <a href="#status.code.registry" title="Status Code Registry">Section&nbsp;4.1</a> of this document.
     1708      </p>
     1709      <p id="rfc.section.10.2.p.2">The HTTP Status Code Registry located at &lt;<a href="http://www.iana.org/assignments/http-status-codes">http://www.iana.org/assignments/http-status-codes</a>&gt; should be updated with the registrations below:
    17051710      </p>
    17061711      <div id="rfc.table.2">
     
    17181723                  <td>100</td>
    17191724                  <td>Continue</td>
    1720                   <td> <a href="#status.100" id="rfc.xref.status.100.2" title="100 Continue">Section&nbsp;9.1.1</a>
     1725                  <td> <a href="#status.100" id="rfc.xref.status.100.2" title="100 Continue">Section&nbsp;8.1.1</a>
    17211726                  </td>
    17221727               </tr>
     
    17241729                  <td>101</td>
    17251730                  <td>Switching Protocols</td>
    1726                   <td> <a href="#status.101" id="rfc.xref.status.101.2" title="101 Switching Protocols">Section&nbsp;9.1.2</a>
     1731                  <td> <a href="#status.101" id="rfc.xref.status.101.2" title="101 Switching Protocols">Section&nbsp;8.1.2</a>
    17271732                  </td>
    17281733               </tr>
     
    17301735                  <td>200</td>
    17311736                  <td>OK</td>
    1732                   <td> <a href="#status.200" id="rfc.xref.status.200.2" title="200 OK">Section&nbsp;9.2.1</a>
     1737                  <td> <a href="#status.200" id="rfc.xref.status.200.2" title="200 OK">Section&nbsp;8.2.1</a>
    17331738                  </td>
    17341739               </tr>
     
    17361741                  <td>201</td>
    17371742                  <td>Created</td>
    1738                   <td> <a href="#status.201" id="rfc.xref.status.201.2" title="201 Created">Section&nbsp;9.2.2</a>
     1743                  <td> <a href="#status.201" id="rfc.xref.status.201.2" title="201 Created">Section&nbsp;8.2.2</a>
    17391744                  </td>
    17401745               </tr>
     
    17421747                  <td>202</td>
    17431748                  <td>Accepted</td>
    1744                   <td> <a href="#status.202" id="rfc.xref.status.202.2" title="202 Accepted">Section&nbsp;9.2.3</a>
     1749                  <td> <a href="#status.202" id="rfc.xref.status.202.2" title="202 Accepted">Section&nbsp;8.2.3</a>
    17451750                  </td>
    17461751               </tr>
     
    17481753                  <td>203</td>
    17491754                  <td>Non-Authoritative Information</td>
    1750                   <td> <a href="#status.203" id="rfc.xref.status.203.2" title="203 Non-Authoritative Information">Section&nbsp;9.2.4</a>
     1755                  <td> <a href="#status.203" id="rfc.xref.status.203.2" title="203 Non-Authoritative Information">Section&nbsp;8.2.4</a>
    17511756                  </td>
    17521757               </tr>
     
    17541759                  <td>204</td>
    17551760                  <td>No Content</td>
    1756                   <td> <a href="#status.204" id="rfc.xref.status.204.2" title="204 No Content">Section&nbsp;9.2.5</a>
     1761                  <td> <a href="#status.204" id="rfc.xref.status.204.2" title="204 No Content">Section&nbsp;8.2.5</a>
    17571762                  </td>
    17581763               </tr>
     
    17601765                  <td>205</td>
    17611766                  <td>Reset Content</td>
    1762                   <td> <a href="#status.205" id="rfc.xref.status.205.2" title="205 Reset Content">Section&nbsp;9.2.6</a>
     1767                  <td> <a href="#status.205" id="rfc.xref.status.205.2" title="205 Reset Content">Section&nbsp;8.2.6</a>
    17631768                  </td>
    17641769               </tr>
     
    17661771                  <td>206</td>
    17671772                  <td>Partial Content</td>
    1768                   <td> <a href="#status.206" id="rfc.xref.status.206.2" title="206 Partial Content">Section&nbsp;9.2.7</a>
     1773                  <td> <a href="#status.206" id="rfc.xref.status.206.2" title="206 Partial Content">Section&nbsp;8.2.7</a>
    17691774                  </td>
    17701775               </tr>
     
    17721777                  <td>300</td>
    17731778                  <td>Multiple Choices</td>
    1774                   <td> <a href="#status.300" id="rfc.xref.status.300.2" title="300 Multiple Choices">Section&nbsp;9.3.1</a>
     1779                  <td> <a href="#status.300" id="rfc.xref.status.300.2" title="300 Multiple Choices">Section&nbsp;8.3.1</a>
    17751780                  </td>
    17761781               </tr>
     
    17781783                  <td>301</td>
    17791784                  <td>Moved Permanently</td>
    1780                   <td> <a href="#status.301" id="rfc.xref.status.301.2" title="301 Moved Permanently">Section&nbsp;9.3.2</a>
     1785                  <td> <a href="#status.301" id="rfc.xref.status.301.2" title="301 Moved Permanently">Section&nbsp;8.3.2</a>
    17811786                  </td>
    17821787               </tr>
     
    17841789                  <td>302</td>
    17851790                  <td>Found</td>
    1786                   <td> <a href="#status.302" id="rfc.xref.status.302.2" title="302 Found">Section&nbsp;9.3.3</a>
     1791                  <td> <a href="#status.302" id="rfc.xref.status.302.2" title="302 Found">Section&nbsp;8.3.3</a>
    17871792                  </td>
    17881793               </tr>
     
    17901795                  <td>303</td>
    17911796                  <td>See Other</td>
    1792                   <td> <a href="#status.303" id="rfc.xref.status.303.2" title="303 See Other">Section&nbsp;9.3.4</a>
     1797                  <td> <a href="#status.303" id="rfc.xref.status.303.2" title="303 See Other">Section&nbsp;8.3.4</a>
    17931798                  </td>
    17941799               </tr>
     
    17961801                  <td>304</td>
    17971802                  <td>Not Modified</td>
    1798                   <td> <a href="#status.304" id="rfc.xref.status.304.2" title="304 Not Modified">Section&nbsp;9.3.5</a>
     1803                  <td> <a href="#status.304" id="rfc.xref.status.304.2" title="304 Not Modified">Section&nbsp;8.3.5</a>
    17991804                  </td>
    18001805               </tr>
     
    18021807                  <td>305</td>
    18031808                  <td>Use Proxy</td>
    1804                   <td> <a href="#status.305" id="rfc.xref.status.305.2" title="305 Use Proxy">Section&nbsp;9.3.6</a>
     1809                  <td> <a href="#status.305" id="rfc.xref.status.305.2" title="305 Use Proxy">Section&nbsp;8.3.6</a>
    18051810                  </td>
    18061811               </tr>
     
    18081813                  <td>306</td>
    18091814                  <td>(Unused)</td>
    1810                   <td> <a href="#status.306" id="rfc.xref.status.306.1" title="306 (Unused)">Section&nbsp;9.3.7</a>
     1815                  <td> <a href="#status.306" id="rfc.xref.status.306.1" title="306 (Unused)">Section&nbsp;8.3.7</a>
    18111816                  </td>
    18121817               </tr>
     
    18141819                  <td>307</td>
    18151820                  <td>Temporary Redirect</td>
    1816                   <td> <a href="#status.307" id="rfc.xref.status.307.2" title="307 Temporary Redirect">Section&nbsp;9.3.8</a>
     1821                  <td> <a href="#status.307" id="rfc.xref.status.307.2" title="307 Temporary Redirect">Section&nbsp;8.3.8</a>
    18171822                  </td>
    18181823               </tr>
     
    18201825                  <td>400</td>
    18211826                  <td>Bad Request</td>
    1822                   <td> <a href="#status.400" id="rfc.xref.status.400.2" title="400 Bad Request">Section&nbsp;9.4.1</a>
     1827                  <td> <a href="#status.400" id="rfc.xref.status.400.2" title="400 Bad Request">Section&nbsp;8.4.1</a>
    18231828                  </td>
    18241829               </tr>
     
    18261831                  <td>401</td>
    18271832                  <td>Unauthorized</td>
    1828                   <td> <a href="#status.401" id="rfc.xref.status.401.2" title="401 Unauthorized">Section&nbsp;9.4.2</a>
     1833                  <td> <a href="#status.401" id="rfc.xref.status.401.2" title="401 Unauthorized">Section&nbsp;8.4.2</a>
    18291834                  </td>
    18301835               </tr>
     
    18321837                  <td>402</td>
    18331838                  <td>Payment Required</td>
    1834                   <td> <a href="#status.402" id="rfc.xref.status.402.2" title="402 Payment Required">Section&nbsp;9.4.3</a>
     1839                  <td> <a href="#status.402" id="rfc.xref.status.402.2" title="402 Payment Required">Section&nbsp;8.4.3</a>
    18351840                  </td>
    18361841               </tr>
     
    18381843                  <td>403</td>
    18391844                  <td>Forbidden</td>
    1840                   <td> <a href="#status.403" id="rfc.xref.status.403.2" title="403 Forbidden">Section&nbsp;9.4.4</a>
     1845                  <td> <a href="#status.403" id="rfc.xref.status.403.2" title="403 Forbidden">Section&nbsp;8.4.4</a>
    18411846                  </td>
    18421847               </tr>
     
    18441849                  <td>404</td>
    18451850                  <td>Not Found</td>
    1846                   <td> <a href="#status.404" id="rfc.xref.status.404.2" title="404 Not Found">Section&nbsp;9.4.5</a>
     1851                  <td> <a href="#status.404" id="rfc.xref.status.404.2" title="404 Not Found">Section&nbsp;8.4.5</a>
    18471852                  </td>
    18481853               </tr>
     
    18501855                  <td>405</td>
    18511856                  <td>Method Not Allowed</td>
    1852                   <td> <a href="#status.405" id="rfc.xref.status.405.2" title="405 Method Not Allowed">Section&nbsp;9.4.6</a>
     1857                  <td> <a href="#status.405" id="rfc.xref.status.405.2" title="405 Method Not Allowed">Section&nbsp;8.4.6</a>
    18531858                  </td>
    18541859               </tr>
     
    18561861                  <td>406</td>
    18571862                  <td>Not Acceptable</td>
    1858                   <td> <a href="#status.406" id="rfc.xref.status.406.2" title="406 Not Acceptable">Section&nbsp;9.4.7</a>
     1863                  <td> <a href="#status.406" id="rfc.xref.status.406.2" title="406 Not Acceptable">Section&nbsp;8.4.7</a>
    18591864                  </td>
    18601865               </tr>
     
    18621867                  <td>407</td>
    18631868                  <td>Proxy Authentication Required</td>
    1864                   <td> <a href="#status.407" id="rfc.xref.status.407.2" title="407 Proxy Authentication Required">Section&nbsp;9.4.8</a>
     1869                  <td> <a href="#status.407" id="rfc.xref.status.407.2" title="407 Proxy Authentication Required">Section&nbsp;8.4.8</a>
    18651870                  </td>
    18661871               </tr>
     
    18681873                  <td>408</td>
    18691874                  <td>Request Timeout</td>
    1870                   <td> <a href="#status.408" id="rfc.xref.status.408.2" title="408 Request Timeout">Section&nbsp;9.4.9</a>
     1875                  <td> <a href="#status.408" id="rfc.xref.status.408.2" title="408 Request Timeout">Section&nbsp;8.4.9</a>
    18711876                  </td>
    18721877               </tr>
     
    18741879                  <td>409</td>
    18751880                  <td>Conflict</td>
    1876                   <td> <a href="#status.409" id="rfc.xref.status.409.2" title="409 Conflict">Section&nbsp;9.4.10</a>
     1881                  <td> <a href="#status.409" id="rfc.xref.status.409.2" title="409 Conflict">Section&nbsp;8.4.10</a>
    18771882                  </td>
    18781883               </tr>
     
    18801885                  <td>410</td>
    18811886                  <td>Gone</td>
    1882                   <td> <a href="#status.410" id="rfc.xref.status.410.2" title="410 Gone">Section&nbsp;9.4.11</a>
     1887                  <td> <a href="#status.410" id="rfc.xref.status.410.2" title="410 Gone">Section&nbsp;8.4.11</a>
    18831888                  </td>
    18841889               </tr>
     
    18861891                  <td>411</td>
    18871892                  <td>Length Required</td>
    1888                   <td> <a href="#status.411" id="rfc.xref.status.411.2" title="411 Length Required">Section&nbsp;9.4.12</a>
     1893                  <td> <a href="#status.411" id="rfc.xref.status.411.2" title="411 Length Required">Section&nbsp;8.4.12</a>
    18891894                  </td>
    18901895               </tr>
     
    18921897                  <td>412</td>
    18931898                  <td>Precondition Failed</td>
    1894                   <td> <a href="#status.412" id="rfc.xref.status.412.2" title="412 Precondition Failed">Section&nbsp;9.4.13</a>
     1899                  <td> <a href="#status.412" id="rfc.xref.status.412.2" title="412 Precondition Failed">Section&nbsp;8.4.13</a>
    18951900                  </td>
    18961901               </tr>
     
    18981903                  <td>413</td>
    18991904                  <td>Request Entity Too Large</td>
    1900                   <td> <a href="#status.413" id="rfc.xref.status.413.2" title="413 Request Entity Too Large">Section&nbsp;9.4.14</a>
     1905                  <td> <a href="#status.413" id="rfc.xref.status.413.2" title="413 Request Entity Too Large">Section&nbsp;8.4.14</a>
    19011906                  </td>
    19021907               </tr>
     
    19041909                  <td>414</td>
    19051910                  <td>Request-target Too Long</td>
    1906                   <td> <a href="#status.414" id="rfc.xref.status.414.2" title="414 Request-target Too Long">Section&nbsp;9.4.15</a>
     1911                  <td> <a href="#status.414" id="rfc.xref.status.414.2" title="414 Request-target Too Long">Section&nbsp;8.4.15</a>
    19071912                  </td>
    19081913               </tr>
     
    19101915                  <td>415</td>
    19111916                  <td>Unsupported Media Type</td>
    1912                   <td> <a href="#status.415" id="rfc.xref.status.415.2" title="415 Unsupported Media Type">Section&nbsp;9.4.16</a>
     1917                  <td> <a href="#status.415" id="rfc.xref.status.415.2" title="415 Unsupported Media Type">Section&nbsp;8.4.16</a>
    19131918                  </td>
    19141919               </tr>
     
    19161921                  <td>416</td>
    19171922                  <td>Requested Range Not Satisfiable</td>
    1918                   <td> <a href="#status.416" id="rfc.xref.status.416.2" title="416 Requested Range Not Satisfiable">Section&nbsp;9.4.17</a>
     1923                  <td> <a href="#status.416" id="rfc.xref.status.416.2" title="416 Requested Range Not Satisfiable">Section&nbsp;8.4.17</a>
    19191924                  </td>
    19201925               </tr>
     
    19221927                  <td>417</td>
    19231928                  <td>Expectation Failed</td>
    1924                   <td> <a href="#status.417" id="rfc.xref.status.417.2" title="417 Expectation Failed">Section&nbsp;9.4.18</a>
     1929                  <td> <a href="#status.417" id="rfc.xref.status.417.2" title="417 Expectation Failed">Section&nbsp;8.4.18</a>
    19251930                  </td>
    19261931               </tr>
     
    19281933                  <td>500</td>
    19291934                  <td>Internal Server Error</td>
    1930                   <td> <a href="#status.500" id="rfc.xref.status.500.2" title="500 Internal Server Error">Section&nbsp;9.5.1</a>
     1935                  <td> <a href="#status.500" id="rfc.xref.status.500.2" title="500 Internal Server Error">Section&nbsp;8.5.1</a>
    19311936                  </td>
    19321937               </tr>
     
    19341939                  <td>501</td>
    19351940                  <td>Not Implemented</td>
    1936                   <td> <a href="#status.501" id="rfc.xref.status.501.2" title="501 Not Implemented">Section&nbsp;9.5.2</a>
     1941                  <td> <a href="#status.501" id="rfc.xref.status.501.2" title="501 Not Implemented">Section&nbsp;8.5.2</a>
    19371942                  </td>
    19381943               </tr>
     
    19401945                  <td>502</td>
    19411946                  <td>Bad Gateway</td>
    1942                   <td> <a href="#status.502" id="rfc.xref.status.502.2" title="502 Bad Gateway">Section&nbsp;9.5.3</a>
     1947                  <td> <a href="#status.502" id="rfc.xref.status.502.2" title="502 Bad Gateway">Section&nbsp;8.5.3</a>
    19431948                  </td>
    19441949               </tr>
     
    19461951                  <td>503</td>
    19471952                  <td>Service Unavailable</td>
    1948                   <td> <a href="#status.503" id="rfc.xref.status.503.2" title="503 Service Unavailable">Section&nbsp;9.5.4</a>
     1953                  <td> <a href="#status.503" id="rfc.xref.status.503.2" title="503 Service Unavailable">Section&nbsp;8.5.4</a>
    19491954                  </td>
    19501955               </tr>
     
    19521957                  <td>504</td>
    19531958                  <td>Gateway Timeout</td>
    1954                   <td> <a href="#status.504" id="rfc.xref.status.504.2" title="504 Gateway Timeout">Section&nbsp;9.5.5</a>
     1959                  <td> <a href="#status.504" id="rfc.xref.status.504.2" title="504 Gateway Timeout">Section&nbsp;8.5.5</a>
    19551960                  </td>
    19561961               </tr>
     
    19581963                  <td>505</td>
    19591964                  <td>HTTP Version Not Supported</td>
    1960                   <td> <a href="#status.505" id="rfc.xref.status.505.2" title="505 HTTP Version Not Supported">Section&nbsp;9.5.6</a>
     1965                  <td> <a href="#status.505" id="rfc.xref.status.505.2" title="505 HTTP Version Not Supported">Section&nbsp;8.5.6</a>
    19611966                  </td>
    19621967               </tr>
     
    19641969         </table>
    19651970      </div>
    1966       <h2 id="rfc.section.11.3"><a href="#rfc.section.11.3">11.3</a>&nbsp;<a id="message.header.registration" href="#message.header.registration">Message Header Registration</a></h2>
    1967       <p id="rfc.section.11.3.p.1">The Message Header Registry located at &lt;<a href="http://www.iana.org/assignments/message-headers/message-header-index.html">http://www.iana.org/assignments/message-headers/message-header-index.html</a>&gt; should be updated with the permanent registrations below (see <a href="#RFC3864" id="rfc.xref.RFC3864.1"><cite title="Registration Procedures for Message Header Fields">[RFC3864]</cite></a>):
     1971      <h2 id="rfc.section.10.3"><a href="#rfc.section.10.3">10.3</a>&nbsp;<a id="message.header.registration" href="#message.header.registration">Message Header Registration</a></h2>
     1972      <p id="rfc.section.10.3.p.1">The Message Header Registry located at &lt;<a href="http://www.iana.org/assignments/message-headers/message-header-index.html">http://www.iana.org/assignments/message-headers/message-header-index.html</a>&gt; should be updated with the permanent registrations below (see <a href="#RFC3864" id="rfc.xref.RFC3864.1"><cite title="Registration Procedures for Message Header Fields">[RFC3864]</cite></a>):
    19681973      </p>
    19691974      <div id="rfc.table.3">
     
    19831988                  <td>http</td>
    19841989                  <td>standard</td>
    1985                   <td> <a href="#header.allow" id="rfc.xref.header.allow.3" title="Allow">Section&nbsp;10.1</a>
     1990                  <td> <a href="#header.allow" id="rfc.xref.header.allow.3" title="Allow">Section&nbsp;9.1</a>
    19861991                  </td>
    19871992               </tr>
     
    19901995                  <td>http</td>
    19911996                  <td>standard</td>
    1992                   <td> <a href="#header.expect" id="rfc.xref.header.expect.3" title="Expect">Section&nbsp;10.2</a>
     1997                  <td> <a href="#header.expect" id="rfc.xref.header.expect.3" title="Expect">Section&nbsp;9.2</a>
    19931998                  </td>
    19941999               </tr>
     
    19972002                  <td>http</td>
    19982003                  <td>standard</td>
    1999                   <td> <a href="#header.from" id="rfc.xref.header.from.2" title="From">Section&nbsp;10.3</a>
     2004                  <td> <a href="#header.from" id="rfc.xref.header.from.2" title="From">Section&nbsp;9.3</a>
    20002005                  </td>
    20012006               </tr>
     
    20042009                  <td>http</td>
    20052010                  <td>standard</td>
    2006                   <td> <a href="#header.location" id="rfc.xref.header.location.3" title="Location">Section&nbsp;10.4</a>
     2011                  <td> <a href="#header.location" id="rfc.xref.header.location.3" title="Location">Section&nbsp;9.4</a>
    20072012                  </td>
    20082013               </tr>
     
    20112016                  <td>http</td>
    20122017                  <td>standard</td>
    2013                   <td> <a href="#header.max-forwards" id="rfc.xref.header.max-forwards.3" title="Max-Forwards">Section&nbsp;10.5</a>
     2018                  <td> <a href="#header.max-forwards" id="rfc.xref.header.max-forwards.3" title="Max-Forwards">Section&nbsp;9.5</a>
    20142019                  </td>
    20152020               </tr>
     
    20182023                  <td>http</td>
    20192024                  <td>standard</td>
    2020                   <td> <a href="#header.referer" id="rfc.xref.header.referer.2" title="Referer">Section&nbsp;10.6</a>
     2025                  <td> <a href="#header.referer" id="rfc.xref.header.referer.2" title="Referer">Section&nbsp;9.6</a>
    20212026                  </td>
    20222027               </tr>
     
    20252030                  <td>http</td>
    20262031                  <td>standard</td>
    2027                   <td> <a href="#header.retry-after" id="rfc.xref.header.retry-after.2" title="Retry-After">Section&nbsp;10.7</a>
     2032                  <td> <a href="#header.retry-after" id="rfc.xref.header.retry-after.2" title="Retry-After">Section&nbsp;9.7</a>
    20282033                  </td>
    20292034               </tr>
     
    20322037                  <td>http</td>
    20332038                  <td>standard</td>
    2034                   <td> <a href="#header.server" id="rfc.xref.header.server.2" title="Server">Section&nbsp;10.8</a>
     2039                  <td> <a href="#header.server" id="rfc.xref.header.server.2" title="Server">Section&nbsp;9.8</a>
    20352040                  </td>
    20362041               </tr>
     
    20392044                  <td>http</td>
    20402045                  <td>standard</td>
    2041                   <td> <a href="#header.user-agent" id="rfc.xref.header.user-agent.2" title="User-Agent">Section&nbsp;10.9</a>
     2046                  <td> <a href="#header.user-agent" id="rfc.xref.header.user-agent.2" title="User-Agent">Section&nbsp;9.9</a>
    20422047                  </td>
    20432048               </tr>
     
    20452050         </table>
    20462051      </div>
    2047       <p id="rfc.section.11.3.p.2">The change controller is: "IETF (iesg@ietf.org) - Internet Engineering Task Force".</p>
    2048       <h1 id="rfc.section.12"><a href="#rfc.section.12">12.</a>&nbsp;<a id="security.considerations" href="#security.considerations">Security Considerations</a></h1>
    2049       <p id="rfc.section.12.p.1">This section is meant to inform application developers, information providers, and users of the security limitations in HTTP/1.1
     2052      <p id="rfc.section.10.3.p.2">The change controller is: "IETF (iesg@ietf.org) - Internet Engineering Task Force".</p>
     2053      <h1 id="rfc.section.11"><a href="#rfc.section.11">11.</a>&nbsp;<a id="security.considerations" href="#security.considerations">Security Considerations</a></h1>
     2054      <p id="rfc.section.11.p.1">This section is meant to inform application developers, information providers, and users of the security limitations in HTTP/1.1
    20502055         as described by this document. The discussion does not include definitive solutions to the problems revealed, though it does
    20512056         make some suggestions for reducing security risks.
    20522057      </p>
    2053       <h2 id="rfc.section.12.1"><a href="#rfc.section.12.1">12.1</a>&nbsp;<a id="security.sensitive" href="#security.sensitive">Transfer of Sensitive Information</a></h2>
    2054       <p id="rfc.section.12.1.p.1">Like any generic data transfer protocol, HTTP cannot regulate the content of the data that is transferred, nor is there any
     2058      <h2 id="rfc.section.11.1"><a href="#rfc.section.11.1">11.1</a>&nbsp;<a id="security.sensitive" href="#security.sensitive">Transfer of Sensitive Information</a></h2>
     2059      <p id="rfc.section.11.1.p.1">Like any generic data transfer protocol, HTTP cannot regulate the content of the data that is transferred, nor is there any
    20552060         a priori method of determining the sensitivity of any particular piece of information within the context of any given request.
    20562061         Therefore, applications <em class="bcp14">SHOULD</em> supply as much control over this information as possible to the provider of that information. Four header fields are worth
    20572062         special mention in this context: Server, Via, Referer and From.
    20582063      </p>
    2059       <p id="rfc.section.12.1.p.2">Revealing the specific software version of the server might allow the server machine to become more vulnerable to attacks
     2064      <p id="rfc.section.11.1.p.2">Revealing the specific software version of the server might allow the server machine to become more vulnerable to attacks
    20602065         against software that is known to contain security holes. Implementors <em class="bcp14">SHOULD</em> make the Server header field a configurable option.
    20612066      </p>
    2062       <p id="rfc.section.12.1.p.3">Proxies which serve as a portal through a network firewall <em class="bcp14">SHOULD</em> take special precautions regarding the transfer of header information that identifies the hosts behind the firewall. In particular,
     2067      <p id="rfc.section.11.1.p.3">Proxies which serve as a portal through a network firewall <em class="bcp14">SHOULD</em> take special precautions regarding the transfer of header information that identifies the hosts behind the firewall. In particular,
    20632068         they <em class="bcp14">SHOULD</em> remove, or replace with sanitized versions, any Via fields generated behind the firewall.
    20642069      </p>
    2065       <p id="rfc.section.12.1.p.4">The Referer header allows reading patterns to be studied and reverse links drawn. Although it can be very useful, its power
     2070      <p id="rfc.section.11.1.p.4">The Referer header allows reading patterns to be studied and reverse links drawn. Although it can be very useful, its power
    20662071         can be abused if user details are not separated from the information contained in the Referer. Even when the personal information
    20672072         has been removed, the Referer header might indicate a private document's URI whose publication would be inappropriate.
    20682073      </p>
    2069       <p id="rfc.section.12.1.p.5">The information sent in the From field might conflict with the user's privacy interests or their site's security policy, and
     2074      <p id="rfc.section.11.1.p.5">The information sent in the From field might conflict with the user's privacy interests or their site's security policy, and
    20702075         hence it <em class="bcp14">SHOULD NOT</em> be transmitted without the user being able to disable, enable, and modify the contents of the field. The user <em class="bcp14">MUST</em> be able to set the contents of this field within a user preference or application defaults configuration.
    20712076      </p>
    2072       <p id="rfc.section.12.1.p.6">We suggest, though do not require, that a convenient toggle interface be provided for the user to enable or disable the sending
     2077      <p id="rfc.section.11.1.p.6">We suggest, though do not require, that a convenient toggle interface be provided for the user to enable or disable the sending
    20732078         of From and Referer information.
    20742079      </p>
    2075       <p id="rfc.section.12.1.p.7">The User-Agent (<a href="#header.user-agent" id="rfc.xref.header.user-agent.3" title="User-Agent">Section&nbsp;10.9</a>) or Server (<a href="#header.server" id="rfc.xref.header.server.3" title="Server">Section&nbsp;10.8</a>) header fields can sometimes be used to determine that a specific client or server have a particular security hole which
     2080      <p id="rfc.section.11.1.p.7">The User-Agent (<a href="#header.user-agent" id="rfc.xref.header.user-agent.3" title="User-Agent">Section&nbsp;9.9</a>) or Server (<a href="#header.server" id="rfc.xref.header.server.3" title="Server">Section&nbsp;9.8</a>) header fields can sometimes be used to determine that a specific client or server have a particular security hole which
    20762081         might be exploited. Unfortunately, this same information is often used for other valuable purposes for which HTTP currently
    20772082         has no better mechanism.
    20782083      </p>
    2079       <h2 id="rfc.section.12.2"><a href="#rfc.section.12.2">12.2</a>&nbsp;<a id="encoding.sensitive.information.in.uris" href="#encoding.sensitive.information.in.uris">Encoding Sensitive Information in URIs</a></h2>
    2080       <p id="rfc.section.12.2.p.1">Because the source of a link might be private information or might reveal an otherwise private information source, it is strongly
     2084      <h2 id="rfc.section.11.2"><a href="#rfc.section.11.2">11.2</a>&nbsp;<a id="encoding.sensitive.information.in.uris" href="#encoding.sensitive.information.in.uris">Encoding Sensitive Information in URIs</a></h2>
     2085      <p id="rfc.section.11.2.p.1">Because the source of a link might be private information or might reveal an otherwise private information source, it is strongly
    20812086         recommended that the user be able to select whether or not the Referer field is sent. For example, a browser client could
    20822087         have a toggle switch for browsing openly/anonymously, which would respectively enable/disable the sending of Referer and From
    20832088         information.
    20842089      </p>
    2085       <p id="rfc.section.12.2.p.2">Clients <em class="bcp14">SHOULD NOT</em> include a Referer header field in a (non-secure) HTTP request if the referring page was transferred with a secure protocol.
    2086       </p>
    2087       <p id="rfc.section.12.2.p.3">Authors of services should not use GET-based forms for the submission of sensitive data because that data will be encoded
     2090      <p id="rfc.section.11.2.p.2">Clients <em class="bcp14">SHOULD NOT</em> include a Referer header field in a (non-secure) HTTP request if the referring page was transferred with a secure protocol.
     2091      </p>
     2092      <p id="rfc.section.11.2.p.3">Authors of services should not use GET-based forms for the submission of sensitive data because that data will be encoded
    20882093         in the Request-target. Many existing servers, proxies, and user agents log or display the Request-target in places where it
    20892094         might be visible to third parties. Such services can use POST-based form submission instead.
    20902095      </p>
    2091       <h2 id="rfc.section.12.3"><a href="#rfc.section.12.3">12.3</a>&nbsp;<a id="location.spoofing" href="#location.spoofing">Location Headers and Spoofing</a></h2>
    2092       <p id="rfc.section.12.3.p.1">If a single server supports multiple organizations that do not trust one another, then it <em class="bcp14">MUST</em> check the values of Location and Content-Location headers in responses that are generated under control of said organizations
     2096      <h2 id="rfc.section.11.3"><a href="#rfc.section.11.3">11.3</a>&nbsp;<a id="location.spoofing" href="#location.spoofing">Location Headers and Spoofing</a></h2>
     2097      <p id="rfc.section.11.3.p.1">If a single server supports multiple organizations that do not trust one another, then it <em class="bcp14">MUST</em> check the values of Location and Content-Location headers in responses that are generated under control of said organizations
    20932098         to make sure that they do not attempt to invalidate resources over which they have no authority.
    20942099      </p>
    2095       <h1 id="rfc.section.13"><a href="#rfc.section.13">13.</a>&nbsp;<a id="ack" href="#ack">Acknowledgments</a></h1>
    2096       <h1 id="rfc.references"><a id="rfc.section.14" href="#rfc.section.14">14.</a> References
     2100      <h1 id="rfc.section.12"><a href="#rfc.section.12">12.</a>&nbsp;<a id="ack" href="#ack">Acknowledgments</a></h1>
     2101      <h1 id="rfc.references"><a id="rfc.section.13" href="#rfc.section.13">13.</a> References
    20972102      </h1>
    2098       <h2 id="rfc.references.1"><a href="#rfc.section.14.1" id="rfc.section.14.1">14.1</a> Normative References
     2103      <h2 id="rfc.references.1"><a href="#rfc.section.13.1" id="rfc.section.13.1">13.1</a> Normative References
    20992104      </h2>
    21002105      <table summary="Normative References">             
     
    21352140         </tr>
    21362141      </table>
    2137       <h2 id="rfc.references.2"><a href="#rfc.section.14.2" id="rfc.section.14.2">14.2</a> Informative References
     2142      <h2 id="rfc.references.2"><a href="#rfc.section.13.2" id="rfc.section.13.2">13.2</a> Informative References
    21382143      </h2>
    21392144      <table summary="Informative References">             
     
    21922197      <h1 id="rfc.section.A"><a href="#rfc.section.A">A.</a>&nbsp;<a id="compatibility" href="#compatibility">Compatibility with Previous Versions</a></h1>
    21932198      <h2 id="rfc.section.A.1"><a href="#rfc.section.A.1">A.1</a>&nbsp;<a id="changes.from.rfc.2068" href="#changes.from.rfc.2068">Changes from RFC 2068</a></h2>
    2194       <p id="rfc.section.A.1.p.1">Clarified which error code should be used for inbound server failures (e.g. DNS failures). (<a href="#status.504" id="rfc.xref.status.504.3" title="504 Gateway Timeout">Section&nbsp;9.5.5</a>).
    2195       </p>
    2196       <p id="rfc.section.A.1.p.2">201 (Created) had a race that required an Etag be sent when a resource is first created. (<a href="#status.201" id="rfc.xref.status.201.3" title="201 Created">Section&nbsp;9.2.2</a>).
     2199      <p id="rfc.section.A.1.p.1">Clarified which error code should be used for inbound server failures (e.g. DNS failures). (<a href="#status.504" id="rfc.xref.status.504.3" title="504 Gateway Timeout">Section&nbsp;8.5.5</a>).
     2200      </p>
     2201      <p id="rfc.section.A.1.p.2">201 (Created) had a race that required an Etag be sent when a resource is first created. (<a href="#status.201" id="rfc.xref.status.201.3" title="201 Created">Section&nbsp;8.2.2</a>).
    21972202      </p>
    21982203      <p id="rfc.section.A.1.p.3">Rewrite of message transmission requirements to make it much harder for implementors to get it wrong, as the consequences
     
    22142219      </ol>
    22152220      <p id="rfc.section.A.1.p.4">This change adds the Expect header and 417 status code.</p>
    2216       <p id="rfc.section.A.1.p.5">Clean up confusion between 403 and 404 responses. (Section <a href="#status.403" id="rfc.xref.status.403.3" title="403 Forbidden">9.4.4</a>, <a href="#status.404" id="rfc.xref.status.404.3" title="404 Not Found">9.4.5</a>, and <a href="#status.410" id="rfc.xref.status.410.3" title="410 Gone">9.4.11</a>)
     2221      <p id="rfc.section.A.1.p.5">Clean up confusion between 403 and 404 responses. (Section <a href="#status.403" id="rfc.xref.status.403.3" title="403 Forbidden">8.4.4</a>, <a href="#status.404" id="rfc.xref.status.404.3" title="404 Not Found">8.4.5</a>, and <a href="#status.410" id="rfc.xref.status.410.3" title="410 Gone">8.4.11</a>)
    22172222      </p>
    22182223      <p id="rfc.section.A.1.p.6">The PATCH<span id="rfc.iref.p.3"></span><span id="rfc.iref.m.10"></span>, LINK<span id="rfc.iref.l.2"></span><span id="rfc.iref.m.11"></span>, UNLINK<span id="rfc.iref.u.2"></span><span id="rfc.iref.m.12"></span> methods were defined but not commonly implemented in previous versions of this specification. See <a href="http://tools.ietf.org/html/rfc2068#section-19.6.1">Section 19.6.1</a> of <a href="#RFC2068" id="rfc.xref.RFC2068.2"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a>.
    22192224      </p>
    22202225      <h2 id="rfc.section.A.2"><a href="#rfc.section.A.2">A.2</a>&nbsp;<a id="changes.from.rfc.2616" href="#changes.from.rfc.2616">Changes from RFC 2616</a></h2>
    2221       <p id="rfc.section.A.2.p.1">This document takes over the Status Code Registry, previously defined in <a href="http://tools.ietf.org/html/rfc2817#section-7.1">Section 7.1</a> of <a href="#RFC2817" id="rfc.xref.RFC2817.3"><cite title="Upgrading to TLS Within HTTP/1.1">[RFC2817]</cite></a>. (<a href="#status.code.registry" title="Status Code Registry">Section&nbsp;5.1</a>)
    2222       </p>
    2223       <p id="rfc.section.A.2.p.2">Clarify definition of POST. (<a href="#POST" id="rfc.xref.POST.3" title="POST">Section&nbsp;8.5</a>)
     2226      <p id="rfc.section.A.2.p.1">This document takes over the Status Code Registry, previously defined in <a href="http://tools.ietf.org/html/rfc2817#section-7.1">Section 7.1</a> of <a href="#RFC2817" id="rfc.xref.RFC2817.3"><cite title="Upgrading to TLS Within HTTP/1.1">[RFC2817]</cite></a>. (<a href="#status.code.registry" title="Status Code Registry">Section&nbsp;4.1</a>)
     2227      </p>
     2228      <p id="rfc.section.A.2.p.2">Clarify definition of POST. (<a href="#POST" id="rfc.xref.POST.3" title="POST">Section&nbsp;7.5</a>)
    22242229      </p>
    22252230      <p id="rfc.section.A.2.p.3">Failed to consider that there are many other request methods that are safe to automatically redirect, and further that the
    2226          user agent is able to make that determination based on the request method semantics. (Sections <a href="#status.301" id="rfc.xref.status.301.3" title="301 Moved Permanently">9.3.2</a>, <a href="#status.302" id="rfc.xref.status.302.3" title="302 Found">9.3.3</a> and <a href="#status.307" id="rfc.xref.status.307.3" title="307 Temporary Redirect">9.3.8</a>)
     2231         user agent is able to make that determination based on the request method semantics. (Sections <a href="#status.301" id="rfc.xref.status.301.3" title="301 Moved Permanently">8.3.2</a>, <a href="#status.302" id="rfc.xref.status.302.3" title="302 Found">8.3.3</a> and <a href="#status.307" id="rfc.xref.status.307.3" title="307 Temporary Redirect">8.3.8</a>)
    22272232      </p>
    22282233      <p id="rfc.section.A.2.p.4">Deprecate 305 Use Proxy status code, because user agents did not implement it. It used to indicate that the requested resource
    22292234         must be accessed through the proxy given by the Location field. The Location field gave the URI of the proxy. The recipient
    2230          was expected to repeat this single request via the proxy. (<a href="#status.305" id="rfc.xref.status.305.3" title="305 Use Proxy">Section&nbsp;9.3.6</a>)
     2235         was expected to repeat this single request via the proxy. (<a href="#status.305" id="rfc.xref.status.305.3" title="305 Use Proxy">Section&nbsp;8.3.6</a>)
    22312236      </p>
    22322237      <p id="rfc.section.A.2.p.5">Reclassify Allow header as response header, removing the option to specify it in a PUT request. Relax the server requirement
    2233          on the contents of the Allow header and remove requirement on clients to always trust the header value. (<a href="#header.allow" id="rfc.xref.header.allow.4" title="Allow">Section&nbsp;10.1</a>)
     2238         on the contents of the Allow header and remove requirement on clients to always trust the header value. (<a href="#header.allow" id="rfc.xref.header.allow.4" title="Allow">Section&nbsp;9.1</a>)
    22342239      </p>
    22352240      <p id="rfc.section.A.2.p.6">Correct syntax of Location header to allow fragment, as referred symbol wasn't what was expected, and add some clarifications
    2236          as to when it would not be appropriate. (<a href="#header.location" id="rfc.xref.header.location.4" title="Location">Section&nbsp;10.4</a>)
     2241         as to when it would not be appropriate. (<a href="#header.location" id="rfc.xref.header.location.4" title="Location">Section&nbsp;9.4</a>)
    22372242      </p>
    22382243      <p id="rfc.section.A.2.p.7">In the description of the Server header, the Via field was described as a SHOULD. The requirement was and is stated correctly
    2239          in the description of the Via header in <a href="p1-messaging.html#header.via" title="Via">Section 8.9</a> of <a href="#Part1" id="rfc.xref.Part1.33"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>. (<a href="#header.server" id="rfc.xref.header.server.4" title="Server">Section&nbsp;10.8</a>)
     2244         in the description of the Via header in <a href="p1-messaging.html#header.via" title="Via">Section 8.9</a> of <a href="#Part1" id="rfc.xref.Part1.33"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>. (<a href="#header.server" id="rfc.xref.header.server.4" title="Server">Section&nbsp;9.8</a>)
    22402245      </p>
    22412246      <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a>&nbsp;<a id="collected.abnf" href="#collected.abnf">Collected ABNF</a></h1>
    2242       <div id="rfc.figure.u.30"></div> <pre class="inline">Accept = &lt;Accept, defined in [Part3], Section 6.1&gt;
    2243 Accept-Charset = &lt;Accept-Charset, defined in [Part3], Section 6.2&gt;
    2244 Accept-Encoding = &lt;Accept-Encoding, defined in [Part3], Section 6.3&gt;
    2245 Accept-Language = &lt;Accept-Language, defined in [Part3], Section 6.4&gt;
    2246 Accept-Ranges = &lt;Accept-Ranges, defined in [Part5], Section 6.1&gt;
    2247 Age = &lt;Age, defined in [Part6], Section 16.1&gt;
     2247      <div id="rfc.figure.u.30"></div> <pre class="inline">Accept = &lt;Accept, defined in [Part3], Section 5.1&gt;
     2248Accept-Charset = &lt;Accept-Charset, defined in [Part3], Section 5.2&gt;
     2249Accept-Encoding = &lt;Accept-Encoding, defined in [Part3], Section 5.3&gt;
     2250Accept-Language = &lt;Accept-Language, defined in [Part3], Section 5.4&gt;
     2251Accept-Ranges = &lt;Accept-Ranges, defined in [Part5], Section 5.1&gt;
     2252Age = &lt;Age, defined in [Part6], Section 15.1&gt;
    22482253Allow = "Allow:" OWS Allow-v
    22492254Allow-v = [ ( "," / Method ) *( OWS "," [ OWS Method ] ) ]
    2250 Authorization = &lt;Authorization, defined in [Part7], Section 4.1&gt;
     2255Authorization = &lt;Authorization, defined in [Part7], Section 3.1&gt;
    22512256CR = &lt;CR, defined in [Part1], Section 1.2.2&gt;
    22522257DIGIT = &lt;DIGIT, defined in [Part1], Section 1.2.2&gt;
    2253 ETag = &lt;ETag, defined in [Part4], Section 7.1&gt;
     2258ETag = &lt;ETag, defined in [Part4], Section 6.1&gt;
    22542259Expect = "Expect:" OWS Expect-v
    22552260Expect-v = *( "," OWS ) expectation *( OWS "," [ OWS expectation ] )
     
    22582263HTTP-date = &lt;HTTP-date, defined in [Part1], Section 3.2.1&gt;
    22592264Host = &lt;Host, defined in [Part1], Section 2.1&gt;
    2260 If-Match = &lt;If-Match, defined in [Part4], Section 7.2&gt;
     2265If-Match = &lt;If-Match, defined in [Part4], Section 6.2&gt;
    22612266If-Modified-Since = &lt;If-Modified-Since, defined in [Part4], Section
    2262  7.3&gt;
    2263 If-None-Match = &lt;If-None-Match, defined in [Part4], Section 7.4&gt;
    2264 If-Range = &lt;If-Range, defined in [Part5], Section 6.3&gt;
     2267 6.3&gt;
     2268If-None-Match = &lt;If-None-Match, defined in [Part4], Section 6.4&gt;
     2269If-Range = &lt;If-Range, defined in [Part5], Section 5.3&gt;
    22652270If-Unmodified-Since = &lt;If-Unmodified-Since, defined in [Part4],
    2266  Section 7.5&gt;
     2271 Section 6.5&gt;
    22672272LF = &lt;LF, defined in [Part1], Section 1.2.2&gt;
    22682273Location = "Location:" OWS Location-v
     
    22752280OWS = &lt;OWS, defined in [Part1], Section 1.2.2&gt;
    22762281Proxy-Authenticate = &lt;Proxy-Authenticate, defined in [Part7], Section
    2277  4.2&gt;
     2282 3.2&gt;
    22782283Proxy-Authorization = &lt;Proxy-Authorization, defined in [Part7],
    2279  Section 4.3&gt;
     2284 Section 3.3&gt;
    22802285RWS = &lt;RWS, defined in [Part1], Section 1.2.2&gt;
    2281 Range = &lt;Range, defined in [Part5], Section 6.4&gt;
     2286Range = &lt;Range, defined in [Part5], Section 5.4&gt;
    22822287Reason-Phrase = *( WSP / VCHAR / obs-text )
    22832288Referer = "Referer:" OWS Referer-v
     
    22972302User-Agent-v = product *( RWS ( product / comment ) )
    22982303VCHAR = &lt;VCHAR, defined in [Part1], Section 1.2.2&gt;
    2299 Vary = &lt;Vary, defined in [Part6], Section 16.5&gt;
     2304Vary = &lt;Vary, defined in [Part6], Section 15.5&gt;
    23002305WSP = &lt;WSP, defined in [Part1], Section 1.2.2&gt;
    23012306WWW-Authenticate = &lt;WWW-Authenticate, defined in [Part7], Section
    2302  4.4&gt;
     2307 3.4&gt;
    23032308absolute-URI = &lt;absolute-URI, defined in [Part1], Section 2.1&gt;
    23042309comment = &lt;comment, defined in [Part1], Section 1.2.2&gt;
     
    24442449      </p>
    24452450      <ul>
    2446          <li>Add appendix containing collected and expanded ABNF.</li>
     2451         <li>Add appendix containing collected and expanded ABNF, reorganize ABNF introduction.</li>
    24472452      </ul>
    24482453      <h1><a id="rfc.copyright" href="#rfc.copyright">Full Copyright Statement</a></h1>
     
    24762481         <ul class="ind">
    24772482            <li class="indline0"><a id="rfc.index.1" href="#rfc.index.1"><b>1</b></a><ul class="ind">
    2478                   <li class="indline1">100 Continue (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.100.1">5</a>, <a class="iref" href="#rfc.iref.25"><b>9.1.1</b></a>, <a class="iref" href="#rfc.xref.status.100.2">11.2</a></li>
    2479                   <li class="indline1">101 Switching Protocols (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.101.1">5</a>, <a class="iref" href="#rfc.iref.26"><b>9.1.2</b></a>, <a class="iref" href="#rfc.xref.status.101.2">11.2</a></li>
     2483                  <li class="indline1">100 Continue (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.100.1">4</a>, <a class="iref" href="#rfc.iref.25"><b>8.1.1</b></a>, <a class="iref" href="#rfc.xref.status.100.2">10.2</a></li>
     2484                  <li class="indline1">101 Switching Protocols (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.101.1">4</a>, <a class="iref" href="#rfc.iref.26"><b>8.1.2</b></a>, <a class="iref" href="#rfc.xref.status.101.2">10.2</a></li>
    24802485               </ul>
    24812486            </li>
    24822487            <li class="indline0"><a id="rfc.index.2" href="#rfc.index.2"><b>2</b></a><ul class="ind">
    2483                   <li class="indline1">200 OK (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.200.1">5</a>, <a class="iref" href="#rfc.iref.27"><b>9.2.1</b></a>, <a class="iref" href="#rfc.xref.status.200.2">11.2</a></li>
    2484                   <li class="indline1">201 Created (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.201.1">5</a>, <a class="iref" href="#rfc.iref.28"><b>9.2.2</b></a>, <a class="iref" href="#rfc.xref.status.201.2">11.2</a>, <a class="iref" href="#rfc.xref.status.201.3">A.1</a></li>
    2485                   <li class="indline1">202 Accepted (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.202.1">5</a>, <a class="iref" href="#rfc.iref.29"><b>9.2.3</b></a>, <a class="iref" href="#rfc.xref.status.202.2">11.2</a></li>
    2486                   <li class="indline1">203 Non-Authoritative Information (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.203.1">5</a>, <a class="iref" href="#rfc.iref.30"><b>9.2.4</b></a>, <a class="iref" href="#rfc.xref.status.203.2">11.2</a></li>
    2487                   <li class="indline1">204 No Content (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.204.1">5</a>, <a class="iref" href="#rfc.iref.31"><b>9.2.5</b></a>, <a class="iref" href="#rfc.xref.status.204.2">11.2</a></li>
    2488                   <li class="indline1">205 Reset Content (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.205.1">5</a>, <a class="iref" href="#rfc.iref.32"><b>9.2.6</b></a>, <a class="iref" href="#rfc.xref.status.205.2">11.2</a></li>
    2489                   <li class="indline1">206 Partial Content (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.206.1">5</a>, <a class="iref" href="#rfc.iref.33"><b>9.2.7</b></a>, <a class="iref" href="#rfc.xref.status.206.2">11.2</a></li>
     2488                  <li class="indline1">200 OK (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.200.1">4</a>, <a class="iref" href="#rfc.iref.27"><b>8.2.1</b></a>, <a class="iref" href="#rfc.xref.status.200.2">10.2</a></li>
     2489                  <li class="indline1">201 Created (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.201.1">4</a>, <a class="iref" href="#rfc.iref.28"><b>8.2.2</b></a>, <a class="iref" href="#rfc.xref.status.201.2">10.2</a>, <a class="iref" href="#rfc.xref.status.201.3">A.1</a></li>
     2490                  <li class="indline1">202 Accepted (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.202.1">4</a>, <a class="iref" href="#rfc.iref.29"><b>8.2.3</b></a>, <a class="iref" href="#rfc.xref.status.202.2">10.2</a></li>
     2491                  <li class="indline1">203 Non-Authoritative Information (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.203.1">4</a>, <a class="iref" href="#rfc.iref.30"><b>8.2.4</b></a>, <a class="iref" href="#rfc.xref.status.203.2">10.2</a></li>
     2492                  <li class="indline1">204 No Content (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.204.1">4</a>, <a class="iref" href="#rfc.iref.31"><b>8.2.5</b></a>, <a class="iref" href="#rfc.xref.status.204.2">10.2</a></li>
     2493                  <li class="indline1">205 Reset Content (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.205.1">4</a>, <a class="iref" href="#rfc.iref.32"><b>8.2.6</b></a>, <a class="iref" href="#rfc.xref.status.205.2">10.2</a></li>
     2494                  <li class="indline1">206 Partial Content (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.206.1">4</a>, <a class="iref" href="#rfc.iref.33"><b>8.2.7</b></a>, <a class="iref" href="#rfc.xref.status.206.2">10.2</a></li>
    24902495               </ul>
    24912496            </li>
    24922497            <li class="indline0"><a id="rfc.index.3" href="#rfc.index.3"><b>3</b></a><ul class="ind">
    2493                   <li class="indline1">300 Multiple Choices (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.300.1">5</a>, <a class="iref" href="#rfc.iref.34"><b>9.3.1</b></a>, <a class="iref" href="#rfc.xref.status.300.2">11.2</a></li>
    2494                   <li class="indline1">301 Moved Permanently (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.301.1">5</a>, <a class="iref" href="#rfc.iref.35"><b>9.3.2</b></a>, <a class="iref" href="#rfc.xref.status.301.2">11.2</a>, <a class="iref" href="#rfc.xref.status.301.3">A.2</a></li>
    2495                   <li class="indline1">302 Found (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.302.1">5</a>, <a class="iref" href="#rfc.iref.36"><b>9.3.3</b></a>, <a class="iref" href="#rfc.xref.status.302.2">11.2</a>, <a class="iref" href="#rfc.xref.status.302.3">A.2</a></li>
    2496                   <li class="indline1">303 See Other (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.303.1">5</a>, <a class="iref" href="#rfc.iref.37"><b>9.3.4</b></a>, <a class="iref" href="#rfc.xref.status.303.2">11.2</a></li>
    2497                   <li class="indline1">304 Not Modified (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.304.1">5</a>, <a class="iref" href="#rfc.iref.38"><b>9.3.5</b></a>, <a class="iref" href="#rfc.xref.status.304.2">11.2</a></li>
    2498                   <li class="indline1">305 Use Proxy (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.305.1">5</a>, <a class="iref" href="#rfc.iref.39"><b>9.3.6</b></a>, <a class="iref" href="#rfc.xref.status.305.2">11.2</a>, <a class="iref" href="#rfc.xref.status.305.3">A.2</a></li>
    2499                   <li class="indline1">306 (Unused) (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.iref.40"><b>9.3.7</b></a>, <a class="iref" href="#rfc.xref.status.306.1">11.2</a></li>
    2500                   <li class="indline1">307 Temporary Redirect (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.307.1">5</a>, <a class="iref" href="#rfc.iref.41"><b>9.3.8</b></a>, <a class="iref" href="#rfc.xref.status.307.2">11.2</a>, <a class="iref" href="#rfc.xref.status.307.3">A.2</a></li>
     2498                  <li class="indline1">300 Multiple Choices (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.300.1">4</a>, <a class="iref" href="#rfc.iref.34"><b>8.3.1</b></a>, <a class="iref" href="#rfc.xref.status.300.2">10.2</a></li>
     2499                  <li class="indline1">301 Moved Permanently (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.301.1">4</a>, <a class="iref" href="#rfc.iref.35"><b>8.3.2</b></a>, <a class="iref" href="#rfc.xref.status.301.2">10.2</a>, <a class="iref" href="#rfc.xref.status.301.3">A.2</a></li>
     2500                  <li class="indline1">302 Found (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.302.1">4</a>, <a class="iref" href="#rfc.iref.36"><b>8.3.3</b></a>, <a class="iref" href="#rfc.xref.status.302.2">10.2</a>, <a class="iref" href="#rfc.xref.status.302.3">A.2</a></li>
     2501                  <li class="indline1">303 See Other (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.303.1">4</a>, <a class="iref" href="#rfc.iref.37"><b>8.3.4</b></a>, <a class="iref" href="#rfc.xref.status.303.2">10.2</a></li>
     2502                  <li class="indline1">304 Not Modified (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.304.1">4</a>, <a class="iref" href="#rfc.iref.38"><b>8.3.5</b></a>, <a class="iref" href="#rfc.xref.status.304.2">10.2</a></li>
     2503                  <li class="indline1">305 Use Proxy (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.305.1">4</a>, <a class="iref" href="#rfc.iref.39"><b>8.3.6</b></a>, <a class="iref" href="#rfc.xref.status.305.2">10.2</a>, <a class="iref" href="#rfc.xref.status.305.3">A.2</a></li>
     2504                  <li class="indline1">306 (Unused) (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.iref.40"><b>8.3.7</b></a>, <a class="iref" href="#rfc.xref.status.306.1">10.2</a></li>
     2505                  <li class="indline1">307 Temporary Redirect (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.307.1">4</a>, <a class="iref" href="#rfc.iref.41"><b>8.3.8</b></a>, <a class="iref" href="#rfc.xref.status.307.2">10.2</a>, <a class="iref" href="#rfc.xref.status.307.3">A.2</a></li>
    25012506               </ul>
    25022507            </li>
    25032508            <li class="indline0"><a id="rfc.index.4" href="#rfc.index.4"><b>4</b></a><ul class="ind">
    2504                   <li class="indline1">400 Bad Request (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.400.1">5</a>, <a class="iref" href="#rfc.iref.42"><b>9.4.1</b></a>, <a class="iref" href="#rfc.xref.status.400.2">11.2</a></li>
    2505                   <li class="indline1">401 Unauthorized (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.401.1">5</a>, <a class="iref" href="#rfc.iref.43"><b>9.4.2</b></a>, <a class="iref" href="#rfc.xref.status.401.2">11.2</a></li>
    2506                   <li class="indline1">402 Payment Required (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.402.1">5</a>, <a class="iref" href="#rfc.iref.44"><b>9.4.3</b></a>, <a class="iref" href="#rfc.xref.status.402.2">11.2</a></li>
    2507                   <li class="indline1">403 Forbidden (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.403.1">5</a>, <a class="iref" href="#rfc.iref.45"><b>9.4.4</b></a>, <a class="iref" href="#rfc.xref.status.403.2">11.2</a>, <a class="iref" href="#rfc.xref.status.403.3">A.1</a></li>
    2508                   <li class="indline1">404 Not Found (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.404.1">5</a>, <a class="iref" href="#rfc.iref.46"><b>9.4.5</b></a>, <a class="iref" href="#rfc.xref.status.404.2">11.2</a>, <a class="iref" href="#rfc.xref.status.404.3">A.1</a></li>
    2509                   <li class="indline1">405 Method Not Allowed (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.405.1">5</a>, <a class="iref" href="#rfc.iref.47"><b>9.4.6</b></a>, <a class="iref" href="#rfc.xref.status.405.2">11.2</a></li>
    2510                   <li class="indline1">406 Not Acceptable (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.406.1">5</a>, <a class="iref" href="#rfc.iref.48"><b>9.4.7</b></a>, <a class="iref" href="#rfc.xref.status.406.2">11.2</a></li>
    2511                   <li class="indline1">407 Proxy Authentication Required (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.407.1">5</a>, <a class="iref" href="#rfc.iref.49"><b>9.4.8</b></a>, <a class="iref" href="#rfc.xref.status.407.2">11.2</a></li>
    2512                   <li class="indline1">408 Request Timeout (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.408.1">5</a>, <a class="iref" href="#rfc.iref.50"><b>9.4.9</b></a>, <a class="iref" href="#rfc.xref.status.408.2">11.2</a></li>
    2513                   <li class="indline1">409 Conflict (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.409.1">5</a>, <a class="iref" href="#rfc.iref.51"><b>9.4.10</b></a>, <a class="iref" href="#rfc.xref.status.409.2">11.2</a></li>
    2514                   <li class="indline1">410 Gone (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.410.1">5</a>, <a class="iref" href="#rfc.iref.52"><b>9.4.11</b></a>, <a class="iref" href="#rfc.xref.status.410.2">11.2</a>, <a class="iref" href="#rfc.xref.status.410.3">A.1</a></li>
    2515                   <li class="indline1">411 Length Required (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.411.1">5</a>, <a class="iref" href="#rfc.iref.53"><b>9.4.12</b></a>, <a class="iref" href="#rfc.xref.status.411.2">11.2</a></li>
    2516                   <li class="indline1">412 Precondition Failed (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.412.1">5</a>, <a class="iref" href="#rfc.iref.54"><b>9.4.13</b></a>, <a class="iref" href="#rfc.xref.status.412.2">11.2</a></li>
    2517                   <li class="indline1">413 Request Entity Too Large (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.413.1">5</a>, <a class="iref" href="#rfc.iref.55"><b>9.4.14</b></a>, <a class="iref" href="#rfc.xref.status.413.2">11.2</a></li>
    2518                   <li class="indline1">414 Request-target Too Long (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.414.1">5</a>, <a class="iref" href="#rfc.iref.56"><b>9.4.15</b></a>, <a class="iref" href="#rfc.xref.status.414.2">11.2</a></li>
    2519                   <li class="indline1">415 Unsupported Media Type (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.415.1">5</a>, <a class="iref" href="#rfc.iref.57"><b>9.4.16</b></a>, <a class="iref" href="#rfc.xref.status.415.2">11.2</a></li>
    2520                   <li class="indline1">416 Requested Range Not Satisfiable (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.416.1">5</a>, <a class="iref" href="#rfc.iref.58"><b>9.4.17</b></a>, <a class="iref" href="#rfc.xref.status.416.2">11.2</a></li>
    2521                   <li class="indline1">417 Expectation Failed (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.417.1">5</a>, <a class="iref" href="#rfc.iref.59"><b>9.4.18</b></a>, <a class="iref" href="#rfc.xref.status.417.2">11.2</a></li>
     2509                  <li class="indline1">400 Bad Request (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.400.1">4</a>, <a class="iref" href="#rfc.iref.42"><b>8.4.1</b></a>, <a class="iref" href="#rfc.xref.status.400.2">10.2</a></li>
     2510                  <li class="indline1">401 Unauthorized (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.401.1">4</a>, <a class="iref" href="#rfc.iref.43"><b>8.4.2</b></a>, <a class="iref" href="#rfc.xref.status.401.2">10.2</a></li>
     2511                  <li class="indline1">402 Payment Required (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.402.1">4</a>, <a class="iref" href="#rfc.iref.44"><b>8.4.3</b></a>, <a class="iref" href="#rfc.xref.status.402.2">10.2</a></li>
     2512                  <li class="indline1">403 Forbidden (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.403.1">4</a>, <a class="iref" href="#rfc.iref.45"><b>8.4.4</b></a>, <a class="iref" href="#rfc.xref.status.403.2">10.2</a>, <a class="iref" href="#rfc.xref.status.403.3">A.1</a></li>
     2513                  <li class="indline1">404 Not Found (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.404.1">4</a>, <a class="iref" href="#rfc.iref.46"><b>8.4.5</b></a>, <a class="iref" href="#rfc.xref.status.404.2">10.2</a>, <a class="iref" href="#rfc.xref.status.404.3">A.1</a></li>
     2514                  <li class="indline1">405 Method Not Allowed (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.405.1">4</a>, <a class="iref" href="#rfc.iref.47"><b>8.4.6</b></a>, <a class="iref" href="#rfc.xref.status.405.2">10.2</a></li>
     2515                  <li class="indline1">406 Not Acceptable (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.406.1">4</a>, <a class="iref" href="#rfc.iref.48"><b>8.4.7</b></a>, <a class="iref" href="#rfc.xref.status.406.2">10.2</a></li>
     2516                  <li class="indline1">407 Proxy Authentication Required (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.407.1">4</a>, <a class="iref" href="#rfc.iref.49"><b>8.4.8</b></a>, <a class="iref" href="#rfc.xref.status.407.2">10.2</a></li>
     2517                  <li class="indline1">408 Request Timeout (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.408.1">4</a>, <a class="iref" href="#rfc.iref.50"><b>8.4.9</b></a>, <a class="iref" href="#rfc.xref.status.408.2">10.2</a></li>
     2518                  <li class="indline1">409 Conflict (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.409.1">4</a>, <a class="iref" href="#rfc.iref.51"><b>8.4.10</b></a>, <a class="iref" href="#rfc.xref.status.409.2">10.2</a></li>
     2519                  <li class="indline1">410 Gone (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.410.1">4</a>, <a class="iref" href="#rfc.iref.52"><b>8.4.11</b></a>, <a class="iref" href="#rfc.xref.status.410.2">10.2</a>, <a class="iref" href="#rfc.xref.status.410.3">A.1</a></li>
     2520                  <li class="indline1">411 Length Required (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.411.1">4</a>, <a class="iref" href="#rfc.iref.53"><b>8.4.12</b></a>, <a class="iref" href="#rfc.xref.status.411.2">10.2</a></li>
     2521                  <li class="indline1">412 Precondition Failed (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.412.1">4</a>, <a class="iref" href="#rfc.iref.54"><b>8.4.13</b></a>, <a class="iref" href="#rfc.xref.status.412.2">10.2</a></li>
     2522                  <li class="indline1">413 Request Entity Too Large (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.413.1">4</a>, <a class="iref" href="#rfc.iref.55"><b>8.4.14</b></a>, <a class="iref" href="#rfc.xref.status.413.2">10.2</a></li>
     2523                  <li class="indline1">414 Request-target Too Long (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.414.1">4</a>, <a class="iref" href="#rfc.iref.56"><b>8.4.15</b></a>, <a class="iref" href="#rfc.xref.status.414.2">10.2</a></li>
     2524                  <li class="indline1">415 Unsupported Media Type (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.415.1">4</a>, <a class="iref" href="#rfc.iref.57"><b>8.4.16</b></a>, <a class="iref" href="#rfc.xref.status.415.2">10.2</a></li>
     2525                  <li class="indline1">416 Requested Range Not Satisfiable (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.416.1">4</a>, <a class="iref" href="#rfc.iref.58"><b>8.4.17</b></a>, <a class="iref" href="#rfc.xref.status.416.2">10.2</a></li>
     2526                  <li class="indline1">417 Expectation Failed (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.417.1">4</a>, <a class="iref" href="#rfc.iref.59"><b>8.4.18</b></a>, <a class="iref" href="#rfc.xref.status.417.2">10.2</a></li>
    25222527               </ul>
    25232528            </li>
    25242529            <li class="indline0"><a id="rfc.index.5" href="#rfc.index.5"><b>5</b></a><ul class="ind">
    2525                   <li class="indline1">500 Internal Server Error (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.500.1">5</a>, <a class="iref" href="#rfc.iref.60"><b>9.5.1</b></a>, <a class="iref" href="#rfc.xref.status.500.2">11.2</a></li>
    2526                   <li class="indline1">501 Not Implemented (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.501.1">5</a>, <a class="iref" href="#rfc.iref.61"><b>9.5.2</b></a>, <a class="iref" href="#rfc.xref.status.501.2">11.2</a></li>
    2527                   <li class="indline1">502 Bad Gateway (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.502.1">5</a>, <a class="iref" href="#rfc.iref.62"><b>9.5.3</b></a>, <a class="iref" href="#rfc.xref.status.502.2">11.2</a></li>
    2528                   <li class="indline1">503 Service Unavailable (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.503.1">5</a>, <a class="iref" href="#rfc.iref.63"><b>9.5.4</b></a>, <a class="iref" href="#rfc.xref.status.503.2">11.2</a></li>
    2529                   <li class="indline1">504 Gateway Timeout (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.504.1">5</a>, <a class="iref" href="#rfc.iref.64"><b>9.5.5</b></a>, <a class="iref" href="#rfc.xref.status.504.2">11.2</a>, <a class="iref" href="#rfc.xref.status.504.3">A.1</a></li>
    2530                   <li class="indline1">505 HTTP Version Not Supported (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.505.1">5</a>, <a class="iref" href="#rfc.iref.65"><b>9.5.6</b></a>, <a class="iref" href="#rfc.xref.status.505.2">11.2</a></li>
     2530                  <li class="indline1">500 Internal Server Error (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.500.1">4</a>, <a class="iref" href="#rfc.iref.60"><b>8.5.1</b></a>, <a class="iref" href="#rfc.xref.status.500.2">10.2</a></li>
     2531                  <li class="indline1">501 Not Implemented (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.501.1">4</a>, <a class="iref" href="#rfc.iref.61"><b>8.5.2</b></a>, <a class="iref" href="#rfc.xref.status.501.2">10.2</a></li>
     2532                  <li class="indline1">502 Bad Gateway (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.502.1">4</a>, <a class="iref" href="#rfc.iref.62"><b>8.5.3</b></a>, <a class="iref" href="#rfc.xref.status.502.2">10.2</a></li>
     2533                  <li class="indline1">503 Service Unavailable (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.503.1">4</a>, <a class="iref" href="#rfc.iref.63"><b>8.5.4</b></a>, <a class="iref" href="#rfc.xref.status.503.2">10.2</a></li>
     2534                  <li class="indline1">504 Gateway Timeout (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.504.1">4</a>, <a class="iref" href="#rfc.iref.64"><b>8.5.5</b></a>, <a class="iref" href="#rfc.xref.status.504.2">10.2</a>, <a class="iref" href="#rfc.xref.status.504.3">A.1</a></li>
     2535                  <li class="indline1">505 HTTP Version Not Supported (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.505.1">4</a>, <a class="iref" href="#rfc.iref.65"><b>8.5.6</b></a>, <a class="iref" href="#rfc.xref.status.505.2">10.2</a></li>
    25312536               </ul>
    25322537            </li>
    25332538            <li class="indline0"><a id="rfc.index.A" href="#rfc.index.A"><b>A</b></a><ul class="ind">
    2534                   <li class="indline1">Allow header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.allow.1">3</a>, <a class="iref" href="#rfc.xref.header.allow.2">6</a>, <a class="iref" href="#rfc.iref.a.1"><b>10.1</b></a>, <a class="iref" href="#rfc.xref.header.allow.3">11.3</a>, <a class="iref" href="#rfc.xref.header.allow.4">A.2</a></li>
     2539                  <li class="indline1">Allow header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.allow.1">2</a>, <a class="iref" href="#rfc.xref.header.allow.2">5</a>, <a class="iref" href="#rfc.iref.a.1"><b>9.1</b></a>, <a class="iref" href="#rfc.xref.header.allow.3">10.3</a>, <a class="iref" href="#rfc.xref.header.allow.4">A.2</a></li>
    25352540               </ul>
    25362541            </li>
    25372542            <li class="indline0"><a id="rfc.index.C" href="#rfc.index.C"><b>C</b></a><ul class="ind">
    2538                   <li class="indline1">CONNECT method&nbsp;&nbsp;<a class="iref" href="#rfc.xref.CONNECT.1">3</a>, <a class="iref" href="#rfc.iref.c.1"><b>8.9</b></a>, <a class="iref" href="#rfc.xref.CONNECT.2">11.1</a></li>
     2543                  <li class="indline1">CONNECT method&nbsp;&nbsp;<a class="iref" href="#rfc.xref.CONNECT.1">2</a>, <a class="iref" href="#rfc.iref.c.1"><b>7.9</b></a>, <a class="iref" href="#rfc.xref.CONNECT.2">10.1</a></li>
    25392544               </ul>
    25402545            </li>
    25412546            <li class="indline0"><a id="rfc.index.D" href="#rfc.index.D"><b>D</b></a><ul class="ind">
    2542                   <li class="indline1">DELETE method&nbsp;&nbsp;<a class="iref" href="#rfc.xref.DELETE.1">3</a>, <a class="iref" href="#rfc.iref.d.1"><b>8.7</b></a>, <a class="iref" href="#rfc.xref.DELETE.2">11.1</a></li>
     2547                  <li class="indline1">DELETE method&nbsp;&nbsp;<a class="iref" href="#rfc.xref.DELETE.1">2</a>, <a class="iref" href="#rfc.iref.d.1"><b>7.7</b></a>, <a class="iref" href="#rfc.xref.DELETE.2">10.1</a></li>
    25432548               </ul>
    25442549            </li>
    25452550            <li class="indline0"><a id="rfc.index.E" href="#rfc.index.E"><b>E</b></a><ul class="ind">
    2546                   <li class="indline1">Expect header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.expect.1">4</a>, <a class="iref" href="#rfc.xref.header.expect.2">9.4.18</a>, <a class="iref" href="#rfc.iref.e.1"><b>10.2</b></a>, <a class="iref" href="#rfc.xref.header.expect.3">11.3</a></li>
     2551                  <li class="indline1">Expect header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.expect.1">3</a>, <a class="iref" href="#rfc.xref.header.expect.2">8.4.18</a>, <a class="iref" href="#rfc.iref.e.1"><b>9.2</b></a>, <a class="iref" href="#rfc.xref.header.expect.3">10.3</a></li>
    25472552               </ul>
    25482553            </li>
    25492554            <li class="indline0"><a id="rfc.index.F" href="#rfc.index.F"><b>F</b></a><ul class="ind">
    2550                   <li class="indline1">From header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.from.1">4</a>, <a class="iref" href="#rfc.iref.f.1"><b>10.3</b></a>, <a class="iref" href="#rfc.xref.header.from.2">11.3</a></li>
     2555                  <li class="indline1">From header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.from.1">3</a>, <a class="iref" href="#rfc.iref.f.1"><b>9.3</b></a>, <a class="iref" href="#rfc.xref.header.from.2">10.3</a></li>
    25512556               </ul>
    25522557            </li>
    25532558            <li class="indline0"><a id="rfc.index.G" href="#rfc.index.G"><b>G</b></a><ul class="ind">
    2554                   <li class="indline1">GET method&nbsp;&nbsp;<a class="iref" href="#rfc.xref.GET.1">3</a>, <a class="iref" href="#rfc.iref.g.8"><b>8.3</b></a>, <a class="iref" href="#rfc.xref.GET.2">11.1</a></li>
     2559                  <li class="indline1">GET method&nbsp;&nbsp;<a class="iref" href="#rfc.xref.GET.1">2</a>, <a class="iref" href="#rfc.iref.g.8"><b>7.3</b></a>, <a class="iref" href="#rfc.xref.GET.2">10.1</a></li>
    25552560                  <li class="indline1"><tt>Grammar</tt>&nbsp;&nbsp;
    25562561                     <ul class="ind">
    2557                         <li class="indline1"><tt>Allow</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.9"><b>10.1</b></a></li>
    2558                         <li class="indline1"><tt>Allow-v</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.10"><b>10.1</b></a></li>
    2559                         <li class="indline1"><tt>delta-seconds</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.26"><b>10.7</b></a></li>
    2560                         <li class="indline1"><tt>Expect</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.11"><b>10.2</b></a></li>
    2561                         <li class="indline1"><tt>expect-params</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.15"><b>10.2</b></a></li>
    2562                         <li class="indline1"><tt>Expect-v</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.12"><b>10.2</b></a></li>
    2563                         <li class="indline1"><tt>expectation</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.13"><b>10.2</b></a></li>
    2564                         <li class="indline1"><tt>expectation-extension</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.14"><b>10.2</b></a></li>
    2565                         <li class="indline1"><tt>extension-code</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.5"><b>5</b></a></li>
    2566                         <li class="indline1"><tt>extension-method</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.2"><b>3</b></a></li>
    2567                         <li class="indline1"><tt>From</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.16"><b>10.3</b></a></li>
    2568                         <li class="indline1"><tt>From-v</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.17"><b>10.3</b></a></li>
    2569                         <li class="indline1"><tt>Location</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.18"><b>10.4</b></a></li>
    2570                         <li class="indline1"><tt>Location-v</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.19"><b>10.4</b></a></li>
    2571                         <li class="indline1"><tt>Max-Forwards</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.20"><b>10.5</b></a></li>
    2572                         <li class="indline1"><tt>Max-Forwards-v</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.21"><b>10.5</b></a></li>
    2573                         <li class="indline1"><tt>Method</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.1"><b>3</b></a></li>
    2574                         <li class="indline1"><tt>Reason-Phrase</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.6"><b>5</b></a></li>
    2575                         <li class="indline1"><tt>Referer</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.22"><b>10.6</b></a></li>
    2576                         <li class="indline1"><tt>Referer-v</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.23"><b>10.6</b></a></li>
    2577                         <li class="indline1"><tt>request-header</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.3"><b>4</b></a></li>
    2578                         <li class="indline1"><tt>response-header</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.7"><b>6</b></a></li>
    2579                         <li class="indline1"><tt>Retry-After</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.24"><b>10.7</b></a></li>
    2580                         <li class="indline1"><tt>Retry-After-v</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.25"><b>10.7</b></a></li>
    2581                         <li class="indline1"><tt>Server</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.27"><b>10.8</b></a></li>
    2582                         <li class="indline1"><tt>Server-v</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.28"><b>10.8</b></a></li>
    2583                         <li class="indline1"><tt>Status-Code</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.4"><b>5</b></a></li>
    2584                         <li class="indline1"><tt>User-Agent</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.29"><b>10.9</b></a></li>
    2585                         <li class="indline1"><tt>User-Agent-v</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.30"><b>10.9</b></a></li>
     2562                        <li class="indline1"><tt>Allow</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.9"><b>9.1</b></a></li>
     2563                        <li class="indline1"><tt>Allow-v</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.10"><b>9.1</b></a></li>
     2564                        <li class="indline1"><tt>delta-seconds</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.26"><b>9.7</b></a></li>
     2565                        <li class="indline1"><tt>Expect</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.11"><b>9.2</b></a></li>
     2566                        <li class="indline1"><tt>expect-params</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.15"><b>9.2</b></a></li>
     2567                        <li class="indline1"><tt>Expect-v</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.12"><b>9.2</b></a></li>
     2568                        <li class="indline1"><tt>expectation</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.13"><b>9.2</b></a></li>
     2569                        <li class="indline1"><tt>expectation-extension</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.14"><b>9.2</b></a></li>
     2570                        <li class="indline1"><tt>extension-code</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.5"><b>4</b></a></li>
     2571                        <li class="indline1"><tt>extension-method</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.2"><b>2</b></a></li>
     2572                        <li class="indline1"><tt>From</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.16"><b>9.3</b></a></li>
     2573                        <li class="indline1"><tt>From-v</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.17"><b>9.3</b></a></li>
     2574                        <li class="indline1"><tt>Location</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.18"><b>9.4</b></a></li>
     2575                        <li class="indline1"><tt>Location-v</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.19"><b>9.4</b></a></li>
     2576                        <li class="indline1"><tt>Max-Forwards</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.20"><b>9.5</b></a></li>
     2577                        <li class="indline1"><tt>Max-Forwards-v</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.21"><b>9.5</b></a></li>
     2578                        <li class="indline1"><tt>Method</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.1"><b>2</b></a></li>
     2579                        <li class="indline1"><tt>Reason-Phrase</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.6"><b>4</b></a></li>
     2580                        <li class="indline1"><tt>Referer</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.22"><b>9.6</b></a></li>
     2581                        <li class="indline1"><tt>Referer-v</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.23"><b>9.6</b></a></li>
     2582                        <li class="indline1"><tt>request-header</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.3"><b>3</b></a></li>
     2583                        <li class="indline1"><tt>response-header</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.7"><b>5</b></a></li>
     2584                        <li class="indline1"><tt>Retry-After</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.24"><b>9.7</b></a></li>
     2585                        <li class="indline1"><tt>Retry-After-v</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.25"><b>9.7</b></a></li>
     2586                        <li class="indline1"><tt>Server</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.27"><b>9.8</b></a></li>
     2587                        <li class="indline1"><tt>Server-v</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.28"><b>9.8</b></a></li>
     2588                        <li class="indline1"><tt>Status-Code</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.4"><b>4</b></a></li>
     2589                        <li class="indline1"><tt>User-Agent</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.29"><b>9.9</b></a></li>
     2590                        <li class="indline1"><tt>User-Agent-v</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.30"><b>9.9</b></a></li>
    25862591                     </ul>
    25872592                  </li>
     
    25892594            </li>
    25902595            <li class="indline0"><a id="rfc.index.H" href="#rfc.index.H"><b>H</b></a><ul class="ind">
    2591                   <li class="indline1">HEAD method&nbsp;&nbsp;<a class="iref" href="#rfc.xref.HEAD.1">3</a>, <a class="iref" href="#rfc.iref.h.1"><b>8.4</b></a>, <a class="iref" href="#rfc.xref.HEAD.2">11.1</a></li>
     2596                  <li class="indline1">HEAD method&nbsp;&nbsp;<a class="iref" href="#rfc.xref.HEAD.1">2</a>, <a class="iref" href="#rfc.iref.h.1"><b>7.4</b></a>, <a class="iref" href="#rfc.xref.HEAD.2">10.1</a></li>
    25922597                  <li class="indline1">Headers&nbsp;&nbsp;
    25932598                     <ul class="ind">
    2594                         <li class="indline1">Allow&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.allow.1">3</a>, <a class="iref" href="#rfc.xref.header.allow.2">6</a>, <a class="iref" href="#rfc.iref.h.2"><b>10.1</b></a>, <a class="iref" href="#rfc.xref.header.allow.3">11.3</a>, <a class="iref" href="#rfc.xref.header.allow.4">A.2</a></li>
    2595                         <li class="indline1">Expect&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.expect.1">4</a>, <a class="iref" href="#rfc.xref.header.expect.2">9.4.18</a>, <a class="iref" href="#rfc.iref.h.3"><b>10.2</b></a>, <a class="iref" href="#rfc.xref.header.expect.3">11.3</a></li>
    2596                         <li class="indline1">From&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.from.1">4</a>, <a class="iref" href="#rfc.iref.h.4"><b>10.3</b></a>, <a class="iref" href="#rfc.xref.header.from.2">11.3</a></li>
    2597                         <li class="indline1">Location&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.location.1">6</a>, <a class="iref" href="#rfc.xref.header.location.2">8.5</a>, <a class="iref" href="#rfc.iref.h.5"><b>10.4</b></a>, <a class="iref" href="#rfc.xref.header.location.3">11.3</a>, <a class="iref" href="#rfc.xref.header.location.4">A.2</a></li>
    2598                         <li class="indline1">Max-Forwards&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.max-forwards.1">4</a>, <a class="iref" href="#rfc.xref.header.max-forwards.2">8.8</a>, <a class="iref" href="#rfc.iref.h.6"><b>10.5</b></a>, <a class="iref" href="#rfc.xref.header.max-forwards.3">11.3</a></li>
    2599                         <li class="indline1">Referer&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.referer.1">4</a>, <a class="iref" href="#rfc.iref.h.7"><b>10.6</b></a>, <a class="iref" href="#rfc.xref.header.referer.2">11.3</a></li>
    2600                         <li class="indline1">Retry-After&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.retry-after.1">6</a>, <a class="iref" href="#rfc.iref.h.8"><b>10.7</b></a>, <a class="iref" href="#rfc.xref.header.retry-after.2">11.3</a></li>
    2601                         <li class="indline1">Server&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.server.1">6</a>, <a class="iref" href="#rfc.iref.h.9"><b>10.8</b></a>, <a class="iref" href="#rfc.xref.header.server.2">11.3</a>, <a class="iref" href="#rfc.xref.header.server.3">12.1</a>, <a class="iref" href="#rfc.xref.header.server.4">A.2</a></li>
    2602                         <li class="indline1">User-Agent&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.user-agent.1">4</a>, <a class="iref" href="#rfc.iref.h.10"><b>10.9</b></a>, <a class="iref" href="#rfc.xref.header.user-agent.2">11.3</a>, <a class="iref" href="#rfc.xref.header.user-agent.3">12.1</a></li>
     2599                        <li class="indline1">Allow&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.allow.1">2</a>, <a class="iref" href="#rfc.xref.header.allow.2">5</a>, <a class="iref" href="#rfc.iref.h.2"><b>9.1</b></a>, <a class="iref" href="#rfc.xref.header.allow.3">10.3</a>, <a class="iref" href="#rfc.xref.header.allow.4">A.2</a></li>
     2600                        <li class="indline1">Expect&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.expect.1">3</a>, <a class="iref" href="#rfc.xref.header.expect.2">8.4.18</a>, <a class="iref" href="#rfc.iref.h.3"><b>9.2</b></a>, <a class="iref" href="#rfc.xref.header.expect.3">10.3</a></li>
     2601                        <li class="indline1">From&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.from.1">3</a>, <a class="iref" href="#rfc.iref.h.4"><b>9.3</b></a>, <a class="iref" href="#rfc.xref.header.from.2">10.3</a></li>
     2602                        <li class="indline1">Location&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.location.1">5</a>, <a class="iref" href="#rfc.xref.header.location.2">7.5</a>, <a class="iref" href="#rfc.iref.h.5"><b>9.4</b></a>, <a class="iref" href="#rfc.xref.header.location.3">10.3</a>, <a class="iref" href="#rfc.xref.header.location.4">A.2</a></li>
     2603                        <li class="indline1">Max-Forwards&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.max-forwards.1">3</a>, <a class="iref" href="#rfc.xref.header.max-forwards.2">7.8</a>, <a class="iref" href="#rfc.iref.h.6"><b>9.5</b></a>, <a class="iref" href="#rfc.xref.header.max-forwards.3">10.3</a></li>
     2604                        <li class="indline1">Referer&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.referer.1">3</a>, <a class="iref" href="#rfc.iref.h.7"><b>9.6</b></a>, <a class="iref" href="#rfc.xref.header.referer.2">10.3</a></li>
     2605                        <li class="indline1">Retry-After&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.retry-after.1">5</a>, <a class="iref" href="#rfc.iref.h.8"><b>9.7</b></a>, <a class="iref" href="#rfc.xref.header.retry-after.2">10.3</a></li>
     2606                        <li class="indline1">Server&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.server.1">5</a>, <a class="iref" href="#rfc.iref.h.9"><b>9.8</b></a>, <a class="iref" href="#rfc.xref.header.server.2">10.3</a>, <a class="iref" href="#rfc.xref.header.server.3">11.1</a>, <a class="iref" href="#rfc.xref.header.server.4">A.2</a></li>
     2607                        <li class="indline1">User-Agent&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.user-agent.1">3</a>, <a class="iref" href="#rfc.iref.h.10"><b>9.9</b></a>, <a class="iref" href="#rfc.xref.header.user-agent.2">10.3</a>, <a class="iref" href="#rfc.xref.header.user-agent.3">11.1</a></li>
    26032608                     </ul>
    26042609                  </li>
     
    26062611            </li>
    26072612            <li class="indline0"><a id="rfc.index.I" href="#rfc.index.I"><b>I</b></a><ul class="ind">
    2608                   <li class="indline1">Idempotent Methods&nbsp;&nbsp;<a class="iref" href="#rfc.iref.i.1"><b>8.1.2</b></a></li>
     2613                  <li class="indline1">Idempotent Methods&nbsp;&nbsp;<a class="iref" href="#rfc.iref.i.1"><b>7.1.2</b></a></li>
    26092614               </ul>
    26102615            </li>
    26112616            <li class="indline0"><a id="rfc.index.L" href="#rfc.index.L"><b>L</b></a><ul class="ind">
    26122617                  <li class="indline1">LINK method&nbsp;&nbsp;<a class="iref" href="#rfc.iref.l.2"><b>A.1</b></a></li>
    2613                   <li class="indline1">Location header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.location.1">6</a>, <a class="iref" href="#rfc.xref.header.location.2">8.5</a>, <a class="iref" href="#rfc.iref.l.1"><b>10.4</b></a>, <a class="iref" href="#rfc.xref.header.location.3">11.3</a>, <a class="iref" href="#rfc.xref.header.location.4">A.2</a></li>
     2618                  <li class="indline1">Location header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.location.1">5</a>, <a class="iref" href="#rfc.xref.header.location.2">7.5</a>, <a class="iref" href="#rfc.iref.l.1"><b>9.4</b></a>, <a class="iref" href="#rfc.xref.header.location.3">10.3</a>, <a class="iref" href="#rfc.xref.header.location.4">A.2</a></li>
    26142619               </ul>
    26152620            </li>
    26162621            <li class="indline0"><a id="rfc.index.M" href="#rfc.index.M"><b>M</b></a><ul class="ind">
    2617                   <li class="indline1">Max-Forwards header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.max-forwards.1">4</a>, <a class="iref" href="#rfc.xref.header.max-forwards.2">8.8</a>, <a class="iref" href="#rfc.iref.m.9"><b>10.5</b></a>, <a class="iref" href="#rfc.xref.header.max-forwards.3">11.3</a></li>
     2622                  <li class="indline1">Max-Forwards header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.max-forwards.1">3</a>, <a class="iref" href="#rfc.xref.header.max-forwards.2">7.8</a>, <a class="iref" href="#rfc.iref.m.9"><b>9.5</b></a>, <a class="iref" href="#rfc.xref.header.max-forwards.3">10.3</a></li>
    26182623                  <li class="indline1">Methods&nbsp;&nbsp;
    26192624                     <ul class="ind">
    2620                         <li class="indline1">CONNECT&nbsp;&nbsp;<a class="iref" href="#rfc.xref.CONNECT.1">3</a>, <a class="iref" href="#rfc.iref.m.8"><b>8.9</b></a>, <a class="iref" href="#rfc.xref.CONNECT.2">11.1</a></li>
    2621                         <li class="indline1">DELETE&nbsp;&nbsp;<a class="iref" href="#rfc.xref.DELETE.1">3</a>, <a class="iref" href="#rfc.iref.m.6"><b>8.7</b></a>, <a class="iref" href="#rfc.xref.DELETE.2">11.1</a></li>
    2622                         <li class="indline1">GET&nbsp;&nbsp;<a class="iref" href="#rfc.xref.GET.1">3</a>, <a class="iref" href="#rfc.iref.m.2"><b>8.3</b></a>, <a class="iref" href="#rfc.xref.GET.2">11.1</a></li>
    2623                         <li class="indline1">HEAD&nbsp;&nbsp;<a class="iref" href="#rfc.xref.HEAD.1">3</a>, <a class="iref" href="#rfc.iref.m.3"><b>8.4</b></a>, <a class="iref" href="#rfc.xref.HEAD.2">11.1</a></li>
     2625                        <li class="indline1">CONNECT&nbsp;&nbsp;<a class="iref" href="#rfc.xref.CONNECT.1">2</a>, <a class="iref" href="#rfc.iref.m.8"><b>7.9</b></a>, <a class="iref" href="#rfc.xref.CONNECT.2">10.1</a></li>
     2626                        <li class="indline1">DELETE&nbsp;&nbsp;<a class="iref" href="#rfc.xref.DELETE.1">2</a>, <a class="iref" href="#rfc.iref.m.6"><b>7.7</b></a>, <a class="iref" href="#rfc.xref.DELETE.2">10.1</a></li>
     2627                        <li class="indline1">GET&nbsp;&nbsp;<a class="iref" href="#rfc.xref.GET.1">2</a>, <a class="iref" href="#rfc.iref.m.2"><b>7.3</b></a>, <a class="iref" href="#rfc.xref.GET.2">10.1</a></li>
     2628                        <li class="indline1">HEAD&nbsp;&nbsp;<a class="iref" href="#rfc.xref.HEAD.1">2</a>, <a class="iref" href="#rfc.iref.m.3"><b>7.4</b></a>, <a class="iref" href="#rfc.xref.HEAD.2">10.1</a></li>
    26242629                        <li class="indline1">LINK&nbsp;&nbsp;<a class="iref" href="#rfc.iref.m.11"><b>A.1</b></a></li>
    2625                         <li class="indline1">OPTIONS&nbsp;&nbsp;<a class="iref" href="#rfc.xref.OPTIONS.1">3</a>, <a class="iref" href="#rfc.iref.m.1"><b>8.2</b></a>, <a class="iref" href="#rfc.xref.OPTIONS.2">10.5</a>, <a class="iref" href="#rfc.xref.OPTIONS.3">11.1</a></li>
     2630                        <li class="indline1">OPTIONS&nbsp;&nbsp;<a class="iref" href="#rfc.xref.OPTIONS.1">2</a>, <a class="iref" href="#rfc.iref.m.1"><b>7.2</b></a>, <a class="iref" href="#rfc.xref.OPTIONS.2">9.5</a>, <a class="iref" href="#rfc.xref.OPTIONS.3">10.1</a></li>
    26262631                        <li class="indline1">PATCH&nbsp;&nbsp;<a class="iref" href="#rfc.iref.m.10"><b>A.1</b></a></li>
    2627                         <li class="indline1">POST&nbsp;&nbsp;<a class="iref" href="#rfc.xref.POST.1">3</a>, <a class="iref" href="#rfc.iref.m.4"><b>8.5</b></a>, <a class="iref" href="#rfc.xref.POST.2">11.1</a>, <a class="iref" href="#rfc.xref.POST.3">A.2</a></li>
    2628                         <li class="indline1">PUT&nbsp;&nbsp;<a class="iref" href="#rfc.xref.PUT.1">3</a>, <a class="iref" href="#rfc.iref.m.5"><b>8.6</b></a>, <a class="iref" href="#rfc.xref.PUT.2">11.1</a></li>
    2629                         <li class="indline1">TRACE&nbsp;&nbsp;<a class="iref" href="#rfc.xref.TRACE.1">3</a>, <a class="iref" href="#rfc.iref.m.7"><b>8.8</b></a>, <a class="iref" href="#rfc.xref.TRACE.2">10.5</a>, <a class="iref" href="#rfc.xref.TRACE.3">11.1</a></li>
     2632                        <li class="indline1">POST&nbsp;&nbsp;<a class="iref" href="#rfc.xref.POST.1">2</a>, <a class="iref" href="#rfc.iref.m.4"><b>7.5</b></a>, <a class="iref" href="#rfc.xref.POST.2">10.1</a>, <a class="iref" href="#rfc.xref.POST.3">A.2</a></li>
     2633                        <li class="indline1">PUT&nbsp;&nbsp;<a class="iref" href="#rfc.xref.PUT.1">2</a>, <a class="iref" href="#rfc.iref.m.5"><b>7.6</b></a>, <a class="iref" href="#rfc.xref.PUT.2">10.1</a></li>
     2634                        <li class="indline1">TRACE&nbsp;&nbsp;<a class="iref" href="#rfc.xref.TRACE.1">2</a>, <a class="iref" href="#rfc.iref.m.7"><b>7.8</b></a>, <a class="iref" href="#rfc.xref.TRACE.2">9.5</a>, <a class="iref" href="#rfc.xref.TRACE.3">10.1</a></li>
    26302635                        <li class="indline1">UNLINK&nbsp;&nbsp;<a class="iref" href="#rfc.iref.m.12"><b>A.1</b></a></li>
    26312636                     </ul>
     
    26342639            </li>
    26352640            <li class="indline0"><a id="rfc.index.O" href="#rfc.index.O"><b>O</b></a><ul class="ind">
    2636                   <li class="indline1">OPTIONS method&nbsp;&nbsp;<a class="iref" href="#rfc.xref.OPTIONS.1">3</a>, <a class="iref" href="#rfc.iref.o.1"><b>8.2</b></a>, <a class="iref" href="#rfc.xref.OPTIONS.2">10.5</a>, <a class="iref" href="#rfc.xref.OPTIONS.3">11.1</a></li>
     2641                  <li class="indline1">OPTIONS method&nbsp;&nbsp;<a class="iref" href="#rfc.xref.OPTIONS.1">2</a>, <a class="iref" href="#rfc.iref.o.1"><b>7.2</b></a>, <a class="iref" href="#rfc.xref.OPTIONS.2">9.5</a>, <a class="iref" href="#rfc.xref.OPTIONS.3">10.1</a></li>
    26372642               </ul>
    26382643            </li>
    26392644            <li class="indline0"><a id="rfc.index.P" href="#rfc.index.P"><b>P</b></a><ul class="ind">
    2640                   <li class="indline1"><em>Part1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.1">1</a>, <a class="iref" href="#rfc.xref.Part1.2">2</a>, <a class="iref" href="#rfc.xref.Part1.3">2</a>, <a class="iref" href="#rfc.xref.Part1.4">2</a>, <a class="iref" href="#rfc.xref.Part1.5">2</a>, <a class="iref" href="#rfc.xref.Part1.6">2</a>, <a class="iref" href="#rfc.xref.Part1.7">2</a>, <a class="iref" href="#rfc.xref.Part1.8">2</a>, <a class="iref" href="#rfc.xref.Part1.9">2</a>, <a class="iref" href="#rfc.xref.Part1.10">2</a>, <a class="iref" href="#rfc.xref.Part1.11">2</a>, <a class="iref" href="#rfc.xref.Part1.12">2</a>, <a class="iref" href="#rfc.xref.Part1.13">2</a>, <a class="iref" href="#rfc.xref.Part1.14">2</a>, <a class="iref" href="#rfc.xref.Part1.15">2</a>, <a class="iref" href="#rfc.xref.Part1.16">2</a>, <a class="iref" href="#rfc.xref.Part1.17">2</a>, <a class="iref" href="#rfc.xref.Part1.18">2</a>, <a class="iref" href="#rfc.xref.Part1.19">2</a>, <a class="iref" href="#rfc.xref.Part1.20">2</a>, <a class="iref" href="#rfc.xref.Part1.21">2</a>, <a class="iref" href="#rfc.xref.Part1.22">4</a>, <a class="iref" href="#rfc.xref.Part1.23">4</a>, <a class="iref" href="#rfc.xref.Part1.24">7</a>, <a class="iref" href="#rfc.xref.Part1.25">8.8</a>, <a class="iref" href="#rfc.xref.Part1.26">8.8</a>, <a class="iref" href="#rfc.xref.Part1.27">9.1.1</a>, <a class="iref" href="#rfc.xref.Part1.28">9.5.6</a>, <a class="iref" href="#rfc.xref.Part1.29">10.2</a>, <a class="iref" href="#rfc.xref.Part1.30">10.8</a>, <a class="iref" href="#rfc.xref.Part1.31">10.8</a>, <a class="iref" href="#rfc.xref.Part1.32">10.9</a>, <a class="iref" href="#Part1"><b>14.1</b></a>, <a class="iref" href="#rfc.xref.Part1.33">A.2</a><ul class="ind">
    2641                         <li class="indline1"><em>Section 1.2.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.2">2</a></li>
    2642                         <li class="indline1"><em>Section 1.2.2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.3">2</a>, <a class="iref" href="#rfc.xref.Part1.4">2</a>, <a class="iref" href="#rfc.xref.Part1.5">2</a>, <a class="iref" href="#rfc.xref.Part1.6">2</a>, <a class="iref" href="#rfc.xref.Part1.7">2</a>, <a class="iref" href="#rfc.xref.Part1.8">2</a>, <a class="iref" href="#rfc.xref.Part1.9">2</a>, <a class="iref" href="#rfc.xref.Part1.10">2</a>, <a class="iref" href="#rfc.xref.Part1.11">2</a>, <a class="iref" href="#rfc.xref.Part1.12">2</a>, <a class="iref" href="#rfc.xref.Part1.13">2</a>, <a class="iref" href="#rfc.xref.Part1.14">2</a></li>
    2643                         <li class="indline1"><em>Section 2.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.15">2</a>, <a class="iref" href="#rfc.xref.Part1.16">2</a>, <a class="iref" href="#rfc.xref.Part1.17">2</a>, <a class="iref" href="#rfc.xref.Part1.19">2</a></li>
    2644                         <li class="indline1"><em>Section 3.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.28">9.5.6</a></li>
    2645                         <li class="indline1"><em>Section 3.2.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.18">2</a></li>
    2646                         <li class="indline1"><em>Section 3.4</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.20">2</a>, <a class="iref" href="#rfc.xref.Part1.30">10.8</a>, <a class="iref" href="#rfc.xref.Part1.32">10.9</a></li>
    2647                         <li class="indline1"><em>Section 4.3</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.24">7</a></li>
    2648                         <li class="indline1"><em>Section 7.2.3</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.27">9.1.1</a>, <a class="iref" href="#rfc.xref.Part1.29">10.2</a></li>
    2649                         <li class="indline1"><em>Section 8.4</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.22">4</a></li>
    2650                         <li class="indline1"><em>Section 8.8</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.21">2</a>, <a class="iref" href="#rfc.xref.Part1.23">4</a></li>
    2651                         <li class="indline1"><em>Section 8.9</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.25">8.8</a>, <a class="iref" href="#rfc.xref.Part1.31">10.8</a>, <a class="iref" href="#rfc.xref.Part1.33">A.2</a></li>
    2652                         <li class="indline1"><em>Section 9.3.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.26">8.8</a></li>
     2645                  <li class="indline1"><em>Part1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.1">1</a>, <a class="iref" href="#rfc.xref.Part1.2">1.2</a>, <a class="iref" href="#rfc.xref.Part1.3">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.4">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.5">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.6">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.7">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.8">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.9">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.10">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.11">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.12">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.13">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.14">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.15">1.2.2</a>, <a class="iref" href="#rfc.xref.Part1.16">1.2.2</a>, <a class="iref" href="#rfc.xref.Part1.17">1.2.2</a>, <a class="iref" href="#rfc.xref.Part1.18">1.2.2</a>, <a class="iref" href="#rfc.xref.Part1.19">1.2.2</a>, <a class="iref" href="#rfc.xref.Part1.20">1.2.2</a>, <a class="iref" href="#rfc.xref.Part1.21">1.2.2</a>, <a class="iref" href="#rfc.xref.Part1.22">3</a>, <a class="iref" href="#rfc.xref.Part1.23">3</a>, <a class="iref" href="#rfc.xref.Part1.24">6</a>, <a class="iref" href="#rfc.xref.Part1.25">7.8</a>, <a class="iref" href="#rfc.xref.Part1.26">7.8</a>, <a class="iref" href="#rfc.xref.Part1.27">8.1.1</a>, <a class="iref" href="#rfc.xref.Part1.28">8.5.6</a>, <a class="iref" href="#rfc.xref.Part1.29">9.2</a>, <a class="iref" href="#rfc.xref.Part1.30">9.8</a>, <a class="iref" href="#rfc.xref.Part1.31">9.8</a>, <a class="iref" href="#rfc.xref.Part1.32">9.9</a>, <a class="iref" href="#Part1"><b>13.1</b></a>, <a class="iref" href="#rfc.xref.Part1.33">A.2</a><ul class="ind">
     2646                        <li class="indline1"><em>Section 1.2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.2">1.2</a></li>
     2647                        <li class="indline1"><em>Section 1.2.2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.3">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.4">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.5">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.6">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.7">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.8">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.9">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.10">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.11">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.12">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.13">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.14">1.2.1</a></li>
     2648                        <li class="indline1"><em>Section 2.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.15">1.2.2</a>, <a class="iref" href="#rfc.xref.Part1.16">1.2.2</a>, <a class="iref" href="#rfc.xref.Part1.17">1.2.2</a>, <a class="iref" href="#rfc.xref.Part1.19">1.2.2</a></li>
     2649                        <li class="indline1"><em>Section 3.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.28">8.5.6</a></li>
     2650                        <li class="indline1"><em>Section 3.2.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.18">1.2.2</a></li>
     2651                        <li class="indline1"><em>Section 3.4</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.20">1.2.2</a>, <a class="iref" href="#rfc.xref.Part1.30">9.8</a>, <a class="iref" href="#rfc.xref.Part1.32">9.9</a></li>
     2652                        <li class="indline1"><em>Section 4.3</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.24">6</a></li>
     2653                        <li class="indline1"><em>Section 7.2.3</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.27">8.1.1</a>, <a class="iref" href="#rfc.xref.Part1.29">9.2</a></li>
     2654                        <li class="indline1"><em>Section 8.4</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.22">3</a></li>
     2655                        <li class="indline1"><em>Section 8.8</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.21">1.2.2</a>, <a class="iref" href="#rfc.xref.Part1.23">3</a></li>
     2656                        <li class="indline1"><em>Section 8.9</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.25">7.8</a>, <a class="iref" href="#rfc.xref.Part1.31">9.8</a>, <a class="iref" href="#rfc.xref.Part1.33">A.2</a></li>
     2657                        <li class="indline1"><em>Section 9.3.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.26">7.8</a></li>
    26532658                     </ul>
    26542659                  </li>
    2655                   <li class="indline1"><em>Part3</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.1">2</a>, <a class="iref" href="#rfc.xref.Part3.2">2</a>, <a class="iref" href="#rfc.xref.Part3.3">2</a>, <a class="iref" href="#rfc.xref.Part3.4">2</a>, <a class="iref" href="#rfc.xref.Part3.5">4</a>, <a class="iref" href="#rfc.xref.Part3.6">4</a>, <a class="iref" href="#rfc.xref.Part3.7">4</a>, <a class="iref" href="#rfc.xref.Part3.8">4</a>, <a class="iref" href="#rfc.xref.Part3.9">7</a>, <a class="iref" href="#rfc.xref.Part3.10">9.3.1</a>, <a class="iref" href="#rfc.xref.Part3.11">10.4</a>, <a class="iref" href="#Part3"><b>14.1</b></a><ul class="ind">
    2656                         <li class="indline1"><em>Section 5</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.10">9.3.1</a></li>
    2657                         <li class="indline1"><em>Section 6.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.1">2</a>, <a class="iref" href="#rfc.xref.Part3.5">4</a></li>
    2658                         <li class="indline1"><em>Section 6.2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.2">2</a>, <a class="iref" href="#rfc.xref.Part3.6">4</a></li>
    2659                         <li class="indline1"><em>Section 6.3</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.3">2</a>, <a class="iref" href="#rfc.xref.Part3.7">4</a></li>
    2660                         <li class="indline1"><em>Section 6.4</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.4">2</a>, <a class="iref" href="#rfc.xref.Part3.8">4</a></li>
    2661                         <li class="indline1"><em>Section 6.7</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.11">10.4</a></li>
     2660                  <li class="indline1"><em>Part3</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.1">1.2.2</a>, <a class="iref" href="#rfc.xref.Part3.2">1.2.2</a>, <a class="iref" href="#rfc.xref.Part3.3">1.2.2</a>, <a class="iref" href="#rfc.xref.Part3.4">1.2.2</a>, <a class="iref" href="#rfc.xref.Part3.5">3</a>, <a class="iref" href="#rfc.xref.Part3.6">3</a>, <a class="iref" href="#rfc.xref.Part3.7">3</a>, <a class="iref" href="#rfc.xref.Part3.8">3</a>, <a class="iref" href="#rfc.xref.Part3.9">6</a>, <a class="iref" href="#rfc.xref.Part3.10">8.3.1</a>, <a class="iref" href="#rfc.xref.Part3.11">9.4</a>, <a class="iref" href="#Part3"><b>13.1</b></a><ul class="ind">
     2661                        <li class="indline1"><em>Section 4</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.10">8.3.1</a></li>
     2662                        <li class="indline1"><em>Section 5.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.1">1.2.2</a>, <a class="iref" href="#rfc.xref.Part3.5">3</a></li>
     2663                        <li class="indline1"><em>Section 5.2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.2">1.2.2</a>, <a class="iref" href="#rfc.xref.Part3.6">3</a></li>
     2664                        <li class="indline1"><em>Section 5.3</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.3">1.2.2</a>, <a class="iref" href="#rfc.xref.Part3.7">3</a></li>
     2665                        <li class="indline1"><em>Section 5.4</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.4">1.2.2</a>, <a class="iref" href="#rfc.xref.Part3.8">3</a></li>
     2666                        <li class="indline1"><em>Section 5.7</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.11">9.4</a></li>
    26622667                     </ul>
    26632668                  </li>
    2664                   <li class="indline1"><em>Part4</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part4.1">2</a>, <a class="iref" href="#rfc.xref.Part4.2">2</a>, <a class="iref" href="#rfc.xref.Part4.3">2</a>, <a class="iref" href="#rfc.xref.Part4.4">2</a>, <a class="iref" href="#rfc.xref.Part4.5">2</a>, <a class="iref" href="#rfc.xref.Part4.6">4</a>, <a class="iref" href="#rfc.xref.Part4.7">4</a>, <a class="iref" href="#rfc.xref.Part4.8">4</a>, <a class="iref" href="#rfc.xref.Part4.9">4</a>, <a class="iref" href="#rfc.xref.Part4.10">6</a>, <a class="iref" href="#rfc.xref.Part4.11">9.2.2</a>, <a class="iref" href="#rfc.xref.Part4.12">9.3.5</a>, <a class="iref" href="#rfc.xref.Part4.13">9.4.13</a>, <a class="iref" href="#Part4"><b>14.1</b></a>, <a class="iref" href="#rfc.xref.Part4.14">C.2</a><ul class="ind">
    2665                         <li class="indline1"><em>Section 7.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part4.1">2</a>, <a class="iref" href="#rfc.xref.Part4.10">6</a>, <a class="iref" href="#rfc.xref.Part4.11">9.2.2</a></li>
    2666                         <li class="indline1"><em>Section 7.2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part4.2">2</a>, <a class="iref" href="#rfc.xref.Part4.6">4</a></li>
    2667                         <li class="indline1"><em>Section 7.3</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part4.3">2</a>, <a class="iref" href="#rfc.xref.Part4.7">4</a></li>
    2668                         <li class="indline1"><em>Section 7.4</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part4.4">2</a>, <a class="iref" href="#rfc.xref.Part4.8">4</a></li>
    2669                         <li class="indline1"><em>Section 7.5</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part4.5">2</a>, <a class="iref" href="#rfc.xref.Part4.9">4</a></li>
     2669                  <li class="indline1"><em>Part4</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part4.1">1.2.2</a>, <a class="iref" href="#rfc.xref.Part4.2">1.2.2</a>, <a class="iref" href="#rfc.xref.Part4.3">1.2.2</a>, <a class="iref" href="#rfc.xref.Part4.4">1.2.2</a>, <a class="iref" href="#rfc.xref.Part4.5">1.2.2</a>, <a class="iref" href="#rfc.xref.Part4.6">3</a>, <a class="iref" href="#rfc.xref.Part4.7">3</a>, <a class="iref" href="#rfc.xref.Part4.8">3</a>, <a class="iref" href="#rfc.xref.Part4.9">3</a>, <a class="iref" href="#rfc.xref.Part4.10">5</a>, <a class="iref" href="#rfc.xref.Part4.11">8.2.2</a>, <a class="iref" href="#rfc.xref.Part4.12">8.3.5</a>, <a class="iref" href="#rfc.xref.Part4.13">8.4.13</a>, <a class="iref" href="#Part4"><b>13.1</b></a>, <a class="iref" href="#rfc.xref.Part4.14">C.2</a><ul class="ind">
     2670                        <li class="indline1"><em>Section 6.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part4.1">1.2.2</a>, <a class="iref" href="#rfc.xref.Part4.10">5</a>, <a class="iref" href="#rfc.xref.Part4.11">8.2.2</a></li>
     2671                        <li class="indline1"><em>Section 6.2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part4.2">1.2.2</a>, <a class="iref" href="#rfc.xref.Part4.6">3</a></li>
     2672                        <li class="indline1"><em>Section 6.3</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part4.3">1.2.2</a>, <a class="iref" href="#rfc.xref.Part4.7">3</a></li>
     2673                        <li class="indline1"><em>Section 6.4</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part4.4">1.2.2</a>, <a class="iref" href="#rfc.xref.Part4.8">3</a></li>
     2674                        <li class="indline1"><em>Section 6.5</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part4.5">1.2.2</a>, <a class="iref" href="#rfc.xref.Part4.9">3</a></li>
    26702675                     </ul>
    26712676                  </li>
    2672                   <li class="indline1"><em>Part5</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part5.1">2</a>, <a class="iref" href="#rfc.xref.Part5.2">2</a>, <a class="iref" href="#rfc.xref.Part5.3">2</a>, <a class="iref" href="#rfc.xref.Part5.4">4</a>, <a class="iref" href="#rfc.xref.Part5.5">4</a>, <a class="iref" href="#rfc.xref.Part5.6">6</a>, <a class="iref" href="#rfc.xref.Part5.7">8.3</a>, <a class="iref" href="#rfc.xref.Part5.8">9.1.2</a>, <a class="iref" href="#rfc.xref.Part5.9">9.2.7</a>, <a class="iref" href="#rfc.xref.Part5.10">9.4.17</a>, <a class="iref" href="#Part5"><b>14.1</b></a><ul class="ind">
    2673                         <li class="indline1"><em>Section 6.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part5.1">2</a>, <a class="iref" href="#rfc.xref.Part5.6">6</a></li>
    2674                         <li class="indline1"><em>Section 6.3</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part5.2">2</a>, <a class="iref" href="#rfc.xref.Part5.4">4</a></li>
    2675                         <li class="indline1"><em>Section 6.4</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part5.3">2</a>, <a class="iref" href="#rfc.xref.Part5.5">4</a>, <a class="iref" href="#rfc.xref.Part5.7">8.3</a>, <a class="iref" href="#rfc.xref.Part5.8">9.1.2</a>, <a class="iref" href="#rfc.xref.Part5.10">9.4.17</a></li>
     2677                  <li class="indline1"><em>Part5</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part5.1">1.2.2</a>, <a class="iref" href="#rfc.xref.Part5.2">1.2.2</a>, <a class="iref" href="#rfc.xref.Part5.3">1.2.2</a>, <a class="iref" href="#rfc.xref.Part5.4">3</a>, <a class="iref" href="#rfc.xref.Part5.5">3</a>, <a class="iref" href="#rfc.xref.Part5.6">5</a>, <a class="iref" href="#rfc.xref.Part5.7">7.3</a>, <a class="iref" href="#rfc.xref.Part5.8">8.1.2</a>, <a class="iref" href="#rfc.xref.Part5.9">8.2.7</a>, <a class="iref" href="#rfc.xref.Part5.10">8.4.17</a>, <a class="iref" href="#Part5"><b>13.1</b></a><ul class="ind">
     2678                        <li class="indline1"><em>Section 5.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part5.1">1.2.2</a>, <a class="iref" href="#rfc.xref.Part5.6">5</a></li>
     2679                        <li class="indline1"><em>Section 5.3</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part5.2">1.2.2</a>, <a class="iref" href="#rfc.xref.Part5.4">3</a></li>
     2680                        <li class="indline1"><em>Section 5.4</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part5.3">1.2.2</a>, <a class="iref" href="#rfc.xref.Part5.5">3</a>, <a class="iref" href="#rfc.xref.Part5.7">7.3</a>, <a class="iref" href="#rfc.xref.Part5.8">8.1.2</a>, <a class="iref" href="#rfc.xref.Part5.10">8.4.17</a></li>
    26762681                     </ul>
    26772682                  </li>
    2678                   <li class="indline1"><em>Part6</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part6.1">2</a>, <a class="iref" href="#rfc.xref.Part6.2">2</a>, <a class="iref" href="#rfc.xref.Part6.3">6</a>, <a class="iref" href="#rfc.xref.Part6.4">6</a>, <a class="iref" href="#rfc.xref.Part6.5">8.3</a>, <a class="iref" href="#Part6"><b>14.1</b></a><ul class="ind">
    2679                         <li class="indline1"><em>Section 16.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part6.1">2</a>, <a class="iref" href="#rfc.xref.Part6.3">6</a></li>
    2680                         <li class="indline1"><em>Section 16.5</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part6.2">2</a>, <a class="iref" href="#rfc.xref.Part6.4">6</a></li>
     2683                  <li class="indline1"><em>Part6</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part6.1">1.2.2</a>, <a class="iref" href="#rfc.xref.Part6.2">1.2.2</a>, <a class="iref" href="#rfc.xref.Part6.3">5</a>, <a class="iref" href="#rfc.xref.Part6.4">5</a>, <a class="iref" href="#rfc.xref.Part6.5">7.3</a>, <a class="iref" href="#Part6"><b>13.1</b></a><ul class="ind">
     2684                        <li class="indline1"><em>Section 15.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part6.1">1.2.2</a>, <a class="iref" href="#rfc.xref.Part6.3">5</a></li>
     2685                        <li class="indline1"><em>Section 15.5</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part6.2">1.2.2</a>, <a class="iref" href="#rfc.xref.Part6.4">5</a></li>
    26812686                     </ul>
    26822687                  </li>
    2683                   <li class="indline1"><em>Part7</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part7.1">2</a>, <a class="iref" href="#rfc.xref.Part7.2">2</a>, <a class="iref" href="#rfc.xref.Part7.3">2</a>, <a class="iref" href="#rfc.xref.Part7.4">2</a>, <a class="iref" href="#rfc.xref.Part7.5">4</a>, <a class="iref" href="#rfc.xref.Part7.6">4</a>, <a class="iref" href="#rfc.xref.Part7.7">6</a>, <a class="iref" href="#rfc.xref.Part7.8">6</a>, <a class="iref" href="#rfc.xref.Part7.9">9.4.2</a>, <a class="iref" href="#rfc.xref.Part7.10">9.4.8</a>, <a class="iref" href="#Part7"><b>14.1</b></a><ul class="ind">
    2684                         <li class="indline1"><em>Section 4.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part7.1">2</a>, <a class="iref" href="#rfc.xref.Part7.5">4</a></li>
    2685                         <li class="indline1"><em>Section 4.2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part7.2">2</a>, <a class="iref" href="#rfc.xref.Part7.7">6</a></li>
    2686                         <li class="indline1"><em>Section 4.3</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part7.3">2</a>, <a class="iref" href="#rfc.xref.Part7.6">4</a></li>
    2687                         <li class="indline1"><em>Section 4.4</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part7.4">2</a>, <a class="iref" href="#rfc.xref.Part7.8">6</a></li>
     2688                  <li class="indline1"><em>Part7</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part7.1">1.2.2</a>, <a class="iref" href="#rfc.xref.Part7.2">1.2.2</a>, <a class="iref" href="#rfc.xref.Part7.3">1.2.2</a>, <a class="iref" href="#rfc.xref.Part7.4">1.2.2</a>, <a class="iref" href="#rfc.xref.Part7.5">3</a>, <a class="iref" href="#rfc.xref.Part7.6">3</a>, <a class="iref" href="#rfc.xref.Part7.7">5</a>, <a class="iref" href="#rfc.xref.Part7.8">5</a>, <a class="iref" href="#rfc.xref.Part7.9">8.4.2</a>, <a class="iref" href="#rfc.xref.Part7.10">8.4.8</a>, <a class="iref" href="#Part7"><b>13.1</b></a><ul class="ind">
     2689                        <li class="indline1"><em>Section 3.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part7.1">1.2.2</a>, <a class="iref" href="#rfc.xref.Part7.5">3</a></li>
     2690                        <li class="indline1"><em>Section 3.2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part7.2">1.2.2</a>, <a class="iref" href="#rfc.xref.Part7.7">5</a></li>
     2691                        <li class="indline1"><em>Section 3.3</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part7.3">1.2.2</a>, <a class="iref" href="#rfc.xref.Part7.6">3</a></li>
     2692                        <li class="indline1"><em>Section 3.4</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part7.4">1.2.2</a>, <a class="iref" href="#rfc.xref.Part7.8">5</a></li>
    26882693                     </ul>
    26892694                  </li>
    26902695                  <li class="indline1">PATCH method&nbsp;&nbsp;<a class="iref" href="#rfc.iref.p.3"><b>A.1</b></a></li>
    2691                   <li class="indline1">POST method&nbsp;&nbsp;<a class="iref" href="#rfc.xref.POST.1">3</a>, <a class="iref" href="#rfc.iref.p.1"><b>8.5</b></a>, <a class="iref" href="#rfc.xref.POST.2">11.1</a>, <a class="iref" href="#rfc.xref.POST.3">A.2</a></li>
    2692                   <li class="indline1">PUT method&nbsp;&nbsp;<a class="iref" href="#rfc.xref.PUT.1">3</a>, <a class="iref" href="#rfc.iref.p.2"><b>8.6</b></a>, <a class="iref" href="#rfc.xref.PUT.2">11.1</a></li>
     2696                  <li class="indline1">POST method&nbsp;&nbsp;<a class="iref" href="#rfc.xref.POST.1">2</a>, <a class="iref" href="#rfc.iref.p.1"><b>7.5</b></a>, <a class="iref" href="#rfc.xref.POST.2">10.1</a>, <a class="iref" href="#rfc.xref.POST.3">A.2</a></li>
     2697                  <li class="indline1">PUT method&nbsp;&nbsp;<a class="iref" href="#rfc.xref.PUT.1">2</a>, <a class="iref" href="#rfc.iref.p.2"><b>7.6</b></a>, <a class="iref" href="#rfc.xref.PUT.2">10.1</a></li>
    26932698               </ul>
    26942699            </li>
    26952700            <li class="indline0"><a id="rfc.index.R" href="#rfc.index.R"><b>R</b></a><ul class="ind">
    2696                   <li class="indline1">Referer header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.referer.1">4</a>, <a class="iref" href="#rfc.iref.r.1"><b>10.6</b></a>, <a class="iref" href="#rfc.xref.header.referer.2">11.3</a></li>
    2697                   <li class="indline1">Retry-After header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.retry-after.1">6</a>, <a class="iref" href="#rfc.iref.r.2"><b>10.7</b></a>, <a class="iref" href="#rfc.xref.header.retry-after.2">11.3</a></li>
    2698                   <li class="indline1"><em>RFC1945</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC1945.1">9.3.3</a>, <a class="iref" href="#RFC1945"><b>14.2</b></a></li>
    2699                   <li class="indline1"><em>RFC2068</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2068.1">9.3.3</a>, <a class="iref" href="#RFC2068"><b>14.2</b></a>, <a class="iref" href="#rfc.xref.RFC2068.2">A.1</a><ul class="ind">
     2701                  <li class="indline1">Referer header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.referer.1">3</a>, <a class="iref" href="#rfc.iref.r.1"><b>9.6</b></a>, <a class="iref" href="#rfc.xref.header.referer.2">10.3</a></li>
     2702                  <li class="indline1">Retry-After header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.retry-after.1">5</a>, <a class="iref" href="#rfc.iref.r.2"><b>9.7</b></a>, <a class="iref" href="#rfc.xref.header.retry-after.2">10.3</a></li>
     2703                  <li class="indline1"><em>RFC1945</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC1945.1">8.3.3</a>, <a class="iref" href="#RFC1945"><b>13.2</b></a></li>
     2704                  <li class="indline1"><em>RFC2068</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2068.1">8.3.3</a>, <a class="iref" href="#RFC2068"><b>13.2</b></a>, <a class="iref" href="#rfc.xref.RFC2068.2">A.1</a><ul class="ind">
    27002705                        <li class="indline1"><em>Section 19.6.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2068.2">A.1</a></li>
    27012706                     </ul>
    27022707                  </li>
    2703                   <li class="indline1"><em>RFC2119</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2119.1">1.1</a>, <a class="iref" href="#RFC2119"><b>14.1</b></a></li>
    2704                   <li class="indline1"><em>RFC2616</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2616.1">1</a>, <a class="iref" href="#RFC2616"><b>14.2</b></a>, <a class="iref" href="#rfc.xref.RFC2616.2">C.1</a></li>
    2705                   <li class="indline1"><em>RFC2817</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2817.1">8.9</a>, <a class="iref" href="#rfc.xref.RFC2817.2">11.2</a>, <a class="iref" href="#RFC2817"><b>14.2</b></a>, <a class="iref" href="#rfc.xref.RFC2817.3">A.2</a><ul class="ind">
    2706                         <li class="indline1"><em>Section 7.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2817.2">11.2</a>, <a class="iref" href="#rfc.xref.RFC2817.3">A.2</a></li>
     2708                  <li class="indline1"><em>RFC2119</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2119.1">1.1</a>, <a class="iref" href="#RFC2119"><b>13.1</b></a></li>
     2709                  <li class="indline1"><em>RFC2616</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2616.1">1</a>, <a class="iref" href="#RFC2616"><b>13.2</b></a>, <a class="iref" href="#rfc.xref.RFC2616.2">C.1</a></li>
     2710                  <li class="indline1"><em>RFC2817</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2817.1">7.9</a>, <a class="iref" href="#rfc.xref.RFC2817.2">10.2</a>, <a class="iref" href="#RFC2817"><b>13.2</b></a>, <a class="iref" href="#rfc.xref.RFC2817.3">A.2</a><ul class="ind">
     2711                        <li class="indline1"><em>Section 7.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2817.2">10.2</a>, <a class="iref" href="#rfc.xref.RFC2817.3">A.2</a></li>
    27072712                     </ul>
    27082713                  </li>
    2709                   <li class="indline1"><em>RFC3864</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC3864.1">11.3</a>, <a class="iref" href="#RFC3864"><b>14.2</b></a></li>
    2710                   <li class="indline1"><em>RFC5226</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC5226.1">3.1</a>, <a class="iref" href="#rfc.xref.RFC5226.2">5.1</a>, <a class="iref" href="#RFC5226"><b>14.2</b></a><ul class="ind">
    2711                         <li class="indline1"><em>Section 4.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC5226.1">3.1</a>, <a class="iref" href="#rfc.xref.RFC5226.2">5.1</a></li>
     2714                  <li class="indline1"><em>RFC3864</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC3864.1">10.3</a>, <a class="iref" href="#RFC3864"><b>13.2</b></a></li>
     2715                  <li class="indline1"><em>RFC5226</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC5226.1">2.1</a>, <a class="iref" href="#rfc.xref.RFC5226.2">4.1</a>, <a class="iref" href="#RFC5226"><b>13.2</b></a><ul class="ind">
     2716                        <li class="indline1"><em>Section 4.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC5226.1">2.1</a>, <a class="iref" href="#rfc.xref.RFC5226.2">4.1</a></li>
    27122717                     </ul>
    27132718                  </li>
    2714                   <li class="indline1"><em>RFC5322</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC5322.1">10.3</a>, <a class="iref" href="#rfc.xref.RFC5322.2">10.3</a>, <a class="iref" href="#RFC5322"><b>14.2</b></a><ul class="ind">
    2715                         <li class="indline1"><em>Section 3.4</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC5322.1">10.3</a>, <a class="iref" href="#rfc.xref.RFC5322.2">10.3</a></li>
     2719                  <li class="indline1"><em>RFC5322</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC5322.1">9.3</a>, <a class="iref" href="#rfc.xref.RFC5322.2">9.3</a>, <a class="iref" href="#RFC5322"><b>13.2</b></a><ul class="ind">
     2720                        <li class="indline1"><em>Section 3.4</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC5322.1">9.3</a>, <a class="iref" href="#rfc.xref.RFC5322.2">9.3</a></li>
    27162721                     </ul>
    27172722                  </li>
     
    27192724            </li>
    27202725            <li class="indline0"><a id="rfc.index.S" href="#rfc.index.S"><b>S</b></a><ul class="ind">
    2721                   <li class="indline1">Safe Methods&nbsp;&nbsp;<a class="iref" href="#rfc.iref.s.1"><b>8.1.1</b></a></li>
    2722                   <li class="indline1">Server header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.server.1">6</a>, <a class="iref" href="#rfc.iref.s.43"><b>10.8</b></a>, <a class="iref" href="#rfc.xref.header.server.2">11.3</a>, <a class="iref" href="#rfc.xref.header.server.3">12.1</a>, <a class="iref" href="#rfc.xref.header.server.4">A.2</a></li>
     2726                  <li class="indline1">Safe Methods&nbsp;&nbsp;<a class="iref" href="#rfc.iref.s.1"><b>7.1.1</b></a></li>
     2727                  <li class="indline1">Server header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.server.1">5</a>, <a class="iref" href="#rfc.iref.s.43"><b>9.8</b></a>, <a class="iref" href="#rfc.xref.header.server.2">10.3</a>, <a class="iref" href="#rfc.xref.header.server.3">11.1</a>, <a class="iref" href="#rfc.xref.header.server.4">A.2</a></li>
    27232728                  <li class="indline1">Status Codes&nbsp;&nbsp;
    27242729                     <ul class="ind">
    2725                         <li class="indline1">100 Continue&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.100.1">5</a>, <a class="iref" href="#rfc.iref.s.2"><b>9.1.1</b></a>, <a class="iref" href="#rfc.xref.status.100.2">11.2</a></li>
    2726                         <li class="indline1">101 Switching Protocols&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.101.1">5</a>, <a class="iref" href="#rfc.iref.s.3"><b>9.1.2</b></a>, <a class="iref" href="#rfc.xref.status.101.2">11.2</a></li>
    2727                         <li class="indline1">200 OK&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.200.1">5</a>, <a class="iref" href="#rfc.iref.s.4"><b>9.2.1</b></a>, <a class="iref" href="#rfc.xref.status.200.2">11.2</a></li>
    2728                         <li class="indline1">201 Created&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.201.1">5</a>, <a class="iref" href="#rfc.iref.s.5"><b>9.2.2</b></a>, <a class="iref" href="#rfc.xref.status.201.2">11.2</a>, <a class="iref" href="#rfc.xref.status.201.3">A.1</a></li>
    2729                         <li class="indline1">202 Accepted&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.202.1">5</a>, <a class="iref" href="#rfc.iref.s.6"><b>9.2.3</b></a>, <a class="iref" href="#rfc.xref.status.202.2">11.2</a></li>
    2730                         <li class="indline1">203 Non-Authoritative Information&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.203.1">5</a>, <a class="iref" href="#rfc.iref.s.7"><b>9.2.4</b></a>, <a class="iref" href="#rfc.xref.status.203.2">11.2</a></li>
    2731                         <li class="indline1">204 No Content&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.204.1">5</a>, <a class="iref" href="#rfc.iref.s.8"><b>9.2.5</b></a>, <a class="iref" href="#rfc.xref.status.204.2">11.2</a></li>
    2732                         <li class="indline1">205 Reset Content&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.205.1">5</a>, <a class="iref" href="#rfc.iref.s.9"><b>9.2.6</b></a>, <a class="iref" href="#rfc.xref.status.205.2">11.2</a></li>
    2733                         <li class="indline1">206 Partial Content&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.206.1">5</a>, <a class="iref" href="#rfc.iref.s.10"><b>9.2.7</b></a>, <a class="iref" href="#rfc.xref.status.206.2">11.2</a></li>
    2734                         <li class="indline1">300 Multiple Choices&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.300.1">5</a>, <a class="iref" href="#rfc.iref.s.11"><b>9.3.1</b></a>, <a class="iref" href="#rfc.xref.status.300.2">11.2</a></li>
    2735                         <li class="indline1">301 Moved Permanently&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.301.1">5</a>, <a class="iref" href="#rfc.iref.s.12"><b>9.3.2</b></a>, <a class="iref" href="#rfc.xref.status.301.2">11.2</a>, <a class="iref" href="#rfc.xref.status.301.3">A.2</a></li>
    2736                         <li class="indline1">302 Found&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.302.1">5</a>, <a class="iref" href="#rfc.iref.s.13"><b>9.3.3</b></a>, <a class="iref" href="#rfc.xref.status.302.2">11.2</a>, <a class="iref" href="#rfc.xref.status.302.3">A.2</a></li>
    2737                         <li class="indline1">303 See Other&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.303.1">5</a>, <a class="iref" href="#rfc.iref.s.14"><b>9.3.4</b></a>, <a class="iref" href="#rfc.xref.status.303.2">11.2</a></li>
    2738                         <li class="indline1">304 Not Modified&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.304.1">5</a>, <a class="iref" href="#rfc.iref.s.15"><b>9.3.5</b></a>, <a class="iref" href="#rfc.xref.status.304.2">11.2</a></li>
    2739                         <li class="indline1">305 Use Proxy&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.305.1">5</a>, <a class="iref" href="#rfc.iref.s.16"><b>9.3.6</b></a>, <a class="iref" href="#rfc.xref.status.305.2">11.2</a>, <a class="iref" href="#rfc.xref.status.305.3">A.2</a></li>
    2740                         <li class="indline1">306 (Unused)&nbsp;&nbsp;<a class="iref" href="#rfc.iref.s.17"><b>9.3.7</b></a>, <a class="iref" href="#rfc.xref.status.306.1">11.2</a></li>
    2741                         <li class="indline1">307 Temporary Redirect&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.307.1">5</a>, <a class="iref" href="#rfc.iref.s.18"><b>9.3.8</b></a>, <a class="iref" href="#rfc.xref.status.307.2">11.2</a>, <a class="iref" href="#rfc.xref.status.307.3">A.2</a></li>
    2742                         <li class="indline1">400 Bad Request&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.400.1">5</a>, <a class="iref" href="#rfc.iref.s.19"><b>9.4.1</b></a>, <a class="iref" href="#rfc.xref.status.400.2">11.2</a></li>
    2743                         <li class="indline1">401 Unauthorized&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.401.1">5</a>, <a class="iref" href="#rfc.iref.s.20"><b>9.4.2</b></a>, <a class="iref" href="#rfc.xref.status.401.2">11.2</a></li>
    2744                         <li class="indline1">402 Payment Required&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.402.1">5</a>, <a class="iref" href="#rfc.iref.s.21"><b>9.4.3</b></a>, <a class="iref" href="#rfc.xref.status.402.2">11.2</a></li>
    2745                         <li class="indline1">403 Forbidden&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.403.1">5</a>, <a class="iref" href="#rfc.iref.s.22"><b>9.4.4</b></a>, <a class="iref" href="#rfc.xref.status.403.2">11.2</a>, <a class="iref" href="#rfc.xref.status.403.3">A.1</a></li>
    2746                         <li class="indline1">404 Not Found&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.404.1">5</a>, <a class="iref" href="#rfc.iref.s.23"><b>9.4.5</b></a>, <a class="iref" href="#rfc.xref.status.404.2">11.2</a>, <a class="iref" href="#rfc.xref.status.404.3">A.1</a></li>
    2747                         <li class="indline1">405 Method Not Allowed&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.405.1">5</a>, <a class="iref" href="#rfc.iref.s.24"><b>9.4.6</b></a>, <a class="iref" href="#rfc.xref.status.405.2">11.2</a></li>
    2748                         <li class="indline1">406 Not Acceptable&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.406.1">5</a>, <a class="iref" href="#rfc.iref.s.25"><b>9.4.7</b></a>, <a class="iref" href="#rfc.xref.status.406.2">11.2</a></li>
    2749                         <li class="indline1">407 Proxy Authentication Required&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.407.1">5</a>, <a class="iref" href="#rfc.iref.s.26"><b>9.4.8</b></a>, <a class="iref" href="#rfc.xref.status.407.2">11.2</a></li>
    2750                         <li class="indline1">408 Request Timeout&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.408.1">5</a>, <a class="iref" href="#rfc.iref.s.27"><b>9.4.9</b></a>, <a class="iref" href="#rfc.xref.status.408.2">11.2</a></li>
    2751                         <li class="indline1">409 Conflict&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.409.1">5</a>, <a class="iref" href="#rfc.iref.s.28"><b>9.4.10</b></a>, <a class="iref" href="#rfc.xref.status.409.2">11.2</a></li>
    2752                         <li class="indline1">410 Gone&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.410.1">5</a>, <a class="iref" href="#rfc.iref.s.29"><b>9.4.11</b></a>, <a class="iref" href="#rfc.xref.status.410.2">11.2</a>, <a class="iref" href="#rfc.xref.status.410.3">A.1</a></li>
    2753                         <li class="indline1">411 Length Required&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.411.1">5</a>, <a class="iref" href="#rfc.iref.s.30"><b>9.4.12</b></a>, <a class="iref" href="#rfc.xref.status.411.2">11.2</a></li>
    2754                         <li class="indline1">412 Precondition Failed&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.412.1">5</a>, <a class="iref" href="#rfc.iref.s.31"><b>9.4.13</b></a>, <a class="iref" href="#rfc.xref.status.412.2">11.2</a></li>
    2755                         <li class="indline1">413 Request Entity Too Large&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.413.1">5</a>, <a class="iref" href="#rfc.iref.s.32"><b>9.4.14</b></a>, <a class="iref" href="#rfc.xref.status.413.2">11.2</a></li>
    2756                         <li class="indline1">414 Request-target Too Long&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.414.1">5</a>, <a class="iref" href="#rfc.iref.s.33"><b>9.4.15</b></a>, <a class="iref" href="#rfc.xref.status.414.2">11.2</a></li>
    2757                         <li class="indline1">415 Unsupported Media Type&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.415.1">5</a>, <a class="iref" href="#rfc.iref.s.34"><b>9.4.16</b></a>, <a class="iref" href="#rfc.xref.status.415.2">11.2</a></li>
    2758                         <li class="indline1">416 Requested Range Not Satisfiable&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.416.1">5</a>, <a class="iref" href="#rfc.iref.s.35"><b>9.4.17</b></a>, <a class="iref" href="#rfc.xref.status.416.2">11.2</a></li>
    2759                         <li class="indline1">417 Expectation Failed&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.417.1">5</a>, <a class="iref" href="#rfc.iref.s.36"><b>9.4.18</b></a>, <a class="iref" href="#rfc.xref.status.417.2">11.2</a></li>
    2760                         <li class="indline1">500 Internal Server Error&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.500.1">5</a>, <a class="iref" href="#rfc.iref.s.37"><b>9.5.1</b></a>, <a class="iref" href="#rfc.xref.status.500.2">11.2</a></li>
    2761                         <li class="indline1">501 Not Implemented&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.501.1">5</a>, <a class="iref" href="#rfc.iref.s.38"><b>9.5.2</b></a>, <a class="iref" href="#rfc.xref.status.501.2">11.2</a></li>
    2762                         <li class="indline1">502 Bad Gateway&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.502.1">5</a>, <a class="iref" href="#rfc.iref.s.39"><b>9.5.3</b></a>, <a class="iref" href="#rfc.xref.status.502.2">11.2</a></li>
    2763                         <li class="indline1">503 Service Unavailable&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.503.1">5</a>, <a class="iref" href="#rfc.iref.s.40"><b>9.5.4</b></a>, <a class="iref" href="#rfc.xref.status.503.2">11.2</a></li>
    2764                         <li class="indline1">504 Gateway Timeout&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.504.1">5</a>, <a class="iref" href="#rfc.iref.s.41"><b>9.5.5</b></a>, <a class="iref" href="#rfc.xref.status.504.2">11.2</a>, <a class="iref" href="#rfc.xref.status.504.3">A.1</a></li>
    2765                         <li class="indline1">505 HTTP Version Not Supported&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.505.1">5</a>, <a class="iref" href="#rfc.iref.s.42"><b>9.5.6</b></a>, <a class="iref" href="#rfc.xref.status.505.2">11.2</a></li>
     2730                        <li class="indline1">100 Continue&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.100.1">4</a>, <a class="iref" href="#rfc.iref.s.2"><b>8.1.1</b></a>, <a class="iref" href="#rfc.xref.status.100.2">10.2</a></li>
     2731                        <li class="indline1">101 Switching Protocols&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.101.1">4</a>, <a class="iref" href="#rfc.iref.s.3"><b>8.1.2</b></a>, <a class="iref" href="#rfc.xref.status.101.2">10.2</a></li>
     2732                        <li class="indline1">200 OK&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.200.1">4</a>, <a class="iref" href="#rfc.iref.s.4"><b>8.2.1</b></a>, <a class="iref" href="#rfc.xref.status.200.2">10.2</a></li>
     2733                        <li class="indline1">201 Created&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.201.1">4</a>, <a class="iref" href="#rfc.iref.s.5"><b>8.2.2</b></a>, <a class="iref" href="#rfc.xref.status.201.2">10.2</a>, <a class="iref" href="#rfc.xref.status.201.3">A.1</a></li>
     2734                        <li class="indline1">202 Accepted&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.202.1">4</a>, <a class="iref" href="#rfc.iref.s.6"><b>8.2.3</b></a>, <a class="iref" href="#rfc.xref.status.202.2">10.2</a></li>
     2735                        <li class="indline1">203 Non-Authoritative Information&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.203.1">4</a>, <a class="iref" href="#rfc.iref.s.7"><b>8.2.4</b></a>, <a class="iref" href="#rfc.xref.status.203.2">10.2</a></li>
     2736                        <li class="indline1">204 No Content&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.204.1">4</a>, <a class="iref" href="#rfc.iref.s.8"><b>8.2.5</b></a>, <a class="iref" href="#rfc.xref.status.204.2">10.2</a></li>
     2737                        <li class="indline1">205 Reset Content&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.205.1">4</a>, <a class="iref" href="#rfc.iref.s.9"><b>8.2.6</b></a>, <a class="iref" href="#rfc.xref.status.205.2">10.2</a></li>
     2738                        <li class="indline1">206 Partial Content&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.206.1">4</a>, <a class="iref" href="#rfc.iref.s.10"><b>8.2.7</b></a>, <a class="iref" href="#rfc.xref.status.206.2">10.2</a></li>
     2739                        <li class="indline1">300 Multiple Choices&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.300.1">4</a>, <a class="iref" href="#rfc.iref.s.11"><b>8.3.1</b></a>, <a class="iref" href="#rfc.xref.status.300.2">10.2</a></li>
     2740                        <li class="indline1">301 Moved Permanently&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.301.1">4</a>, <a class="iref" href="#rfc.iref.s.12"><b>8.3.2</b></a>, <a class="iref" href="#rfc.xref.status.301.2">10.2</a>, <a class="iref" href="#rfc.xref.status.301.3">A.2</a></li>
     2741                        <li class="indline1">302 Found&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.302.1">4</a>, <a class="iref" href="#rfc.iref.s.13"><b>8.3.3</b></a>, <a class="iref" href="#rfc.xref.status.302.2">10.2</a>, <a class="iref" href="#rfc.xref.status.302.3">A.2</a></li>
     2742                        <li class="indline1">303 See Other&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.303.1">4</a>, <a class="iref" href="#rfc.iref.s.14"><b>8.3.4</b></a>, <a class="iref" href="#rfc.xref.status.303.2">10.2</a></li>
     2743                        <li class="indline1">304 Not Modified&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.304.1">4</a>, <a class="iref" href="#rfc.iref.s.15"><b>8.3.5</b></a>, <a class="iref" href="#rfc.xref.status.304.2">10.2</a></li>
     2744                        <li class="indline1">305 Use Proxy&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.305.1">4</a>, <a class="iref" href="#rfc.iref.s.16"><b>8.3.6</b></a>, <a class="iref" href="#rfc.xref.status.305.2">10.2</a>, <a class="iref" href="#rfc.xref.status.305.3">A.2</a></li>
     2745                        <li class="indline1">306 (Unused)&nbsp;&nbsp;<a class="iref" href="#rfc.iref.s.17"><b>8.3.7</b></a>, <a class="iref" href="#rfc.xref.status.306.1">10.2</a></li>
     2746                        <li class="indline1">307 Temporary Redirect&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.307.1">4</a>, <a class="iref" href="#rfc.iref.s.18"><b>8.3.8</b></a>, <a class="iref" href="#rfc.xref.status.307.2">10.2</a>, <a class="iref" href="#rfc.xref.status.307.3">A.2</a></li>
     2747                        <li class="indline1">400 Bad Request&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.400.1">4</a>, <a class="iref" href="#rfc.iref.s.19"><b>8.4.1</b></a>, <a class="iref" href="#rfc.xref.status.400.2">10.2</a></li>
     2748                        <li class="indline1">401 Unauthorized&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.401.1">4</a>, <a class="iref" href="#rfc.iref.s.20"><b>8.4.2</b></a>, <a class="iref" href="#rfc.xref.status.401.2">10.2</a></li>
     2749                        <li class="indline1">402 Payment Required&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.402.1">4</a>, <a class="iref" href="#rfc.iref.s.21"><b>8.4.3</b></a>, <a class="iref" href="#rfc.xref.status.402.2">10.2</a></li>
     2750                        <li class="indline1">403 Forbidden&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.403.1">4</a>, <a class="iref" href="#rfc.iref.s.22"><b>8.4.4</b></a>, <a class="iref" href="#rfc.xref.status.403.2">10.2</a>, <a class="iref" href="#rfc.xref.status.403.3">A.1</a></li>
     2751                        <li class="indline1">404 Not Found&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.404.1">4</a>, <a class="iref" href="#rfc.iref.s.23"><b>8.4.5</b></a>, <a class="iref" href="#rfc.xref.status.404.2">10.2</a>, <a class="iref" href="#rfc.xref.status.404.3">A.1</a></li>
     2752                        <li class="indline1">405 Method Not Allowed&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.405.1">4</a>, <a class="iref" href="#rfc.iref.s.24"><b>8.4.6</b></a>, <a class="iref" href="#rfc.xref.status.405.2">10.2</a></li>
     2753                        <li class="indline1">406 Not Acceptable&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.406.1">4</a>, <a class="iref" href="#rfc.iref.s.25"><b>8.4.7</b></a>, <a class="iref" href="#rfc.xref.status.406.2">10.2</a></li>
     2754                        <li class="indline1">407 Proxy Authentication Required&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.407.1">4</a>, <a class="iref" href="#rfc.iref.s.26"><b>8.4.8</b></a>, <a class="iref" href="#rfc.xref.status.407.2">10.2</a></li>
     2755                        <li class="indline1">408 Request Timeout&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.408.1">4</a>, <a class="iref" href="#rfc.iref.s.27"><b>8.4.9</b></a>, <a class="iref" href="#rfc.xref.status.408.2">10.2</a></li>
     2756                        <li class="indline1">409 Conflict&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.409.1">4</a>, <a class="iref" href="#rfc.iref.s.28"><b>8.4.10</b></a>, <a class="iref" href="#rfc.xref.status.409.2">10.2</a></li>
     2757                        <li class="indline1">410 Gone&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.410.1">4</a>, <a class="iref" href="#rfc.iref.s.29"><b>8.4.11</b></a>, <a class="iref" href="#rfc.xref.status.410.2">10.2</a>, <a class="iref" href="#rfc.xref.status.410.3">A.1</a></li>
     2758                        <li class="indline1">411 Length Required&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.411.1">4</a>, <a class="iref" href="#rfc.iref.s.30"><b>8.4.12</b></a>, <a class="iref" href="#rfc.xref.status.411.2">10.2</a></li>
     2759                        <li class="indline1">412 Precondition Failed&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.412.1">4</a>, <a class="iref" href="#rfc.iref.s.31"><b>8.4.13</b></a>, <a class="iref" href="#rfc.xref.status.412.2">10.2</a></li>
     2760                        <li class="indline1">413 Request Entity Too Large&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.413.1">4</a>, <a class="iref" href="#rfc.iref.s.32"><b>8.4.14</b></a>, <a class="iref" href="#rfc.xref.status.413.2">10.2</a></li>
     2761                        <li class="indline1">414 Request-target Too Long&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.414.1">4</a>, <a class="iref" href="#rfc.iref.s.33"><b>8.4.15</b></a>, <a class="iref" href="#rfc.xref.status.414.2">10.2</a></li>
     2762                        <li class="indline1">415 Unsupported Media Type&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.415.1">4</a>, <a class="iref" href="#rfc.iref.s.34"><b>8.4.16</b></a>, <a class="iref" href="#rfc.xref.status.415.2">10.2</a></li>
     2763                        <li class="indline1">416 Requested Range Not Satisfiable&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.416.1">4</a>, <a class="iref" href="#rfc.iref.s.35"><b>8.4.17</b></a>, <a class="iref" href="#rfc.xref.status.416.2">10.2</a></li>
     2764                        <li class="indline1">417 Expectation Failed&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.417.1">4</a>, <a class="iref" href="#rfc.iref.s.36"><b>8.4.18</b></a>, <a class="iref" href="#rfc.xref.status.417.2">10.2</a></li>
     2765                        <li class="indline1">500 Internal Server Error&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.500.1">4</a>, <a class="iref" href="#rfc.iref.s.37"><b>8.5.1</b></a>, <a class="iref" href="#rfc.xref.status.500.2">10.2</a></li>
     2766                        <li class="indline1">501 Not Implemented&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.501.1">4</a>, <a class="iref" href="#rfc.iref.s.38"><b>8.5.2</b></a>, <a class="iref" href="#rfc.xref.status.501.2">10.2</a></li>
     2767                        <li class="indline1">502 Bad Gateway&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.502.1">4</a>, <a class="iref" href="#rfc.iref.s.39"><b>8.5.3</b></a>, <a class="iref" href="#rfc.xref.status.502.2">10.2</a></li>
     2768                        <li class="indline1">503 Service Unavailable&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.503.1">4</a>, <a class="iref" href="#rfc.iref.s.40"><b>8.5.4</b></a>, <a class="iref" href="#rfc.xref.status.503.2">10.2</a></li>
     2769                        <li class="indline1">504 Gateway Timeout&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.504.1">4</a>, <a class="iref" href="#rfc.iref.s.41"><b>8.5.5</b></a>, <a class="iref" href="#rfc.xref.status.504.2">10.2</a>, <a class="iref" href="#rfc.xref.status.504.3">A.1</a></li>
     2770                        <li class="indline1">505 HTTP Version Not Supported&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.505.1">4</a>, <a class="iref" href="#rfc.iref.s.42"><b>8.5.6</b></a>, <a class="iref" href="#rfc.xref.status.505.2">10.2</a></li>
    27662771                     </ul>
    27672772                  </li>
     
    27692774            </li>
    27702775            <li class="indline0"><a id="rfc.index.T" href="#rfc.index.T"><b>T</b></a><ul class="ind">
    2771                   <li class="indline1">TRACE method&nbsp;&nbsp;<a class="iref" href="#rfc.xref.TRACE.1">3</a>, <a class="iref" href="#rfc.iref.t.1"><b>8.8</b></a>, <a class="iref" href="#rfc.xref.TRACE.2">10.5</a>, <a class="iref" href="#rfc.xref.TRACE.3">11.1</a></li>
     2776                  <li class="indline1">TRACE method&nbsp;&nbsp;<a class="iref" href="#rfc.xref.TRACE.1">2</a>, <a class="iref" href="#rfc.iref.t.1"><b>7.8</b></a>, <a class="iref" href="#rfc.xref.TRACE.2">9.5</a>, <a class="iref" href="#rfc.xref.TRACE.3">10