Ignore:
Timestamp:
11/12/08 16:02:40 (11 years ago)
Author:
julian.reschke@…
Message:

Synchronize with trunk (../latest), with the exception of Part 6. Fix P7 where it pointed into a section that was removed from Part 6.

File:
1 edited

Legend:

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

    r348 r437  
    333333  }
    334334  @top-right {
    335        content: "November 2008";
     335       content: "December 2008";
    336336  }
    337337  @top-center {
     
    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">
    381       <link rel="Appendix" title="B Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.B">
     380      <link rel="Appendix" title="B Collected ABNF" href="#rfc.section.B">
     381      <link rel="Appendix" title="C Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.C">
    382382      <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.400, 2008-10-10 14:04:14, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">
    383383      <link rel="schema.DC" href="http://purl.org/dc/elements/1.1/">
     
    392392      <meta name="DC.Creator" content="Reschke, J. F.">
    393393      <meta name="DC.Identifier" content="urn:ietf:id:draft-ietf-httpbis-p2-semantics-latest">
    394       <meta name="DC.Date.Issued" scheme="ISO8601" content="2008-11">
     394      <meta name="DC.Date.Issued" scheme="ISO8601" content="2008-12">
    395395      <meta name="DC.Relation.Replaces" content="urn:ietf:rfc:2616">
    396396      <meta name="DC.Description.Abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 2 of the seven-part specification that defines the protocol referred to as &#34;HTTP/1.1&#34; and, taken together, obsoletes RFC 2616. Part 2 defines the semantics of HTTP messages as expressed by request methods, request-header fields, response status codes, and response-header fields.">
     
    428428         </tr>
    429429         <tr>
    430             <td class="header left">Expires: May 2009</td>
     430            <td class="header left">Expires: June 2009</td>
    431431            <td class="header right">H. Frystyk</td>
    432432         </tr>
     
    477477         <tr>
    478478            <td class="header left"></td>
    479             <td class="header right">November 12, 2008</td>
     479            <td class="header right">December 11, 2008</td>
    480480         </tr>
    481481      </table>
     
    497497      <p>The list of Internet-Draft Shadow Directories can be accessed at &lt;<a href="http://www.ietf.org/shadow.html">http://www.ietf.org/shadow.html</a>&gt;.
    498498      </p>
    499       <p>This Internet-Draft will expire in May 2009.</p>
     499      <p>This Internet-Draft will expire in June 2009.</p>
    500500      <h1 id="rfc.abstract"><a href="#rfc.abstract">Abstract</a></h1>
    501501      <p>The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information
     
    509509         list is at &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/report/11">http://tools.ietf.org/wg/httpbis/trac/report/11</a>&gt; and related documents (including fancy diffs) can be found at &lt;<a href="http://tools.ietf.org/wg/httpbis/">http://tools.ietf.org/wg/httpbis/</a>&gt;.
    510510      </p> 
    511       <p>The changes in this draft are summarized in <a href="#changes.since.04" title="Since draft-ietf-httpbis-p2-semantics-04">Appendix&nbsp;B.6</a>.
     511      <p>The changes in this draft are summarized in <a href="#changes.since.05" title="Since draft-ietf-httpbis-p2-semantics-05">Appendix&nbsp;C.7</a>.
    512512      </p>
    513513      <hr class="noprint">
     
    516516         <li class="tocline0">1.&nbsp;&nbsp;&nbsp;<a href="#introduction">Introduction</a><ul class="toc">
    517517               <li class="tocline1">1.1&nbsp;&nbsp;&nbsp;<a href="#intro.requirements">Requirements</a></li>
    518             </ul>
    519          </li>
    520          <li class="tocline0">2.&nbsp;&nbsp;&nbsp;<a href="#notation">Notational Conventions and Generic Grammar</a></li>
    521          <li class="tocline0">3.&nbsp;&nbsp;&nbsp;<a href="#method">Method</a><ul class="toc">
    522                <li class="tocline1">3.1&nbsp;&nbsp;&nbsp;<a href="#method.registry">Method Registry</a></li>
    523             </ul>
    524          </li>
    525          <li class="tocline0">4.&nbsp;&nbsp;&nbsp;<a href="#request.header.fields">Request Header Fields</a></li>
    526          <li class="tocline0">5.&nbsp;&nbsp;&nbsp;<a href="#status.code.and.reason.phrase">Status Code and Reason Phrase</a><ul class="toc">
    527                <li class="tocline1">5.1&nbsp;&nbsp;&nbsp;<a href="#status.code.registry">Status Code Registry</a></li>
    528             </ul>
    529          </li>
    530          <li class="tocline0">6.&nbsp;&nbsp;&nbsp;<a href="#response.header.fields">Response Header Fields</a></li>
    531          <li class="tocline0">7.&nbsp;&nbsp;&nbsp;<a href="#entity">Entity</a></li>
    532          <li class="tocline0">8.&nbsp;&nbsp;&nbsp;<a href="#method.definitions">Method Definitions</a><ul class="toc">
    533                <li class="tocline1">8.1&nbsp;&nbsp;&nbsp;<a href="#safe.and.idempotent">Safe and Idempotent Methods</a><ul class="toc">
    534                      <li class="tocline1">8.1.1&nbsp;&nbsp;&nbsp;<a href="#safe.methods">Safe Methods</a></li>
    535                      <li class="tocline1">8.1.2&nbsp;&nbsp;&nbsp;<a href="#idempotent.methods">Idempotent Methods</a></li>
    536                   </ul>
    537                </li>
    538                <li class="tocline1">8.2&nbsp;&nbsp;&nbsp;<a href="#OPTIONS">OPTIONS</a></li>
    539                <li class="tocline1">8.3&nbsp;&nbsp;&nbsp;<a href="#GET">GET</a></li>
    540                <li class="tocline1">8.4&nbsp;&nbsp;&nbsp;<a href="#HEAD">HEAD</a></li>
    541                <li class="tocline1">8.5&nbsp;&nbsp;&nbsp;<a href="#POST">POST</a></li>
    542                <li class="tocline1">8.6&nbsp;&nbsp;&nbsp;<a href="#PUT">PUT</a></li>
    543                <li class="tocline1">8.7&nbsp;&nbsp;&nbsp;<a href="#DELETE">DELETE</a></li>
    544                <li class="tocline1">8.8&nbsp;&nbsp;&nbsp;<a href="#TRACE">TRACE</a></li>
    545                <li class="tocline1">8.9&nbsp;&nbsp;&nbsp;<a href="#CONNECT">CONNECT</a></li>
    546             </ul>
    547          </li>
    548          <li class="tocline0">9.&nbsp;&nbsp;&nbsp;<a href="#status.codes">Status Code Definitions</a><ul class="toc">
    549                <li class="tocline1">9.1&nbsp;&nbsp;&nbsp;<a href="#status.1xx">Informational 1xx</a><ul class="toc">
    550                      <li class="tocline1">9.1.1&nbsp;&nbsp;&nbsp;<a href="#status.100">100 Continue</a></li>
    551                      <li class="tocline1">9.1.2&nbsp;&nbsp;&nbsp;<a href="#status.101">101 Switching Protocols</a></li>
    552                   </ul>
    553                </li>
    554                <li class="tocline1">9.2&nbsp;&nbsp;&nbsp;<a href="#status.2xx">Successful 2xx</a><ul class="toc">
    555                      <li class="tocline1">9.2.1&nbsp;&nbsp;&nbsp;<a href="#status.200">200 OK</a></li>
    556                      <li class="tocline1">9.2.2&nbsp;&nbsp;&nbsp;<a href="#status.201">201 Created</a></li>
    557                      <li class="tocline1">9.2.3&nbsp;&nbsp;&nbsp;<a href="#status.202">202 Accepted</a></li>
    558                      <li class="tocline1">9.2.4&nbsp;&nbsp;&nbsp;<a href="#status.203">203 Non-Authoritative Information</a></li>
    559                      <li class="tocline1">9.2.5&nbsp;&nbsp;&nbsp;<a href="#status.204">204 No Content</a></li>
    560                      <li class="tocline1">9.2.6&nbsp;&nbsp;&nbsp;<a href="#status.205">205 Reset Content</a></li>
    561                      <li class="tocline1">9.2.7&nbsp;&nbsp;&nbsp;<a href="#status.206">206 Partial Content</a></li>
    562                   </ul>
    563                </li>
    564                <li class="tocline1">9.3&nbsp;&nbsp;&nbsp;<a href="#status.3xx">Redirection 3xx</a><ul class="toc">
    565                      <li class="tocline1">9.3.1&nbsp;&nbsp;&nbsp;<a href="#status.300">300 Multiple Choices</a></li>
    566                      <li class="tocline1">9.3.2&nbsp;&nbsp;&nbsp;<a href="#status.301">301 Moved Permanently</a></li>
    567                      <li class="tocline1">9.3.3&nbsp;&nbsp;&nbsp;<a href="#status.302">302 Found</a></li>
    568                      <li class="tocline1">9.3.4&nbsp;&nbsp;&nbsp;<a href="#status.303">303 See Other</a></li>
    569                      <li class="tocline1">9.3.5&nbsp;&nbsp;&nbsp;<a href="#status.304">304 Not Modified</a></li>
    570                      <li class="tocline1">9.3.6&nbsp;&nbsp;&nbsp;<a href="#status.305">305 Use Proxy</a></li>
    571                      <li class="tocline1">9.3.7&nbsp;&nbsp;&nbsp;<a href="#status.306">306 (Unused)</a></li>
    572                      <li class="tocline1">9.3.8&nbsp;&nbsp;&nbsp;<a href="#status.307">307 Temporary Redirect</a></li>
    573                   </ul>
    574                </li>
    575                <li class="tocline1">9.4&nbsp;&nbsp;&nbsp;<a href="#status.4xx">Client Error 4xx</a><ul class="toc">
    576                      <li class="tocline1">9.4.1&nbsp;&nbsp;&nbsp;<a href="#status.400">400 Bad Request</a></li>
    577                      <li class="tocline1">9.4.2&nbsp;&nbsp;&nbsp;<a href="#status.401">401 Unauthorized</a></li>
    578                      <li class="tocline1">9.4.3&nbsp;&nbsp;&nbsp;<a href="#status.402">402 Payment Required</a></li>
    579                      <li class="tocline1">9.4.4&nbsp;&nbsp;&nbsp;<a href="#status.403">403 Forbidden</a></li>
    580                      <li class="tocline1">9.4.5&nbsp;&nbsp;&nbsp;<a href="#status.404">404 Not Found</a></li>
    581                      <li class="tocline1">9.4.6&nbsp;&nbsp;&nbsp;<a href="#status.405">405 Method Not Allowed</a></li>
    582                      <li class="tocline1">9.4.7&nbsp;&nbsp;&nbsp;<a href="#status.406">406 Not Acceptable</a></li>
    583                      <li class="tocline1">9.4.8&nbsp;&nbsp;&nbsp;<a href="#status.407">407 Proxy Authentication Required</a></li>
    584                      <li class="tocline1">9.4.9&nbsp;&nbsp;&nbsp;<a href="#status.408">408 Request Timeout</a></li>
    585                      <li class="tocline1">9.4.10&nbsp;&nbsp;&nbsp;<a href="#status.409">409 Conflict</a></li>
    586                      <li class="tocline1">9.4.11&nbsp;&nbsp;&nbsp;<a href="#status.410">410 Gone</a></li>
    587                      <li class="tocline1">9.4.12&nbsp;&nbsp;&nbsp;<a href="#status.411">411 Length Required</a></li>
    588                      <li class="tocline1">9.4.13&nbsp;&nbsp;&nbsp;<a href="#status.412">412 Precondition Failed</a></li>
    589                      <li class="tocline1">9.4.14&nbsp;&nbsp;&nbsp;<a href="#status.413">413 Request Entity Too Large</a></li>
    590                      <li class="tocline1">9.4.15&nbsp;&nbsp;&nbsp;<a href="#status.414">414 Request-URI Too Long</a></li>
    591                      <li class="tocline1">9.4.16&nbsp;&nbsp;&nbsp;<a href="#status.415">415 Unsupported Media Type</a></li>
    592                      <li class="tocline1">9.4.17&nbsp;&nbsp;&nbsp;<a href="#status.416">416 Requested Range Not Satisfiable</a></li>
    593                      <li class="tocline1">9.4.18&nbsp;&nbsp;&nbsp;<a href="#status.417">417 Expectation Failed</a></li>
    594                   </ul>
    595                </li>
    596                <li class="tocline1">9.5&nbsp;&nbsp;&nbsp;<a href="#status.5xx">Server Error 5xx</a><ul class="toc">
    597                      <li class="tocline1">9.5.1&nbsp;&nbsp;&nbsp;<a href="#status.500">500 Internal Server Error</a></li>
    598                      <li class="tocline1">9.5.2&nbsp;&nbsp;&nbsp;<a href="#status.501">501 Not Implemented</a></li>
    599                      <li class="tocline1">9.5.3&nbsp;&nbsp;&nbsp;<a href="#status.502">502 Bad Gateway</a></li>
    600                      <li class="tocline1">9.5.4&nbsp;&nbsp;&nbsp;<a href="#status.503">503 Service Unavailable</a></li>
    601                      <li class="tocline1">9.5.5&nbsp;&nbsp;&nbsp;<a href="#status.504">504 Gateway Timeout</a></li>
    602                      <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>
    603521                  </ul>
    604522               </li>
    605523            </ul>
    606524         </li>
    607          <li class="tocline0">10.&nbsp;&nbsp;&nbsp;<a href="#header.fields">Header Field Definitions</a><ul class="toc">
    608                <li class="tocline1">10.1&nbsp;&nbsp;&nbsp;<a href="#header.allow">Allow</a></li>
    609                <li class="tocline1">10.2&nbsp;&nbsp;&nbsp;<a href="#header.expect">Expect</a></li>
    610                <li class="tocline1">10.3&nbsp;&nbsp;&nbsp;<a href="#header.from">From</a></li>
    611                <li class="tocline1">10.4&nbsp;&nbsp;&nbsp;<a href="#header.location">Location</a></li>
    612                <li class="tocline1">10.5&nbsp;&nbsp;&nbsp;<a href="#header.max-forwards">Max-Forwards</a></li>
    613                <li class="tocline1">10.6&nbsp;&nbsp;&nbsp;<a href="#header.referer">Referer</a></li>
    614                <li class="tocline1">10.7&nbsp;&nbsp;&nbsp;<a href="#header.retry-after">Retry-After</a></li>
    615                <li class="tocline1">10.8&nbsp;&nbsp;&nbsp;<a href="#header.server">Server</a></li>
    616                <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>
    617527            </ul>
    618528         </li>
    619          <li class="tocline0">11.&nbsp;&nbsp;&nbsp;<a href="#IANA.considerations">IANA Considerations</a><ul class="toc">
    620                <li class="tocline1">11.1&nbsp;&nbsp;&nbsp;<a href="#method.registration">Method Registry</a></li>
    621                <li class="tocline1">11.2&nbsp;&nbsp;&nbsp;<a href="#status.code.registration">Status Code Registry</a></li>
    622                <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>
    623532            </ul>
    624533         </li>
    625          <li class="tocline0">12.&nbsp;&nbsp;&nbsp;<a href="#security.considerations">Security Considerations</a><ul class="toc">
    626                <li class="tocline1">12.1&nbsp;&nbsp;&nbsp;<a href="#security.sensitive">Transfer of Sensitive Information</a></li>
    627                <li class="tocline1">12.2&nbsp;&nbsp;&nbsp;<a href="#encoding.sensitive.information.in.uris">Encoding Sensitive Information in URIs</a></li>
    628                <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>
    629550            </ul>
    630551         </li>
    631          <li class="tocline0">13.&nbsp;&nbsp;&nbsp;<a href="#ack">Acknowledgments</a></li>
    632          <li class="tocline0">14.&nbsp;&nbsp;&nbsp;<a href="#rfc.references">References</a><ul class="toc">
    633                <li class="tocline1">14.1&nbsp;&nbsp;&nbsp;<a href="#rfc.references.1">Normative References</a></li>
    634                <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>
    635639            </ul>
    636640         </li>
     
    641645            </ul>
    642646         </li>
    643          <li class="tocline0">B.&nbsp;&nbsp;&nbsp;<a href="#change.log">Change Log (to be removed by RFC Editor before publication)</a><ul class="toc">
    644                <li class="tocline1">B.1&nbsp;&nbsp;&nbsp;<a href="#rfc.section.B.1">Since RFC2616</a></li>
    645                <li class="tocline1">B.2&nbsp;&nbsp;&nbsp;<a href="#rfc.section.B.2">Since draft-ietf-httpbis-p2-semantics-00</a></li>
    646                <li class="tocline1">B.3&nbsp;&nbsp;&nbsp;<a href="#rfc.section.B.3">Since draft-ietf-httpbis-p2-semantics-01</a></li>
    647                <li class="tocline1">B.4&nbsp;&nbsp;&nbsp;<a href="#changes.since.02">Since draft-ietf-httpbis-p2-semantics-02</a></li>
    648                <li class="tocline1">B.5&nbsp;&nbsp;&nbsp;<a href="#changes.since.03">Since draft-ietf-httpbis-p2-semantics-03</a></li>
    649                <li class="tocline1">B.6&nbsp;&nbsp;&nbsp;<a href="#changes.since.04">Since draft-ietf-httpbis-p2-semantics-04</a></li>
     647         <li class="tocline0">B.&nbsp;&nbsp;&nbsp;<a href="#collected.abnf">Collected ABNF</a></li>
     648         <li class="tocline0">C.&nbsp;&nbsp;&nbsp;<a href="#change.log">Change Log (to be removed by RFC Editor before publication)</a><ul class="toc">
     649               <li class="tocline1">C.1&nbsp;&nbsp;&nbsp;<a href="#rfc.section.C.1">Since RFC2616</a></li>
     650               <li class="tocline1">C.2&nbsp;&nbsp;&nbsp;<a href="#rfc.section.C.2">Since draft-ietf-httpbis-p2-semantics-00</a></li>
     651               <li class="tocline1">C.3&nbsp;&nbsp;&nbsp;<a href="#rfc.section.C.3">Since draft-ietf-httpbis-p2-semantics-01</a></li>
     652               <li class="tocline1">C.4&nbsp;&nbsp;&nbsp;<a href="#changes.since.02">Since draft-ietf-httpbis-p2-semantics-02</a></li>
     653               <li class="tocline1">C.5&nbsp;&nbsp;&nbsp;<a href="#changes.since.03">Since draft-ietf-httpbis-p2-semantics-03</a></li>
     654               <li class="tocline1">C.6&nbsp;&nbsp;&nbsp;<a href="#changes.since.04">Since draft-ietf-httpbis-p2-semantics-04</a></li>
     655               <li class="tocline1">C.7&nbsp;&nbsp;&nbsp;<a href="#changes.since.05">Since draft-ietf-httpbis-p2-semantics-05</a></li>
    650656            </ul>
    651657         </li>
     
    671677      <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."
    672678      </p>
    673       <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>
    674       <p id="rfc.section.2.p.1">This specification uses the ABNF syntax defined in <a href="p1-messaging.html#notation.abnf" title="ABNF Extensions">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>: <span class="comment">[abnf.dep: ABNF syntax and basic rules will be adopted from RFC 5234, see &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>&gt;.]</span>
    675       </p>
    676       <div id="rfc.figure.u.1"></div><pre class="inline">  <a href="#notation" class="smpl">DIGIT</a>         = &lt;DIGIT, 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;
    677 </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.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;
    678   <a href="#notation" class="smpl">quoted-string</a> = &lt;quoted-string, 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;
    679   <a href="#notation" class="smpl">token</a>         = &lt;token, 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;
    680 </pre><div id="abnf.dependencies">
    681          <p id="rfc.section.2.p.4">                                                  The ABNF rules below are defined in other parts:</p>
    682       </div>
    683       <div id="rfc.figure.u.3"></div><pre class="inline">  <a href="#abnf.dependencies" class="smpl">absoluteURI</a>   = &lt;absoluteURI, defined in <a href="#Part1" id="rfc.xref.Part1.8"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#uri" title="Uniform Resource Identifiers">Section 2.1</a>&gt;
    684   <a href="#abnf.dependencies" class="smpl">fragment</a>      = &lt;fragment, 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#uri" title="Uniform Resource Identifiers">Section 2.1</a>&gt;
    685   <a href="#abnf.dependencies" class="smpl">Host</a>          = &lt;Host, 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#header.host" title="Host">Section 8.4</a>&gt;
    686   <a href="#abnf.dependencies" class="smpl">HTTP-date</a>     = &lt;HTTP-date, 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#full.date" title="Full Date">Section 3.2.1</a>&gt;
    687   <a href="#abnf.dependencies" class="smpl">product</a>       = &lt;product, 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#product.tokens" title="Product Tokens">Section 3.4</a>&gt;
    688   <a href="#abnf.dependencies" class="smpl">relativeURI</a>   = &lt;relativeURI, 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#uri" title="Uniform Resource Identifiers">Section 2.1</a>&gt;
    689   <a href="#abnf.dependencies" class="smpl">TE</a>            = &lt;TE, 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#header.upgrade" title="Upgrade">Section 8.8</a>&gt;
    690 </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;
     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>. The following core rules are included by reference, as defined in <a href="#RFC5234" id="rfc.xref.RFC5234.1"><cite title="Augmented BNF for Syntax Specifications: ABNF">[RFC5234]</cite></a>, <a href="http://tools.ietf.org/html/rfc5234#section-B.1">Appendix B.1</a>: ALPHA (letters), CR (carriage return), CRLF (CR LF), CTL (controls), DIGIT (decimal 0-9), DQUOTE (double quote), HEXDIG
     681         (hexadecimal 0-9/A-F/a-f), LF (line feed), OCTET (any 8-bit sequence of data), SP (space), VCHAR (any visible USASCII character),
     682         and WSP (whitespace).
     683      </p>
     684      <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>
     685      <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>:
     686      </p>
     687      <div id="rfc.figure.u.1"></div><pre class="inline">  <a href="#core.rules" class="smpl">comment</a>       = &lt;comment, 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;
     688  <a href="#core.rules" class="smpl">quoted-string</a> = &lt;quoted-string, 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;
     689  <a href="#core.rules" class="smpl">token</a>         = &lt;token, 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;
     690  <a href="#core.rules" class="smpl">OWS</a>           = &lt;OWS, 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;
     691  <a href="#core.rules" class="smpl">RWS</a>           = &lt;RWS, 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;
     692  <a href="#core.rules" class="smpl">obs-text</a>      = &lt;obs-text, 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;
     693</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>
     694      <p id="rfc.section.1.2.2.p.1">The ABNF rules below are defined in other parts:</p>
     695      <div id="rfc.figure.u.2"></div><pre class="inline">  <a href="#abnf.dependencies" class="smpl">absolute-URI</a>  = &lt;absolute-URI, defined in <a href="#Part1" id="rfc.xref.Part1.10"><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;
     696  <a href="#abnf.dependencies" class="smpl">fragment</a>      = &lt;fragment, defined in <a href="#Part1" id="rfc.xref.Part1.11"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#uri" title="Uniform Resource Identifiers">Section 2.1</a>&gt;
     697  <a href="#abnf.dependencies" class="smpl">Host</a>          = &lt;Host, 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#uri" title="Uniform Resource Identifiers">Section 2.1</a>&gt;
     698  <a href="#abnf.dependencies" class="smpl">HTTP-date</a>     = &lt;HTTP-date, 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#full.date" title="Full Date">Section 3.2.1</a>&gt;
     699  <a href="#abnf.dependencies" class="smpl">partial-URI</a>   = &lt;partial-URI, 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#uri" title="Uniform Resource Identifiers">Section 2.1</a>&gt;
     700  <a href="#abnf.dependencies" class="smpl">product</a>       = &lt;product, 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#product.tokens" title="Product Tokens">Section 3.4</a>&gt;
     701  <a href="#abnf.dependencies" class="smpl">TE</a>            = &lt;TE, 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#header.upgrade" title="Upgrade">Section 8.8</a>&gt;
     702</pre><div id="rfc.figure.u.3"></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;
    691703  <a href="#abnf.dependencies" class="smpl">Accept-Charset</a> =
    692              &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;
     704             &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;
    693705  <a href="#abnf.dependencies" class="smpl">Accept-Encoding</a> =
    694              &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;
     706             &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;
    695707  <a href="#abnf.dependencies" class="smpl">Accept-Language</a> =
    696              &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;
    697 </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;
    698   <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;
     708             &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;
     709</pre><div id="rfc.figure.u.4"></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;
     710  <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;
    699711  <a href="#abnf.dependencies" class="smpl">If-Modified-Since</a> =
    700              &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;
    701   <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;
     712             &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;
     713  <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;
    702714  <a href="#abnf.dependencies" class="smpl">If-Unmodified-Since</a> =
    703              &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;
    704 </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;
    705   <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;
    706   <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;
    707 </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;
    708   <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;
    709 </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;
     715             &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;
     716</pre><div id="rfc.figure.u.5"></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;
     717  <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;
     718  <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;
     719</pre><div id="rfc.figure.u.6"></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 4.1</a>&gt;
     720  <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 4.5</a>&gt;
     721</pre><div id="rfc.figure.u.7"></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;
    710722  <a href="#abnf.dependencies" class="smpl">Proxy-Authenticate</a> =
    711              &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;
     723             &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;
    712724  <a href="#abnf.dependencies" class="smpl">Proxy-Authorization</a> =
    713              &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;
     725             &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;
    714726  <a href="#abnf.dependencies" class="smpl">WWW-Authenticate</a> =
    715              &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;
    716 </pre><h1 id="rfc.section.3"><a href="#rfc.section.3">3.</a>&nbsp;<a id="method" href="#method">Method</a></h1>
    717       <p id="rfc.section.3.p.1">The Method token indicates the method to be performed on the resource identified by the Request-URI. The method is case-sensitive.</p>
    718       <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>
    719                  / %x47.45.54               ; "GET", <a href="#GET" id="rfc.xref.GET.1" title="GET">Section&nbsp;8.3</a>
    720                  / %x48.45.41.44            ; "HEAD", <a href="#HEAD" id="rfc.xref.HEAD.1" title="HEAD">Section&nbsp;8.4</a>
    721                  / %x50.4F.53.54            ; "POST", <a href="#POST" id="rfc.xref.POST.1" title="POST">Section&nbsp;8.5</a>
    722                  / %x50.55.54               ; "PUT", <a href="#PUT" id="rfc.xref.PUT.1" title="PUT">Section&nbsp;8.6</a>
    723                  / %x44.45.4C.45.54.45      ; "DELETE", <a href="#DELETE" id="rfc.xref.DELETE.1" title="DELETE">Section&nbsp;8.7</a>
    724                  / %x54.52.41.43.45         ; "TRACE", <a href="#TRACE" id="rfc.xref.TRACE.1" title="TRACE">Section&nbsp;8.8</a>
    725                  / %x43.4F.4E.4E.45.43.54   ; "CONNECT", <a href="#CONNECT" id="rfc.xref.CONNECT.1" title="CONNECT">Section&nbsp;8.9</a>
     727             &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;
     728</pre><h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a>&nbsp;<a id="method" href="#method">Method</a></h1>
     729      <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>
     730      <div id="rfc.figure.u.8"></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>
     731                 / %x47.45.54               ; "GET", <a href="#GET" id="rfc.xref.GET.1" title="GET">Section&nbsp;7.3</a>
     732                 / %x48.45.41.44            ; "HEAD", <a href="#HEAD" id="rfc.xref.HEAD.1" title="HEAD">Section&nbsp;7.4</a>
     733                 / %x50.4F.53.54            ; "POST", <a href="#POST" id="rfc.xref.POST.1" title="POST">Section&nbsp;7.5</a>
     734                 / %x50.55.54               ; "PUT", <a href="#PUT" id="rfc.xref.PUT.1" title="PUT">Section&nbsp;7.6</a>
     735                 / %x44.45.4C.45.54.45      ; "DELETE", <a href="#DELETE" id="rfc.xref.DELETE.1" title="DELETE">Section&nbsp;7.7</a>
     736                 / %x54.52.41.43.45         ; "TRACE", <a href="#TRACE" id="rfc.xref.TRACE.1" title="TRACE">Section&nbsp;7.8</a>
     737                 / %x43.4F.4E.4E.45.43.54   ; "CONNECT", <a href="#CONNECT" id="rfc.xref.CONNECT.1" title="CONNECT">Section&nbsp;7.9</a>
    726738                 / <a href="#method" class="smpl">extension-method</a>
    727   <a href="#method" class="smpl">extension-method</a> = <a href="#notation" class="smpl">token</a>
    728 </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
     739  <a href="#method" class="smpl">extension-method</a> = <a href="#core.rules" class="smpl">token</a>
     740</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
    729741         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
    730742         resource, and 501 (Not Implemented) if the method is unrecognized or not implemented by the origin server. The methods GET
    731          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>.
    732       </p>
    733       <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>
    734       <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>
    735       <p id="rfc.section.3.1.p.2">Registrations <em class="bcp14">MUST</em> include the following fields:
     743         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>.
     744      </p>
     745      <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>
     746      <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>
     747      <p id="rfc.section.2.1.p.2">Registrations <em class="bcp14">MUST</em> include the following fields:
    736748      </p>
    737749      <ul>
    738          <li>Method Name (see <a href="#method" title="Method">Section&nbsp;3</a>)
    739          </li>
    740          <li>Safe ("yes" or "no", see <a href="#safe.methods" title="Safe Methods">Section&nbsp;8.1.1</a>)
     750         <li>Method Name (see <a href="#method" title="Method">Section&nbsp;2</a>)
     751         </li>
     752         <li>Safe ("yes" or "no", see <a href="#safe.methods" title="Safe Methods">Section&nbsp;7.1.1</a>)
    741753         </li>
    742754         <li>Pointer to specification text</li>
    743755      </ul>
    744       <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
     756      <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
    745757         document.
    746758      </p>
    747       <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;.
    748       </p>
    749       <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>
    750       <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,
     759      <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;.
     760      </p>
     761      <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>
     762      <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,
    751763         to the server. These fields act as request modifiers, with semantics equivalent to the parameters on a programming language
    752764         method invocation.
    753765      </p>
    754       <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>
    755                  / <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>
    756                  / <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>
    757                  / <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>
    758                  / <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>
    759                  / <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>
    760                  / <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>
    761                  / <a href="#abnf.dependencies" class="smpl">Host</a>                     ; <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#header.host" title="Host">Section 8.4</a>
    762                  / <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>
    763                  / <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>
    764                  / <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>
    765                  / <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>
    766                  / <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>
    767                  / <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>
    768                  / <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>
    769                  / <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>
    770                  / <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>
    771                  / <a href="#abnf.dependencies" class="smpl">TE</a>                       ; <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#header.upgrade" title="Upgrade">Section 8.8</a>
    772                  / <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>
    773 </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
     766      <div id="rfc.figure.u.9"></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>
     767                 / <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>
     768                 / <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>
     769                 / <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>
     770                 / <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>
     771                 / <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>
     772                 / <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>
     773                 / <a href="#abnf.dependencies" class="smpl">Host</a>                     ; <a href="#Part1" id="rfc.xref.Part1.17"><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>
     774                 / <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>
     775                 / <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>
     776                 / <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>
     777                 / <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>
     778                 / <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>
     779                 / <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>
     780                 / <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>
     781                 / <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>
     782                 / <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>
     783                 / <a href="#abnf.dependencies" class="smpl">TE</a>                       ; <a href="#Part1" id="rfc.xref.Part1.18"><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>
     784                 / <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>
     785</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
    774786         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.
    775787         Unrecognized header fields are treated as entity-header fields.
    776788      </p>
    777       <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>
    778       <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
    779          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
     789      <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>
     790      <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
     791         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
    780792         by automata and the Reason-Phrase is intended for the human user. The client is not required to examine or display the Reason-Phrase.
    781793      </p>
    782       <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,
     794      <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,
    783795         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.
    784796      </p>
    785       <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>    =
    786          "100"  ; <a href="#status.100" id="rfc.xref.status.100.1" title="100 Continue">Section&nbsp;9.1.1</a>: Continue
    787        / "101"  ; <a href="#status.101" id="rfc.xref.status.101.1" title="101 Switching Protocols">Section&nbsp;9.1.2</a>: Switching Protocols
    788        / "200"  ; <a href="#status.200" id="rfc.xref.status.200.1" title="200 OK">Section&nbsp;9.2.1</a>: OK
    789        / "201"  ; <a href="#status.201" id="rfc.xref.status.201.1" title="201 Created">Section&nbsp;9.2.2</a>: Created
    790        / "202"  ; <a href="#status.202" id="rfc.xref.status.202.1" title="202 Accepted">Section&nbsp;9.2.3</a>: Accepted
    791        / "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
    792        / "204"  ; <a href="#status.204" id="rfc.xref.status.204.1" title="204 No Content">Section&nbsp;9.2.5</a>: No Content
    793        / "205"  ; <a href="#status.205" id="rfc.xref.status.205.1" title="205 Reset Content">Section&nbsp;9.2.6</a>: Reset Content
    794        / "206"  ; <a href="#status.206" id="rfc.xref.status.206.1" title="206 Partial Content">Section&nbsp;9.2.7</a>: Partial Content
    795        / "300"  ; <a href="#status.300" id="rfc.xref.status.300.1" title="300 Multiple Choices">Section&nbsp;9.3.1</a>: Multiple Choices
    796        / "301"  ; <a href="#status.301" id="rfc.xref.status.301.1" title="301 Moved Permanently">Section&nbsp;9.3.2</a>: Moved Permanently
    797        / "302"  ; <a href="#status.302" id="rfc.xref.status.302.1" title="302 Found">Section&nbsp;9.3.3</a>: Found
    798        / "303"  ; <a href="#status.303" id="rfc.xref.status.303.1" title="303 See Other">Section&nbsp;9.3.4</a>: See Other
    799        / "304"  ; <a href="#status.304" id="rfc.xref.status.304.1" title="304 Not Modified">Section&nbsp;9.3.5</a>: Not Modified
    800        / "305"  ; <a href="#status.305" id="rfc.xref.status.305.1" title="305 Use Proxy">Section&nbsp;9.3.6</a>: Use Proxy
    801        / "307"  ; <a href="#status.307" id="rfc.xref.status.307.1" title="307 Temporary Redirect">Section&nbsp;9.3.8</a>: Temporary Redirect
    802        / "400"  ; <a href="#status.400" id="rfc.xref.status.400.1" title="400 Bad Request">Section&nbsp;9.4.1</a>: Bad Request
    803        / "401"  ; <a href="#status.401" id="rfc.xref.status.401.1" title="401 Unauthorized">Section&nbsp;9.4.2</a>: Unauthorized
    804        / "402"  ; <a href="#status.402" id="rfc.xref.status.402.1" title="402 Payment Required">Section&nbsp;9.4.3</a>: Payment Required
    805        / "403"  ; <a href="#status.403" id="rfc.xref.status.403.1" title="403 Forbidden">Section&nbsp;9.4.4</a>: Forbidden
    806        / "404"  ; <a href="#status.404" id="rfc.xref.status.404.1" title="404 Not Found">Section&nbsp;9.4.5</a>: Not Found
    807        / "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
    808        / "406"  ; <a href="#status.406" id="rfc.xref.status.406.1" title="406 Not Acceptable">Section&nbsp;9.4.7</a>: Not Acceptable
    809        / "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
    810        / "408"  ; <a href="#status.408" id="rfc.xref.status.408.1" title="408 Request Timeout">Section&nbsp;9.4.9</a>: Request Time-out
    811        / "409"  ; <a href="#status.409" id="rfc.xref.status.409.1" title="409 Conflict">Section&nbsp;9.4.10</a>: Conflict
    812        / "410"  ; <a href="#status.410" id="rfc.xref.status.410.1" title="410 Gone">Section&nbsp;9.4.11</a>: Gone
    813        / "411"  ; <a href="#status.411" id="rfc.xref.status.411.1" title="411 Length Required">Section&nbsp;9.4.12</a>: Length Required
    814        / "412"  ; <a href="#status.412" id="rfc.xref.status.412.1" title="412 Precondition Failed">Section&nbsp;9.4.13</a>: Precondition Failed
    815        / "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
    816        / "414"  ; <a href="#status.414" id="rfc.xref.status.414.1" title="414 Request-URI Too Long">Section&nbsp;9.4.15</a>: Request-URI Too Large
    817        / "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
    818        / "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
    819        / "417"  ; <a href="#status.417" id="rfc.xref.status.417.1" title="417 Expectation Failed">Section&nbsp;9.4.18</a>: Expectation Failed
    820        / "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
    821        / "501"  ; <a href="#status.501" id="rfc.xref.status.501.1" title="501 Not Implemented">Section&nbsp;9.5.2</a>: Not Implemented
    822        / "502"  ; <a href="#status.502" id="rfc.xref.status.502.1" title="502 Bad Gateway">Section&nbsp;9.5.3</a>: Bad Gateway
    823        / "503"  ; <a href="#status.503" id="rfc.xref.status.503.1" title="503 Service Unavailable">Section&nbsp;9.5.4</a>: Service Unavailable
    824        / "504"  ; <a href="#status.504" id="rfc.xref.status.504.1" title="504 Gateway Timeout">Section&nbsp;9.5.5</a>: Gateway Time-out
    825        / "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
    826        / <a href="#request.header.fields" class="smpl">extension-code</a>
    827 
    828   <a href="#request.header.fields" class="smpl">extension-code</a> = 3<a href="#notation" class="smpl">DIGIT</a>
    829   <a href="#status.code.and.reason.phrase" class="smpl">Reason-Phrase</a>  = *&lt;TEXT, excluding CR, LF&gt;
    830 </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,
     797      <div id="rfc.figure.u.10"></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>    =
     798         "100"  ; <a href="#status.100" id="rfc.xref.status.100.1" title="100 Continue">Section&nbsp;8.1.1</a>: Continue
     799       / "101"  ; <a href="#status.101" id="rfc.xref.status.101.1" title="101 Switching Protocols">Section&nbsp;8.1.2</a>: Switching Protocols
     800       / "200"  ; <a href="#status.200" id="rfc.xref.status.200.1" title="200 OK">Section&nbsp;8.2.1</a>: OK
     801       / "201"  ; <a href="#status.201" id="rfc.xref.status.201.1" title="201 Created">Section&nbsp;8.2.2</a>: Created
     802       / "202"  ; <a href="#status.202" id="rfc.xref.status.202.1" title="202 Accepted">Section&nbsp;8.2.3</a>: Accepted
     803       / "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
     804       / "204"  ; <a href="#status.204" id="rfc.xref.status.204.1" title="204 No Content">Section&nbsp;8.2.5</a>: No Content
     805       / "205"  ; <a href="#status.205" id="rfc.xref.status.205.1" title="205 Reset Content">Section&nbsp;8.2.6</a>: Reset Content
     806       / "206"  ; <a href="#status.206" id="rfc.xref.status.206.1" title="206 Partial Content">Section&nbsp;8.2.7</a>: Partial Content
     807       / "300"  ; <a href="#status.300" id="rfc.xref.status.300.1" title="300 Multiple Choices">Section&nbsp;8.3.1</a>: Multiple Choices
     808       / "301"  ; <a href="#status.301" id="rfc.xref.status.301.1" title="301 Moved Permanently">Section&nbsp;8.3.2</a>: Moved Permanently
     809       / "302"  ; <a href="#status.302" id="rfc.xref.status.302.1" title="302 Found">Section&nbsp;8.3.3</a>: Found
     810       / "303"  ; <a href="#status.303" id="rfc.xref.status.303.1" title="303 See Other">Section&nbsp;8.3.4</a>: See Other
     811       / "304"  ; <a href="#status.304" id="rfc.xref.status.304.1" title="304 Not Modified">Section&nbsp;8.3.5</a>: Not Modified
     812       / "305"  ; <a href="#status.305" id="rfc.xref.status.305.1" title="305 Use Proxy">Section&nbsp;8.3.6</a>: Use Proxy
     813       / "307"  ; <a href="#status.307" id="rfc.xref.status.307.1" title="307 Temporary Redirect">Section&nbsp;8.3.8</a>: Temporary Redirect
     814       / "400"  ; <a href="#status.400" id="rfc.xref.status.400.1" title="400 Bad Request">Section&nbsp;8.4.1</a>: Bad Request
     815       / "401"  ; <a href="#status.401" id="rfc.xref.status.401.1" title="401 Unauthorized">Section&nbsp;8.4.2</a>: Unauthorized
     816       / "402"  ; <a href="#status.402" id="rfc.xref.status.402.1" title="402 Payment Required">Section&nbsp;8.4.3</a>: Payment Required
     817       / "403"  ; <a href="#status.403" id="rfc.xref.status.403.1" title="403 Forbidden">Section&nbsp;8.4.4</a>: Forbidden
     818       / "404"  ; <a href="#status.404" id="rfc.xref.status.404.1" title="404 Not Found">Section&nbsp;8.4.5</a>: Not Found
     819       / "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
     820       / "406"  ; <a href="#status.406" id="rfc.xref.status.406.1" title="406 Not Acceptable">Section&nbsp;8.4.7</a>: Not Acceptable
     821       / "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
     822       / "408"  ; <a href="#status.408" id="rfc.xref.status.408.1" title="408 Request Timeout">Section&nbsp;8.4.9</a>: Request Time-out
     823       / "409"  ; <a href="#status.409" id="rfc.xref.status.409.1" title="409 Conflict">Section&nbsp;8.4.10</a>: Conflict
     824       / "410"  ; <a href="#status.410" id="rfc.xref.status.410.1" title="410 Gone">Section&nbsp;8.4.11</a>: Gone
     825       / "411"  ; <a href="#status.411" id="rfc.xref.status.411.1" title="411 Length Required">Section&nbsp;8.4.12</a>: Length Required
     826       / "412"  ; <a href="#status.412" id="rfc.xref.status.412.1" title="412 Precondition Failed">Section&nbsp;8.4.13</a>: Precondition Failed
     827       / "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
     828       / "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
     829       / "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
     830       / "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
     831       / "417"  ; <a href="#status.417" id="rfc.xref.status.417.1" title="417 Expectation Failed">Section&nbsp;8.4.18</a>: Expectation Failed
     832       / "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
     833       / "501"  ; <a href="#status.501" id="rfc.xref.status.501.1" title="501 Not Implemented">Section&nbsp;8.5.2</a>: Not Implemented
     834       / "502"  ; <a href="#status.502" id="rfc.xref.status.502.1" title="502 Bad Gateway">Section&nbsp;8.5.3</a>: Bad Gateway
     835       / "503"  ; <a href="#status.503" id="rfc.xref.status.503.1" title="503 Service Unavailable">Section&nbsp;8.5.4</a>: Service Unavailable
     836       / "504"  ; <a href="#status.504" id="rfc.xref.status.504.1" title="504 Gateway Timeout">Section&nbsp;8.5.5</a>: Gateway Time-out
     837       / "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
     838       / <a href="#status.code.and.reason.phrase" class="smpl">extension-code</a>
     839
     840  <a href="#status.code.and.reason.phrase" class="smpl">extension-code</a> = 3<a href="#notation" class="smpl">DIGIT</a>
     841  <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="#core.rules" class="smpl">obs-text</a> )
     842</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,
    831843         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
    832844         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
     
    834846         which will explain the unusual status.
    835847      </p>
    836       <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>
    837       <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>
    838       <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
     848      <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>
     849      <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>
     850      <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
    839851         document.
    840852      </p>
    841       <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;.
    842       </p>
    843       <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>
    844       <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
     853      <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;.
     854      </p>
     855      <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>
     856      <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
    845857         Status-Line. These header fields give information about the server and about further access to the resource identified by
    846          the Request-URI.
    847       </p>
    848       <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>
    849                   / <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>
    850                   / <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>
    851                   / <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>
    852                   / <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>
    853                   / <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>
    854                   / <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>
    855                   / <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>
    856                   / <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>
    857                   / <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>
    858 </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
     858         the request-target.
     859      </p>
     860      <div id="rfc.figure.u.11"></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>
     861                  / <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 4.1</a>
     862                  / <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>
     863                  / <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>
     864                  / <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>
     865                  / <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>
     866                  / <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>
     867                  / <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>
     868                  / <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 4.5</a>
     869                  / <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>
     870</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
    859871         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
    860872         fields. Unrecognized header fields are treated as entity-header fields.
    861873      </p>
    862       <h1 id="rfc.section.7"><a href="#rfc.section.7">7.</a>&nbsp;<a id="entity" href="#entity">Entity</a></h1>
    863       <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
     874      <h1 id="rfc.section.6"><a href="#rfc.section.6">6.</a>&nbsp;<a id="entity" href="#entity">Entity</a></h1>
     875      <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
    864876         fields and an entity-body, although some responses will only include the entity-headers. HTTP entity-body and entity-header
    865877         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>.
    866878      </p>
    867       <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.17"><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
     879      <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.19"><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
    868880         safe and proper transfer of the message.
    869881      </p>
    870       <h1 id="rfc.section.8"><a href="#rfc.section.8">8.</a>&nbsp;<a id="method.definitions" href="#method.definitions">Method Definitions</a></h1>
    871       <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
     882      <h1 id="rfc.section.7"><a href="#rfc.section.7">7.</a>&nbsp;<a id="method.definitions" href="#method.definitions">Method Definitions</a></h1>
     883      <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
    872884         to share the same semantics for separately extended clients and servers.
    873885      </p>
    874       <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>
     886      <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>
    875887      <div id="rfc.iref.s.1"></div>
    876       <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>
    877       <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
     888      <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>
     889      <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
    878890         careful to allow the user to be aware of any actions they might take which may have an unexpected significance to themselves
    879891         or others.
    880892      </p>
    881       <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
     893      <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
    882894         made aware of the fact that a possibly unsafe action is being requested.
    883895      </p>
    884       <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;
     896      <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;
    885897         in fact, some dynamic resources consider that a feature. The important distinction here is that the user did not request the
    886898         side-effects, so therefore cannot be held accountable for them.
    887899      </p>
    888900      <div id="rfc.iref.i.1"></div>
    889       <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>
    890       <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
     901      <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>
     902      <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
    891903         &gt; 0 identical requests is the same as for a single request. The methods GET, HEAD, PUT and DELETE share this property. Also,
    892904         the methods OPTIONS and TRACE <em class="bcp14">SHOULD NOT</em> have side effects, and so are inherently idempotent.
    893905      </p>
    894       <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
     906      <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
    895907         sequence are idempotent. (A sequence is idempotent if a single execution of the entire sequence always yields a result that
    896908         is not changed by a reexecution of all, or part, of that sequence.) For example, a sequence is non-idempotent if its result
    897909         depends on a value that is later modified in the same sequence.
    898910      </p>
    899       <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
     911      <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
    900912         on the same set of resources).
    901913      </p>
    902       <h2 id="rfc.section.8.2"><a href="#rfc.section.8.2">8.2</a>&nbsp;<a id="OPTIONS" href="#OPTIONS">OPTIONS</a></h2>
     914      <h2 id="rfc.section.7.2"><a href="#rfc.section.7.2">7.2</a>&nbsp;<a id="OPTIONS" href="#OPTIONS">OPTIONS</a></h2>
    903915      <div id="rfc.iref.o.1"></div>
    904916      <div id="rfc.iref.m.1"></div>
    905       <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
    906          chain identified by the Request-URI. This method allows the client to determine the options and/or requirements associated
     917      <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
     918         chain identified by the request-target. This method allows the client to determine the options and/or requirements associated
    907919         with a resource, or the capabilities of a server, without implying a resource action or initiating a resource retrieval.
    908920      </p>
    909       <p id="rfc.section.8.2.p.2">Responses to this method are not cacheable.</p>
    910       <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
     921      <p id="rfc.section.7.2.p.2">Responses to this method are not cacheable.</p>
     922      <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
    911923         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
    912924         to HTTP might use the OPTIONS body to make more detailed queries on the server.
    913925      </p>
    914       <p id="rfc.section.8.2.p.4">If the Request-URI is an asterisk ("*"), the OPTIONS request is intended to apply to the server in general rather than to
    915          a specific resource. Since a server's communication options typically depend on the resource, the "*" request is only useful
     926      <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
     927         to a specific resource. Since a server's communication options typically depend on the resource, the "*" request is only useful
    916928         as a "ping" or "no-op" type of method; it does nothing beyond allowing the client to test the capabilities of the server.
    917929         For example, this can be used to test a proxy for HTTP/1.1 compliance (or lack thereof).
    918930      </p>
    919       <p id="rfc.section.8.2.p.5">If the Request-URI is not an asterisk, the OPTIONS request applies only to the options that are available when communicating
     931      <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
    920932         with that resource.
    921933      </p>
    922       <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.,
     934      <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.,
    923935         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,
    924936         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".
    925937      </p>
    926       <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 absoluteURI for which
     938      <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
    927939         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
    928940         request <em class="bcp14">MUST NOT</em> include a Max-Forwards field.
    929941      </p>
    930       <h2 id="rfc.section.8.3"><a href="#rfc.section.8.3">8.3</a>&nbsp;<a id="GET" href="#GET">GET</a></h2>
     942      <h2 id="rfc.section.7.3"><a href="#rfc.section.7.3">7.3</a>&nbsp;<a id="GET" href="#GET">GET</a></h2>
    931943      <div id="rfc.iref.g.8"></div>
    932944      <div id="rfc.iref.m.2"></div>
    933       <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-URI. If the Request-URI
    934          refers to a data-producing process, it is the produced data which shall be returned as the entity in the response and not
    935          the source text of the process, unless that text happens to be the output of the process.
    936       </p>
    937       <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,
     945      <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
     946         request-target refers to a data-producing process, it is the produced data which shall be returned as the entity in the response
     947         and not the source text of the process, unless that text happens to be the output of the process.
     948      </p>
     949      <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,
    938950         If-Match, If-None-Match, or If-Range header field. A conditional GET method requests that the entity be transferred only under
    939951         the circumstances described by the conditional header field(s). The conditional GET method is intended to reduce unnecessary
     
    941953         held by the client.
    942954      </p>
    943       <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
    944          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
     955      <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
     956         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
    945957         without transferring data already held by the client.
    946958      </p>
    947       <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>.
    948       </p>
    949       <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.
    950       </p>
    951       <h2 id="rfc.section.8.4"><a href="#rfc.section.8.4">8.4</a>&nbsp;<a id="HEAD" href="#HEAD">HEAD</a></h2>
     959      <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>.
     960      </p>
     961      <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.
     962      </p>
     963      <h2 id="rfc.section.7.4"><a href="#rfc.section.7.4">7.4</a>&nbsp;<a id="HEAD" href="#HEAD">HEAD</a></h2>
    952964      <div id="rfc.iref.h.1"></div>
    953965      <div id="rfc.iref.m.3"></div>
    954       <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
     966      <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
    955967         the entity implied by the request without transferring the entity-body itself. This method is often used for testing hypertext
    956968         links for validity, accessibility, and recent modification.
    957969      </p>
    958       <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
     970      <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
    959971         from the current entity (as would be indicated by a change in Content-Length, Content-MD5, ETag or Last-Modified), then the
    960972         cache <em class="bcp14">MUST</em> treat the cache entry as stale.
     
    962974      <div id="rfc.iref.p.1"></div>
    963975      <div id="rfc.iref.m.4"></div>
    964       <h2 id="rfc.section.8.5"><a href="#rfc.section.8.5">8.5</a>&nbsp;<a id="POST" href="#POST">POST</a></h2>
    965       <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
    966          by the resource identified by the Request-URI in the Request-Line. POST is designed to allow a uniform method to cover the
    967          following functions:
     976      <h2 id="rfc.section.7.5"><a href="#rfc.section.7.5">7.5</a>&nbsp;<a id="POST" href="#POST">POST</a></h2>
     977      <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
     978         by the resource identified by the request-target in the Request-Line. POST is designed to allow a uniform method to cover
     979         the following functions:
    968980      </p>
    969981      <ul>
     
    973985         <li>Extending a database through an append operation.</li>
    974986      </ul>
    975       <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-URI.</p>
    976       <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
     987      <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>
     988      <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
    977989         200 (OK) or 204 (No Content) is the appropriate response status, depending on whether or not the response includes an entity
    978990         that describes the result.
    979991      </p>
    980       <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
    981          header (see <a href="#header.location" id="rfc.xref.header.location.2" title="Location">Section&nbsp;10.4</a>).
    982       </p>
    983       <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.
     992      <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
     993         header (see <a href="#header.location" id="rfc.xref.header.location.2" title="Location">Section&nbsp;9.4</a>).
     994      </p>
     995      <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.
    984996         However, the 303 (See Other) response can be used to direct the user agent to retrieve a cacheable resource.
    985997      </p>
    986998      <div id="rfc.iref.p.2"></div>
    987999      <div id="rfc.iref.m.5"></div>
    988       <h2 id="rfc.section.8.6"><a href="#rfc.section.8.6">8.6</a>&nbsp;<a id="PUT" href="#PUT">PUT</a></h2>
    989       <p id="rfc.section.8.6.p.1">The PUT method requests that the enclosed entity be stored at the supplied Request-URI. If the Request-URI refers to an already
    990          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-URI does not point to an existing
     1000      <h2 id="rfc.section.7.6"><a href="#rfc.section.7.6">7.6</a>&nbsp;<a id="PUT" href="#PUT">PUT</a></h2>
     1001      <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
     1002         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
    9911003         resource, and that URI is capable of being defined as a new resource by the requesting user agent, the origin server can create
    992          the resource with that URI. If a new resource is created at the Request-URI, the origin server <em class="bcp14">MUST</em> inform the user agent via the 201 (Created) response. If an existing resource is modified, either the 200 (OK) or 204 (No
    993          Content) response codes <em class="bcp14">SHOULD</em> be sent to indicate successful completion of the request. If the resource could not be created or modified with the Request-URI,
     1004         the resource with that URI. If a new resource is created at the request-target, the origin server <em class="bcp14">MUST</em> inform the user agent via the 201 (Created) response. If an existing resource is modified, either the 200 (OK) or 204 (No
     1005         Content) response codes <em class="bcp14">SHOULD</em> be sent to indicate successful completion of the request. If the resource could not be created or modified with the request-target,
    9941006         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.
    9951007      </p>
    996       <p id="rfc.section.8.6.p.2">If the request passes through a cache and the Request-URI 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.
    997       </p>
    998       <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-URI. The
    999          URI in a POST request identifies the resource that will handle the enclosed entity. That resource might be a data-accepting
     1008      <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.
     1009      </p>
     1010      <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.
     1011         The URI in a POST request identifies the resource that will handle the enclosed entity. That resource might be a data-accepting
    10001012         process, a gateway to some other protocol, or a separate entity that accepts annotations. In contrast, the URI in a PUT request
    10011013         identifies the entity enclosed with the request -- the user agent knows what URI is intended and the server <em class="bcp14">MUST NOT</em> attempt to apply the request to some other resource. If the server desires that the request be applied to a different URI,
    10021014         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.
    10031015      </p>
    1004       <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
     1016      <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
    10051017         is separate from the URI identifying each particular version. In this case, a PUT request on a general URI might result in
    10061018         several other URIs being defined by the origin server.
    10071019      </p>
    1008       <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>
    1009       <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.
     1020      <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>
     1021      <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.
    10101022      </p>
    10111023      <div id="rfc.iref.d.1"></div>
    10121024      <div id="rfc.iref.m.6"></div>
    1013       <h2 id="rfc.section.8.7"><a href="#rfc.section.8.7">8.7</a>&nbsp;<a id="DELETE" href="#DELETE">DELETE</a></h2>
    1014       <p id="rfc.section.8.7.p.1">The DELETE method requests that the origin server delete the resource identified by the Request-URI. 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
     1025      <h2 id="rfc.section.7.7"><a href="#rfc.section.7.7">7.7</a>&nbsp;<a id="DELETE" href="#DELETE">DELETE</a></h2>
     1026      <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
    10151027         has been carried out, even if the status code returned from the origin server indicates that the action has been completed
    10161028         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
    10171029         location.
    10181030      </p>
    1019       <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,
     1031      <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,
    10201032         or 204 (No Content) if the action has been enacted but the response does not include an entity.
    10211033      </p>
    1022       <p id="rfc.section.8.7.p.3">If the request passes through a cache and the Request-URI 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.
    1023       </p>
    1024       <h2 id="rfc.section.8.8"><a href="#rfc.section.8.8">8.8</a>&nbsp;<a id="TRACE" href="#TRACE">TRACE</a></h2>
     1034      <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.
     1035      </p>
     1036      <h2 id="rfc.section.7.8"><a href="#rfc.section.7.8">7.8</a>&nbsp;<a id="TRACE" href="#TRACE">TRACE</a></h2>
    10251037      <div id="rfc.iref.t.1"></div>
    10261038      <div id="rfc.iref.m.7"></div>
    1027       <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
     1039      <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
    10281040         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
    1029          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.
    1030       </p>
    1031       <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
    1032          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.18"><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
     1041         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.
     1042      </p>
     1043      <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
     1044         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.20"><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
    10331045         client to limit the length of the request chain, which is useful for testing a chain of proxies forwarding messages in an
    10341046         infinite loop.
    10351047      </p>
    1036       <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.19"><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.
     1048      <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.21"><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.
    10371049      </p>
    10381050      <div id="rfc.iref.c.1"></div>
    10391051      <div id="rfc.iref.m.8"></div>
    1040       <h2 id="rfc.section.8.9"><a href="#rfc.section.8.9">8.9</a>&nbsp;<a id="CONNECT" href="#CONNECT">CONNECT</a></h2>
    1041       <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.
     1052      <h2 id="rfc.section.7.9"><a href="#rfc.section.7.9">7.9</a>&nbsp;<a id="CONNECT" href="#CONNECT">CONNECT</a></h2>
     1053      <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.
    10421054         SSL tunneling <a href="#RFC2817" id="rfc.xref.RFC2817.1"><cite title="Upgrading to TLS Within HTTP/1.1">[RFC2817]</cite></a>).
    10431055      </p>
    1044       <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>
    1045       <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
     1056      <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>
     1057      <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
    10461058         in the response.
    10471059      </p>
    1048       <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>
    1049       <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
     1060      <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>
     1061      <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
    10501062         terminated by an empty line. There are no required headers for this class of status code. Since HTTP/1.0 did not define any
    10511063         1xx status codes, servers <em class="bcp14">MUST NOT</em> send a 1xx response to an HTTP/1.0 client except under experimental conditions.
    10521064      </p>
    1053       <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
     1065      <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
    10541066         (Continue) status message. Unexpected 1xx status responses <em class="bcp14">MAY</em> be ignored by a user agent.
    10551067      </p>
    1056       <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
     1068      <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
    10571069         requested the generation of the 1xx response. (For example, if a proxy adds a "Expect: 100-continue" field when it forwards
    10581070         a request, then it need not forward the corresponding 100 (Continue) response(s).)
     
    10601072      <div id="rfc.iref.25"></div>
    10611073      <div id="rfc.iref.s.2"></div>
    1062       <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>
    1063       <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
     1074      <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>
     1075      <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
    10641076         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
    1065          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.20"><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.
     1077         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.22"><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.
    10661078      </p>
    10671079      <div id="rfc.iref.26"></div>
    10681080      <div id="rfc.iref.s.3"></div>
    1069       <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>
    1070       <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
     1081      <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>
     1082      <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
    10711083         by the response's Upgrade header field immediately after the empty line which terminates the 101 response.
    10721084      </p>
    1073       <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
     1085      <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
    10741086         older versions, and switching to a real-time, synchronous protocol might be advantageous when delivering resources that use
    10751087         such features.
    10761088      </p>
    1077       <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>
    1078       <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>
     1089      <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>
     1090      <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>
    10791091      <div id="rfc.iref.27"></div>
    10801092      <div id="rfc.iref.s.4"></div>
    1081       <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>
    1082       <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
     1093      <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>
     1094      <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
    10831095         example:
    10841096      </p>
     
    10951107      <div id="rfc.iref.28"></div>
    10961108      <div id="rfc.iref.s.5"></div>
    1097       <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>
    1098       <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
     1109      <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>
     1110      <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
    10991111         by the URI(s) returned in the entity of the response, with the most specific URI for the resource given by a Location header
    11001112         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
     
    11021114         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.
    11031115      </p>
    1104       <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,
    1105          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>.
     1116      <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,
     1117         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>.
    11061118      </p>
    11071119      <div id="rfc.iref.29"></div>
    11081120      <div id="rfc.iref.s.6"></div>
    1109       <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>
    1110       <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
     1121      <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>
     1122      <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
    11111123         be acted upon, as it might be disallowed when processing actually takes place. There is no facility for re-sending a status
    11121124         code from an asynchronous operation such as this.
    11131125      </p>
    1114       <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
     1126      <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
    11151127         (perhaps a batch-oriented process that is only run once per day) without requiring that the user agent's connection to the
    11161128         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
     
    11191131      <div id="rfc.iref.30"></div>
    11201132      <div id="rfc.iref.s.7"></div>
    1121       <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>
    1122       <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
     1133      <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>
     1134      <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
    11231135         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
    11241136         result in a superset of the metainformation known by the origin server. Use of this response code is not required and is only
     
    11271139      <div id="rfc.iref.31"></div>
    11281140      <div id="rfc.iref.s.8"></div>
    1129       <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>
    1130       <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.
     1141      <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>
     1142      <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.
    11311143         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.
    11321144      </p>
    1133       <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
     1145      <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
    11341146         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.
    11351147      </p>
    1136       <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.
     1148      <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.
    11371149      </p>
    11381150      <div id="rfc.iref.32"></div>
    11391151      <div id="rfc.iref.s.9"></div>
    1140       <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>
    1141       <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
     1152      <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>
     1153      <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
    11421154         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
    11431155         another input action. The response <em class="bcp14">MUST NOT</em> include an entity.
     
    11451157      <div id="rfc.iref.33"></div>
    11461158      <div id="rfc.iref.s.10"></div>
    1147       <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>
    1148       <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
     1159      <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>
     1160      <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
    11491161         in <a href="#Part5" id="rfc.xref.Part5.9"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>.
    11501162      </p>
    1151       <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>
    1152       <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.
     1163      <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>
     1164      <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.
    11531165         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
    11541166         GET or HEAD. A client <em class="bcp14">SHOULD</em> detect infinite redirection loops, since such loops generate network traffic for each redirection.
     
    11611173      <div id="rfc.iref.34"></div>
    11621174      <div id="rfc.iref.s.11"></div>
    1163       <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>
    1164       <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
    1165          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
     1175      <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>
     1176      <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
     1177         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
    11661178         location.
    11671179      </p>
    1168       <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
     1180      <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
    11691181         the one most appropriate. The entity format is specified by the media type given in the Content-Type header field. Depending
    11701182         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.
    11711183      </p>
    1172       <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.
     1184      <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.
    11731185      </p>
    11741186      <div id="rfc.iref.35"></div>
    11751187      <div id="rfc.iref.s.12"></div>
    1176       <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>
    1177       <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-URI
     1188      <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>
     1189      <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
    11781190         to one or more of the new references returned by the server, where possible. This response is cacheable unless indicated otherwise.
    11791191      </p>
    1180       <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).
    1181       </p>
    1182       <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
     1192      <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).
     1193      </p>
     1194      <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
    11831195         the request was issued.
    11841196      </p>
     
    11901202      <div id="rfc.iref.36"></div>
    11911203      <div id="rfc.iref.s.13"></div>
    1192       <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>
    1193       <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
    1194          client <em class="bcp14">SHOULD</em> continue to use the Request-URI for future requests. This response is only cacheable if indicated by a Cache-Control or Expires
    1195          header field.
    1196       </p>
    1197       <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).
    1198       </p>
    1199       <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
     1204      <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>
     1205      <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
     1206         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
     1207         Expires header field.
     1208      </p>
     1209      <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).
     1210      </p>
     1211      <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
    12001212         the request was issued.
    12011213      </p>
     
    12091221      <div id="rfc.iref.37"></div>
    12101222      <div id="rfc.iref.s.14"></div>
    1211       <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>
    1212       <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
     1223      <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>
     1224      <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
    12131225         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,
    12141226         be redirected again, or end with an error status. The Location URI is not a substitute reference for the originally requested
    12151227         resource.
    12161228      </p>
    1217       <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
     1229      <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
    12181230         the user agent to a selected resource, since doing so provides the information corresponding to the POST response in a form
    12191231         that can be separately identified, bookmarked, and cached independent of the original request.
    12201232      </p>
    1221       <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
     1233      <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
    12221234         transferred by the server over HTTP. The Location URI indicates a resource that is descriptive of the requested resource such
    12231235         that the follow-on representation may be useful without implying that it adequately represents the previously requested resource.
     
    12251237         description are outside the scope of HTTP and thus entirely determined by the resource owner(s).
    12261238      </p>
    1227       <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,
     1239      <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,
    12281240         the entity of a 303 response <em class="bcp14">SHOULD</em> contain a short hypertext note with a hyperlink to the Location URI.
    12291241      </p>
    12301242      <div id="rfc.iref.38"></div>
    12311243      <div id="rfc.iref.s.15"></div>
    1232       <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>
    1233       <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,
     1244      <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>
     1245      <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,
    12341246         as defined in <a href="#Part4" id="rfc.xref.Part4.12"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>.
    12351247      </p>
    12361248      <div id="rfc.iref.39"></div>
    12371249      <div id="rfc.iref.s.16"></div>
    1238       <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>
    1239       <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.
     1250      <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>
     1251      <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.
    12401252      </p>
    12411253      <div id="rfc.iref.40"></div>
    12421254      <div id="rfc.iref.s.17"></div>
    1243       <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>
    1244       <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>
     1255      <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>
     1256      <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>
    12451257      <div id="rfc.iref.41"></div>
    12461258      <div id="rfc.iref.s.18"></div>
    1247       <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>
    1248       <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-URI for future requests. This response is only cacheable if indicated by a Cache-Control or Expires
    1249          header field.
    1250       </p>
    1251       <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
     1259      <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>
     1260      <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
     1261         Expires header field.
     1262      </p>
     1263      <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
    12521264         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.
    12531265      </p>
    1254       <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
     1266      <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
    12551267         the request was issued.
    12561268      </p>
    1257       <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>
    1258       <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
     1269      <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>
     1270      <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
    12591271         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.
    12601272         These status codes are applicable to any request method. User agents <em class="bcp14">SHOULD</em> display any included entity to the user.
    12611273      </p>
    1262       <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
     1274      <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
    12631275         the input connection. If the client continues sending data to the server after the close, the server's TCP stack will send
    12641276         a reset packet to the client, which may erase the client's unacknowledged input buffers before they can be read and interpreted
     
    12671279      <div id="rfc.iref.42"></div>
    12681280      <div id="rfc.iref.s.19"></div>
    1269       <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>
    1270       <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.
     1281      <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>
     1282      <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.
    12711283      </p>
    12721284      <div id="rfc.iref.43"></div>
    12731285      <div id="rfc.iref.s.20"></div>
    1274       <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>
    1275       <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>).
     1286      <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>
     1287      <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>).
    12761288      </p>
    12771289      <div id="rfc.iref.44"></div>
    12781290      <div id="rfc.iref.s.21"></div>
    1279       <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>
    1280       <p id="rfc.section.9.4.3.p.1">This code is reserved for future use.</p>
     1291      <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>
     1292      <p id="rfc.section.8.4.3.p.1">This code is reserved for future use.</p>
    12811293      <div id="rfc.iref.45"></div>
    12821294      <div id="rfc.iref.s.22"></div>
    1283       <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>
    1284       <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,
     1295      <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>
     1296      <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,
    12851297         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,
    12861298         the status code 404 (Not Found) can be used instead.
     
    12881300      <div id="rfc.iref.46"></div>
    12891301      <div id="rfc.iref.s.23"></div>
    1290       <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>
    1291       <p id="rfc.section.9.4.5.p.1">The server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or
    1292          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
     1302      <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>
     1303      <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
     1304         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
    12931305         and has no forwarding address. This status code is commonly used when the server does not wish to reveal exactly why the request
    12941306         has been refused, or when no other response is applicable.
     
    12961308      <div id="rfc.iref.47"></div>
    12971309      <div id="rfc.iref.s.24"></div>
    1298       <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>
    1299       <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-URI. The response <em class="bcp14">MUST</em> include an Allow header containing a list of valid methods for the requested resource.
     1310      <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>
     1311      <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.
    13001312      </p>
    13011313      <div id="rfc.iref.48"></div>
    13021314      <div id="rfc.iref.s.25"></div>
    1303       <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>
    1304       <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
     1315      <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>
     1316      <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
    13051317         not acceptable according to the accept headers sent in the request.
    13061318      </p>
    1307       <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
     1319      <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
    13081320         can choose the one most appropriate. The entity format is specified by the media type given in the Content-Type header field.
    13091321         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.
     
    13151327         </dd>
    13161328      </dl>
    1317       <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.
     1329      <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.
    13181330      </p>
    13191331      <div id="rfc.iref.49"></div>
    13201332      <div id="rfc.iref.s.26"></div>
    1321       <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>
    1322       <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>).
     1333      <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>
     1334      <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>).
    13231335      </p>
    13241336      <div id="rfc.iref.50"></div>
    13251337      <div id="rfc.iref.s.27"></div>
    1326       <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>
    1327       <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.
     1338      <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>
     1339      <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.
    13281340      </p>
    13291341      <div id="rfc.iref.51"></div>
    13301342      <div id="rfc.iref.s.28"></div>
    1331       <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>
    1332       <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
     1343      <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>
     1344      <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
    13331345         situations where it is expected that the user might be able to resolve the conflict and resubmit the request. The response
    13341346         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
    13351347         enough information for the user or user agent to fix the problem; however, that might not be possible and is not required.
    13361348      </p>
    1337       <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
     1349      <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
    13381350         being PUT included changes to a resource which conflict with those made by an earlier (third-party) request, the server might
    13391351         use the 409 response to indicate that it can't complete the request. In this case, the response entity would likely contain
     
    13421354      <div id="rfc.iref.52"></div>
    13431355      <div id="rfc.iref.s.29"></div>
    1344       <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>
    1345       <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
    1346          to be considered permanent. Clients with link editing capabilities <em class="bcp14">SHOULD</em> delete references to the Request-URI after user approval. If the server does not know, or has no facility to determine, whether
    1347          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.
    1348       </p>
    1349       <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
     1356      <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>
     1357      <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
     1358         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,
     1359         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.
     1360      </p>
     1361      <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
    13501362         is intentionally unavailable and that the server owners desire that remote links to that resource be removed. Such an event
    13511363         is common for limited-time, promotional services and for resources belonging to individuals no longer working at the server's
     
    13551367      <div id="rfc.iref.53"></div>
    13561368      <div id="rfc.iref.s.30"></div>
    1357       <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>
    1358       <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
     1369      <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>
     1370      <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
    13591371         message.
    13601372      </p>
    13611373      <div id="rfc.iref.54"></div>
    13621374      <div id="rfc.iref.s.31"></div>
    1363       <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>
    1364       <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
     1375      <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>
     1376      <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
    13651377         defined in <a href="#Part4" id="rfc.xref.Part4.13"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>.
    13661378      </p>
    13671379      <div id="rfc.iref.55"></div>
    13681380      <div id="rfc.iref.s.32"></div>
    1369       <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>
    1370       <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.
     1381      <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>
     1382      <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.
    13711383         The server <em class="bcp14">MAY</em> close the connection to prevent the client from continuing the request.
    13721384      </p>
    1373       <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.
     1385      <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.
    13741386      </p>
    13751387      <div id="rfc.iref.56"></div>
    13761388      <div id="rfc.iref.s.33"></div>
    1377       <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-URI Too Long</a></h3>
    1378       <p id="rfc.section.9.4.15.p.1">The server is refusing to service the request because the Request-URI is longer than the server is willing to interpret. This
    1379          rare condition is only likely to occur when a client has improperly converted a POST request to a GET request with long query
    1380          information, when the client has descended into a URI "black hole" of redirection (e.g., a redirected URI prefix that points
    1381          to a suffix of itself), or when the server is under attack by a client attempting to exploit security holes present in some
    1382          servers using fixed-length buffers for reading or manipulating the Request-URI.
     1389      <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>
     1390      <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.
     1391         This rare condition is only likely to occur when a client has improperly converted a POST request to a GET request with long
     1392         query information, when the client has descended into a URI "black hole" of redirection (e.g., a redirected URI prefix that
     1393         points to a suffix of itself), or when the server is under attack by a client attempting to exploit security holes present
     1394         in some servers using fixed-length buffers for reading or manipulating the request-target.
    13831395      </p>
    13841396      <div id="rfc.iref.57"></div>
    13851397      <div id="rfc.iref.s.34"></div>
    1386       <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>
    1387       <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
     1398      <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>
     1399      <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
    13881400         resource for the requested method.
    13891401      </p>
    13901402      <div id="rfc.iref.58"></div>
    13911403      <div id="rfc.iref.s.35"></div>
    1392       <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>
    1393       <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.
     1404      <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>
     1405      <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.
    13941406      </p>
    13951407      <div id="rfc.iref.59"></div>
    13961408      <div id="rfc.iref.s.36"></div>
    1397       <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>
    1398       <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
     1409      <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>
     1410      <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
    13991411         not be met by the next-hop server.
    14001412      </p>
    1401       <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>
    1402       <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
     1413      <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>
     1414      <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
    14031415         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.
    14041416         User agents <em class="bcp14">SHOULD</em> display any included entity to the user. These response codes are applicable to any request method.
     
    14061418      <div id="rfc.iref.60"></div>
    14071419      <div id="rfc.iref.s.37"></div>
    1408       <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>
    1409       <p id="rfc.section.9.5.1.p.1">The server encountered an unexpected condition which prevented it from fulfilling the request.</p>
     1420      <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>
     1421      <p id="rfc.section.8.5.1.p.1">The server encountered an unexpected condition which prevented it from fulfilling the request.</p>
    14101422      <div id="rfc.iref.61"></div>
    14111423      <div id="rfc.iref.s.38"></div>
    1412       <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>
    1413       <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
     1424      <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>
     1425      <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
    14141426         does not recognize the request method and is not capable of supporting it for any resource.
    14151427      </p>
    14161428      <div id="rfc.iref.62"></div>
    14171429      <div id="rfc.iref.s.39"></div>
    1418       <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>
    1419       <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
     1430      <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>
     1431      <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
    14201432         to fulfill the request.
    14211433      </p>
    14221434      <div id="rfc.iref.63"></div>
    14231435      <div id="rfc.iref.s.40"></div>
    1424       <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>
    1425       <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
     1436      <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>
     1437      <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
    14261438         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.
    14271439      </p>
     
    14331445      <div id="rfc.iref.64"></div>
    14341446      <div id="rfc.iref.s.41"></div>
    1435       <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>
    1436       <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
     1447      <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>
     1448      <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
    14371449         URI (e.g. HTTP, FTP, LDAP) or some other auxiliary server (e.g. DNS) it needed to access in attempting to complete the request.
    14381450      </p>
     
    14431455      <div id="rfc.iref.65"></div>
    14441456      <div id="rfc.iref.s.42"></div>
    1445       <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>
    1446       <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
     1457      <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>
     1458      <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
    14471459         is indicating that it is unable or unwilling to complete the request using the same major version as the client, as described
    1448          in <a href="p1-messaging.html#http.version" title="HTTP Version">Section 3.1</a> of <a href="#Part1" id="rfc.xref.Part1.21"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, 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.
    1449       </p>
    1450       <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>
    1451       <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>
    1452       <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
     1460         in <a href="p1-messaging.html#http.version" title="HTTP Version">Section 3.1</a> of <a href="#Part1" id="rfc.xref.Part1.23"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, 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.
     1461      </p>
     1462      <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>
     1463      <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>
     1464      <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
    14531465         receives the entity.
    14541466      </p>
    14551467      <div id="rfc.iref.a.1"></div>
    14561468      <div id="rfc.iref.h.2"></div>
    1457       <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>
    1458       <p id="rfc.section.10.1.p.1">The Allow response-header field lists the set of methods advertised as supported by the resource identified by the Request-URI.
     1469      <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>
     1470      <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.
    14591471         The purpose of this field is strictly to inform the recipient of valid methods associated with the resource. An Allow header
    14601472         field <em class="bcp14">MUST</em> be present in a 405 (Method Not Allowed) response.
    14611473      </p>
    1462       <div id="rfc.figure.u.13"></div><pre class="inline"><span id="rfc.iref.g.9"></span>  <a href="#header.allow" class="smpl">Allow</a>   = "Allow" ":" #<a href="#method" class="smpl">Method</a>
    1463 </pre><p id="rfc.section.10.1.p.3">Example of use:</p>
    1464       <div id="rfc.figure.u.14"></div><pre class="text">       Allow: GET, HEAD, PUT
    1465 </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>
    1466       <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
     1474      <div id="rfc.figure.u.12"></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>
     1475  <a href="#header.allow" class="smpl">Allow-v</a> = #<a href="#method" class="smpl">Method</a>
     1476</pre><p id="rfc.section.9.1.p.3">Example of use:</p>
     1477      <div id="rfc.figure.u.13"></div><pre class="text">  Allow: GET, HEAD, PUT
     1478</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>
     1479      <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
    14671480         means of communicating with the origin server.
    14681481      </p>
    14691482      <div id="rfc.iref.e.1"></div>
    14701483      <div id="rfc.iref.h.3"></div>
    1471       <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>
    1472       <p id="rfc.section.10.2.p.1">The Expect request-header field is used to indicate that particular server behaviors are required by the client.</p>
    1473       <div id="rfc.figure.u.15"></div><pre class="inline"><span id="rfc.iref.g.10"></span><span id="rfc.iref.g.11"></span><span id="rfc.iref.g.12"></span><span id="rfc.iref.g.13"></span>  <a href="#header.expect" class="smpl">Expect</a>       =  "Expect" ":" 1#<a href="#header.expect" class="smpl">expectation</a>
     1484      <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>
     1485      <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>
     1486      <div id="rfc.figure.u.14"></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>
     1487  <a href="#header.expect" class="smpl">Expect-v</a>     = 1#<a href="#header.expect" class="smpl">expectation</a>
    14741488 
    1475   <a href="#header.expect" class="smpl">expectation</a>  =  "100-continue" / <a href="#header.expect" class="smpl">expectation-extension</a>
    1476   <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> )
     1489  <a href="#header.expect" class="smpl">expectation</a>  = "100-continue" / <a href="#header.expect" class="smpl">expectation-extension</a>
     1490  <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> )
    14771491                           *<a href="#header.expect" class="smpl">expect-params</a> ]
    1478   <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> ) ]
    1479 </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
     1492  <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> ) ]
     1493</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
    14801494         the request, some other 4xx status.
    14811495      </p>
    1482       <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
     1496      <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
    14831497         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.
    14841498      </p>
    1485       <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
     1499      <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
    14861500         for quoted-string expectation-extensions.
    14871501      </p>
    1488       <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
     1502      <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
    14891503         request-header itself is end-to-end; it <em class="bcp14">MUST</em> be forwarded if the request is forwarded.
    14901504      </p>
    1491       <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>
    1492       <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.22"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a> for the use of the 100 (Continue) status.
     1505      <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>
     1506      <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.24"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a> for the use of the 100 (Continue) status.
    14931507      </p>
    14941508      <div id="rfc.iref.f.1"></div>
    14951509      <div id="rfc.iref.h.4"></div>
    1496       <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>
    1497       <p id="rfc.section.10.3.p.1">The From request-header field, if given, <em class="bcp14">SHOULD</em> contain an Internet e-mail address for the human user who controls the requesting user agent. The address <em class="bcp14">SHOULD</em> be machine-usable, as defined by "mailbox" in <a href="http://tools.ietf.org/html/rfc5322#section-3.4">Section 3.4</a> of <a href="#RFC5322" id="rfc.xref.RFC5322.1"><cite title="Internet Message Format">[RFC5322]</cite></a>:
    1498       </p>
    1499       <div id="rfc.figure.u.16"></div><pre class="inline"><span id="rfc.iref.g.14"></span>  <a href="#header.from" class="smpl">From</a>    = "From" ":" <a href="#header.from" class="smpl">mailbox</a>
     1510      <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>
     1511      <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>:
     1512      </p>
     1513      <div id="rfc.figure.u.15"></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>
     1514  <a href="#header.from" class="smpl">From-v</a>  = <a href="#header.from" class="smpl">mailbox</a>
    15001515 
    15011516  <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;
    1502 </pre><p id="rfc.section.10.3.p.3">An example is:</p>
    1503       <div id="rfc.figure.u.17"></div><pre class="text">    From: webmaster@example.org
    1504 </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
     1517</pre><p id="rfc.section.9.3.p.3">An example is:</p>
     1518      <div id="rfc.figure.u.16"></div><pre class="text">  From: webmaster@example.org
     1519</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
    15051520         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
    15061521         end.
    15071522      </p>
    1508       <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
     1523      <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
    15091524         issuer's address <em class="bcp14">SHOULD</em> be used.
    15101525      </p>
    1511       <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
     1526      <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
    15121527         security policy. It is strongly recommended that the user be able to disable, enable, and modify the value of this field at
    15131528         any time prior to a request.
     
    15151530      <div id="rfc.iref.l.1"></div>
    15161531      <div id="rfc.iref.h.5"></div>
    1517       <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>
    1518       <p id="rfc.section.10.4.p.1">The Location response-header field is used for the identification of a new resource or to redirect the recipient to a location
    1519          other than the Request-URI for completion of the request. For 201 (Created) responses, the Location is that of the new resource
    1520          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
     1532      <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>
     1533      <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
     1534         other than the request-target for completion of the request. For 201 (Created) responses, the Location is that of the new
     1535         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
    15211536         URI.
    15221537      </p>
    1523       <div id="rfc.figure.u.18"></div><pre class="inline"><span id="rfc.iref.g.15"></span>  <a href="#header.location" class="smpl">Location</a>       = "Location" ":" <a href="#abnf.dependencies" class="smpl">absoluteURI</a> [ "#" <a href="#abnf.dependencies" class="smpl">fragment</a> ]
    1524 </pre><p id="rfc.section.10.4.p.3">An example is:</p>
    1525       <div id="rfc.figure.u.19"></div><pre class="text">    Location: http://www.example.org/pub/WWW/People.html
    1526 </pre><p id="rfc.section.10.4.p.5"> </p>
     1538      <div id="rfc.figure.u.17"></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>
     1539  <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> ]
     1540</pre><p id="rfc.section.9.4.p.3">An example is:</p>
     1541      <div id="rfc.figure.u.18"></div><pre class="text">  Location: http://www.example.org/pub/WWW/People.html
     1542</pre><p id="rfc.section.9.4.p.5"> </p>
    15271543      <dl class="empty">
    1528          <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.
     1544         <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.
    15291545            It is therefore possible for a response to contain header fields for both Location and Content-Location.
    15301546         </dd>
    15311547      </dl>
    1532       <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>
     1548      <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>
    15331549      <ul>
    15341550         <li>With a 201 Created response, because in this usage the Location header specifies the URL for the entire created resource.</li>
     
    15401556      <div id="rfc.iref.m.9"></div>
    15411557      <div id="rfc.iref.h.6"></div>
    1542       <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>
    1543       <p id="rfc.section.10.5.p.1">The Max-Forwards request-header 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
     1558      <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>
     1559      <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
    15441560         useful when the client is attempting to trace a request chain which appears to be failing or looping in mid-chain.
    15451561      </p>
    1546       <div id="rfc.figure.u.20"></div><pre class="inline"><span id="rfc.iref.g.16"></span>  <a href="#header.max-forwards" class="smpl">Max-Forwards</a>   = "Max-Forwards" ":" 1*<a href="#notation" class="smpl">DIGIT</a>
    1547 </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>
    1548       <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).
    1549       </p>
    1550       <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
     1562      <div id="rfc.figure.u.19"></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>
     1563  <a href="#header.max-forwards" class="smpl">Max-Forwards-v</a> = 1*<a href="#notation" class="smpl">DIGIT</a>
     1564</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>
     1565      <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).
     1566      </p>
     1567      <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
    15511568         referred to as part of that method definition.
    15521569      </p>
    15531570      <div id="rfc.iref.r.1"></div>
    15541571      <div id="rfc.iref.h.7"></div>
    1555       <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>
    1556       <p id="rfc.section.10.6.p.1">The Referer[sic] request-header field allows the client to specify, for the server's benefit, the address (URI) of the resource
    1557          from which the Request-URI was obtained (the "referrer", although the header field is misspelled.) The Referer request-header
    1558          allows a server to generate lists of back-links to resources for interest, logging, optimized caching, etc. It also allows
    1559          obsolete or mistyped links to be traced for maintenance. The Referer field <em class="bcp14">MUST NOT</em> be sent if the Request-URI was obtained from a source that does not have its own URI, such as input from the user keyboard.
    1560       </p>
    1561       <div id="rfc.figure.u.21"></div><pre class="inline"><span id="rfc.iref.g.17"></span>  <a href="#header.referer" class="smpl">Referer</a>        = "Referer" ":" ( <a href="#abnf.dependencies" class="smpl">absoluteURI</a> / <a href="#abnf.dependencies" class="smpl">relativeURI</a> )
    1562 </pre><p id="rfc.section.10.6.p.3">Example:</p>
    1563       <div id="rfc.figure.u.22"></div><pre class="text">    Referer: http://www.example.org/hypertext/Overview.html
    1564 </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-URI. The URI <em class="bcp14">MUST NOT</em> include a fragment. See <a href="#encoding.sensitive.information.in.uris" title="Encoding Sensitive Information in URIs">Section&nbsp;12.2</a> for security considerations.
     1572      <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>
     1573      <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
     1574         resource from which the request-target was obtained (the "referrer", although the header field is misspelled.) The Referer
     1575         request-header allows a server to generate lists of back-links to resources for interest, logging, optimized caching, etc.
     1576         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.
     1577      </p>
     1578      <div id="rfc.figure.u.20"></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>
     1579  <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>
     1580</pre><p id="rfc.section.9.6.p.3">Example:</p>
     1581      <div id="rfc.figure.u.21"></div><pre class="text">  Referer: http://www.example.org/hypertext/Overview.html
     1582</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.
    15651583      </p>
    15661584      <div id="rfc.iref.r.2"></div>
    15671585      <div id="rfc.iref.h.8"></div>
    1568       <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>
    1569       <p id="rfc.section.10.7.p.1">The Retry-After response-header field can be used with a 503 (Service Unavailable) response to indicate how long the service
     1586      <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>
     1587      <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
    15701588         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
    15711589         the redirected request. The value of this field can be either an HTTP-date or an integer number of seconds (in decimal) after
    15721590         the time of the response.
    15731591      </p>
    1574       <div id="rfc.figure.u.23"></div><pre class="inline"><span id="rfc.iref.g.18"></span>  <a href="#header.retry-after" class="smpl">Retry-After</a>   = "Retry-After" ":" ( <a href="#abnf.dependencies" class="smpl">HTTP-date</a> / <a href="#rule.delta-seconds" class="smpl">delta-seconds</a> )
     1592      <div id="rfc.figure.u.22"></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>
     1593  <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>
    15751594</pre><div id="rule.delta-seconds">
    1576          <p id="rfc.section.10.7.p.3">  Time spans are non-negative decimal integers, representing time in seconds.</p>
     1595         <p id="rfc.section.9.7.p.3">  Time spans are non-negative decimal integers, representing time in seconds.</p>
    15771596      </div>
    1578       <div id="rfc.figure.u.24"></div><pre class="inline"><span id="rfc.iref.g.19"></span>  <a href="#rule.delta-seconds" class="smpl">delta-seconds</a>  = 1*<a href="#notation" class="smpl">DIGIT</a>
    1579 </pre><p id="rfc.section.10.7.p.5">Two examples of its use are</p>
    1580       <div id="rfc.figure.u.25"></div><pre class="text">    Retry-After: Fri, 31 Dec 1999 23:59:59 GMT
    1581     Retry-After: 120
    1582 </pre><p id="rfc.section.10.7.p.7">In the latter example, the delay is 2 minutes.</p>
     1597      <div id="rfc.figure.u.23"></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>
     1598</pre><p id="rfc.section.9.7.p.5">Two examples of its use are</p>
     1599      <div id="rfc.figure.u.24"></div><pre class="text">  Retry-After: Fri, 31 Dec 1999 23:59:59 GMT
     1600  Retry-After: 120
     1601</pre><p id="rfc.section.9.7.p.7">In the latter example, the delay is 2 minutes.</p>
    15831602      <div id="rfc.iref.s.43"></div>
    15841603      <div id="rfc.iref.h.9"></div>
    1585       <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>
    1586       <p id="rfc.section.10.8.p.1">The Server response-header field contains information about the software used by the origin server to handle the request.
    1587          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.23"><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
     1604      <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>
     1605      <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.
     1606         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.25"><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
    15881607         for identifying the application.
    15891608      </p>
    1590       <div id="rfc.figure.u.26"></div><pre class="inline"><span id="rfc.iref.g.20"></span>  <a href="#header.server" class="smpl">Server</a>         = "Server" ":" 1*( <a href="#abnf.dependencies" class="smpl">product</a> / <a href="#notation" class="smpl">comment</a> )
    1591 </pre><p id="rfc.section.10.8.p.3">Example:</p>
    1592       <div id="rfc.figure.u.27"></div><pre class="text">    Server: CERN/3.0 libwww/2.17
    1593 </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.24"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>).
     1609      <div id="rfc.figure.u.25"></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>
     1610  <a href="#header.server" class="smpl">Server-v</a>       = <a href="#abnf.dependencies" class="smpl">product</a>
     1611                   *( <a href="#core.rules" class="smpl">RWS</a> ( <a href="#abnf.dependencies" class="smpl">product</a> / <a href="#core.rules" class="smpl">comment</a> ) )
     1612</pre><p id="rfc.section.9.8.p.3">Example:</p>
     1613      <div id="rfc.figure.u.26"></div><pre class="text">  Server: CERN/3.0 libwww/2.17
     1614</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.26"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>).
    15941615      </p>
    15951616      <dl class="empty">
     
    16011622      <div id="rfc.iref.u.1"></div>
    16021623      <div id="rfc.iref.h.10"></div>
    1603       <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>
    1604       <p id="rfc.section.10.9.p.1">The User-Agent request-header field contains information about the user agent originating the request. This is for statistical
     1624      <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>
     1625      <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
    16051626         purposes, the tracing of protocol violations, and automated recognition of user agents for the sake of tailoring responses
    1606          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.25"><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
     1627         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.27"><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
    16071628         product tokens are listed in order of their significance for identifying the application.
    16081629      </p>
    1609       <div id="rfc.figure.u.28"></div><pre class="inline"><span id="rfc.iref.g.21"></span>  <a href="#header.user-agent" class="smpl">User-Agent</a>     = "User-Agent" ":" 1*( <a href="#abnf.dependencies" class="smpl">product</a> / <a href="#notation" class="smpl">comment</a> )
    1610 </pre><p id="rfc.section.10.9.p.3">Example:</p>
    1611       <div id="rfc.figure.u.29"></div><pre class="text">    User-Agent: CERN-LineMode/2.15 libwww/2.17b3
    1612 </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>
    1613       <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>
    1614       <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.
    1615       </p>
    1616       <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:
     1630      <div id="rfc.figure.u.27"></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>
     1631  <a href="#header.user-agent" class="smpl">User-Agent-v</a>   = <a href="#abnf.dependencies" class="smpl">product</a>
     1632                   *( <a href="#core.rules" class="smpl">RWS</a> ( <a href="#abnf.dependencies" class="smpl">product</a> / <a href="#core.rules" class="smpl">comment</a> ) )
     1633</pre><p id="rfc.section.9.9.p.3">Example:</p>
     1634      <div id="rfc.figure.u.28"></div><pre class="text">  User-Agent: CERN-LineMode/2.15 libwww/2.17b3
     1635</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>
     1636      <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>
     1637      <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.
     1638      </p>
     1639      <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:
    16171640      </p>
    16181641      <div id="rfc.table.1">
     
    16301653                  <td>CONNECT</td>
    16311654                  <td>no</td>
    1632                   <td> <a href="#CONNECT" id="rfc.xref.CONNECT.2" title="CONNECT">Section&nbsp;8.9</a>
     1655                  <td> <a href="#CONNECT" id="rfc.xref.CONNECT.2" title="CONNECT">Section&nbsp;7.9</a>
    16331656                  </td>
    16341657               </tr>
     
    16361659                  <td>DELETE</td>
    16371660                  <td>no</td>
    1638                   <td> <a href="#DELETE" id="rfc.xref.DELETE.2" title="DELETE">Section&nbsp;8.7</a>
     1661                  <td> <a href="#DELETE" id="rfc.xref.DELETE.2" title="DELETE">Section&nbsp;7.7</a>
    16391662                  </td>
    16401663               </tr>
     
    16421665                  <td>GET</td>
    16431666                  <td>yes</td>
    1644                   <td> <a href="#GET" id="rfc.xref.GET.2" title="GET">Section&nbsp;8.3</a>
     1667                  <td> <a href="#GET" id="rfc.xref.GET.2" title="GET">Section&nbsp;7.3</a>
    16451668                  </td>
    16461669               </tr>
     
    16481671                  <td>HEAD</td>
    16491672                  <td>yes</td>
    1650                   <td> <a href="#HEAD" id="rfc.xref.HEAD.2" title="HEAD">Section&nbsp;8.4</a>
     1673                  <td> <a href="#HEAD" id="rfc.xref.HEAD.2" title="HEAD">Section&nbsp;7.4</a>
    16511674                  </td>
    16521675               </tr>
     
    16541677                  <td>OPTIONS</td>
    16551678                  <td>yes</td>
    1656                   <td> <a href="#OPTIONS" id="rfc.xref.OPTIONS.3" title="OPTIONS">Section&nbsp;8.2</a>
     1679                  <td> <a href="#OPTIONS" id="rfc.xref.OPTIONS.3" title="OPTIONS">Section&nbsp;7.2</a>
    16571680                  </td>
    16581681               </tr>
     
    16601683                  <td>POST</td>
    16611684                  <td>no</td>
    1662                   <td> <a href="#POST" id="rfc.xref.POST.2" title="POST">Section&nbsp;8.5</a>
     1685                  <td> <a href="#POST" id="rfc.xref.POST.2" title="POST">Section&nbsp;7.5</a>
    16631686                  </td>
    16641687               </tr>
     
    16661689                  <td>PUT</td>
    16671690                  <td>no</td>
    1668                   <td> <a href="#PUT" id="rfc.xref.PUT.2" title="PUT">Section&nbsp;8.6</a>
     1691                  <td> <a href="#PUT" id="rfc.xref.PUT.2" title="PUT">Section&nbsp;7.6</a>
    16691692                  </td>
    16701693               </tr>
     
    16721695                  <td>TRACE</td>
    16731696                  <td>yes</td>
    1674                   <td> <a href="#TRACE" id="rfc.xref.TRACE.3" title="TRACE">Section&nbsp;8.8</a>
     1697                  <td> <a href="#TRACE" id="rfc.xref.TRACE.3" title="TRACE">Section&nbsp;7.8</a>
    16751698                  </td>
    16761699               </tr>
     
    16781701         </table>
    16791702      </div>
    1680       <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>
    1681       <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.
    1682       </p>
    1683       <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:
     1703      <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>
     1704      <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.
     1705      </p>
     1706      <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:
    16841707      </p>
    16851708      <div id="rfc.table.2">
     
    16971720                  <td>100</td>
    16981721                  <td>Continue</td>
    1699                   <td> <a href="#status.100" id="rfc.xref.status.100.2" title="100 Continue">Section&nbsp;9.1.1</a>
     1722                  <td> <a href="#status.100" id="rfc.xref.status.100.2" title="100 Continue">Section&nbsp;8.1.1</a>
    17001723                  </td>
    17011724               </tr>
     
    17031726                  <td>101</td>
    17041727                  <td>Switching Protocols</td>
    1705                   <td> <a href="#status.101" id="rfc.xref.status.101.2" title="101 Switching Protocols">Section&nbsp;9.1.2</a>
     1728                  <td> <a href="#status.101" id="rfc.xref.status.101.2" title="101 Switching Protocols">Section&nbsp;8.1.2</a>
    17061729                  </td>
    17071730               </tr>
     
    17091732                  <td>200</td>
    17101733                  <td>OK</td>
    1711                   <td> <a href="#status.200" id="rfc.xref.status.200.2" title="200 OK">Section&nbsp;9.2.1</a>
     1734                  <td> <a href="#status.200" id="rfc.xref.status.200.2" title="200 OK">Section&nbsp;8.2.1</a>
    17121735                  </td>
    17131736               </tr>
     
    17151738                  <td>201</td>
    17161739                  <td>Created</td>
    1717                   <td> <a href="#status.201" id="rfc.xref.status.201.2" title="201 Created">Section&nbsp;9.2.2</a>
     1740                  <td> <a href="#status.201" id="rfc.xref.status.201.2" title="201 Created">Section&nbsp;8.2.2</a>
    17181741                  </td>
    17191742               </tr>
     
    17211744                  <td>202</td>
    17221745                  <td>Accepted</td>
    1723                   <td> <a href="#status.202" id="rfc.xref.status.202.2" title="202 Accepted">Section&nbsp;9.2.3</a>
     1746                  <td> <a href="#status.202" id="rfc.xref.status.202.2" title="202 Accepted">Section&nbsp;8.2.3</a>
    17241747                  </td>
    17251748               </tr>
     
    17271750                  <td>203</td>
    17281751                  <td>Non-Authoritative Information</td>
    1729                   <td> <a href="#status.203" id="rfc.xref.status.203.2" title="203 Non-Authoritative Information">Section&nbsp;9.2.4</a>
     1752                  <td> <a href="#status.203" id="rfc.xref.status.203.2" title="203 Non-Authoritative Information">Section&nbsp;8.2.4</a>
    17301753                  </td>
    17311754               </tr>
     
    17331756                  <td>204</td>
    17341757                  <td>No Content</td>
    1735                   <td> <a href="#status.204" id="rfc.xref.status.204.2" title="204 No Content">Section&nbsp;9.2.5</a>
     1758                  <td> <a href="#status.204" id="rfc.xref.status.204.2" title="204 No Content">Section&nbsp;8.2.5</a>
    17361759                  </td>
    17371760               </tr>
     
    17391762                  <td>205</td>
    17401763                  <td>Reset Content</td>
    1741                   <td> <a href="#status.205" id="rfc.xref.status.205.2" title="205 Reset Content">Section&nbsp;9.2.6</a>
     1764                  <td> <a href="#status.205" id="rfc.xref.status.205.2" title="205 Reset Content">Section&nbsp;8.2.6</a>
    17421765                  </td>
    17431766               </tr>
     
    17451768                  <td>206</td>
    17461769                  <td>Partial Content</td>
    1747                   <td> <a href="#status.206" id="rfc.xref.status.206.2" title="206 Partial Content">Section&nbsp;9.2.7</a>
     1770                  <td> <a href="#status.206" id="rfc.xref.status.206.2" title="206 Partial Content">Section&nbsp;8.2.7</a>
    17481771                  </td>
    17491772               </tr>
     
    17511774                  <td>300</td>
    17521775                  <td>Multiple Choices</td>
    1753                   <td> <a href="#status.300" id="rfc.xref.status.300.2" title="300 Multiple Choices">Section&nbsp;9.3.1</a>
     1776                  <td> <a href="#status.300" id="rfc.xref.status.300.2" title="300 Multiple Choices">Section&nbsp;8.3.1</a>
    17541777                  </td>
    17551778               </tr>
     
    17571780                  <td>301</td>
    17581781                  <td>Moved Permanently</td>
    1759                   <td> <a href="#status.301" id="rfc.xref.status.301.2" title="301 Moved Permanently">Section&nbsp;9.3.2</a>
     1782                  <td> <a href="#status.301" id="rfc.xref.status.301.2" title="301 Moved Permanently">Section&nbsp;8.3.2</a>
    17601783                  </td>
    17611784               </tr>
     
    17631786                  <td>302</td>
    17641787                  <td>Found</td>
    1765                   <td> <a href="#status.302" id="rfc.xref.status.302.2" title="302 Found">Section&nbsp;9.3.3</a>
     1788                  <td> <a href="#status.302" id="rfc.xref.status.302.2" title="302 Found">Section&nbsp;8.3.3</a>
    17661789                  </td>
    17671790               </tr>
     
    17691792                  <td>303</td>
    17701793                  <td>See Other</td>
    1771                   <td> <a href="#status.303" id="rfc.xref.status.303.2" title="303 See Other">Section&nbsp;9.3.4</a>
     1794                  <td> <a href="#status.303" id="rfc.xref.status.303.2" title="303 See Other">Section&nbsp;8.3.4</a>
    17721795                  </td>
    17731796               </tr>
     
    17751798                  <td>304</td>
    17761799                  <td>Not Modified</td>
    1777                   <td> <a href="#status.304" id="rfc.xref.status.304.2" title="304 Not Modified">Section&nbsp;9.3.5</a>
     1800                  <td> <a href="#status.304" id="rfc.xref.status.304.2" title="304 Not Modified">Section&nbsp;8.3.5</a>
    17781801                  </td>
    17791802               </tr>
     
    17811804                  <td>305</td>
    17821805                  <td>Use Proxy</td>
    1783                   <td> <a href="#status.305" id="rfc.xref.status.305.2" title="305 Use Proxy">Section&nbsp;9.3.6</a>
     1806                  <td> <a href="#status.305" id="rfc.xref.status.305.2" title="305 Use Proxy">Section&nbsp;8.3.6</a>
    17841807                  </td>
    17851808               </tr>
     
    17871810                  <td>306</td>
    17881811                  <td>(Unused)</td>
    1789                   <td> <a href="#status.306" id="rfc.xref.status.306.1" title="306 (Unused)">Section&nbsp;9.3.7</a>
     1812                  <td> <a href="#status.306" id="rfc.xref.status.306.1" title="306 (Unused)">Section&nbsp;8.3.7</a>
    17901813                  </td>
    17911814               </tr>
     
    17931816                  <td>307</td>
    17941817                  <td>Temporary Redirect</td>
    1795                   <td> <a href="#status.307" id="rfc.xref.status.307.2" title="307 Temporary Redirect">Section&nbsp;9.3.8</a>
     1818                  <td> <a href="#status.307" id="rfc.xref.status.307.2" title="307 Temporary Redirect">Section&nbsp;8.3.8</a>
    17961819                  </td>
    17971820               </tr>
     
    17991822                  <td>400</td>
    18001823                  <td>Bad Request</td>
    1801                   <td> <a href="#status.400" id="rfc.xref.status.400.2" title="400 Bad Request">Section&nbsp;9.4.1</a>
     1824                  <td> <a href="#status.400" id="rfc.xref.status.400.2" title="400 Bad Request">Section&nbsp;8.4.1</a>
    18021825                  </td>
    18031826               </tr>
     
    18051828                  <td>401</td>
    18061829                  <td>Unauthorized</td>
    1807                   <td> <a href="#status.401" id="rfc.xref.status.401.2" title="401 Unauthorized">Section&nbsp;9.4.2</a>
     1830                  <td> <a href="#status.401" id="rfc.xref.status.401.2" title="401 Unauthorized">Section&nbsp;8.4.2</a>
    18081831                  </td>
    18091832               </tr>
     
    18111834                  <td>402</td>
    18121835                  <td>Payment Required</td>
    1813                   <td> <a href="#status.402" id="rfc.xref.status.402.2" title="402 Payment Required">Section&nbsp;9.4.3</a>
     1836                  <td> <a href="#status.402" id="rfc.xref.status.402.2" title="402 Payment Required">Section&nbsp;8.4.3</a>
    18141837                  </td>
    18151838               </tr>
     
    18171840                  <td>403</td>
    18181841                  <td>Forbidden</td>
    1819                   <td> <a href="#status.403" id="rfc.xref.status.403.2" title="403 Forbidden">Section&nbsp;9.4.4</a>
     1842                  <td> <a href="#status.403" id="rfc.xref.status.403.2" title="403 Forbidden">Section&nbsp;8.4.4</a>
    18201843                  </td>
    18211844               </tr>
     
    18231846                  <td>404</td>
    18241847                  <td>Not Found</td>
    1825                   <td> <a href="#status.404" id="rfc.xref.status.404.2" title="404 Not Found">Section&nbsp;9.4.5</a>
     1848                  <td> <a href="#status.404" id="rfc.xref.status.404.2" title="404 Not Found">Section&nbsp;8.4.5</a>
    18261849                  </td>
    18271850               </tr>
     
    18291852                  <td>405</td>
    18301853                  <td>Method Not Allowed</td>
    1831                   <td> <a href="#status.405" id="rfc.xref.status.405.2" title="405 Method Not Allowed">Section&nbsp;9.4.6</a>
     1854                  <td> <a href="#status.405" id="rfc.xref.status.405.2" title="405 Method Not Allowed">Section&nbsp;8.4.6</a>
    18321855                  </td>
    18331856               </tr>
     
    18351858                  <td>406</td>
    18361859                  <td>Not Acceptable</td>
    1837                   <td> <a href="#status.406" id="rfc.xref.status.406.2" title="406 Not Acceptable">Section&nbsp;9.4.7</a>
     1860                  <td> <a href="#status.406" id="rfc.xref.status.406.2" title="406 Not Acceptable">Section&nbsp;8.4.7</a>
    18381861                  </td>
    18391862               </tr>
     
    18411864                  <td>407</td>
    18421865                  <td>Proxy Authentication Required</td>
    1843                   <td> <a href="#status.407" id="rfc.xref.status.407.2" title="407 Proxy Authentication Required">Section&nbsp;9.4.8</a>
     1866                  <td> <a href="#status.407" id="rfc.xref.status.407.2" title="407 Proxy Authentication Required">Section&nbsp;8.4.8</a>
    18441867                  </td>
    18451868               </tr>
     
    18471870                  <td>408</td>
    18481871                  <td>Request Timeout</td>
    1849                   <td> <a href="#status.408" id="rfc.xref.status.408.2" title="408 Request Timeout">Section&nbsp;9.4.9</a>
     1872                  <td> <a href="#status.408" id="rfc.xref.status.408.2" title="408 Request Timeout">Section&nbsp;8.4.9</a>
    18501873                  </td>
    18511874               </tr>
     
    18531876                  <td>409</td>
    18541877                  <td>Conflict</td>
    1855                   <td> <a href="#status.409" id="rfc.xref.status.409.2" title="409 Conflict">Section&nbsp;9.4.10</a>
     1878                  <td> <a href="#status.409" id="rfc.xref.status.409.2" title="409 Conflict">Section&nbsp;8.4.10</a>
    18561879                  </td>
    18571880               </tr>
     
    18591882                  <td>410</td>
    18601883                  <td>Gone</td>
    1861                   <td> <a href="#status.410" id="rfc.xref.status.410.2" title="410 Gone">Section&nbsp;9.4.11</a>
     1884                  <td> <a href="#status.410" id="rfc.xref.status.410.2" title="410 Gone">Section&nbsp;8.4.11</a>
    18621885                  </td>
    18631886               </tr>
     
    18651888                  <td>411</td>
    18661889                  <td>Length Required</td>
    1867                   <td> <a href="#status.411" id="rfc.xref.status.411.2" title="411 Length Required">Section&nbsp;9.4.12</a>
     1890                  <td> <a href="#status.411" id="rfc.xref.status.411.2" title="411 Length Required">Section&nbsp;8.4.12</a>
    18681891                  </td>
    18691892               </tr>
     
    18711894                  <td>412</td>
    18721895                  <td>Precondition Failed</td>
    1873                   <td> <a href="#status.412" id="rfc.xref.status.412.2" title="412 Precondition Failed">Section&nbsp;9.4.13</a>
     1896                  <td> <a href="#status.412" id="rfc.xref.status.412.2" title="412 Precondition Failed">Section&nbsp;8.4.13</a>
    18741897                  </td>
    18751898               </tr>
     
    18771900                  <td>413</td>
    18781901                  <td>Request Entity Too Large</td>
    1879                   <td> <a href="#status.413" id="rfc.xref.status.413.2" title="413 Request Entity Too Large">Section&nbsp;9.4.14</a>
     1902                  <td> <a href="#status.413" id="rfc.xref.status.413.2" title="413 Request Entity Too Large">Section&nbsp;8.4.14</a>
    18801903                  </td>
    18811904               </tr>
    18821905               <tr>
    18831906                  <td>414</td>
    1884                   <td>Request-URI Too Long</td>
    1885                   <td> <a href="#status.414" id="rfc.xref.status.414.2" title="414 Request-URI Too Long">Section&nbsp;9.4.15</a>
     1907                  <td>Request-target Too Long</td>
     1908                  <td> <a href="#status.414" id="rfc.xref.status.414.2" title="414 Request-target Too Long">Section&nbsp;8.4.15</a>
    18861909                  </td>
    18871910               </tr>
     
    18891912                  <td>415</td>
    18901913                  <td>Unsupported Media Type</td>
    1891                   <td> <a href="#status.415" id="rfc.xref.status.415.2" title="415 Unsupported Media Type">Section&nbsp;9.4.16</a>
     1914                  <td> <a href="#status.415" id="rfc.xref.status.415.2" title="415 Unsupported Media Type">Section&nbsp;8.4.16</a>
    18921915                  </td>
    18931916               </tr>
     
    18951918                  <td>416</td>
    18961919                  <td>Requested Range Not Satisfiable</td>
    1897                   <td> <a href="#status.416" id="rfc.xref.status.416.2" title="416 Requested Range Not Satisfiable">Section&nbsp;9.4.17</a>
     1920                  <td> <a href="#status.416" id="rfc.xref.status.416.2" title="416 Requested Range Not Satisfiable">Section&nbsp;8.4.17</a>
    18981921                  </td>
    18991922               </tr>
     
    19011924                  <td>417</td>
    19021925                  <td>Expectation Failed</td>
    1903                   <td> <a href="#status.417" id="rfc.xref.status.417.2" title="417 Expectation Failed">Section&nbsp;9.4.18</a>
     1926                  <td> <a href="#status.417" id="rfc.xref.status.417.2" title="417 Expectation Failed">Section&nbsp;8.4.18</a>
    19041927                  </td>
    19051928               </tr>
     
    19071930                  <td>500</td>
    19081931                  <td>Internal Server Error</td>
    1909                   <td> <a href="#status.500" id="rfc.xref.status.500.2" title="500 Internal Server Error">Section&nbsp;9.5.1</a>
     1932                  <td> <a href="#status.500" id="rfc.xref.status.500.2" title="500 Internal Server Error">Section&nbsp;8.5.1</a>
    19101933                  </td>
    19111934               </tr>
     
    19131936                  <td>501</td>
    19141937                  <td>Not Implemented</td>
    1915                   <td> <a href="#status.501" id="rfc.xref.status.501.2" title="501 Not Implemented">Section&nbsp;9.5.2</a>
     1938                  <td> <a href="#status.501" id="rfc.xref.status.501.2" title="501 Not Implemented">Section&nbsp;8.5.2</a>
    19161939                  </td>
    19171940               </tr>
     
    19191942                  <td>502</td>
    19201943                  <td>Bad Gateway</td>
    1921                   <td> <a href="#status.502" id="rfc.xref.status.502.2" title="502 Bad Gateway">Section&nbsp;9.5.3</a>
     1944                  <td> <a href="#status.502" id="rfc.xref.status.502.2" title="502 Bad Gateway">Section&nbsp;8.5.3</a>
    19221945                  </td>
    19231946               </tr>
     
    19251948                  <td>503</td>
    19261949                  <td>Service Unavailable</td>
    1927                   <td> <a href="#status.503" id="rfc.xref.status.503.2" title="503 Service Unavailable">Section&nbsp;9.5.4</a>
     1950                  <td> <a href="#status.503" id="rfc.xref.status.503.2" title="503 Service Unavailable">Section&nbsp;8.5.4</a>
    19281951                  </td>
    19291952               </tr>
     
    19311954                  <td>504</td>
    19321955                  <td>Gateway Timeout</td>
    1933                   <td> <a href="#status.504" id="rfc.xref.status.504.2" title="504 Gateway Timeout">Section&nbsp;9.5.5</a>
     1956                  <td> <a href="#status.504" id="rfc.xref.status.504.2" title="504 Gateway Timeout">Section&nbsp;8.5.5</a>
    19341957                  </td>
    19351958               </tr>
     
    19371960                  <td>505</td>
    19381961                  <td>HTTP Version Not Supported</td>
    1939                   <td> <a href="#status.505" id="rfc.xref.status.505.2" title="505 HTTP Version Not Supported">Section&nbsp;9.5.6</a>
     1962                  <td> <a href="#status.505" id="rfc.xref.status.505.2" title="505 HTTP Version Not Supported">Section&nbsp;8.5.6</a>
    19401963                  </td>
    19411964               </tr>
     
    19431966         </table>
    19441967      </div>
    1945       <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>
    1946       <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>):
     1968      <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>
     1969      <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>):
    19471970      </p>
    19481971      <div id="rfc.table.3">
     
    19621985                  <td>http</td>
    19631986                  <td>standard</td>
    1964                   <td> <a href="#header.allow" id="rfc.xref.header.allow.3" title="Allow">Section&nbsp;10.1</a>
     1987                  <td> <a href="#header.allow" id="rfc.xref.header.allow.3" title="Allow">Section&nbsp;9.1</a>
    19651988                  </td>
    19661989               </tr>
     
    19691992                  <td>http</td>
    19701993                  <td>standard</td>
    1971                   <td> <a href="#header.expect" id="rfc.xref.header.expect.3" title="Expect">Section&nbsp;10.2</a>
     1994                  <td> <a href="#header.expect" id="rfc.xref.header.expect.3" title="Expect">Section&nbsp;9.2</a>
    19721995                  </td>
    19731996               </tr>
     
    19761999                  <td>http</td>
    19772000                  <td>standard</td>
    1978                   <td> <a href="#header.from" id="rfc.xref.header.from.2" title="From">Section&nbsp;10.3</a>
     2001                  <td> <a href="#header.from" id="rfc.xref.header.from.2" title="From">Section&nbsp;9.3</a>
    19792002                  </td>
    19802003               </tr>
     
    19832006                  <td>http</td>
    19842007                  <td>standard</td>
    1985                   <td> <a href="#header.location" id="rfc.xref.header.location.3" title="Location">Section&nbsp;10.4</a>
     2008                  <td> <a href="#header.location" id="rfc.xref.header.location.3" title="Location">Section&nbsp;9.4</a>
    19862009                  </td>
    19872010               </tr>
     
    19902013                  <td>http</td>
    19912014                  <td>standard</td>
    1992                   <td> <a href="#header.max-forwards" id="rfc.xref.header.max-forwards.3" title="Max-Forwards">Section&nbsp;10.5</a>
     2015                  <td> <a href="#header.max-forwards" id="rfc.xref.header.max-forwards.3" title="Max-Forwards">Section&nbsp;9.5</a>
    19932016                  </td>
    19942017               </tr>
     
    19972020                  <td>http</td>
    19982021                  <td>standard</td>
    1999                   <td> <a href="#header.referer" id="rfc.xref.header.referer.2" title="Referer">Section&nbsp;10.6</a>
     2022                  <td> <a href="#header.referer" id="rfc.xref.header.referer.2" title="Referer">Section&nbsp;9.6</a>
    20002023                  </td>
    20012024               </tr>
     
    20042027                  <td>http</td>
    20052028                  <td>standard</td>
    2006                   <td> <a href="#header.retry-after" id="rfc.xref.header.retry-after.2" title="Retry-After">Section&nbsp;10.7</a>
     2029                  <td> <a href="#header.retry-after" id="rfc.xref.header.retry-after.2" title="Retry-After">Section&nbsp;9.7</a>
    20072030                  </td>
    20082031               </tr>
     
    20112034                  <td>http</td>
    20122035                  <td>standard</td>
    2013                   <td> <a href="#header.server" id="rfc.xref.header.server.2" title="Server">Section&nbsp;10.8</a>
     2036                  <td> <a href="#header.server" id="rfc.xref.header.server.2" title="Server">Section&nbsp;9.8</a>
    20142037                  </td>
    20152038               </tr>
     
    20182041                  <td>http</td>
    20192042                  <td>standard</td>
    2020                   <td> <a href="#header.user-agent" id="rfc.xref.header.user-agent.2" title="User-Agent">Section&nbsp;10.9</a>
     2043                  <td> <a href="#header.user-agent" id="rfc.xref.header.user-agent.2" title="User-Agent">Section&nbsp;9.9</a>
    20212044                  </td>
    20222045               </tr>
     
    20242047         </table>
    20252048      </div>
    2026       <p id="rfc.section.11.3.p.2">The change controller is: "IETF (iesg@ietf.org) - Internet Engineering Task Force".</p>
    2027       <h1 id="rfc.section.12"><a href="#rfc.section.12">12.</a>&nbsp;<a id="security.considerations" href="#security.considerations">Security Considerations</a></h1>
    2028       <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
     2049      <p id="rfc.section.10.3.p.2">The change controller is: "IETF (iesg@ietf.org) - Internet Engineering Task Force".</p>
     2050      <h1 id="rfc.section.11"><a href="#rfc.section.11">11.</a>&nbsp;<a id="security.considerations" href="#security.considerations">Security Considerations</a></h1>
     2051      <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
    20292052         as described by this document. The discussion does not include definitive solutions to the problems revealed, though it does
    20302053         make some suggestions for reducing security risks.
    20312054      </p>
    2032       <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>
    2033       <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
     2055      <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>
     2056      <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
    20342057         a priori method of determining the sensitivity of any particular piece of information within the context of any given request.
    20352058         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
    20362059         special mention in this context: Server, Via, Referer and From.
    20372060      </p>
    2038       <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
     2061      <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
    20392062         against software that is known to contain security holes. Implementors <em class="bcp14">SHOULD</em> make the Server header field a configurable option.
    20402063      </p>
    2041       <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,
     2064      <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,
    20422065         they <em class="bcp14">SHOULD</em> remove, or replace with sanitized versions, any Via fields generated behind the firewall.
    20432066      </p>
    2044       <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
     2067      <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
    20452068         can be abused if user details are not separated from the information contained in the Referer. Even when the personal information
    20462069         has been removed, the Referer header might indicate a private document's URI whose publication would be inappropriate.
    20472070      </p>
    2048       <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
     2071      <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
    20492072         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.
    20502073      </p>
    2051       <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
     2074      <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
    20522075         of From and Referer information.
    20532076      </p>
    2054       <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
     2077      <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
    20552078         might be exploited. Unfortunately, this same information is often used for other valuable purposes for which HTTP currently
    20562079         has no better mechanism.
    20572080      </p>
    2058       <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>
    2059       <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
     2081      <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>
     2082      <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
    20602083         recommended that the user be able to select whether or not the Referer field is sent. For example, a browser client could
    20612084         have a toggle switch for browsing openly/anonymously, which would respectively enable/disable the sending of Referer and From
    20622085         information.
    20632086      </p>
    2064       <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.
    2065       </p>
    2066       <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
    2067          in the Request-URI. Many existing servers, proxies, and user agents log or display the Request-URI in places where it might
    2068          be visible to third parties. Such services can use POST-based form submission instead.
    2069       </p>
    2070       <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>
    2071       <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
     2087      <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.
     2088      </p>
     2089      <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
     2090         in the Request-target. Many existing servers, proxies, and user agents log or display the Request-target in places where it
     2091         might be visible to third parties. Such services can use POST-based form submission instead.
     2092      </p>
     2093      <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>
     2094      <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
    20722095         to make sure that they do not attempt to invalidate resources over which they have no authority.
    20732096      </p>
    2074       <h1 id="rfc.section.13"><a href="#rfc.section.13">13.</a>&nbsp;<a id="ack" href="#ack">Acknowledgments</a></h1>
    2075       <h1 id="rfc.references"><a id="rfc.section.14" href="#rfc.section.14">14.</a> References
     2097      <h1 id="rfc.section.12"><a href="#rfc.section.12">12.</a>&nbsp;<a id="ack" href="#ack">Acknowledgments</a></h1>
     2098      <h1 id="rfc.references"><a id="rfc.section.13" href="#rfc.section.13">13.</a> References
    20762099      </h1>
    2077       <h2 id="rfc.references.1"><a href="#rfc.section.14.1" id="rfc.section.14.1">14.1</a> Normative References
     2100      <h2 id="rfc.references.1"><a href="#rfc.section.13.1" id="rfc.section.13.1">13.1</a> Normative References
    20782101      </h2>
    2079       <table summary="Normative References">             
     2102      <table summary="Normative References">               
    20802103         <tr>
    20812104            <td class="reference"><b id="Part1">[Part1]</b></td>
    2082             <td class="top"><a title="Day Software">Fielding, R., Ed.</a>, <a title="One Laptop per Child">Gettys, J.</a>, <a title="Hewlett-Packard Company">Mogul, J.</a>, <a title="Microsoft Corporation">Frystyk, H.</a>, <a title="Adobe Systems, Incorporated">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, <a title="World Wide Web Consortium">Berners-Lee, T.</a>, <a title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a title="greenbytes GmbH">J. F. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p1-messaging-latest">HTTP/1.1, part 1: URIs, Connections, and Message Parsing</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p1-messaging-latest (work in progress), November&nbsp;2008.
     2105            <td class="top"><a title="Day Software">Fielding, R., Ed.</a>, <a title="One Laptop per Child">Gettys, J.</a>, <a title="Hewlett-Packard Company">Mogul, J.</a>, <a title="Microsoft Corporation">Frystyk, H.</a>, <a title="Adobe Systems, Incorporated">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, <a title="World Wide Web Consortium">Berners-Lee, T.</a>, <a title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a title="greenbytes GmbH">J. F. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p1-messaging-latest">HTTP/1.1, part 1: URIs, Connections, and Message Parsing</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p1-messaging-latest (work in progress), December&nbsp;2008.
    20832106            </td>
    20842107         </tr>
    20852108         <tr>
    20862109            <td class="reference"><b id="Part3">[Part3]</b></td>
    2087             <td class="top"><a title="Day Software">Fielding, R., Ed.</a>, <a title="One Laptop per Child">Gettys, J.</a>, <a title="Hewlett-Packard Company">Mogul, J.</a>, <a title="Microsoft Corporation">Frystyk, H.</a>, <a title="Adobe Systems, Incorporated">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, <a title="World Wide Web Consortium">Berners-Lee, T.</a>, <a title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a title="greenbytes GmbH">J. F. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p3-payload-latest">HTTP/1.1, part 3: Message Payload and Content Negotiation</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p3-payload-latest (work in progress), November&nbsp;2008.
     2110            <td class="top"><a title="Day Software">Fielding, R., Ed.</a>, <a title="One Laptop per Child">Gettys, J.</a>, <a title="Hewlett-Packard Company">Mogul, J.</a>, <a title="Microsoft Corporation">Frystyk, H.</a>, <a title="Adobe Systems, Incorporated">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, <a title="World Wide Web Consortium">Berners-Lee, T.</a>, <a title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a title="greenbytes GmbH">J. F. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p3-payload-latest">HTTP/1.1, part 3: Message Payload and Content Negotiation</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p3-payload-latest (work in progress), December&nbsp;2008.
    20882111            </td>
    20892112         </tr>
    20902113         <tr>
    20912114            <td class="reference"><b id="Part4">[Part4]</b></td>
    2092             <td class="top"><a title="Day Software">Fielding, R., Ed.</a>, <a title="One Laptop per Child">Gettys, J.</a>, <a title="Hewlett-Packard Company">Mogul, J.</a>, <a title="Microsoft Corporation">Frystyk, H.</a>, <a title="Adobe Systems, Incorporated">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, <a title="World Wide Web Consortium">Berners-Lee, T.</a>, <a title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a title="greenbytes GmbH">J. F. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p4-conditional-latest">HTTP/1.1, part 4: Conditional Requests</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p4-conditional-latest (work in progress), November&nbsp;2008.
     2115            <td class="top"><a title="Day Software">Fielding, R., Ed.</a>, <a title="One Laptop per Child">Gettys, J.</a>, <a title="Hewlett-Packard Company">Mogul, J.</a>, <a title="Microsoft Corporation">Frystyk, H.</a>, <a title="Adobe Systems, Incorporated">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, <a title="World Wide Web Consortium">Berners-Lee, T.</a>, <a title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a title="greenbytes GmbH">J. F. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p4-conditional-latest">HTTP/1.1, part 4: Conditional Requests</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p4-conditional-latest (work in progress), December&nbsp;2008.
    20932116            </td>
    20942117         </tr>
    20952118         <tr>
    20962119            <td class="reference"><b id="Part5">[Part5]</b></td>
    2097             <td class="top"><a title="Day Software">Fielding, R., Ed.</a>, <a title="One Laptop per Child">Gettys, J.</a>, <a title="Hewlett-Packard Company">Mogul, J.</a>, <a title="Microsoft Corporation">Frystyk, H.</a>, <a title="Adobe Systems, Incorporated">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, <a title="World Wide Web Consortium">Berners-Lee, T.</a>, <a title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a title="greenbytes GmbH">J. F. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p5-range-latest">HTTP/1.1, part 5: Range Requests and Partial Responses</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p5-range-latest (work in progress), November&nbsp;2008.
     2120            <td class="top"><a title="Day Software">Fielding, R., Ed.</a>, <a title="One Laptop per Child">Gettys, J.</a>, <a title="Hewlett-Packard Company">Mogul, J.</a>, <a title="Microsoft Corporation">Frystyk, H.</a>, <a title="Adobe Systems, Incorporated">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, <a title="World Wide Web Consortium">Berners-Lee, T.</a>, <a title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a title="greenbytes GmbH">J. F. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p5-range-latest">HTTP/1.1, part 5: Range Requests and Partial Responses</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p5-range-latest (work in progress), December&nbsp;2008.
    20982121            </td>
    20992122         </tr>
    21002123         <tr>
    21012124            <td class="reference"><b id="Part6">[Part6]</b></td>
    2102             <td class="top"><a title="Day Software">Fielding, R., Ed.</a>, <a title="One Laptop per Child">Gettys, J.</a>, <a title="Hewlett-Packard Company">Mogul, J.</a>, <a title="Microsoft Corporation">Frystyk, H.</a>, <a title="Adobe Systems, Incorporated">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, <a title="World Wide Web Consortium">Berners-Lee, T.</a>, <a title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a title="greenbytes GmbH">J. F. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p6-cache-latest">HTTP/1.1, part 6: Caching</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p6-cache-latest (work in progress), November&nbsp;2008.
     2125            <td class="top"><a title="Day Software">Fielding, R., Ed.</a>, <a title="One Laptop per Child">Gettys, J.</a>, <a title="Hewlett-Packard Company">Mogul, J.</a>, <a title="Microsoft Corporation">Frystyk, H.</a>, <a title="Adobe Systems, Incorporated">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, <a title="World Wide Web Consortium">Berners-Lee, T.</a>, <a title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a title="greenbytes GmbH">J. F. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p6-cache-latest">HTTP/1.1, part 6: Caching</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p6-cache-latest (work in progress), December&nbsp;2008.
    21032126            </td>
    21042127         </tr>
    21052128         <tr>
    21062129            <td class="reference"><b id="Part7">[Part7]</b></td>
    2107             <td class="top"><a title="Day Software">Fielding, R., Ed.</a>, <a title="One Laptop per Child">Gettys, J.</a>, <a title="Hewlett-Packard Company">Mogul, J.</a>, <a title="Microsoft Corporation">Frystyk, H.</a>, <a title="Adobe Systems, Incorporated">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, <a title="World Wide Web Consortium">Berners-Lee, T.</a>, <a title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a title="greenbytes GmbH">J. F. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p7-auth-latest">HTTP/1.1, part 7: Authentication</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p7-auth-latest (work in progress), November&nbsp;2008.
     2130            <td class="top"><a title="Day Software">Fielding, R., Ed.</a>, <a title="One Laptop per Child">Gettys, J.</a>, <a title="Hewlett-Packard Company">Mogul, J.</a>, <a title="Microsoft Corporation">Frystyk, H.</a>, <a title="Adobe Systems, Incorporated">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, <a title="World Wide Web Consortium">Berners-Lee, T.</a>, <a title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a title="greenbytes GmbH">J. F. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p7-auth-latest">HTTP/1.1, part 7: Authentication</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p7-auth-latest (work in progress), December&nbsp;2008.
    21082131            </td>
    21092132         </tr>
     
    21132136            </td>
    21142137         </tr>
     2138         <tr>
     2139            <td class="reference"><b id="RFC5234">[RFC5234]</b></td>
     2140            <td class="top"><a title="Brandenburg InternetWorking">Crocker, D., Ed.</a> and <a title="THUS plc.">P. Overell</a>, “<a href="http://tools.ietf.org/html/rfc5234">Augmented BNF for Syntax Specifications: ABNF</a>”, STD&nbsp;68, RFC&nbsp;5234, January&nbsp;2008.
     2141            </td>
     2142         </tr>
    21152143      </table>
    2116       <h2 id="rfc.references.2"><a href="#rfc.section.14.2" id="rfc.section.14.2">14.2</a> Informative References
     2144      <h2 id="rfc.references.2"><a href="#rfc.section.13.2" id="rfc.section.13.2">13.2</a> Informative References
    21172145      </h2>
    21182146      <table summary="Informative References">             
     
    21712199      <h1 id="rfc.section.A"><a href="#rfc.section.A">A.</a>&nbsp;<a id="compatibility" href="#compatibility">Compatibility with Previous Versions</a></h1>
    21722200      <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>
    2173       <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>).
    2174       </p>
    2175       <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>).
     2201      <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>).
     2202      </p>
     2203      <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>).
    21762204      </p>
    21772205      <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
     
    21932221      </ol>
    21942222      <p id="rfc.section.A.1.p.4">This change adds the Expect header and 417 status code.</p>
    2195       <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>)
     2223      <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>)
    21962224      </p>
    21972225      <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>.
    21982226      </p>
    21992227      <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>
    2200       <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>)
    2201       </p>
    2202       <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>)
     2228      <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>)
     2229      </p>
     2230      <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>)
    22032231      </p>
    22042232      <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
    2205          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>)
     2233         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>)
    22062234      </p>
    22072235      <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
    22082236         must be accessed through the proxy given by the Location field. The Location field gave the URI of the proxy. The recipient
    2209          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>)
     2237         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>)
    22102238      </p>
    22112239      <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
    2212          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>)
     2240         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>)
    22132241      </p>
    22142242      <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
    2215          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>)
     2243         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>)
    22162244      </p>
    22172245      <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
    2218          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.26"><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>)
    2219       </p>
    2220       <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a>&nbsp;<a id="change.log" href="#change.log">Change Log (to be removed by RFC Editor before publication)</a></h1>
    2221       <h2 id="rfc.section.B.1"><a href="#rfc.section.B.1">B.1</a>&nbsp;Since RFC2616
     2246         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.28"><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>)
     2247      </p>
     2248      <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a>&nbsp;<a id="collected.abnf" href="#collected.abnf">Collected ABNF</a></h1>
     2249      <div id="rfc.figure.u.29"></div> <pre class="inline"><a href="#abnf.dependencies" class="smpl">Accept</a> = &lt;Accept, defined in [Part3], Section 5.1&gt;
     2250<a href="#abnf.dependencies" class="smpl">Accept-Charset</a> = &lt;Accept-Charset, defined in [Part3], Section 5.2&gt;
     2251<a href="#abnf.dependencies" class="smpl">Accept-Encoding</a> = &lt;Accept-Encoding, defined in [Part3], Section 5.3&gt;
     2252<a href="#abnf.dependencies" class="smpl">Accept-Language</a> = &lt;Accept-Language, defined in [Part3], Section 5.4&gt;
     2253<a href="#abnf.dependencies" class="smpl">Accept-Ranges</a> = &lt;Accept-Ranges, defined in [Part5], Section 5.1&gt;
     2254<a href="#abnf.dependencies" class="smpl">Age</a> = &lt;Age, defined in [Part6], Section 15.1&gt;
     2255<a href="#header.allow" class="smpl">Allow</a> = "Allow:" OWS Allow-v
     2256<a href="#header.allow" class="smpl">Allow-v</a> = [ ( "," / Method ) *( OWS "," [ OWS Method ] ) ]
     2257<a href="#abnf.dependencies" class="smpl">Authorization</a> = &lt;Authorization, defined in [Part7], Section 3.1&gt;
     2258
     2259<a href="#abnf.dependencies" class="smpl">ETag</a> = &lt;ETag, defined in [Part4], Section 6.1&gt;
     2260<a href="#header.expect" class="smpl">Expect</a> = "Expect:" OWS Expect-v
     2261<a href="#header.expect" class="smpl">Expect-v</a> = *( "," OWS ) expectation *( OWS "," [ OWS expectation ] )
     2262
     2263<a href="#header.from" class="smpl">From</a> = "From:" OWS From-v
     2264<a href="#header.from" class="smpl">From-v</a> = mailbox
     2265
     2266<a href="#abnf.dependencies" class="smpl">HTTP-date</a> = &lt;HTTP-date, defined in [Part1], Section 3.2.1&gt;
     2267<a href="#abnf.dependencies" class="smpl">Host</a> = &lt;Host, defined in [Part1], Section 2.1&gt;
     2268
     2269<a href="#abnf.dependencies" class="smpl">If-Match</a> = &lt;If-Match, defined in [Part4], Section 6.2&gt;
     2270<a href="#abnf.dependencies" class="smpl">If-Modified-Since</a> = &lt;If-Modified-Since, defined in [Part4], Section
     2271 6.3&gt;
     2272<a href="#abnf.dependencies" class="smpl">If-None-Match</a> = &lt;If-None-Match, defined in [Part4], Section 6.4&gt;
     2273<a href="#abnf.dependencies" class="smpl">If-Range</a> = &lt;If-Range, defined in [Part5], Section 5.3&gt;
     2274<a href="#abnf.dependencies" class="smpl">If-Unmodified-Since</a> = &lt;If-Unmodified-Since, defined in [Part4],
     2275 Section 6.5&gt;
     2276
     2277<a href="#header.location" class="smpl">Location</a> = "Location:" OWS Location-v
     2278<a href="#header.location" class="smpl">Location-v</a> = absolute-URI [ "#" fragment ]
     2279
     2280<a href="#header.max-forwards" class="smpl">Max-Forwards</a> = "Max-Forwards:" OWS Max-Forwards-v
     2281<a href="#header.max-forwards" class="smpl">Max-Forwards-v</a> = 1*DIGIT
     2282<a href="#method" class="smpl">Method</a> = %x4F.50.54.49.4F.4E.53 / %x47.45.54 / %x48.45.41.44 /
     2283 %x50.4F.53.54 / %x50.55.54 / %x44.45.4C.45.54.45 / %x54.52.41.43.45
     2284 / %x43.4F.4E.4E.45.43.54 / extension-method
     2285
     2286<a href="#core.rules" class="smpl">OWS</a> = &lt;OWS, defined in [Part1], Section 1.2.2&gt;
     2287
     2288<a href="#abnf.dependencies" class="smpl">Proxy-Authenticate</a> = &lt;Proxy-Authenticate, defined in [Part7], Section
     2289 3.2&gt;
     2290<a href="#abnf.dependencies" class="smpl">Proxy-Authorization</a> = &lt;Proxy-Authorization, defined in [Part7],
     2291 Section 3.3&gt;
     2292
     2293<a href="#core.rules" class="smpl">RWS</a> = &lt;RWS, defined in [Part1], Section 1.2.2&gt;
     2294<a href="#abnf.dependencies" class="smpl">Range</a> = &lt;Range, defined in [Part5], Section 5.4&gt;
     2295<a href="#status.code.and.reason.phrase" class="smpl">Reason-Phrase</a> = *( WSP / VCHAR / obs-text )
     2296<a href="#header.referer" class="smpl">Referer</a> = "Referer:" OWS Referer-v
     2297<a href="#header.referer" class="smpl">Referer-v</a> = absolute-URI / partial-URI
     2298<a href="#header.retry-after" class="smpl">Retry-After</a> = "Retry-After:" OWS Retry-After-v
     2299<a href="#header.retry-after" class="smpl">Retry-After-v</a> = HTTP-date / delta-seconds
     2300
     2301<a href="#header.server" class="smpl">Server</a> = "Server:" OWS Server-v
     2302<a href="#header.server" class="smpl">Server-v</a> = product *( RWS ( product / comment ) )
     2303<a href="#status.code.and.reason.phrase" class="smpl">Status-Code</a> = "100" / "101" / "200" / "201" / "202" / "203" / "204" /
     2304 "205" / "206" / "300" / "301" / "302" / "303" / "304" / "305" /
     2305 "307" / "400" / "401" / "402" / "403" / "404" / "405" / "406" /
     2306 "407" / "408" / "409" / "410" / "411" / "412" / "413" / "414" /
     2307 "415" / "416" / "417" / "500" / "501" / "502" / "503" / "504" /
     2308 "505" / extension-code
     2309
     2310<a href="#abnf.dependencies" class="smpl">TE</a> = &lt;TE, defined in [Part1], Section 8.8&gt;
     2311
     2312<a href="#header.user-agent" class="smpl">User-Agent</a> = "User-Agent:" OWS User-Agent-v
     2313<a href="#header.user-agent" class="smpl">User-Agent-v</a> = product *( RWS ( product / comment ) )
     2314
     2315<a href="#abnf.dependencies" class="smpl">Vary</a> = &lt;Vary, defined in [Part6], Section 15.5&gt;
     2316
     2317<a href="#abnf.dependencies" class="smpl">WWW-Authenticate</a> = &lt;WWW-Authenticate, defined in [Part7], Section
     2318 3.4&gt;
     2319
     2320<a href="#abnf.dependencies" class="smpl">absolute-URI</a> = &lt;absolute-URI, defined in [Part1], Section 2.1&gt;
     2321
     2322<a href="#core.rules" class="smpl">comment</a> = &lt;comment, defined in [Part1], Section 1.2.2&gt;
     2323
     2324<a href="#rule.delta-seconds" class="smpl">delta-seconds</a> = 1*DIGIT
     2325
     2326<a href="#header.expect" class="smpl">expect-params</a> = ";" token [ "=" ( token / quoted-string ) ]
     2327<a href="#header.expect" class="smpl">expectation</a> = "100-continue" / expectation-extension
     2328<a href="#header.expect" class="smpl">expectation-extension</a> = token [ "=" ( token / quoted-string )
     2329 *expect-params ]
     2330<a href="#status.code.and.reason.phrase" class="smpl">extension-code</a> = 3DIGIT
     2331<a href="#method" class="smpl">extension-method</a> = token
     2332
     2333<a href="#abnf.dependencies" class="smpl">fragment</a> = &lt;fragment, defined in [Part1], Section 2.1&gt;
     2334
     2335<a href="#header.from" class="smpl">mailbox</a> = &lt;mailbox, defined in [RFC5322], Section 3.4&gt;
     2336
     2337<a href="#core.rules" class="smpl">obs-text</a> = &lt;obs-text, defined in [Part1], Section 1.2.2&gt;
     2338
     2339<a href="#abnf.dependencies" class="smpl">partial-URI</a> = &lt;partial-URI, defined in [Part1], Section 2.1&gt;
     2340<a href="#abnf.dependencies" class="smpl">product</a> = &lt;product, defined in [Part1], Section 3.4&gt;
     2341
     2342<a href="#core.rules" class="smpl">quoted-string</a> = &lt;quoted-string, defined in [Part1], Section 1.2.2&gt;
     2343
     2344<a href="#request.header.fields" class="smpl">request-header</a> = Accept / Accept-Charset / Accept-Encoding /
     2345 Accept-Language / Authorization / Expect / From / Host / If-Match /
     2346 If-Modified-Since / If-None-Match / If-Range / If-Unmodified-Since /
     2347 Max-Forwards / Proxy-Authorization / Range / Referer / TE /
     2348 User-Agent
     2349<a href="#response.header.fields" class="smpl">response-header</a> = Accept-Ranges / Age / Allow / ETag / Location /
     2350 Proxy-Authenticate / Retry-After / Server / Vary / WWW-Authenticate
     2351
     2352<a href="#core.rules" class="smpl">token</a> = &lt;token, defined in [Part1], Section 1.2.2&gt;
     2353
     2354; Reason-Phrase defined but not used
     2355; Status-Code defined but not used
     2356; request-header defined but not used
     2357; response-header defined but not used
     2358
     2359
     2360</pre> <h1 id="rfc.section.C"><a href="#rfc.section.C">C.</a>&nbsp;<a id="change.log" href="#change.log">Change Log (to be removed by RFC Editor before publication)</a></h1>
     2361      <h2 id="rfc.section.C.1"><a href="#rfc.section.C.1">C.1</a>&nbsp;Since RFC2616
    22222362      </h2>
    2223       <p id="rfc.section.B.1.p.1">Extracted relevant partitions from <a href="#RFC2616" id="rfc.xref.RFC2616.2"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>.
    2224       </p>
    2225       <h2 id="rfc.section.B.2"><a href="#rfc.section.B.2">B.2</a>&nbsp;Since draft-ietf-httpbis-p2-semantics-00
     2363      <p id="rfc.section.C.1.p.1">Extracted relevant partitions from <a href="#RFC2616" id="rfc.xref.RFC2616.2"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>.
     2364      </p>
     2365      <h2 id="rfc.section.C.2"><a href="#rfc.section.C.2">C.2</a>&nbsp;Since draft-ietf-httpbis-p2-semantics-00
    22262366      </h2>
    2227       <p id="rfc.section.B.2.p.1">Closed issues: </p>
     2367      <p id="rfc.section.C.2.p.1">Closed issues: </p>
    22282368      <ul>
    22292369         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/5">http://tools.ietf.org/wg/httpbis/trac/ticket/5</a>&gt;: "Via is a MUST" (&lt;<a href="http://purl.org/NET/http-errata#via-must">http://purl.org/NET/http-errata#via-must</a>&gt;)
     
    22442384         </li>
    22452385      </ul>
    2246       <p id="rfc.section.B.2.p.2">Other changes: </p>
     2386      <p id="rfc.section.C.2.p.2">Other changes: </p>
    22472387      <ul>
    22482388         <li>Move definitions of 304 and 412 condition codes to <a href="#Part4" id="rfc.xref.Part4.14"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>
    22492389         </li>
    22502390      </ul>
    2251       <h2 id="rfc.section.B.3"><a href="#rfc.section.B.3">B.3</a>&nbsp;Since draft-ietf-httpbis-p2-semantics-01
     2391      <h2 id="rfc.section.C.3"><a href="#rfc.section.C.3">C.3</a>&nbsp;Since draft-ietf-httpbis-p2-semantics-01
    22522392      </h2>
    2253       <p id="rfc.section.B.3.p.1">Closed issues: </p>
     2393      <p id="rfc.section.C.3.p.1">Closed issues: </p>
    22542394      <ul>
    22552395         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/21">http://tools.ietf.org/wg/httpbis/trac/ticket/21</a>&gt;: "PUT side effects"
     
    22582398         </li>
    22592399      </ul>
    2260       <p id="rfc.section.B.3.p.2">Ongoing work on ABNF conversion (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>&gt;):
     2400      <p id="rfc.section.C.3.p.2">Ongoing work on ABNF conversion (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>&gt;):
    22612401      </p>
    22622402      <ul>
     
    22652405         <li>Copy definition of delta-seconds from Part6 instead of referencing it.</li>
    22662406      </ul>
    2267       <h2 id="rfc.section.B.4"><a href="#rfc.section.B.4">B.4</a>&nbsp;<a id="changes.since.02" href="#changes.since.02">Since draft-ietf-httpbis-p2-semantics-02</a></h2>
    2268       <p id="rfc.section.B.4.p.1">Closed issues: </p>
     2407      <h2 id="rfc.section.C.4"><a href="#rfc.section.C.4">C.4</a>&nbsp;<a id="changes.since.02" href="#changes.since.02">Since draft-ietf-httpbis-p2-semantics-02</a></h2>
     2408      <p id="rfc.section.C.4.p.1">Closed issues: </p>
    22692409      <ul>
    22702410         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/24">http://tools.ietf.org/wg/httpbis/trac/ticket/24</a>&gt;: "Requiring Allow in 405 responses"
     
    22832423         </li>
    22842424      </ul>
    2285       <p id="rfc.section.B.4.p.2">Ongoing work on IANA Message Header Registration (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/40">http://tools.ietf.org/wg/httpbis/trac/ticket/40</a>&gt;):
     2425      <p id="rfc.section.C.4.p.2">Ongoing work on IANA Message Header Registration (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/40">http://tools.ietf.org/wg/httpbis/trac/ticket/40</a>&gt;):
    22862426      </p>
    22872427      <ul>
    22882428         <li>Reference RFC 3984, and update header registrations for headers defined in this document.</li>
    22892429      </ul>
    2290       <p id="rfc.section.B.4.p.3">Ongoing work on ABNF conversion (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>&gt;):
     2430      <p id="rfc.section.C.4.p.3">Ongoing work on ABNF conversion (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>&gt;):
    22912431      </p>
    22922432      <ul>
    22932433         <li>Replace string literals when the string really is case-sensitive (method).</li>
    22942434      </ul>
    2295       <h2 id="rfc.section.B.5"><a href="#rfc.section.B.5">B.5</a>&nbsp;<a id="changes.since.03" href="#changes.since.03">Since draft-ietf-httpbis-p2-semantics-03</a></h2>
    2296       <p id="rfc.section.B.5.p.1">Closed issues: </p>
     2435      <h2 id="rfc.section.C.5"><a href="#rfc.section.C.5">C.5</a>&nbsp;<a id="changes.since.03" href="#changes.since.03">Since draft-ietf-httpbis-p2-semantics-03</a></h2>
     2436      <p id="rfc.section.C.5.p.1">Closed issues: </p>
    22972437      <ul>
    22982438         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/98">http://tools.ietf.org/wg/httpbis/trac/ticket/98</a>&gt;: "OPTIONS request bodies"
     
    23032443         </li>
    23042444      </ul>
    2305       <p id="rfc.section.B.5.p.2">Ongoing work on Method Registry (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/72">http://tools.ietf.org/wg/httpbis/trac/ticket/72</a>&gt;):
     2445      <p id="rfc.section.C.5.p.2">Ongoing work on Method Registry (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/72">http://tools.ietf.org/wg/httpbis/trac/ticket/72</a>&gt;):
    23062446      </p>
    23072447      <ul>
    23082448         <li>Added initial proposal for registration process, plus initial content (non-HTTP/1.1 methods to be added by a separate specification).</li>
    23092449      </ul>
    2310       <h2 id="rfc.section.B.6"><a href="#rfc.section.B.6">B.6</a>&nbsp;<a id="changes.since.04" href="#changes.since.04">Since draft-ietf-httpbis-p2-semantics-04</a></h2>
    2311       <p id="rfc.section.B.6.p.1">Closed issues: </p>
     2450      <h2 id="rfc.section.C.6"><a href="#rfc.section.C.6">C.6</a>&nbsp;<a id="changes.since.04" href="#changes.since.04">Since draft-ietf-httpbis-p2-semantics-04</a></h2>
     2451      <p id="rfc.section.C.6.p.1">Closed issues: </p>
    23122452      <ul>
    23132453         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/103">http://tools.ietf.org/wg/httpbis/trac/ticket/103</a>&gt;: "Content-*"
     
    23162456         </li>
    23172457      </ul>
    2318       <p id="rfc.section.B.6.p.2">Ongoing work on ABNF conversion (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>&gt;):
     2458      <p id="rfc.section.C.6.p.2">Ongoing work on ABNF conversion (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>&gt;):
    23192459      </p>
    23202460      <ul>
    23212461         <li>Use "/" instead of "|" for alternatives.</li>
     2462         <li>Introduce new ABNF rules for "bad" whitespace ("BWS"), optional whitespace ("OWS") and required whitespace ("RWS").</li>
     2463         <li>Rewrite ABNFs to spell out whitespace rules, factor out header value format definitions.</li>
     2464      </ul>
     2465      <h2 id="rfc.section.C.7"><a href="#rfc.section.C.7">C.7</a>&nbsp;<a id="changes.since.05" href="#changes.since.05">Since draft-ietf-httpbis-p2-semantics-05</a></h2>
     2466      <p id="rfc.section.C.7.p.1">Closed issues: </p>
     2467      <ul>
     2468         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/94">http://tools.ietf.org/wg/httpbis/trac/ticket/94</a>&gt;: "Reason-Phrase BNF"
     2469         </li>
     2470      </ul>
     2471      <p id="rfc.section.C.7.p.2">Ongoing work on ABNF conversion (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>&gt;):
     2472      </p>
     2473      <ul>
     2474         <li>Add appendix containing collected and expanded ABNF, reorganize ABNF introduction.</li>
    23222475      </ul>
    23232476      <h1><a id="rfc.copyright" href="#rfc.copyright">Full Copyright Statement</a></h1>
     
    23512504         <ul class="ind">
    23522505            <li class="indline0"><a id="rfc.index.1" href="#rfc.index.1"><b>1</b></a><ul class="ind">
    2353                   <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>
    2354                   <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>
     2506                  <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>
     2507                  <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>
    23552508               </ul>
    23562509            </li>
    23572510            <li class="indline0"><a id="rfc.index.2" href="#rfc.index.2"><b>2</b></a><ul class="ind">
    2358                   <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>
    2359                   <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>
    2360                   <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>
    2361                   <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>
    2362                   <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>
    2363                   <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>
    2364                   <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>
     2511                  <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>
     2512                  <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>
     2513                  <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>
     2514                  <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>
     2515                  <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>
     2516                  <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>
     2517                  <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>
    23652518               </ul>
    23662519            </li>
    23672520            <li class="indline0"><a id="rfc.index.3" href="#rfc.index.3"><b>3</b></a><ul class="ind">
    2368                   <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>
    2369                   <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>
    2370                   <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>
    2371                   <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>
    2372                   <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>
    2373                   <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>
    2374                   <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>
    2375                   <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>
     2521                  <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>
     2522                  <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>
     2523                  <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>
     2524                  <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>
     2525                  <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>
     2526                  <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>
     2527                  <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>
     2528                  <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>
    23762529               </ul>
    23772530            </li>
    23782531            <li class="indline0"><a id="rfc.index.4" href="#rfc.index.4"><b>4</b></a><ul class="ind">
    2379                   <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>
    2380                   <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>
    2381                   <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>
    2382                   <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>
    2383                   <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>
    2384                   <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>
    2385                   <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>
    2386                   <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>
    2387                   <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>
    2388                   <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>
    2389                   <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>
    2390                   <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>
    2391                   <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>
    2392                   <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>
    2393                   <li class="indline1">414 Request-URI 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>
    2394                   <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>
    2395                   <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>
    2396                   <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>
     2532                  <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>
     2533                  <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>
     2534                  <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>
     2535                  <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>
     2536                  <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>
     2537                  <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>
     2538                  <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>
     2539                  <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>
     2540                  <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>
     2541                  <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>
     2542                  <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>
     2543                  <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>
     2544                  <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>
     2545                  <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>
     2546                  <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>
     2547                  <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>
     2548                  <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>
     2549                  <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>
    23972550               </ul>
    23982551            </li>
    23992552            <li class="indline0"><a id="rfc.index.5" href="#rfc.index.5"><b>5</b></a><ul class="ind">
    2400                   <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>
    2401                   <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>
    2402                   <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>
    2403                   <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>
    2404                   <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>
    2405                   <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>
     2553                  <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>
     2554                  <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>
     2555                  <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>
     2556                  <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>
     2557                  <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>
     2558                  <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>
    24062559               </ul>
    24072560            </li>
    24082561            <li class="indline0"><a id="rfc.index.A" href="#rfc.index.A"><b>A</b></a><ul class="ind">
    2409                   <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>
     2562                  <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>
    24102563               </ul>
    24112564            </li>
    24122565            <li class="indline0"><a id="rfc.index.C" href="#rfc.index.C"><b>C</b></a><ul class="ind">
    2413                   <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>
     2566                  <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>
    24142567               </ul>
    24152568            </li>
    24162569            <li class="indline0"><a id="rfc.index.D" href="#rfc.index.D"><b>D</b></a><ul class="ind">
    2417                   <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>
     2570                  <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>
    24182571               </ul>
    24192572            </li>
    24202573            <li class="indline0"><a id="rfc.index.E" href="#rfc.index.E"><b>E</b></a><ul class="ind">
    2421                   <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>
     2574                  <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>
    24222575               </ul>
    24232576            </li>
    24242577            <li class="indline0"><a id="rfc.index.F" href="#rfc.index.F"><b>F</b></a><ul class="ind">
    2425                   <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>
     2578                  <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>
    24262579               </ul>
    24272580            </li>
    24282581            <li class="indline0"><a id="rfc.index.G" href="#rfc.index.G"><b>G</b></a><ul class="ind">
    2429                   <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>
     2582                  <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>
    24302583                  <li class="indline1"><tt>Grammar</tt>&nbsp;&nbsp;
    24312584                     <ul class="ind">
    2432                         <li class="indline1"><tt>Allow</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.9"><b>10.1</b></a></li>
    2433                         <li class="indline1"><tt>delta-seconds</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.19"><b>10.7</b></a></li>
    2434                         <li class="indline1"><tt>Expect</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.10"><b>10.2</b></a></li>
    2435                         <li class="indline1"><tt>expect-params</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.13"><b>10.2</b></a></li>
    2436                         <li class="indline1"><tt>expectation</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.11"><b>10.2</b></a></li>
    2437                         <li class="indline1"><tt>expectation-extension</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.12"><b>10.2</b></a></li>
    2438                         <li class="indline1"><tt>extension-code</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.5"><b>5</b></a></li>
    2439                         <li class="indline1"><tt>extension-method</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.2"><b>3</b></a></li>
    2440                         <li class="indline1"><tt>From</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.14"><b>10.3</b></a></li>
    2441                         <li class="indline1"><tt>Location</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.15"><b>10.4</b></a></li>
    2442                         <li class="indline1"><tt>Max-Forwards</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.16"><b>10.5</b></a></li>
    2443                         <li class="indline1"><tt>Method</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.1"><b>3</b></a></li>
    2444                         <li class="indline1"><tt>Reason-Phrase</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.6"><b>5</b></a></li>
    2445                         <li class="indline1"><tt>Referer</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.17"><b>10.6</b></a></li>
    2446                         <li class="indline1"><tt>request-header</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.3"><b>4</b></a></li>
    2447                         <li class="indline1"><tt>response-header</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.7"><b>6</b></a></li>
    2448                         <li class="indline1"><tt>Retry-After</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.18"><b>10.7</b></a></li>
    2449                         <li class="indline1"><tt>Server</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.20"><b>10.8</b></a></li>
    2450                         <li class="indline1"><tt>Status-Code</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.4"><b>5</b></a></li>
    2451                         <li class="indline1"><tt>User-Agent</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.21"><b>10.9</b></a></li>
     2585                        <li class="indline1"><tt>Allow</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.9"><b>9.1</b></a></li>
     2586                        <li class="indline1"><tt>Allow-v</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.10"><b>9.1</b></a></li>
     2587                        <li class="indline1"><tt>delta-seconds</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.26"><b>9.7</b></a></li>
     2588                        <li class="indline1"><tt>Expect</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.11"><b>9.2</b></a></li>
     2589                        <li class="indline1"><tt>expect-params</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.15"><b>9.2</b></a></li>
     2590                        <li class="indline1"><tt>Expect-v</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.12"><b>9.2</b></a></li>
     2591                        <li class="indline1"><tt>expectation</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.13"><b>9.2</b></a></li>
     2592                        <li class="indline1"><tt>expectation-extension</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.14"><b>9.2</b></a></li>
     2593                        <li class="indline1"><tt>extension-code</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.5"><b>4</b></a></li>
     2594                        <li class="indline1"><tt>extension-method</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.2"><b>2</b></a></li>
     2595                        <li class="indline1"><tt>From</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.16"><b>9.3</b></a></li>
     2596                        <li class="indline1"><tt>From-v</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.17"><b>9.3</b></a></li>
     2597                        <li class="indline1"><tt>Location</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.18"><b>9.4</b></a></li>
     2598                        <li class="indline1"><tt>Location-v</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.19"><b>9.4</b></a></li>
     2599                        <li class="indline1"><tt>Max-Forwards</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.20"><b>9.5</b></a></li>
     2600                        <li class="indline1"><tt>Max-Forwards-v</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.21"><b>9.5</b></a></li>
     2601                        <li class="indline1"><tt>Method</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.1"><b>2</b></a></li>
     2602                        <li class="indline1"><tt>Reason-Phrase</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.6"><b>4</b></a></li>
     2603                        <li class="indline1"><tt>Referer</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.22"><b>9.6</b></a></li>
     2604                        <li class="indline1"><tt>Referer-v</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.23"><b>9.6</b></a></li>
     2605                        <li class="indline1"><tt>request-header</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.3"><b>3</b></a></li>
     2606                        <li class="indline1"><tt>response-header</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.7"><b>5</b></a></li>
     2607                        <li class="indline1"><tt>Retry-After</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.24"><b>9.7</b></a></li>
     2608                        <li class="indline1"><tt>Retry-After-v</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.25"><b>9.7</b></a></li>
     2609                        <li class="indline1"><tt>Server</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.27"><b>9.8</b></a></li>
     2610                        <li class="indline1"><tt>Server-v</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.28"><b>9.8</b></a></li>
     2611                        <li class="indline1"><tt>Status-Code</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.4"><b>4</b></a></li>
     2612                        <li class="indline1"><tt>User-Agent</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.29"><b>9.9</b></a></li>
     2613                        <li class="indline1"><tt>User-Agent-v</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.30"><b>9.9</b></a></li>
    24522614                     </ul>
    24532615                  </li>
     
    24552617            </li>
    24562618            <li class="indline0"><a id="rfc.index.H" href="#rfc.index.H"><b>H</b></a><ul class="ind">
    2457                   <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>
     2619                  <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>
    24582620                  <li class="indline1">Headers&nbsp;&nbsp;
    24592621                     <ul class="ind">
    2460                         <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>
    2461                         <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>
    2462                         <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>
    2463                         <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>
    2464                         <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>
    2465                         <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>
    2466                         <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>
    2467                         <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>
    2468                         <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>
     2622                        <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>
     2623                        <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>
     2624                        <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>
     2625                        <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>
     2626                        <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>
     2627                        <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>
     2628                        <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>
     2629                        <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>
     2630                        <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>
    24692631                     </ul>
    24702632                  </li>
     
    24722634            </li>
    24732635            <li class="indline0"><a id="rfc.index.I" href="#rfc.index.I"><b>I</b></a><ul class="ind">
    2474                   <li class="indline1">Idempotent Methods&nbsp;&nbsp;<a class="iref" href="#rfc.iref.i.1"><b>8.1.2</b></a></li>
     2636                  <li class="indline1">Idempotent Methods&nbsp;&nbsp;<a class="iref" href="#rfc.iref.i.1"><b>7.1.2</b></a></li>
    24752637               </ul>
    24762638            </li>
    24772639            <li class="indline0"><a id="rfc.index.L" href="#rfc.index.L"><b>L</b></a><ul class="ind">
    24782640                  <li class="indline1">LINK method&nbsp;&nbsp;<a class="iref" href="#rfc.iref.l.2"><b>A.1</b></a></li>
    2479                   <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>
     2641                  <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>
    24802642               </ul>
    24812643            </li>
    24822644            <li class="indline0"><a id="rfc.index.M" href="#rfc.index.M"><b>M</b></a><ul class="ind">
    2483                   <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>
     2645                  <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>
    24842646                  <li class="indline1">Methods&nbsp;&nbsp;
    24852647                     <ul class="ind">
    2486                         <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>
    2487                         <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>
    2488                         <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>
    2489                         <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>
     2648                        <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>
     2649                        <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>
     2650                        <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>
     2651                        <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>
    24902652                        <li class="indline1">LINK&nbsp;&nbsp;<a class="iref" href="#rfc.iref.m.11"><b>A.1</b></a></li>
    2491                         <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>
     2653                        <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>
    24922654                        <li class="indline1">PATCH&nbsp;&nbsp;<a class="iref" href="#rfc.iref.m.10"><b>A.1</b></a></li>
    2493                         <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>
    2494                         <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>
    2495                         <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>
     2655                        <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>
     2656                        <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>
     2657                        <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>
    24962658                        <li class="indline1">UNLINK&nbsp;&nbsp;<a class="iref" href="#rfc.iref.m.12"><b>A.1</b></a></li>
    24972659                     </ul>
     
    25002662            </li>
    25012663            <li class="indline0"><a id="rfc.index.O" href="#rfc.index.O"><b>O</b></a><ul class="ind">
    2502                   <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>
     2664                  <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>
    25032665               </ul>
    25042666            </li>
    25052667            <li class="indline0"><a id="rfc.index.P" href="#rfc.index.P"><b>P</b></a><ul class="ind">
    2506                   <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">4</a>, <a class="iref" href="#rfc.xref.Part1.16">4</a>, <a class="iref" href="#rfc.xref.Part1.17">7</a>, <a class="iref" href="#rfc.xref.Part1.18">8.8</a>, <a class="iref" href="#rfc.xref.Part1.19">8.8</a>, <a class="iref" href="#rfc.xref.Part1.20">9.1.1</a>, <a class="iref" href="#rfc.xref.Part1.21">9.5.6</a>, <a class="iref" href="#rfc.xref.Part1.22">10.2</a>, <a class="iref" href="#rfc.xref.Part1.23">10.8</a>, <a class="iref" href="#rfc.xref.Part1.24">10.8</a>, <a class="iref" href="#rfc.xref.Part1.25">10.9</a>, <a class="iref" href="#Part1"><b>14.1</b></a>, <a class="iref" href="#rfc.xref.Part1.26">A.2</a><ul class="ind">
    2507                         <li class="indline1"><em>Section 1.2.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.2">2</a></li>
    2508                         <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></li>
    2509                         <li class="indline1"><em>Section 2.1</em>&nbsp;&nbsp;<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.13">2</a></li>
    2510                         <li class="indline1"><em>Section 3.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.21">9.5.6</a></li>
    2511                         <li class="indline1"><em>Section 3.2.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.11">2</a></li>
    2512                         <li class="indline1"><em>Section 3.4</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.12">2</a>, <a class="iref" href="#rfc.xref.Part1.23">10.8</a>, <a class="iref" href="#rfc.xref.Part1.25">10.9</a></li>
    2513                         <li class="indline1"><em>Section 4.3</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.17">7</a></li>
    2514                         <li class="indline1"><em>Section 7.2.3</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.20">9.1.1</a>, <a class="iref" href="#rfc.xref.Part1.22">10.2</a></li>
    2515                         <li class="indline1"><em>Section 8.4</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.10">2</a>, <a class="iref" href="#rfc.xref.Part1.15">4</a></li>
    2516                         <li class="indline1"><em>Section 8.8</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.14">2</a>, <a class="iref" href="#rfc.xref.Part1.16">4</a></li>
    2517                         <li class="indline1"><em>Section 8.9</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.18">8.8</a>, <a class="iref" href="#rfc.xref.Part1.24">10.8</a>, <a class="iref" href="#rfc.xref.Part1.26">A.2</a></li>
    2518                         <li class="indline1"><em>Section 9.3.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.19">8.8</a></li>
     2668                  <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.2</a>, <a class="iref" href="#rfc.xref.Part1.11">1.2.2</a>, <a class="iref" href="#rfc.xref.Part1.12">1.2.2</a>, <a class="iref" href="#rfc.xref.Part1.13">1.2.2</a>, <a class="iref" href="#rfc.xref.Part1.14">1.2.2</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">3</a>, <a class="iref" href="#rfc.xref.Part1.18">3</a>, <a class="iref" href="#rfc.xref.Part1.19">6</a>, <a class="iref" href="#rfc.xref.Part1.20">7.8</a>, <a class="iref" href="#rfc.xref.Part1.21">7.8</a>, <a class="iref" href="#rfc.xref.Part1.22">8.1.1</a>, <a class="iref" href="#rfc.xref.Part1.23">8.5.6</a>, <a class="iref" href="#rfc.xref.Part1.24">9.2</a>, <a class="iref" href="#rfc.xref.Part1.25">9.8</a>, <a class="iref" href="#rfc.xref.Part1.26">9.8</a>, <a class="iref" href="#rfc.xref.Part1.27">9.9</a>, <a class="iref" href="#Part1"><b>13.1</b></a>, <a class="iref" href="#rfc.xref.Part1.28">A.2</a><ul class="ind">
     2669                        <li class="indline1"><em>Section 1.2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.2">1.2</a></li>
     2670                        <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></li>
     2671                        <li class="indline1"><em>Section 2.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.10">1.2.2</a>, <a class="iref" href="#rfc.xref.Part1.11">1.2.2</a>, <a class="iref" href="#rfc.xref.Part1.12">1.2.2</a>, <a class="iref" href="#rfc.xref.Part1.14">1.2.2</a></li>
     2672                        <li class="indline1"><em>Section 3.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.23">8.5.6</a></li>
     2673                        <li class="indline1"><em>Section 3.2.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.13">1.2.2</a></li>
     2674                        <li class="indline1"><em>Section 3.4</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.15">1.2.2</a>, <a class="iref" href="#rfc.xref.Part1.25">9.8</a>, <a class="iref" href="#rfc.xref.Part1.27">9.9</a></li>
     2675                        <li class="indline1"><em>Section 4.3</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.19">6</a></li>
     2676                        <li class="indline1"><em>Section 7.2.3</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.22">8.1.1</a>, <a class="iref" href="#rfc.xref.Part1.24">9.2</a></li>
     2677                        <li class="indline1"><em>Section 8.4</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.17">3</a></li>
     2678                        <li class="indline1"><em>Section 8.8</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.16">1.2.2</a>, <a class="iref" href="#rfc.xref.Part1.18">3</a></li>
     2679                        <li class="indline1"><em>Section 8.9</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.20">7.8</a>, <a class="iref" href="#rfc.xref.Part1.26">9.8</a>, <a class="iref" href="#rfc.xref.Part1.28">A.2</a></li>
     2680                        <li class="indline1"><em>Section 9.3.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.21">7.8</a></li>
    25192681                     </ul>
    25202682                  </li>
    2521                   <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">
    2522                         <li class="indline1"><em>Section 5</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.10">9.3.1</a></li>
    2523                         <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>
    2524                         <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>
    2525                         <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>
    2526                         <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>
    2527                         <li class="indline1"><em>Section 6.7</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.11">10.4</a></li>
     2683                  <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">
     2684                        <li class="indline1"><em>Section 4</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.10">8.3.1</a></li>
     2685                        <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>
     2686                        <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>
     2687                        <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>
     2688                        <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>
     2689                        <li class="indline1"><em>Section 5.7</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.11">9.4</a></li>
    25282690                     </ul>
    25292691                  </li>
    2530                   <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">B.2</a><ul class="ind">
    2531                         <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>
    2532                         <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>
    2533                         <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>
    2534                         <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>
    2535                         <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>
     2692                  <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">
     2693                        <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>
     2694                        <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>
     2695                        <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>
     2696                        <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>
     2697                        <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>
    25362698                     </ul>
    25372699                  </li>
    2538                   <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">
    2539                         <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>
    2540                         <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>
    2541                         <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>
     2700                  <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">
     2701                        <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>
     2702                        <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>
     2703                        <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>
    25422704                     </ul>
    25432705                  </li>
    2544                   <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">
    2545                         <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>
    2546                         <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>
     2706                  <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">
     2707                        <li class="indline1"><em>Section 4.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>
     2708                        <li class="indline1"><em>Section 4.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>
    25472709                     </ul>
    25482710                  </li>
    2549                   <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">
    2550                         <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>
    2551                         <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>
    2552                         <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>
    2553                         <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>
     2711                  <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">
     2712                        <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>
     2713                        <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>
     2714                        <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>
     2715                        <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>
    25542716                     </ul>
    25552717                  </li>
    25562718                  <li class="indline1">PATCH method&nbsp;&nbsp;<a class="iref" href="#rfc.iref.p.3"><b>A.1</b></a></li>
    2557                   <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>
    2558                   <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>
     2719                  <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>
     2720                  <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>
    25592721               </ul>
    25602722            </li>
    25612723            <li class="indline0"><a id="rfc.index.R" href="#rfc.index.R"><b>R</b></a><ul class="ind">
    2562                   <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>
    2563                   <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>
    2564                   <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>
    2565                   <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">
     2724                  <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>
     2725                  <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>
     2726                  <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>
     2727                  <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">
    25662728                        <li class="indline1"><em>Section 19.6.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2068.2">A.1</a></li>
    25672729                     </ul>
    25682730                  </li>
    2569                   <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>
    2570                   <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">B.1</a></li>
    2571                   <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">
    2572                         <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>
     2731                  <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>
     2732                  <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>
     2733                  <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">
     2734                        <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>
    25732735                     </ul>
    25742736                  </li>
    2575                   <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>
    2576                   <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">
    2577                         <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>
     2737                  <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>
     2738                  <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">
     2739                        <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>
    25782740                     </ul>
    25792741                  </li>
    2580                   <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">
    2581                         <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>
     2742                  <li class="indline1"><em>RFC5234</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC5234.1">1.2</a>, <a class="iref" href="#RFC5234"><b>13.1</b></a><ul class="ind">
     2743                        <li class="indline1"><em>Appendix B.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC5234.1">1.2</a></li>
     2744                     </ul>
     2745                  </li>
     2746                  <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">
     2747                        <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>
    25822748                     </ul>
    25832749                  </li>
     
    25852751            </li>
    25862752            <li class="indline0"><a id="rfc.index.S" href="#rfc.index.S"><b>S</b></a><ul class="ind">
    2587                   <li class="indline1">Safe Methods&nbsp;&nbsp;<a class="iref" href="#rfc.iref.s.1"><b>8.1.1</b></a></li>
    2588                   <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>
     2753                  <li class="indline1">Safe Methods&nbsp;&nbsp;<a class="iref" href="#rfc.iref.s.1"><b>7.1.1</b></a></li>
     2754                  <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>
    25892755                  <li class="indline1">Status Codes&nbsp;&nbsp;
    25902756                     <ul class="ind">
    2591                         <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>
    2592                         <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>
    2593                         <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>
    2594                         <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>
    2595                         <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>
    2596                         <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>
    2597                         <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>
    2598                         <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>
    2599                         <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>
    2600                         <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>
    2601                         <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>
    2602                         <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>
    2603                         <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>
    2604                         <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>
    2605                         <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>
    2606                         <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>
    2607                         <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>
    2608                         <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>
    2609                         <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>
    2610                         <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>
    2611                         <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>
    2612                         <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>
    2613                         <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>
    2614                         <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>
    2615                         <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>
    2616                         <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>
    2617                         <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>
    2618                         <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>
    2619                         <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>
    2620                         <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>
    2621                         <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>
    2622                         <li class="indline1">414 Request-URI 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>
    2623                         <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>
    2624                         <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>
    2625                         <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>
    2626                         <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>
    2627                         <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>
    2628                         <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>
    2629                         <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>
    2630                         <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>
    2631                         <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>
     2757                        <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>
     2758                        <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>
     2759                        <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>
     2760                        <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>
     2761                        <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>
     2762                        <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>
     2763                        <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>
     2764                        <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>
     2765                        <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>
     2766                        <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>
     2767                        <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>
     2768                        <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>
     2769                        <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>
     2770                        <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>
     2771                        <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>
     2772                        <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>
     2773                        <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>
     2774                        <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>
     2775                        <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>
     2776                        <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>
     2777                        <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>
     2778                        <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>
     2779                        <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>
     2780                        <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>
     2781                        <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>
     2782                        <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>
     2783                        <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>
     2784                        <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>
     2785                        <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>
     2786                        <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>
     2787                        <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>
     2788                        <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>
     2789                        <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>
     2790                        <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>
     2791                        <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>
     2792                        <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>
     2793                        <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>
     2794                        <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>
     2795                        <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>
     2796                        <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>
     2797                        <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>
    26322798                     </ul>
    26332799                  </li>
     
    26352801            </li>
    26362802            <li class="indline0"><a id="rfc.index.T" href="#rfc.index.T"><b>T</b></a><ul class="ind">
    2637                   <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>
     2803                  <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.1</a></li>
    26382804               </ul>
    26392805            </li>
    26402806            <li class="indline0"><a id="rfc.index.U" href="#rfc.index.U"><b>U</b></a><ul class="ind">
    26412807                  <li class="indline1">UNLINK method&nbsp;&nbsp;<a class="iref" href="#rfc.iref.u.2"><b>A.1</b></a></li>
    2642                   <li class="indline1">User-Agent header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.user-agent.1">4</a>, <a class="iref" href="#rfc.iref.u.1"><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>
     2808                  <li class="indline1">User-Agent header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.user-agent.1">3</a>, <a class="iref" href="#rfc.iref.u.1"><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>
    26432809               </ul>
    26442810            </li>
Note: See TracChangeset for help on using the changeset viewer.