Ignore:
Timestamp:
Dec 15, 2012, 1:54:13 PM (7 years ago)
Author:
fielding@…
Message:

Move product tokens into UA and clean User-Agent and Server definitions; Retitle Context and Informative sections; partly addresses #419

File:
1 edited

Legend:

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

    r2050 r2051  
    449449  }
    450450  @bottom-center {
    451        content: "Expires June 16, 2013";
     451       content: "Expires June 18, 2013";
    452452  }
    453453  @bottom-right {
     
    474474      <link rel="Chapter" title="2 Resources" href="#rfc.section.2">
    475475      <link rel="Chapter" title="3 Representations" href="#rfc.section.3">
    476       <link rel="Chapter" title="4 Product Tokens" href="#rfc.section.4">
    477       <link rel="Chapter" title="5 Request Methods" href="#rfc.section.5">
    478       <link rel="Chapter" title="6 Request Header Fields" href="#rfc.section.6">
    479       <link rel="Chapter" title="7 Response Status Codes" href="#rfc.section.7">
    480       <link rel="Chapter" title="8 Response Header Fields" href="#rfc.section.8">
    481       <link rel="Chapter" title="9 IANA Considerations" href="#rfc.section.9">
    482       <link rel="Chapter" title="10 Security Considerations" href="#rfc.section.10">
    483       <link rel="Chapter" title="11 Acknowledgments" href="#rfc.section.11">
    484       <link rel="Chapter" href="#rfc.section.12" title="12 References">
     476      <link rel="Chapter" title="4 Request Methods" href="#rfc.section.4">
     477      <link rel="Chapter" title="5 Request Header Fields" href="#rfc.section.5">
     478      <link rel="Chapter" title="6 Response Status Codes" href="#rfc.section.6">
     479      <link rel="Chapter" title="7 Response Header Fields" href="#rfc.section.7">
     480      <link rel="Chapter" title="8 IANA Considerations" href="#rfc.section.8">
     481      <link rel="Chapter" title="9 Security Considerations" href="#rfc.section.9">
     482      <link rel="Chapter" title="10 Acknowledgments" href="#rfc.section.10">
     483      <link rel="Chapter" href="#rfc.section.11" title="11 References">
    485484      <link rel="Appendix" title="A Differences between HTTP and MIME" href="#rfc.section.A">
    486485      <link rel="Appendix" title="B Additional Features" href="#rfc.section.B">
     
    496495      <meta name="dct.creator" content="Reschke, J. F.">
    497496      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p2-semantics-latest">
    498       <meta name="dct.issued" scheme="ISO8601" content="2012-12-13">
     497      <meta name="dct.issued" scheme="ISO8601" content="2012-12-15">
    499498      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    500499      <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. This document defines the semantics of HTTP/1.1 messages, as expressed by request methods, request header fields, response status codes, and response header fields, along with the payload of messages (metadata and body content) and mechanisms for content negotiation.">
     
    524523            <tr>
    525524               <td class="left">Intended status: Standards Track</td>
    526                <td class="right">December 13, 2012</td>
     525               <td class="right">December 15, 2012</td>
    527526            </tr>
    528527            <tr>
    529                <td class="left">Expires: June 16, 2013</td>
     528               <td class="left">Expires: June 18, 2013</td>
    530529               <td class="right"></td>
    531530            </tr>
     
    555554         in progress”.
    556555      </p>
    557       <p>This Internet-Draft will expire on June 16, 2013.</p>
     556      <p>This Internet-Draft will expire on June 18, 2013.</p>
    558557      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    559558      <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
     
    615614            </ul>
    616615         </li>
    617          <li><a href="#rfc.section.4">4.</a>&nbsp;&nbsp;&nbsp;<a href="#product.tokens">Product Tokens</a></li>
    618          <li><a href="#rfc.section.5">5.</a>&nbsp;&nbsp;&nbsp;<a href="#methods">Request Methods</a><ul>
    619                <li><a href="#rfc.section.5.1">5.1</a>&nbsp;&nbsp;&nbsp;<a href="#method.overview">Overview</a></li>
    620                <li><a href="#rfc.section.5.2">5.2</a>&nbsp;&nbsp;&nbsp;<a href="#method.properties">Common Method Properties</a><ul>
    621                      <li><a href="#rfc.section.5.2.1">5.2.1</a>&nbsp;&nbsp;&nbsp;<a href="#safe.methods">Safe Methods</a></li>
    622                      <li><a href="#rfc.section.5.2.2">5.2.2</a>&nbsp;&nbsp;&nbsp;<a href="#idempotent.methods">Idempotent Methods</a></li>
    623                      <li><a href="#rfc.section.5.2.3">5.2.3</a>&nbsp;&nbsp;&nbsp;<a href="#cacheable.methods">Cacheable Methods</a></li>
     616         <li><a href="#rfc.section.4">4.</a>&nbsp;&nbsp;&nbsp;<a href="#methods">Request Methods</a><ul>
     617               <li><a href="#rfc.section.4.1">4.1</a>&nbsp;&nbsp;&nbsp;<a href="#method.overview">Overview</a></li>
     618               <li><a href="#rfc.section.4.2">4.2</a>&nbsp;&nbsp;&nbsp;<a href="#method.properties">Common Method Properties</a><ul>
     619                     <li><a href="#rfc.section.4.2.1">4.2.1</a>&nbsp;&nbsp;&nbsp;<a href="#safe.methods">Safe Methods</a></li>
     620                     <li><a href="#rfc.section.4.2.2">4.2.2</a>&nbsp;&nbsp;&nbsp;<a href="#idempotent.methods">Idempotent Methods</a></li>
     621                     <li><a href="#rfc.section.4.2.3">4.2.3</a>&nbsp;&nbsp;&nbsp;<a href="#cacheable.methods">Cacheable Methods</a></li>
    624622                  </ul>
    625623               </li>
    626                <li><a href="#rfc.section.5.3">5.3</a>&nbsp;&nbsp;&nbsp;<a href="#method.definitions">Method Definitions</a><ul>
    627                      <li><a href="#rfc.section.5.3.1">5.3.1</a>&nbsp;&nbsp;&nbsp;<a href="#GET">GET</a></li>
    628                      <li><a href="#rfc.section.5.3.2">5.3.2</a>&nbsp;&nbsp;&nbsp;<a href="#HEAD">HEAD</a></li>
    629                      <li><a href="#rfc.section.5.3.3">5.3.3</a>&nbsp;&nbsp;&nbsp;<a href="#POST">POST</a></li>
    630                      <li><a href="#rfc.section.5.3.4">5.3.4</a>&nbsp;&nbsp;&nbsp;<a href="#PUT">PUT</a></li>
    631                      <li><a href="#rfc.section.5.3.5">5.3.5</a>&nbsp;&nbsp;&nbsp;<a href="#DELETE">DELETE</a></li>
    632                      <li><a href="#rfc.section.5.3.6">5.3.6</a>&nbsp;&nbsp;&nbsp;<a href="#CONNECT">CONNECT</a></li>
    633                      <li><a href="#rfc.section.5.3.7">5.3.7</a>&nbsp;&nbsp;&nbsp;<a href="#OPTIONS">OPTIONS</a></li>
    634                      <li><a href="#rfc.section.5.3.8">5.3.8</a>&nbsp;&nbsp;&nbsp;<a href="#TRACE">TRACE</a></li>
     624               <li><a href="#rfc.section.4.3">4.3</a>&nbsp;&nbsp;&nbsp;<a href="#method.definitions">Method Definitions</a><ul>
     625                     <li><a href="#rfc.section.4.3.1">4.3.1</a>&nbsp;&nbsp;&nbsp;<a href="#GET">GET</a></li>
     626                     <li><a href="#rfc.section.4.3.2">4.3.2</a>&nbsp;&nbsp;&nbsp;<a href="#HEAD">HEAD</a></li>
     627                     <li><a href="#rfc.section.4.3.3">4.3.3</a>&nbsp;&nbsp;&nbsp;<a href="#POST">POST</a></li>
     628                     <li><a href="#rfc.section.4.3.4">4.3.4</a>&nbsp;&nbsp;&nbsp;<a href="#PUT">PUT</a></li>
     629                     <li><a href="#rfc.section.4.3.5">4.3.5</a>&nbsp;&nbsp;&nbsp;<a href="#DELETE">DELETE</a></li>
     630                     <li><a href="#rfc.section.4.3.6">4.3.6</a>&nbsp;&nbsp;&nbsp;<a href="#CONNECT">CONNECT</a></li>
     631                     <li><a href="#rfc.section.4.3.7">4.3.7</a>&nbsp;&nbsp;&nbsp;<a href="#OPTIONS">OPTIONS</a></li>
     632                     <li><a href="#rfc.section.4.3.8">4.3.8</a>&nbsp;&nbsp;&nbsp;<a href="#TRACE">TRACE</a></li>
    635633                  </ul>
    636634               </li>
    637635            </ul>
    638636         </li>
    639          <li><a href="#rfc.section.6">6.</a>&nbsp;&nbsp;&nbsp;<a href="#request.header.fields">Request Header Fields</a><ul>
    640                <li><a href="#rfc.section.6.1">6.1</a>&nbsp;&nbsp;&nbsp;<a href="#request.controls">Controls</a><ul>
    641                      <li><a href="#rfc.section.6.1.1">6.1.1</a>&nbsp;&nbsp;&nbsp;<a href="#header.max-forwards">Max-Forwards</a></li>
    642                      <li><a href="#rfc.section.6.1.2">6.1.2</a>&nbsp;&nbsp;&nbsp;<a href="#header.expect">Expect</a><ul>
    643                            <li><a href="#rfc.section.6.1.2.1">6.1.2.1</a>&nbsp;&nbsp;&nbsp;<a href="#use.of.the.100.status">Use of the 100 (Continue) Status</a></li>
     637         <li><a href="#rfc.section.5">5.</a>&nbsp;&nbsp;&nbsp;<a href="#request.header.fields">Request Header Fields</a><ul>
     638               <li><a href="#rfc.section.5.1">5.1</a>&nbsp;&nbsp;&nbsp;<a href="#request.controls">Controls</a><ul>
     639                     <li><a href="#rfc.section.5.1.1">5.1.1</a>&nbsp;&nbsp;&nbsp;<a href="#header.max-forwards">Max-Forwards</a></li>
     640                     <li><a href="#rfc.section.5.1.2">5.1.2</a>&nbsp;&nbsp;&nbsp;<a href="#header.expect">Expect</a><ul>
     641                           <li><a href="#rfc.section.5.1.2.1">5.1.2.1</a>&nbsp;&nbsp;&nbsp;<a href="#use.of.the.100.status">Use of the 100 (Continue) Status</a></li>
    644642                        </ul>
    645643                     </li>
    646644                  </ul>
    647645               </li>
    648                <li><a href="#rfc.section.6.2">6.2</a>&nbsp;&nbsp;&nbsp;<a href="#request.conditionals">Conditionals</a></li>
    649                <li><a href="#rfc.section.6.3">6.3</a>&nbsp;&nbsp;&nbsp;<a href="#request.conneg">Content Negotiation</a><ul>
    650                      <li><a href="#rfc.section.6.3.1">6.3.1</a>&nbsp;&nbsp;&nbsp;<a href="#quality.values">Quality Values</a></li>
    651                      <li><a href="#rfc.section.6.3.2">6.3.2</a>&nbsp;&nbsp;&nbsp;<a href="#header.accept">Accept</a></li>
    652                      <li><a href="#rfc.section.6.3.3">6.3.3</a>&nbsp;&nbsp;&nbsp;<a href="#header.accept-charset">Accept-Charset</a></li>
    653                      <li><a href="#rfc.section.6.3.4">6.3.4</a>&nbsp;&nbsp;&nbsp;<a href="#header.accept-encoding">Accept-Encoding</a></li>
    654                      <li><a href="#rfc.section.6.3.5">6.3.5</a>&nbsp;&nbsp;&nbsp;<a href="#header.accept-language">Accept-Language</a></li>
     646               <li><a href="#rfc.section.5.2">5.2</a>&nbsp;&nbsp;&nbsp;<a href="#request.conditionals">Conditionals</a></li>
     647               <li><a href="#rfc.section.5.3">5.3</a>&nbsp;&nbsp;&nbsp;<a href="#request.conneg">Content Negotiation</a><ul>
     648                     <li><a href="#rfc.section.5.3.1">5.3.1</a>&nbsp;&nbsp;&nbsp;<a href="#quality.values">Quality Values</a></li>
     649                     <li><a href="#rfc.section.5.3.2">5.3.2</a>&nbsp;&nbsp;&nbsp;<a href="#header.accept">Accept</a></li>
     650                     <li><a href="#rfc.section.5.3.3">5.3.3</a>&nbsp;&nbsp;&nbsp;<a href="#header.accept-charset">Accept-Charset</a></li>
     651                     <li><a href="#rfc.section.5.3.4">5.3.4</a>&nbsp;&nbsp;&nbsp;<a href="#header.accept-encoding">Accept-Encoding</a></li>
     652                     <li><a href="#rfc.section.5.3.5">5.3.5</a>&nbsp;&nbsp;&nbsp;<a href="#header.accept-language">Accept-Language</a></li>
    655653                  </ul>
    656654               </li>
    657                <li><a href="#rfc.section.6.4">6.4</a>&nbsp;&nbsp;&nbsp;<a href="#request.auth">Authentication Credentials</a></li>
    658                <li><a href="#rfc.section.6.5">6.5</a>&nbsp;&nbsp;&nbsp;<a href="#request.context">Context</a><ul>
    659                      <li><a href="#rfc.section.6.5.1">6.5.1</a>&nbsp;&nbsp;&nbsp;<a href="#header.from">From</a></li>
    660                      <li><a href="#rfc.section.6.5.2">6.5.2</a>&nbsp;&nbsp;&nbsp;<a href="#header.referer">Referer</a></li>
    661                      <li><a href="#rfc.section.6.5.3">6.5.3</a>&nbsp;&nbsp;&nbsp;<a href="#header.user-agent">User-Agent</a></li>
     655               <li><a href="#rfc.section.5.4">5.4</a>&nbsp;&nbsp;&nbsp;<a href="#request.auth">Authentication Credentials</a></li>
     656               <li><a href="#rfc.section.5.5">5.5</a>&nbsp;&nbsp;&nbsp;<a href="#request.context">Request Context</a><ul>
     657                     <li><a href="#rfc.section.5.5.1">5.5.1</a>&nbsp;&nbsp;&nbsp;<a href="#header.from">From</a></li>
     658                     <li><a href="#rfc.section.5.5.2">5.5.2</a>&nbsp;&nbsp;&nbsp;<a href="#header.referer">Referer</a></li>
     659                     <li><a href="#rfc.section.5.5.3">5.5.3</a>&nbsp;&nbsp;&nbsp;<a href="#header.user-agent">User-Agent</a></li>
    662660                  </ul>
    663661               </li>
    664662            </ul>
    665663         </li>
    666          <li><a href="#rfc.section.7">7.</a>&nbsp;&nbsp;&nbsp;<a href="#status.codes">Response Status Codes</a><ul>
    667                <li><a href="#rfc.section.7.1">7.1</a>&nbsp;&nbsp;&nbsp;<a href="#overview.of.status.codes">Overview of Status Codes</a></li>
    668                <li><a href="#rfc.section.7.2">7.2</a>&nbsp;&nbsp;&nbsp;<a href="#status.1xx">Informational 1xx</a><ul>
    669                      <li><a href="#rfc.section.7.2.1">7.2.1</a>&nbsp;&nbsp;&nbsp;<a href="#status.100">100 Continue</a></li>
    670                      <li><a href="#rfc.section.7.2.2">7.2.2</a>&nbsp;&nbsp;&nbsp;<a href="#status.101">101 Switching Protocols</a></li>
     664         <li><a href="#rfc.section.6">6.</a>&nbsp;&nbsp;&nbsp;<a href="#status.codes">Response Status Codes</a><ul>
     665               <li><a href="#rfc.section.6.1">6.1</a>&nbsp;&nbsp;&nbsp;<a href="#overview.of.status.codes">Overview of Status Codes</a></li>
     666               <li><a href="#rfc.section.6.2">6.2</a>&nbsp;&nbsp;&nbsp;<a href="#status.1xx">Informational 1xx</a><ul>
     667                     <li><a href="#rfc.section.6.2.1">6.2.1</a>&nbsp;&nbsp;&nbsp;<a href="#status.100">100 Continue</a></li>
     668                     <li><a href="#rfc.section.6.2.2">6.2.2</a>&nbsp;&nbsp;&nbsp;<a href="#status.101">101 Switching Protocols</a></li>
    671669                  </ul>
    672670               </li>
    673                <li><a href="#rfc.section.7.3">7.3</a>&nbsp;&nbsp;&nbsp;<a href="#status.2xx">Successful 2xx</a><ul>
    674                      <li><a href="#rfc.section.7.3.1">7.3.1</a>&nbsp;&nbsp;&nbsp;<a href="#status.200">200 OK</a></li>
    675                      <li><a href="#rfc.section.7.3.2">7.3.2</a>&nbsp;&nbsp;&nbsp;<a href="#status.201">201 Created</a></li>
    676                      <li><a href="#rfc.section.7.3.3">7.3.3</a>&nbsp;&nbsp;&nbsp;<a href="#status.202">202 Accepted</a></li>
    677                      <li><a href="#rfc.section.7.3.4">7.3.4</a>&nbsp;&nbsp;&nbsp;<a href="#status.203">203 Non-Authoritative Information</a></li>
    678                      <li><a href="#rfc.section.7.3.5">7.3.5</a>&nbsp;&nbsp;&nbsp;<a href="#status.204">204 No Content</a></li>
    679                      <li><a href="#rfc.section.7.3.6">7.3.6</a>&nbsp;&nbsp;&nbsp;<a href="#status.205">205 Reset Content</a></li>
     671               <li><a href="#rfc.section.6.3">6.3</a>&nbsp;&nbsp;&nbsp;<a href="#status.2xx">Successful 2xx</a><ul>
     672                     <li><a href="#rfc.section.6.3.1">6.3.1</a>&nbsp;&nbsp;&nbsp;<a href="#status.200">200 OK</a></li>
     673                     <li><a href="#rfc.section.6.3.2">6.3.2</a>&nbsp;&nbsp;&nbsp;<a href="#status.201">201 Created</a></li>
     674                     <li><a href="#rfc.section.6.3.3">6.3.3</a>&nbsp;&nbsp;&nbsp;<a href="#status.202">202 Accepted</a></li>
     675                     <li><a href="#rfc.section.6.3.4">6.3.4</a>&nbsp;&nbsp;&nbsp;<a href="#status.203">203 Non-Authoritative Information</a></li>
     676                     <li><a href="#rfc.section.6.3.5">6.3.5</a>&nbsp;&nbsp;&nbsp;<a href="#status.204">204 No Content</a></li>
     677                     <li><a href="#rfc.section.6.3.6">6.3.6</a>&nbsp;&nbsp;&nbsp;<a href="#status.205">205 Reset Content</a></li>
    680678                  </ul>
    681679               </li>
    682                <li><a href="#rfc.section.7.4">7.4</a>&nbsp;&nbsp;&nbsp;<a href="#status.3xx">Redirection 3xx</a><ul>
    683                      <li><a href="#rfc.section.7.4.1">7.4.1</a>&nbsp;&nbsp;&nbsp;<a href="#status.300">300 Multiple Choices</a></li>
    684                      <li><a href="#rfc.section.7.4.2">7.4.2</a>&nbsp;&nbsp;&nbsp;<a href="#status.301">301 Moved Permanently</a></li>
    685                      <li><a href="#rfc.section.7.4.3">7.4.3</a>&nbsp;&nbsp;&nbsp;<a href="#status.302">302 Found</a></li>
    686                      <li><a href="#rfc.section.7.4.4">7.4.4</a>&nbsp;&nbsp;&nbsp;<a href="#status.303">303 See Other</a></li>
    687                      <li><a href="#rfc.section.7.4.5">7.4.5</a>&nbsp;&nbsp;&nbsp;<a href="#status.305">305 Use Proxy</a></li>
    688                      <li><a href="#rfc.section.7.4.6">7.4.6</a>&nbsp;&nbsp;&nbsp;<a href="#status.306">306 (Unused)</a></li>
    689                      <li><a href="#rfc.section.7.4.7">7.4.7</a>&nbsp;&nbsp;&nbsp;<a href="#status.307">307 Temporary Redirect</a></li>
     680               <li><a href="#rfc.section.6.4">6.4</a>&nbsp;&nbsp;&nbsp;<a href="#status.3xx">Redirection 3xx</a><ul>
     681                     <li><a href="#rfc.section.6.4.1">6.4.1</a>&nbsp;&nbsp;&nbsp;<a href="#status.300">300 Multiple Choices</a></li>
     682                     <li><a href="#rfc.section.6.4.2">6.4.2</a>&nbsp;&nbsp;&nbsp;<a href="#status.301">301 Moved Permanently</a></li>
     683                     <li><a href="#rfc.section.6.4.3">6.4.3</a>&nbsp;&nbsp;&nbsp;<a href="#status.302">302 Found</a></li>
     684                     <li><a href="#rfc.section.6.4.4">6.4.4</a>&nbsp;&nbsp;&nbsp;<a href="#status.303">303 See Other</a></li>
     685                     <li><a href="#rfc.section.6.4.5">6.4.5</a>&nbsp;&nbsp;&nbsp;<a href="#status.305">305 Use Proxy</a></li>
     686                     <li><a href="#rfc.section.6.4.6">6.4.6</a>&nbsp;&nbsp;&nbsp;<a href="#status.306">306 (Unused)</a></li>
     687                     <li><a href="#rfc.section.6.4.7">6.4.7</a>&nbsp;&nbsp;&nbsp;<a href="#status.307">307 Temporary Redirect</a></li>
    690688                  </ul>
    691689               </li>
    692                <li><a href="#rfc.section.7.5">7.5</a>&nbsp;&nbsp;&nbsp;<a href="#status.4xx">Client Error 4xx</a><ul>
    693                      <li><a href="#rfc.section.7.5.1">7.5.1</a>&nbsp;&nbsp;&nbsp;<a href="#status.400">400 Bad Request</a></li>
    694                      <li><a href="#rfc.section.7.5.2">7.5.2</a>&nbsp;&nbsp;&nbsp;<a href="#status.402">402 Payment Required</a></li>
    695                      <li><a href="#rfc.section.7.5.3">7.5.3</a>&nbsp;&nbsp;&nbsp;<a href="#status.403">403 Forbidden</a></li>
    696                      <li><a href="#rfc.section.7.5.4">7.5.4</a>&nbsp;&nbsp;&nbsp;<a href="#status.404">404 Not Found</a></li>
    697                      <li><a href="#rfc.section.7.5.5">7.5.5</a>&nbsp;&nbsp;&nbsp;<a href="#status.405">405 Method Not Allowed</a></li>
    698                      <li><a href="#rfc.section.7.5.6">7.5.6</a>&nbsp;&nbsp;&nbsp;<a href="#status.406">406 Not Acceptable</a></li>
    699                      <li><a href="#rfc.section.7.5.7">7.5.7</a>&nbsp;&nbsp;&nbsp;<a href="#status.408">408 Request Timeout</a></li>
    700                      <li><a href="#rfc.section.7.5.8">7.5.8</a>&nbsp;&nbsp;&nbsp;<a href="#status.409">409 Conflict</a></li>
    701                      <li><a href="#rfc.section.7.5.9">7.5.9</a>&nbsp;&nbsp;&nbsp;<a href="#status.410">410 Gone</a></li>
    702                      <li><a href="#rfc.section.7.5.10">7.5.10</a>&nbsp;&nbsp;&nbsp;<a href="#status.411">411 Length Required</a></li>
    703                      <li><a href="#rfc.section.7.5.11">7.5.11</a>&nbsp;&nbsp;&nbsp;<a href="#status.413">413 Request Representation Too Large</a></li>
    704                      <li><a href="#rfc.section.7.5.12">7.5.12</a>&nbsp;&nbsp;&nbsp;<a href="#status.414">414 URI Too Long</a></li>
    705                      <li><a href="#rfc.section.7.5.13">7.5.13</a>&nbsp;&nbsp;&nbsp;<a href="#status.415">415 Unsupported Media Type</a></li>
    706                      <li><a href="#rfc.section.7.5.14">7.5.14</a>&nbsp;&nbsp;&nbsp;<a href="#status.417">417 Expectation Failed</a></li>
    707                      <li><a href="#rfc.section.7.5.15">7.5.15</a>&nbsp;&nbsp;&nbsp;<a href="#status.426">426 Upgrade Required</a></li>
     690               <li><a href="#rfc.section.6.5">6.5</a>&nbsp;&nbsp;&nbsp;<a href="#status.4xx">Client Error 4xx</a><ul>
     691                     <li><a href="#rfc.section.6.5.1">6.5.1</a>&nbsp;&nbsp;&nbsp;<a href="#status.400">400 Bad Request</a></li>
     692                     <li><a href="#rfc.section.6.5.2">6.5.2</a>&nbsp;&nbsp;&nbsp;<a href="#status.402">402 Payment Required</a></li>
     693                     <li><a href="#rfc.section.6.5.3">6.5.3</a>&nbsp;&nbsp;&nbsp;<a href="#status.403">403 Forbidden</a></li>
     694                     <li><a href="#rfc.section.6.5.4">6.5.4</a>&nbsp;&nbsp;&nbsp;<a href="#status.404">404 Not Found</a></li>
     695                     <li><a href="#rfc.section.6.5.5">6.5.5</a>&nbsp;&nbsp;&nbsp;<a href="#status.405">405 Method Not Allowed</a></li>
     696                     <li><a href="#rfc.section.6.5.6">6.5.6</a>&nbsp;&nbsp;&nbsp;<a href="#status.406">406 Not Acceptable</a></li>
     697                     <li><a href="#rfc.section.6.5.7">6.5.7</a>&nbsp;&nbsp;&nbsp;<a href="#status.408">408 Request Timeout</a></li>
     698                     <li><a href="#rfc.section.6.5.8">6.5.8</a>&nbsp;&nbsp;&nbsp;<a href="#status.409">409 Conflict</a></li>
     699                     <li><a href="#rfc.section.6.5.9">6.5.9</a>&nbsp;&nbsp;&nbsp;<a href="#status.410">410 Gone</a></li>
     700                     <li><a href="#rfc.section.6.5.10">6.5.10</a>&nbsp;&nbsp;&nbsp;<a href="#status.411">411 Length Required</a></li>
     701                     <li><a href="#rfc.section.6.5.11">6.5.11</a>&nbsp;&nbsp;&nbsp;<a href="#status.413">413 Request Representation Too Large</a></li>
     702                     <li><a href="#rfc.section.6.5.12">6.5.12</a>&nbsp;&nbsp;&nbsp;<a href="#status.414">414 URI Too Long</a></li>
     703                     <li><a href="#rfc.section.6.5.13">6.5.13</a>&nbsp;&nbsp;&nbsp;<a href="#status.415">415 Unsupported Media Type</a></li>
     704                     <li><a href="#rfc.section.6.5.14">6.5.14</a>&nbsp;&nbsp;&nbsp;<a href="#status.417">417 Expectation Failed</a></li>
     705                     <li><a href="#rfc.section.6.5.15">6.5.15</a>&nbsp;&nbsp;&nbsp;<a href="#status.426">426 Upgrade Required</a></li>
    708706                  </ul>
    709707               </li>
    710                <li><a href="#rfc.section.7.6">7.6</a>&nbsp;&nbsp;&nbsp;<a href="#status.5xx">Server Error 5xx</a><ul>
    711                      <li><a href="#rfc.section.7.6.1">7.6.1</a>&nbsp;&nbsp;&nbsp;<a href="#status.500">500 Internal Server Error</a></li>
    712                      <li><a href="#rfc.section.7.6.2">7.6.2</a>&nbsp;&nbsp;&nbsp;<a href="#status.501">501 Not Implemented</a></li>
    713                      <li><a href="#rfc.section.7.6.3">7.6.3</a>&nbsp;&nbsp;&nbsp;<a href="#status.502">502 Bad Gateway</a></li>
    714                      <li><a href="#rfc.section.7.6.4">7.6.4</a>&nbsp;&nbsp;&nbsp;<a href="#status.503">503 Service Unavailable</a></li>
    715                      <li><a href="#rfc.section.7.6.5">7.6.5</a>&nbsp;&nbsp;&nbsp;<a href="#status.504">504 Gateway Timeout</a></li>
    716                      <li><a href="#rfc.section.7.6.6">7.6.6</a>&nbsp;&nbsp;&nbsp;<a href="#status.505">505 HTTP Version Not Supported</a></li>
     708               <li><a href="#rfc.section.6.6">6.6</a>&nbsp;&nbsp;&nbsp;<a href="#status.5xx">Server Error 5xx</a><ul>
     709                     <li><a href="#rfc.section.6.6.1">6.6.1</a>&nbsp;&nbsp;&nbsp;<a href="#status.500">500 Internal Server Error</a></li>
     710                     <li><a href="#rfc.section.6.6.2">6.6.2</a>&nbsp;&nbsp;&nbsp;<a href="#status.501">501 Not Implemented</a></li>
     711                     <li><a href="#rfc.section.6.6.3">6.6.3</a>&nbsp;&nbsp;&nbsp;<a href="#status.502">502 Bad Gateway</a></li>
     712                     <li><a href="#rfc.section.6.6.4">6.6.4</a>&nbsp;&nbsp;&nbsp;<a href="#status.503">503 Service Unavailable</a></li>
     713                     <li><a href="#rfc.section.6.6.5">6.6.5</a>&nbsp;&nbsp;&nbsp;<a href="#status.504">504 Gateway Timeout</a></li>
     714                     <li><a href="#rfc.section.6.6.6">6.6.6</a>&nbsp;&nbsp;&nbsp;<a href="#status.505">505 HTTP Version Not Supported</a></li>
    717715                  </ul>
    718716               </li>
    719717            </ul>
    720718         </li>
    721          <li><a href="#rfc.section.8">8.</a>&nbsp;&nbsp;&nbsp;<a href="#response.header.fields">Response Header Fields</a><ul>
    722                <li><a href="#rfc.section.8.1">8.1</a>&nbsp;&nbsp;&nbsp;<a href="#response.control.data">Control Data</a><ul>
    723                      <li><a href="#rfc.section.8.1.1">8.1.1</a>&nbsp;&nbsp;&nbsp;<a href="#origination.date">Origination Date</a><ul>
    724                            <li><a href="#rfc.section.8.1.1.1">8.1.1.1</a>&nbsp;&nbsp;&nbsp;<a href="#http.date">Date/Time Formats</a></li>
    725                            <li><a href="#rfc.section.8.1.1.2">8.1.1.2</a>&nbsp;&nbsp;&nbsp;<a href="#header.date">Date</a></li>
     719         <li><a href="#rfc.section.7">7.</a>&nbsp;&nbsp;&nbsp;<a href="#response.header.fields">Response Header Fields</a><ul>
     720               <li><a href="#rfc.section.7.1">7.1</a>&nbsp;&nbsp;&nbsp;<a href="#response.control.data">Control Data</a><ul>
     721                     <li><a href="#rfc.section.7.1.1">7.1.1</a>&nbsp;&nbsp;&nbsp;<a href="#origination.date">Origination Date</a><ul>
     722                           <li><a href="#rfc.section.7.1.1.1">7.1.1.1</a>&nbsp;&nbsp;&nbsp;<a href="#http.date">Date/Time Formats</a></li>
     723                           <li><a href="#rfc.section.7.1.1.2">7.1.1.2</a>&nbsp;&nbsp;&nbsp;<a href="#header.date">Date</a></li>
    726724                        </ul>
    727725                     </li>
    728                      <li><a href="#rfc.section.8.1.2">8.1.2</a>&nbsp;&nbsp;&nbsp;<a href="#header.location">Location</a></li>
    729                      <li><a href="#rfc.section.8.1.3">8.1.3</a>&nbsp;&nbsp;&nbsp;<a href="#header.retry-after">Retry-After</a></li>
     726                     <li><a href="#rfc.section.7.1.2">7.1.2</a>&nbsp;&nbsp;&nbsp;<a href="#header.location">Location</a></li>
     727                     <li><a href="#rfc.section.7.1.3">7.1.3</a>&nbsp;&nbsp;&nbsp;<a href="#header.retry-after">Retry-After</a></li>
    730728                  </ul>
    731729               </li>
    732                <li><a href="#rfc.section.8.2">8.2</a>&nbsp;&nbsp;&nbsp;<a href="#selected.representation">Selected Representation Header Fields</a><ul>
    733                      <li><a href="#rfc.section.8.2.1">8.2.1</a>&nbsp;&nbsp;&nbsp;<a href="#header.vary">Vary</a></li>
     730               <li><a href="#rfc.section.7.2">7.2</a>&nbsp;&nbsp;&nbsp;<a href="#selected.representation">Selected Representation Header Fields</a><ul>
     731                     <li><a href="#rfc.section.7.2.1">7.2.1</a>&nbsp;&nbsp;&nbsp;<a href="#header.vary">Vary</a></li>
    734732                  </ul>
    735733               </li>
    736                <li><a href="#rfc.section.8.3">8.3</a>&nbsp;&nbsp;&nbsp;<a href="#response.auth">Authentication Challenges</a></li>
    737                <li><a href="#rfc.section.8.4">8.4</a>&nbsp;&nbsp;&nbsp;<a href="#response.inform">Informative</a><ul>
    738                      <li><a href="#rfc.section.8.4.1">8.4.1</a>&nbsp;&nbsp;&nbsp;<a href="#header.allow">Allow</a></li>
    739                      <li><a href="#rfc.section.8.4.2">8.4.2</a>&nbsp;&nbsp;&nbsp;<a href="#header.server">Server</a></li>
     734               <li><a href="#rfc.section.7.3">7.3</a>&nbsp;&nbsp;&nbsp;<a href="#response.auth">Authentication Challenges</a></li>
     735               <li><a href="#rfc.section.7.4">7.4</a>&nbsp;&nbsp;&nbsp;<a href="#response.context">Response Context</a><ul>
     736                     <li><a href="#rfc.section.7.4.1">7.4.1</a>&nbsp;&nbsp;&nbsp;<a href="#header.allow">Allow</a></li>
     737                     <li><a href="#rfc.section.7.4.2">7.4.2</a>&nbsp;&nbsp;&nbsp;<a href="#header.server">Server</a></li>
    740738                  </ul>
    741739               </li>
    742740            </ul>
    743741         </li>
    744          <li><a href="#rfc.section.9">9.</a>&nbsp;&nbsp;&nbsp;<a href="#IANA.considerations">IANA Considerations</a><ul>
    745                <li><a href="#rfc.section.9.1">9.1</a>&nbsp;&nbsp;&nbsp;<a href="#method.registry">Method Registry</a><ul>
    746                      <li><a href="#rfc.section.9.1.1">9.1.1</a>&nbsp;&nbsp;&nbsp;<a href="#method.procedure">Procedure</a></li>
    747                      <li><a href="#rfc.section.9.1.2">9.1.2</a>&nbsp;&nbsp;&nbsp;<a href="#considerations.for.new.methods">Considerations for New Methods</a></li>
    748                      <li><a href="#rfc.section.9.1.3">9.1.3</a>&nbsp;&nbsp;&nbsp;<a href="#method.registration">Registrations</a></li>
     742         <li><a href="#rfc.section.8">8.</a>&nbsp;&nbsp;&nbsp;<a href="#IANA.considerations">IANA Considerations</a><ul>
     743               <li><a href="#rfc.section.8.1">8.1</a>&nbsp;&nbsp;&nbsp;<a href="#method.registry">Method Registry</a><ul>
     744                     <li><a href="#rfc.section.8.1.1">8.1.1</a>&nbsp;&nbsp;&nbsp;<a href="#method.procedure">Procedure</a></li>
     745                     <li><a href="#rfc.section.8.1.2">8.1.2</a>&nbsp;&nbsp;&nbsp;<a href="#considerations.for.new.methods">Considerations for New Methods</a></li>
     746                     <li><a href="#rfc.section.8.1.3">8.1.3</a>&nbsp;&nbsp;&nbsp;<a href="#method.registration">Registrations</a></li>
    749747                  </ul>
    750748               </li>
    751                <li><a href="#rfc.section.9.2">9.2</a>&nbsp;&nbsp;&nbsp;<a href="#status.code.registry">Status Code Registry</a><ul>
    752                      <li><a href="#rfc.section.9.2.1">9.2.1</a>&nbsp;&nbsp;&nbsp;<a href="#status.code.procedure">Procedure</a></li>
    753                      <li><a href="#rfc.section.9.2.2">9.2.2</a>&nbsp;&nbsp;&nbsp;<a href="#considerations.for.new.status.codes">Considerations for New Status Codes</a></li>
    754                      <li><a href="#rfc.section.9.2.3">9.2.3</a>&nbsp;&nbsp;&nbsp;<a href="#status.code.registration">Registrations</a></li>
     749               <li><a href="#rfc.section.8.2">8.2</a>&nbsp;&nbsp;&nbsp;<a href="#status.code.registry">Status Code Registry</a><ul>
     750                     <li><a href="#rfc.section.8.2.1">8.2.1</a>&nbsp;&nbsp;&nbsp;<a href="#status.code.procedure">Procedure</a></li>
     751                     <li><a href="#rfc.section.8.2.2">8.2.2</a>&nbsp;&nbsp;&nbsp;<a href="#considerations.for.new.status.codes">Considerations for New Status Codes</a></li>
     752                     <li><a href="#rfc.section.8.2.3">8.2.3</a>&nbsp;&nbsp;&nbsp;<a href="#status.code.registration">Registrations</a></li>
    755753                  </ul>
    756754               </li>
    757                <li><a href="#rfc.section.9.3">9.3</a>&nbsp;&nbsp;&nbsp;<a href="#header.field.registry">Header Field Registry</a><ul>
    758                      <li><a href="#rfc.section.9.3.1">9.3.1</a>&nbsp;&nbsp;&nbsp;<a href="#considerations.for.new.header.fields">Considerations for New Header Fields</a></li>
    759                      <li><a href="#rfc.section.9.3.2">9.3.2</a>&nbsp;&nbsp;&nbsp;<a href="#header.field.registration">Registrations</a></li>
     755               <li><a href="#rfc.section.8.3">8.3</a>&nbsp;&nbsp;&nbsp;<a href="#header.field.registry">Header Field Registry</a><ul>
     756                     <li><a href="#rfc.section.8.3.1">8.3.1</a>&nbsp;&nbsp;&nbsp;<a href="#considerations.for.new.header.fields">Considerations for New Header Fields</a></li>
     757                     <li><a href="#rfc.section.8.3.2">8.3.2</a>&nbsp;&nbsp;&nbsp;<a href="#header.field.registration">Registrations</a></li>
    760758                  </ul>
    761759               </li>
    762                <li><a href="#rfc.section.9.4">9.4</a>&nbsp;&nbsp;&nbsp;<a href="#content.coding.registry">Content Coding Registry</a><ul>
    763                      <li><a href="#rfc.section.9.4.1">9.4.1</a>&nbsp;&nbsp;&nbsp;<a href="#content.coding.procedure">Procedure</a></li>
    764                      <li><a href="#rfc.section.9.4.2">9.4.2</a>&nbsp;&nbsp;&nbsp;<a href="#content.coding.registration">Registrations</a></li>
     760               <li><a href="#rfc.section.8.4">8.4</a>&nbsp;&nbsp;&nbsp;<a href="#content.coding.registry">Content Coding Registry</a><ul>
     761                     <li><a href="#rfc.section.8.4.1">8.4.1</a>&nbsp;&nbsp;&nbsp;<a href="#content.coding.procedure">Procedure</a></li>
     762                     <li><a href="#rfc.section.8.4.2">8.4.2</a>&nbsp;&nbsp;&nbsp;<a href="#content.coding.registration">Registrations</a></li>
    765763                  </ul>
    766764               </li>
    767765            </ul>
    768766         </li>
    769          <li><a href="#rfc.section.10">10.</a>&nbsp;&nbsp;&nbsp;<a href="#security.considerations">Security Considerations</a><ul>
    770                <li><a href="#rfc.section.10.1">10.1</a>&nbsp;&nbsp;&nbsp;<a href="#security.sensitive">Transfer of Sensitive Information</a></li>
    771                <li><a href="#rfc.section.10.2">10.2</a>&nbsp;&nbsp;&nbsp;<a href="#encoding.sensitive.information.in.uris">Encoding Sensitive Information in URIs</a></li>
    772                <li><a href="#rfc.section.10.3">10.3</a>&nbsp;&nbsp;&nbsp;<a href="#location.spoofing-leakage">Location Header Fields: Spoofing and Information Leakage</a></li>
    773                <li><a href="#rfc.section.10.4">10.4</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.10.4">Security Considerations for CONNECT</a></li>
    774                <li><a href="#rfc.section.10.5">10.5</a>&nbsp;&nbsp;&nbsp;<a href="#privacy.issues.connected.to.accept.header.fields">Privacy Issues Connected to Accept Header Fields</a></li>
     767         <li><a href="#rfc.section.9">9.</a>&nbsp;&nbsp;&nbsp;<a href="#security.considerations">Security Considerations</a><ul>
     768               <li><a href="#rfc.section.9.1">9.1</a>&nbsp;&nbsp;&nbsp;<a href="#security.sensitive">Transfer of Sensitive Information</a></li>
     769               <li><a href="#rfc.section.9.2">9.2</a>&nbsp;&nbsp;&nbsp;<a href="#encoding.sensitive.information.in.uris">Encoding Sensitive Information in URIs</a></li>
     770               <li><a href="#rfc.section.9.3">9.3</a>&nbsp;&nbsp;&nbsp;<a href="#location.spoofing-leakage">Location Header Fields: Spoofing and Information Leakage</a></li>
     771               <li><a href="#rfc.section.9.4">9.4</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.9.4">Security Considerations for CONNECT</a></li>
     772               <li><a href="#rfc.section.9.5">9.5</a>&nbsp;&nbsp;&nbsp;<a href="#privacy.issues.connected.to.accept.header.fields">Privacy Issues Connected to Accept Header Fields</a></li>
    775773            </ul>
    776774         </li>
    777          <li><a href="#rfc.section.11">11.</a>&nbsp;&nbsp;&nbsp;<a href="#acks">Acknowledgments</a></li>
    778          <li><a href="#rfc.section.12">12.</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.references">References</a><ul>
    779                <li><a href="#rfc.section.12.1">12.1</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.references.1">Normative References</a></li>
    780                <li><a href="#rfc.section.12.2">12.2</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.references.2">Informative References</a></li>
     775         <li><a href="#rfc.section.10">10.</a>&nbsp;&nbsp;&nbsp;<a href="#acks">Acknowledgments</a></li>
     776         <li><a href="#rfc.section.11">11.</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.references">References</a><ul>
     777               <li><a href="#rfc.section.11.1">11.1</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.references.1">Normative References</a></li>
     778               <li><a href="#rfc.section.11.2">11.2</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.references.2">Informative References</a></li>
    781779            </ul>
    782780         </li>
     
    812810         (<a href="#representations" title="Representations">Section&nbsp;3</a>).
    813811      </p>
    814       <p id="rfc.section.1.p.3">HTTP semantics include the intentions defined by each request method (<a href="#methods" title="Request Methods">Section&nbsp;5</a>), extensions to those semantics that might be described in request header fields (<a href="#request.header.fields" title="Request Header Fields">Section&nbsp;6</a>), the meaning of status codes to indicate a machine-readable response (<a href="#status.codes" title="Response Status Codes">Section&nbsp;7</a>), and the meaning of other control data and resource metadata that might be given in response header fields (<a href="#response.header.fields" title="Response Header Fields">Section&nbsp;8</a>).
     812      <p id="rfc.section.1.p.3">HTTP semantics include the intentions defined by each request method (<a href="#methods" title="Request Methods">Section&nbsp;4</a>), extensions to those semantics that might be described in request header fields (<a href="#request.header.fields" title="Request Header Fields">Section&nbsp;5</a>), the meaning of status codes to indicate a machine-readable response (<a href="#status.codes" title="Response Status Codes">Section&nbsp;6</a>), and the meaning of other control data and resource metadata that might be given in response header fields (<a href="#response.header.fields" title="Response Header Fields">Section&nbsp;7</a>).
    815813      </p>
    816814      <p id="rfc.section.1.p.4"><span id="rfc.iref.c.1"></span> This document also defines representation metadata that describe how a payload is intended to be interpreted by a recipient,
     
    838836      </p>
    839837      <p id="rfc.section.2.p.3">One design goal of HTTP is to separate resource identification from request semantics, which is made possible by vesting the
    840          request semantics in the request method (<a href="#methods" title="Request Methods">Section&nbsp;5</a>) and a few request-modifying header fields (<a href="#request.header.fields" title="Request Header Fields">Section&nbsp;6</a>). Resource owners <em class="bcp14">SHOULD NOT</em> include request semantics within a URI, such as by specifying an action to invoke within the path or query components of the
     838         request semantics in the request method (<a href="#methods" title="Request Methods">Section&nbsp;4</a>) and a few request-modifying header fields (<a href="#request.header.fields" title="Request Header Fields">Section&nbsp;5</a>). Resource owners <em class="bcp14">SHOULD NOT</em> include request semantics within a URI, such as by specifying an action to invoke within the path or query components of the
    841839         effective request URI, unless those semantics are disabled when they are inconsistent with the request method.
    842840      </p>
     
    892890      <h3 id="rfc.section.3.1.1"><a href="#rfc.section.3.1.1">3.1.1</a>&nbsp;<a id="data.type" href="#data.type">Processing the Data</a></h3>
    893891      <h4 id="rfc.section.3.1.1.1"><a href="#rfc.section.3.1.1.1">3.1.1.1</a>&nbsp;<a id="media.type" href="#media.type">Media Type</a></h4>
    894       <p id="rfc.section.3.1.1.1.p.1">HTTP uses Internet Media Types <a href="#RFC2046" id="rfc.xref.RFC2046.1"><cite title="Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types">[RFC2046]</cite></a> in the <a href="#header.content-type" class="smpl">Content-Type</a> (<a href="#header.content-type" id="rfc.xref.header.content-type.2" title="Content-Type">Section&nbsp;3.1.1.5</a>) and <a href="#header.accept" class="smpl">Accept</a> (<a href="#header.accept" id="rfc.xref.header.accept.1" title="Accept">Section&nbsp;6.3.2</a>) header fields in order to provide open and extensible data typing and type negotiation. Media types define both a data format
     892      <p id="rfc.section.3.1.1.1.p.1">HTTP uses Internet Media Types <a href="#RFC2046" id="rfc.xref.RFC2046.1"><cite title="Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types">[RFC2046]</cite></a> in the <a href="#header.content-type" class="smpl">Content-Type</a> (<a href="#header.content-type" id="rfc.xref.header.content-type.2" title="Content-Type">Section&nbsp;3.1.1.5</a>) and <a href="#header.accept" class="smpl">Accept</a> (<a href="#header.accept" id="rfc.xref.header.accept.1" title="Accept">Section&nbsp;5.3.2</a>) header fields in order to provide open and extensible data typing and type negotiation. Media types define both a data format
    895893         and various processing models: how to process that data in accordance with each context in which it is received.
    896894      </p>
     
    985983      <div id="rfc.figure.u.7"></div><pre class="inline"><span id="rfc.iref.g.10"></span>  <a href="#content.codings" class="smpl">content-coding</a>   = <a href="#imported.abnf" class="smpl">token</a>
    986984</pre><p id="rfc.section.3.1.2.1.p.3">All content-coding values are case-insensitive and ought to be registered within the HTTP Content Coding registry, as defined
    987          in <a href="#content.coding.registry" title="Content Coding Registry">Section&nbsp;9.4</a>. They are used in the <a href="#header.accept-encoding" class="smpl">Accept-Encoding</a> (<a href="#header.accept-encoding" id="rfc.xref.header.accept-encoding.1" title="Accept-Encoding">Section&nbsp;6.3.4</a>) and <a href="#header.content-encoding" class="smpl">Content-Encoding</a> (<a href="#header.content-encoding" id="rfc.xref.header.content-encoding.2" title="Content-Encoding">Section&nbsp;3.1.2.2</a>) header fields.
     985         in <a href="#content.coding.registry" title="Content Coding Registry">Section&nbsp;8.4</a>. They are used in the <a href="#header.accept-encoding" class="smpl">Accept-Encoding</a> (<a href="#header.accept-encoding" id="rfc.xref.header.accept-encoding.1" title="Accept-Encoding">Section&nbsp;5.3.4</a>) and <a href="#header.content-encoding" class="smpl">Content-Encoding</a> (<a href="#header.content-encoding" id="rfc.xref.header.content-encoding.2" title="Content-Encoding">Section&nbsp;3.1.2.2</a>) header fields.
    988986      </p>
    989987      <p id="rfc.section.3.1.2.1.p.4">The following content-coding values are defined by this specification: </p>
     
    11541152         by both the request method and the response status code.
    11551153      </p>
    1156       <p id="rfc.section.3.3.p.3">For example, a representation in the payload of a PUT request (<a href="#PUT" id="rfc.xref.PUT.1" title="PUT">Section&nbsp;5.3.4</a>) represents the desired state of the target resource if the request is successfully applied, whereas a representation in
    1157          the payload of a POST request (<a href="#POST" id="rfc.xref.POST.1" title="POST">Section&nbsp;5.3.3</a>) represents an anonymous resource for providing data to be processed, such as the information that a user entered within
     1154      <p id="rfc.section.3.3.p.3">For example, a representation in the payload of a PUT request (<a href="#PUT" id="rfc.xref.PUT.1" title="PUT">Section&nbsp;4.3.4</a>) represents the desired state of the target resource if the request is successfully applied, whereas a representation in
     1155         the payload of a POST request (<a href="#POST" id="rfc.xref.POST.1" title="POST">Section&nbsp;4.3.3</a>) represents an anonymous resource for providing data to be processed, such as the information that a user entered within
    11581156         an HTML form.
    11591157      </p>
    1160       <p id="rfc.section.3.3.p.4">Likewise, the payload of a <a href="#status.200" class="smpl">200 (OK)</a> response to GET (<a href="#GET" id="rfc.xref.GET.1" title="GET">Section&nbsp;5.3.1</a>) contains a representation of the target resource, as observed at the time of the message origination date (<a href="#header.date" id="rfc.xref.header.date.1" title="Date">Section&nbsp;8.1.1.2</a>), whereas the same status code in a response to POST might contain either a representation of the processing result or a
     1158      <p id="rfc.section.3.3.p.4">Likewise, the payload of a <a href="#status.200" class="smpl">200 (OK)</a> response to GET (<a href="#GET" id="rfc.xref.GET.1" title="GET">Section&nbsp;4.3.1</a>) contains a representation of the target resource, as observed at the time of the message origination date (<a href="#header.date" id="rfc.xref.header.date.1" title="Date">Section&nbsp;7.1.1.2</a>), whereas the same status code in a response to POST might contain either a representation of the processing result or a
    11611159         current representation of the target resource after applying the processing. Response messages with an error status code usually
    11621160         contain a representation that describes the error and what next steps are suggested for resolving it.
     
    12101208         the server to select the preferred representation, it is called <dfn>proactive negotiation</dfn> (a.k.a., <dfn>server-driven negotiation</dfn>). Selection is based on the available representations for a response (the dimensions over which it might vary; e.g., language,
    12111209         content-coding, etc.) compared to various information supplied in the request, including both the explicit negotiation fields
    1212          of <a href="#request.conneg" title="Content Negotiation">Section&nbsp;6.3</a> and implicit characteristics, such as the client's network address or parts of the <a href="#header.user-agent" class="smpl">User-Agent</a> field.
     1210         of <a href="#request.conneg" title="Content Negotiation">Section&nbsp;5.3</a> and implicit characteristics, such as the client's network address or parts of the <a href="#header.user-agent" class="smpl">User-Agent</a> field.
    12131211      </p>
    12141212      <p id="rfc.section.3.4.1.p.2">Proactive negotiation is advantageous when the algorithm for selecting from among the available representations is difficult
     
    12331231         the user agent's preferences is better than sending a <a href="#status.406" class="smpl">406 (Not Acceptable)</a> response.
    12341232      </p>
    1235       <p id="rfc.section.3.4.1.p.5">An origin server <em class="bcp14">MAY</em> generate a <a href="#header.vary" class="smpl">Vary</a> header field (<a href="#header.vary" id="rfc.xref.header.vary.1" title="Vary">Section&nbsp;8.2.1</a>) in responses that are subject to proactive negotiation to indicate what parameters of request information might be used
     1233      <p id="rfc.section.3.4.1.p.5">An origin server <em class="bcp14">MAY</em> generate a <a href="#header.vary" class="smpl">Vary</a> header field (<a href="#header.vary" id="rfc.xref.header.vary.1" title="Vary">Section&nbsp;7.2.1</a>) in responses that are subject to proactive negotiation to indicate what parameters of request information might be used
    12361234         in its selection algorithm, thereby providing a means for recipients to determine the reusability of that same response for
    12371235         user agents with differing request information.
     
    12561254         such a mechanism from being developed as an extension.
    12571255      </p>
    1258       <h1 id="rfc.section.4"><a href="#rfc.section.4">4.</a>&nbsp;<a id="product.tokens" href="#product.tokens">Product Tokens</a></h1>
    1259       <p id="rfc.section.4.p.1">Product tokens are used to allow communicating applications to identify themselves by software name and version. Most fields
    1260          using product tokens also allow sub-products which form a significant part of the application to be listed, separated by whitespace.
    1261          By convention, the products are listed in order of their significance for identifying the application.
    1262       </p>
    1263       <div id="rfc.figure.u.17"></div><pre class="inline"><span id="rfc.iref.g.15"></span><span id="rfc.iref.g.16"></span>  <a href="#product.tokens" class="smpl">product</a>         = <a href="#imported.abnf" class="smpl">token</a> ["/" <a href="#product.tokens" class="smpl">product-version</a>]
    1264   <a href="#product.tokens" class="smpl">product-version</a> = <a href="#imported.abnf" class="smpl">token</a>
    1265 </pre><p id="rfc.section.4.p.3">Examples:</p>
    1266       <div id="rfc.figure.u.18"></div><pre class="text">  User-Agent: CERN-LineMode/2.15 libwww/2.17b3
    1267   Server: Apache/0.8.4
    1268 </pre><p id="rfc.section.4.p.5">Product tokens <em class="bcp14">SHOULD</em> be short and to the point. They <em class="bcp14">MUST NOT</em> be used for advertising or other non-essential information. Although any token octet <em class="bcp14">MAY</em> appear in a product-version, this token <em class="bcp14">SHOULD</em> only be used for a version identifier (i.e., successive versions of the same product <em class="bcp14">SHOULD</em> only differ in the product-version portion of the product value).
    1269       </p>
    1270       <h1 id="rfc.section.5"><a href="#rfc.section.5">5.</a>&nbsp;<a id="methods" href="#methods">Request Methods</a></h1>
    1271       <h2 id="rfc.section.5.1"><a href="#rfc.section.5.1">5.1</a>&nbsp;<a id="method.overview" href="#method.overview">Overview</a></h2>
    1272       <p id="rfc.section.5.1.p.1">The request method token is the primary source of request semantics; it indicates the purpose for which the client has made
    1273          this request and what is expected by the client as a successful result. The request semantics <em class="bcp14">MAY</em> be further specialized by the semantics of some header fields when present in a request (<a href="#request.header.fields" title="Request Header Fields">Section&nbsp;6</a>) if those additional semantics do not conflict with the method.
    1274       </p>
    1275       <div id="rfc.figure.u.19"></div><pre class="inline"><span id="rfc.iref.g.17"></span>  <a href="#method.overview" class="smpl">method</a> = <a href="#imported.abnf" class="smpl">token</a>
    1276 </pre><p id="rfc.section.5.1.p.3">HTTP was originally designed to be usable as an interface to distributed object systems. The request method was envisioned
     1256      <h1 id="rfc.section.4"><a href="#rfc.section.4">4.</a>&nbsp;<a id="methods" href="#methods">Request Methods</a></h1>
     1257      <h2 id="rfc.section.4.1"><a href="#rfc.section.4.1">4.1</a>&nbsp;<a id="method.overview" href="#method.overview">Overview</a></h2>
     1258      <p id="rfc.section.4.1.p.1">The request method token is the primary source of request semantics; it indicates the purpose for which the client has made
     1259         this request and what is expected by the client as a successful result. The request semantics <em class="bcp14">MAY</em> be further specialized by the semantics of some header fields when present in a request (<a href="#request.header.fields" title="Request Header Fields">Section&nbsp;5</a>) if those additional semantics do not conflict with the method.
     1260      </p>
     1261      <div id="rfc.figure.u.17"></div><pre class="inline"><span id="rfc.iref.g.15"></span>  <a href="#method.overview" class="smpl">method</a> = <a href="#imported.abnf" class="smpl">token</a>
     1262</pre><p id="rfc.section.4.1.p.3">HTTP was originally designed to be usable as an interface to distributed object systems. The request method was envisioned
    12771263         as applying semantics to a target resource in much the same way as invoking a defined method on an identified object would
    12781264         apply semantics. The method token is case-sensitive because it might be used as a gateway to object-based systems with case-sensitive
    12791265         method names.
    12801266      </p>
    1281       <p id="rfc.section.5.1.p.4">Unlike distributed objects, the standardized request methods in HTTP are not resource-specific, since uniform interfaces provide
     1267      <p id="rfc.section.4.1.p.4">Unlike distributed objects, the standardized request methods in HTTP are not resource-specific, since uniform interfaces provide
    12821268         for better visibility and reuse in network-based systems <a href="#REST" id="rfc.xref.REST.2"><cite title="Architectural Styles and the Design of Network-based Software Architectures">[REST]</cite></a>. Once defined, a standardized method <em class="bcp14">MUST</em> have the same semantics when applied to any resource, though each resource determines for itself whether those semantics are
    12831269         implemented or allowed.
    12841270      </p>
    1285       <p id="rfc.section.5.1.p.5">This specification defines a number of standardized methods that are commonly used in HTTP, as outlined by the following table.
     1271      <p id="rfc.section.4.1.p.5">This specification defines a number of standardized methods that are commonly used in HTTP, as outlined by the following table.
    12861272         By convention, standardized methods are defined in all-uppercase ASCII letters.
    12871273      </p>
     
    13001286                  <td class="left">GET</td>
    13011287                  <td class="left">Transfer a current representation of the target resource.</td>
    1302                   <td class="left"><a href="#GET" id="rfc.xref.GET.2" title="GET">5.3.1</a></td>
     1288                  <td class="left"><a href="#GET" id="rfc.xref.GET.2" title="GET">4.3.1</a></td>
    13031289               </tr>
    13041290               <tr>
    13051291                  <td class="left">HEAD</td>
    13061292                  <td class="left">Same as GET, but do not include a message body in the response.</td>
    1307                   <td class="left"><a href="#HEAD" id="rfc.xref.HEAD.1" title="HEAD">5.3.2</a></td>
     1293                  <td class="left"><a href="#HEAD" id="rfc.xref.HEAD.1" title="HEAD">4.3.2</a></td>
    13081294               </tr>
    13091295               <tr>
    13101296                  <td class="left">POST</td>
    13111297                  <td class="left">Perform resource-specific processing on the request payload.</td>
    1312                   <td class="left"><a href="#POST" id="rfc.xref.POST.2" title="POST">5.3.3</a></td>
     1298                  <td class="left"><a href="#POST" id="rfc.xref.POST.2" title="POST">4.3.3</a></td>
    13131299               </tr>
    13141300               <tr>
    13151301                  <td class="left">PUT</td>
    13161302                  <td class="left">Replace all current representations of the target resource with the request payload.</td>
    1317                   <td class="left"><a href="#PUT" id="rfc.xref.PUT.2" title="PUT">5.3.4</a></td>
     1303                  <td class="left"><a href="#PUT" id="rfc.xref.PUT.2" title="PUT">4.3.4</a></td>
    13181304               </tr>
    13191305               <tr>
    13201306                  <td class="left">DELETE</td>
    13211307                  <td class="left">Remove all current representations of the target resource.</td>
    1322                   <td class="left"><a href="#DELETE" id="rfc.xref.DELETE.1" title="DELETE">5.3.5</a></td>
     1308                  <td class="left"><a href="#DELETE" id="rfc.xref.DELETE.1" title="DELETE">4.3.5</a></td>
    13231309               </tr>
    13241310               <tr>
    13251311                  <td class="left">CONNECT</td>
    13261312                  <td class="left">Establish a tunnel to the server identified by the target resource.</td>
    1327                   <td class="left"><a href="#CONNECT" id="rfc.xref.CONNECT.1" title="CONNECT">5.3.6</a></td>
     1313                  <td class="left"><a href="#CONNECT" id="rfc.xref.CONNECT.1" title="CONNECT">4.3.6</a></td>
    13281314               </tr>
    13291315               <tr>
    13301316                  <td class="left">OPTIONS</td>
    13311317                  <td class="left">Describe the communication options for the target resource.</td>
    1332                   <td class="left"><a href="#OPTIONS" id="rfc.xref.OPTIONS.1" title="OPTIONS">5.3.7</a></td>
     1318                  <td class="left"><a href="#OPTIONS" id="rfc.xref.OPTIONS.1" title="OPTIONS">4.3.7</a></td>
    13331319               </tr>
    13341320               <tr>
    13351321                  <td class="left">TRACE</td>
    13361322                  <td class="left">Perform a message loop-back test along the path to the target resource.</td>
    1337                   <td class="left"><a href="#TRACE" id="rfc.xref.TRACE.1" title="TRACE">5.3.8</a></td>
     1323                  <td class="left"><a href="#TRACE" id="rfc.xref.TRACE.1" title="TRACE">4.3.8</a></td>
    13381324               </tr>
    13391325            </tbody>
    13401326         </table>
    13411327      </div>
    1342       <p id="rfc.section.5.1.p.6">The methods GET and HEAD <em class="bcp14">MUST</em> be supported by all general-purpose servers. All other methods are <em class="bcp14">OPTIONAL</em>. When implemented, a server <em class="bcp14">MUST</em> implement the above methods according to the semantics defined for them in <a href="#method.definitions" title="Method Definitions">Section&nbsp;5.3</a>.
    1343       </p>
    1344       <p id="rfc.section.5.1.p.7">Additional methods <em class="bcp14">MAY</em> be used in HTTP; many have already been standardized outside the scope of this specification and ought to be registered within
    1345          the HTTP Method Registry maintained by IANA, as defined in <a href="#method.registry" title="Method Registry">Section&nbsp;9.1</a>.
    1346       </p>
    1347       <p id="rfc.section.5.1.p.8">The set of methods allowed by a target resource can be listed in an <a href="#header.allow" class="smpl">Allow</a> header field (<a href="#header.allow" id="rfc.xref.header.allow.1" title="Allow">Section&nbsp;8.4.1</a>). However, the set of allowed methods can change dynamically. When a request message is received that is unrecognized or
     1328      <p id="rfc.section.4.1.p.6">The methods GET and HEAD <em class="bcp14">MUST</em> be supported by all general-purpose servers. All other methods are <em class="bcp14">OPTIONAL</em>. When implemented, a server <em class="bcp14">MUST</em> implement the above methods according to the semantics defined for them in <a href="#method.definitions" title="Method Definitions">Section&nbsp;4.3</a>.
     1329      </p>
     1330      <p id="rfc.section.4.1.p.7">Additional methods <em class="bcp14">MAY</em> be used in HTTP; many have already been standardized outside the scope of this specification and ought to be registered within
     1331         the HTTP Method Registry maintained by IANA, as defined in <a href="#method.registry" title="Method Registry">Section&nbsp;8.1</a>.
     1332      </p>
     1333      <p id="rfc.section.4.1.p.8">The set of methods allowed by a target resource can be listed in an <a href="#header.allow" class="smpl">Allow</a> header field (<a href="#header.allow" id="rfc.xref.header.allow.1" title="Allow">Section&nbsp;7.4.1</a>). However, the set of allowed methods can change dynamically. When a request message is received that is unrecognized or
    13481334         not implemented by an origin server, the origin server <em class="bcp14">SHOULD</em> respond with the <a href="#status.501" class="smpl">501 (Not Implemented)</a> status code. When a request message is received that is known by an origin server but not allowed for the target resource,
    13491335         the origin server <em class="bcp14">SHOULD</em> respond with the <a href="#status.405" class="smpl">405 (Method Not Allowed)</a> status code.
    13501336      </p>
    1351       <h2 id="rfc.section.5.2"><a href="#rfc.section.5.2">5.2</a>&nbsp;<a id="method.properties" href="#method.properties">Common Method Properties</a></h2>
     1337      <h2 id="rfc.section.4.2"><a href="#rfc.section.4.2">4.2</a>&nbsp;<a id="method.properties" href="#method.properties">Common Method Properties</a></h2>
    13521338      <div id="rfc.iref.s.1"></div>
    1353       <h3 id="rfc.section.5.2.1"><a href="#rfc.section.5.2.1">5.2.1</a>&nbsp;<a id="safe.methods" href="#safe.methods">Safe Methods</a></h3>
    1354       <p id="rfc.section.5.2.1.p.1">Request methods are considered "<dfn id="safe">safe</dfn>" if their defined semantics are essentially read-only; i.e., the client does not request, and does not expect, any state
     1339      <h3 id="rfc.section.4.2.1"><a href="#rfc.section.4.2.1">4.2.1</a>&nbsp;<a id="safe.methods" href="#safe.methods">Safe Methods</a></h3>
     1340      <p id="rfc.section.4.2.1.p.1">Request methods are considered "<dfn id="safe">safe</dfn>" if their defined semantics are essentially read-only; i.e., the client does not request, and does not expect, any state
    13551341         change on the origin server as a result of applying a safe method to a target resource. Likewise, reasonable use of a safe
    13561342         method is not expected to cause any harm, loss of property, or unusual burden on the origin server.
    13571343      </p>
    1358       <p id="rfc.section.5.2.1.p.2">This definition of safe methods does not prevent an implementation from including behavior that is potentially harmful, not
     1344      <p id="rfc.section.4.2.1.p.2">This definition of safe methods does not prevent an implementation from including behavior that is potentially harmful, not
    13591345         entirely read-only, or which causes side-effects while invoking a safe method. What is important, however, is that the client
    13601346         did not request that additional behavior and cannot be held accountable for it. For example, most servers append request information
     
    13631349         the Web will often have the side-effect of charging an advertising account.
    13641350      </p>
    1365       <p id="rfc.section.5.2.1.p.3">The GET, HEAD, OPTIONS, and TRACE request methods are defined to be safe.</p>
    1366       <p id="rfc.section.5.2.1.p.4">The purpose of distinguishing between safe and unsafe methods is to allow automated retrieval processes (spiders) and cache
     1351      <p id="rfc.section.4.2.1.p.3">The GET, HEAD, OPTIONS, and TRACE request methods are defined to be safe.</p>
     1352      <p id="rfc.section.4.2.1.p.4">The purpose of distinguishing between safe and unsafe methods is to allow automated retrieval processes (spiders) and cache
    13671353         performance optimization (pre-fetching) to work without fear of causing harm. In addition, it allows a user agent to apply
    13681354         appropriate constraints on the automated use of unsafe methods when processing potentially untrusted content.
    13691355      </p>
    1370       <p id="rfc.section.5.2.1.p.5">A user agent <em class="bcp14">SHOULD</em> distinguish between safe and unsafe methods when presenting potential actions to a user, such that the user can be made aware
     1356      <p id="rfc.section.4.2.1.p.5">A user agent <em class="bcp14">SHOULD</em> distinguish between safe and unsafe methods when presenting potential actions to a user, such that the user can be made aware
    13711357         of an unsafe action before it is requested.
    13721358      </p>
    1373       <p id="rfc.section.5.2.1.p.6">When a resource is constructed such that parameters within the effective request URI have the effect of selecting an action,
     1359      <p id="rfc.section.4.2.1.p.6">When a resource is constructed such that parameters within the effective request URI have the effect of selecting an action,
    13741360         it is the resource owner's responsibility to ensure that the action is consistent with the request method semantics. For example,
    13751361         it is common for Web-based content editing software to use actions within query parameters, such as "page?do=delete". If the
     
    13791365      </p>
    13801366      <div id="rfc.iref.i.1"></div>
    1381       <h3 id="rfc.section.5.2.2"><a href="#rfc.section.5.2.2">5.2.2</a>&nbsp;<a id="idempotent.methods" href="#idempotent.methods">Idempotent Methods</a></h3>
    1382       <p id="rfc.section.5.2.2.p.1">Request methods are considered "<dfn id="idempotent">idempotent</dfn>" if the intended effect of multiple identical requests is the same as for a single request. PUT, DELETE, and all safe request
     1367      <h3 id="rfc.section.4.2.2"><a href="#rfc.section.4.2.2">4.2.2</a>&nbsp;<a id="idempotent.methods" href="#idempotent.methods">Idempotent Methods</a></h3>
     1368      <p id="rfc.section.4.2.2.p.1">Request methods are considered "<dfn id="idempotent">idempotent</dfn>" if the intended effect of multiple identical requests is the same as for a single request. PUT, DELETE, and all safe request
    13831369         methods are idempotent.
    13841370      </p>
    1385       <p id="rfc.section.5.2.2.p.2">Like the definition of safe, the idempotent property only applies to what has been requested by the user; a server is free
     1371      <p id="rfc.section.4.2.2.p.2">Like the definition of safe, the idempotent property only applies to what has been requested by the user; a server is free
    13861372         to log each request separately, retain a revision control history, or implement other non-idempotent side-effects for each
    13871373         idempotent request.
    13881374      </p>
    1389       <p id="rfc.section.5.2.2.p.3">Idempotent methods are distinguished because the request can be repeated automatically if a communication failure occurs before
     1375      <p id="rfc.section.4.2.2.p.3">Idempotent methods are distinguished because the request can be repeated automatically if a communication failure occurs before
    13901376         the client is able to read the server's response. For example, if a client sends a PUT request and the underlying connection
    13911377         is closed before any response is received, then it can establish a new connection and retry the idempotent request because
     
    13941380      </p>
    13951381      <div id="rfc.iref.c.8"></div>
    1396       <h3 id="rfc.section.5.2.3"><a href="#rfc.section.5.2.3">5.2.3</a>&nbsp;<a id="cacheable.methods" href="#cacheable.methods">Cacheable Methods</a></h3>
    1397       <p id="rfc.section.5.2.3.p.1">Request methods are considered "<dfn id="cacheable">cacheable</dfn>" if it is possible and useful to answer a current client request with a stored response from a prior request. GET and HEAD
     1382      <h3 id="rfc.section.4.2.3"><a href="#rfc.section.4.2.3">4.2.3</a>&nbsp;<a id="cacheable.methods" href="#cacheable.methods">Cacheable Methods</a></h3>
     1383      <p id="rfc.section.4.2.3.p.1">Request methods are considered "<dfn id="cacheable">cacheable</dfn>" if it is possible and useful to answer a current client request with a stored response from a prior request. GET and HEAD
    13981384         are defined to be cacheable. In general, safe methods that do not depend on a current or authoritative response are cacheable,
    13991385         though the overwhelming majority of caches only support GET and HEAD. HTTP requirements for cache behavior and cacheable responses
    14001386         are defined in <a href="#Part6" id="rfc.xref.Part6.2"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>.
    14011387      </p>
    1402       <h2 id="rfc.section.5.3"><a href="#rfc.section.5.3">5.3</a>&nbsp;<a id="method.definitions" href="#method.definitions">Method Definitions</a></h2>
    1403       <h3 id="rfc.section.5.3.1"><a href="#rfc.section.5.3.1">5.3.1</a>&nbsp;<a id="GET" href="#GET">GET</a></h3>
    1404       <div id="rfc.iref.g.18"></div>
    1405       <p id="rfc.section.5.3.1.p.1">The GET method requests transfer of a current representation of the target resource.</p>
    1406       <p id="rfc.section.5.3.1.p.2">If the target resource is a data-producing process, it is the produced data which shall be returned as the representation
     1388      <h2 id="rfc.section.4.3"><a href="#rfc.section.4.3">4.3</a>&nbsp;<a id="method.definitions" href="#method.definitions">Method Definitions</a></h2>
     1389      <h3 id="rfc.section.4.3.1"><a href="#rfc.section.4.3.1">4.3.1</a>&nbsp;<a id="GET" href="#GET">GET</a></h3>
     1390      <div id="rfc.iref.g.16"></div>
     1391      <p id="rfc.section.4.3.1.p.1">The GET method requests transfer of a current representation of the target resource.</p>
     1392      <p id="rfc.section.4.3.1.p.2">If the target resource is a data-producing process, it is the produced data which shall be returned as the representation
    14071393         in the response and not the source text of the process, unless that text happens to be the output of the process.
    14081394      </p>
    1409       <p id="rfc.section.5.3.1.p.3">The semantics of the GET method change to a "conditional GET" if the request message includes an <a href="p4-conditional.html#header.if-modified-since" class="smpl">If-Modified-Since</a>, <a href="p4-conditional.html#header.if-unmodified-since" class="smpl">If-Unmodified-Since</a>, <a href="p4-conditional.html#header.if-match" class="smpl">If-Match</a>, <a href="p4-conditional.html#header.if-none-match" class="smpl">If-None-Match</a>, or <a href="p5-range.html#header.if-range" class="smpl">If-Range</a> header field (<a href="#Part4" id="rfc.xref.Part4.1"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests">[Part4]</cite></a>). A conditional GET requests that the representation be transferred only under the circumstances described by the conditional
     1395      <p id="rfc.section.4.3.1.p.3">The semantics of the GET method change to a "conditional GET" if the request message includes an <a href="p4-conditional.html#header.if-modified-since" class="smpl">If-Modified-Since</a>, <a href="p4-conditional.html#header.if-unmodified-since" class="smpl">If-Unmodified-Since</a>, <a href="p4-conditional.html#header.if-match" class="smpl">If-Match</a>, <a href="p4-conditional.html#header.if-none-match" class="smpl">If-None-Match</a>, or <a href="p5-range.html#header.if-range" class="smpl">If-Range</a> header field (<a href="#Part4" id="rfc.xref.Part4.1"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests">[Part4]</cite></a>). A conditional GET requests that the representation be transferred only under the circumstances described by the conditional
    14101396         header field(s). The conditional GET request is intended to reduce unnecessary network usage by allowing cached representations
    14111397         to be refreshed without requiring multiple requests or transferring data already held by the client.
    14121398      </p>
    1413       <p id="rfc.section.5.3.1.p.4">The semantics of the GET method change to a "partial GET" if the request message includes a <a href="p5-range.html#range.retrieval.requests" class="smpl">Range</a> header field (<a href="#Part5" id="rfc.xref.Part5.3"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Range Requests">[Part5]</cite></a>). A partial GET requests that only part of the representation 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.4"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Range Requests">[Part5]</cite></a>. The partial GET request is intended to reduce unnecessary network usage by allowing partially-retrieved representations
     1399      <p id="rfc.section.4.3.1.p.4">The semantics of the GET method change to a "partial GET" if the request message includes a <a href="p5-range.html#range.retrieval.requests" class="smpl">Range</a> header field (<a href="#Part5" id="rfc.xref.Part5.3"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Range Requests">[Part5]</cite></a>). A partial GET requests that only part of the representation 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.4"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Range Requests">[Part5]</cite></a>. The partial GET request is intended to reduce unnecessary network usage by allowing partially-retrieved representations
    14141400         to be completed without transferring data already held by the client.
    14151401      </p>
    1416       <p id="rfc.section.5.3.1.p.5">A payload within a GET request message has no defined semantics; sending a payload body on a GET request might cause some
     1402      <p id="rfc.section.4.3.1.p.5">A payload within a GET request message has no defined semantics; sending a payload body on a GET request might cause some
    14171403         existing implementations to reject the request.
    14181404      </p>
    1419       <p id="rfc.section.5.3.1.p.6">The response to a GET request is cacheable and <em class="bcp14">MAY</em> be used to satisfy subsequent GET and HEAD requests (see <a href="#Part6" id="rfc.xref.Part6.3"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>).
    1420       </p>
    1421       <p id="rfc.section.5.3.1.p.7">See <a href="#encoding.sensitive.information.in.uris" title="Encoding Sensitive Information in URIs">Section&nbsp;10.2</a> for security considerations when used for forms.
    1422       </p>
    1423       <h3 id="rfc.section.5.3.2"><a href="#rfc.section.5.3.2">5.3.2</a>&nbsp;<a id="HEAD" href="#HEAD">HEAD</a></h3>
     1405      <p id="rfc.section.4.3.1.p.6">The response to a GET request is cacheable and <em class="bcp14">MAY</em> be used to satisfy subsequent GET and HEAD requests (see <a href="#Part6" id="rfc.xref.Part6.3"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>).
     1406      </p>
     1407      <p id="rfc.section.4.3.1.p.7">See <a href="#encoding.sensitive.information.in.uris" title="Encoding Sensitive Information in URIs">Section&nbsp;9.2</a> for security considerations when used for forms.
     1408      </p>
     1409      <h3 id="rfc.section.4.3.2"><a href="#rfc.section.4.3.2">4.3.2</a>&nbsp;<a id="HEAD" href="#HEAD">HEAD</a></h3>
    14241410      <div id="rfc.iref.h.1"></div>
    1425       <p id="rfc.section.5.3.2.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 metadata contained in the HTTP header fields 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 metadata about the
     1411      <p id="rfc.section.4.3.2.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 metadata contained in the HTTP header fields 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 metadata about the
    14261412         representation implied by the request without transferring the representation data. This method is often used for testing
    14271413         hypertext links for validity, accessibility, and recent modification.
    14281414      </p>
    1429       <p id="rfc.section.5.3.2.p.2">The response to a HEAD request is cacheable and <em class="bcp14">MAY</em> be used to satisfy a subsequent HEAD request. It also has potential side effects on previously stored responses to GET; see <a href="p6-cache.html#head.effects" title="Updating Caches with HEAD Responses">Section 5</a> of <a href="#Part6" id="rfc.xref.Part6.4"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>.
    1430       </p>
    1431       <p id="rfc.section.5.3.2.p.3">A payload within a HEAD request message has no defined semantics; sending a payload body on a HEAD request might cause some
     1415      <p id="rfc.section.4.3.2.p.2">The response to a HEAD request is cacheable and <em class="bcp14">MAY</em> be used to satisfy a subsequent HEAD request. It also has potential side effects on previously stored responses to GET; see <a href="p6-cache.html#head.effects" title="Updating Caches with HEAD Responses">Section 5</a> of <a href="#Part6" id="rfc.xref.Part6.4"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>.
     1416      </p>
     1417      <p id="rfc.section.4.3.2.p.3">A payload within a HEAD request message has no defined semantics; sending a payload body on a HEAD request might cause some
    14321418         existing implementations to reject the request.
    14331419      </p>
    14341420      <div id="rfc.iref.p.2"></div>
    1435       <h3 id="rfc.section.5.3.3"><a href="#rfc.section.5.3.3">5.3.3</a>&nbsp;<a id="POST" href="#POST">POST</a></h3>
    1436       <p id="rfc.section.5.3.3.p.1">The POST method requests that the origin server accept the representation enclosed in the request as data to be processed
     1421      <h3 id="rfc.section.4.3.3"><a href="#rfc.section.4.3.3">4.3.3</a>&nbsp;<a id="POST" href="#POST">POST</a></h3>
     1422      <p id="rfc.section.4.3.3.p.1">The POST method requests that the origin server accept the representation enclosed in the request as data to be processed
    14371423         by the target resource. POST is designed to allow a uniform method to cover the following functions:
    14381424      </p>
     
    14431429         <li>Extending a database through an append operation.</li>
    14441430      </ul>
    1445       <p id="rfc.section.5.3.3.p.2">The actual function performed by the POST method is determined by the server and is usually dependent on the effective request
     1431      <p id="rfc.section.4.3.3.p.2">The actual function performed by the POST method is determined by the server and is usually dependent on the effective request
    14461432         URI.
    14471433      </p>
    1448       <p id="rfc.section.5.3.3.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 <a href="#status.200" class="smpl">200 (OK)</a> or <a href="#status.204" class="smpl">204 (No Content)</a> is the appropriate response status code, depending on whether or not the response includes a representation that describes
     1434      <p id="rfc.section.4.3.3.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 <a href="#status.200" class="smpl">200 (OK)</a> or <a href="#status.204" class="smpl">204 (No Content)</a> is the appropriate response status code, depending on whether or not the response includes a representation that describes
    14491435         the result.
    14501436      </p>
    1451       <p id="rfc.section.5.3.3.p.4">If a resource has been created on the origin server, the response <em class="bcp14">SHOULD</em> be <a href="#status.201" class="smpl">201 (Created)</a> and contain a representation which describes the status of the request and refers to the new resource, and a <a href="#header.location" class="smpl">Location</a> header field (see <a href="#header.location" id="rfc.xref.header.location.1" title="Location">Section&nbsp;8.1.2</a>).
    1452       </p>
    1453       <p id="rfc.section.5.3.3.p.5">Responses to POST requests are only cacheable when they include explicit freshness information (see <a href="p6-cache.html#calculating.freshness.lifetime" title="Calculating Freshness Lifetime">Section 4.1.1</a> of <a href="#Part6" id="rfc.xref.Part6.5"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>). A cached POST response with a <a href="#header.content-location" class="smpl">Content-Location</a> header field (see <a href="#header.content-location" id="rfc.xref.header.content-location.2" title="Content-Location">Section&nbsp;3.1.4.2</a>) whose value is the effective Request URI <em class="bcp14">MAY</em> be used to satisfy subsequent GET and HEAD (not POST) requests.
    1454       </p>
    1455       <p id="rfc.section.5.3.3.p.6">Note that POST caching is not widely implemented. However, the <a href="#status.303" class="smpl">303 (See Other)</a> response can be used to direct the user agent to retrieve a cacheable representation of the resource.
    1456       </p>
    1457       <h3 id="rfc.section.5.3.4"><a href="#rfc.section.5.3.4">5.3.4</a>&nbsp;<a id="PUT" href="#PUT">PUT</a></h3>
     1437      <p id="rfc.section.4.3.3.p.4">If a resource has been created on the origin server, the response <em class="bcp14">SHOULD</em> be <a href="#status.201" class="smpl">201 (Created)</a> and contain a representation which describes the status of the request and refers to the new resource, and a <a href="#header.location" class="smpl">Location</a> header field (see <a href="#header.location" id="rfc.xref.header.location.1" title="Location">Section&nbsp;7.1.2</a>).
     1438      </p>
     1439      <p id="rfc.section.4.3.3.p.5">Responses to POST requests are only cacheable when they include explicit freshness information (see <a href="p6-cache.html#calculating.freshness.lifetime" title="Calculating Freshness Lifetime">Section 4.1.1</a> of <a href="#Part6" id="rfc.xref.Part6.5"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>). A cached POST response with a <a href="#header.content-location" class="smpl">Content-Location</a> header field (see <a href="#header.content-location" id="rfc.xref.header.content-location.2" title="Content-Location">Section&nbsp;3.1.4.2</a>) whose value is the effective Request URI <em class="bcp14">MAY</em> be used to satisfy subsequent GET and HEAD (not POST) requests.
     1440      </p>
     1441      <p id="rfc.section.4.3.3.p.6">Note that POST caching is not widely implemented. However, the <a href="#status.303" class="smpl">303 (See Other)</a> response can be used to direct the user agent to retrieve a cacheable representation of the resource.
     1442      </p>
     1443      <h3 id="rfc.section.4.3.4"><a href="#rfc.section.4.3.4">4.3.4</a>&nbsp;<a id="PUT" href="#PUT">PUT</a></h3>
    14581444      <div id="rfc.iref.p.3"></div>
    1459       <p id="rfc.section.5.3.4.p.1">The PUT method requests that the state of the target resource be created or replaced with the state defined by the representation
     1445      <p id="rfc.section.4.3.4.p.1">The PUT method requests that the state of the target resource be created or replaced with the state defined by the representation
    14601446         enclosed in the request message payload. A successful PUT of a given representation would suggest that a subsequent GET on
    14611447         that same target resource will result in an equivalent representation being returned in a <a href="#status.200" class="smpl">200 (OK)</a> response. However, there is no guarantee that such a state change will be observable, since the target resource might be acted
     
    14641450         by the origin server.
    14651451      </p>
    1466       <p id="rfc.section.5.3.4.p.2">If the target resource does not have a current representation and the PUT successfully creates one, then the origin server <em class="bcp14">MUST</em> inform the user agent by sending a <a href="#status.201" class="smpl">201 (Created)</a> response. If the target resource does have a current representation and that representation is successfully modified in accordance
     1452      <p id="rfc.section.4.3.4.p.2">If the target resource does not have a current representation and the PUT successfully creates one, then the origin server <em class="bcp14">MUST</em> inform the user agent by sending a <a href="#status.201" class="smpl">201 (Created)</a> response. If the target resource does have a current representation and that representation is successfully modified in accordance
    14671453         with the state of the enclosed representation, then either a <a href="#status.200" class="smpl">200 (OK)</a> or <a href="#status.204" class="smpl">204 (No Content)</a> response <em class="bcp14">SHOULD</em> be sent to indicate successful completion of the request.
    14681454      </p>
    1469       <p id="rfc.section.5.3.4.p.3">Unrecognized header fields <em class="bcp14">SHOULD</em> be ignored (i.e., not saved as part of the resource state).
    1470       </p>
    1471       <p id="rfc.section.5.3.4.p.4">An origin server <em class="bcp14">SHOULD</em> verify that the PUT representation is consistent with any constraints which the server has for the target resource that cannot
     1455      <p id="rfc.section.4.3.4.p.3">Unrecognized header fields <em class="bcp14">SHOULD</em> be ignored (i.e., not saved as part of the resource state).
     1456      </p>
     1457      <p id="rfc.section.4.3.4.p.4">An origin server <em class="bcp14">SHOULD</em> verify that the PUT representation is consistent with any constraints which the server has for the target resource that cannot
    14721458         or will not be changed by the PUT. This is particularly important when the origin server uses internal configuration information
    14731459         related to the URI in order to set the values for representation metadata on GET responses. When a PUT representation is inconsistent
     
    14751461         appropriate error message containing sufficient information to explain why the representation is unsuitable. The <a href="#status.409" class="smpl">409 (Conflict)</a> or <a href="#status.415" class="smpl">415 (Unsupported Media Type)</a> status codes are suggested, with the latter being specific to constraints on <a href="#header.content-type" class="smpl">Content-Type</a> values.
    14761462      </p>
    1477       <p id="rfc.section.5.3.4.p.5">For example, if the target resource is configured to always have a <a href="#header.content-type" class="smpl">Content-Type</a> of "text/html" and the representation being PUT has a Content-Type of "image/jpeg", then the origin server <em class="bcp14">SHOULD</em> do one of:
     1463      <p id="rfc.section.4.3.4.p.5">For example, if the target resource is configured to always have a <a href="#header.content-type" class="smpl">Content-Type</a> of "text/html" and the representation being PUT has a Content-Type of "image/jpeg", then the origin server <em class="bcp14">SHOULD</em> do one of:
    14781464      </p>
    14791465      <ol class="la">
     
    14861472         </li>
    14871473      </ol>
    1488       <p id="rfc.section.5.3.4.p.6">HTTP does not define exactly how a PUT method affects the state of an origin server beyond what can be expressed by the intent
     1474      <p id="rfc.section.4.3.4.p.6">HTTP does not define exactly how a PUT method affects the state of an origin server beyond what can be expressed by the intent
    14891475         of the user agent request and the semantics of the origin server response. It does not define what a resource might be, in
    14901476         any sense of that word, beyond the interface provided via HTTP. It does not define how resource state is "stored", nor how
     
    14931479         the server.
    14941480      </p>
    1495       <p id="rfc.section.5.3.4.p.7">The fundamental difference between the POST and PUT methods is highlighted by the different intent for the target resource.
     1481      <p id="rfc.section.4.3.4.p.7">The fundamental difference between the POST and PUT methods is highlighted by the different intent for the target resource.
    14961482         The target resource in a POST request is intended to handle the enclosed representation as a data-accepting process, such
    14971483         as for a gateway to some other protocol or a document that accepts annotations. In contrast, the target resource in a PUT
     
    14991485         and visible to intermediaries, even though the exact effect is only known by the origin server.
    15001486      </p>
    1501       <p id="rfc.section.5.3.4.p.8">Proper interpretation of a PUT request presumes that the user agent knows what target resource is desired. A service that
     1487      <p id="rfc.section.4.3.4.p.8">Proper interpretation of a PUT request presumes that the user agent knows what target resource is desired. A service that
    15021488         is intended to select a proper URI on behalf of the client, after receiving a state-changing request, <em class="bcp14">SHOULD</em> be implemented using the POST method rather than PUT. If the origin server will not make the requested PUT state change to
    15031489         the target resource and instead wishes to have it applied to a different resource, such as when the resource has been moved
    15041490         to a different URI, then the origin server <em class="bcp14">MUST</em> send a <a href="#status.301" class="smpl">301 (Moved Permanently)</a> response; the user agent <em class="bcp14">MAY</em> then make its own decision regarding whether or not to redirect the request.
    15051491      </p>
    1506       <p id="rfc.section.5.3.4.p.9">A PUT request applied to the target resource <em class="bcp14">MAY</em> have side-effects on other resources. For example, an article might have a URI for identifying "the current version" (a resource)
     1492      <p id="rfc.section.4.3.4.p.9">A PUT request applied to the target resource <em class="bcp14">MAY</em> have side-effects on other resources. For example, an article might have a URI for identifying "the current version" (a resource)
    15071493         which is separate from the URIs identifying each particular version (different resources that at one point shared the same
    15081494         state as the current version resource). A successful PUT request on "the current version" URI might therefore create a new
     
    15101496         the related resources.
    15111497      </p>
    1512       <p id="rfc.section.5.3.4.p.10">An origin server <em class="bcp14">SHOULD</em> reject any PUT request that contains a <a href="p5-range.html#header.content-range" class="smpl">Content-Range</a> header field (<a href="p5-range.html#header.content-range" title="Content-Range">Section 5.2</a> of <a href="#Part5" id="rfc.xref.Part5.5"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Range Requests">[Part5]</cite></a>), since it might be misinterpreted as partial content (or might be partial content that is being mistakenly PUT as a full
     1498      <p id="rfc.section.4.3.4.p.10">An origin server <em class="bcp14">SHOULD</em> reject any PUT request that contains a <a href="p5-range.html#header.content-range" class="smpl">Content-Range</a> header field (<a href="p5-range.html#header.content-range" title="Content-Range">Section 5.2</a> of <a href="#Part5" id="rfc.xref.Part5.5"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Range Requests">[Part5]</cite></a>), since it might be misinterpreted as partial content (or might be partial content that is being mistakenly PUT as a full
    15131499         representation). Partial content updates are possible by targeting a separately identified resource with state that overlaps
    15141500         a portion of the larger resource, or by using a different method that has been specifically defined for partial updates (for
    15151501         example, the PATCH method defined in <a href="#RFC5789" id="rfc.xref.RFC5789.1"><cite title="PATCH Method for HTTP">[RFC5789]</cite></a>).
    15161502      </p>
    1517       <p id="rfc.section.5.3.4.p.11">Responses to the PUT method are not cacheable. If a PUT request passes through a cache that has one or more stored responses
     1503      <p id="rfc.section.4.3.4.p.11">Responses to the PUT method are not cacheable. If a PUT request passes through a cache that has one or more stored responses
    15181504         for the effective request URI, those stored responses will be invalidated (see <a href="p6-cache.html#invalidation.after.updates.or.deletions" title="Request Methods that Invalidate">Section 6</a> of <a href="#Part6" id="rfc.xref.Part6.6"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>).
    15191505      </p>
    1520       <h3 id="rfc.section.5.3.5"><a href="#rfc.section.5.3.5">5.3.5</a>&nbsp;<a id="DELETE" href="#DELETE">DELETE</a></h3>
     1506      <h3 id="rfc.section.4.3.5"><a href="#rfc.section.4.3.5">4.3.5</a>&nbsp;<a id="DELETE" href="#DELETE">DELETE</a></h3>
    15211507      <div id="rfc.iref.d.2"></div>
    1522       <p id="rfc.section.5.3.5.p.1">The DELETE method requests that the origin server delete the target resource. 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
     1508      <p id="rfc.section.4.3.5.p.1">The DELETE method requests that the origin server delete the target resource. 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
    15231509         has been carried out, even if the status code returned from the origin server indicates that the action has been completed
    15241510         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
    15251511         location.
    15261512      </p>
    1527       <p id="rfc.section.5.3.5.p.2">A successful response <em class="bcp14">SHOULD</em> be <a href="#status.200" class="smpl">200 (OK)</a> if the response includes a representation describing the status, <a href="#status.202" class="smpl">202 (Accepted)</a> if the action has not yet been enacted, or <a href="#status.204" class="smpl">204 (No Content)</a> if the action has been enacted but the response does not include a representation.
    1528       </p>
    1529       <p id="rfc.section.5.3.5.p.3">A payload within a DELETE request message has no defined semantics; sending a payload body on a DELETE request might cause
     1513      <p id="rfc.section.4.3.5.p.2">A successful response <em class="bcp14">SHOULD</em> be <a href="#status.200" class="smpl">200 (OK)</a> if the response includes a representation describing the status, <a href="#status.202" class="smpl">202 (Accepted)</a> if the action has not yet been enacted, or <a href="#status.204" class="smpl">204 (No Content)</a> if the action has been enacted but the response does not include a representation.
     1514      </p>
     1515      <p id="rfc.section.4.3.5.p.3">A payload within a DELETE request message has no defined semantics; sending a payload body on a DELETE request might cause
    15301516         some existing implementations to reject the request.
    15311517      </p>
    1532       <p id="rfc.section.5.3.5.p.4">Responses to the DELETE method are not cacheable. If a DELETE request passes through a cache that has one or more stored responses
     1518      <p id="rfc.section.4.3.5.p.4">Responses to the DELETE method are not cacheable. If a DELETE request passes through a cache that has one or more stored responses
    15331519         for the effective request URI, those stored responses will be invalidated (see <a href="p6-cache.html#invalidation.after.updates.or.deletions" title="Request Methods that Invalidate">Section 6</a> of <a href="#Part6" id="rfc.xref.Part6.7"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>).
    15341520      </p>
    15351521      <div id="rfc.iref.c.9"></div>
    1536       <h3 id="rfc.section.5.3.6"><a href="#rfc.section.5.3.6">5.3.6</a>&nbsp;<a id="CONNECT" href="#CONNECT">CONNECT</a></h3>
    1537       <p id="rfc.section.5.3.6.p.1">The CONNECT method requests that the proxy establish a tunnel to the request-target and, if successful, thereafter restrict
     1522      <h3 id="rfc.section.4.3.6"><a href="#rfc.section.4.3.6">4.3.6</a>&nbsp;<a id="CONNECT" href="#CONNECT">CONNECT</a></h3>
     1523      <p id="rfc.section.4.3.6.p.1">The CONNECT method requests that the proxy establish a tunnel to the request-target and, if successful, thereafter restrict
    15381524         its behavior to blind forwarding of packets until the connection is closed.
    15391525      </p>
    1540       <p id="rfc.section.5.3.6.p.2">When using CONNECT, the request-target <em class="bcp14">MUST</em> use the authority form (<a href="p1-messaging.html#request-target" title="Request Target">Section 5.3</a> of <a href="#Part1" id="rfc.xref.Part1.15"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>); i.e., the request-target consists of only the host name and port number of the tunnel destination, separated by a colon.
     1526      <p id="rfc.section.4.3.6.p.2">When using CONNECT, the request-target <em class="bcp14">MUST</em> use the authority form (<a href="p1-messaging.html#request-target" title="Request Target">Section 5.3</a> of <a href="#Part1" id="rfc.xref.Part1.15"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>); i.e., the request-target consists of only the host name and port number of the tunnel destination, separated by a colon.
    15411527         For example,
    15421528      </p>
    1543       <div id="rfc.figure.u.20"></div><pre class="text2">CONNECT server.example.com:80 HTTP/1.1
     1529      <div id="rfc.figure.u.18"></div><pre class="text2">CONNECT server.example.com:80 HTTP/1.1
    15441530Host: server.example.com:80
    15451531
    1546 </pre><p id="rfc.section.5.3.6.p.4">Any <a href="#status.2xx" class="smpl">2xx (Successful)</a> response to a CONNECT request indicates that the proxy has established a connection to the requested host and port, and has
     1532</pre><p id="rfc.section.4.3.6.p.4">Any <a href="#status.2xx" class="smpl">2xx (Successful)</a> response to a CONNECT request indicates that the proxy has established a connection to the requested host and port, and has
    15471533         switched to tunneling the current connection to that server connection. The tunneled data from the server begins immediately
    15481534         after the blank line that concludes the successful response's header block.
    15491535      </p>
    1550       <p id="rfc.section.5.3.6.p.5">A server <em class="bcp14">SHOULD NOT</em> send any <a href="p1-messaging.html#header.transfer-encoding" class="smpl">Transfer-Encoding</a> or <a href="p1-messaging.html#header.content-length" class="smpl">Content-Length</a> header fields in a successful response. A client <em class="bcp14">MUST</em> ignore any Content-Length or Transfer-Encoding header fields received in a successful response.
    1551       </p>
    1552       <p id="rfc.section.5.3.6.p.6">Any response other than a successful response indicates that the tunnel has not yet been formed and that the connection remains
     1536      <p id="rfc.section.4.3.6.p.5">A server <em class="bcp14">SHOULD NOT</em> send any <a href="p1-messaging.html#header.transfer-encoding" class="smpl">Transfer-Encoding</a> or <a href="p1-messaging.html#header.content-length" class="smpl">Content-Length</a> header fields in a successful response. A client <em class="bcp14">MUST</em> ignore any Content-Length or Transfer-Encoding header fields received in a successful response.
     1537      </p>
     1538      <p id="rfc.section.4.3.6.p.6">Any response other than a successful response indicates that the tunnel has not yet been formed and that the connection remains
    15531539         governed by HTTP.
    15541540      </p>
    1555       <p id="rfc.section.5.3.6.p.7">Proxy authentication might be used to establish the authority to create a tunnel:</p>
    1556       <div id="rfc.figure.u.21"></div><pre class="text2">CONNECT server.example.com:80 HTTP/1.1
     1541      <p id="rfc.section.4.3.6.p.7">Proxy authentication might be used to establish the authority to create a tunnel:</p>
     1542      <div id="rfc.figure.u.19"></div><pre class="text2">CONNECT server.example.com:80 HTTP/1.1
    15571543Host: server.example.com:80
    15581544Proxy-Authorization: basic aGVsbG86d29ybGQ=
    15591545
    1560 </pre><p id="rfc.section.5.3.6.p.9">A payload within a CONNECT request message has no defined semantics; sending a payload body on a CONNECT request might cause
     1546</pre><p id="rfc.section.4.3.6.p.9">A payload within a CONNECT request message has no defined semantics; sending a payload body on a CONNECT request might cause
    15611547         some existing implementations to reject the request.
    15621548      </p>
    1563       <p id="rfc.section.5.3.6.p.10">Similar to a pipelined HTTP/1.1 request, data to be tunneled from client to server <em class="bcp14">MAY</em> be sent immediately after the request (before a response is received). The usual caveats also apply: data can be discarded
     1549      <p id="rfc.section.4.3.6.p.10">Similar to a pipelined HTTP/1.1 request, data to be tunneled from client to server <em class="bcp14">MAY</em> be sent immediately after the request (before a response is received). The usual caveats also apply: data can be discarded
    15641550         if the eventual response is negative, and the connection can be reset with no response if more than one TCP segment is outstanding.
    15651551      </p>
    1566       <p id="rfc.section.5.3.6.p.11">It might be the case that the proxy itself can only reach the requested origin server through another proxy. In this case,
     1552      <p id="rfc.section.4.3.6.p.11">It might be the case that the proxy itself can only reach the requested origin server through another proxy. In this case,
    15671553         the first proxy <em class="bcp14">SHOULD</em> make a CONNECT request of that next proxy, requesting a tunnel to the authority. A proxy <em class="bcp14">MUST NOT</em> respond with any <a href="#status.2xx" class="smpl">2xx</a> status code unless it has either a direct or tunnel connection established to the authority.
    15681554      </p>
    1569       <p id="rfc.section.5.3.6.p.12">If at any point either one of the peers gets disconnected, any outstanding data that came from that peer will be passed to
     1555      <p id="rfc.section.4.3.6.p.12">If at any point either one of the peers gets disconnected, any outstanding data that came from that peer will be passed to
    15701556         the other one, and after that also the other connection will be terminated by the proxy. If there is outstanding data to that
    15711557         peer undelivered, that data will be discarded.
    15721558      </p>
    1573       <p id="rfc.section.5.3.6.p.13">An origin server which receives a CONNECT request for itself <em class="bcp14">MAY</em> respond with a <a href="#status.2xx" class="smpl">2xx</a> status code to indicate that a connection is established. However, most origin servers do not implement CONNECT.
    1574       </p>
    1575       <h3 id="rfc.section.5.3.7"><a href="#rfc.section.5.3.7">5.3.7</a>&nbsp;<a id="OPTIONS" href="#OPTIONS">OPTIONS</a></h3>
     1559      <p id="rfc.section.4.3.6.p.13">An origin server which receives a CONNECT request for itself <em class="bcp14">MAY</em> respond with a <a href="#status.2xx" class="smpl">2xx</a> status code to indicate that a connection is established. However, most origin servers do not implement CONNECT.
     1560      </p>
     1561      <h3 id="rfc.section.4.3.7"><a href="#rfc.section.4.3.7">4.3.7</a>&nbsp;<a id="OPTIONS" href="#OPTIONS">OPTIONS</a></h3>
    15761562      <div id="rfc.iref.o.1"></div>
    1577       <p id="rfc.section.5.3.7.p.1">The OPTIONS method requests information about the communication options available on the request/response chain identified
     1563      <p id="rfc.section.4.3.7.p.1">The OPTIONS method requests information about the communication options available on the request/response chain identified
    15781564         by the effective request URI. This method allows a client to determine the options and/or requirements associated with a resource,
    15791565         or the capabilities of a server, without implying a resource action or initiating a resource retrieval.
    15801566      </p>
    1581       <p id="rfc.section.5.3.7.p.2">Responses to the OPTIONS method are not cacheable.</p>
    1582       <p id="rfc.section.5.3.7.p.3">If the OPTIONS request includes a payload, then the media type <em class="bcp14">MUST</em> be indicated by a <a href="#header.content-type" class="smpl">Content-Type</a> field. Although this specification does not define any use for such a body, future extensions to HTTP might use the OPTIONS
     1567      <p id="rfc.section.4.3.7.p.2">Responses to the OPTIONS method are not cacheable.</p>
     1568      <p id="rfc.section.4.3.7.p.3">If the OPTIONS request includes a payload, then the media type <em class="bcp14">MUST</em> be indicated by a <a href="#header.content-type" class="smpl">Content-Type</a> field. Although this specification does not define any use for such a body, future extensions to HTTP might use the OPTIONS
    15831569         body to make more detailed queries on the server.
    15841570      </p>
    1585       <p id="rfc.section.5.3.7.p.4">If the request-target (<a href="p1-messaging.html#request-target" title="Request Target">Section 5.3</a> of <a href="#Part1" id="rfc.xref.Part1.16"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>) is an asterisk ("*"), the OPTIONS request is intended to apply to the server in general rather than to a specific resource.
     1571      <p id="rfc.section.4.3.7.p.4">If the request-target (<a href="p1-messaging.html#request-target" title="Request Target">Section 5.3</a> of <a href="#Part1" id="rfc.xref.Part1.16"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>) is an asterisk ("*"), the OPTIONS request is intended to apply to the server in general rather than to a specific resource.
    15861572         Since a server's communication options typically depend on the resource, the "*" request is only useful as a "ping" or "no-op"
    15871573         type of method; it does nothing beyond allowing the client to test the capabilities of the server. For example, this can be
    15881574         used to test a proxy for HTTP/1.1 conformance (or lack thereof).
    15891575      </p>
    1590       <p id="rfc.section.5.3.7.p.5">If the request-target is not an asterisk, the OPTIONS request applies only to the options that are available when communicating
     1576      <p id="rfc.section.4.3.7.p.5">If the request-target is not an asterisk, the OPTIONS request applies only to the options that are available when communicating
    15911577         with that resource.
    15921578      </p>
    1593       <p id="rfc.section.5.3.7.p.6">A <a href="#status.200" class="smpl">200 (OK)</a> 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., <a href="#header.allow" class="smpl">Allow</a>), possibly including extensions not defined by this specification. The response payload, if any, <em class="bcp14">SHOULD</em> also include information about the communication options. The format for such a payload is not defined by this specification,
     1579      <p id="rfc.section.4.3.7.p.6">A <a href="#status.200" class="smpl">200 (OK)</a> 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., <a href="#header.allow" class="smpl">Allow</a>), possibly including extensions not defined by this specification. The response payload, if any, <em class="bcp14">SHOULD</em> also include information about the communication options. The format for such a payload is not defined by this specification,
    15941580         but might be defined by future extensions to HTTP. Content negotiation <em class="bcp14">MAY</em> be used to select the appropriate representation. If no payload body is included, the response <em class="bcp14">MUST</em> include a <a href="p1-messaging.html#header.content-length" class="smpl">Content-Length</a> field with a field-value of "0".
    15951581      </p>
    1596       <p id="rfc.section.5.3.7.p.7">The <a href="#header.max-forwards" class="smpl">Max-Forwards</a> header field <em class="bcp14">MAY</em> be used to target a specific proxy in the request chain (see <a href="#header.max-forwards" id="rfc.xref.header.max-forwards.1" title="Max-Forwards">Section&nbsp;6.1.1</a>). If no Max-Forwards field is present in the request, then the forwarded request <em class="bcp14">MUST NOT</em> include a Max-Forwards field.
    1597       </p>
    1598       <h3 id="rfc.section.5.3.8"><a href="#rfc.section.5.3.8">5.3.8</a>&nbsp;<a id="TRACE" href="#TRACE">TRACE</a></h3>
     1582      <p id="rfc.section.4.3.7.p.7">The <a href="#header.max-forwards" class="smpl">Max-Forwards</a> header field <em class="bcp14">MAY</em> be used to target a specific proxy in the request chain (see <a href="#header.max-forwards" id="rfc.xref.header.max-forwards.1" title="Max-Forwards">Section&nbsp;5.1.1</a>). If no Max-Forwards field is present in the request, then the forwarded request <em class="bcp14">MUST NOT</em> include a Max-Forwards field.
     1583      </p>
     1584      <h3 id="rfc.section.4.3.8"><a href="#rfc.section.4.3.8">4.3.8</a>&nbsp;<a id="TRACE" href="#TRACE">TRACE</a></h3>
    15991585      <div id="rfc.iref.t.1"></div>
    1600       <p id="rfc.section.5.3.8.p.1">The TRACE method requests a remote, application-level loop-back of the request message. The final recipient of the request <em class="bcp14">SHOULD</em> reflect the message received back to the client as the message body of a <a href="#status.200" class="smpl">200 (OK)</a> response. The final recipient is either the origin server or the first proxy to receive a <a href="#header.max-forwards" class="smpl">Max-Forwards</a> 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;6.1.1</a>). A TRACE request <em class="bcp14">MUST NOT</em> include a message body.
    1601       </p>
    1602       <p id="rfc.section.5.3.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
     1586      <p id="rfc.section.4.3.8.p.1">The TRACE method requests a remote, application-level loop-back of the request message. The final recipient of the request <em class="bcp14">SHOULD</em> reflect the message received back to the client as the message body of a <a href="#status.200" class="smpl">200 (OK)</a> response. The final recipient is either the origin server or the first proxy to receive a <a href="#header.max-forwards" class="smpl">Max-Forwards</a> 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;5.1.1</a>). A TRACE request <em class="bcp14">MUST NOT</em> include a message body.
     1587      </p>
     1588      <p id="rfc.section.4.3.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
    16031589         or diagnostic information. The value of the <a href="p1-messaging.html#header.via" class="smpl">Via</a> header field (<a href="p1-messaging.html#header.via" title="Via">Section 5.7.1</a> of <a href="#Part1" id="rfc.xref.Part1.17"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>) is of particular interest, since it acts as a trace of the request chain. Use of the <a href="#header.max-forwards" class="smpl">Max-Forwards</a> header field allows the client to limit the length of the request chain, which is useful for testing a chain of proxies forwarding
    16041590         messages in an infinite loop.
    16051591      </p>
    1606       <p id="rfc.section.5.3.8.p.3">If the request is valid, the response <em class="bcp14">SHOULD</em> have a <a href="#header.content-type" class="smpl">Content-Type</a> of "message/http" (see <a href="p1-messaging.html#internet.media.type.message.http" title="Internet Media Type message/http">Section 7.3.1</a> of <a href="#Part1" id="rfc.xref.Part1.18"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>) and contain a message body that encloses a copy of the entire request message. Responses to the TRACE method are not cacheable.
    1607       </p>
    1608       <h1 id="rfc.section.6"><a href="#rfc.section.6">6.</a>&nbsp;<a id="request.header.fields" href="#request.header.fields">Request Header Fields</a></h1>
    1609       <p id="rfc.section.6.p.1">A client sends request header fields to provide more information about the request context, make the request conditional based
     1592      <p id="rfc.section.4.3.8.p.3">If the request is valid, the response <em class="bcp14">SHOULD</em> have a <a href="#header.content-type" class="smpl">Content-Type</a> of "message/http" (see <a href="p1-messaging.html#internet.media.type.message.http" title="Internet Media Type message/http">Section 7.3.1</a> of <a href="#Part1" id="rfc.xref.Part1.18"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>) and contain a message body that encloses a copy of the entire request message. Responses to the TRACE method are not cacheable.
     1593      </p>
     1594      <h1 id="rfc.section.5"><a href="#rfc.section.5">5.</a>&nbsp;<a id="request.header.fields" href="#request.header.fields">Request Header Fields</a></h1>
     1595      <p id="rfc.section.5.p.1">A client sends request header fields to provide more information about the request context, make the request conditional based
    16101596         on the target resource state, suggest preferred formats for the response, supply authentication credentials, or modify the
    16111597         expected request processing. These fields act as request modifiers, similar to the parameters on a programming language method
    16121598         invocation.
    16131599      </p>
    1614       <h2 id="rfc.section.6.1"><a href="#rfc.section.6.1">6.1</a>&nbsp;<a id="request.controls" href="#request.controls">Controls</a></h2>
    1615       <p id="rfc.section.6.1.p.1">Controls are request header fields that direct specific handling of the request.</p>
     1600      <h2 id="rfc.section.5.1"><a href="#rfc.section.5.1">5.1</a>&nbsp;<a id="request.controls" href="#request.controls">Controls</a></h2>
     1601      <p id="rfc.section.5.1.p.1">Controls are request header fields that direct specific handling of the request.</p>
    16161602      <div id="rfc.table.u.3">
    16171603         <table class="tt full left" cellpadding="3" cellspacing="0">
     
    16291615               <tr>
    16301616                  <td class="left">Max-Forwards</td>
    1631                   <td class="left"><a href="#header.max-forwards" id="rfc.xref.header.max-forwards.3" title="Max-Forwards">Section&nbsp;6.1.1</a></td>
     1617                  <td class="left"><a href="#header.max-forwards" id="rfc.xref.header.max-forwards.3" title="Max-Forwards">Section&nbsp;5.1.1</a></td>
    16321618               </tr>
    16331619               <tr>
    16341620                  <td class="left">Expect</td>
    1635                   <td class="left"><a href="#header.expect" id="rfc.xref.header.expect.1" title="Expect">Section&nbsp;6.1.2</a></td>
     1621                  <td class="left"><a href="#header.expect" id="rfc.xref.header.expect.1" title="Expect">Section&nbsp;5.1.2</a></td>
    16361622               </tr>
    16371623               <tr>
     
    16431629      </div>
    16441630      <div id="rfc.iref.m.1"></div>
    1645       <h3 id="rfc.section.6.1.1"><a href="#rfc.section.6.1.1">6.1.1</a>&nbsp;<a id="header.max-forwards" href="#header.max-forwards">Max-Forwards</a></h3>
    1646       <p id="rfc.section.6.1.1.p.1">The "Max-Forwards" header field provides a mechanism with the TRACE (<a href="#TRACE" id="rfc.xref.TRACE.2" title="TRACE">Section&nbsp;5.3.8</a>) and OPTIONS (<a href="#OPTIONS" id="rfc.xref.OPTIONS.2" title="OPTIONS">Section&nbsp;5.3.7</a>) methods to limit the number of times that the request is forwarded by proxies. This can be useful when the client is attempting
     1631      <h3 id="rfc.section.5.1.1"><a href="#rfc.section.5.1.1">5.1.1</a>&nbsp;<a id="header.max-forwards" href="#header.max-forwards">Max-Forwards</a></h3>
     1632      <p id="rfc.section.5.1.1.p.1">The "Max-Forwards" header field provides a mechanism with the TRACE (<a href="#TRACE" id="rfc.xref.TRACE.2" title="TRACE">Section&nbsp;4.3.8</a>) and OPTIONS (<a href="#OPTIONS" id="rfc.xref.OPTIONS.2" title="OPTIONS">Section&nbsp;4.3.7</a>) methods to limit the number of times that the request is forwarded by proxies. This can be useful when the client is attempting
    16471633         to trace a request which appears to be failing or looping mid-chain.
    16481634      </p>
    1649       <div id="rfc.figure.u.22"></div><pre class="inline"><span id="rfc.iref.g.19"></span>  <a href="#header.max-forwards" class="smpl">Max-Forwards</a> = 1*<a href="#imported.abnf" class="smpl">DIGIT</a>
    1650 </pre><p id="rfc.section.6.1.1.p.3">The Max-Forwards value is a decimal integer indicating the remaining number of times this request message can be forwarded.</p>
    1651       <p id="rfc.section.6.1.1.p.4">Each recipient of a TRACE or OPTIONS request containing a Max-Forwards header field <em class="bcp14">MUST</em> check and update its value prior to forwarding the request. If the received value is zero (0), the recipient <em class="bcp14">MUST NOT</em> forward the request; instead, it <em class="bcp14">MUST</em> respond as the final recipient. If the received Max-Forwards value is greater than zero, then the forwarded message <em class="bcp14">MUST</em> contain an updated Max-Forwards field with a value decremented by one (1).
    1652       </p>
    1653       <p id="rfc.section.6.1.1.p.5">The Max-Forwards header field <em class="bcp14">MAY</em> be ignored for all other request methods.
     1635      <div id="rfc.figure.u.20"></div><pre class="inline"><span id="rfc.iref.g.17"></span>  <a href="#header.max-forwards" class="smpl">Max-Forwards</a> = 1*<a href="#imported.abnf" class="smpl">DIGIT</a>
     1636</pre><p id="rfc.section.5.1.1.p.3">The Max-Forwards value is a decimal integer indicating the remaining number of times this request message can be forwarded.</p>
     1637      <p id="rfc.section.5.1.1.p.4">Each recipient of a TRACE or OPTIONS request containing a Max-Forwards header field <em class="bcp14">MUST</em> check and update its value prior to forwarding the request. If the received value is zero (0), the recipient <em class="bcp14">MUST NOT</em> forward the request; instead, it <em class="bcp14">MUST</em> respond as the final recipient. If the received Max-Forwards value is greater than zero, then the forwarded message <em class="bcp14">MUST</em> contain an updated Max-Forwards field with a value decremented by one (1).
     1638      </p>
     1639      <p id="rfc.section.5.1.1.p.5">The Max-Forwards header field <em class="bcp14">MAY</em> be ignored for all other request methods.
    16541640      </p>
    16551641      <div id="rfc.iref.e.1"></div>
    1656       <h3 id="rfc.section.6.1.2"><a href="#rfc.section.6.1.2">6.1.2</a>&nbsp;<a id="header.expect" href="#header.expect">Expect</a></h3>
    1657       <p id="rfc.section.6.1.2.p.1">The "Expect" header field is used to indicate that particular server behaviors are required by the client.</p>
    1658       <div id="rfc.figure.u.23"></div><pre class="inline"><span id="rfc.iref.g.20"></span><span id="rfc.iref.g.21"></span><span id="rfc.iref.g.22"></span><span id="rfc.iref.g.23"></span><span id="rfc.iref.g.24"></span>  <a href="#header.expect" class="smpl">Expect</a>       = 1#<a href="#header.expect" class="smpl">expectation</a>
     1642      <h3 id="rfc.section.5.1.2"><a href="#rfc.section.5.1.2">5.1.2</a>&nbsp;<a id="header.expect" href="#header.expect">Expect</a></h3>
     1643      <p id="rfc.section.5.1.2.p.1">The "Expect" header field is used to indicate that particular server behaviors are required by the client.</p>
     1644      <div id="rfc.figure.u.21"></div><pre class="inline"><span id="rfc.iref.g.18"></span><span id="rfc.iref.g.19"></span><span id="rfc.iref.g.20"></span><span id="rfc.iref.g.21"></span><span id="rfc.iref.g.22"></span>  <a href="#header.expect" class="smpl">Expect</a>       = 1#<a href="#header.expect" class="smpl">expectation</a>
    16591645 
    16601646  <a href="#header.expect" class="smpl">expectation</a>  = <a href="#header.expect" class="smpl">expect-name</a> [ <a href="#imported.abnf" class="smpl">BWS</a> "=" <a href="#imported.abnf" class="smpl">BWS</a> <a href="#header.expect" class="smpl">expect-value</a> ]
     
    16641650  <a href="#header.expect" class="smpl">expect-name</a>  = <a href="#imported.abnf" class="smpl">token</a>
    16651651  <a href="#header.expect" class="smpl">expect-value</a> = <a href="#imported.abnf" class="smpl">token</a> / <a href="#imported.abnf" class="smpl">quoted-string</a>
    1666 </pre><p id="rfc.section.6.1.2.p.3">If all received Expect header field(s) are syntactically valid but contain an expectation that the recipient does not understand
     1652</pre><p id="rfc.section.5.1.2.p.3">If all received Expect header field(s) are syntactically valid but contain an expectation that the recipient does not understand
    16671653         or cannot comply with, the recipient <em class="bcp14">MUST</em> respond with a <a href="#status.417" class="smpl">417 (Expectation Failed)</a> status code. A recipient of a syntactically invalid Expectation header field <em class="bcp14">MUST</em> respond with a <a href="#status.4xx" class="smpl">4xx</a> status code other than 417.
    16681654      </p>
    1669       <p id="rfc.section.6.1.2.p.4">The only expectation defined by this specification is:</p>
    1670       <p id="rfc.section.6.1.2.p.5"><span id="rfc.iref.48"></span><span id="rfc.iref.e.2"></span> 100-continue
     1655      <p id="rfc.section.5.1.2.p.4">The only expectation defined by this specification is:</p>
     1656      <p id="rfc.section.5.1.2.p.5"><span id="rfc.iref.46"></span><span id="rfc.iref.e.2"></span> 100-continue
    16711657      </p>
    16721658      <ul class="empty">
    16731659         <li>The "100-continue" expectation is defined below. It does not support any expect-params.</li>
    16741660      </ul>
    1675       <p id="rfc.section.6.1.2.p.6">Comparison is case-insensitive for names (expect-name), and case-sensitive for values (expect-value).</p>
    1676       <p id="rfc.section.6.1.2.p.7">The Expect mechanism is hop-by-hop: the above requirements apply to any server, including proxies. However, the Expect header
     1661      <p id="rfc.section.5.1.2.p.6">Comparison is case-insensitive for names (expect-name), and case-sensitive for values (expect-value).</p>
     1662      <p id="rfc.section.5.1.2.p.7">The Expect mechanism is hop-by-hop: the above requirements apply to any server, including proxies. However, the Expect header
    16771663         field itself is end-to-end; it <em class="bcp14">MUST</em> be forwarded if the request is forwarded.
    16781664      </p>
    1679       <p id="rfc.section.6.1.2.p.8">Many older HTTP/1.0 and HTTP/1.1 applications do not understand the Expect header field.</p>
    1680       <h4 id="rfc.section.6.1.2.1"><a href="#rfc.section.6.1.2.1">6.1.2.1</a>&nbsp;<a id="use.of.the.100.status" href="#use.of.the.100.status">Use of the 100 (Continue) Status</a></h4>
    1681       <p id="rfc.section.6.1.2.1.p.1">The purpose of the <a href="#status.100" class="smpl">100 (Continue)</a> status code (<a href="#status.100" id="rfc.xref.status.100.1" title="100 Continue">Section&nbsp;7.2.1</a>) is to allow a client that is sending a request message with a payload to determine if the origin server is willing to accept
     1665      <p id="rfc.section.5.1.2.p.8">Many older HTTP/1.0 and HTTP/1.1 applications do not understand the Expect header field.</p>
     1666      <h4 id="rfc.section.5.1.2.1"><a href="#rfc.section.5.1.2.1">5.1.2.1</a>&nbsp;<a id="use.of.the.100.status" href="#use.of.the.100.status">Use of the 100 (Continue) Status</a></h4>
     1667      <p id="rfc.section.5.1.2.1.p.1">The purpose of the <a href="#status.100" class="smpl">100 (Continue)</a> status code (<a href="#status.100" id="rfc.xref.status.100.1" title="100 Continue">Section&nbsp;6.2.1</a>) is to allow a client that is sending a request message with a payload to determine if the origin server is willing to accept
    16821668         the request (based on the request header fields) before the client sends the payload body. In some cases, it might either
    16831669         be inappropriate or highly inefficient for the client to send the payload body if the server will reject the message without
    16841670         looking at the body.
    16851671      </p>
    1686       <p id="rfc.section.6.1.2.1.p.2">Requirements for HTTP/1.1 clients: </p>
     1672      <p id="rfc.section.5.1.2.1.p.2">Requirements for HTTP/1.1 clients: </p>
    16871673      <ul>
    16881674         <li>If a client will wait for a <a href="#status.100" class="smpl">100 (Continue)</a> response before sending the payload body, it <em class="bcp14">MUST</em> send an <a href="#header.expect" class="smpl">Expect</a> header field with the "100-continue" expectation.
     
    16911677         </li>
    16921678      </ul>
    1693       <p id="rfc.section.6.1.2.1.p.3">Because of the presence of older implementations, the protocol allows ambiguous situations in which a client might send "Expect:
     1679      <p id="rfc.section.5.1.2.1.p.3">Because of the presence of older implementations, the protocol allows ambiguous situations in which a client might send "Expect:
    16941680         100-continue" without receiving either a <a href="#status.417" class="smpl">417 (Expectation Failed)</a> or a <a href="#status.100" class="smpl">100 (Continue)</a> status code. Therefore, when a client sends this header field to an origin server (possibly via a proxy) from which it has
    16951681         never seen a <a href="#status.100" class="smpl">100 (Continue)</a> status code, the client <em class="bcp14">SHOULD NOT</em> wait for an indefinite period before sending the payload body.
    16961682      </p>
    1697       <p id="rfc.section.6.1.2.1.p.4">Requirements for HTTP/1.1 origin servers: </p>
     1683      <p id="rfc.section.5.1.2.1.p.4">Requirements for HTTP/1.1 origin servers: </p>
    16981684      <ul>
    16991685         <li>Upon receiving a request which includes an <a href="#header.expect" class="smpl">Expect</a> header field with the "100-continue" expectation, an origin server <em class="bcp14">MUST</em> either respond with <a href="#status.100" class="smpl">100 (Continue)</a> status code and continue to read from the input stream, or respond with a final status code. The origin server <em class="bcp14">MUST NOT</em> wait for the payload body before sending the <a href="#status.100" class="smpl">100 (Continue)</a> response. If it responds with a final status code, it <em class="bcp14">MAY</em> close the transport connection or it <em class="bcp14">MAY</em> continue to read and discard the rest of the request. It <em class="bcp14">MUST NOT</em> perform the request method if it returns a final status code.
     
    17151701         </li>
    17161702      </ul>
    1717       <p id="rfc.section.6.1.2.1.p.5">Requirements for HTTP/1.1 proxies: </p>
     1703      <p id="rfc.section.5.1.2.1.p.5">Requirements for HTTP/1.1 proxies: </p>
    17181704      <ul>
    17191705         <li>If a proxy receives a request that includes an <a href="#header.expect" class="smpl">Expect</a> header field with the "100-continue" expectation, and the proxy either knows that the next-hop server complies with HTTP/1.1
     
    17241710         <li>Proxies <em class="bcp14">SHOULD</em> maintain a record of the HTTP version numbers received from recently-referenced next-hop servers.
    17251711         </li>
    1726          <li>A proxy <em class="bcp14">MUST NOT</em> forward a <a href="#status.100" class="smpl">100 (Continue)</a> response if the request message was received from an HTTP/1.0 (or earlier) client and did not include an <a href="#header.expect" class="smpl">Expect</a> header field with the "100-continue" expectation. This requirement overrides the general rule for forwarding of <a href="#status.1xx" class="smpl">1xx</a> responses (see <a href="#status.100" id="rfc.xref.status.100.2" title="100 Continue">Section&nbsp;7.2.1</a>).
     1712         <li>A proxy <em class="bcp14">MUST NOT</em> forward a <a href="#status.100" class="smpl">100 (Continue)</a> response if the request message was received from an HTTP/1.0 (or earlier) client and did not include an <a href="#header.expect" class="smpl">Expect</a> header field with the "100-continue" expectation. This requirement overrides the general rule for forwarding of <a href="#status.1xx" class="smpl">1xx</a> responses (see <a href="#status.100" id="rfc.xref.status.100.2" title="100 Continue">Section&nbsp;6.2.1</a>).
    17271713         </li>
    17281714      </ul>
    1729       <h2 id="rfc.section.6.2"><a href="#rfc.section.6.2">6.2</a>&nbsp;<a id="request.conditionals" href="#request.conditionals">Conditionals</a></h2>
    1730       <p id="rfc.section.6.2.p.1">Conditionals are request header fields that indicate a precondition to be tested before applying the method semantics to the
     1715      <h2 id="rfc.section.5.2"><a href="#rfc.section.5.2">5.2</a>&nbsp;<a id="request.conditionals" href="#request.conditionals">Conditionals</a></h2>
     1716      <p id="rfc.section.5.2.p.1">Conditionals are request header fields that indicate a precondition to be tested before applying the method semantics to the
    17311717         target resource. Each precondition is based on metadata that is expected to change if the selected representation of the target
    17321718         resource is changed. The HTTP/1.1 conditional request mechanisms are defined in <a href="#Part4" id="rfc.xref.Part4.2"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests">[Part4]</cite></a>.
     
    17641750         </table>
    17651751      </div>
    1766       <h2 id="rfc.section.6.3"><a href="#rfc.section.6.3">6.3</a>&nbsp;<a id="request.conneg" href="#request.conneg">Content Negotiation</a></h2>
     1752      <h2 id="rfc.section.5.3"><a href="#rfc.section.5.3">5.3</a>&nbsp;<a id="request.conneg" href="#request.conneg">Content Negotiation</a></h2>
    17671753      <div id="rfc.table.u.5">
    17681754         <table class="tt full left" cellpadding="3" cellspacing="0">
     
    17761762               <tr>
    17771763                  <td class="left">Accept</td>
    1778                   <td class="left"><a href="#header.accept" id="rfc.xref.header.accept.2" title="Accept">Section&nbsp;6.3.2</a></td>
     1764                  <td class="left"><a href="#header.accept" id="rfc.xref.header.accept.2" title="Accept">Section&nbsp;5.3.2</a></td>
    17791765               </tr>
    17801766               <tr>
    17811767                  <td class="left">Accept-Charset</td>
    1782                   <td class="left"><a href="#header.accept-charset" id="rfc.xref.header.accept-charset.1" title="Accept-Charset">Section&nbsp;6.3.3</a></td>
     1768                  <td class="left"><a href="#header.accept-charset" id="rfc.xref.header.accept-charset.1" title="Accept-Charset">Section&nbsp;5.3.3</a></td>
    17831769               </tr>
    17841770               <tr>
    17851771                  <td class="left">Accept-Encoding</td>
    1786                   <td class="left"><a href="#header.accept-encoding" id="rfc.xref.header.accept-encoding.2" title="Accept-Encoding">Section&nbsp;6.3.4</a></td>
     1772                  <td class="left"><a href="#header.accept-encoding" id="rfc.xref.header.accept-encoding.2" title="Accept-Encoding">Section&nbsp;5.3.4</a></td>
    17871773               </tr>
    17881774               <tr>
    17891775                  <td class="left">Accept-Language</td>
    1790                   <td class="left"><a href="#header.accept-language" id="rfc.xref.header.accept-language.1" title="Accept-Language">Section&nbsp;6.3.5</a></td>
     1776                  <td class="left"><a href="#header.accept-language" id="rfc.xref.header.accept-language.1" title="Accept-Language">Section&nbsp;5.3.5</a></td>
    17911777               </tr>
    17921778            </tbody>
    17931779         </table>
    17941780      </div>
    1795       <h3 id="rfc.section.6.3.1"><a href="#rfc.section.6.3.1">6.3.1</a>&nbsp;<a id="quality.values" href="#quality.values">Quality Values</a></h3>
    1796       <p id="rfc.section.6.3.1.p.1">Many of the request header fields for proactive content negotiation use a common parameter, named "q" (case-insensitive),
     1781      <h3 id="rfc.section.5.3.1"><a href="#rfc.section.5.3.1">5.3.1</a>&nbsp;<a id="quality.values" href="#quality.values">Quality Values</a></h3>
     1782      <p id="rfc.section.5.3.1.p.1">Many of the request header fields for proactive content negotiation use a common parameter, named "q" (case-insensitive),
    17971783         to assign a relative "weight" to the preference for that associated kind of content. This weight is referred to as a "quality
    17981784         value" (or "qvalue") because the same parameter name is often used within server configurations to assign a weight to the
    17991785         relative quality of the various representations that can be selected for a resource.
    18001786      </p>
    1801       <p id="rfc.section.6.3.1.p.2">The weight is normalized to a real number in the range 0 through 1, where 0.001 is the least preferred and 1 is the most preferred;
     1787      <p id="rfc.section.5.3.1.p.2">The weight is normalized to a real number in the range 0 through 1, where 0.001 is the least preferred and 1 is the most preferred;
    18021788         a value of 0 means "not acceptable". If no "q" parameter is present, the default weight is 1.
    18031789      </p>
    1804       <div id="rfc.figure.u.24"></div><pre class="inline"><span id="rfc.iref.g.25"></span><span id="rfc.iref.g.26"></span>  <a href="#quality.values" class="smpl">weight</a> = <a href="#imported.abnf" class="smpl">OWS</a> ";" <a href="#imported.abnf" class="smpl">OWS</a> "q=" <a href="#quality.values" class="smpl">qvalue</a>
     1790      <div id="rfc.figure.u.22"></div><pre class="inline"><span id="rfc.iref.g.23"></span><span id="rfc.iref.g.24"></span>  <a href="#quality.values" class="smpl">weight</a> = <a href="#imported.abnf" class="smpl">OWS</a> ";" <a href="#imported.abnf" class="smpl">OWS</a> "q=" <a href="#quality.values" class="smpl">qvalue</a>
    18051791  <a href="#quality.values" class="smpl">qvalue</a> = ( "0" [ "." 0*3<a href="#imported.abnf" class="smpl">DIGIT</a> ] )
    18061792         / ( "1" [ "." 0*3("0") ] )
    1807 </pre><p id="rfc.section.6.3.1.p.4">A sender of qvalue <em class="bcp14">MUST NOT</em> generate more than three digits after the decimal point. User configuration of these values ought to be limited in the same
     1793</pre><p id="rfc.section.5.3.1.p.4">A sender of qvalue <em class="bcp14">MUST NOT</em> generate more than three digits after the decimal point. User configuration of these values ought to be limited in the same
    18081794         fashion.
    18091795      </p>
    18101796      <div id="rfc.iref.a.1"></div>
    1811       <h3 id="rfc.section.6.3.2"><a href="#rfc.section.6.3.2">6.3.2</a>&nbsp;<a id="header.accept" href="#header.accept">Accept</a></h3>
    1812       <p id="rfc.section.6.3.2.p.1">The "Accept" header field can be used by user agents to specify response media types that are acceptable. Accept header fields
     1797      <h3 id="rfc.section.5.3.2"><a href="#rfc.section.5.3.2">5.3.2</a>&nbsp;<a id="header.accept" href="#header.accept">Accept</a></h3>
     1798      <p id="rfc.section.5.3.2.p.1">The "Accept" header field can be used by user agents to specify response media types that are acceptable. Accept header fields
    18131799         can be used to indicate that the request is specifically limited to a small set of desired types, as in the case of a request
    18141800         for an in-line image.
    18151801      </p>
    1816       <div id="rfc.figure.u.25"></div><pre class="inline"><span id="rfc.iref.g.27"></span><span id="rfc.iref.g.28"></span><span id="rfc.iref.g.29"></span><span id="rfc.iref.g.30"></span>  <a href="#header.accept" class="smpl">Accept</a> = #( <a href="#header.accept" class="smpl">media-range</a> [ <a href="#header.accept" class="smpl">accept-params</a> ] )
     1802      <div id="rfc.figure.u.23"></div><pre class="inline"><span id="rfc.iref.g.25"></span><span id="rfc.iref.g.26"></span><span id="rfc.iref.g.27"></span><span id="rfc.iref.g.28"></span>  <a href="#header.accept" class="smpl">Accept</a> = #( <a href="#header.accept" class="smpl">media-range</a> [ <a href="#header.accept" class="smpl">accept-params</a> ] )
    18171803 
    18181804  <a href="#header.accept" class="smpl">media-range</a>    = ( "*/*"
     
    18221808  <a href="#header.accept" class="smpl">accept-params</a>  = <a href="#quality.values" class="smpl">weight</a> *( <a href="#header.accept" class="smpl">accept-ext</a> )
    18231809  <a href="#header.accept" class="smpl">accept-ext</a>     = <a href="#imported.abnf" class="smpl">OWS</a> ";" <a href="#imported.abnf" class="smpl">OWS</a> <a href="#imported.abnf" class="smpl">token</a> [ "=" <a href="#imported.abnf" class="smpl">word</a> ]
    1824 </pre><p id="rfc.section.6.3.2.p.3">The asterisk "*" character is used to group media types into ranges, with "*/*" indicating all media types and "type/*" indicating
     1810</pre><p id="rfc.section.5.3.2.p.3">The asterisk "*" character is used to group media types into ranges, with "*/*" indicating all media types and "type/*" indicating
    18251811         all subtypes of that type. The media-range <em class="bcp14">MAY</em> include media type parameters that are applicable to that range.
    18261812      </p>
    1827       <p id="rfc.section.6.3.2.p.4">Each media-range <em class="bcp14">MAY</em> be followed by one or more accept-params, beginning with the "q" parameter for indicating a relative weight, as defined in <a href="#quality.values" title="Quality Values">Section&nbsp;6.3.1</a>. The first "q" parameter (if any) separates the media-range parameter(s) from the accept-params.
    1828       </p>
    1829       <div class="note" id="rfc.section.6.3.2.p.5">
     1813      <p id="rfc.section.5.3.2.p.4">Each media-range <em class="bcp14">MAY</em> be followed by one or more accept-params, beginning with the "q" parameter for indicating a relative weight, as defined in <a href="#quality.values" title="Quality Values">Section&nbsp;5.3.1</a>. The first "q" parameter (if any) separates the media-range parameter(s) from the accept-params.
     1814      </p>
     1815      <div class="note" id="rfc.section.5.3.2.p.5">
    18301816         <p> <b>Note:</b> Use of the "q" parameter name to separate media type parameters from Accept extension parameters is due to historical practice.
    18311817            Although this prevents any media type parameter named "q" from being used with a media range, such an event is believed to
     
    18341820         </p>
    18351821      </div>
    1836       <p id="rfc.section.6.3.2.p.6">The example</p>
    1837       <div id="rfc.figure.u.26"></div><pre class="text">  Accept: audio/*; q=0.2, audio/basic
    1838 </pre><p id="rfc.section.6.3.2.p.8"> <em class="bcp14">SHOULD</em> be interpreted as "I prefer audio/basic, but send me any audio type if it is the best available after an 80% mark-down in
     1822      <p id="rfc.section.5.3.2.p.6">The example</p>
     1823      <div id="rfc.figure.u.24"></div><pre class="text">  Accept: audio/*; q=0.2, audio/basic
     1824</pre><p id="rfc.section.5.3.2.p.8"> <em class="bcp14">SHOULD</em> be interpreted as "I prefer audio/basic, but send me any audio type if it is the best available after an 80% mark-down in
    18391825         quality".
    18401826      </p>
    1841       <p id="rfc.section.6.3.2.p.9">A request without any Accept header field implies that the user agent will accept any media type in response. If an Accept
     1827      <p id="rfc.section.5.3.2.p.9">A request without any Accept header field implies that the user agent will accept any media type in response. If an Accept
    18421828         header field is present in a request and none of the available representations for the response have a media type that is
    18431829         listed as acceptable, the origin server <em class="bcp14">MAY</em> either honor the Accept header field by sending a <a href="#status.406" class="smpl">406 (Not Acceptable)</a> response or disregard the Accept header field by treating the response as if it is not subject to content negotiation.
    18441830      </p>
    1845       <p id="rfc.section.6.3.2.p.10">A more elaborate example is</p>
    1846       <div id="rfc.figure.u.27"></div><pre class="text">  Accept: text/plain; q=0.5, text/html,
     1831      <p id="rfc.section.5.3.2.p.10">A more elaborate example is</p>
     1832      <div id="rfc.figure.u.25"></div><pre class="text">  Accept: text/plain; q=0.5, text/html,
    18471833          text/x-dvi; q=0.8, text/x-c
    1848 </pre><p id="rfc.section.6.3.2.p.12">Verbally, this would be interpreted as "text/html and text/x-c are the equally preferred media types, but if they do not exist,
     1834</pre><p id="rfc.section.5.3.2.p.12">Verbally, this would be interpreted as "text/html and text/x-c are the equally preferred media types, but if they do not exist,
    18491835         then send the text/x-dvi representation, and if that does not exist, send the text/plain representation".
    18501836      </p>
    1851       <p id="rfc.section.6.3.2.p.13">Media ranges can be overridden by more specific media ranges or specific media types. If more than one media range applies
     1837      <p id="rfc.section.5.3.2.p.13">Media ranges can be overridden by more specific media ranges or specific media types. If more than one media range applies
    18521838         to a given type, the most specific reference has precedence. For example,
    18531839      </p>
    1854       <div id="rfc.figure.u.28"></div><pre class="text">  Accept: text/*, text/plain, text/plain;format=flowed, */*
    1855 </pre><p id="rfc.section.6.3.2.p.15">have the following precedence: </p>
     1840      <div id="rfc.figure.u.26"></div><pre class="text">  Accept: text/*, text/plain, text/plain;format=flowed, */*
     1841</pre><p id="rfc.section.5.3.2.p.15">have the following precedence: </p>
    18561842      <ol>
    18571843         <li>text/plain;format=flowed</li>
     
    18601846         <li>*/*</li>
    18611847      </ol>
    1862       <p id="rfc.section.6.3.2.p.16">The media type quality factor associated with a given type is determined by finding the media range with the highest precedence
     1848      <p id="rfc.section.5.3.2.p.16">The media type quality factor associated with a given type is determined by finding the media range with the highest precedence
    18631849         which matches that type. For example,
    18641850      </p>
    1865       <div id="rfc.figure.u.29"></div><pre class="text">  Accept: text/*;q=0.3, text/html;q=0.7, text/html;level=1,
     1851      <div id="rfc.figure.u.27"></div><pre class="text">  Accept: text/*;q=0.3, text/html;q=0.7, text/html;level=1,
    18661852          text/html;level=2;q=0.4, */*;q=0.5
    1867 </pre><p id="rfc.section.6.3.2.p.18">would cause the following values to be associated:</p>
     1853</pre><p id="rfc.section.5.3.2.p.18">would cause the following values to be associated:</p>
    18681854      <div id="rfc.table.u.6">
    18691855         <table class="tt full left" cellpadding="3" cellspacing="0">
     
    19021888         </table>
    19031889      </div>
    1904       <p id="rfc.section.6.3.2.p.19"> <b>Note:</b> A user agent might be provided with a default set of quality values for certain media ranges. However, unless the user agent
     1890      <p id="rfc.section.5.3.2.p.19"> <b>Note:</b> A user agent might be provided with a default set of quality values for certain media ranges. However, unless the user agent
    19051891         is a closed system which cannot interact with other rendering agents, this default set ought to be configurable by the user.
    19061892      </p>
    19071893      <div id="rfc.iref.a.2"></div>
    1908       <h3 id="rfc.section.6.3.3"><a href="#rfc.section.6.3.3">6.3.3</a>&nbsp;<a id="header.accept-charset" href="#header.accept-charset">Accept-Charset</a></h3>
    1909       <p id="rfc.section.6.3.3.p.1">The "Accept-Charset" header field can be sent by a user agent to indicate what charsets are acceptable in a selected representation.
     1894      <h3 id="rfc.section.5.3.3"><a href="#rfc.section.5.3.3">5.3.3</a>&nbsp;<a id="header.accept-charset" href="#header.accept-charset">Accept-Charset</a></h3>
     1895      <p id="rfc.section.5.3.3.p.1">The "Accept-Charset" header field can be sent by a user agent to indicate what charsets are acceptable in a selected representation.
    19101896         This field allows user agents capable of understanding more comprehensive or special-purpose charsets to signal that capability
    19111897         to an origin server which is capable of representing documents in those charsets.
    19121898      </p>
    1913       <div id="rfc.figure.u.30"></div><pre class="inline"><span id="rfc.iref.g.31"></span>  <a href="#header.accept-charset" class="smpl">Accept-Charset</a> = 1#( ( <a href="#charset" class="smpl">charset</a> / "*" ) [ <a href="#quality.values" class="smpl">weight</a> ] )
    1914 </pre><p id="rfc.section.6.3.3.p.3">Charset names are defined in <a href="#charset" title="Charset">Section&nbsp;3.1.1.2</a>. A user agent <em class="bcp14">MAY</em> associate a quality value with each charset to indicate the user's relative preference for that charset, as defined in <a href="#quality.values" title="Quality Values">Section&nbsp;6.3.1</a>. An example is
    1915       </p>
    1916       <div id="rfc.figure.u.31"></div><pre class="text">  Accept-Charset: iso-8859-5, unicode-1-1;q=0.8
    1917 </pre><p id="rfc.section.6.3.3.p.5">The special value "*", if present in the Accept-Charset field, matches every charset which is not mentioned elsewhere in the
     1899      <div id="rfc.figure.u.28"></div><pre class="inline"><span id="rfc.iref.g.29"></span>  <a href="#header.accept-charset" class="smpl">Accept-Charset</a> = 1#( ( <a href="#charset" class="smpl">charset</a> / "*" ) [ <a href="#quality.values" class="smpl">weight</a> ] )
     1900</pre><p id="rfc.section.5.3.3.p.3">Charset names are defined in <a href="#charset" title="Charset">Section&nbsp;3.1.1.2</a>. A user agent <em class="bcp14">MAY</em> associate a quality value with each charset to indicate the user's relative preference for that charset, as defined in <a href="#quality.values" title="Quality Values">Section&nbsp;5.3.1</a>. An example is
     1901      </p>
     1902      <div id="rfc.figure.u.29"></div><pre class="text">  Accept-Charset: iso-8859-5, unicode-1-1;q=0.8
     1903</pre><p id="rfc.section.5.3.3.p.5">The special value "*", if present in the Accept-Charset field, matches every charset which is not mentioned elsewhere in the
    19181904         Accept-Charset field. If no "*" is present in an Accept-Charset field, then any charsets not explicitly mentioned in the field
    19191905         are considered "not acceptable" to the client.
    19201906      </p>
    1921       <p id="rfc.section.6.3.3.p.6">A request without any Accept-Charset header field implies that the user agent will accept any charset in response. Most general-purpose
     1907      <p id="rfc.section.5.3.3.p.6">A request without any Accept-Charset header field implies that the user agent will accept any charset in response. Most general-purpose
    19221908         user agents do not send Accept-Charset, unless specifically configured to do so, because a detailed list of supported charsets
    19231909         makes it easier for a server to identify an individual by virtue of the user agent's request characteristics (a.k.a., fingerprinting).
    19241910      </p>
    1925       <p id="rfc.section.6.3.3.p.7">If an Accept-Charset header field is present in a request and none of the available representations for the response has a
     1911      <p id="rfc.section.5.3.3.p.7">If an Accept-Charset header field is present in a request and none of the available representations for the response has a
    19261912         charset that is listed as acceptable, the origin server <em class="bcp14">MAY</em> either honor the Accept-Charset header field, by sending a <a href="#status.406" class="smpl">406 (Not Acceptable)</a> response, or disregard the Accept-Charset header field by treating the resource as if it is not subject to content negotiation.
    19271913      </p>
    19281914      <div id="rfc.iref.a.3"></div>
    1929       <h3 id="rfc.section.6.3.4"><a href="#rfc.section.6.3.4">6.3.4</a>&nbsp;<a id="header.accept-encoding" href="#header.accept-encoding">Accept-Encoding</a></h3>
    1930       <p id="rfc.section.6.3.4.p.1">The "Accept-Encoding" header field can be used by user agents to indicate what response content-codings (<a href="#content.codings" title="Content Codings">Section&nbsp;3.1.2.1</a>) are acceptable in the response. An "identity" token is used as a synonym for "no encoding" in order to communicate when
     1915      <h3 id="rfc.section.5.3.4"><a href="#rfc.section.5.3.4">5.3.4</a>&nbsp;<a id="header.accept-encoding" href="#header.accept-encoding">Accept-Encoding</a></h3>
     1916      <p id="rfc.section.5.3.4.p.1">The "Accept-Encoding" header field can be used by user agents to indicate what response content-codings (<a href="#content.codings" title="Content Codings">Section&nbsp;3.1.2.1</a>) are acceptable in the response. An "identity" token is used as a synonym for "no encoding" in order to communicate when
    19311917         no encoding is preferred.
    19321918      </p>
    1933       <div id="rfc.figure.u.32"></div><pre class="inline"><span id="rfc.iref.g.32"></span><span id="rfc.iref.g.33"></span>  <a href="#header.accept-encoding" class="smpl">Accept-Encoding</a>  = #( <a href="#header.accept-encoding" class="smpl">codings</a> [ <a href="#quality.values" class="smpl">weight</a> ] )
     1919      <div id="rfc.figure.u.30"></div><pre class="inline"><span id="rfc.iref.g.30"></span><span id="rfc.iref.g.31"></span>  <a href="#header.accept-encoding" class="smpl">Accept-Encoding</a>  = #( <a href="#header.accept-encoding" class="smpl">codings</a> [ <a href="#quality.values" class="smpl">weight</a> ] )
    19341920  <a href="#header.accept-encoding" class="smpl">codings</a>          = <a href="#content.codings" class="smpl">content-coding</a> / "identity" / "*"
    1935 </pre><p id="rfc.section.6.3.4.p.3">Each codings value <em class="bcp14">MAY</em> be given an associated quality value which represents the preference for that encoding, as defined in <a href="#quality.values" title="Quality Values">Section&nbsp;6.3.1</a>.
    1936       </p>
    1937       <p id="rfc.section.6.3.4.p.4">For example,</p>
    1938       <div id="rfc.figure.u.33"></div><pre class="text">  Accept-Encoding: compress, gzip
     1921</pre><p id="rfc.section.5.3.4.p.3">Each codings value <em class="bcp14">MAY</em> be given an associated quality value which represents the preference for that encoding, as defined in <a href="#quality.values" title="Quality Values">Section&nbsp;5.3.1</a>.
     1922      </p>
     1923      <p id="rfc.section.5.3.4.p.4">For example,</p>
     1924      <div id="rfc.figure.u.31"></div><pre class="text">  Accept-Encoding: compress, gzip
    19391925  Accept-Encoding:
    19401926  Accept-Encoding: *
    19411927  Accept-Encoding: compress;q=0.5, gzip;q=1.0
    19421928  Accept-Encoding: gzip;q=1.0, identity; q=0.5, *;q=0
    1943 </pre><p id="rfc.section.6.3.4.p.6">A server tests whether a content-coding for a given representation is acceptable, according to an Accept-Encoding field, using
     1929</pre><p id="rfc.section.5.3.4.p.6">A server tests whether a content-coding for a given representation is acceptable, according to an Accept-Encoding field, using
    19441930         these rules:
    19451931      </p>
     
    19521938         </li>
    19531939         <li>If the representation's content-coding is one of the content-codings listed in the Accept-Encoding field, then it is acceptable
    1954             unless it is accompanied by a qvalue of 0. (As defined in <a href="#quality.values" title="Quality Values">Section&nbsp;6.3.1</a>, a qvalue of 0 means "not acceptable".)
     1940            unless it is accompanied by a qvalue of 0. (As defined in <a href="#quality.values" title="Quality Values">Section&nbsp;5.3.1</a>, a qvalue of 0 means "not acceptable".)
    19551941         </li>
    19561942         <li>If multiple content-codings are acceptable, then the acceptable content-coding with the highest non-zero qvalue is preferred.</li>
    19571943      </ol>
    1958       <p id="rfc.section.6.3.4.p.7">An Accept-Encoding header field with a combined field-value that is empty implies that the user agent does not want any content-coding
     1944      <p id="rfc.section.5.3.4.p.7">An Accept-Encoding header field with a combined field-value that is empty implies that the user agent does not want any content-coding
    19591945         in response. If an Accept-Encoding header field is present in a request and none of the available representations for the
    19601946         response have a content-coding that is listed as acceptable, the origin server <em class="bcp14">SHOULD</em> send a response without any content-coding.
    19611947      </p>
    1962       <p id="rfc.section.6.3.4.p.8">A request without an Accept-Encoding header field implies that the user agent will accept any content-coding in response.</p>
    1963       <div class="note" id="rfc.section.6.3.4.p.9">
     1948      <p id="rfc.section.5.3.4.p.8">A request without an Accept-Encoding header field implies that the user agent will accept any content-coding in response.</p>
     1949      <div class="note" id="rfc.section.5.3.4.p.9">
    19641950         <p> <b>Note:</b> Most HTTP/1.0 applications do not recognize or obey qvalues associated with content-codings. This means that qvalues will
    19651951            not work and are not permitted with x-gzip or x-compress.
     
    19671953      </div>
    19681954      <div id="rfc.iref.a.4"></div>
    1969       <h3 id="rfc.section.6.3.5"><a href="#rfc.section.6.3.5">6.3.5</a>&nbsp;<a id="header.accept-language" href="#header.accept-language">Accept-Language</a></h3>
    1970       <p id="rfc.section.6.3.5.p.1">The "Accept-Language" header field can be used by user agents to indicate the set of natural languages that are preferred
     1955      <h3 id="rfc.section.5.3.5"><a href="#rfc.section.5.3.5">5.3.5</a>&nbsp;<a id="header.accept-language" href="#header.accept-language">Accept-Language</a></h3>
     1956      <p id="rfc.section.5.3.5.p.1">The "Accept-Language" header field can be used by user agents to indicate the set of natural languages that are preferred
    19711957         in the response. Language tags are defined in <a href="#language.tags" title="Language Tags">Section&nbsp;3.1.3.1</a>.
    19721958      </p>
    1973       <div id="rfc.figure.u.34"></div><pre class="inline"><span id="rfc.iref.g.34"></span><span id="rfc.iref.g.35"></span>  <a href="#header.accept-language" class="smpl">Accept-Language</a> = 1#( <a href="#header.accept-language" class="smpl">language-range</a> [ <a href="#quality.values" class="smpl">weight</a> ] )
     1959      <div id="rfc.figure.u.32"></div><pre class="inline"><span id="rfc.iref.g.32"></span><span id="rfc.iref.g.33"></span>  <a href="#header.accept-language" class="smpl">Accept-Language</a> = 1#( <a href="#header.accept-language" class="smpl">language-range</a> [ <a href="#quality.values" class="smpl">weight</a> ] )
    19741960  <a href="#header.accept-language" class="smpl">language-range</a>  =
    19751961            &lt;language-range, defined in <a href="#RFC4647" id="rfc.xref.RFC4647.1"><cite title="Matching of Language Tags">[RFC4647]</cite></a>, <a href="http://tools.ietf.org/html/rfc4647#section-2.1">Section 2.1</a>&gt;
    1976 </pre><p id="rfc.section.6.3.5.p.3">Each language-range can be given an associated quality value which represents an estimate of the user's preference for the
    1977          languages specified by that range, as defined in <a href="#quality.values" title="Quality Values">Section&nbsp;6.3.1</a>. For example,
    1978       </p>
    1979       <div id="rfc.figure.u.35"></div><pre class="text">  Accept-Language: da, en-gb;q=0.8, en;q=0.7
    1980 </pre><p id="rfc.section.6.3.5.p.5">would mean: "I prefer Danish, but will accept British English and other types of English". (See also <a href="http://tools.ietf.org/html/rfc4647#section-2.3">Section 2.3</a> of <a href="#RFC4647" id="rfc.xref.RFC4647.2"><cite title="Matching of Language Tags">[RFC4647]</cite></a>)
    1981       </p>
    1982       <p id="rfc.section.6.3.5.p.6">For matching, <a href="http://tools.ietf.org/html/rfc4647#section-3">Section 3</a> of <a href="#RFC4647" id="rfc.xref.RFC4647.3"><cite title="Matching of Language Tags">[RFC4647]</cite></a> defines several matching schemes. Implementations can offer the most appropriate matching scheme for their requirements.
    1983       </p>
    1984       <div class="note" id="rfc.section.6.3.5.p.7">
     1962</pre><p id="rfc.section.5.3.5.p.3">Each language-range can be given an associated quality value which represents an estimate of the user's preference for the
     1963         languages specified by that range, as defined in <a href="#quality.values" title="Quality Values">Section&nbsp;5.3.1</a>. For example,
     1964      </p>
     1965      <div id="rfc.figure.u.33"></div><pre class="text">  Accept-Language: da, en-gb;q=0.8, en;q=0.7
     1966</pre><p id="rfc.section.5.3.5.p.5">would mean: "I prefer Danish, but will accept British English and other types of English". (See also <a href="http://tools.ietf.org/html/rfc4647#section-2.3">Section 2.3</a> of <a href="#RFC4647" id="rfc.xref.RFC4647.2"><cite title="Matching of Language Tags">[RFC4647]</cite></a>)
     1967      </p>
     1968      <p id="rfc.section.5.3.5.p.6">For matching, <a href="http://tools.ietf.org/html/rfc4647#section-3">Section 3</a> of <a href="#RFC4647" id="rfc.xref.RFC4647.3"><cite title="Matching of Language Tags">[RFC4647]</cite></a> defines several matching schemes. Implementations can offer the most appropriate matching scheme for their requirements.
     1969      </p>
     1970      <div class="note" id="rfc.section.5.3.5.p.7">
    19851971         <p> <b>Note:</b> The "Basic Filtering" scheme (<a href="#RFC4647" id="rfc.xref.RFC4647.4"><cite title="Matching of Language Tags">[RFC4647]</cite></a>, <a href="http://tools.ietf.org/html/rfc4647#section-3.3.1">Section 3.3.1</a>) is identical to the matching scheme that was previously defined in <a href="http://tools.ietf.org/html/rfc2616#section-14.4">Section 14.4</a> of <a href="#RFC2616" id="rfc.xref.RFC2616.1"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>.
    19861972         </p>
    19871973      </div>
    1988       <p id="rfc.section.6.3.5.p.8">It might be contrary to the privacy expectations of the user to send an Accept-Language header field with the complete linguistic
    1989          preferences of the user in every request. For a discussion of this issue, see <a href="#privacy.issues.connected.to.accept.header.fields" title="Privacy Issues Connected to Accept Header Fields">Section&nbsp;10.5</a>.
    1990       </p>
    1991       <p id="rfc.section.6.3.5.p.9">As intelligibility is highly dependent on the individual user, it is recommended that client applications make the choice
     1974      <p id="rfc.section.5.3.5.p.8">It might be contrary to the privacy expectations of the user to send an Accept-Language header field with the complete linguistic
     1975         preferences of the user in every request. For a discussion of this issue, see <a href="#privacy.issues.connected.to.accept.header.fields" title="Privacy Issues Connected to Accept Header Fields">Section&nbsp;9.5</a>.
     1976      </p>
     1977      <p id="rfc.section.5.3.5.p.9">As intelligibility is highly dependent on the individual user, it is recommended that client applications make the choice
    19921978         of linguistic preference available to the user. If the choice is not made available, then the Accept-Language header field <em class="bcp14">MUST NOT</em> be given in the request.
    19931979      </p>
    1994       <div class="note" id="rfc.section.6.3.5.p.10">
     1980      <div class="note" id="rfc.section.5.3.5.p.10">
    19951981         <p> <b>Note:</b> When making the choice of linguistic preference available to the user, we remind implementers of the fact that users are not
    19961982            familiar with the details of language matching as described above, and ought to be provided appropriate guidance. As an example,
     
    19991985         </p>
    20001986      </div>
    2001       <h2 id="rfc.section.6.4"><a href="#rfc.section.6.4">6.4</a>&nbsp;<a id="request.auth" href="#request.auth">Authentication Credentials</a></h2>
     1987      <h2 id="rfc.section.5.4"><a href="#rfc.section.5.4">5.4</a>&nbsp;<a id="request.auth" href="#request.auth">Authentication Credentials</a></h2>
    20021988      <div id="rfc.table.u.7">
    20031989         <table class="tt full left" cellpadding="3" cellspacing="0">
     
    20202006         </table>
    20212007      </div>
    2022       <h2 id="rfc.section.6.5"><a href="#rfc.section.6.5">6.5</a>&nbsp;<a id="request.context" href="#request.context">Context</a></h2>
     2008      <h2 id="rfc.section.5.5"><a href="#rfc.section.5.5">5.5</a>&nbsp;<a id="request.context" href="#request.context">Request Context</a></h2>
    20232009      <div id="rfc.table.u.8">
    20242010         <table class="tt full left" cellpadding="3" cellspacing="0">
     
    20322018               <tr>
    20332019                  <td class="left">From</td>
    2034                   <td class="left"><a href="#header.from" id="rfc.xref.header.from.1" title="From">Section&nbsp;6.5.1</a></td>
     2020                  <td class="left"><a href="#header.from" id="rfc.xref.header.from.1" title="From">Section&nbsp;5.5.1</a></td>
    20352021               </tr>
    20362022               <tr>
    20372023                  <td class="left">Referer</td>
    2038                   <td class="left"><a href="#header.referer" id="rfc.xref.header.referer.1" title="Referer">Section&nbsp;6.5.2</a></td>
     2024                  <td class="left"><a href="#header.referer" id="rfc.xref.header.referer.1" title="Referer">Section&nbsp;5.5.2</a></td>
    20392025               </tr>
    20402026               <tr>
     
    20442030               <tr>
    20452031                  <td class="left">User-Agent</td>
    2046                   <td class="left"><a href="#header.user-agent" id="rfc.xref.header.user-agent.1" title="User-Agent">Section&nbsp;6.5.3</a></td>
     2032                  <td class="left"><a href="#header.user-agent" id="rfc.xref.header.user-agent.1" title="User-Agent">Section&nbsp;5.5.3</a></td>
    20472033               </tr>
    20482034            </tbody>
     
    20502036      </div>
    20512037      <div id="rfc.iref.f.1"></div>
    2052       <h3 id="rfc.section.6.5.1"><a href="#rfc.section.6.5.1">6.5.1</a>&nbsp;<a id="header.from" href="#header.from">From</a></h3>
    2053       <p id="rfc.section.6.5.1.p.1">The "From" header field, if given, <em class="bcp14">SHOULD</em> contain an Internet e-mail address for the human user who controls the requesting user agent. The address <em class="bcp14">SHOULD</em> be machine-usable, as defined by "mailbox" in <a href="http://tools.ietf.org/html/rfc5322#section-3.4">Section 3.4</a> of <a href="#RFC5322" id="rfc.xref.RFC5322.1"><cite title="Internet Message Format">[RFC5322]</cite></a>:
    2054       </p>
    2055       <div id="rfc.figure.u.36"></div><pre class="inline"><span id="rfc.iref.g.36"></span>  <a href="#header.from" class="smpl">From</a>    = <a href="#header.from" class="smpl">mailbox</a>
     2038      <h3 id="rfc.section.5.5.1"><a href="#rfc.section.5.5.1">5.5.1</a>&nbsp;<a id="header.from" href="#header.from">From</a></h3>
     2039      <p id="rfc.section.5.5.1.p.1">The "From" header field, if given, <em class="bcp14">SHOULD</em> contain an Internet e-mail address for the human user who controls the requesting user agent. The address <em class="bcp14">SHOULD</em> be machine-usable, as defined by "mailbox" in <a href="http://tools.ietf.org/html/rfc5322#section-3.4">Section 3.4</a> of <a href="#RFC5322" id="rfc.xref.RFC5322.1"><cite title="Internet Message Format">[RFC5322]</cite></a>:
     2040      </p>
     2041      <div id="rfc.figure.u.34"></div><pre class="inline"><span id="rfc.iref.g.34"></span>  <a href="#header.from" class="smpl">From</a>    = <a href="#header.from" class="smpl">mailbox</a>
    20562042 
    20572043  <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;
    2058 </pre><p id="rfc.section.6.5.1.p.3">An example is:</p>
    2059       <div id="rfc.figure.u.37"></div><pre class="text">  From: webmaster@example.org
    2060 </pre><p id="rfc.section.6.5.1.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
     2044</pre><p id="rfc.section.5.5.1.p.3">An example is:</p>
     2045      <div id="rfc.figure.u.35"></div><pre class="text">  From: webmaster@example.org
     2046</pre><p id="rfc.section.5.5.1.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
    20612047         on behalf of the person given, who accepts responsibility for the method performed. In particular, robot agents <em class="bcp14">SHOULD</em> include this header field so that the person responsible for running the robot can be contacted if problems occur on the receiving
    20622048         end.
    20632049      </p>
    2064       <p id="rfc.section.6.5.1.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
     2050      <p id="rfc.section.5.5.1.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
    20652051         issuer's address <em class="bcp14">SHOULD</em> be used.
    20662052      </p>
    2067       <p id="rfc.section.6.5.1.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
     2053      <p id="rfc.section.5.5.1.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
    20682054         security policy. It is strongly recommended that the user be able to disable, enable, and modify the value of this field at
    20692055         any time prior to a request.
    20702056      </p>
    20712057      <div id="rfc.iref.r.2"></div>
    2072       <h3 id="rfc.section.6.5.2"><a href="#rfc.section.6.5.2">6.5.2</a>&nbsp;<a id="header.referer" href="#header.referer">Referer</a></h3>
    2073       <p id="rfc.section.6.5.2.p.1">The "Referer" [sic] header field allows the client to specify the URI of the resource from which the target URI was obtained
     2058      <h3 id="rfc.section.5.5.2"><a href="#rfc.section.5.5.2">5.5.2</a>&nbsp;<a id="header.referer" href="#header.referer">Referer</a></h3>
     2059      <p id="rfc.section.5.5.2.p.1">The "Referer" [sic] header field allows the client to specify the URI of the resource from which the target URI was obtained
    20742060         (the "referrer", although the header field is misspelled.).
    20752061      </p>
    2076       <p id="rfc.section.6.5.2.p.2">The Referer header field allows servers to generate lists of back-links to resources for interest, logging, optimized caching,
     2062      <p id="rfc.section.5.5.2.p.2">The Referer header field allows servers to generate lists of back-links to resources for interest, logging, optimized caching,
    20772063         etc. It also allows obsolete or mistyped links to be traced for maintenance. Some servers use Referer as a means of controlling
    20782064         where they allow links from (so-called "deep linking"), but legitimate requests do not always contain a Referer header field.
    20792065      </p>
    2080       <p id="rfc.section.6.5.2.p.3">If the target URI was obtained from a source that does not have its own URI (e.g., input from the user keyboard), the Referer
     2066      <p id="rfc.section.5.5.2.p.3">If the target URI was obtained from a source that does not have its own URI (e.g., input from the user keyboard), the Referer
    20812067         field <em class="bcp14">MUST</em> either be sent with the value "about:blank", or not be sent at all. Note that this requirement does not apply to sources with
    20822068         non-HTTP URIs (e.g., FTP).
    20832069      </p>
    2084       <div id="rfc.figure.u.38"></div><pre class="inline"><span id="rfc.iref.g.37"></span>  <a href="#header.referer" class="smpl">Referer</a> = <a href="#imported.abnf" class="smpl">absolute-URI</a> / <a href="#imported.abnf" class="smpl">partial-URI</a>
    2085 </pre><p id="rfc.section.6.5.2.p.5">Example:</p>
    2086       <div id="rfc.figure.u.39"></div><pre class="text">  Referer: http://www.example.org/hypertext/Overview.html
    2087 </pre><p id="rfc.section.6.5.2.p.7">If the field value is a relative URI, it <em class="bcp14">SHOULD</em> be interpreted relative to the effective request URI. The URI <em class="bcp14">MUST NOT</em> include a fragment. See <a href="#encoding.sensitive.information.in.uris" title="Encoding Sensitive Information in URIs">Section&nbsp;10.2</a> for security considerations.
     2070      <div id="rfc.figure.u.36"></div><pre class="inline"><span id="rfc.iref.g.35"></span>  <a href="#header.referer" class="smpl">Referer</a> = <a href="#imported.abnf" class="smpl">absolute-URI</a> / <a href="#imported.abnf" class="smpl">partial-URI</a>
     2071</pre><p id="rfc.section.5.5.2.p.5">Example:</p>
     2072      <div id="rfc.figure.u.37"></div><pre class="text">  Referer: http://www.example.org/hypertext/Overview.html
     2073</pre><p id="rfc.section.5.5.2.p.7">If the field value is a relative URI, it <em class="bcp14">SHOULD</em> be interpreted relative to the effective request URI. The URI <em class="bcp14">MUST NOT</em> include a fragment. See <a href="#encoding.sensitive.information.in.uris" title="Encoding Sensitive Information in URIs">Section&nbsp;9.2</a> for security considerations.
    20882074      </p>
    20892075      <div id="rfc.iref.u.1"></div>
    2090       <h3 id="rfc.section.6.5.3"><a href="#rfc.section.6.5.3">6.5.3</a>&nbsp;<a id="header.user-agent" href="#header.user-agent">User-Agent</a></h3>
    2091       <p id="rfc.section.6.5.3.p.1">The "User-Agent" header field contains information about the user agent originating the request. User agents <em class="bcp14">SHOULD</em> include this field with requests.
    2092       </p>
    2093       <p id="rfc.section.6.5.3.p.2">Typically, it is used for statistical purposes, the tracing of protocol violations, and tailoring responses to avoid particular
    2094          user agent limitations.
    2095       </p>
    2096       <p id="rfc.section.6.5.3.p.3">The field can contain multiple product tokens (<a href="#product.tokens" title="Product Tokens">Section&nbsp;4</a>) and comments (<a href="p1-messaging.html#header.fields" title="Header Fields">Section 3.2</a> of <a href="#Part1" id="rfc.xref.Part1.21"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>) identifying the agent and its significant subproducts. By convention, the product tokens are listed in order of their significance
    2097          for identifying the application.
    2098       </p>
    2099       <p id="rfc.section.6.5.3.p.4">Because this field is usually sent on every request a user agent makes, implementations are encouraged not to include needlessly
    2100          fine-grained detail, and to limit (or even prohibit) the addition of subproducts by third parties. Overly long and detailed
    2101          User-Agent field values make requests larger and can also be used to identify ("fingerprint") the user against their wishes.
    2102       </p>
    2103       <p id="rfc.section.6.5.3.p.5">Likewise, implementations are encouraged not to use the product tokens of other implementations in order to declare compatibility
    2104          with them, as this circumvents the purpose of the field. Finally, they are encouraged not to use comments to identify products;
    2105          doing so makes the field value more difficult to parse.
    2106       </p>
    2107       <div id="rfc.figure.u.40"></div><pre class="inline"><span id="rfc.iref.g.38"></span>  <a href="#header.user-agent" class="smpl">User-Agent</a> = <a href="#product.tokens" class="smpl">product</a> *( <a href="#imported.abnf" class="smpl">RWS</a> ( <a href="#product.tokens" class="smpl">product</a> / <a href="#imported.abnf" class="smpl">comment</a> ) )
    2108 </pre><p id="rfc.section.6.5.3.p.7">Example:</p>
    2109       <div id="rfc.figure.u.41"></div><pre class="text">  User-Agent: CERN-LineMode/2.15 libwww/2.17b3
    2110 </pre><h1 id="rfc.section.7"><a href="#rfc.section.7">7.</a>&nbsp;<a id="status.codes" href="#status.codes">Response Status Codes</a></h1>
    2111       <p id="rfc.section.7.p.1">The status-code element is a 3-digit integer code giving the result of the attempt to understand and satisfy the request.</p>
    2112       <p id="rfc.section.7.p.2">HTTP status codes are extensible. HTTP applications are not required to understand the meaning of all registered status codes,
     2076      <h3 id="rfc.section.5.5.3"><a href="#rfc.section.5.5.3">5.5.3</a>&nbsp;<a id="header.user-agent" href="#header.user-agent">User-Agent</a></h3>
     2077      <p id="rfc.section.5.5.3.p.1">The "User-Agent" header field contains information about the user agent originating the request, which is often used by servers
     2078         to help identify the scope of reported interoperability problems, to work around or tailor responses to avoid particular user
     2079         agent limitations, and for analytics regarding browser or operating system use. A user agent <em class="bcp14">SHOULD</em> include a User-Agent field in each request unless specifically configured not to do so.
     2080      </p>
     2081      <div id="rfc.figure.u.38"></div><pre class="inline"><span id="rfc.iref.g.36"></span>  <a href="#header.user-agent" class="smpl">User-Agent</a> = <a href="#header.user-agent" class="smpl">product</a> *( <a href="#imported.abnf" class="smpl">RWS</a> ( <a href="#header.user-agent" class="smpl">product</a> / <a href="#imported.abnf" class="smpl">comment</a> ) )
     2082</pre><p id="rfc.section.5.5.3.p.3">The User-Agent field-value consists of one or more product identifiers, each followed by zero or more comments (<a href="p1-messaging.html#header.fields" title="Header Fields">Section 3.2</a> of <a href="#Part1" id="rfc.xref.Part1.21"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>), which together identify the user agent software and its significant subproducts. By convention, the product identifiers
     2083         are listed in order of their significance for identifying the user agent software. Each product identifier consists of a name
     2084         and optional version.
     2085      </p>
     2086      <div id="rfc.figure.u.39"></div><pre class="inline"><span id="rfc.iref.g.37"></span><span id="rfc.iref.g.38"></span>  <a href="#header.user-agent" class="smpl">product</a>         = <a href="#imported.abnf" class="smpl">token</a> ["/" <a href="#header.user-agent" class="smpl">product-version</a>]
     2087  <a href="#header.user-agent" class="smpl">product-version</a> = <a href="#imported.abnf" class="smpl">token</a>
     2088</pre><p id="rfc.section.5.5.3.p.5">Senders <em class="bcp14">SHOULD</em> limit generated product identifiers to what is necessary to identify the product; senders <em class="bcp14">MUST NOT</em> generate advertising or other non-essential information within the product identifier. Senders <em class="bcp14">SHOULD NOT</em> generate information in <a href="#header.user-agent" class="smpl">product-version</a> that is not a version identifier (i.e., successive versions of the same product name ought to only differ in the product-version
     2089         portion of the product identifier).
     2090      </p>
     2091      <p id="rfc.section.5.5.3.p.6">Example:</p>
     2092      <div id="rfc.figure.u.40"></div><pre class="text">  User-Agent: CERN-LineMode/2.15 libwww/2.17b3
     2093</pre><p id="rfc.section.5.5.3.p.8">A user agent <em class="bcp14">SHOULD NOT</em> generate a User-Agent field containing needlessly fine-grained detail and <em class="bcp14">SHOULD</em> limit the addition of subproducts by third parties. Overly long and detailed User-Agent field values increase request latency
     2094         and the risk of a user being identified against their wishes ("fingerprinting").
     2095      </p>
     2096      <p id="rfc.section.5.5.3.p.9">Likewise, implementations are encouraged not to use the product tokens of other implementations in order to declare compatibility
     2097         with them, as this circumvents the purpose of the field. If a user agent masquerades as a different user agent, recipients
     2098         can assume that the user intentionally desires to see responses tailored for that identified user agent, even if they might
     2099         not work as well for the actual user agent being used.
     2100      </p>
     2101      <h1 id="rfc.section.6"><a href="#rfc.section.6">6.</a>&nbsp;<a id="status.codes" href="#status.codes">Response Status Codes</a></h1>
     2102      <p id="rfc.section.6.p.1">The status-code element is a 3-digit integer code giving the result of the attempt to understand and satisfy the request.</p>
     2103      <p id="rfc.section.6.p.2">HTTP status codes are extensible. HTTP applications are not required to understand the meaning of all registered status codes,
    21132104         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
    21142105         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
     
    21162107         information which will explain the unusual status.
    21172108      </p>
    2118       <p id="rfc.section.7.p.3">The first digit of the status-code defines the class of response. The last two digits do not have any categorization role.
     2109      <p id="rfc.section.6.p.3">The first digit of the status-code defines the class of response. The last two digits do not have any categorization role.
    21192110         There are 5 values for the first digit:
    21202111      </p>
     
    21312122         </li>
    21322123      </ul>
    2133       <p id="rfc.section.7.p.4">For most status codes the response can carry a payload, in which case a <a href="#header.content-type" class="smpl">Content-Type</a> header field indicates the payload's media type (<a href="#header.content-type" id="rfc.xref.header.content-type.3" title="Content-Type">Section&nbsp;3.1.1.5</a>).
    2134       </p>
    2135       <h2 id="rfc.section.7.1"><a href="#rfc.section.7.1">7.1</a>&nbsp;<a id="overview.of.status.codes" href="#overview.of.status.codes">Overview of Status Codes</a></h2>
    2136       <p id="rfc.section.7.1.p.1">The status codes listed below are defined in this specification, <a href="p4-conditional.html#status.code.definitions" title="Status Code Definitions">Section 4</a> of <a href="#Part4" id="rfc.xref.Part4.7"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests">[Part4]</cite></a>, <a href="p5-range.html#status.code.definitions" title="Status Code Definitions">Section 3</a> of <a href="#Part5" id="rfc.xref.Part5.8"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Range Requests">[Part5]</cite></a>, and <a href="p7-auth.html#status.code.definitions" title="Status Code Definitions">Section 3</a> of <a href="#Part7" id="rfc.xref.Part7.3"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Authentication">[Part7]</cite></a>. The reason phrases listed here are only recommendations — they can be replaced by local equivalents without affecting the
     2124      <p id="rfc.section.6.p.4">For most status codes the response can carry a payload, in which case a <a href="#header.content-type" class="smpl">Content-Type</a> header field indicates the payload's media type (<a href="#header.content-type" id="rfc.xref.header.content-type.3" title="Content-Type">Section&nbsp;3.1.1.5</a>).
     2125      </p>
     2126      <h2 id="rfc.section.6.1"><a href="#rfc.section.6.1">6.1</a>&nbsp;<a id="overview.of.status.codes" href="#overview.of.status.codes">Overview of Status Codes</a></h2>
     2127      <p id="rfc.section.6.1.p.1">The status codes listed below are defined in this specification, <a href="p4-conditional.html#status.code.definitions" title="Status Code Definitions">Section 4</a> of <a href="#Part4" id="rfc.xref.Part4.7"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests">[Part4]</cite></a>, <a href="p5-range.html#status.code.definitions" title="Status Code Definitions">Section 3</a> of <a href="#Part5" id="rfc.xref.Part5.8"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Range Requests">[Part5]</cite></a>, and <a href="p7-auth.html#status.code.definitions" title="Status Code Definitions">Section 3</a> of <a href="#Part7" id="rfc.xref.Part7.3"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Authentication">[Part7]</cite></a>. The reason phrases listed here are only recommendations — they can be replaced by local equivalents without affecting the
    21372128         protocol.
    21382129      </p>
     
    21502141                  <td class="left">100</td>
    21512142                  <td class="left">Continue</td>
    2152                   <td class="left"><a href="#status.100" id="rfc.xref.status.100.3" title="100 Continue">Section&nbsp;7.2.1</a></td>
     2143                  <td class="left"><a href="#status.100" id="rfc.xref.status.100.3" title="100 Continue">Section&nbsp;6.2.1</a></td>
    21532144               </tr>
    21542145               <tr>
    21552146                  <td class="left">101</td>
    21562147                  <td class="left">Switching Protocols</td>
    2157                   <td class="left"><a href="#status.101" id="rfc.xref.status.101.1" title="101 Switching Protocols">Section&nbsp;7.2.2</a></td>
     2148                  <td class="left"><a href="#status.101" id="rfc.xref.status.101.1" title="101 Switching Protocols">Section&nbsp;6.2.2</a></td>
    21582149               </tr>
    21592150               <tr>
    21602151                  <td class="left">200</td>
    21612152                  <td class="left">OK</td>
    2162                   <td class="left"><a href="#status.200" id="rfc.xref.status.200.1" title="200 OK">Section&nbsp;7.3.1</a></td>
     2153                  <td class="left"><a href="#status.200" id="rfc.xref.status.200.1" title="200 OK">Section&nbsp;6.3.1</a></td>
    21632154               </tr>
    21642155               <tr>
    21652156                  <td class="left">201</td>
    21662157                  <td class="left">Created</td>
    2167                   <td class="left"><a href="#status.201" id="rfc.xref.status.201.1" title="201 Created">Section&nbsp;7.3.2</a></td>
     2158                  <td class="left"><a href="#status.201" id="rfc.xref.status.201.1" title="201 Created">Section&nbsp;6.3.2</a></td>
    21682159               </tr>
    21692160               <tr>
    21702161                  <td class="left">202</td>
    21712162                  <td class="left">Accepted</td>
    2172                   <td class="left"><a href="#status.202" id="rfc.xref.status.202.1" title="202 Accepted">Section&nbsp;7.3.3</a></td>
     2163                  <td class="left"><a href="#status.202" id="rfc.xref.status.202.1" title="202 Accepted">Section&nbsp;6.3.3</a></td>
    21732164               </tr>
    21742165               <tr>
    21752166                  <td class="left">203</td>
    21762167                  <td class="left">Non-Authoritative Information</td>
    2177                   <td class="left"><a href="#status.203" id="rfc.xref.status.203.1" title="203 Non-Authoritative Information">Section&nbsp;7.3.4</a></td>
     2168                  <td class="left"><a href="#status.203" id="rfc.xref.status.203.1" title="203 Non-Authoritative Information">Section&nbsp;6.3.4</a></td>
    21782169               </tr>
    21792170               <tr>
    21802171                  <td class="left">204</td>
    21812172                  <td class="left">No Content</td>
    2182                   <td class="left"><a href="#status.204" id="rfc.xref.status.204.1" title="204 No Content">Section&nbsp;7.3.5</a></td>
     2173                  <td class="left"><a href="#status.204" id="rfc.xref.status.204.1" title="204 No Content">Section&nbsp;6.3.5</a></td>
    21832174               </tr>
    21842175               <tr>
    21852176                  <td class="left">205</td>
    21862177                  <td class="left">Reset Content</td>
    2187                   <td class="left"><a href="#status.205" id="rfc.xref.status.205.1" title="205 Reset Content">Section&nbsp;7.3.6</a></td>
     2178                  <td class="left"><a href="#status.205" id="rfc.xref.status.205.1" title="205 Reset Content">Section&nbsp;6.3.6</a></td>
    21882179               </tr>
    21892180               <tr>
     
    21952186                  <td class="left">300</td>
    21962187                  <td class="left">Multiple Choices</td>
    2197                   <td class="left"><a href="#status.300" id="rfc.xref.status.300.1" title="300 Multiple Choices">Section&nbsp;7.4.1</a></td>
     2188                  <td class="left"><a href="#status.300" id="rfc.xref.status.300.1" title="300 Multiple Choices">Section&nbsp;6.4.1</a></td>
    21982189               </tr>
    21992190               <tr>
    22002191                  <td class="left">301</td>
    22012192                  <td class="left">Moved Permanently</td>
    2202                   <td class="left"><a href="#status.301" id="rfc.xref.status.301.1" title="301 Moved Permanently">Section&nbsp;7.4.2</a></td>
     2193                  <td class="left"><a href="#status.301" id="rfc.xref.status.301.1" title="301 Moved Permanently">Section&nbsp;6.4.2</a></td>
    22032194               </tr>
    22042195               <tr>
    22052196                  <td class="left">302</td>
    22062197                  <td class="left">Found</td>
    2207                   <td class="left"><a href="#status.302" id="rfc.xref.status.302.1" title="302 Found">Section&nbsp;7.4.3</a></td>
     2198                  <td class="left"><a href="#status.302" id="rfc.xref.status.302.1" title="302 Found">Section&nbsp;6.4.3</a></td>
    22082199               </tr>
    22092200               <tr>
    22102201                  <td class="left">303</td>
    22112202                  <td class="left">See Other</td>
    2212                   <td class="left"><a href="#status.303" id="rfc.xref.status.303.1" title="303 See Other">Section&nbsp;7.4.4</a></td>
     2203                  <td class="left"><a href="#status.303" id="rfc.xref.status.303.1" title="303 See Other">Section&nbsp;6.4.4</a></td>
    22132204               </tr>
    22142205               <tr>
     
    22202211                  <td class="left">305</td>
    22212212                  <td class="left">Use Proxy</td>
    2222                   <td class="left"><a href="#status.305" id="rfc.xref.status.305.1" title="305 Use Proxy">Section&nbsp;7.4.5</a></td>
     2213                  <td class="left"><a href="#status.305" id="rfc.xref.status.305.1" title="305 Use Proxy">Section&nbsp;6.4.5</a></td>
    22232214               </tr>
    22242215               <tr>
    22252216                  <td class="left">307</td>
    22262217                  <td class="left">Temporary Redirect</td>
    2227                   <td class="left"><a href="#status.307" id="rfc.xref.status.307.1" title="307 Temporary Redirect">Section&nbsp;7.4.7</a></td>
     2218                  <td class="left"><a href="#status.307" id="rfc.xref.status.307.1" title="307 Temporary Redirect">Section&nbsp;6.4.7</a></td>
    22282219               </tr>
    22292220               <tr>
    22302221                  <td class="left">400</td>
    22312222                  <td class="left">Bad Request</td>
    2232                   <td class="left"><a href="#status.400" id="rfc.xref.status.400.1" title="400 Bad Request">Section&nbsp;7.5.1</a></td>
     2223                  <td class="left"><a href="#status.400" id="rfc.xref.status.400.1" title="400 Bad Request">Section&nbsp;6.5.1</a></td>
    22332224               </tr>
    22342225               <tr>
     
    22402231                  <td class="left">402</td>
    22412232                  <td class="left">Payment Required</td>
    2242                   <td class="left"><a href="#status.402" id="rfc.xref.status.402.1" title="402 Payment Required">Section&nbsp;7.5.2</a></td>
     2233                  <td class="left"><a href="#status.402" id="rfc.xref.status.402.1" title="402 Payment Required">Section&nbsp;6.5.2</a></td>
    22432234               </tr>
    22442235               <tr>
    22452236                  <td class="left">403</td>
    22462237                  <td class="left">Forbidden</td>
    2247                   <td class="left"><a href="#status.403" id="rfc.xref.status.403.1" title="403 Forbidden">Section&nbsp;7.5.3</a></td>
     2238                  <td class="left"><a href="#status.403" id="rfc.xref.status.403.1" title="403 Forbidden">Section&nbsp;6.5.3</a></td>
    22482239               </tr>
    22492240               <tr>
    22502241                  <td class="left">404</td>
    22512242                  <td class="left">Not Found</td>
    2252                   <td class="left"><a href="#status.404" id="rfc.xref.status.404.1" title="404 Not Found">Section&nbsp;7.5.4</a></td>
     2243                  <td class="left"><a href="#status.404" id="rfc.xref.status.404.1" title="404 Not Found">Section&nbsp;6.5.4</a></td>
    22532244               </tr>
    22542245               <tr>
    22552246                  <td class="left">405</td>
    22562247                  <td class="left">Method Not Allowed</td>
    2257                   <td class="left"><a href="#status.405" id="rfc.xref.status.405.1" title="405 Method Not Allowed">Section&nbsp;7.5.5</a></td>
     2248                  <td class="left"><a href="#status.405" id="rfc.xref.status.405.1" title="405 Method Not Allowed">Section&nbsp;6.5.5</a></td>
    22582249               </tr>
    22592250               <tr>
    22602251                  <td class="left">406</td>
    22612252                  <td class="left">Not Acceptable</td>
    2262                   <td class="left"><a href="#status.406" id="rfc.xref.status.406.1" title="406 Not Acceptable">Section&nbsp;7.5.6</a></td>
     2253                  <td class="left"><a href="#status.406" id="rfc.xref.status.406.1" title="406 Not Acceptable">Section&nbsp;6.5.6</a></td>
    22632254               </tr>
    22642255               <tr>
     
    22702261                  <td class="left">408</td>
    22712262                  <td class="left">Request Time-out</td>
    2272                   <td class="left"><a href="#status.408" id="rfc.xref.status.408.1" title="408 Request Timeout">Section&nbsp;7.5.7</a></td>
     2263                  <td class="left"><a href="#status.408" id="rfc.xref.status.408.1" title="408 Request Timeout">Section&nbsp;6.5.7</a></td>
    22732264               </tr>
    22742265               <tr>
    22752266                  <td class="left">409</td>
    22762267                  <td class="left">Conflict</td>
    2277                   <td class="left"><a href="#status.409" id="rfc.xref.status.409.1" title="409 Conflict">Section&nbsp;7.5.8</a></td>
     2268                  <td class="left"><a href="#status.409" id="rfc.xref.status.409.1" title="409 Conflict">Section&nbsp;6.5.8</a></td>
    22782269               </tr>
    22792270               <tr>
    22802271                  <td class="left">410</td>
    22812272                  <td class="left">Gone</td>
    2282                   <td class="left"><a href="#status.410" id="rfc.xref.status.410.1" title="410 Gone">Section&nbsp;7.5.9</a></td>
     2273                  <td class="left"><a href="#status.410" id="rfc.xref.status.410.1" title="410 Gone">Section&nbsp;6.5.9</a></td>
    22832274               </tr>
    22842275               <tr>
    22852276                  <td class="left">411</td>
    22862277                  <td class="left">Length Required</td>
    2287                   <td class="left"><a href="#status.411" id="rfc.xref.status.411.1" title="411 Length Required">Section&nbsp;7.5.10</a></td>
     2278                  <td class="left"><a href="#status.411" id="rfc.xref.status.411.1" title="411 Length Required">Section&nbsp;6.5.10</a></td>
    22882279               </tr>
    22892280               <tr>
     
    22952286                  <td class="left">413</td>
    22962287                  <td class="left">Request Representation Too Large</td>
    2297                   <td class="left"><a href="#status.413" id="rfc.xref.status.413.1" title="413 Request Representation Too Large">Section&nbsp;7.5.11</a></td>
     2288                  <td class="left"><a href="#status.413" id="rfc.xref.status.413.1" title="413 Request Representation Too Large">Section&nbsp;6.5.11</a></td>
    22982289               </tr>
    22992290               <tr>
    23002291                  <td class="left">414</td>
    23012292                  <td class="left">URI Too Long</td>
    2302                   <td class="left"><a href="#status.414" id="rfc.xref.status.414.1" title="414 URI Too Long">Section&nbsp;7.5.12</a></td>
     2293                  <td class="left"><a href="#status.414" id="rfc.xref.status.414.1" title="414 URI Too Long">Section&nbsp;6.5.12</a></td>
    23032294               </tr>
    23042295               <tr>
    23052296                  <td class="left">415</td>
    23062297                  <td class="left">Unsupported Media Type</td>
    2307                   <td class="left"><a href="#status.415" id="rfc.xref.status.415.1" title="415 Unsupported Media Type">Section&nbsp;7.5.13</a></td>
     2298                  <td class="left"><a href="#status.415" id="rfc.xref.status.415.1" title="415 Unsupported Media Type">Section&nbsp;6.5.13</a></td>
    23082299               </tr>
    23092300               <tr>
     
    23152306                  <td class="left">417</td>
    23162307                  <td class="left">Expectation Failed</td>
    2317                   <td class="left"><a href="#status.417" id="rfc.xref.status.417.1" title="417 Expectation Failed">Section&nbsp;7.5.14</a></td>
     2308                  <td class="left"><a href="#status.417" id="rfc.xref.status.417.1" title="417 Expectation Failed">Section&nbsp;6.5.14</a></td>
    23182309               </tr>
    23192310               <tr>
    23202311                  <td class="left">426</td>
    23212312                  <td class="left">Upgrade Required</td>
    2322                   <td class="left"><a href="#status.426" id="rfc.xref.status.426.1" title="426 Upgrade Required">Section&nbsp;7.5.15</a></td>
     2313                  <td class="left"><a href="#status.426" id="rfc.xref.status.426.1" title="426 Upgrade Required">Section&nbsp;6.5.15</a></td>
    23232314               </tr>
    23242315               <tr>
    23252316                  <td class="left">500</td>
    23262317                  <td class="left">Internal Server Error</td>
    2327                   <td class="left"><a href="#status.500" id="rfc.xref.status.500.1" title="500 Internal Server Error">Section&nbsp;7.6.1</a></td>
     2318                  <td class="left"><a href="#status.500" id="rfc.xref.status.500.1" title="500 Internal Server Error">Section&nbsp;6.6.1</a></td>
    23282319               </tr>
    23292320               <tr>
    23302321                  <td class="left">501</td>
    23312322                  <td class="left">Not Implemented</td>
    2332                   <td class="left"><a href="#status.501" id="rfc.xref.status.501.1" title="501 Not Implemented">Section&nbsp;7.6.2</a></td>
     2323                  <td class="left"><a href="#status.501" id="rfc.xref.status.501.1" title="501 Not Implemented">Section&nbsp;6.6.2</a></td>
    23332324               </tr>
    23342325               <tr>
    23352326                  <td class="left">502</td>
    23362327                  <td class="left">Bad Gateway</td>
    2337                   <td class="left"><a href="#status.502" id="rfc.xref.status.502.1" title="502 Bad Gateway">Section&nbsp;7.6.3</a></td>
     2328                  <td class="left"><a href="#status.502" id="rfc.xref.status.502.1" title="502 Bad Gateway">Section&nbsp;6.6.3</a></td>
    23382329               </tr>
    23392330               <tr>
    23402331                  <td class="left">503</td>
    23412332                  <td class="left">Service Unavailable</td>
    2342                   <td class="left"><a href="#status.503" id="rfc.xref.status.503.1" title="503 Service Unavailable">Section&nbsp;7.6.4</a></td>
     2333                  <td class="left"><a href="#status.503" id="rfc.xref.status.503.1" title="503 Service Unavailable">Section&nbsp;6.6.4</a></td>
    23432334               </tr>
    23442335               <tr>
    23452336                  <td class="left">504</td>
    23462337                  <td class="left">Gateway Time-out</td>
    2347                   <td class="left"><a href="#status.504" id="rfc.xref.status.504.1" title="504 Gateway Timeout">Section&nbsp;7.6.5</a></td>
     2338                  <td class="left"><a href="#status.504" id="rfc.xref.status.504.1" title="504 Gateway Timeout">Section&nbsp;6.6.5</a></td>
    23482339               </tr>
    23492340               <tr>
    23502341                  <td class="left">505</td>
    23512342                  <td class="left">HTTP Version not supported</td>
    2352                   <td class="left"><a href="#status.505" id="rfc.xref.status.505.1" title="505 HTTP Version Not Supported">Section&nbsp;7.6.6</a></td>
     2343                  <td class="left"><a href="#status.505" id="rfc.xref.status.505.1" title="505 HTTP Version Not Supported">Section&nbsp;6.6.6</a></td>
    23532344               </tr>
    23542345            </tbody>
    23552346         </table>
    23562347      </div>
    2357       <p id="rfc.section.7.1.p.2">Note that this list is not exhaustive — it does not include extension status codes defined in other specifications.</p>
    2358       <h2 id="rfc.section.7.2"><a href="#rfc.section.7.2">7.2</a>&nbsp;<a id="status.1xx" href="#status.1xx">Informational 1xx</a></h2>
     2348      <p id="rfc.section.6.1.p.2">Note that this list is not exhaustive — it does not include extension status codes defined in other specifications.</p>
     2349      <h2 id="rfc.section.6.2"><a href="#rfc.section.6.2">6.2</a>&nbsp;<a id="status.1xx" href="#status.1xx">Informational 1xx</a></h2>
    23592350      <div id="rfc.iref.70"></div>
    23602351      <div id="rfc.iref.s.2"></div>
    2361       <p id="rfc.section.7.2.p.1">This class of status code indicates a provisional response, consisting only of the status-line and optional header fields,
     2352      <p id="rfc.section.6.2.p.1">This class of status code indicates a provisional response, consisting only of the status-line and optional header fields,
    23622353         and is terminated by an empty line. There are no required header fields for this class of status code. Since HTTP/1.0 did
    23632354         not define any 1xx status codes, servers <em class="bcp14">MUST NOT</em> send a 1xx response to an HTTP/1.0 client except under experimental conditions.
    23642355      </p>
    2365       <p id="rfc.section.7.2.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 <a href="#status.100" class="smpl">100
     2356      <p id="rfc.section.6.2.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 <a href="#status.100" class="smpl">100
    23662357            (Continue)</a> status message. Unexpected 1xx status responses <em class="bcp14">MAY</em> be ignored by a user agent.
    23672358      </p>
    2368       <p id="rfc.section.7.2.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
     2359      <p id="rfc.section.6.2.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
    23692360         requested the generation of the 1xx response. (For example, if a proxy adds an "Expect: 100-continue" field when it forwards
    23702361         a request, then it need not forward the corresponding <a href="#status.100" class="smpl">100 (Continue)</a> response(s).)
    23712362      </p>
    23722363      <div id="rfc.iref.71"></div>
    2373       <h3 id="rfc.section.7.2.1"><a href="#rfc.section.7.2.1">7.2.1</a>&nbsp;<a id="status.100" href="#status.100">100 Continue</a></h3>
    2374       <p id="rfc.section.7.2.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
     2364      <h3 id="rfc.section.6.2.1"><a href="#rfc.section.6.2.1">6.2.1</a>&nbsp;<a id="status.100" href="#status.100">100 Continue</a></h3>
     2365      <p id="rfc.section.6.2.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
    23752366         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
    2376          server <em class="bcp14">MUST</em> send a final response after the request has been completed. See <a href="#use.of.the.100.status" title="Use of the 100 (Continue) Status">Section&nbsp;6.1.2.1</a> for detailed discussion of the use and handling of this status code.
     2367         server <em class="bcp14">MUST</em> send a final response after the request has been completed. See <a href="#use.of.the.100.status" title="Use of the 100 (Continue) Status">Section&nbsp;5.1.2.1</a> for detailed discussion of the use and handling of this status code.
    23772368      </p>
    23782369      <div id="rfc.iref.71"></div>
    2379       <h3 id="rfc.section.7.2.2"><a href="#rfc.section.7.2.2">7.2.2</a>&nbsp;<a id="status.101" href="#status.101">101 Switching Protocols</a></h3>
    2380       <p id="rfc.section.7.2.2.p.1">The server understands and is willing to comply with the client's request, via the <a href="p1-messaging.html#header.upgrade" class="smpl">Upgrade</a> message header field (<a href="p1-messaging.html#header.upgrade" title="Upgrade">Section 6.7</a> of <a href="#Part1" id="rfc.xref.Part1.22"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>), for a change in the application protocol being used on this connection. The server will switch protocols to those defined
     2370      <h3 id="rfc.section.6.2.2"><a href="#rfc.section.6.2.2">6.2.2</a>&nbsp;<a id="status.101" href="#status.101">101 Switching Protocols</a></h3>
     2371      <p id="rfc.section.6.2.2.p.1">The server understands and is willing to comply with the client's request, via the <a href="p1-messaging.html#header.upgrade" class="smpl">Upgrade</a> message header field (<a href="p1-messaging.html#header.upgrade" title="Upgrade">Section 6.7</a> of <a href="#Part1" id="rfc.xref.Part1.22"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>), for a change in the application protocol being used on this connection. The server will switch protocols to those defined
    23812372         by the response's Upgrade header field immediately after the empty line which terminates the 101 response.
    23822373      </p>
    2383       <p id="rfc.section.7.2.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
     2374      <p id="rfc.section.6.2.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
    23842375         older versions, and switching to a real-time, synchronous protocol might be advantageous when delivering resources that use
    23852376         such features.
    23862377      </p>
    2387       <h2 id="rfc.section.7.3"><a href="#rfc.section.7.3">7.3</a>&nbsp;<a id="status.2xx" href="#status.2xx">Successful 2xx</a></h2>
     2378      <h2 id="rfc.section.6.3"><a href="#rfc.section.6.3">6.3</a>&nbsp;<a id="status.2xx" href="#status.2xx">Successful 2xx</a></h2>
    23882379      <div id="rfc.iref.71"></div>
    23892380      <div id="rfc.iref.s.3"></div>
    2390       <p id="rfc.section.7.3.p.1">This class of status code indicates that the client's request was successfully received, understood, and accepted.</p>
     2381      <p id="rfc.section.6.3.p.1">This class of status code indicates that the client's request was successfully received, understood, and accepted.</p>
    23912382      <div id="rfc.iref.72"></div>
    2392       <h3 id="rfc.section.7.3.1"><a href="#rfc.section.7.3.1">7.3.1</a>&nbsp;<a id="status.200" href="#status.200">200 OK</a></h3>
    2393       <p id="rfc.section.7.3.1.p.1">The request has succeeded. The payload returned with the response is dependent on the method used in the request, for example: </p>
     2383      <h3 id="rfc.section.6.3.1"><a href="#rfc.section.6.3.1">6.3.1</a>&nbsp;<a id="status.200" href="#status.200">200 OK</a></h3>
     2384      <p id="rfc.section.6.3.1.p.1">The request has succeeded. The payload returned with the response is dependent on the method used in the request, for example: </p>
    23942385      <dl>
    23952386         <dt>GET</dt>
     
    24022393         <dd>a representation containing the request message as received by the end server.</dd>
    24032394      </dl>
    2404       <p id="rfc.section.7.3.1.p.2">Caches <em class="bcp14">MAY</em> use a heuristic (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 4.1.2</a> of <a href="#Part6" id="rfc.xref.Part6.8"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>) to determine freshness for 200 responses.
     2395      <p id="rfc.section.6.3.1.p.2">Caches <em class="bcp14">MAY</em> use a heuristic (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 4.1.2</a> of <a href="#Part6" id="rfc.xref.Part6.8"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>) to determine freshness for 200 responses.
    24052396      </p>
    24062397      <div id="rfc.iref.72"></div>
    2407       <h3 id="rfc.section.7.3.2"><a href="#rfc.section.7.3.2">7.3.2</a>&nbsp;<a id="status.201" href="#status.201">201 Created</a></h3>
    2408       <p id="rfc.section.7.3.2.p.1">The request has been fulfilled and has resulted in one or more new resources being created.</p>
    2409       <p id="rfc.section.7.3.2.p.2">Newly created resources are typically linked to from the response payload, with the most relevant URI also being carried in
     2398      <h3 id="rfc.section.6.3.2"><a href="#rfc.section.6.3.2">6.3.2</a>&nbsp;<a id="status.201" href="#status.201">201 Created</a></h3>
     2399      <p id="rfc.section.6.3.2.p.1">The request has been fulfilled and has resulted in one or more new resources being created.</p>
     2400      <p id="rfc.section.6.3.2.p.2">Newly created resources are typically linked to from the response payload, with the most relevant URI also being carried in
    24102401         the <a href="#header.location" class="smpl">Location</a> header field. If the newly created resource's URI is the same as the Effective Request URI, this information can be omitted
    24112402         (e.g., in the case of a response to a PUT request).
    24122403      </p>
    2413       <p id="rfc.section.7.3.2.p.3">The origin server <em class="bcp14">MUST</em> create the resource(s) before returning the 201 status code. If the action cannot be carried out immediately, the server <em class="bcp14">SHOULD</em> respond with a <a href="#status.202" class="smpl">202 (Accepted)</a> response instead.
    2414       </p>
    2415       <p id="rfc.section.7.3.2.p.4">A 201 response <em class="bcp14">MAY</em> contain an <a href="p4-conditional.html#header.etag" class="smpl">ETag</a> response header field indicating the current value of the entity-tag for the representation of the resource identified by
     2404      <p id="rfc.section.6.3.2.p.3">The origin server <em class="bcp14">MUST</em> create the resource(s) before returning the 201 status code. If the action cannot be carried out immediately, the server <em class="bcp14">SHOULD</em> respond with a <a href="#status.202" class="smpl">202 (Accepted)</a> response instead.
     2405      </p>
     2406      <p id="rfc.section.6.3.2.p.4">A 201 response <em class="bcp14">MAY</em> contain an <a href="p4-conditional.html#header.etag" class="smpl">ETag</a> response header field indicating the current value of the entity-tag for the representation of the resource identified by
    24162407         the <a href="#header.location" class="smpl">Location</a> header field or, in case the Location header field was omitted, by the Effective Request URI (see <a href="p4-conditional.html#header.etag" title="ETag">Section 2.3</a> of <a href="#Part4" id="rfc.xref.Part4.10"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests">[Part4]</cite></a>).
    24172408      </p>
    24182409      <div id="rfc.iref.72"></div>
    2419       <h3 id="rfc.section.7.3.3"><a href="#rfc.section.7.3.3">7.3.3</a>&nbsp;<a id="status.202" href="#status.202">202 Accepted</a></h3>
    2420       <p id="rfc.section.7.3.3.p.1">The request has been accepted for processing, but the processing has not been completed. The request might or might not eventually
     2410      <h3 id="rfc.section.6.3.3"><a href="#rfc.section.6.3.3">6.3.3</a>&nbsp;<a id="status.202" href="#status.202">202 Accepted</a></h3>
     2411      <p id="rfc.section.6.3.3.p.1">The request has been accepted for processing, but the processing has not been completed. The request might or might not eventually
    24212412         be acted upon, as it might be disallowed when processing actually takes place. There is no facility for re-sending a status
    24222413         code from an asynchronous operation such as this.
    24232414      </p>
    2424       <p id="rfc.section.7.3.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
     2415      <p id="rfc.section.6.3.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
    24252416         (perhaps a batch-oriented process that is only run once per day) without requiring that the user agent's connection to the
    24262417         server persist until the process is completed. The representation 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
     
    24282419      </p>
    24292420      <div id="rfc.iref.72"></div>
    2430       <h3 id="rfc.section.7.3.4"><a href="#rfc.section.7.3.4">7.3.4</a>&nbsp;<a id="status.203" href="#status.203">203 Non-Authoritative Information</a></h3>
    2431       <p id="rfc.section.7.3.4.p.1">The request was successful but the enclosed payload has been modified from that of the origin server's <a href="#status.200" class="smpl">200 (OK)</a> response by a transforming proxy (<a href="p1-messaging.html#message.transformations" title="Transformations">Section 5.7.2</a> of <a href="#Part1" id="rfc.xref.Part1.23"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>). This status code allows the proxy to notify recipients when a transformation has been applied, since that knowledge might
     2421      <h3 id="rfc.section.6.3.4"><a href="#rfc.section.6.3.4">6.3.4</a>&nbsp;<a id="status.203" href="#status.203">203 Non-Authoritative Information</a></h3>
     2422      <p id="rfc.section.6.3.4.p.1">The request was successful but the enclosed payload has been modified from that of the origin server's <a href="#status.200" class="smpl">200 (OK)</a> response by a transforming proxy (<a href="p1-messaging.html#message.transformations" title="Transformations">Section 5.7.2</a> of <a href="#Part1" id="rfc.xref.Part1.23"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>). This status code allows the proxy to notify recipients when a transformation has been applied, since that knowledge might
    24322423         impact later decisions regarding the content. For example, future cache validation requests for the content might only be
    24332424         applicable along the same request path (through the same proxies).
    24342425      </p>
    2435       <p id="rfc.section.7.3.4.p.2">The 203 response is similar to the Warning code of 214 Transformation Applied (<a href="p6-cache.html#header.warning" title="Warning">Section 7.5</a> of <a href="#Part6" id="rfc.xref.Part6.9"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>), which has the advantage of being applicable to responses with any status code.
     2426      <p id="rfc.section.6.3.4.p.2">The 203 response is similar to the Warning code of 214 Transformation Applied (<a href="p6-cache.html#header.warning" title="Warning">Section 7.5</a> of <a href="#Part6" id="rfc.xref.Part6.9"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>), which has the advantage of being applicable to responses with any status code.
    24362427      </p>
    24372428      <div id="rfc.iref.72"></div>
    2438       <h3 id="rfc.section.7.3.5"><a href="#rfc.section.7.3.5">7.3.5</a>&nbsp;<a id="status.204" href="#status.204">204 No Content</a></h3>
    2439       <p id="rfc.section.7.3.5.p.1">The 204 (No Content) status code indicates that the server has successfully fulfilled the request and that there is no additional
     2429      <h3 id="rfc.section.6.3.5"><a href="#rfc.section.6.3.5">6.3.5</a>&nbsp;<a id="status.204" href="#status.204">204 No Content</a></h3>
     2430      <p id="rfc.section.6.3.5.p.1">The 204 (No Content) status code indicates that the server has successfully fulfilled the request and that there is no additional
    24402431         content to return in the response payload body. Metadata in the response header fields refer to the target resource and its
    24412432         current representation after the requested action.
    24422433      </p>
    2443       <p id="rfc.section.7.3.5.p.2">For example, if a 204 status code is received in response to a PUT request and the response contains an <a href="p4-conditional.html#header.etag" class="smpl">ETag</a> header field, then the PUT was successful and the ETag field-value contains the entity-tag for the new representation of that
     2434      <p id="rfc.section.6.3.5.p.2">For example, if a 204 status code is received in response to a PUT request and the response contains an <a href="p4-conditional.html#header.etag" class="smpl">ETag</a> header field, then the PUT was successful and the ETag field-value contains the entity-tag for the new representation of that
    24442435         target resource.
    24452436      </p>
    2446       <p id="rfc.section.7.3.5.p.3">The 204 response allows a server to indicate that the action has been successfully applied to the target resource while implying
     2437      <p id="rfc.section.6.3.5.p.3">The 204 response allows a server to indicate that the action has been successfully applied to the target resource while implying
    24472438         that the user agent <em class="bcp14">SHOULD NOT</em> traverse away from its current "document view" (if any). The server assumes that the user agent will provide some indication
    24482439         of the success to its user, in accord with its own interface, and apply any new or updated metadata in the response to the
    24492440         active representation.
    24502441      </p>
    2451       <p id="rfc.section.7.3.5.p.4">For example, a 204 status code is commonly used with document editing interfaces corresponding to a "save" action, such that
     2442      <p id="rfc.section.6.3.5.p.4">For example, a 204 status code is commonly used with document editing interfaces corresponding to a "save" action, such that
    24522443         the document being saved remains available to the user for editing. It is also frequently used with interfaces that expect
    24532444         automated data transfers to be prevalent, such as within distributed version control systems.
    24542445      </p>
    2455       <p id="rfc.section.7.3.5.p.5">The 204 response <em class="bcp14">MUST NOT</em> include a message body, and thus is always terminated by the first empty line after the header fields.
     2446      <p id="rfc.section.6.3.5.p.5">The 204 response <em class="bcp14">MUST NOT</em> include a message body, and thus is always terminated by the first empty line after the header fields.
    24562447      </p>
    24572448      <div id="rfc.iref.72"></div>
    2458       <h3 id="rfc.section.7.3.6"><a href="#rfc.section.7.3.6">7.3.6</a>&nbsp;<a id="status.205" href="#status.205">205 Reset Content</a></h3>
    2459       <p id="rfc.section.7.3.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
     2449      <h3 id="rfc.section.6.3.6"><a href="#rfc.section.6.3.6">6.3.6</a>&nbsp;<a id="status.205" href="#status.205">205 Reset Content</a></h3>
     2450      <p id="rfc.section.6.3.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
    24602451         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
    24612452         another input action.
    24622453      </p>
    2463       <p id="rfc.section.7.3.6.p.2">The message body included with the response <em class="bcp14">MUST</em> be empty. Note that receivers still need to parse the response according to the algorithm defined in <a href="p1-messaging.html#message.body" title="Message Body">Section 3.3</a> of <a href="#Part1" id="rfc.xref.Part1.24"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>.
    2464       </p>
    2465       <h2 id="rfc.section.7.4"><a href="#rfc.section.7.4">7.4</a>&nbsp;<a id="status.3xx" href="#status.3xx">Redirection 3xx</a></h2>
     2454      <p id="rfc.section.6.3.6.p.2">The message body included with the response <em class="bcp14">MUST</em> be empty. Note that receivers still need to parse the response according to the algorithm defined in <a href="p1-messaging.html#message.body" title="Message Body">Section 3.3</a> of <a href="#Part1" id="rfc.xref.Part1.24"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>.
     2455      </p>
     2456      <h2 id="rfc.section.6.4"><a href="#rfc.section.6.4">6.4</a>&nbsp;<a id="status.3xx" href="#status.3xx">Redirection 3xx</a></h2>
    24662457      <div id="rfc.iref.72"></div>
    24672458      <div id="rfc.iref.s.4"></div>
    2468       <p id="rfc.section.7.4.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.</p>
    2469       <p id="rfc.section.7.4.p.2">There are several types of redirects: </p>
     2459      <p id="rfc.section.6.4.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.</p>
     2460      <p id="rfc.section.6.4.p.2">There are several types of redirects: </p>
    24702461      <ol>
    24712462         <li>
     
    24902481         </li>
    24912482      </ol>
    2492       <div class="note" id="rfc.section.7.4.p.3">
     2483      <div class="note" id="rfc.section.6.4.p.3">
    24932484         <p> <b>Note:</b> In HTTP/1.0, only the status codes <a href="#status.301" class="smpl">301 (Moved Permanently)</a> and <a href="#status.302" class="smpl">302 (Found)</a> were defined for the first type of redirect, and the second type did not exist at all (<a href="#RFC1945" id="rfc.xref.RFC1945.1"><cite title="Hypertext Transfer Protocol -- HTTP/1.0">[RFC1945]</cite></a>, <a href="http://tools.ietf.org/html/rfc1945#section-9.3">Section 9.3</a>). However it turned out that web forms using POST expected redirects to change the operation for the subsequent request to
    24942485            retrieval (GET). To address this use case, HTTP/1.1 introduced the second type of redirect with the status code <a href="#status.303" class="smpl">303 (See Other)</a> (<a href="#RFC2068" id="rfc.xref.RFC2068.2"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a>, <a href="http://tools.ietf.org/html/rfc2068#section-10.3.4">Section 10.3.4</a>). As user agents did not change their behavior to maintain backwards compatibility, the first revision of HTTP/1.1 added
     
    24962487         </p>
    24972488      </div>
    2498       <p id="rfc.section.7.4.p.4">A <a href="#header.location" class="smpl">Location</a> header field on a 3xx response indicates that a client <em class="bcp14">MAY</em> automatically redirect to the URI provided; see <a href="#header.location" id="rfc.xref.header.location.2" title="Location">Section&nbsp;8.1.2</a>.
    2499       </p>
    2500       <p id="rfc.section.7.4.p.5">Note that for methods not known to be "safe", as defined in <a href="#safe.methods" title="Safe Methods">Section&nbsp;5.2.1</a>, automatic redirection needs to done with care, since the redirect might change the conditions under which the request was
     2489      <p id="rfc.section.6.4.p.4">A <a href="#header.location" class="smpl">Location</a> header field on a 3xx response indicates that a client <em class="bcp14">MAY</em> automatically redirect to the URI provided; see <a href="#header.location" id="rfc.xref.header.location.2" title="Location">Section&nbsp;7.1.2</a>.
     2490      </p>
     2491      <p id="rfc.section.6.4.p.5">Note that for methods not known to be "safe", as defined in <a href="#safe.methods" title="Safe Methods">Section&nbsp;4.2.1</a>, automatic redirection needs to done with care, since the redirect might change the conditions under which the request was
    25012492         issued.
    25022493      </p>
    2503       <p id="rfc.section.7.4.p.6">Clients <em class="bcp14">SHOULD</em> detect and intervene in cyclical redirections (i.e., "infinite" redirection loops).
    2504       </p>
    2505       <div class="note" id="rfc.section.7.4.p.7">
     2494      <p id="rfc.section.6.4.p.6">Clients <em class="bcp14">SHOULD</em> detect and intervene in cyclical redirections (i.e., "infinite" redirection loops).
     2495      </p>
     2496      <div class="note" id="rfc.section.6.4.p.7">
    25062497         <p> <b>Note:</b> An earlier version of this specification recommended a maximum of five redirections (<a href="#RFC2068" id="rfc.xref.RFC2068.3"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a>, <a href="http://tools.ietf.org/html/rfc2068#section-10.3">Section 10.3</a>). Content developers need to be aware that some clients might implement such a fixed limitation.
    25072498         </p>
    25082499      </div>
    25092500      <div id="rfc.iref.73"></div>
    2510       <h3 id="rfc.section.7.4.1"><a href="#rfc.section.7.4.1">7.4.1</a>&nbsp;<a id="status.300" href="#status.300">300 Multiple Choices</a></h3>
    2511       <p id="rfc.section.7.4.1.p.1">The target resource has more than one representation, each with its own specific location, and reactive negotiation information
     2501      <h3 id="rfc.section.6.4.1"><a href="#rfc.section.6.4.1">6.4.1</a>&nbsp;<a id="status.300" href="#status.300">300 Multiple Choices</a></h3>
     2502      <p id="rfc.section.6.4.1.p.1">The target resource has more than one representation, each with its own specific location, and reactive negotiation information
    25122503         (<a href="#content.negotiation" title="Content Negotiation">Section&nbsp;3.4</a>) is being provided so that the user (or user agent) can select a preferred representation by redirecting its request to that
    25132504         location.
    25142505      </p>
    2515       <p id="rfc.section.7.4.1.p.2">Unless it was a HEAD request, the response <em class="bcp14">SHOULD</em> include a representation containing a list of representation metadata and location(s) from which the user or user agent can
     2506      <p id="rfc.section.6.4.1.p.2">Unless it was a HEAD request, the response <em class="bcp14">SHOULD</em> include a representation containing a list of representation metadata and location(s) from which the user or user agent can
    25162507         choose the one most appropriate. Depending upon the format and the capabilities of the user agent, selection of the most appropriate
    25172508         choice <em class="bcp14">MAY</em> be performed automatically. However, this specification does not define any standard for such automatic selection.
    25182509      </p>
    2519       <p id="rfc.section.7.4.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 <a href="#header.location" class="smpl">Location</a> field; user agents <em class="bcp14">MAY</em> use the Location field value for automatic redirection.
    2520       </p>
    2521       <p id="rfc.section.7.4.1.p.4">Caches <em class="bcp14">MAY</em> use a heuristic (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 4.1.2</a> of <a href="#Part6" id="rfc.xref.Part6.10"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>) to determine freshness for 300 responses.
     2510      <p id="rfc.section.6.4.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 <a href="#header.location" class="smpl">Location</a> field; user agents <em class="bcp14">MAY</em> use the Location field value for automatic redirection.
     2511      </p>
     2512      <p id="rfc.section.6.4.1.p.4">Caches <em class="bcp14">MAY</em> use a heuristic (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 4.1.2</a> of <a href="#Part6" id="rfc.xref.Part6.10"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>) to determine freshness for 300 responses.
    25222513      </p>
    25232514      <div id="rfc.iref.73"></div>
    2524       <h3 id="rfc.section.7.4.2"><a href="#rfc.section.7.4.2">7.4.2</a>&nbsp;<a id="status.301" href="#status.301">301 Moved Permanently</a></h3>
    2525       <p id="rfc.section.7.4.2.p.1">The target resource has been assigned a new permanent URI and any future references to this resource <em class="bcp14">SHOULD</em> use one of the returned URIs. Clients with link editing capabilities ought to automatically re-link references to the effective
     2515      <h3 id="rfc.section.6.4.2"><a href="#rfc.section.6.4.2">6.4.2</a>&nbsp;<a id="status.301" href="#status.301">301 Moved Permanently</a></h3>
     2516      <p id="rfc.section.6.4.2.p.1">The target resource has been assigned a new permanent URI and any future references to this resource <em class="bcp14">SHOULD</em> use one of the returned URIs. Clients with link editing capabilities ought to automatically re-link references to the effective
    25262517         request URI to one or more of the new references returned by the server, where possible.
    25272518      </p>
    2528       <p id="rfc.section.7.4.2.p.2">Caches <em class="bcp14">MAY</em> use a heuristic (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 4.1.2</a> of <a href="#Part6" id="rfc.xref.Part6.11"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>) to determine freshness for 301 responses.
    2529       </p>
    2530       <p id="rfc.section.7.4.2.p.3">The new permanent URI <em class="bcp14">SHOULD</em> be given by the <a href="#header.location" class="smpl">Location</a> field in the response. A response payload can contain a short hypertext note with a hyperlink to the new URI(s).
    2531       </p>
    2532       <div class="note" id="rfc.section.7.4.2.p.4">
     2519      <p id="rfc.section.6.4.2.p.2">Caches <em class="bcp14">MAY</em> use a heuristic (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 4.1.2</a> of <a href="#Part6" id="rfc.xref.Part6.11"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>) to determine freshness for 301 responses.
     2520      </p>
     2521      <p id="rfc.section.6.4.2.p.3">The new permanent URI <em class="bcp14">SHOULD</em> be given by the <a href="#header.location" class="smpl">Location</a> field in the response. A response payload can contain a short hypertext note with a hyperlink to the new URI(s).
     2522      </p>
     2523      <div class="note" id="rfc.section.6.4.2.p.4">
    25332524         <p> <b>Note:</b> For historic reasons, user agents <em class="bcp14">MAY</em> change the request method from POST to GET for the subsequent request. If this behavior is undesired, status code <a href="#status.307" class="smpl">307 (Temporary Redirect)</a> can be used instead.
    25342525         </p>
    25352526      </div>
    25362527      <div id="rfc.iref.73"></div>
    2537       <h3 id="rfc.section.7.4.3"><a href="#rfc.section.7.4.3">7.4.3</a>&nbsp;<a id="status.302" href="#status.302">302 Found</a></h3>
    2538       <p id="rfc.section.7.4.3.p.1">The target resource resides temporarily under a different URI. Since the redirection might be altered on occasion, the client <em class="bcp14">SHOULD</em> continue to use the effective request URI for future requests.
    2539       </p>
    2540       <p id="rfc.section.7.4.3.p.2">The temporary URI <em class="bcp14">SHOULD</em> be given by the <a href="#header.location" class="smpl">Location</a> field in the response. A response payload can contain a short hypertext note with a hyperlink to the new URI(s).
    2541       </p>
    2542       <div class="note" id="rfc.section.7.4.3.p.3">
     2528      <h3 id="rfc.section.6.4.3"><a href="#rfc.section.6.4.3">6.4.3</a>&nbsp;<a id="status.302" href="#status.302">302 Found</a></h3>
     2529      <p id="rfc.section.6.4.3.p.1">The target resource resides temporarily under a different URI. Since the redirection might be altered on occasion, the client <em class="bcp14">SHOULD</em> continue to use the effective request URI for future requests.
     2530      </p>
     2531      <p id="rfc.section.6.4.3.p.2">The temporary URI <em class="bcp14">SHOULD</em> be given by the <a href="#header.location" class="smpl">Location</a> field in the response. A response payload can contain a short hypertext note with a hyperlink to the new URI(s).
     2532      </p>
     2533      <div class="note" id="rfc.section.6.4.3.p.3">
    25432534         <p> <b>Note:</b> For historic reasons, user agents <em class="bcp14">MAY</em> change the request method from POST to GET for the subsequent request. If this behavior is undesired, status code <a href="#status.307" class="smpl">307 (Temporary Redirect)</a> can be used instead.
    25442535         </p>
    25452536      </div>
    25462537      <div id="rfc.iref.73"></div>
    2547       <h3 id="rfc.section.7.4.4"><a href="#rfc.section.7.4.4">7.4.4</a>&nbsp;<a id="status.303" href="#status.303">303 See Other</a></h3>
    2548       <p id="rfc.section.7.4.4.p.1">The 303 status code indicates that the server is redirecting the user agent to a different resource, as indicated by a URI
     2538      <h3 id="rfc.section.6.4.4"><a href="#rfc.section.6.4.4">6.4.4</a>&nbsp;<a id="status.303" href="#status.303">303 See Other</a></h3>
     2539      <p id="rfc.section.6.4.4.p.1">The 303 status code indicates that the server is redirecting the user agent to a different resource, as indicated by a URI
    25492540         in the <a href="#header.location" class="smpl">Location</a> header field, that is intended to provide an indirect response to the original request. In order to satisfy the original request,
    25502541         a user agent <em class="bcp14">SHOULD</em> perform a retrieval request using the Location URI (a GET or HEAD request if using HTTP), which can itself be redirected further,
     
    25522543         not considered equivalent to the effective request URI.
    25532544      </p>
    2554       <p id="rfc.section.7.4.4.p.2">This status code is generally applicable to any HTTP method. It is primarily used to allow the output of a POST action to
     2545      <p id="rfc.section.6.4.4.p.2">This status code is generally applicable to any HTTP method. It is primarily used to allow the output of a POST action to
    25552546         redirect the user agent to a selected resource, since doing so provides the information corresponding to the POST response
    25562547         in a form that can be separately identified, bookmarked, and cached independent of the original request.
    25572548      </p>
    2558       <p id="rfc.section.7.4.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
     2549      <p id="rfc.section.6.4.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
    25592550         transferred by the server over HTTP. The <a href="#header.location" class="smpl">Location</a> URI indicates a resource that is descriptive of the target resource, such that the follow-on representation might be useful
    25602551         to recipients without implying that it adequately represents the target resource. Note that answers to the questions of what
     
    25622553         and thus entirely determined by the URI owner(s).
    25632554      </p>
    2564       <p id="rfc.section.7.4.4.p.4">Except for responses to a HEAD request, the representation of a 303 response <em class="bcp14">SHOULD</em> contain a short hypertext note with a hyperlink to the <a href="#header.location" class="smpl">Location</a> URI.
     2555      <p id="rfc.section.6.4.4.p.4">Except for responses to a HEAD request, the representation of a 303 response <em class="bcp14">SHOULD</em> contain a short hypertext note with a hyperlink to the <a href="#header.location" class="smpl">Location</a> URI.
    25652556      </p>
    25662557      <div id="rfc.iref.73"></div>
    2567       <h3 id="rfc.section.7.4.5"><a href="#rfc.section.7.4.5">7.4.5</a>&nbsp;<a id="status.305" href="#status.305">305 Use Proxy</a></h3>
    2568       <p id="rfc.section.7.4.5.p.1">The 305 status code was defined in a previous version of this specification (see <a href="#changes.from.rfc.2616" title="Changes from RFC 2616">Appendix&nbsp;C</a>), and is now deprecated.
     2558      <h3 id="rfc.section.6.4.5"><a href="#rfc.section.6.4.5">6.4.5</a>&nbsp;<a id="status.305" href="#status.305">305 Use Proxy</a></h3>
     2559      <p id="rfc.section.6.4.5.p.1">The 305 status code was defined in a previous version of this specification (see <a href="#changes.from.rfc.2616" title="Changes from RFC 2616">Appendix&nbsp;C</a>), and is now deprecated.
    25692560      </p>
    25702561      <div id="rfc.iref.73"></div>
    2571       <h3 id="rfc.section.7.4.6"><a href="#rfc.section.7.4.6">7.4.6</a>&nbsp;<a id="status.306" href="#status.306">306 (Unused)</a></h3>
    2572       <p id="rfc.section.7.4.6.p.1">The 306 status code was used in a previous version of the specification, is no longer used, and the code is reserved.</p>
     2562      <h3 id="rfc.section.6.4.6"><a href="#rfc.section.6.4.6">6.4.6</a>&nbsp;<a id="status.306" href="#status.306">306 (Unused)</a></h3>
     2563      <p id="rfc.section.6.4.6.p.1">The 306 status code was used in a previous version of the specification, is no longer used, and the code is reserved.</p>
    25732564      <div id="rfc.iref.73"></div>
    2574       <h3 id="rfc.section.7.4.7"><a href="#rfc.section.7.4.7">7.4.7</a>&nbsp;<a id="status.307" href="#status.307">307 Temporary Redirect</a></h3>
    2575       <p id="rfc.section.7.4.7.p.1">The target resource resides temporarily under a different URI. Since the redirection can change over time, the client <em class="bcp14">SHOULD</em> continue to use the effective request URI for future requests.
    2576       </p>
    2577       <p id="rfc.section.7.4.7.p.2">The temporary URI <em class="bcp14">SHOULD</em> be given by the <a href="#header.location" class="smpl">Location</a> field in the response. A response payload can contain a short hypertext note with a hyperlink to the new URI(s).
    2578       </p>
    2579       <div class="note" id="rfc.section.7.4.7.p.3">
     2565      <h3 id="rfc.section.6.4.7"><a href="#rfc.section.6.4.7">6.4.7</a>&nbsp;<a id="status.307" href="#status.307">307 Temporary Redirect</a></h3>
     2566      <p id="rfc.section.6.4.7.p.1">The target resource resides temporarily under a different URI. Since the redirection can change over time, the client <em class="bcp14">SHOULD</em> continue to use the effective request URI for future requests.
     2567      </p>
     2568      <p id="rfc.section.6.4.7.p.2">The temporary URI <em class="bcp14">SHOULD</em> be given by the <a href="#header.location" class="smpl">Location</a> field in the response. A response payload can contain a short hypertext note with a hyperlink to the new URI(s).
     2569      </p>
     2570      <div class="note" id="rfc.section.6.4.7.p.3">
    25802571         <p> <b>Note:</b> This status code is similar to <a href="#status.302" class="smpl">302 (Found)</a>, except that it does not allow rewriting the request method from POST to GET. This specification defines no equivalent counterpart
    25812572            for <a href="#status.301" class="smpl">301 (Moved
     
    25832574         </p>
    25842575      </div>
    2585       <h2 id="rfc.section.7.5"><a href="#rfc.section.7.5">7.5</a>&nbsp;<a id="status.4xx" href="#status.4xx">Client Error 4xx</a></h2>
     2576      <h2 id="rfc.section.6.5"><a href="#rfc.section.6.5">6.5</a>&nbsp;<a id="status.4xx" href="#status.4xx">Client Error 4xx</a></h2>
    25862577      <div id="rfc.iref.73"></div>
    25872578      <div id="rfc.iref.s.5"></div>
    2588       <p id="rfc.section.7.5.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
     2579      <p id="rfc.section.6.5.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
    25892580         request, the server <em class="bcp14">SHOULD</em> include a representation containing an explanation of the error situation, and whether it is a temporary or permanent condition.
    25902581         These status codes are applicable to any request method. User agents <em class="bcp14">SHOULD</em> display any included representation to the user.
    25912582      </p>
    25922583      <div id="rfc.iref.74"></div>
    2593       <h3 id="rfc.section.7.5.1"><a href="#rfc.section.7.5.1">7.5.1</a>&nbsp;<a id="status.400" href="#status.400">400 Bad Request</a></h3>
    2594       <p id="rfc.section.7.5.1.p.1">The server cannot or will not process the request, due to a client error (e.g., malformed syntax).</p>
     2584      <h3 id="rfc.section.6.5.1"><a href="#rfc.section.6.5.1">6.5.1</a>&nbsp;<a id="status.400" href="#status.400">400 Bad Request</a></h3>
     2585      <p id="rfc.section.6.5.1.p.1">The server cannot or will not process the request, due to a client error (e.g., malformed syntax).</p>
    25952586      <div id="rfc.iref.74"></div>
    2596       <h3 id="rfc.section.7.5.2"><a href="#rfc.section.7.5.2">7.5.2</a>&nbsp;<a id="status.402" href="#status.402">402 Payment Required</a></h3>
    2597       <p id="rfc.section.7.5.2.p.1">This code is reserved for future use.</p>
     2587      <h3 id="rfc.section.6.5.2"><a href="#rfc.section.6.5.2">6.5.2</a>&nbsp;<a id="status.402" href="#status.402">402 Payment Required</a></h3>
     2588      <p id="rfc.section.6.5.2.p.1">This code is reserved for future use.</p>
    25982589      <div id="rfc.iref.74"></div>
    2599       <h3 id="rfc.section.7.5.3"><a href="#rfc.section.7.5.3">7.5.3</a>&nbsp;<a id="status.403" href="#status.403">403 Forbidden</a></h3>
    2600       <p id="rfc.section.7.5.3.p.1">The server understood the request, but refuses to authorize it. Providing different user authentication credentials might
     2590      <h3 id="rfc.section.6.5.3"><a href="#rfc.section.6.5.3">6.5.3</a>&nbsp;<a id="status.403" href="#status.403">403 Forbidden</a></h3>
     2591      <p id="rfc.section.6.5.3.p.1">The server understood the request, but refuses to authorize it. Providing different user authentication credentials might
    26012592         be successful, but any credentials that were provided in the request are insufficient. The request <em class="bcp14">SHOULD NOT</em> be repeated with the same credentials.
    26022593      </p>
    2603       <p id="rfc.section.7.5.3.p.2">If the request method was not HEAD and the server wishes to make public why the request has not been fulfilled, it <em class="bcp14">SHOULD</em> describe the reason for the refusal in the representation. If the server does not wish to make this information available
     2594      <p id="rfc.section.6.5.3.p.2">If the request method was not HEAD and the server wishes to make public why the request has not been fulfilled, it <em class="bcp14">SHOULD</em> describe the reason for the refusal in the representation. If the server does not wish to make this information available
    26042595         to the client, the status code <a href="#status.404" class="smpl">404
    26052596            (Not Found)</a>  <em class="bcp14">MAY</em> be used instead.
    26062597      </p>
    26072598      <div id="rfc.iref.74"></div>
    2608       <h3 id="rfc.section.7.5.4"><a href="#rfc.section.7.5.4">7.5.4</a>&nbsp;<a id="status.404" href="#status.404">404 Not Found</a></h3>
    2609       <p id="rfc.section.7.5.4.p.1">The server has not found anything matching the effective request URI. No indication is given of whether the condition is temporary
     2599      <h3 id="rfc.section.6.5.4"><a href="#rfc.section.6.5.4">6.5.4</a>&nbsp;<a id="status.404" href="#status.404">404 Not Found</a></h3>
     2600      <p id="rfc.section.6.5.4.p.1">The server has not found anything matching the effective request URI. No indication is given of whether the condition is temporary
    26102601         or permanent. The <a href="#status.410" class="smpl">410 (Gone)</a> 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
    26112602         and has no forwarding address. This status code is commonly used when the server does not wish to reveal exactly why the request
     
    26132604      </p>
    26142605      <div id="rfc.iref.74"></div>
    2615       <h3 id="rfc.section.7.5.5"><a href="#rfc.section.7.5.5">7.5.5</a>&nbsp;<a id="status.405" href="#status.405">405 Method Not Allowed</a></h3>
    2616       <p id="rfc.section.7.5.5.p.1">The method specified in the request-line is not allowed for the target resource. The response <em class="bcp14">MUST</em> include an <a href="#header.allow" class="smpl">Allow</a> header field containing a list of valid methods for the requested resource.
     2606      <h3 id="rfc.section.6.5.5"><a href="#rfc.section.6.5.5">6.5.5</a>&nbsp;<a id="status.405" href="#status.405">405 Method Not Allowed</a></h3>
     2607      <p id="rfc.section.6.5.5.p.1">The method specified in the request-line is not allowed for the target resource. The response <em class="bcp14">MUST</em> include an <a href="#header.allow" class="smpl">Allow</a> header field containing a list of valid methods for the requested resource.
    26172608      </p>
    26182609      <div id="rfc.iref.74"></div>
    2619       <h3 id="rfc.section.7.5.6"><a href="#rfc.section.7.5.6">7.5.6</a>&nbsp;<a id="status.406" href="#status.406">406 Not Acceptable</a></h3>
    2620       <p id="rfc.section.7.5.6.p.1">The resource identified by the request is only capable of generating response representations which have content characteristics
     2610      <h3 id="rfc.section.6.5.6"><a href="#rfc.section.6.5.6">6.5.6</a>&nbsp;<a id="status.406" href="#status.406">406 Not Acceptable</a></h3>
     2611      <p id="rfc.section.6.5.6.p.1">The resource identified by the request is only capable of generating response representations which have content characteristics
    26212612         not acceptable according to the <a href="#header.accept" class="smpl">Accept</a> and Accept-* header fields sent in the request.
    26222613      </p>
    2623       <p id="rfc.section.7.5.6.p.2">Unless it was a HEAD request, the response <em class="bcp14">SHOULD</em> include a representation containing a list of available representation characteristics and location(s) from which the user
     2614      <p id="rfc.section.6.5.6.p.2">Unless it was a HEAD request, the response <em class="bcp14">SHOULD</em> include a representation containing a list of available representation characteristics and location(s) from which the user
    26242615         or user agent can choose the one most appropriate. Depending upon the format and the capabilities of the user agent, selection
    26252616         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.
    26262617      </p>
    2627       <div class="note" id="rfc.section.7.5.6.p.3">
     2618      <div class="note" id="rfc.section.6.5.6.p.3">
    26282619         <p> <b>Note:</b> HTTP/1.1 servers are allowed to return responses which are not acceptable according to the accept header fields sent in the
    26292620            request. In some cases, this might even be preferable to sending a 406 response. User agents are encouraged to inspect the
     
    26312622         </p>
    26322623      </div>
    2633       <p id="rfc.section.7.5.6.p.4">If the response could be unacceptable, a user agent <em class="bcp14">SHOULD</em> temporarily stop receipt of more data and query the user for a decision on further actions.
     2624      <p id="rfc.section.6.5.6.p.4">If the response could be unacceptable, a user agent <em class="bcp14">SHOULD</em> temporarily stop receipt of more data and query the user for a decision on further actions.
    26342625      </p>
    26352626      <div id="rfc.iref.74"></div>
    2636       <h3 id="rfc.section.7.5.7"><a href="#rfc.section.7.5.7">7.5.7</a>&nbsp;<a id="status.408" href="#status.408">408 Request Timeout</a></h3>
    2637       <p id="rfc.section.7.5.7.p.1">The server did not receive a complete request message within the time that it was prepared to wait. If the client has sent
     2627      <h3 id="rfc.section.6.5.7"><a href="#rfc.section.6.5.7">6.5.7</a>&nbsp;<a id="status.408" href="#status.408">408 Request Timeout</a></h3>
     2628      <p id="rfc.section.6.5.7.p.1">The server did not receive a complete request message within the time that it was prepared to wait. If the client has sent
    26382629         a request, it <em class="bcp14">MAY</em> repeat that request, possibly on a new connection if the server indicates that the present connection is being closed.
    26392630      </p>
    26402631      <div id="rfc.iref.74"></div>
    2641       <h3 id="rfc.section.7.5.8"><a href="#rfc.section.7.5.8">7.5.8</a>&nbsp;<a id="status.409" href="#status.409">409 Conflict</a></h3>
    2642       <p id="rfc.section.7.5.8.p.1">The request could not be completed due to a conflict with the current state of the resource. This code is only allowed in
     2632      <h3 id="rfc.section.6.5.8"><a href="#rfc.section.6.5.8">6.5.8</a>&nbsp;<a id="status.409" href="#status.409">409 Conflict</a></h3>
     2633      <p id="rfc.section.6.5.8.p.1">The request could not be completed due to a conflict with the current state of the resource. This code is only allowed in
    26432634         situations where it is expected that the user might be able to resolve the conflict and resubmit the request. The payload <em class="bcp14">SHOULD</em> include enough information for the user to recognize the source of the conflict. Ideally, the response representation would
    26442635         include enough information for the user or user agent to fix the problem; however, that might not be possible and is not required.
    26452636      </p>
    2646       <p id="rfc.section.7.5.8.p.2">Conflicts are most likely to occur in response to a PUT request. For example, if versioning were being used and the representation
     2637      <p id="rfc.section.6.5.8.p.2">Conflicts are most likely to occur in response to a PUT request. For example, if versioning were being used and the representation
    26472638         being PUT included changes to a resource which conflict with those made by an earlier (third-party) request, the server might
    26482639         use the 409 response to indicate that it can't complete the request. In this case, the response representation would likely
     
    26502641      </p>
    26512642      <div id="rfc.iref.74"></div>
    2652       <h3 id="rfc.section.7.5.9"><a href="#rfc.section.7.5.9">7.5.9</a>&nbsp;<a id="status.410" href="#status.410">410 Gone</a></h3>
    2653       <p id="rfc.section.7.5.9.p.1">The target resource is no longer available at the server and no forwarding address is known. This condition is expected to
     2643      <h3 id="rfc.section.6.5.9"><a href="#rfc.section.6.5.9">6.5.9</a>&nbsp;<a id="status.410" href="#status.410">410 Gone</a></h3>
     2644      <p id="rfc.section.6.5.9.p.1">The target resource is no longer available at the server and no forwarding address is known. This condition is expected to
    26542645         be considered permanent. Clients with link editing capabilities <em class="bcp14">SHOULD</em> delete references to the effective request URI after user approval. If the server does not know, or has no facility to determine,
    26552646         whether or not the condition is permanent, the status code <a href="#status.404" class="smpl">404 (Not Found)</a>  <em class="bcp14">SHOULD</em> be used instead.
    26562647      </p>
    2657       <p id="rfc.section.7.5.9.p.2">The 410 response is primarily intended to assist the task of web maintenance by notifying the recipient that the resource
     2648      <p id="rfc.section.6.5.9.p.2">The 410 response is primarily intended to assist the task of web maintenance by notifying the recipient that the resource
    26582649         is intentionally unavailable and that the server owners desire that remote links to that resource be removed. Such an event
    26592650         is common for limited-time, promotional services and for resources belonging to individuals no longer working at the server's
     
    26612652         — that is left to the discretion of the server owner.
    26622653      </p>
    2663       <p id="rfc.section.7.5.9.p.3">Caches <em class="bcp14">MAY</em> use a heuristic (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 4.1.2</a> of <a href="#Part6" id="rfc.xref.Part6.12"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>) to determine freshness for 410 responses.
     2654      <p id="rfc.section.6.5.9.p.3">Caches <em class="bcp14">MAY</em> use a heuristic (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 4.1.2</a> of <a href="#Part6" id="rfc.xref.Part6.12"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>) to determine freshness for 410 responses.
    26642655      </p>
    26652656      <div id="rfc.iref.74"></div>
    2666       <h3 id="rfc.section.7.5.10"><a href="#rfc.section.7.5.10">7.5.10</a>&nbsp;<a id="status.411" href="#status.411">411 Length Required</a></h3>
    2667       <p id="rfc.section.7.5.10.p.1">The server refuses to accept the request without a defined <a href="p1-messaging.html#header.content-length" class="smpl">Content-Length</a>. 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
     2657      <h3 id="rfc.section.6.5.10"><a href="#rfc.section.6.5.10">6.5.10</a>&nbsp;<a id="status.411" href="#status.411">411 Length Required</a></h3>
     2658      <p id="rfc.section.6.5.10.p.1">The server refuses to accept the request without a defined <a href="p1-messaging.html#header.content-length" class="smpl">Content-Length</a>. 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
    26682659         message.
    26692660      </p>
    26702661      <div id="rfc.iref.74"></div>
    2671       <h3 id="rfc.section.7.5.11"><a href="#rfc.section.7.5.11">7.5.11</a>&nbsp;<a id="status.413" href="#status.413">413 Request Representation Too Large</a></h3>
    2672       <p id="rfc.section.7.5.11.p.1">The server is refusing to process a request because the request representation is larger than the server is willing or able
     2662      <h3 id="rfc.section.6.5.11"><a href="#rfc.section.6.5.11">6.5.11</a>&nbsp;<a id="status.413" href="#status.413">413 Request Representation Too Large</a></h3>
     2663      <p id="rfc.section.6.5.11.p.1">The server is refusing to process a request because the request representation is larger than the server is willing or able
    26732664         to process. The server <em class="bcp14">MAY</em> close the connection to prevent the client from continuing the request.
    26742665      </p>
    2675       <p id="rfc.section.7.5.11.p.2">If the condition is temporary, the server <em class="bcp14">SHOULD</em> include a <a href="#header.retry-after" class="smpl">Retry-After</a> header field to indicate that it is temporary and after what time the client <em class="bcp14">MAY</em> try again.
     2666      <p id="rfc.section.6.5.11.p.2">If the condition is temporary, the server <em class="bcp14">SHOULD</em> include a <a href="#header.retry-after" class="smpl">Retry-After</a> header field to indicate that it is temporary and after what time the client <em class="bcp14">MAY</em> try again.
    26762667      </p>
    26772668      <div id="rfc.iref.74"></div>
    2678       <h3 id="rfc.section.7.5.12"><a href="#rfc.section.7.5.12">7.5.12</a>&nbsp;<a id="status.414" href="#status.414">414 URI Too Long</a></h3>
    2679       <p id="rfc.section.7.5.12.p.1">The server is refusing to service the request because the effective request URI is longer than the server is willing to interpret.
     2669      <h3 id="rfc.section.6.5.12"><a href="#rfc.section.6.5.12">6.5.12</a>&nbsp;<a id="status.414" href="#status.414">414 URI Too Long</a></h3>
     2670      <p id="rfc.section.6.5.12.p.1">The server is refusing to service the request because the effective request URI is longer than the server is willing to interpret.
    26802671         This rare condition is only likely to occur when a client has improperly converted a POST request to a GET request with long
    26812672         query information, when the client has descended into a URI "black hole" of redirection (e.g., a redirected URI prefix that
     
    26842675      </p>
    26852676      <div id="rfc.iref.74"></div>
    2686       <h3 id="rfc.section.7.5.13"><a href="#rfc.section.7.5.13">7.5.13</a>&nbsp;<a id="status.415" href="#status.415">415 Unsupported Media Type</a></h3>
    2687       <p id="rfc.section.7.5.13.p.1">The server is refusing to service the request because the request payload is in a format not supported by this request method
     2677      <h3 id="rfc.section.6.5.13"><a href="#rfc.section.6.5.13">6.5.13</a>&nbsp;<a id="status.415" href="#status.415">415 Unsupported Media Type</a></h3>
     2678      <p id="rfc.section.6.5.13.p.1">The server is refusing to service the request because the request payload is in a format not supported by this request method
    26882679         on the target resource. The format problem might be due to the request's indicated <a href="#header.content-type" class="smpl">Content-Type</a> or <a href="#header.content-encoding" class="smpl">Content-Encoding</a>, or as a result of inspecting the data directly.
    26892680      </p>
    26902681      <div id="rfc.iref.74"></div>
    2691       <h3 id="rfc.section.7.5.14"><a href="#rfc.section.7.5.14">7.5.14</a>&nbsp;<a id="status.417" href="#status.417">417 Expectation Failed</a></h3>
    2692       <p id="rfc.section.7.5.14.p.1">The expectation given in an <a href="#header.expect" class="smpl">Expect</a> header field (see <a href="#header.expect" id="rfc.xref.header.expect.2" title="Expect">Section&nbsp;6.1.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
     2682      <h3 id="rfc.section.6.5.14"><a href="#rfc.section.6.5.14">6.5.14</a>&nbsp;<a id="status.417" href="#status.417">417 Expectation Failed</a></h3>
     2683      <p id="rfc.section.6.5.14.p.1">The expectation given in an <a href="#header.expect" class="smpl">Expect</a> header field (see <a href="#header.expect" id="rfc.xref.header.expect.2" title="Expect">Section&nbsp;5.1.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
    26932684         not be met by the next-hop server.
    26942685      </p>
    26952686      <div id="rfc.iref.74"></div>
    2696       <h3 id="rfc.section.7.5.15"><a href="#rfc.section.7.5.15">7.5.15</a>&nbsp;<a id="status.426" href="#status.426">426 Upgrade Required</a></h3>
    2697       <p id="rfc.section.7.5.15.p.1">The request can not be completed without a prior protocol upgrade. This response <em class="bcp14">MUST</em> include an <a href="p1-messaging.html#header.upgrade" class="smpl">Upgrade</a> header field (<a href="p1-messaging.html#header.upgrade" title="Upgrade">Section 6.7</a> of <a href="#Part1" id="rfc.xref.Part1.25"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>) specifying the required protocols.
    2698       </p>
    2699       <div id="rfc.figure.u.42"></div>
     2687      <h3 id="rfc.section.6.5.15"><a href="#rfc.section.6.5.15">6.5.15</a>&nbsp;<a id="status.426" href="#status.426">426 Upgrade Required</a></h3>
     2688      <p id="rfc.section.6.5.15.p.1">The request can not be completed without a prior protocol upgrade. This response <em class="bcp14">MUST</em> include an <a href="p1-messaging.html#header.upgrade" class="smpl">Upgrade</a> header field (<a href="p1-messaging.html#header.upgrade" title="Upgrade">Section 6.7</a> of <a href="#Part1" id="rfc.xref.Part1.25"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>) specifying the required protocols.
     2689      </p>
     2690      <div id="rfc.figure.u.41"></div>
    27002691      <p>Example:</p>  <pre class="text">HTTP/1.1 426 Upgrade Required
    27012692Upgrade: HTTP/3.0
     
    27052696
    27062697<span id="s426body">This service requires use of the HTTP/3.0 protocol.
    2707 </span></pre><p id="rfc.section.7.5.15.p.3">The server <em class="bcp14">SHOULD</em> include a message body in the 426 response which indicates in human readable form the reason for the error and describes any
     2698</span></pre><p id="rfc.section.6.5.15.p.3">The server <em class="bcp14">SHOULD</em> include a message body in the 426 response which indicates in human readable form the reason for the error and describes any
    27082699         alternative courses which might be available to the user.
    27092700      </p>
    2710       <h2 id="rfc.section.7.6"><a href="#rfc.section.7.6">7.6</a>&nbsp;<a id="status.5xx" href="#status.5xx">Server Error 5xx</a></h2>
     2701      <h2 id="rfc.section.6.6"><a href="#rfc.section.6.6">6.6</a>&nbsp;<a id="status.5xx" href="#status.5xx">Server Error 5xx</a></h2>
    27112702      <div id="rfc.iref.74"></div>
    27122703      <div id="rfc.iref.s.6"></div>
    2713       <p id="rfc.section.7.6.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
     2704      <p id="rfc.section.6.6.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
    27142705         of performing the request. Except when responding to a HEAD request, the server <em class="bcp14">SHOULD</em> include a representation containing an explanation of the error situation, and whether it is a temporary or permanent condition.
    27152706         User agents <em class="bcp14">SHOULD</em> display any included representation to the user. These response codes are applicable to any request method.
    27162707      </p>
    27172708      <div id="rfc.iref.75"></div>
    2718       <h3 id="rfc.section.7.6.1"><a href="#rfc.section.7.6.1">7.6.1</a>&nbsp;<a id="status.500" href="#status.500">500 Internal Server Error</a></h3>
    2719       <p id="rfc.section.7.6.1.p.1">The server encountered an unexpected condition which prevented it from fulfilling the request.</p>
     2709      <h3 id="rfc.section.6.6.1"><a href="#rfc.section.6.6.1">6.6.1</a>&nbsp;<a id="status.500" href="#status.500">500 Internal Server Error</a></h3>
     2710      <p id="rfc.section.6.6.1.p.1">The server encountered an unexpected condition which prevented it from fulfilling the request.</p>
    27202711      <div id="rfc.iref.75"></div>
    2721       <h3 id="rfc.section.7.6.2"><a href="#rfc.section.7.6.2">7.6.2</a>&nbsp;<a id="status.501" href="#status.501">501 Not Implemented</a></h3>
    2722       <p id="rfc.section.7.6.2.p.1">The server does not support the functionality required to fulfill the request. This is the appropriate response when the server
     2712      <h3 id="rfc.section.6.6.2"><a href="#rfc.section.6.6.2">6.6.2</a>&nbsp;<a id="status.501" href="#status.501">501 Not Implemented</a></h3>
     2713      <p id="rfc.section.6.6.2.p.1">The server does not support the functionality required to fulfill the request. This is the appropriate response when the server
    27232714         does not recognize the request method and is not capable of supporting it for any resource.
    27242715      </p>
    27252716      <div id="rfc.iref.75"></div>
    2726       <h3 id="rfc.section.7.6.3"><a href="#rfc.section.7.6.3">7.6.3</a>&nbsp;<a id="status.502" href="#status.502">502 Bad Gateway</a></h3>
    2727       <p id="rfc.section.7.6.3.p.1">The server, while acting as a gateway or proxy, received an invalid response from the upstream server it accessed in attempting
     2717      <h3 id="rfc.section.6.6.3"><a href="#rfc.section.6.6.3">6.6.3</a>&nbsp;<a id="status.502" href="#status.502">502 Bad Gateway</a></h3>
     2718      <p id="rfc.section.6.6.3.p.1">The server, while acting as a gateway or proxy, received an invalid response from the upstream server it accessed in attempting
    27282719         to fulfill the request.
    27292720      </p>
    27302721      <div id="rfc.iref.75"></div>
    2731       <h3 id="rfc.section.7.6.4"><a href="#rfc.section.7.6.4">7.6.4</a>&nbsp;<a id="status.503" href="#status.503">503 Service Unavailable</a></h3>
    2732       <p id="rfc.section.7.6.4.p.1">The server is currently unable to handle the request due to a temporary overloading or maintenance of the server.</p>
    2733       <p id="rfc.section.7.6.4.p.2">The implication is that this is a temporary condition which will be alleviated after some delay. If known, the length of the
    2734          delay <em class="bcp14">MAY</em> be indicated in a <a href="#header.retry-after" class="smpl">Retry-After</a> header field (<a href="#header.retry-after" id="rfc.xref.header.retry-after.1" title="Retry-After">Section&nbsp;8.1.3</a>). If no Retry-After is given, the client <em class="bcp14">SHOULD</em> handle the response as it would for a <a href="#status.500" class="smpl">500 (Internal
     2722      <h3 id="rfc.section.6.6.4"><a href="#rfc.section.6.6.4">6.6.4</a>&nbsp;<a id="status.503" href="#status.503">503 Service Unavailable</a></h3>
     2723      <p id="rfc.section.6.6.4.p.1">The server is currently unable to handle the request due to a temporary overloading or maintenance of the server.</p>
     2724      <p id="rfc.section.6.6.4.p.2">The implication is that this is a temporary condition which will be alleviated after some delay. If known, the length of the
     2725         delay <em class="bcp14">MAY</em> be indicated in a <a href="#header.retry-after" class="smpl">Retry-After</a> header field (<a href="#header.retry-after" id="rfc.xref.header.retry-after.1" title="Retry-After">Section&nbsp;7.1.3</a>). If no Retry-After is given, the client <em class="bcp14">SHOULD</em> handle the response as it would for a <a href="#status.500" class="smpl">500 (Internal
    27352726            Server Error)</a> response.
    27362727      </p>
    2737       <div class="note" id="rfc.section.7.6.4.p.3">
     2728      <div class="note" id="rfc.section.6.6.4.p.3">
    27382729         <p> <b>Note:</b> The existence of the 503 status code does not imply that a server has to use it when becoming overloaded. Some servers might
    27392730            wish to simply refuse the connection.
     
    27412732      </div>
    27422733      <div id="rfc.iref.75"></div>
    2743       <h3 id="rfc.section.7.6.5"><a href="#rfc.section.7.6.5">7.6.5</a>&nbsp;<a id="status.504" href="#status.504">504 Gateway Timeout</a></h3>
    2744       <p id="rfc.section.7.6.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
     2734      <h3 id="rfc.section.6.6.5"><a href="#rfc.section.6.6.5">6.6.5</a>&nbsp;<a id="status.504" href="#status.504">504 Gateway Timeout</a></h3>
     2735      <p id="rfc.section.6.6.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
    27452736         URI (e.g., HTTP, FTP, LDAP) or some other auxiliary server (e.g., DNS) it needed to access in attempting to complete the request.
    27462737      </p>
    2747       <div class="note" id="rfc.section.7.6.5.p.2">
     2738      <div class="note" id="rfc.section.6.6.5.p.2">
    27482739         <p> <b>Note</b> to implementers: some deployed proxies are known to return <a href="#status.400" class="smpl">400 (Bad Request)</a> or <a href="#status.500" class="smpl">500 (Internal Server
    27492740               Error)</a> when DNS lookups time out.
     
    27512742      </div>
    27522743      <div id="rfc.iref.75"></div>
    2753       <h3 id="rfc.section.7.6.6"><a href="#rfc.section.7.6.6">7.6.6</a>&nbsp;<a id="status.505" href="#status.505">505 HTTP Version Not Supported</a></h3>
    2754       <p id="rfc.section.7.6.6.p.1">The server does not support, or refuses to support, the protocol version that was used in the request message. The server
     2744      <h3 id="rfc.section.6.6.6"><a href="#rfc.section.6.6.6">6.6.6</a>&nbsp;<a id="status.505" href="#status.505">505 HTTP Version Not Supported</a></h3>
     2745      <p id="rfc.section.6.6.6.p.1">The server does not support, or refuses to support, the protocol version that was used in the request message. The server
    27552746         is indicating that it is unable or unwilling to complete the request using the same major version as the client, as described
    27562747         in <a href="p1-messaging.html#http.version" title="Protocol Versioning">Section 2.6</a> of <a href="#Part1" id="rfc.xref.Part1.26"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>, other than with this error message. The response <em class="bcp14">SHOULD</em> contain a representation describing why that version is not supported and what other protocols are supported by that server.
    27572748      </p>
    2758       <h1 id="rfc.section.8"><a href="#rfc.section.8">8.</a>&nbsp;<a id="response.header.fields" href="#response.header.fields">Response Header Fields</a></h1>
    2759       <p id="rfc.section.8.p.1">The response header fields allow the server to pass additional information about the response which cannot be placed in the
     2749      <h1 id="rfc.section.7"><a href="#rfc.section.7">7.</a>&nbsp;<a id="response.header.fields" href="#response.header.fields">Response Header Fields</a></h1>
     2750      <p id="rfc.section.7.p.1">The response header fields allow the server to pass additional information about the response which cannot be placed in the
    27602751         status-line. These header fields give information about the server and about further access to the target resource (<a href="p1-messaging.html#effective.request.uri" title="Effective Request URI">Section 5.5</a> of <a href="#Part1" id="rfc.xref.Part1.27"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>).
    27612752      </p>
    2762       <h2 id="rfc.section.8.1"><a href="#rfc.section.8.1">8.1</a>&nbsp;<a id="response.control.data" href="#response.control.data">Control Data</a></h2>
    2763       <p id="rfc.section.8.1.p.1">Response header fields can supply control data that supplements the status code or instructs the client where to go next.</p>
     2753      <h2 id="rfc.section.7.1"><a href="#rfc.section.7.1">7.1</a>&nbsp;<a id="response.control.data" href="#response.control.data">Control Data</a></h2>
     2754      <p id="rfc.section.7.1.p.1">Response header fields can supply control data that supplements the status code or instructs the client where to go next.</p>
    27642755      <div id="rfc.table.u.10">
    27652756         <table class="tt full left" cellpadding="3" cellspacing="0">
     
    27772768               <tr>
    27782769                  <td class="left">Date</td>
    2779                   <td class="left"><a href="#header.date" id="rfc.xref.header.date.2" title="Date">Section&nbsp;8.1.1.2</a></td>
     2770                  <td class="left"><a href="#header.date" id="rfc.xref.header.date.2" title="Date">Section&nbsp;7.1.1.2</a></td>
    27802771               </tr>
    27812772               <tr>
    27822773                  <td class="left">Location</td>
    2783                   <td class="left"><a href="#header.location" id="rfc.xref.header.location.3" title="Location">Section&nbsp;8.1.2</a></td>
     2774                  <td class="left"><a href="#header.location" id="rfc.xref.header.location.3" title="Location">Section&nbsp;7.1.2</a></td>
    27842775               </tr>
    27852776               <tr>
    27862777                  <td class="left">Retry-After</td>
    2787                   <td class="left"><a href="#header.retry-after" id="rfc.xref.header.retry-after.2" title="Retry-After">Section&nbsp;8.1.3</a></td>
     2778                  <td class="left"><a href="#header.retry-after" id="rfc.xref.header.retry-after.2" title="Retry-After">Section&nbsp;7.1.3</a></td>
    27882779               </tr>
    27892780            </tbody>
    27902781         </table>
    27912782      </div>
    2792       <h3 id="rfc.section.8.1.1"><a href="#rfc.section.8.1.1">8.1.1</a>&nbsp;<a id="origination.date" href="#origination.date">Origination Date</a></h3>
    2793       <h4 id="rfc.section.8.1.1.1"><a href="#rfc.section.8.1.1.1">8.1.1.1</a>&nbsp;<a id="http.date" href="#http.date">Date/Time Formats</a></h4>
    2794       <p id="rfc.section.8.1.1.1.p.1">HTTP applications have historically allowed three different formats for date/time stamps. However, the preferred format is
     2783      <h3 id="rfc.section.7.1.1"><a href="#rfc.section.7.1.1">7.1.1</a>&nbsp;<a id="origination.date" href="#origination.date">Origination Date</a></h3>
     2784      <h4 id="rfc.section.7.1.1.1"><a href="#rfc.section.7.1.1.1">7.1.1.1</a>&nbsp;<a id="http.date" href="#http.date">Date/Time Formats</a></h4>
     2785      <p id="rfc.section.7.1.1.1.p.1">HTTP applications have historically allowed three different formats for date/time stamps. However, the preferred format is
    27952786         a fixed-length subset of that defined by <a href="#RFC1123" id="rfc.xref.RFC1123.1"><cite title="Requirements for Internet Hosts - Application and Support">[RFC1123]</cite></a>:
    27962787      </p>
    2797       <div id="rfc.figure.u.43"></div><pre class="text">Sun, 06 Nov 1994 08:49:37 GMT  ; RFC 1123
    2798 </pre><p id="rfc.section.8.1.1.1.p.3">The other formats are described here only for compatibility with obsolete implementations.</p>
    2799       <div id="rfc.figure.u.44"></div><pre class="text">Sunday, 06-Nov-94 08:49:37 GMT ; obsolete RFC 850 format
     2788      <div id="rfc.figure.u.42"></div><pre class="text">Sun, 06 Nov 1994 08:49:37 GMT  ; RFC 1123
     2789</pre><p id="rfc.section.7.1.1.1.p.3">The other formats are described here only for compatibility with obsolete implementations.</p>
     2790      <div id="rfc.figure.u.43"></div><pre class="text">Sunday, 06-Nov-94 08:49:37 GMT ; obsolete RFC 850 format
    28002791Sun Nov  6 08:49:37 1994       ; ANSI C's asctime() format
    2801 </pre><p id="rfc.section.8.1.1.1.p.5">HTTP/1.1 clients and servers that parse a date value <em class="bcp14">MUST</em> accept all three formats (for compatibility with HTTP/1.0), though they <em class="bcp14">MUST</em> only generate the RFC 1123 format for representing HTTP-date values in header fields.
    2802       </p>
    2803       <p id="rfc.section.8.1.1.1.p.6">All HTTP date/time stamps <em class="bcp14">MUST</em> be represented in Greenwich Mean Time (GMT), without exception. For the purposes of HTTP, GMT is exactly equal to UTC (Coordinated
     2792</pre><p id="rfc.section.7.1.1.1.p.5">HTTP/1.1 clients and servers that parse a date value <em class="bcp14">MUST</em> accept all three formats (for compatibility with HTTP/1.0), though they <em class="bcp14">MUST</em> only generate the RFC 1123 format for representing HTTP-date values in header fields.
     2793      </p>
     2794      <p id="rfc.section.7.1.1.1.p.6">All HTTP date/time stamps <em class="bcp14">MUST</em> be represented in Greenwich Mean Time (GMT), without exception. For the purposes of HTTP, GMT is exactly equal to UTC (Coordinated
    28042795         Universal Time). This is indicated in the first two formats by the inclusion of "GMT" as the three-letter abbreviation for
    28052796         time zone, and <em class="bcp14">MUST</em> be assumed when reading the asctime format. HTTP-date is case sensitive and <em class="bcp14">MUST NOT</em> include additional whitespace beyond that specifically included as SP in the grammar.
    28062797      </p>
    2807       <div id="rfc.figure.u.45"></div><pre class="inline"><span id="rfc.iref.g.39"></span>  <a href="#http.date" class="smpl">HTTP-date</a>    = <a href="#preferred.date.format" class="smpl">rfc1123-date</a> / <a href="#obsolete.date.formats" class="smpl">obs-date</a>
     2798      <div id="rfc.figure.u.44"></div><pre class="inline"><span id="rfc.iref.g.39"></span>  <a href="#http.date" class="smpl">HTTP-date</a>    = <a href="#preferred.date.format" class="smpl">rfc1123-date</a> / <a href="#obsolete.date.formats" class="smpl">obs-date</a>
    28082799</pre><div id="preferred.date.format">
    2809          <p id="rfc.section.8.1.1.1.p.8">                    Preferred format:</p>
     2800         <p id="rfc.section.7.1.1.1.p.8">                    Preferred format:</p>
    28102801      </div>
    2811       <div id="rfc.figure.u.46"></div><pre class="inline"><span id="rfc.iref.g.40"></span><span id="rfc.iref.g.41"></span><span id="rfc.iref.g.42"></span><span id="rfc.iref.g.43"></span><span id="rfc.iref.g.44"></span><span id="rfc.iref.g.45"></span><span id="rfc.iref.g.46"></span><span id="rfc.iref.g.47"></span><span id="rfc.iref.g.48"></span><span id="rfc.iref.g.49"></span><span id="rfc.iref.g.50"></span><span id="rfc.iref.g.51"></span>  <a href="#preferred.date.format" class="smpl">rfc1123-date</a> = <a href="#preferred.date.format" class="smpl">day-name</a> "," <a href="#imported.abnf" class="smpl">SP</a> date1 <a href="#imported.abnf" class="smpl">SP</a> <a href="#preferred.date.format" class="smpl">time-of-day</a> <a href="#imported.abnf" class="smpl">SP</a> <a href="#preferred.date.format" class="smpl">GMT</a>
     2802      <div id="rfc.figure.u.45"></div><pre class="inline"><span id="rfc.iref.g.40"></span><span id="rfc.iref.g.41"></span><span id="rfc.iref.g.42"></span><span id="rfc.iref.g.43"></span><span id="rfc.iref.g.44"></span><span id="rfc.iref.g.45"></span><span id="rfc.iref.g.46"></span><span id="rfc.iref.g.47"></span><span id="rfc.iref.g.48"></span><span id="rfc.iref.g.49"></span><span id="rfc.iref.g.50"></span><span id="rfc.iref.g.51"></span>  <a href="#preferred.date.format" class="smpl">rfc1123-date</a> = <a href="#preferred.date.format" class="smpl">day-name</a> "," <a href="#imported.abnf" class="smpl">SP</a> date1 <a href="#imported.abnf" class="smpl">SP</a> <a href="#preferred.date.format" class="smpl">time-of-day</a> <a href="#imported.abnf" class="smpl">SP</a> <a href="#preferred.date.format" class="smpl">GMT</a>
    28122803  ; fixed length subset of the format defined in
    28132804  ; <a href="http://tools.ietf.org/html/rfc1123#section-5.2.14">Section 5.2.14</a> of <a href="#RFC1123" id="rfc.xref.RFC1123.2"><cite title="Requirements for Internet Hosts - Application and Support">[RFC1123]</cite></a>
     
    28472838  <a href="#preferred.date.format" class="smpl">minute</a>       = 2<a href="#imported.abnf" class="smpl">DIGIT</a>               
    28482839  <a href="#preferred.date.format" class="smpl">second</a>       = 2<a href="#imported.abnf" class="smpl">DIGIT</a>               
    2849 </pre><p id="rfc.section.8.1.1.1.p.10">The semantics of <a href="#preferred.date.format" class="smpl">day-name</a>, <a href="#preferred.date.format" class="smpl">day</a>, <a href="#preferred.date.format" class="smpl">month</a>, <a href="#preferred.date.format" class="smpl">year</a>, and <a href="#preferred.date.format" class="smpl">time-of-day</a> are the same as those defined for the RFC 5322 constructs with the corresponding name (<a href="#RFC5322" id="rfc.xref.RFC5322.3"><cite title="Internet Message Format">[RFC5322]</cite></a>, <a href="http://tools.ietf.org/html/rfc5322#section-3.3">Section 3.3</a>).
     2840</pre><p id="rfc.section.7.1.1.1.p.10">The semantics of <a href="#preferred.date.format" class="smpl">day-name</a>, <a href="#preferred.date.format" class="smpl">day</a>, <a href="#preferred.date.format" class="smpl">month</a>, <a href="#preferred.date.format" class="smpl">year</a>, and <a href="#preferred.date.format" class="smpl">time-of-day</a> are the same as those defined for the RFC 5322 constructs with the corresponding name (<a href="#RFC5322" id="rfc.xref.RFC5322.3"><cite title="Internet Message Format">[RFC5322]</cite></a>, <a href="http://tools.ietf.org/html/rfc5322#section-3.3">Section 3.3</a>).
    28502841      </p>
    28512842      <div id="obsolete.date.formats">
    2852          <p id="rfc.section.8.1.1.1.p.11">              Obsolete formats:</p>
     2843         <p id="rfc.section.7.1.1.1.p.11">              Obsolete formats:</p>
    28532844      </div>
    2854       <div id="rfc.figure.u.47"></div><pre class="inline"><span id="rfc.iref.g.52"></span>  <a href="#obsolete.date.formats" class="smpl">obs-date</a>     = <a href="#obsolete.date.formats" class="smpl">rfc850-date</a> / <a href="#obsolete.date.formats" class="smpl">asctime-date</a>
    2855 </pre><div id="rfc.figure.u.48"></div><pre class="inline"><span id="rfc.iref.g.53"></span>  <a href="#obsolete.date.formats" class="smpl">rfc850-date</a>  = <a href="#obsolete.date.formats" class="smpl">day-name-l</a> "," <a href="#imported.abnf" class="smpl">SP</a> <a href="#obsolete.date.formats" class="smpl">date2</a> <a href="#imported.abnf" class="smpl">SP</a> <a href="#preferred.date.format" class="smpl">time-of-day</a> <a href="#imported.abnf" class="smpl">SP</a> <a href="#preferred.date.format" class="smpl">GMT</a>
     2845      <div id="rfc.figure.u.46"></div><pre class="inline"><span id="rfc.iref.g.52"></span>  <a href="#obsolete.date.formats" class="smpl">obs-date</a>     = <a href="#obsolete.date.formats" class="smpl">rfc850-date</a> / <a href="#obsolete.date.formats" class="smpl">asctime-date</a>
     2846</pre><div id="rfc.figure.u.47"></div><pre class="inline"><span id="rfc.iref.g.53"></span>  <a href="#obsolete.date.formats" class="smpl">rfc850-date</a>  = <a href="#obsolete.date.formats" class="smpl">day-name-l</a> "," <a href="#imported.abnf" class="smpl">SP</a> <a href="#obsolete.date.formats" class="smpl">date2</a> <a href="#imported.abnf" class="smpl">SP</a> <a href="#preferred.date.format" class="smpl">time-of-day</a> <a href="#imported.abnf" class="smpl">SP</a> <a href="#preferred.date.format" class="smpl">GMT</a>
    28562847  <a href="#obsolete.date.formats" class="smpl">date2</a>        = <a href="#preferred.date.format" class="smpl">day</a> "-" <a href="#preferred.date.format" class="smpl">month</a> "-" 2<a href="#imported.abnf" class="smpl">DIGIT</a>
    28572848                 ; day-month-year (e.g., 02-Jun-82)
     
    28642855         / %x53.61.74.75.72.64.61.79 ; "Saturday", case-sensitive
    28652856         / %x53.75.6E.64.61.79 ; "Sunday", case-sensitive
    2866 </pre><div id="rfc.figure.u.49"></div><pre class="inline"><span id="rfc.iref.g.54"></span>  <a href="#obsolete.date.formats" class="smpl">asctime-date</a> = <a href="#preferred.date.format" class="smpl">day-name</a> <a href="#imported.abnf" class="smpl">SP</a> <a href="#obsolete.date.formats" class="smpl">date3</a> <a href="#imported.abnf" class="smpl">SP</a> <a href="#preferred.date.format" class="smpl">time-of-day</a> <a href="#imported.abnf" class="smpl">SP</a> <a href="#preferred.date.format" class="smpl">year</a>
     2857</pre><div id="rfc.figure.u.48"></div><pre class="inline"><span id="rfc.iref.g.54"></span>  <a href="#obsolete.date.formats" class="smpl">asctime-date</a> = <a href="#preferred.date.format" class="smpl">day-name</a> <a href="#imported.abnf" class="smpl">SP</a> <a href="#obsolete.date.formats" class="smpl">date3</a> <a href="#imported.abnf" class="smpl">SP</a> <a href="#preferred.date.format" class="smpl">time-of-day</a> <a href="#imported.abnf" class="smpl">SP</a> <a href="#preferred.date.format" class="smpl">year</a>
    28672858  <a href="#obsolete.date.formats" class="smpl">date3</a>        = <a href="#preferred.date.format" class="smpl">month</a> <a href="#imported.abnf" class="smpl">SP</a> ( 2<a href="#imported.abnf" class="smpl">DIGIT</a> / ( <a href="#imported.abnf" class="smpl">SP</a> 1<a href="#imported.abnf" class="smpl">DIGIT</a> ))
    28682859                 ; month day (e.g., Jun  2)
    2869 </pre><div class="note" id="rfc.section.8.1.1.1.p.15">
     2860</pre><div class="note" id="rfc.section.7.1.1.1.p.15">
    28702861         <p> <b>Note:</b> Recipients of date values are encouraged to be robust in accepting date values that might have been sent by non-HTTP applications,
    28712862            as is sometimes the case when retrieving or posting messages via proxies/gateways to SMTP or NNTP.
    28722863         </p>
    28732864      </div>
    2874       <div class="note" id="rfc.section.8.1.1.1.p.16">
     2865      <div class="note" id="rfc.section.7.1.1.1.p.16">
    28752866         <p> <b>Note:</b> HTTP requirements for the date/time stamp format apply only to their usage within the protocol stream. Clients and servers
    28762867            are not required to use these formats for user presentation, request logging, etc.
     
    28782869      </div>
    28792870      <div id="rfc.iref.d.3"></div>
    2880       <h4 id="rfc.section.8.1.1.2"><a href="#rfc.section.8.1.1.2">8.1.1.2</a>&nbsp;<a id="header.date" href="#header.date">Date</a></h4>
    2881       <p id="rfc.section.8.1.1.2.p.1">The "Date" header field represents the date and time at which the message was originated, having the same semantics as the
    2882          Origination Date Field (orig-date) defined in <a href="http://tools.ietf.org/html/rfc5322#section-3.6.1">Section 3.6.1</a> of <a href="#RFC5322" id="rfc.xref.RFC5322.4"><cite title="Internet Message Format">[RFC5322]</cite></a>. The field value is an HTTP-date, as defined in <a href="#http.date" title="Date/Time Formats">Section&nbsp;8.1.1.1</a>; it <em class="bcp14">MUST</em> be sent in rfc1123-date format.
    2883       </p>
    2884       <div id="rfc.figure.u.50"></div><pre class="inline"><span id="rfc.iref.g.55"></span>  <a href="#header.date" class="smpl">Date</a> = <a href="#http.date" class="smpl">HTTP-date</a>
    2885 </pre><p id="rfc.section.8.1.1.2.p.3">An example is</p>
    2886       <div id="rfc.figure.u.51"></div><pre class="text">  Date: Tue, 15 Nov 1994 08:12:31 GMT
    2887 </pre><p id="rfc.section.8.1.1.2.p.5">Origin servers <em class="bcp14">MUST</em> include a Date header field in all responses, except in these cases:
     2871      <h4 id="rfc.section.7.1.1.2"><a href="#rfc.section.7.1.1.2">7.1.1.2</a>&nbsp;<a id="header.date" href="#header.date">Date</a></h4>
     2872      <p id="rfc.section.7.1.1.2.p.1">The "Date" header field represents the date and time at which the message was originated, having the same semantics as the
     2873         Origination Date Field (orig-date) defined in <a href="http://tools.ietf.org/html/rfc5322#section-3.6.1">Section 3.6.1</a> of <a href="#RFC5322" id="rfc.xref.RFC5322.4"><cite title="Internet Message Format">[RFC5322]</cite></a>. The field value is an HTTP-date, as defined in <a href="#http.date" title="Date/Time Formats">Section&nbsp;7.1.1.1</a>; it <em class="bcp14">MUST</em> be sent in rfc1123-date format.
     2874      </p>
     2875      <div id="rfc.figure.u.49"></div><pre class="inline"><span id="rfc.iref.g.55"></span>  <a href="#header.date" class="smpl">Date</a> = <a href="#http.date" class="smpl">HTTP-date</a>
     2876</pre><p id="rfc.section.7.1.1.2.p.3">An example is</p>
     2877      <div id="rfc.figure.u.50"></div><pre class="text">  Date: Tue, 15 Nov 1994 08:12:31 GMT
     2878</pre><p id="rfc.section.7.1.1.2.p.5">Origin servers <em class="bcp14">MUST</em> include a Date header field in all responses, except in these cases:
    28882879      </p>
    28892880      <ol>
     
    28962887         </li>
    28972888      </ol>
    2898       <p id="rfc.section.8.1.1.2.p.6">A received message that does not have a Date header field <em class="bcp14">MUST</em> be assigned one by the recipient if the message will be cached by that recipient.
    2899       </p>
    2900       <p id="rfc.section.8.1.1.2.p.7">Clients can use the Date header field as well; in order to keep request messages small, they are advised not to include it
     2889      <p id="rfc.section.7.1.1.2.p.6">A received message that does not have a Date header field <em class="bcp14">MUST</em> be assigned one by the recipient if the message will be cached by that recipient.
     2890      </p>
     2891      <p id="rfc.section.7.1.1.2.p.7">Clients can use the Date header field as well; in order to keep request messages small, they are advised not to include it
    29012892         when it doesn't convey any useful information (as is usually the case for requests that do not contain a payload).
    29022893      </p>
    2903       <p id="rfc.section.8.1.1.2.p.8">The HTTP-date sent in a Date header field <em class="bcp14">SHOULD NOT</em> represent a date and time subsequent to the generation of the message. It <em class="bcp14">SHOULD</em> represent the best available approximation of the date and time of message generation, unless the implementation has no means
     2894      <p id="rfc.section.7.1.1.2.p.8">The HTTP-date sent in a Date header field <em class="bcp14">SHOULD NOT</em> represent a date and time subsequent to the generation of the message. It <em class="bcp14">SHOULD</em> represent the best available approximation of the date and time of message generation, unless the implementation has no means
    29042895         of generating a reasonably accurate date and time. In theory, the date ought to represent the moment just before the payload
    29052896         is generated. In practice, the date can be generated at any time during the message origination without affecting its semantic
     
    29072898      </p>
    29082899      <div id="rfc.iref.l.1"></div>
    2909       <h3 id="rfc.section.8.1.2"><a href="#rfc.section.8.1.2">8.1.2</a>&nbsp;<a id="header.location" href="#header.location">Location</a></h3>
    2910       <p id="rfc.section.8.1.2.p.1">The "Location" header field <em class="bcp14">MAY</em> be sent in responses to refer to a specific resource in accordance with the semantics of the status code.
    2911       </p>
    2912       <div id="rfc.figure.u.52"></div><pre class="inline"><span id="rfc.iref.g.56"></span>  <a href="#header.location" class="smpl">Location</a> = <a href="#imported.abnf" class="smpl">URI-reference</a>
    2913 </pre><p id="rfc.section.8.1.2.p.3">For <a href="#status.201" class="smpl">201 (Created)</a> responses, the Location is the URI of the new resource which was created by the request. For <a href="#status.3xx" class="smpl">3xx (Redirection)</a> responses, the location <em class="bcp14">SHOULD</em> indicate the server's preferred URI for automatic redirection to the resource.
    2914       </p>
    2915       <p id="rfc.section.8.1.2.p.4">The field value consists of a single URI-reference. When it has the form of a relative reference (<a href="#RFC3986" id="rfc.xref.RFC3986.1"><cite title="Uniform Resource Identifier (URI): Generic Syntax">[RFC3986]</cite></a>, <a href="http://tools.ietf.org/html/rfc3986#section-4.2">Section 4.2</a>), the final value is computed by resolving it against the effective request URI (<a href="#RFC3986" id="rfc.xref.RFC3986.2"><cite title="Uniform Resource Identifier (URI): Generic Syntax">[RFC3986]</cite></a>, <a href="http://tools.ietf.org/html/rfc3986#section-5">Section 5</a>). If the original URI, as navigated to by the user agent, did contain a fragment identifier, and the final value does not,
     2900      <h3 id="rfc.section.7.1.2"><a href="#rfc.section.7.1.2">7.1.2</a>&nbsp;<a id="header.location" href="#header.location">Location</a></h3>
     2901      <p id="rfc.section.7.1.2.p.1">The "Location" header field <em class="bcp14">MAY</em> be sent in responses to refer to a specific resource in accordance with the semantics of the status code.
     2902      </p>
     2903      <div id="rfc.figure.u.51"></div><pre class="inline"><span id="rfc.iref.g.56"></span>  <a href="#header.location" class="smpl">Location</a> = <a href="#imported.abnf" class="smpl">URI-reference</a>
     2904</pre><p id="rfc.section.7.1.2.p.3">For <a href="#status.201" class="smpl">201 (Created)</a> responses, the Location is the URI of the new resource which was created by the request. For <a href="#status.3xx" class="smpl">3xx (Redirection)</a> responses, the location <em class="bcp14">SHOULD</em> indicate the server's preferred URI for automatic redirection to the resource.
     2905      </p>
     2906      <p id="rfc.section.7.1.2.p.4">The field value consists of a single URI-reference. When it has the form of a relative reference (<a href="#RFC3986" id="rfc.xref.RFC3986.1"><cite title="Uniform Resource Identifier (URI): Generic Syntax">[RFC3986]</cite></a>, <a href="http://tools.ietf.org/html/rfc3986#section-4.2">Section 4.2</a>), the final value is computed by resolving it against the effective request URI (<a href="#RFC3986" id="rfc.xref.RFC3986.2"><cite title="Uniform Resource Identifier (URI): Generic Syntax">[RFC3986]</cite></a>, <a href="http://tools.ietf.org/html/rfc3986#section-5">Section 5</a>). If the original URI, as navigated to by the user agent, did contain a fragment identifier, and the final value does not,
    29162907         then the original URI's fragment identifier is added to the final value.
    29172908      </p>
    2918       <div id="rfc.figure.u.53"></div>
     2909      <div id="rfc.figure.u.52"></div>
    29192910      <p>For example, the original URI "http://www.example.org/~tim", combined with a field value given as:</p>  <pre class="text">  Location: /pub/WWW/People.html#tim
    29202911</pre>  <p>would result in a final value of "http://www.example.org/pub/WWW/People.html#tim"</p>
    2921       <div id="rfc.figure.u.54"></div>
     2912      <div id="rfc.figure.u.53"></div>
    29222913      <p>An original URI "http://www.example.org/index.html#larry", combined with a field value given as:</p>  <pre class="text">  Location: http://www.example.net/index.html
    29232914</pre>  <p>would result in a final value of "http://www.example.net/index.html#larry", preserving the original fragment identifier.</p>
    2924       <div class="note" id="rfc.section.8.1.2.p.7">
     2915      <div class="note" id="rfc.section.7.1.2.p.7">
    29252916         <p> <b>Note:</b> Some recipients attempt to recover from Location fields that are not valid URI references. This specification does not mandate
    29262917            or define such processing, but does allow it.
    29272918         </p>
    29282919      </div>
    2929       <p id="rfc.section.8.1.2.p.8">There are circumstances in which a fragment identifier in a Location URI would not be appropriate. For instance, when it appears
     2920      <p id="rfc.section.7.1.2.p.8">There are circumstances in which a fragment identifier in a Location URI would not be appropriate. For instance, when it appears
    29302921         in a <a href="#status.201" class="smpl">201
    29312922            (Created)</a> response, where the Location header field specifies the URI for the entire created resource.
    29322923      </p>
    2933       <div class="note" id="rfc.section.8.1.2.p.9">
     2924      <div class="note" id="rfc.section.7.1.2.p.9">
    29342925         <p> <b>Note:</b> The <a href="#header.content-location" class="smpl">Content-Location</a> header field (<a href="#header.content-location" id="rfc.xref.header.content-location.3" title="Content-Location">Section&nbsp;3.1.4.2</a>) differs from Location in that the Content-Location identifies the most specific resource corresponding to the enclosed representation.
    29352926            It is therefore possible for a response to contain header fields for both Location and Content-Location.
     
    29372928      </div>
    29382929      <div id="rfc.iref.r.3"></div>
    2939       <h3 id="rfc.section.8.1.3"><a href="#rfc.section.8.1.3">8.1.3</a>&nbsp;<a id="header.retry-after" href="#header.retry-after">Retry-After</a></h3>
    2940       <p id="rfc.section.8.1.3.p.1">The header "Retry-After" field can be used with a <a href="#status.503" class="smpl">503 (Service
     2930      <h3 id="rfc.section.7.1.3"><a href="#rfc.section.7.1.3">7.1.3</a>&nbsp;<a id="header.retry-after" href="#header.retry-after">Retry-After</a></h3>
     2931      <p id="rfc.section.7.1.3.p.1">The header "Retry-After" field can be used with a <a href="#status.503" class="smpl">503 (Service
    29412932            Unavailable)</a> response to indicate how long the service is expected to be unavailable to the requesting client. This field <em class="bcp14">MAY</em> also be used with any <a href="#status.3xx" class="smpl">3xx (Redirection)</a> response to indicate the minimum time the user agent is asked to wait before issuing the redirected request.
    29422933      </p>
    2943       <p id="rfc.section.8.1.3.p.2">The value of this field can be either an HTTP-date or an integer number of seconds (in decimal) after the time of the response.</p>
    2944       <div id="rfc.figure.u.55"></div><pre class="inline"><span id="rfc.iref.g.57"></span>  <a href="#header.retry-after" class="smpl">Retry-After</a> = <a href="#http.date" class="smpl">HTTP-date</a> / <a href="#rule.delta-seconds" class="smpl">delta-seconds</a>
     2934      <p id="rfc.section.7.1.3.p.2">The value of this field can be either an HTTP-date or an integer number of seconds (in decimal) after the time of the response.</p>
     2935      <div id="rfc.figure.u.54"></div><pre class="inline"><span id="rfc.iref.g.57"></span>  <a href="#header.retry-after" class="smpl">Retry-After</a> = <a href="#http.date" class="smpl">HTTP-date</a> / <a href="#rule.delta-seconds" class="smpl">delta-seconds</a>
    29452936</pre><div id="rule.delta-seconds">
    2946          <p id="rfc.section.8.1.3.p.4">  Time spans are non-negative decimal integers, representing time in seconds.</p>
     2937         <p id="rfc.section.7.1.3.p.4">  Time spans are non-negative decimal integers, representing time in seconds.</p>
    29472938      </div>
    2948       <div id="rfc.figure.u.56"></div><pre class="inline"><span id="rfc.iref.g.58"></span>  <a href="#rule.delta-seconds" class="smpl">delta-seconds</a>  = 1*<a href="#imported.abnf" class="smpl">DIGIT</a>
    2949 </pre><p id="rfc.section.8.1.3.p.6">Two examples of its use are</p>
    2950       <div id="rfc.figure.u.57"></div><pre class="text">  Retry-After: Fri, 31 Dec 1999 23:59:59 GMT
     2939      <div id="rfc.figure.u.55"></div><pre class="inline"><span id="rfc.iref.g.58"></span>  <a href="#rule.delta-seconds" class="smpl">delta-seconds</a>  = 1*<a href="#imported.abnf" class="smpl">DIGIT</a>
     2940</pre><p id="rfc.section.7.1.3.p.6">Two examples of its use are</p>
     2941      <div id="rfc.figure.u.56"></div><pre class="text">  Retry-After: Fri, 31 Dec 1999 23:59:59 GMT
    29512942  Retry-After: 120
    2952 </pre><p id="rfc.section.8.1.3.p.8">In the latter example, the delay is 2 minutes.</p>
    2953       <h2 id="rfc.section.8.2"><a href="#rfc.section.8.2">8.2</a>&nbsp;<a id="selected.representation" href="#selected.representation">Selected Representation Header Fields</a></h2>
    2954       <p id="rfc.section.8.2.p.1"><span id="rfc.iref.s.7"></span> We use the term "<dfn>selected representation</dfn>" to refer to the the current representation of a target resource that would have been selected in a successful response if
     2943</pre><p id="rfc.section.7.1.3.p.8">In the latter example, the delay is 2 minutes.</p>
     2944      <h2 id="rfc.section.7.2"><a href="#rfc.section.7.2">7.2</a>&nbsp;<a id="selected.representation" href="#selected.representation">Selected Representation Header Fields</a></h2>
     2945      <p id="rfc.section.7.2.p.1"><span id="rfc.iref.s.7"></span> We use the term "<dfn>selected representation</dfn>" to refer to the the current representation of a target resource that would have been selected in a successful response if
    29552946         the same request had used the method GET and excluded any conditional request header fields.
    29562947      </p>
    2957       <p id="rfc.section.8.2.p.2">Additional header fields define metadata about the selected representation, which might differ from the representation included
     2948      <p id="rfc.section.7.2.p.2">Additional header fields define metadata about the selected representation, which might differ from the representation included
    29582949         in the message for responses to some state-changing methods. The following header fields are defined as selected representation
    29592950         metadata:
     
    29782969               <tr>
    29792970                  <td class="left">Vary</td>
    2980                   <td class="left"><a href="#header.vary" id="rfc.xref.header.vary.2" title="Vary">Section&nbsp;8.2.1</a></td>
     2971                  <td class="left"><a href="#header.vary" id="rfc.xref.header.vary.2" title="Vary">Section&nbsp;7.2.1</a></td>
    29812972               </tr>
    29822973            </tbody>
     
    29842975      </div>
    29852976      <div id="rfc.iref.v.1"></div>
    2986       <h3 id="rfc.section.8.2.1"><a href="#rfc.section.8.2.1">8.2.1</a>&nbsp;<a id="header.vary" href="#header.vary">Vary</a></h3>
    2987       <p id="rfc.section.8.2.1.p.1">The "Vary" header field conveys the set of header fields that were used to select the representation.</p>
    2988       <p id="rfc.section.8.2.1.p.2">Caches use this information as part of determining whether a stored response can be used to satisfy a given request (<a href="p6-cache.html#caching.negotiated.responses" title="Using Negotiated Responses">Section 4.3</a> of <a href="#Part6" id="rfc.xref.Part6.14"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>).
    2989       </p>
    2990       <p id="rfc.section.8.2.1.p.3">In uncacheable or stale responses, the Vary field value advises the user agent about the criteria that were used to select
     2977      <h3 id="rfc.section.7.2.1"><a href="#rfc.section.7.2.1">7.2.1</a>&nbsp;<a id="header.vary" href="#header.vary">Vary</a></h3>
     2978      <p id="rfc.section.7.2.1.p.1">The "Vary" header field conveys the set of header fields that were used to select the representation.</p>
     2979      <p id="rfc.section.7.2.1.p.2">Caches use this information as part of determining whether a stored response can be used to satisfy a given request (<a href="p6-cache.html#caching.negotiated.responses" title="Using Negotiated Responses">Section 4.3</a> of <a href="#Part6" id="rfc.xref.Part6.14"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>).
     2980      </p>
     2981      <p id="rfc.section.7.2.1.p.3">In uncacheable or stale responses, the Vary field value advises the user agent about the criteria that were used to select
    29912982         the representation.
    29922983      </p>
    2993       <div id="rfc.figure.u.58"></div><pre class="inline"><span id="rfc.iref.g.59"></span>  <a href="#header.vary" class="smpl">Vary</a> = "*" / 1#<a href="#imported.abnf" class="smpl">field-name</a>
    2994 </pre><p id="rfc.section.8.2.1.p.5">The set of header fields named by the Vary field value is known as the selecting header fields.</p>
    2995       <p id="rfc.section.8.2.1.p.6">A server <em class="bcp14">SHOULD</em> include a Vary header field with any cacheable response that is subject to proactive negotiation. Doing so allows a cache
     2984      <div id="rfc.figure.u.57"></div><pre class="inline"><span id="rfc.iref.g.59"></span>  <a href="#header.vary" class="smpl">Vary</a> = "*" / 1#<a href="#imported.abnf" class="smpl">field-name</a>
     2985</pre><p id="rfc.section.7.2.1.p.5">The set of header fields named by the Vary field value is known as the selecting header fields.</p>
     2986      <p id="rfc.section.7.2.1.p.6">A server <em class="bcp14">SHOULD</em> include a Vary header field with any cacheable response that is subject to proactive negotiation. Doing so allows a cache
    29962987         to properly interpret future requests on that resource and informs the user agent about the presence of negotiation on that
    29972988         resource. A server <em class="bcp14">MAY</em> include a Vary header field with a non-cacheable response that is subject to proactive negotiation, since this might provide
    29982989         the user agent with useful information about the dimensions over which the response varies at the time of the response.
    29992990      </p>
    3000       <p id="rfc.section.8.2.1.p.7">A Vary field value of "*" signals that unspecified parameters not limited to the header fields (e.g., the network address
     2991      <p id="rfc.section.7.2.1.p.7">A Vary field value of "*" signals that unspecified parameters not limited to the header fields (e.g., the network address
    30012992         of the client), play a role in the selection of the response representation; therefore, a cache cannot determine whether this
    30022993         response is appropriate. A proxy <em class="bcp14">MUST NOT</em> generate the "*" value.
    30032994      </p>
    3004       <p id="rfc.section.8.2.1.p.8">The field-names given are not limited to the set of standard header fields defined by this specification. Field names are
     2995      <p id="rfc.section.7.2.1.p.8">The field-names given are not limited to the set of standard header fields defined by this specification. Field names are
    30052996         case-insensitive.
    30062997      </p>
    3007       <h2 id="rfc.section.8.3"><a href="#rfc.section.8.3">8.3</a>&nbsp;<a id="response.auth" href="#response.auth">Authentication Challenges</a></h2>
    3008       <p id="rfc.section.8.3.p.1">Authentication challenges indicate what mechanisms are available for the client to provide authentication credentials in future
     2998      <h2 id="rfc.section.7.3"><a href="#rfc.section.7.3">7.3</a>&nbsp;<a id="response.auth" href="#response.auth">Authentication Challenges</a></h2>
     2999      <p id="rfc.section.7.3.p.1">Authentication challenges indicate what mechanisms are available for the client to provide authentication credentials in future
    30093000         requests.
    30103001      </p>
     
    30293020         </table>
    30303021      </div>
    3031       <h2 id="rfc.section.8.4"><a href="#rfc.section.8.4">8.4</a>&nbsp;<a id="response.inform" href="#response.inform">Informative</a></h2>
    3032       <p id="rfc.section.8.4.p.1">The remaining response header fields provide more information about the target resource for potential use in later requests.</p>
     3022      <h2 id="rfc.section.7.4"><a href="#rfc.section.7.4">7.4</a>&nbsp;<a id="response.context" href="#response.context">Response Context</a></h2>
     3023      <p id="rfc.section.7.4.p.1">The remaining response header fields provide more information about the target resource for potential use in later requests.</p>
    30333024      <div id="rfc.table.u.13">
    30343025         <table class="tt full left" cellpadding="3" cellspacing="0">
     
    30463037               <tr>
    30473038                  <td class="left">Allow</td>
    3048                   <td class="left"><a href="#header.allow" id="rfc.xref.header.allow.2" title="Allow">Section&nbsp;8.4.1</a></td>
     3039                  <td class="left"><a href="#header.allow" id="rfc.xref.header.allow.2" title="Allow">Section&nbsp;7.4.1</a></td>
    30493040               </tr>
    30503041               <tr>
    30513042                  <td class="left">Server</td>
    3052                   <td class="left"><a href="#header.server" id="rfc.xref.header.server.1" title="Server">Section&nbsp;8.4.2</a></td>
     3043                  <td class="left"><a href="#header.server" id="rfc.xref.header.server.1" title="Server">Section&nbsp;7.4.2</a></td>
    30533044               </tr>
    30543045            </tbody>
     
    30563047      </div>
    30573048      <div id="rfc.iref.a.5"></div>
    3058       <h3 id="rfc.section.8.4.1"><a href="#rfc.section.8.4.1">8.4.1</a>&nbsp;<a id="header.allow" href="#header.allow">Allow</a></h3>
    3059       <p id="rfc.section.8.4.1.p.1">The "Allow" header field lists the set of methods advertised as supported by the target resource. The purpose of this field
     3049      <h3 id="rfc.section.7.4.1"><a href="#rfc.section.7.4.1">7.4.1</a>&nbsp;<a id="header.allow" href="#header.allow">Allow</a></h3>
     3050      <p id="rfc.section.7.4.1.p.1">The "Allow" header field lists the set of methods advertised as supported by the target resource. The purpose of this field
    30603051         is strictly to inform the recipient of valid request methods associated with the resource.
    30613052      </p>
    3062       <div id="rfc.figure.u.59"></div><pre class="inline"><span id="rfc.iref.g.60"></span>  <a href="#header.allow" class="smpl">Allow</a> = #<a href="#method.overview" class="smpl">method</a>
    3063 </pre><p id="rfc.section.8.4.1.p.3">Example of use:</p>
    3064       <div id="rfc.figure.u.60"></div><pre class="text">  Allow: GET, HEAD, PUT
    3065 </pre><p id="rfc.section.8.4.1.p.5">The actual set of allowed methods is defined by the origin server at the time of each request.</p>
    3066       <p id="rfc.section.8.4.1.p.6">A proxy <em class="bcp14">MUST NOT</em> modify the Allow header field — it does not need to understand all the methods specified in order to handle them according
     3053      <div id="rfc.figure.u.58"></div><pre class="inline"><span id="rfc.iref.g.60"></span>  <a href="#header.allow" class="smpl">Allow</a> = #<a href="#method.overview" class="smpl">method</a>
     3054</pre><p id="rfc.section.7.4.1.p.3">Example of use:</p>
     3055      <div id="rfc.figure.u.59"></div><pre class="text">  Allow: GET, HEAD, PUT
     3056</pre><p id="rfc.section.7.4.1.p.5">The actual set of allowed methods is defined by the origin server at the time of each request.</p>
     3057      <p id="rfc.section.7.4.1.p.6">A proxy <em class="bcp14">MUST NOT</em> modify the Allow header field — it does not need to understand all the methods specified in order to handle them according
    30673058         to the generic message handling rules.
    30683059      </p>
    30693060      <div id="rfc.iref.s.8"></div>
    3070       <h3 id="rfc.section.8.4.2"><a href="#rfc.section.8.4.2">8.4.2</a>&nbsp;<a id="header.server" href="#header.server">Server</a></h3>
    3071       <p id="rfc.section.8.4.2.p.1">The "Server" header field contains information about the software used by the origin server to handle the request.</p>
    3072       <p id="rfc.section.8.4.2.p.2">The field can contain multiple product tokens (<a href="#product.tokens" title="Product Tokens">Section&nbsp;4</a>) and comments (<a href="p1-messaging.html#header.fields" title="Header Fields">Section 3.2</a> of <a href="#Part1" id="rfc.xref.Part1.28"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>) identifying the server and any significant subproducts. The product tokens are listed in order of their significance for
    3073          identifying the application.
    3074       </p>
    3075       <div id="rfc.figure.u.61"></div><pre class="inline"><span id="rfc.iref.g.61"></span>  <a href="#header.server" class="smpl">Server</a> = <a href="#product.tokens" class="smpl">product</a> *( <a href="#imported.abnf" class="smpl">RWS</a> ( <a href="#product.tokens" class="smpl">product</a> / <a href="#imported.abnf" class="smpl">comment</a> ) )
    3076 </pre><p id="rfc.section.8.4.2.p.4">Example:</p>
    3077       <div id="rfc.figure.u.62"></div><pre class="text">  Server: CERN/3.0 libwww/2.17
    3078 </pre><p id="rfc.section.8.4.2.p.6">If the response is being forwarded through a proxy, the proxy application <em class="bcp14">MUST NOT</em> modify the <a href="#header.server" class="smpl">Server</a> header field. Instead, it <em class="bcp14">MUST</em> include a <a href="p1-messaging.html#header.via" class="smpl">Via</a> field (as described in <a href="p1-messaging.html#header.via" title="Via">Section 5.7.1</a> of <a href="#Part1" id="rfc.xref.Part1.29"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>).
    3079       </p>
    3080       <div class="note" id="rfc.section.8.4.2.p.7">
    3081          <p> <b>Note:</b> Revealing the specific software version of the server might allow the server machine to become more vulnerable to attacks
    3082             against software that is known to contain security holes. Server implementers are encouraged to make this field a configurable
    3083             option.
    3084          </p>
    3085       </div>
    3086       <h1 id="rfc.section.9"><a href="#rfc.section.9">9.</a>&nbsp;<a id="IANA.considerations" href="#IANA.considerations">IANA Considerations</a></h1>
    3087       <h2 id="rfc.section.9.1"><a href="#rfc.section.9.1">9.1</a>&nbsp;<a id="method.registry" href="#method.registry">Method Registry</a></h2>
    3088       <p id="rfc.section.9.1.p.1">The HTTP Method Registry defines the name space for the request method token (<a href="#methods" title="Request Methods">Section&nbsp;5</a>). The method registry is maintained at &lt;<a href="http://www.iana.org/assignments/http-methods">http://www.iana.org/assignments/http-methods</a>&gt;.
    3089       </p>
    3090       <h3 id="rfc.section.9.1.1"><a href="#rfc.section.9.1.1">9.1.1</a>&nbsp;<a id="method.procedure" href="#method.procedure">Procedure</a></h3>
    3091       <p id="rfc.section.9.1.1.p.1">HTTP method registrations <em class="bcp14">MUST</em> include the following fields:
     3061      <h3 id="rfc.section.7.4.2"><a href="#rfc.section.7.4.2">7.4.2</a>&nbsp;<a id="header.server" href="#header.server">Server</a></h3>
     3062      <p id="rfc.section.7.4.2.p.1">The "Server" header field contains information about the software used by the origin server to handle the request, which is
     3063         often used by clients to help identify the scope of reported interoperability problems, to work around or tailor requests
     3064         to avoid particular server limitations, and for analytics regarding server or operating system use. An origin server <em class="bcp14">MAY</em> generate a Server field in its responses.
     3065      </p>
     3066      <div id="rfc.figure.u.60"></div><pre class="inline"><span id="rfc.iref.g.61"></span>  <a href="#header.server" class="smpl">Server</a> = <a href="#header.user-agent" class="smpl">product</a> *( <a href="#imported.abnf" class="smpl">RWS</a> ( <a href="#header.user-agent" class="smpl">product</a> / <a href="#imported.abnf" class="smpl">comment</a> ) )
     3067</pre><p id="rfc.section.7.4.2.p.3">The Server field-value consists of one or more product identifiers, each followed by zero or more comments (<a href="p1-messaging.html#header.fields" title="Header Fields">Section 3.2</a> of <a href="#Part1" id="rfc.xref.Part1.28"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>), which together identify the origin server software and its significant subproducts. By convention, the product identifiers
     3068         are listed in order of their significance for identifying the origin server software. Each product identifier consists of
     3069         a name and optional version, as defined in <a href="#header.user-agent" id="rfc.xref.header.user-agent.2" title="User-Agent">Section&nbsp;5.5.3</a>.
     3070      </p>
     3071      <p id="rfc.section.7.4.2.p.4">Example:</p>
     3072      <div id="rfc.figure.u.61"></div><pre class="text">  Server: CERN/3.0 libwww/2.17
     3073</pre><p id="rfc.section.7.4.2.p.6">An origin server <em class="bcp14">SHOULD NOT</em> generate a Server field containing needlessly fine-grained detail and <em class="bcp14">SHOULD</em> limit the addition of subproducts by third parties. Overly long and detailed Server field values increase response latency
     3074         and potentially reveal internal implementation details that might make it (slightly) easier for attackers to find and exploit
     3075         known security holes.
     3076      </p>
     3077      <h1 id="rfc.section.8"><a href="#rfc.section.8">8.</a>&nbsp;<a id="IANA.considerations" href="#IANA.considerations">IANA Considerations</a></h1>
     3078      <h2 id="rfc.section.8.1"><a href="#rfc.section.8.1">8.1</a>&nbsp;<a id="method.registry" href="#method.registry">Method Registry</a></h2>
     3079      <p id="rfc.section.8.1.p.1">The HTTP Method Registry defines the name space for the request method token (<a href="#methods" title="Request Methods">Section&nbsp;4</a>). The method registry is maintained at &lt;<a href="http://www.iana.org/assignments/http-methods">http://www.iana.org/assignments/http-methods</a>&gt;.
     3080      </p>
     3081      <h3 id="rfc.section.8.1.1"><a href="#rfc.section.8.1.1">8.1.1</a>&nbsp;<a id="method.procedure" href="#method.procedure">Procedure</a></h3>
     3082      <p id="rfc.section.8.1.1.p.1">HTTP method registrations <em class="bcp14">MUST</em> include the following fields:
    30923083      </p>
    30933084      <ul>
    3094          <li>Method Name (see <a href="#methods" title="Request Methods">Section&nbsp;5</a>)
    3095          </li>
    3096          <li>Safe ("yes" or "no", see <a href="#safe.methods" title="Safe Methods">Section&nbsp;5.2.1</a>)
    3097          </li>
    3098          <li>Idempotent ("yes" or "no", see <a href="#idempotent.methods" title="Idempotent Methods">Section&nbsp;5.2.2</a>)
     3085         <li>Method Name (see <a href="#methods" title="Request Methods">Section&nbsp;4</a>)
     3086         </li>
     3087         <li>Safe ("yes" or "no", see <a href="#safe.methods" title="Safe Methods">Section&nbsp;4.2.1</a>)
     3088         </li>
     3089         <li>Idempotent ("yes" or "no", see <a href="#idempotent.methods" title="Idempotent Methods">Section&nbsp;4.2.2</a>)
    30993090         </li>
    31003091         <li>Pointer to specification text</li>
    31013092      </ul>
    3102       <p id="rfc.section.9.1.1.p.2">Values to be added to this name space require IETF Review (see <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>).
    3103       </p>
    3104       <h3 id="rfc.section.9.1.2"><a href="#rfc.section.9.1.2">9.1.2</a>&nbsp;<a id="considerations.for.new.methods" href="#considerations.for.new.methods">Considerations for New Methods</a></h3>
    3105       <p id="rfc.section.9.1.2.p.1">Standardized methods are generic; that is, they are potentially applicable to any resource, not just one particular media
     3093      <p id="rfc.section.8.1.1.p.2">Values to be added to this name space require IETF Review (see <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>).
     3094      </p>
     3095      <h3 id="rfc.section.8.1.2"><a href="#rfc.section.8.1.2">8.1.2</a>&nbsp;<a id="considerations.for.new.methods" href="#considerations.for.new.methods">Considerations for New Methods</a></h3>
     3096      <p id="rfc.section.8.1.2.p.1">Standardized methods are generic; that is, they are potentially applicable to any resource, not just one particular media
    31063097         type, kind of resource, or application. As such, it is preferred that new methods be registered in a document that isn't specific
    31073098         to a single application or data format, since orthogonal technologies deserve orthogonal specification.
    31083099      </p>
    3109       <p id="rfc.section.9.1.2.p.2">Since message parsing (<a href="p1-messaging.html#message.body" title="Message Body">Section 3.3</a> of <a href="#Part1" id="rfc.xref.Part1.30"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>) needs to be independent of method semantics (aside from responses to HEAD), definitions of new methods cannot change the
     3100      <p id="rfc.section.8.1.2.p.2">Since message parsing (<a href="p1-messaging.html#message.body" title="Message Body">Section 3.3</a> of <a href="#Part1" id="rfc.xref.Part1.29"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>) needs to be independent of method semantics (aside from responses to HEAD), definitions of new methods cannot change the
    31103101         parsing algorithm or prohibit the presence of a message body on either the request or the response message. Definitions of
    31113102         new methods can specify that only a zero-length message body is allowed by requiring a Content-Length header field with a
    31123103         value of "0".
    31133104      </p>
    3114       <p id="rfc.section.9.1.2.p.3">New method definitions need to indicate whether they are safe (<a href="#safe.methods" title="Safe Methods">Section&nbsp;5.2.1</a>), idempotent (<a href="#idempotent.methods" title="Idempotent Methods">Section&nbsp;5.2.2</a>), cacheable (<a href="#cacheable.methods" title="Cacheable Methods">Section&nbsp;5.2.3</a>), and what semantics are to be associated with the payload body if any is present in the request. If a method is cacheable,
     3105      <p id="rfc.section.8.1.2.p.3">New method definitions need to indicate whether they are safe (<a href="#safe.methods" title="Safe Methods">Section&nbsp;4.2.1</a>), idempotent (<a href="#idempotent.methods" title="Idempotent Methods">Section&nbsp;4.2.2</a>), cacheable (<a href="#cacheable.methods" title="Cacheable Methods">Section&nbsp;4.2.3</a>), and what semantics are to be associated with the payload body if any is present in the request. If a method is cacheable,
    31153106         the method definition ought to describe how, and under what conditions, a cache can store a response and use it to satisfy
    31163107         a subsequent request.
    31173108      </p>
    3118       <h3 id="rfc.section.9.1.3"><a href="#rfc.section.9.1.3">9.1.3</a>&nbsp;<a id="method.registration" href="#method.registration">Registrations</a></h3>
    3119       <p id="rfc.section.9.1.3.p.1">The HTTP Method Registry shall be populated with the registrations below:</p>
     3109      <h3 id="rfc.section.8.1.3"><a href="#rfc.section.8.1.3">8.1.3</a>&nbsp;<a id="method.registration" href="#method.registration">Registrations</a></h3>
     3110      <p id="rfc.section.8.1.3.p.1">The HTTP Method Registry shall be populated with the registrations below:</p>
    31203111      <div id="rfc.table.2">
    31213112         <div id="iana.method.registration.table"></div>
     
    31343125                  <td class="left">no</td>
    31353126                  <td class="left">no</td>
    3136                   <td class="left"> <a href="#CONNECT" id="rfc.xref.CONNECT.2" title="CONNECT">Section&nbsp;5.3.6</a>
     3127                  <td class="left"> <a href="#CONNECT" id="rfc.xref.CONNECT.2" title="CONNECT">Section&nbsp;4.3.6</a>
    31373128                  </td>
    31383129               </tr>
     
    31413132                  <td class="left">no</td>
    31423133                  <td class="left">yes</td>
    3143                   <td class="left"> <a href="#DELETE" id="rfc.xref.DELETE.2" title="DELETE">Section&nbsp;5.3.5</a>
     3134                  <td class="left"> <a href="#DELETE" id="rfc.xref.DELETE.2" title="DELETE">Section&nbsp;4.3.5</a>
    31443135                  </td>
    31453136               </tr>
     
    31483139                  <td class="left">yes</td>
    31493140                  <td class="left">yes</td>
    3150                   <td class="left"> <a href="#GET" id="rfc.xref.GET.3" title="GET">Section&nbsp;5.3.1</a>
     3141                  <td class="left"> <a href="#GET" id="rfc.xref.GET.3" title="GET">Section&nbsp;4.3.1</a>
    31513142                  </td>
    31523143               </tr>
     
    31553146                  <td class="left">yes</td>
    31563147                  <td class="left">yes</td>
    3157                   <td class="left"> <a href="#HEAD" id="rfc.xref.HEAD.2" title="HEAD">Section&nbsp;5.3.2</a>
     3148                  <td class="left"> <a href="#HEAD" id="rfc.xref.HEAD.2" title="HEAD">Section&nbsp;4.3.2</a>
    31583149                  </td>
    31593150               </tr>
     
    31623153                  <td class="left">yes</td>
    31633154                  <td class="left">yes</td>
    3164                   <td class="left"> <a href="#OPTIONS" id="rfc.xref.OPTIONS.3" title="OPTIONS">Section&nbsp;5.3.7</a>
     3155                  <td class="left"> <a href="#OPTIONS" id="rfc.xref.OPTIONS.3" title="OPTIONS">Section&nbsp;4.3.7</a>
    31653156                  </td>
    31663157               </tr>
     
    31693160                  <td class="left">no</td>
    31703161                  <td class="left">no</td>
    3171                   <td class="left"> <a href="#POST" id="rfc.xref.POST.3" title="POST">Section&nbsp;5.3.3</a>
     3162                  <td class="left"> <a href="#POST" id="rfc.xref.POST.3" title="POST">Section&nbsp;4.3.3</a>
    31723163                  </td>
    31733164               </tr>
     
    31763167                  <td class="left">no</td>
    31773168                  <td class="left">yes</td>
    3178                   <td class="left"> <a href="#PUT" id="rfc.xref.PUT.3" title="PUT">Section&nbsp;5.3.4</a>
     3169                  <td class="left"> <a href="#PUT" id="rfc.xref.PUT.3" title="PUT">Section&nbsp;4.3.4</a>
    31793170                  </td>
    31803171               </tr>
     
    31833174                  <td class="left">yes</td>
    31843175                  <td class="left">yes</td>
    3185                   <td class="left"> <a href="#TRACE" id="rfc.xref.TRACE.3" title="TRACE">Section&nbsp;5.3.8</a>
     3176                  <td class="left"> <a href="#TRACE" id="rfc.xref.TRACE.3" title="TRACE">Section&nbsp;4.3.8</a>
    31863177                  </td>
    31873178               </tr>
     
    31893180         </table>
    31903181      </div>
    3191       <h2 id="rfc.section.9.2"><a href="#rfc.section.9.2">9.2</a>&nbsp;<a id="status.code.registry" href="#status.code.registry">Status Code Registry</a></h2>
    3192       <p id="rfc.section.9.2.p.1">The HTTP Status Code Registry defines the name space for the response status-code token (<a href="#status.codes" title="Response Status Codes">Section&nbsp;7</a>). The status code registry is maintained at &lt;<a href="http://www.iana.org/assignments/http-status-codes">http://www.iana.org/assignments/http-status-codes</a>&gt;.
    3193       </p>
    3194       <p id="rfc.section.9.2.p.2">This section replaces the registration procedure for HTTP Status Codes previously defined in <a href="http://tools.ietf.org/html/rfc2817#section-7.1">Section 7.1</a> of <a href="#RFC2817" id="rfc.xref.RFC2817.1"><cite title="Upgrading to TLS Within HTTP/1.1">[RFC2817]</cite></a>.
    3195       </p>
    3196       <h3 id="rfc.section.9.2.1"><a href="#rfc.section.9.2.1">9.2.1</a>&nbsp;<a id="status.code.procedure" href="#status.code.procedure">Procedure</a></h3>
    3197       <p id="rfc.section.9.2.1.p.1">Values to be added to the HTTP status code name space require IETF Review (see <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>).
    3198       </p>
    3199       <h3 id="rfc.section.9.2.2"><a href="#rfc.section.9.2.2">9.2.2</a>&nbsp;<a id="considerations.for.new.status.codes" href="#considerations.for.new.status.codes">Considerations for New Status Codes</a></h3>
    3200       <p id="rfc.section.9.2.2.p.1">When it is necessary to express semantics for a response that are not defined by current status codes, a new status code can
     3182      <h2 id="rfc.section.8.2"><a href="#rfc.section.8.2">8.2</a>&nbsp;<a id="status.code.registry" href="#status.code.registry">Status Code Registry</a></h2>
     3183      <p id="rfc.section.8.2.p.1">The HTTP Status Code Registry defines the name space for the response status-code token (<a href="#status.codes" title="Response Status Codes">Section&nbsp;6</a>). The status code registry is maintained at &lt;<a href="http://www.iana.org/assignments/http-status-codes">http://www.iana.org/assignments/http-status-codes</a>&gt;.
     3184      </p>
     3185      <p id="rfc.section.8.2.p.2">This section replaces the registration procedure for HTTP Status Codes previously defined in <a href="http://tools.ietf.org/html/rfc2817#section-7.1">Section 7.1</a> of <a href="#RFC2817" id="rfc.xref.RFC2817.1"><cite title="Upgrading to TLS Within HTTP/1.1">[RFC2817]</cite></a>.
     3186      </p>
     3187      <h3 id="rfc.section.8.2.1"><a href="#rfc.section.8.2.1">8.2.1</a>&nbsp;<a id="status.code.procedure" href="#status.code.procedure">Procedure</a></h3>
     3188      <p id="rfc.section.8.2.1.p.1">Values to be added to the HTTP status code name space require IETF Review (see <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>).
     3189      </p>
     3190      <h3 id="rfc.section.8.2.2"><a href="#rfc.section.8.2.2">8.2.2</a>&nbsp;<a id="considerations.for.new.status.codes" href="#considerations.for.new.status.codes">Considerations for New Status Codes</a></h3>
     3191      <p id="rfc.section.8.2.2.p.1">When it is necessary to express semantics for a response that are not defined by current status codes, a new status code can
    32013192         be registered. HTTP status codes are generic; they are potentially applicable to any resource, not just one particular media
    32023193         type, "type" of resource, or application. As such, it is preferred that new status codes be registered in a document that
    32033194         isn't specific to a single application.
    32043195      </p>
    3205       <p id="rfc.section.9.2.2.p.2">New status codes are required to fall under one of the categories defined in <a href="#status.codes" title="Response Status Codes">Section&nbsp;7</a>. To allow existing parsers to properly handle them, new status codes cannot disallow a payload, although they can mandate
     3196      <p id="rfc.section.8.2.2.p.2">New status codes are required to fall under one of the categories defined in <a href="#status.codes" title="Response Status Codes">Section&nbsp;6</a>. To allow existing parsers to properly handle them, new status codes cannot disallow a payload, although they can mandate
    32063197         a zero-length payload body.
    32073198      </p>
    3208       <p id="rfc.section.9.2.2.p.3">A definition for a new status code ought to explain the request conditions that would cause a response containing that status
     3199      <p id="rfc.section.8.2.2.p.3">A definition for a new status code ought to explain the request conditions that would cause a response containing that status
    32093200         code (e.g., combinations of request header fields and/or method(s)) along with any dependencies on response header fields
    32103201         (e.g., what fields are required and what fields can modify the semantics). A response that can transfer a payload ought to
    32113202         specify expected cache behavior (e.g., cacheability and freshness criteria, as described in <a href="#Part6" id="rfc.xref.Part6.15"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>) and whether the payload has any implied association with an identified resource (<a href="#identifying.payload" title="Identifying a Representation">Section&nbsp;3.1.4.1</a>).
    32123203      </p>
    3213       <h3 id="rfc.section.9.2.3"><a href="#rfc.section.9.2.3">9.2.3</a>&nbsp;<a id="status.code.registration" href="#status.code.registration">Registrations</a></h3>
    3214       <p id="rfc.section.9.2.3.p.1">The HTTP Status Code Registry shall be updated with the registrations below:</p>
     3204      <h3 id="rfc.section.8.2.3"><a href="#rfc.section.8.2.3">8.2.3</a>&nbsp;<a id="status.code.registration" href="#status.code.registration">Registrations</a></h3>
     3205      <p id="rfc.section.8.2.3.p.1">The HTTP Status Code Registry shall be updated with the registrations below:</p>
    32153206      <div id="rfc.table.3">
    32163207         <div id="iana.status.code.registration.table"></div>
     
    32273218                  <td class="left">100</td>
    32283219                  <td class="left">Continue</td>
    3229                   <td class="left"> <a href="#status.100" id="rfc.xref.status.100.4" title="100 Continue">Section&nbsp;7.2.1</a>
     3220                  <td class="left"> <a href="#status.100" id="rfc.xref.status.100.4" title="100 Continue">Section&nbsp;6.2.1</a>
    32303221                  </td>
    32313222               </tr>
     
    32333224                  <td class="left">101</td>
    32343225                  <td class="left">Switching Protocols</td>
    3235                   <td class="left"> <a href="#status.101" id="rfc.xref.status.101.2" title="101 Switching Protocols">Section&nbsp;7.2.2</a>
     3226                  <td class="left"> <a href="#status.101" id="rfc.xref.status.101.2" title="101 Switching Protocols">Section&nbsp;6.2.2</a>
    32363227                  </td>
    32373228               </tr>
     
    32393230                  <td class="left">200</td>
    32403231                  <td class="left">OK</td>
    3241                   <td class="left"> <a href="#status.200" id="rfc.xref.status.200.2" title="200 OK">Section&nbsp;7.3.1</a>
     3232                  <td class="left"> <a href="#status.200" id="rfc.xref.status.200.2" title="200 OK">Section&nbsp;6.3.1</a>
    32423233                  </td>
    32433234               </tr>
     
    32453236                  <td class="left">201</td>
    32463237                  <td class="left">Created</td>
    3247                   <td class="left"> <a href="#status.201" id="rfc.xref.status.201.2" title="201 Created">Section&nbsp;7.3.2</a>
     3238                  <td class="left"> <a href="#status.201" id="rfc.xref.status.201.2" title="201 Created">Section&nbsp;6.3.2</a>
    32483239                  </td>
    32493240               </tr>
     
    32513242                  <td class="left">202</td>
    32523243                  <td class="left">Accepted</td>
    3253                   <td class="left"> <a href="#status.202" id="rfc.xref.status.202.2" title="202 Accepted">Section&nbsp;7.3.3</a>
     3244                  <td class="left"> <a href="#status.202" id="rfc.xref.status.202.2" title="202 Accepted">Section&nbsp;6.3.3</a>
    32543245                  </td>
    32553246               </tr>
     
    32573248                  <td class="left">203</td>
    32583249                  <td class="left">Non-Authoritative Information</td>
    3259                   <td class="left"> <a href="#status.203" id="rfc.xref.status.203.2" title="203 Non-Authoritative Information">Section&nbsp;7.3.4</a>
     3250                  <td class="left"> <a href="#status.203" id="rfc.xref.status.203.2" title="203 Non-Authoritative Information">Section&nbsp;6.3.4</a>
    32603251                  </td>
    32613252               </tr>
     
    32633254                  <td class="left">204</td>
    32643255                  <td class="left">No Content</td>
    3265                   <td class="left"> <a href="#status.204" id="rfc.xref.status.204.2" title="204 No Content">Section&nbsp;7.3.5</a>
     3256                  <td class="left"> <a href="#status.204" id="rfc.xref.status.204.2" title="204 No Content">Section&nbsp;6.3.5</a>
    32663257                  </td>
    32673258               </tr>
     
    32693260                  <td class="left">205</td>
    32703261                  <td class="left">Reset Content</td>
    3271                   <td class="left"> <a href="#status.205" id="rfc.xref.status.205.2" title="205 Reset Content">Section&nbsp;7.3.6</a>
     3262                  <td class="left"> <a href="#status.205" id="rfc.xref.status.205.2" title="205 Reset Content">Section&nbsp;6.3.6</a>
    32723263                  </td>
    32733264               </tr>
     
    32753266                  <td class="left">300</td>
    32763267                  <td class="left">Multiple Choices</td>
    3277                   <td class="left"> <a href="#status.300" id="rfc.xref.status.300.2" title="300 Multiple Choices">Section&nbsp;7.4.1</a>
     3268                  <td class="left"> <a href="#status.300" id="rfc.xref.status.300.2" title="300 Multiple Choices">Section&nbsp;6.4.1</a>
    32783269                  </td>
    32793270               </tr>
     
    32813272                  <td class="left">301</td>
    32823273                  <td class="left">Moved Permanently</td>
    3283                   <td class="left"> <a href="#status.301" id="rfc.xref.status.301.2" title="301 Moved Permanently">Section&nbsp;7.4.2</a>
     3274                  <td class="left"> <a href="#status.301" id="rfc.xref.status.301.2" title="301 Moved Permanently">Section&nbsp;6.4.2</a>
    32843275                  </td>
    32853276               </tr>
     
    32873278                  <td class="left">302</td>
    32883279                  <td class="left">Found</td>
    3289                   <td class="left"> <a href="#status.302" id="rfc.xref.status.302.2" title="302 Found">Section&nbsp;7.4.3</a>
     3280                  <td class="left"> <a href="#status.302" id="rfc.xref.status.302.2" title="302 Found">Section&nbsp;6.4.3</a>
    32903281                  </td>
    32913282               </tr>
     
    32933284                  <td class="left">303</td>
    32943285                  <td class="left">See Other</td>
    3295                   <td class="left"> <a href="#status.303" id="rfc.xref.status.303.2" title="303 See Other">Section&nbsp;7.4.4</a>
     3286                  <td class="left"> <a href="#status.303" id="rfc.xref.status.303.2" title="303 See Other">Section&nbsp;6.4.4</a>
    32963287                  </td>
    32973288               </tr>
     
    32993290                  <td class="left">305</td>
    33003291                  <td class="left">Use Proxy</td>
    3301                   <td class="left"> <a href="#status.305" id="rfc.xref.status.305.2" title="305 Use Proxy">Section&nbsp;7.4.5</a>
     3292                  <td class="left"> <a href="#status.305" id="rfc.xref.status.305.2" title="305 Use Proxy">Section&nbsp;6.4.5</a>
    33023293                  </td>
    33033294               </tr>
     
    33053296                  <td class="left">306</td>
    33063297                  <td class="left">(Unused)</td>
    3307                   <td class="left"> <a href="#status.306" id="rfc.xref.status.306.1" title="306 (Unused)">Section&nbsp;7.4.6</a>
     3298                  <td class="left"> <a href="#status.306" id="rfc.xref.status.306.1" title="306 (Unused)">Section&nbsp;6.4.6</a>
    33083299                  </td>
    33093300               </tr>
     
    33113302                  <td class="left">307</td>
    33123303                  <td class="left">Temporary Redirect</td>
    3313                   <td class="left"> <a href="#status.307" id="rfc.xref.status.307.2" title="307 Temporary Redirect">Section&nbsp;7.4.7</a>
     3304                  <td class="left"> <a href="#status.307" id="rfc.xref.status.307.2" title="307 Temporary Redirect">Section&nbsp;6.4.7</a>
    33143305                  </td>
    33153306               </tr>
     
    33173308                  <td class="left">400</td>
    33183309                  <td class="left">Bad Request</td>
    3319                   <td class="left"> <a href="#status.400" id="rfc.xref.status.400.2" title="400 Bad Request">Section&nbsp;7.5.1</a>
     3310                  <td class="left"> <a href="#status.400" id="rfc.xref.status.400.2" title="400 Bad Request">Section&nbsp;6.5.1</a>
    33203311                  </td>
    33213312               </tr>
     
    33233314                  <td class="left">402</td>
    33243315                  <td class="left">Payment Required</td>
    3325                   <td class="left"> <a href="#status.402" id="rfc.xref.status.402.2" title="402 Payment Required">Section&nbsp;7.5.2</a>
     3316                  <td class="left"> <a href="#status.402" id="rfc.xref.status.402.2" title="402 Payment Required">Section&nbsp;6.5.2</a>
    33263317                  </td>
    33273318               </tr>
     
    33293320                  <td class="left">403</td>
    33303321                  <td class="left">Forbidden</td>
    3331                   <td class="left"> <a href="#status.403" id="rfc.xref.status.403.2" title="403 Forbidden">Section&nbsp;7.5.3</a>
     3322                  <td class="left"> <a href="#status.403" id="rfc.xref.status.403.2" title="403 Forbidden">Section&nbsp;6.5.3</a>
    33323323                  </td>
    33333324               </tr>
     
    33353326                  <td class="left">404</td>
    33363327                  <td class="left">Not Found</td>
    3337                   <td class="left"> <a href="#status.404" id="rfc.xref.status.404.2" title="404 Not Found">Section&nbsp;7.5.4</a>
     3328                  <td class="left"> <a href="#status.404" id="rfc.xref.status.404.2" title="404 Not Found">Section&nbsp;6.5.4</a>
    33383329                  </td>
    33393330               </tr>
     
    33413332                  <td class="left">405</td>
    33423333                  <td class="left">Method Not Allowed</td>
    3343                   <td class="left"> <a href="#status.405" id="rfc.xref.status.405.2" title="405 Method Not Allowed">Section&nbsp;7.5.5</a>
     3334                  <td class="left"> <a href="#status.405" id="rfc.xref.status.405.2" title="405 Method Not Allowed">Section&nbsp;6.5.5</a>
    33443335                  </td>
    33453336               </tr>
     
    33473338                  <td class="left">406</td>
    33483339                  <td class="left">Not Acceptable</td>
    3349                   <td class="left"> <a href="#status.406" id="rfc.xref.status.406.2" title="406 Not Acceptable">Section&nbsp;7.5.6</a>
     3340                  <td class="left"> <a href="#status.406" id="rfc.xref.status.406.2" title="406 Not Acceptable">Section&nbsp;6.5.6</a>
    33503341                  </td>
    33513342               </tr>
     
    33533344                  <td class="left">408</td>
    33543345                  <td class="left">Request Timeout</td>
    3355                   <td class="left"> <a href="#status.408" id="rfc.xref.status.408.2" title="408 Request Timeout">Section&nbsp;7.5.7</a>
     3346                  <td class="left"> <a href="#status.408" id="rfc.xref.status.408.2" title="408 Request Timeout">Section&nbsp;6.5.7</a>
    33563347                  </td>
    33573348               </tr>
     
    33593350                  <td class="left">409</td>
    33603351                  <td class="left">Conflict</td>
    3361                   <td class="left"> <a href="#status.409" id="rfc.xref.status.409.2" title="409 Conflict">Section&nbsp;7.5.8</a>
     3352                  <td class="left"> <a href="#status.409" id="rfc.xref.status.409.2" title="409 Conflict">Section&nbsp;6.5.8</a>
    33623353                  </td>
    33633354               </tr>
     
    33653356                  <td class="left">410</td>
    33663357                  <td class="left">Gone</td>
    3367                   <td class="left"> <a href="#status.410" id="rfc.xref.status.410.2" title="410 Gone">Section&nbsp;7.5.9</a>
     3358                  <td class="left"> <a href="#status.410" id="rfc.xref.status.410.2" title="410 Gone">Section&nbsp;6.5.9</a>
    33683359                  </td>
    33693360               </tr>
     
    33713362                  <td class="left">411</td>
    33723363                  <td class="left">Length Required</td>
    3373                   <td class="left"> <a href="#status.411" id="rfc.xref.status.411.2" title="411 Length Required">Section&nbsp;7.5.10</a>
     3364                  <td class="left"> <a href="#status.411" id="rfc.xref.status.411.2" title="411 Length Required">Section&nbsp;6.5.10</a>
    33743365                  </td>
    33753366               </tr>
     
    33773368                  <td class="left">413</td>
    33783369                  <td class="left">Request Representation Too Large</td>
    3379                   <td class="left"> <a href="#status.413" id="rfc.xref.status.413.2" title="413 Request Representation Too Large">Section&nbsp;7.5.11</a>
     3370                  <td class="left"> <a href="#status.413" id="rfc.xref.status.413.2" title="413 Request Representation Too Large">Section&nbsp;6.5.11</a>
    33803371                  </td>
    33813372               </tr>
     
    33833374                  <td class="left">414</td>
    33843375                  <td class="left">URI Too Long</td>
    3385                   <td class="left"> <a href="#status.414" id="rfc.xref.status.414.2" title="414 URI Too Long">Section&nbsp;7.5.12</a>
     3376                  <td class="left"> <a href="#status.414" id="rfc.xref.status.414.2" title="414 URI Too Long">Section&nbsp;6.5.12</a>
    33863377                  </td>
    33873378               </tr>
     
    33893380                  <td class="left">415</td>
    33903381                  <td class="left">Unsupported Media Type</td>
    3391                   <td class="left"> <a href="#status.415" id="rfc.xref.status.415.2" title="415 Unsupported Media Type">Section&nbsp;7.5.13</a>
     3382                  <td class="left"> <a href="#status.415" id="rfc.xref.status.415.2" title="415 Unsupported Media Type">Section&nbsp;6.5.13</a>
    33923383                  </td>
    33933384               </tr>
     
    33953386                  <td class="left">417</td>
    33963387                  <td class="left">Expectation Failed</td>
    3397                   <td class="left"> <a href="#status.417" id="rfc.xref.status.417.2" title="417 Expectation Failed">Section&nbsp;7.5.14</a>
     3388                  <td class="left"> <a href="#status.417" id="rfc.xref.status.417.2" title="417 Expectation Failed">Section&nbsp;6.5.14</a>
    33983389                  </td>
    33993390               </tr>
     
    34013392                  <td class="left">426</td>
    34023393                  <td class="left">Upgrade Required</td>
    3403                   <td class="left"> <a href="#status.426" id="rfc.xref.status.426.2" title="426 Upgrade Required">Section&nbsp;7.5.15</a>
     3394                  <td class="left"> <a href="#status.426" id="rfc.xref.status.426.2" title="426 Upgrade Required">Section&nbsp;6.5.15</a>
    34043395                  </td>
    34053396               </tr>
     
    34073398                  <td class="left">500</td>
    34083399                  <td class="left">Internal Server Error</td>
    3409                   <td class="left"> <a href="#status.500" id="rfc.xref.status.500.2" title="500 Internal Server Error">Section&nbsp;7.6.1</a>
     3400                  <td class="left"> <a href="#status.500" id="rfc.xref.status.500.2" title="500 Internal Server Error">Section&nbsp;6.6.1</a>
    34103401                  </td>
    34113402               </tr>
     
    34133404                  <td class="left">501</td>
    34143405                  <td class="left">Not Implemented</td>
    3415                   <td class="left"> <a href="#status.501" id="rfc.xref.status.501.2" title="501 Not Implemented">Section&nbsp;7.6.2</a>
     3406                  <td class="left"> <a href="#status.501" id="rfc.xref.status.501.2" title="501 Not Implemented">Section&nbsp;6.6.2</a>
    34163407                  </td>
    34173408               </tr>
     
    34193410                  <td class="left">502</td>
    34203411                  <td class="left">Bad Gateway</td>
    3421                   <td class="left"> <a href="#status.502" id="rfc.xref.status.502.2" title="502 Bad Gateway">Section&nbsp;7.6.3</a>
     3412                  <td class="left"> <a href="#status.502" id="rfc.xref.status.502.2" title="502 Bad Gateway">Section&nbsp;6.6.3</a>
    34223413                  </td>
    34233414               </tr>
     
    34253416                  <td class="left">503</td>
    34263417                  <td class="left">Service Unavailable</td>
    3427                   <td class="left"> <a href="#status.503" id="rfc.xref.status.503.2" title="503 Service Unavailable">Section&nbsp;7.6.4</a>
     3418                  <td class="left"> <a href="#status.503" id="rfc.xref.status.503.2" title="503 Service Unavailable">Section&nbsp;6.6.4</a>
    34283419                  </td>
    34293420               </tr>
     
    34313422                  <td class="left">504</td>
    34323423                  <td class="left">Gateway Timeout</td>
    3433                   <td class="left"> <a href="#status.504" id="rfc.xref.status.504.2" title="504 Gateway Timeout">Section&nbsp;7.6.5</a>
     3424                  <td class="left"> <a href="#status.504" id="rfc.xref.status.504.2" title="504 Gateway Timeout">Section&nbsp;6.6.5</a>
    34343425                  </td>
    34353426               </tr>
     
    34373428                  <td class="left">505</td>
    34383429                  <td class="left">HTTP Version Not Supported</td>
    3439                   <td class="left"> <a href="#status.505" id="rfc.xref.status.505.2" title="505 HTTP Version Not Supported">Section&nbsp;7.6.6</a>
     3430                  <td class="left"> <a href="#status.505" id="rfc.xref.status.505.2" title="505 HTTP Version Not Supported">Section&nbsp;6.6.6</a>
    34403431                  </td>
    34413432               </tr>
     
    34433434         </table>
    34443435      </div>
    3445       <h2 id="rfc.section.9.3"><a href="#rfc.section.9.3">9.3</a>&nbsp;<a id="header.field.registry" href="#header.field.registry">Header Field Registry</a></h2>
    3446       <p id="rfc.section.9.3.p.1">HTTP header fields are registered within the Message Header Field Registry located at &lt;<a href="http://www.iana.org/assignments/message-headers/message-header-index.html">http://www.iana.org/assignments/message-headers/message-header-index.html</a>&gt;, as defined by <a href="#BCP90" id="rfc.xref.BCP90.1"><cite title="Registration Procedures for Message Header Fields">[BCP90]</cite></a>.
    3447       </p>
    3448       <h3 id="rfc.section.9.3.1"><a href="#rfc.section.9.3.1">9.3.1</a>&nbsp;<a id="considerations.for.new.header.fields" href="#considerations.for.new.header.fields">Considerations for New Header Fields</a></h3>
    3449       <p id="rfc.section.9.3.1.p.1">Header fields are key:value pairs that can be used to communicate data about the message, its payload, the target resource,
    3450          or the connection (i.e., control data). See <a href="p1-messaging.html#header.fields" title="Header Fields">Section 3.2</a> of <a href="#Part1" id="rfc.xref.Part1.31"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a> for a general definition of header field syntax in HTTP messages.
    3451       </p>
    3452       <p id="rfc.section.9.3.1.p.2">The requirements for header field names are defined in <a href="#BCP90" id="rfc.xref.BCP90.2"><cite title="Registration Procedures for Message Header Fields">[BCP90]</cite></a>. Authors of specifications defining new fields are advised to keep the name as short as practical and to not prefix the name
     3436      <h2 id="rfc.section.8.3"><a href="#rfc.section.8.3">8.3</a>&nbsp;<a id="header.field.registry" href="#header.field.registry">Header Field Registry</a></h2>
     3437      <p id="rfc.section.8.3.p.1">HTTP header fields are registered within the Message Header Field Registry located at &lt;<a href="http://www.iana.org/assignments/message-headers/message-header-index.html">http://www.iana.org/assignments/message-headers/message-header-index.html</a>&gt;, as defined by <a href="#BCP90" id="rfc.xref.BCP90.1"><cite title="Registration Procedures for Message Header Fields">[BCP90]</cite></a>.
     3438      </p>
     3439      <h3 id="rfc.section.8.3.1"><a href="#rfc.section.8.3.1">8.3.1</a>&nbsp;<a id="considerations.for.new.header.fields" href="#considerations.for.new.header.fields">Considerations for New Header Fields</a></h3>
     3440      <p id="rfc.section.8.3.1.p.1">Header fields are key:value pairs that can be used to communicate data about the message, its payload, the target resource,
     3441         or the connection (i.e., control data). See <a href="p1-messaging.html#header.fields" title="Header Fields">Section 3.2</a> of <a href="#Part1" id="rfc.xref.Part1.30"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a> for a general definition of header field syntax in HTTP messages.
     3442      </p>
     3443      <p id="rfc.section.8.3.1.p.2">The requirements for header field names are defined in <a href="#BCP90" id="rfc.xref.BCP90.2"><cite title="Registration Procedures for Message Header Fields">[BCP90]</cite></a>. Authors of specifications defining new fields are advised to keep the name as short as practical and to not prefix the name
    34533444         with "X-" unless the header field will never be used on the Internet. (The "x-" prefix idiom has been extensively misused
    34543445         in practice; it was intended to only be used as a mechanism for avoiding name collisions inside proprietary software or intranet
    34553446         processing, since the prefix would ensure that private names never collide with a newly registered Internet name.)
    34563447      </p>
    3457       <p id="rfc.section.9.3.1.p.3">New header field values typically have their syntax defined using ABNF (<a href="#RFC5234" id="rfc.xref.RFC5234.2"><cite title="Augmented BNF for Syntax Specifications: ABNF">[RFC5234]</cite></a>), using the extension defined in <a href="p1-messaging.html#abnf.extension" title="ABNF list extension: #rule">Appendix B</a> of <a href="#Part1" id="rfc.xref.Part1.32"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a> as necessary, and are usually constrained to the range of ASCII characters. Header fields needing a greater range of characters
     3448      <p id="rfc.section.8.3.1.p.3">New header field values typically have their syntax defined using ABNF (<a href="#RFC5234" id="rfc.xref.RFC5234.2"><cite title="Augmented BNF for Syntax Specifications: ABNF">[RFC5234]</cite></a>), using the extension defined in <a href="p1-messaging.html#abnf.extension" title="ABNF list extension: #rule">Appendix B</a> of <a href="#Part1" id="rfc.xref.Part1.31"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a> as necessary, and are usually constrained to the range of ASCII characters. Header fields needing a greater range of characters
    34583449         can use an encoding such as the one defined in <a href="#RFC5987" id="rfc.xref.RFC5987.1"><cite title="Character Set and Language Encoding for Hypertext Transfer Protocol (HTTP) Header Field Parameters">[RFC5987]</cite></a>.
    34593450      </p>
    3460       <p id="rfc.section.9.3.1.p.4">Because commas (",") are used as a generic delimiter between field-values, they need to be treated with care if they are allowed
     3451      <p id="rfc.section.8.3.1.p.4">Because commas (",") are used as a generic delimiter between field-values, they need to be treated with care if they are allowed
    34613452         in the field-value's payload. Typically, components that might contain a comma are protected with double-quotes using the
    3462          quoted-string ABNF production (<a href="p1-messaging.html#field.components" title="Field value components">Section 3.2.6</a> of <a href="#Part1" id="rfc.xref.Part1.33"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>).
    3463       </p>
    3464       <p id="rfc.section.9.3.1.p.5">For example, a textual date and a URI (either of which might contain a comma) could be safely carried in field-values like
     3453         quoted-string ABNF production (<a href="p1-messaging.html#field.components" title="Field value components">Section 3.2.6</a> of <a href="#Part1" id="rfc.xref.Part1.32"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>).
     3454      </p>
     3455      <p id="rfc.section.8.3.1.p.5">For example, a textual date and a URI (either of which might contain a comma) could be safely carried in field-values like
    34653456         these:
    34663457      </p>
    3467       <div id="rfc.figure.u.63"></div><pre class="text">  Example-URI-Field: "http://example.com/a.html,foo",
     3458      <div id="rfc.figure.u.62"></div><pre class="text">  Example-URI-Field: "http://example.com/a.html,foo",
    34683459                     "http://without-a-comma.example.com/"
    34693460  Example-Date-Field: "Sat, 04 May 1996", "Wed, 14 Sep 2005"
    3470 </pre><p id="rfc.section.9.3.1.p.7">Note that double-quote delimiters almost always are used with the quoted-string production; using a different syntax inside
     3461</pre><p id="rfc.section.8.3.1.p.7">Note that double-quote delimiters almost always are used with the quoted-string production; using a different syntax inside
    34713462         double-quotes will likely cause unnecessary confusion.
    34723463      </p>
    3473       <p id="rfc.section.9.3.1.p.8">Many header fields use a format including (case-insensitively) named parameters (for instance, <a href="#header.content-type" class="smpl">Content-Type</a>, defined in <a href="#header.content-type" id="rfc.xref.header.content-type.4" title="Content-Type">Section&nbsp;3.1.1.5</a>). Allowing both unquoted (token) and quoted (quoted-string) syntax for the parameter value enables recipients to use existing
     3464      <p id="rfc.section.8.3.1.p.8">Many header fields use a format including (case-insensitively) named parameters (for instance, <a href="#header.content-type" class="smpl">Content-Type</a>, defined in <a href="#header.content-type" id="rfc.xref.header.content-type.4" title="Content-Type">Section&nbsp;3.1.1.5</a>). Allowing both unquoted (token) and quoted (quoted-string) syntax for the parameter value enables recipients to use existing
    34743465         parser components. When allowing both forms, the meaning of a parameter value ought to be independent of the syntax used for
    34753466         it (for an example, see the notes on parameter handling for media types in <a href="#media.type" title="Media Type">Section&nbsp;3.1.1.1</a>).
    34763467      </p>
    3477       <p id="rfc.section.9.3.1.p.9">Authors of specifications defining new header fields are advised to consider documenting: </p>
     3468      <p id="rfc.section.8.3.1.p.9">Authors of specifications defining new header fields are advised to consider documenting: </p>
    34783469      <ul>
    34793470         <li>
    3480             <p>Whether the field is a single value, or whether it can be a list (delimited by commas; see <a href="p1-messaging.html#header.fields" title="Header Fields">Section 3.2</a> of <a href="#Part1" id="rfc.xref.Part1.34"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>).
     3471            <p>Whether the field is a single value, or whether it can be a list (delimited by commas; see <a href="p1-messaging.html#header.fields" title="Header Fields">Section 3.2</a> of <a href="#Part1" id="rfc.xref.Part1.33"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>).
    34813472            </p>
    34823473            <p>If it does not use the list syntax, document how to treat messages where the header field occurs multiple times (a sensible
     
    34943485         </li>
    34953486         <li>
    3496             <p>Whether it is appropriate to list the field-name in the <a href="p1-messaging.html#header.connection" class="smpl">Connection</a> header field (i.e., if the header field is to be hop-by-hop; see <a href="p1-messaging.html#header.connection" title="Connection">Section 6.1</a> of <a href="#Part1" id="rfc.xref.Part1.35"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>).
     3487            <p>Whether it is appropriate to list the field-name in the <a href="p1-messaging.html#header.connection" class="smpl">Connection</a> header field (i.e., if the header field is to be hop-by-hop; see <a href="p1-messaging.html#header.connection" title="Connection">Section 6.1</a> of <a href="#Part1" id="rfc.xref.Part1.34"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>).
    34973488            </p>
    34983489         </li>
     
    35053496         </li>
    35063497         <li>
    3507             <p>Whether the header field is useful or allowable in trailers (see <a href="p1-messaging.html#chunked.encoding" title="Chunked Transfer Coding">Section 4.1</a> of <a href="#Part1" id="rfc.xref.Part1.36"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>).
     3498            <p>Whether the header field is useful or allowable in trailers (see <a href="p1-messaging.html#chunked.encoding" title="Chunked Transfer Coding">Section 4.1</a> of <a href="#Part1" id="rfc.xref.Part1.35"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>).
    35083499            </p>
    35093500         </li>
     
    35123503         </li>
    35133504      </ul>
    3514       <h3 id="rfc.section.9.3.2"><a href="#rfc.section.9.3.2">9.3.2</a>&nbsp;<a id="header.field.registration" href="#header.field.registration">Registrations</a></h3>
    3515       <p id="rfc.section.9.3.2.p.1">The Message Header Field Registry shall be updated with the following permanent registrations:</p>
     3505      <h3 id="rfc.section.8.3.2"><a href="#rfc.section.8.3.2">8.3.2</a>&nbsp;<a id="header.field.registration" href="#header.field.registration">Registrations</a></h3>
     3506      <p id="rfc.section.8.3.2.p.1">The Message Header Field Registry shall be updated with the following permanent registrations:</p>
    35163507      <div id="rfc.table.4">
    35173508         <div id="iana.header.registration.table"></div>
     
    35303521                  <td class="left">http</td>
    35313522                  <td class="left">standard</td>
    3532                   <td class="left"> <a href="#header.accept" id="rfc.xref.header.accept.3" title="Accept">Section&nbsp;6.3.2</a>
     3523                  <td class="left"> <a href="#header.accept" id="rfc.xref.header.accept.3" title="Accept">Section&nbsp;5.3.2</a>
    35333524                  </td>
    35343525               </tr>
     
    35373528                  <td class="left">http</td>
    35383529                  <td class="left">standard</td>
    3539                   <td class="left"> <a href="#header.accept-charset" id="rfc.xref.header.accept-charset.2" title="Accept-Charset">Section&nbsp;6.3.3</a>
     3530                  <td class="left"> <a href="#header.accept-charset" id="rfc.xref.header.accept-charset.2" title="Accept-Charset">Section&nbsp;5.3.3</a>
    35403531                  </td>
    35413532               </tr>
     
    35443535                  <td class="left">http</td>
    35453536                  <td class="left">standard</td>
    3546                   <td class="left"> <a href="#header.accept-encoding" id="rfc.xref.header.accept-encoding.3" title="Accept-Encoding">Section&nbsp;6.3.4</a>
     3537                  <td class="left"> <a href="#header.accept-encoding" id="rfc.xref.header.accept-encoding.3" title="Accept-Encoding">Section&nbsp;5.3.4</a>
    35473538                  </td>
    35483539               </tr>
     
    35513542                  <td class="left">http</td>
    35523543                  <td class="left">standard</td>
    3553                   <td class="left"> <a href="#header.accept-language" id="rfc.xref.header.accept-language.2" title="Accept-Language">Section&nbsp;6.3.5</a>
     3544                  <td class="left"> <a href="#header.accept-language" id="rfc.xref.header.accept-language.2" title="Accept-Language">Section&nbsp;5.3.5</a>
    35543545                  </td>
    35553546               </tr>
     
    35583549                  <td class="left">http</td>
    35593550                  <td class="left">standard</td>
    3560                   <td class="left"> <a href="#header.allow" id="rfc.xref.header.allow.3" title="Allow">Section&nbsp;8.4.1</a>
     3551                  <td class="left"> <a href="#header.allow" id="rfc.xref.header.allow.3" title="Allow">Section&nbsp;7.4.1</a>
    35613552                  </td>
    35623553               </tr>
     
    35933584                  <td class="left">http</td>
    35943585                  <td class="left">standard</td>
    3595                   <td class="left"> <a href="#header.date" id="rfc.xref.header.date.3" title="Date">Section&nbsp;8.1.1.2</a>
     3586                  <td class="left"> <a href="#header.date" id="rfc.xref.header.date.3" title="Date">Section&nbsp;7.1.1.2</a>
    35963587                  </td>
    35973588               </tr>
     
    36003591                  <td class="left">http</td>
    36013592                  <td class="left">standard</td>
    3602                   <td class="left"> <a href="#header.expect" id="rfc.xref.header.expect.3" title="Expect">Section&nbsp;6.1.2</a>
     3593                  <td class="left"> <a href="#header.expect" id="rfc.xref.header.expect.3" title="Expect">Section&nbsp;5.1.2</a>
    36033594                  </td>
    36043595               </tr>
     
    36073598                  <td class="left">http</td>
    36083599                  <td class="left">standard</td>
    3609                   <td class="left"> <a href="#header.from" id="rfc.xref.header.from.2" title="From">Section&nbsp;6.5.1</a>
     3600                  <td class="left"> <a href="#header.from" id="rfc.xref.header.from.2" title="From">Section&nbsp;5.5.1</a>
    36103601                  </td>
    36113602               </tr>
     
    36143605                  <td class="left">http</td>
    36153606                  <td class="left">standard</td>
    3616                   <td class="left"> <a href="#header.location" id="rfc.xref.header.location.4" title="Location">Section&nbsp;8.1.2</a>
     3607                  <td class="left"> <a href="#header.location" id="rfc.xref.header.location.4" title="Location">Section&nbsp;7.1.2</a>
    36173608                  </td>
    36183609               </tr>
     
    36283619                  <td class="left">http</td>
    36293620                  <td class="left">standard</td>
    3630                   <td class="left"> <a href="#header.max-forwards" id="rfc.xref.header.max-forwards.4" title="Max-Forwards">Section&nbsp;6.1.1</a>
     3621                  <td class="left"> <a href="#header.max-forwards" id="rfc.xref.header.max-forwards.4" title="Max-Forwards">Section&nbsp;5.1.1</a>
    36313622                  </td>
    36323623               </tr>
     
    36353626                  <td class="left">http</td>
    36363627                  <td class="left">standard</td>
    3637                   <td class="left"> <a href="#header.referer" id="rfc.xref.header.referer.2" title="Referer">Section&nbsp;6.5.2</a>
     3628                  <td class="left"> <a href="#header.referer" id="rfc.xref.header.referer.2" title="Referer">Section&nbsp;5.5.2</a>
    36383629                  </td>
    36393630               </tr>
     
    36423633                  <td class="left">http</td>
    36433634                  <td class="left">standard</td>
    3644                   <td class="left"> <a href="#header.retry-after" id="rfc.xref.header.retry-after.3" title="Retry-After">Section&nbsp;8.1.3</a>
     3635                  <td class="left"> <a href="#header.retry-after" id="rfc.xref.header.retry-after.3" title="Retry-After">Section&nbsp;7.1.3</a>
    36453636                  </td>
    36463637               </tr>
     
    36493640                  <td class="left">http</td>
    36503641                  <td class="left">standard</td>
    3651                   <td class="left"> <a href="#header.server" id="rfc.xref.header.server.2" title="Server">Section&nbsp;8.4.2</a>
     3642                  <td class="left"> <a href="#header.server" id="rfc.xref.header.server.2" title="Server">Section&nbsp;7.4.2</a>
    36523643                  </td>
    36533644               </tr>
     
    36563647                  <td class="left">http</td>
    36573648                  <td class="left">standard</td>
    3658                   <td class="left"> <a href="#header.user-agent" id="rfc.xref.header.user-agent.2" title="User-Agent">Section&nbsp;6.5.3</a>
     3649                  <td class="left"> <a href="#header.user-agent" id="rfc.xref.header.user-agent.3" title="User-Agent">Section&nbsp;5.5.3</a>
    36593650                  </td>
    36603651               </tr>
     
    36633654                  <td class="left">http</td>
    36643655                  <td class="left">standard</td>
    3665                   <td class="left"> <a href="#header.vary" id="rfc.xref.header.vary.3" title="Vary">Section&nbsp;8.2.1</a>
     3656                  <td class="left"> <a href="#header.vary" id="rfc.xref.header.vary.3" title="Vary">Section&nbsp;7.2.1</a>
    36663657                  </td>
    36673658               </tr>
     
    36693660         </table>
    36703661      </div>
    3671       <p id="rfc.section.9.3.2.p.2">The change controller for the above registrations is: "IETF (iesg@ietf.org) - Internet Engineering Task Force".</p>
    3672       <h2 id="rfc.section.9.4"><a href="#rfc.section.9.4">9.4</a>&nbsp;<a id="content.coding.registry" href="#content.coding.registry">Content Coding Registry</a></h2>
    3673       <p id="rfc.section.9.4.p.1">The HTTP Content Coding Registry defines the name space for content coding names (<a href="p1-messaging.html#compression.codings" title="Compression Codings">Section 4.2</a> of <a href="#Part1" id="rfc.xref.Part1.37"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>). The content coding registry is maintained at &lt;<a href="http://www.iana.org/assignments/http-parameters">http://www.iana.org/assignments/http-parameters</a>&gt;.
    3674       </p>
    3675       <h3 id="rfc.section.9.4.1"><a href="#rfc.section.9.4.1">9.4.1</a>&nbsp;<a id="content.coding.procedure" href="#content.coding.procedure">Procedure</a></h3>
    3676       <p id="rfc.section.9.4.1.p.1">Content Coding registrations <em class="bcp14">MUST</em> include the following fields:
     3662      <p id="rfc.section.8.3.2.p.2">The change controller for the above registrations is: "IETF (iesg@ietf.org) - Internet Engineering Task Force".</p>
     3663      <h2 id="rfc.section.8.4"><a href="#rfc.section.8.4">8.4</a>&nbsp;<a id="content.coding.registry" href="#content.coding.registry">Content Coding Registry</a></h2>
     3664      <p id="rfc.section.8.4.p.1">The HTTP Content Coding Registry defines the name space for content coding names (<a href="p1-messaging.html#compression.codings" title="Compression Codings">Section 4.2</a> of <a href="#Part1" id="rfc.xref.Part1.36"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>). The content coding registry is maintained at &lt;<a href="http://www.iana.org/assignments/http-parameters">http://www.iana.org/assignments/http-parameters</a>&gt;.
     3665      </p>
     3666      <h3 id="rfc.section.8.4.1"><a href="#rfc.section.8.4.1">8.4.1</a>&nbsp;<a id="content.coding.procedure" href="#content.coding.procedure">Procedure</a></h3>
     3667      <p id="rfc.section.8.4.1.p.1">Content Coding registrations <em class="bcp14">MUST</em> include the following fields:
    36773668      </p>
    36783669      <ul>
     
    36813672         <li>Pointer to specification text</li>
    36823673      </ul>
    3683       <p id="rfc.section.9.4.1.p.2">Names of content codings <em class="bcp14">MUST NOT</em> overlap with names of transfer codings (<a href="p1-messaging.html#transfer.codings" title="Transfer Codings">Section 4</a> of <a href="#Part1" id="rfc.xref.Part1.38"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>), unless the encoding transformation is identical (as is the case for the compression codings defined in <a href="p1-messaging.html#compression.codings" title="Compression Codings">Section 4.2</a> of <a href="#Part1" id="rfc.xref.Part1.39"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>).
    3684       </p>
    3685       <p id="rfc.section.9.4.1.p.3">Values to be added to this name space require IETF Review (see <a href="http://tools.ietf.org/html/rfc5226#section-4.1">Section 4.1</a> of <a href="#RFC5226" id="rfc.xref.RFC5226.3"><cite title="Guidelines for Writing an IANA Considerations Section in RFCs">[RFC5226]</cite></a>), and <em class="bcp14">MUST</em> conform to the purpose of content coding defined in this section.
    3686       </p>
    3687       <h3 id="rfc.section.9.4.2"><a href="#rfc.section.9.4.2">9.4.2</a>&nbsp;<a id="content.coding.registration" href="#content.coding.registration">Registrations</a></h3>
    3688       <p id="rfc.section.9.4.2.p.1">The HTTP Content Codings Registry shall be updated with the registrations below:</p>
     3674      <p id="rfc.section.8.4.1.p.2">Names of content codings <em class="bcp14">MUST NOT</em> overlap with names of transfer codings (<a href="p1-messaging.html#transfer.codings" title="Transfer Codings">Section 4</a> of <a href="#Part1" id="rfc.xref.Part1.37"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>), unless the encoding transformation is identical (as is the case for the compression codings defined in <a href="p1-messaging.html#compression.codings" title="Compression Codings">Section 4.2</a> of <a href="#Part1" id="rfc.xref.Part1.38"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>).
     3675      </p>
     3676      <p id="rfc.section.8.4.1.p.3">Values to be added to this name space require IETF Review (see <a href="http://tools.ietf.org/html/rfc5226#section-4.1">Section 4.1</a> of <a href="#RFC5226" id="rfc.xref.RFC5226.3"><cite title="Guidelines for Writing an IANA Considerations Section in RFCs">[RFC5226]</cite></a>), and <em class="bcp14">MUST</em> conform to the purpose of content coding defined in this section.
     3677      </p>
     3678      <h3 id="rfc.section.8.4.2"><a href="#rfc.section.8.4.2">8.4.2</a>&nbsp;<a id="content.coding.registration" href="#content.coding.registration">Registrations</a></h3>
     3679      <p id="rfc.section.8.4.2.p.1">The HTTP Content Codings Registry shall be updated with the registrations below:</p>
    36893680      <div id="rfc.table.5">
    36903681         <div id="iana.content.coding.registration.table"></div>
     
    37013692                  <td class="left">compress</td>
    37023693                  <td class="left">UNIX "compress" program method</td>
    3703                   <td class="left"> <a href="p1-messaging.html#compress.coding" title="Compress Coding">Section 4.2.1</a> of <a href="#Part1" id="rfc.xref.Part1.40"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>
     3694                  <td class="left"> <a href="p1-messaging.html#compress.coding" title="Compress Coding">Section 4.2.1</a> of <a href="#Part1" id="rfc.xref.Part1.39"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>
    37043695                  </td>
    37053696               </tr>
     
    37083699                  <td class="left">"deflate" compression mechanism (<a href="#RFC1951" id="rfc.xref.RFC1951.1"><cite title="DEFLATE Compressed Data Format Specification version 1.3">[RFC1951]</cite></a>) used inside the "zlib" data format (<a href="#RFC1950" id="rfc.xref.RFC1950.1"><cite title="ZLIB Compressed Data Format Specification version 3.3">[RFC1950]</cite></a>)
    37093700                  </td>
    3710                   <td class="left"> <a href="p1-messaging.html#deflate.coding" title="Deflate Coding">Section 4.2.2</a> of <a href="#Part1" id="rfc.xref.Part1.41"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>
     3701                  <td class="left"> <a href="p1-messaging.html#deflate.coding" title="Deflate Coding">Section 4.2.2</a> of <a href="#Part1" id="rfc.xref.Part1.40"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>
    37113702                  </td>
    37123703               </tr>
     
    37143705                  <td class="left">gzip</td>
    37153706                  <td class="left">Same as GNU zip <a href="#RFC1952" id="rfc.xref.RFC1952.1"><cite title="GZIP file format specification version 4.3">[RFC1952]</cite></a></td>
    3716                   <td class="left"> <a href="p1-messaging.html#gzip.coding" title="Gzip Coding">Section 4.2.3</a> of <a href="#Part1" id="rfc.xref.Part1.42"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>
     3707                  <td class="left"> <a href="p1-messaging.html#gzip.coding" title="Gzip Coding">Section 4.2.3</a> of <a href="#Part1" id="rfc.xref.Part1.41"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>
    37173708                  </td>
    37183709               </tr>
     
    37213712                  <td class="left">reserved (synonym for "no encoding" in <a href="#header.accept-encoding" class="smpl">Accept-Encoding</a> header field)
    37223713                  </td>
    3723                   <td class="left"> <a href="#header.accept-encoding" id="rfc.xref.header.accept-encoding.4" title="Accept-Encoding">Section&nbsp;6.3.4</a>
     3714                  <td class="left"> <a href="#header.accept-encoding" id="rfc.xref.header.accept-encoding.4" title="Accept-Encoding">Section&nbsp;5.3.4</a>
    37243715                  </td>
    37253716               </tr>
     
    37273718         </table>
    37283719      </div>
    3729       <h1 id="rfc.section.10"><a href="#rfc.section.10">10.</a>&nbsp;<a id="security.considerations" href="#security.considerations">Security Considerations</a></h1>
    3730       <p id="rfc.section.10.p.1">This section is meant to inform application developers, information providers, and users of the security limitations in HTTP/1.1
     3720      <h1 id="rfc.section.9"><a href="#rfc.section.9">9.</a>&nbsp;<a id="security.considerations" href="#security.considerations">Security Considerations</a></h1>
     3721      <p id="rfc.section.9.p.1">This section is meant to inform application developers, information providers, and users of the security limitations in HTTP/1.1
    37313722         as described by this document. The discussion does not include definitive solutions to the problems revealed, though it does
    37323723         make some suggestions for reducing security risks.
    37333724      </p>
    3734       <h2 id="rfc.section.10.1"><a href="#rfc.section.10.1">10.1</a>&nbsp;<a id="security.sensitive" href="#security.sensitive">Transfer of Sensitive Information</a></h2>
    3735       <p id="rfc.section.10.1.p.1">Like any generic data transfer protocol, HTTP cannot regulate the content of the data that is transferred, nor is there any
     3725      <h2 id="rfc.section.9.1"><a href="#rfc.section.9.1">9.1</a>&nbsp;<a id="security.sensitive" href="#security.sensitive">Transfer of Sensitive Information</a></h2>
     3726      <p id="rfc.section.9.1.p.1">Like any generic data transfer protocol, HTTP cannot regulate the content of the data that is transferred, nor is there any
    37363727         a priori method of determining the sensitivity of any particular piece of information within the context of any given request.
    37373728         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
    37383729         special mention in this context: <a href="#header.server" class="smpl">Server</a>, <a href="p1-messaging.html#header.via" class="smpl">Via</a>, <a href="#header.referer" class="smpl">Referer</a> and <a href="#header.from" class="smpl">From</a>.
    37393730      </p>
    3740       <p id="rfc.section.10.1.p.2">Revealing the specific software version of the server might allow the server machine to become more vulnerable to attacks
     3731      <p id="rfc.section.9.1.p.2">Revealing the specific software version of the server might allow the server machine to become more vulnerable to attacks
    37413732         against software that is known to contain security holes. Implementers <em class="bcp14">SHOULD</em> make the <a href="#header.server" class="smpl">Server</a> header field a configurable option.
    37423733      </p>
    3743       <p id="rfc.section.10.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,
     3734      <p id="rfc.section.9.1.p.3">Proxies which serve as a portal through a network firewall <em class="bcp14">SHOULD</em> take special precautions regarding the transfer of header information that identifies the hosts behind the firewall. In particular,
    37443735         they <em class="bcp14">SHOULD</em> remove, or replace with sanitized versions, any <a href="p1-messaging.html#header.via" class="smpl">Via</a> fields generated behind the firewall.
    37453736      </p>
    3746       <p id="rfc.section.10.1.p.4">The <a href="#header.referer" class="smpl">Referer</a> header field allows reading patterns to be studied and reverse links drawn. Although it can be very useful, its power can
     3737      <p id="rfc.section.9.1.p.4">The <a href="#header.referer" class="smpl">Referer</a> header field allows reading patterns to be studied and reverse links drawn. Although it can be very useful, its power can
    37473738         be abused if user details are not separated from the information contained in the Referer. Even when the personal information
    37483739         has been removed, the Referer header field might indicate a private document's URI whose publication would be inappropriate.
    37493740      </p>
    3750       <p id="rfc.section.10.1.p.5">The information sent in the <a href="#header.from" class="smpl">From</a> field might conflict with the user's privacy interests or their site's security policy, and 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.
    3751       </p>
    3752       <p id="rfc.section.10.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
     3741      <p id="rfc.section.9.1.p.5">The information sent in the <a href="#header.from" class="smpl">From</a> field might conflict with the user's privacy interests or their site's security policy, and 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.
     3742      </p>
     3743      <p id="rfc.section.9.1.p.6">We suggest, though do not require, that a convenient toggle interface be provided for the user to enable or disable the sending
    37533744         of <a href="#header.from" class="smpl">From</a> and <a href="#header.referer" class="smpl">Referer</a> information.
    37543745      </p>
    3755       <p id="rfc.section.10.1.p.7">The <a href="#header.user-agent" class="smpl">User-Agent</a> (<a href="#header.user-agent" id="rfc.xref.header.user-agent.3" title="User-Agent">Section&nbsp;6.5.3</a>) or <a href="#header.server" class="smpl">Server</a> (<a href="#header.server" id="rfc.xref.header.server.3" title="Server">Section&nbsp;8.4.2</a>) header fields can sometimes be used to determine that a specific client or server has a particular security hole which might
     3746      <p id="rfc.section.9.1.p.7">The <a href="#header.user-agent" class="smpl">User-Agent</a> (<a href="#header.user-agent" id="rfc.xref.header.user-agent.4" title="User-Agent">Section&nbsp;5.5.3</a>) or <a href="#header.server" class="smpl">Server</a> (<a href="#header.server" id="rfc.xref.header.server.3" title="Server">Section&nbsp;7.4.2</a>) header fields can sometimes be used to determine that a specific client or server has a particular security hole which might
    37563747         be exploited. Unfortunately, this same information is often used for other valuable purposes for which HTTP currently has
    37573748         no better mechanism.
    37583749      </p>
    3759       <p id="rfc.section.10.1.p.8">Furthermore, the <a href="#header.user-agent" class="smpl">User-Agent</a> header field might contain enough entropy to be used, possibly in conjunction with other material, to uniquely identify the
     3750      <p id="rfc.section.9.1.p.8">Furthermore, the <a href="#header.user-agent" class="smpl">User-Agent</a> header field might contain enough entropy to be used, possibly in conjunction with other material, to uniquely identify the
    37603751         user.
    37613752      </p>
    3762       <p id="rfc.section.10.1.p.9">Some request methods, like TRACE (<a href="#TRACE" id="rfc.xref.TRACE.4" title="TRACE">Section&nbsp;5.3.8</a>), expose information that was sent in request header fields within the body of their response. Clients <em class="bcp14">SHOULD</em> be careful with sensitive information, like Cookies, Authorization credentials, and other header fields that might be used
     3753      <p id="rfc.section.9.1.p.9">Some request methods, like TRACE (<a href="#TRACE" id="rfc.xref.TRACE.4" title="TRACE">Section&nbsp;4.3.8</a>), expose information that was sent in request header fields within the body of their response. Clients <em class="bcp14">SHOULD</em> be careful with sensitive information, like Cookies, Authorization credentials, and other header fields that might be used
    37633754         to collect data from the client.
    37643755      </p>
    3765       <h2 id="rfc.section.10.2"><a href="#rfc.section.10.2">10.2</a>&nbsp;<a id="encoding.sensitive.information.in.uris" href="#encoding.sensitive.information.in.uris">Encoding Sensitive Information in URIs</a></h2>
    3766       <p id="rfc.section.10.2.p.1">Because the source of a link might be private information or might reveal an otherwise private information source, it is strongly
     3756      <h2 id="rfc.section.9.2"><a href="#rfc.section.9.2">9.2</a>&nbsp;<a id="encoding.sensitive.information.in.uris" href="#encoding.sensitive.information.in.uris">Encoding Sensitive Information in URIs</a></h2>
     3757      <p id="rfc.section.9.2.p.1">Because the source of a link might be private information or might reveal an otherwise private information source, it is strongly
    37673758         recommended that the user be able to select whether or not the <a href="#header.referer" class="smpl">Referer</a> field is sent. For example, a browser client could have a toggle switch for browsing openly/anonymously, which would respectively
    37683759         enable/disable the sending of Referer and From information.
    37693760      </p>
    3770       <p id="rfc.section.10.2.p.2">Clients <em class="bcp14">SHOULD NOT</em> include a <a href="#header.referer" class="smpl">Referer</a> header field in a (non-secure) HTTP request if the referring page was transferred with a secure protocol.
    3771       </p>
    3772       <p id="rfc.section.10.2.p.3">Authors of services <em class="bcp14">SHOULD NOT</em> use GET-based forms for the submission of sensitive data because that data will be placed in the request-target. Many existing
     3761      <p id="rfc.section.9.2.p.2">Clients <em class="bcp14">SHOULD NOT</em> include a <a href="#header.referer" class="smpl">Referer</a> header field in a (non-secure) HTTP request if the referring page was transferred with a secure protocol.
     3762      </p>
     3763      <p id="rfc.section.9.2.p.3">Authors of services <em class="bcp14">SHOULD NOT</em> use GET-based forms for the submission of sensitive data because that data will be placed in the request-target. Many existing
    37733764         servers, proxies, and user agents log or display the request-target in places where it might be visible to third parties.
    37743765         Such services can use POST-based form submission instead.
    37753766      </p>
    3776       <h2 id="rfc.section.10.3"><a href="#rfc.section.10.3">10.3</a>&nbsp;<a id="location.spoofing-leakage" href="#location.spoofing-leakage">Location Header Fields: Spoofing and Information Leakage</a></h2>
    3777       <p id="rfc.section.10.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 <a href="#header.location" class="smpl">Location</a> and <a href="#header.content-location" class="smpl">Content-Location</a> header fields in responses that are generated under control of said organizations to make sure that they do not attempt to
     3767      <h2 id="rfc.section.9.3"><a href="#rfc.section.9.3">9.3</a>&nbsp;<a id="location.spoofing-leakage" href="#location.spoofing-leakage">Location Header Fields: Spoofing and Information Leakage</a></h2>
     3768      <p id="rfc.section.9.3.p.1">If a single server supports multiple organizations that do not trust one another, then it <em class="bcp14">MUST</em> check the values of <a href="#header.location" class="smpl">Location</a> and <a href="#header.content-location" class="smpl">Content-Location</a> header fields in responses that are generated under control of said organizations to make sure that they do not attempt to
    37783769         invalidate resources over which they have no authority.
    37793770      </p>
    3780       <p id="rfc.section.10.3.p.2">Furthermore, appending the fragment identifier from one URI to another one obtained from a <a href="#header.location" class="smpl">Location</a> header field might leak confidential information to the target server — although the fragment identifier is not transmitted
     3771      <p id="rfc.section.9.3.p.2">Furthermore, appending the fragment identifier from one URI to another one obtained from a <a href="#header.location" class="smpl">Location</a> header field might leak confidential information to the target server — although the fragment identifier is not transmitted
    37813772         in the final request, it might be visible to the user agent through other means, such as scripting.
    37823773      </p>
    3783       <h2 id="rfc.section.10.4"><a href="#rfc.section.10.4">10.4</a>&nbsp;Security Considerations for CONNECT
     3774      <h2 id="rfc.section.9.4"><a href="#rfc.section.9.4">9.4</a>&nbsp;Security Considerations for CONNECT
    37843775      </h2>
    3785       <p id="rfc.section.10.4.p.1">Since tunneled data is opaque to the proxy, there are additional risks to tunneling to other well-known or reserved ports.
     3776      <p id="rfc.section.9.4.p.1">Since tunneled data is opaque to the proxy, there are additional risks to tunneling to other well-known or reserved ports.
    37863777         An HTTP client CONNECTing to port 25 could relay spam via SMTP, for example. As such, proxies <em class="bcp14">SHOULD</em> restrict CONNECT access to a small number of known ports.
    37873778      </p>
    3788       <h2 id="rfc.section.10.5"><a href="#rfc.section.10.5">10.5</a>&nbsp;<a id="privacy.issues.connected.to.accept.header.fields" href="#privacy.issues.connected.to.accept.header.fields">Privacy Issues Connected to Accept Header Fields</a></h2>
    3789       <p id="rfc.section.10.5.p.1">Accept header fields can reveal information about the user to all servers which are accessed. The <a href="#header.accept-language" class="smpl">Accept-Language</a> header field in particular can reveal information the user would consider to be of a private nature, because the understanding
     3779      <h2 id="rfc.section.9.5"><a href="#rfc.section.9.5">9.5</a>&nbsp;<a id="privacy.issues.connected.to.accept.header.fields" href="#privacy.issues.connected.to.accept.header.fields">Privacy Issues Connected to Accept Header Fields</a></h2>
     3780      <p id="rfc.section.9.5.p.1">Accept header fields can reveal information about the user to all servers which are accessed. The <a href="#header.accept-language" class="smpl">Accept-Language</a> header field in particular can reveal information the user would consider to be of a private nature, because the understanding
    37903781         of particular languages is often strongly correlated to the membership of a particular ethnic group. User agents which offer
    37913782         the option to configure the contents of an Accept-Language header field to be sent in every request are strongly encouraged
    37923783         to let the configuration process include a message which makes the user aware of the loss of privacy involved.
    37933784      </p>
    3794       <p id="rfc.section.10.5.p.2">An approach that limits the loss of privacy would be for a user agent to omit the sending of Accept-Language header fields
     3785      <p id="rfc.section.9.5.p.2">An approach that limits the loss of privacy would be for a user agent to omit the sending of Accept-Language header fields
    37953786         by default, and to ask the user whether or not to start sending Accept-Language header fields to a server if it detects, by
    37963787         looking for any <a href="#header.vary" class="smpl">Vary</a> header fields generated by the server, that such sending could improve the quality of service.
    37973788      </p>
    3798       <p id="rfc.section.10.5.p.3">Elaborate user-customized accept header fields sent in every request, in particular if these include quality values, can be
     3789      <p id="rfc.section.9.5.p.3">Elaborate user-customized accept header fields sent in every request, in particular if these include quality values, can be
    37993790         used by servers as relatively reliable and long-lived user identifiers. Such user identifiers would allow content providers
    38003791         to do click-trail tracking, and would allow collaborating content providers to match cross-server click-trails or form submissions
     
    38053796         field configurability <em class="bcp14">SHOULD</em> warn users about the loss of privacy which can be involved.
    38063797      </p>
    3807       <h1 id="rfc.section.11"><a href="#rfc.section.11">11.</a>&nbsp;<a id="acks" href="#acks">Acknowledgments</a></h1>
    3808       <p id="rfc.section.11.p.1">See <a href="p1-messaging.html#acks" title="Acknowledgments">Section 9</a> of <a href="#Part1" id="rfc.xref.Part1.43"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>.
    3809       </p>
    3810       <h1 id="rfc.references"><a id="rfc.section.12" href="#rfc.section.12">12.</a> References
     3798      <h1 id="rfc.section.10"><a href="#rfc.section.10">10.</a>&nbsp;<a id="acks" href="#acks">Acknowledgments</a></h1>
     3799      <p id="rfc.section.10.p.1">See <a href="p1-messaging.html#acks" title="Acknowledgments">Section 9</a> of <a href="#Part1" id="rfc.xref.Part1.42"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>.
     3800      </p>
     3801      <h1 id="rfc.references"><a id="rfc.section.11" href="#rfc.section.11">11.</a> References
    38113802      </h1>
    3812       <h2 id="rfc.references.1"><a href="#rfc.section.12.1" id="rfc.section.12.1">12.1</a> Normative References
     3803      <h2 id="rfc.references.1"><a href="#rfc.section.11.1" id="rfc.section.11.1">11.1</a> Normative References
    38133804      </h2>
    38143805      <table>                               
     
    38943885         </tr>
    38953886      </table>
    3896       <h2 id="rfc.references.2"><a href="#rfc.section.12.2" id="rfc.section.12.2">12.2</a> Informative References
     3887      <h2 id="rfc.references.2"><a href="#rfc.section.11.2" id="rfc.section.11.2">11.2</a> Informative References
    38973888      </h2>
    38983889      <table>                                         
     
    40284019         MIME environments.
    40294020      </p>
    4030       <div id="rfc.figure.u.64"></div><pre class="inline"><span id="rfc.iref.g.62"></span>  <a href="#mime-version" class="smpl">MIME-Version</a> = 1*<a href="#imported.abnf" class="smpl">DIGIT</a> "." 1*<a href="#imported.abnf" class="smpl">DIGIT</a>
     4021      <div id="rfc.figure.u.63"></div><pre class="inline"><span id="rfc.iref.g.62"></span>  <a href="#mime-version" class="smpl">MIME-Version</a> = 1*<a href="#imported.abnf" class="smpl">DIGIT</a> "." 1*<a href="#imported.abnf" class="smpl">DIGIT</a>
    40314022</pre><p id="rfc.section.A.1.p.3">MIME version "1.0" is the default for use in HTTP/1.1. However, HTTP/1.1 message parsing and semantics are defined by this
    40324023         document and not the MIME specification.
     
    40444035      </p>
    40454036      <h2 id="rfc.section.A.3"><a href="#rfc.section.A.3">A.3</a>&nbsp;<a id="conversion.of.date.formats" href="#conversion.of.date.formats">Conversion of Date Formats</a></h2>
    4046       <p id="rfc.section.A.3.p.1">HTTP/1.1 uses a restricted set of date formats (<a href="#http.date" title="Date/Time Formats">Section&nbsp;8.1.1.1</a>) to simplify the process of date comparison. Proxies and gateways from other protocols <em class="bcp14">SHOULD</em> ensure that any <a href="#header.date" class="smpl">Date</a> header field present in a message conforms to one of the HTTP/1.1 formats and rewrite the date if necessary.
     4037      <p id="rfc.section.A.3.p.1">HTTP/1.1 uses a restricted set of date formats (<a href="#http.date" title="Date/Time Formats">Section&nbsp;7.1.1.1</a>) to simplify the process of date comparison. Proxies and gateways from other protocols <em class="bcp14">SHOULD</em> ensure that any <a href="#header.date" class="smpl">Date</a> header field present in a message conforms to one of the HTTP/1.1 formats and rewrite the date if necessary.
    40474038      </p>
    40484039      <h2 id="rfc.section.A.4"><a href="#rfc.section.A.4">A.4</a>&nbsp;<a id="introduction.of.content-encoding" href="#introduction.of.content-encoding">Introduction of Content-Encoding</a></h2>
     
    40884079         resources). (<a href="#header.content-location" id="rfc.xref.header.content-location.5" title="Content-Location">Section&nbsp;3.1.4.2</a>)
    40894080      </p>
    4090       <p id="rfc.section.C.p.6">GET requests can have a body; it just has no meaning. (<a href="#GET" id="rfc.xref.GET.4" title="GET">Section&nbsp;5.3.1</a>)
    4091       </p>
    4092       <p id="rfc.section.C.p.7">The definition of POST has been clarified. (<a href="#POST" id="rfc.xref.POST.4" title="POST">Section&nbsp;5.3.3</a>)
    4093       </p>
    4094       <p id="rfc.section.C.p.8">Servers are no longer required to handle all Content-* header fields in requests. (<a href="#PUT" id="rfc.xref.PUT.4" title="PUT">Section&nbsp;5.3.4</a>)
    4095       </p>
    4096       <p id="rfc.section.C.p.9">Use of <a href="p5-range.html#header.content-range" class="smpl">Content-Range</a> is explicitly banned on PUT requests. (<a href="#PUT" id="rfc.xref.PUT.5" title="PUT">Section&nbsp;5.3.4</a>)
    4097       </p>
    4098       <p id="rfc.section.C.p.10">The CONNECT method is now defined by this specification, taking over from <a href="#RFC2817" id="rfc.xref.RFC2817.2"><cite title="Upgrading to TLS Within HTTP/1.1">[RFC2817]</cite></a>. (<a href="#CONNECT" id="rfc.xref.CONNECT.3" title="CONNECT">Section&nbsp;5.3.6</a>)
    4099       </p>
    4100       <p id="rfc.section.C.p.11">The requirements upon and semantics of CONNECT request and response bodies have been clarified. (<a href="#CONNECT" id="rfc.xref.CONNECT.4" title="CONNECT">Section&nbsp;5.3.6</a>)
    4101       </p>
    4102       <p id="rfc.section.C.p.12">The <a href="#OPTIONS" class="smpl">OPTIONS</a> and <a href="#TRACE" class="smpl">TRACE</a> request methods are now defined as being safe. (<a href="#OPTIONS" id="rfc.xref.OPTIONS.4" title="OPTIONS">Section&nbsp;5.3.7</a> and <a href="#TRACE" id="rfc.xref.TRACE.5" title="TRACE">Section&nbsp;5.3.8</a>)
     4081      <p id="rfc.section.C.p.6">GET requests can have a body; it just has no meaning. (<a href="#GET" id="rfc.xref.GET.4" title="GET">Section&nbsp;4.3.1</a>)
     4082      </p>
     4083      <p id="rfc.section.C.p.7">The definition of POST has been clarified. (<a href="#POST" id="rfc.xref.POST.4" title="POST">Section&nbsp;4.3.3</a>)
     4084      </p>
     4085      <p id="rfc.section.C.p.8">Servers are no longer required to handle all Content-* header fields in requests. (<a href="#PUT" id="rfc.xref.PUT.4" title="PUT">Section&nbsp;4.3.4</a>)
     4086      </p>
     4087      <p id="rfc.section.C.p.9">Use of <a href="p5-range.html#header.content-range" class="smpl">Content-Range</a> is explicitly banned on PUT requests. (<a href="#PUT" id="rfc.xref.PUT.5" title="PUT">Section&nbsp;4.3.4</a>)
     4088      </p>
     4089      <p id="rfc.section.C.p.10">The CONNECT method is now defined by this specification, taking over from <a href="#RFC2817" id="rfc.xref.RFC2817.2"><cite title="Upgrading to TLS Within HTTP/1.1">[RFC2817]</cite></a>. (<a href="#CONNECT" id="rfc.xref.CONNECT.3" title="CONNECT">Section&nbsp;4.3.6</a>)
     4090      </p>
     4091      <p id="rfc.section.C.p.11">The requirements upon and semantics of CONNECT request and response bodies have been clarified. (<a href="#CONNECT" id="rfc.xref.CONNECT.4" title="CONNECT">Section&nbsp;4.3.6</a>)
     4092      </p>
     4093      <p id="rfc.section.C.p.12">The <a href="#OPTIONS" class="smpl">OPTIONS</a> and <a href="#TRACE" class="smpl">TRACE</a> request methods are now defined as being safe. (<a href="#OPTIONS" id="rfc.xref.OPTIONS.4" title="OPTIONS">Section&nbsp;4.3.7</a> and <a href="#TRACE" id="rfc.xref.TRACE.5" title="TRACE">Section&nbsp;4.3.8</a>)
    41034094      </p>
    41044095      <p id="rfc.section.C.p.13">The <a href="#header.max-forwards" class="smpl">Max-Forwards</a> header field is now restricted to the OPTIONS and TRACE methods (previously, extension methods could have used it as well).
    4105          (<a href="#header.max-forwards" id="rfc.xref.header.max-forwards.5" title="Max-Forwards">Section&nbsp;6.1.1</a>)
     4096         (<a href="#header.max-forwards" id="rfc.xref.header.max-forwards.5" title="Max-Forwards">Section&nbsp;5.1.1</a>)
    41064097      </p>
    41074098      <p id="rfc.section.C.p.14">The ABNF for the "<a href="#header.expect" class="smpl">Expect</a>" header field has been both fixed (allowing parameters for value-less expectations as well) and simplified (allowing trailing
    4108          semicolons after "100-continue" when they were invalid before). (<a href="#header.expect" id="rfc.xref.header.expect.4" title="Expect">Section&nbsp;6.1.2</a>)
    4109       </p>
    4110       <p id="rfc.section.C.p.15">Special casing for ISO-8859-1 in <a href="#header.accept-charset" class="smpl">Accept-Charset</a> has been removed. (<a href="#header.accept-charset" id="rfc.xref.header.accept-charset.3" title="Accept-Charset">Section&nbsp;6.3.3</a>)
    4111       </p>
    4112       <p id="rfc.section.C.p.16">Requirements for sending the Date header field have been clarified. (<a href="#header.date" id="rfc.xref.header.date.4" title="Date">Section&nbsp;8.1.1.2</a>)
    4113       </p>
    4114       <p id="rfc.section.C.p.17">The <a href="#header.referer" class="smpl">Referer</a> header field can now have a value of "about:blank" as an alternative to not sending a Referer header field. (<a href="#header.referer" id="rfc.xref.header.referer.3" title="Referer">Section&nbsp;6.5.2</a>)
     4099         semicolons after "100-continue" when they were invalid before). (<a href="#header.expect" id="rfc.xref.header.expect.4" title="Expect">Section&nbsp;5.1.2</a>)
     4100      </p>
     4101      <p id="rfc.section.C.p.15">Special casing for ISO-8859-1 in <a href="#header.accept-charset" class="smpl">Accept-Charset</a> has been removed. (<a href="#header.accept-charset" id="rfc.xref.header.accept-charset.3" title="Accept-Charset">Section&nbsp;5.3.3</a>)
     4102      </p>
     4103      <p id="rfc.section.C.p.16">Requirements for sending the Date header field have been clarified. (<a href="#header.date" id="rfc.xref.header.date.4" title="Date">Section&nbsp;7.1.1.2</a>)
     4104      </p>
     4105      <p id="rfc.section.C.p.17">The <a href="#header.referer" class="smpl">Referer</a> header field can now have a value of "about:blank" as an alternative to not sending a Referer header field. (<a href="#header.referer" id="rfc.xref.header.referer.3" title="Referer">Section&nbsp;5.5.2</a>)