Changeset 1855


Ignore:
Timestamp:
03/09/12 06:21:26 (10 years ago)
Author:
fielding@…
Message:

(editorial) move payload section to immediately follow representation

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

Legend:

Unmodified
Added
Removed

  • draft-ietf-httpbis/latest/p2-semantics.html

    r1854 r1855  
    474474      <link rel="Chapter" title="2 Resource" href="#rfc.section.2">
    475475      <link rel="Chapter" title="3 Representation" href="#rfc.section.3">
    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 Protocol Parameters" href="#rfc.section.8">
    481       <link rel="Chapter" title="9 Payload" href="#rfc.section.9">
     476      <link rel="Chapter" title="4 Payload" 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 Protocol Parameters" href="#rfc.section.9">
    482482      <link rel="Chapter" title="10 Header Field Definitions" href="#rfc.section.10">
    483483      <link rel="Chapter" title="11 IANA Considerations" href="#rfc.section.11">
    … …  
    598598            </ul>
    599599         </li>
    600          <li><a href="#rfc.section.4">4.</a>&nbsp;&nbsp;&nbsp;<a href="#methods">Request Methods</a><ul>
    601                <li><a href="#rfc.section.4.1">4.1</a>&nbsp;&nbsp;&nbsp;<a href="#method.overview">Overview</a></li>
    602                <li><a href="#rfc.section.4.2">4.2</a>&nbsp;&nbsp;&nbsp;<a href="#method.properties">Common Method Properties</a><ul>
    603                      <li><a href="#rfc.section.4.2.1">4.2.1</a>&nbsp;&nbsp;&nbsp;<a href="#safe.methods">Safe Methods</a></li>
    604                      <li><a href="#rfc.section.4.2.2">4.2.2</a>&nbsp;&nbsp;&nbsp;<a href="#idempotent.methods">Idempotent Methods</a></li>
    605                      <li><a href="#rfc.section.4.2.3">4.2.3</a>&nbsp;&nbsp;&nbsp;<a href="#cacheable.methods">Cacheable Methods</a></li>
     600         <li><a href="#rfc.section.4">4.</a>&nbsp;&nbsp;&nbsp;<a href="#payload">Payload</a><ul>
     601               <li><a href="#rfc.section.4.1">4.1</a>&nbsp;&nbsp;&nbsp;<a href="#payload.header.fields">Payload Header Fields</a></li>
     602               <li><a href="#rfc.section.4.2">4.2</a>&nbsp;&nbsp;&nbsp;<a href="#payload.body">Payload Body</a></li>
     603            </ul>
     604         </li>
     605         <li><a href="#rfc.section.5">5.</a>&nbsp;&nbsp;&nbsp;<a href="#methods">Request Methods</a><ul>
     606               <li><a href="#rfc.section.5.1">5.1</a>&nbsp;&nbsp;&nbsp;<a href="#method.overview">Overview</a></li>
     607               <li><a href="#rfc.section.5.2">5.2</a>&nbsp;&nbsp;&nbsp;<a href="#method.properties">Common Method Properties</a><ul>
     608                     <li><a href="#rfc.section.5.2.1">5.2.1</a>&nbsp;&nbsp;&nbsp;<a href="#safe.methods">Safe Methods</a></li>
     609                     <li><a href="#rfc.section.5.2.2">5.2.2</a>&nbsp;&nbsp;&nbsp;<a href="#idempotent.methods">Idempotent Methods</a></li>
     610                     <li><a href="#rfc.section.5.2.3">5.2.3</a>&nbsp;&nbsp;&nbsp;<a href="#cacheable.methods">Cacheable Methods</a></li>
    606611                  </ul>
    607612               </li>
    608                <li><a href="#rfc.section.4.3">4.3</a>&nbsp;&nbsp;&nbsp;<a href="#method.definitions">Method Definitions</a><ul>
    609                      <li><a href="#rfc.section.4.3.1">4.3.1</a>&nbsp;&nbsp;&nbsp;<a href="#GET">GET</a></li>
    610                      <li><a href="#rfc.section.4.3.2">4.3.2</a>&nbsp;&nbsp;&nbsp;<a href="#HEAD">HEAD</a></li>
    611                      <li><a href="#rfc.section.4.3.3">4.3.3</a>&nbsp;&nbsp;&nbsp;<a href="#POST">POST</a></li>
    612                      <li><a href="#rfc.section.4.3.4">4.3.4</a>&nbsp;&nbsp;&nbsp;<a href="#PUT">PUT</a></li>
    613                      <li><a href="#rfc.section.4.3.5">4.3.5</a>&nbsp;&nbsp;&nbsp;<a href="#DELETE">DELETE</a></li>
    614                      <li><a href="#rfc.section.4.3.6">4.3.6</a>&nbsp;&nbsp;&nbsp;<a href="#CONNECT">CONNECT</a></li>
    615                      <li><a href="#rfc.section.4.3.7">4.3.7</a>&nbsp;&nbsp;&nbsp;<a href="#OPTIONS">OPTIONS</a></li>
    616                      <li><a href="#rfc.section.4.3.8">4.3.8</a>&nbsp;&nbsp;&nbsp;<a href="#TRACE">TRACE</a></li>
     613               <li><a href="#rfc.section.5.3">5.3</a>&nbsp;&nbsp;&nbsp;<a href="#method.definitions">Method Definitions</a><ul>
     614                     <li><a href="#rfc.section.5.3.1">5.3.1</a>&nbsp;&nbsp;&nbsp;<a href="#GET">GET</a></li>
     615                     <li><a href="#rfc.section.5.3.2">5.3.2</a>&nbsp;&nbsp;&nbsp;<a href="#HEAD">HEAD</a></li>
     616                     <li><a href="#rfc.section.5.3.3">5.3.3</a>&nbsp;&nbsp;&nbsp;<a href="#POST">POST</a></li>
     617                     <li><a href="#rfc.section.5.3.4">5.3.4</a>&nbsp;&nbsp;&nbsp;<a href="#PUT">PUT</a></li>
     618                     <li><a href="#rfc.section.5.3.5">5.3.5</a>&nbsp;&nbsp;&nbsp;<a href="#DELETE">DELETE</a></li>
     619                     <li><a href="#rfc.section.5.3.6">5.3.6</a>&nbsp;&nbsp;&nbsp;<a href="#CONNECT">CONNECT</a></li>
     620                     <li><a href="#rfc.section.5.3.7">5.3.7</a>&nbsp;&nbsp;&nbsp;<a href="#OPTIONS">OPTIONS</a></li>
     621                     <li><a href="#rfc.section.5.3.8">5.3.8</a>&nbsp;&nbsp;&nbsp;<a href="#TRACE">TRACE</a></li>
    617622                  </ul>
    618623               </li>
    619624            </ul>
    620625         </li>
    621          <li><a href="#rfc.section.5">5.</a>&nbsp;&nbsp;&nbsp;<a href="#request.header.fields">Request Header Fields</a><ul>
    622                <li><a href="#rfc.section.5.1">5.1</a>&nbsp;&nbsp;&nbsp;<a href="#request.controls">Controls</a></li>
    623                <li><a href="#rfc.section.5.2">5.2</a>&nbsp;&nbsp;&nbsp;<a href="#request.conditionals">Conditionals</a></li>
    624                <li><a href="#rfc.section.5.3">5.3</a>&nbsp;&nbsp;&nbsp;<a href="#request.conneg">Content Negotiation</a></li>
    625                <li><a href="#rfc.section.5.4">5.4</a>&nbsp;&nbsp;&nbsp;<a href="#request.auth">Authentication</a></li>
    626                <li><a href="#rfc.section.5.5">5.5</a>&nbsp;&nbsp;&nbsp;<a href="#request.context">Context</a></li>
     626         <li><a href="#rfc.section.6">6.</a>&nbsp;&nbsp;&nbsp;<a href="#request.header.fields">Request Header Fields</a><ul>
     627               <li><a href="#rfc.section.6.1">6.1</a>&nbsp;&nbsp;&nbsp;<a href="#request.controls">Controls</a></li>
     628               <li><a href="#rfc.section.6.2">6.2</a>&nbsp;&nbsp;&nbsp;<a href="#request.conditionals">Conditionals</a></li>
     629               <li><a href="#rfc.section.6.3">6.3</a>&nbsp;&nbsp;&nbsp;<a href="#request.conneg">Content Negotiation</a></li>
     630               <li><a href="#rfc.section.6.4">6.4</a>&nbsp;&nbsp;&nbsp;<a href="#request.auth">Authentication</a></li>
     631               <li><a href="#rfc.section.6.5">6.5</a>&nbsp;&nbsp;&nbsp;<a href="#request.context">Context</a></li>
    627632            </ul>
    628633         </li>
    629          <li><a href="#rfc.section.6">6.</a>&nbsp;&nbsp;&nbsp;<a href="#status.codes">Response Status Codes</a><ul>
    630                <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>
    631                <li><a href="#rfc.section.6.2">6.2</a>&nbsp;&nbsp;&nbsp;<a href="#status.1xx">Informational 1xx</a><ul>
    632                      <li><a href="#rfc.section.6.2.1">6.2.1</a>&nbsp;&nbsp;&nbsp;<a href="#status.100">100 Continue</a></li>
    633                      <li><a href="#rfc.section.6.2.2">6.2.2</a>&nbsp;&nbsp;&nbsp;<a href="#status.101">101 Switching Protocols</a></li>
     634         <li><a href="#rfc.section.7">7.</a>&nbsp;&nbsp;&nbsp;<a href="#status.codes">Response Status Codes</a><ul>
     635               <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>
     636               <li><a href="#rfc.section.7.2">7.2</a>&nbsp;&nbsp;&nbsp;<a href="#status.1xx">Informational 1xx</a><ul>
     637                     <li><a href="#rfc.section.7.2.1">7.2.1</a>&nbsp;&nbsp;&nbsp;<a href="#status.100">100 Continue</a></li>
     638                     <li><a href="#rfc.section.7.2.2">7.2.2</a>&nbsp;&nbsp;&nbsp;<a href="#status.101">101 Switching Protocols</a></li>
    634639                  </ul>
    635640               </li>
    636                <li><a href="#rfc.section.6.3">6.3</a>&nbsp;&nbsp;&nbsp;<a href="#status.2xx">Successful 2xx</a><ul>
    637                      <li><a href="#rfc.section.6.3.1">6.3.1</a>&nbsp;&nbsp;&nbsp;<a href="#status.200">200 OK</a></li>
    638                      <li><a href="#rfc.section.6.3.2">6.3.2</a>&nbsp;&nbsp;&nbsp;<a href="#status.201">201 Created</a></li>
    639                      <li><a href="#rfc.section.6.3.3">6.3.3</a>&nbsp;&nbsp;&nbsp;<a href="#status.202">202 Accepted</a></li>
    640                      <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>
    641                      <li><a href="#rfc.section.6.3.5">6.3.5</a>&nbsp;&nbsp;&nbsp;<a href="#status.204">204 No Content</a></li>
    642                      <li><a href="#rfc.section.6.3.6">6.3.6</a>&nbsp;&nbsp;&nbsp;<a href="#status.205">205 Reset Content</a></li>
     641               <li><a href="#rfc.section.7.3">7.3</a>&nbsp;&nbsp;&nbsp;<a href="#status.2xx">Successful 2xx</a><ul>
     642                     <li><a href="#rfc.section.7.3.1">7.3.1</a>&nbsp;&nbsp;&nbsp;<a href="#status.200">200 OK</a></li>
     643                     <li><a href="#rfc.section.7.3.2">7.3.2</a>&nbsp;&nbsp;&nbsp;<a href="#status.201">201 Created</a></li>
     644                     <li><a href="#rfc.section.7.3.3">7.3.3</a>&nbsp;&nbsp;&nbsp;<a href="#status.202">202 Accepted</a></li>
     645                     <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>
     646                     <li><a href="#rfc.section.7.3.5">7.3.5</a>&nbsp;&nbsp;&nbsp;<a href="#status.204">204 No Content</a></li>
     647                     <li><a href="#rfc.section.7.3.6">7.3.6</a>&nbsp;&nbsp;&nbsp;<a href="#status.205">205 Reset Content</a></li>
    643648                  </ul>
    644649               </li>
    645                <li><a href="#rfc.section.6.4">6.4</a>&nbsp;&nbsp;&nbsp;<a href="#status.3xx">Redirection 3xx</a><ul>
    646                      <li><a href="#rfc.section.6.4.1">6.4.1</a>&nbsp;&nbsp;&nbsp;<a href="#status.300">300 Multiple Choices</a></li>
    647                      <li><a href="#rfc.section.6.4.2">6.4.2</a>&nbsp;&nbsp;&nbsp;<a href="#status.301">301 Moved Permanently</a></li>
    648                      <li><a href="#rfc.section.6.4.3">6.4.3</a>&nbsp;&nbsp;&nbsp;<a href="#status.302">302 Found</a></li>
    649                      <li><a href="#rfc.section.6.4.4">6.4.4</a>&nbsp;&nbsp;&nbsp;<a href="#status.303">303 See Other</a></li>
    650                      <li><a href="#rfc.section.6.4.5">6.4.5</a>&nbsp;&nbsp;&nbsp;<a href="#status.305">305 Use Proxy</a></li>
    651                      <li><a href="#rfc.section.6.4.6">6.4.6</a>&nbsp;&nbsp;&nbsp;<a href="#status.306">306 (Unused)</a></li>
    652                      <li><a href="#rfc.section.6.4.7">6.4.7</a>&nbsp;&nbsp;&nbsp;<a href="#status.307">307 Temporary Redirect</a></li>
     650               <li><a href="#rfc.section.7.4">7.4</a>&nbsp;&nbsp;&nbsp;<a href="#status.3xx">Redirection 3xx</a><ul>
     651                     <li><a href="#rfc.section.7.4.1">7.4.1</a>&nbsp;&nbsp;&nbsp;<a href="#status.300">300 Multiple Choices</a></li>
     652                     <li><a href="#rfc.section.7.4.2">7.4.2</a>&nbsp;&nbsp;&nbsp;<a href="#status.301">301 Moved Permanently</a></li>
     653                     <li><a href="#rfc.section.7.4.3">7.4.3</a>&nbsp;&nbsp;&nbsp;<a href="#status.302">302 Found</a></li>
     654                     <li><a href="#rfc.section.7.4.4">7.4.4</a>&nbsp;&nbsp;&nbsp;<a href="#status.303">303 See Other</a></li>
     655                     <li><a href="#rfc.section.7.4.5">7.4.5</a>&nbsp;&nbsp;&nbsp;<a href="#status.305">305 Use Proxy</a></li>
     656                     <li><a href="#rfc.section.7.4.6">7.4.6</a>&nbsp;&nbsp;&nbsp;<a href="#status.306">306 (Unused)</a></li>
     657                     <li><a href="#rfc.section.7.4.7">7.4.7</a>&nbsp;&nbsp;&nbsp;<a href="#status.307">307 Temporary Redirect</a></li>
    653658                  </ul>
    654659               </li>
    655                <li><a href="#rfc.section.6.5">6.5</a>&nbsp;&nbsp;&nbsp;<a href="#status.4xx">Client Error 4xx</a><ul>
    656                      <li><a href="#rfc.section.6.5.1">6.5.1</a>&nbsp;&nbsp;&nbsp;<a href="#status.400">400 Bad Request</a></li>
    657                      <li><a href="#rfc.section.6.5.2">6.5.2</a>&nbsp;&nbsp;&nbsp;<a href="#status.402">402 Payment Required</a></li>
    658                      <li><a href="#rfc.section.6.5.3">6.5.3</a>&nbsp;&nbsp;&nbsp;<a href="#status.403">403 Forbidden</a></li>
    659                      <li><a href="#rfc.section.6.5.4">6.5.4</a>&nbsp;&nbsp;&nbsp;<a href="#status.404">404 Not Found</a></li>
    660                      <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>
    661                      <li><a href="#rfc.section.6.5.6">6.5.6</a>&nbsp;&nbsp;&nbsp;<a href="#status.406">406 Not Acceptable</a></li>
    662                      <li><a href="#rfc.section.6.5.7">6.5.7</a>&nbsp;&nbsp;&nbsp;<a href="#status.408">408 Request Timeout</a></li>
    663                      <li><a href="#rfc.section.6.5.8">6.5.8</a>&nbsp;&nbsp;&nbsp;<a href="#status.409">409 Conflict</a></li>
    664                      <li><a href="#rfc.section.6.5.9">6.5.9</a>&nbsp;&nbsp;&nbsp;<a href="#status.410">410 Gone</a></li>
    665                      <li><a href="#rfc.section.6.5.10">6.5.10</a>&nbsp;&nbsp;&nbsp;<a href="#status.411">411 Length Required</a></li>
    666                      <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>
    667                      <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>
    668                      <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>
    669                      <li><a href="#rfc.section.6.5.14">6.5.14</a>&nbsp;&nbsp;&nbsp;<a href="#status.417">417 Expectation Failed</a></li>
    670                      <li><a href="#rfc.section.6.5.15">6.5.15</a>&nbsp;&nbsp;&nbsp;<a href="#status.426">426 Upgrade Required</a></li>
     660               <li><a href="#rfc.section.7.5">7.5</a>&nbsp;&nbsp;&nbsp;<a href="#status.4xx">Client Error 4xx</a><ul>
     661                     <li><a href="#rfc.section.7.5.1">7.5.1</a>&nbsp;&nbsp;&nbsp;<a href="#status.400">400 Bad Request</a></li>
     662                     <li><a href="#rfc.section.7.5.2">7.5.2</a>&nbsp;&nbsp;&nbsp;<a href="#status.402">402 Payment Required</a></li>
     663                     <li><a href="#rfc.section.7.5.3">7.5.3</a>&nbsp;&nbsp;&nbsp;<a href="#status.403">403 Forbidden</a></li>
     664                     <li><a href="#rfc.section.7.5.4">7.5.4</a>&nbsp;&nbsp;&nbsp;<a href="#status.404">404 Not Found</a></li>
     665                     <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>
     666                     <li><a href="#rfc.section.7.5.6">7.5.6</a>&nbsp;&nbsp;&nbsp;<a href="#status.406">406 Not Acceptable</a></li>
     667                     <li><a href="#rfc.section.7.5.7">7.5.7</a>&nbsp;&nbsp;&nbsp;<a href="#status.408">408 Request Timeout</a></li>
     668                     <li><a href="#rfc.section.7.5.8">7.5.8</a>&nbsp;&nbsp;&nbsp;<a href="#status.409">409 Conflict</a></li>
     669                     <li><a href="#rfc.section.7.5.9">7.5.9</a>&nbsp;&nbsp;&nbsp;<a href="#status.410">410 Gone</a></li>
     670                     <li><a href="#rfc.section.7.5.10">7.5.10</a>&nbsp;&nbsp;&nbsp;<a href="#status.411">411 Length Required</a></li>
     671                     <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>
     672                     <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>
     673                     <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>
     674                     <li><a href="#rfc.section.7.5.14">7.5.14</a>&nbsp;&nbsp;&nbsp;<a href="#status.417">417 Expectation Failed</a></li>
     675                     <li><a href="#rfc.section.7.5.15">7.5.15</a>&nbsp;&nbsp;&nbsp;<a href="#status.426">426 Upgrade Required</a></li>
    671676                  </ul>
    672677               </li>
    673                <li><a href="#rfc.section.6.6">6.6</a>&nbsp;&nbsp;&nbsp;<a href="#status.5xx">Server Error 5xx</a><ul>
    674                      <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>
    675                      <li><a href="#rfc.section.6.6.2">6.6.2</a>&nbsp;&nbsp;&nbsp;<a href="#status.501">501 Not Implemented</a></li>
    676                      <li><a href="#rfc.section.6.6.3">6.6.3</a>&nbsp;&nbsp;&nbsp;<a href="#status.502">502 Bad Gateway</a></li>
    677                      <li><a href="#rfc.section.6.6.4">6.6.4</a>&nbsp;&nbsp;&nbsp;<a href="#status.503">503 Service Unavailable</a></li>
    678                      <li><a href="#rfc.section.6.6.5">6.6.5</a>&nbsp;&nbsp;&nbsp;<a href="#status.504">504 Gateway Timeout</a></li>
    679                      <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>
     678               <li><a href="#rfc.section.7.6">7.6</a>&nbsp;&nbsp;&nbsp;<a href="#status.5xx">Server Error 5xx</a><ul>
     679                     <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>
     680                     <li><a href="#rfc.section.7.6.2">7.6.2</a>&nbsp;&nbsp;&nbsp;<a href="#status.501">501 Not Implemented</a></li>
     681                     <li><a href="#rfc.section.7.6.3">7.6.3</a>&nbsp;&nbsp;&nbsp;<a href="#status.502">502 Bad Gateway</a></li>
     682                     <li><a href="#rfc.section.7.6.4">7.6.4</a>&nbsp;&nbsp;&nbsp;<a href="#status.503">503 Service Unavailable</a></li>
     683                     <li><a href="#rfc.section.7.6.5">7.6.5</a>&nbsp;&nbsp;&nbsp;<a href="#status.504">504 Gateway Timeout</a></li>
     684                     <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>
    680685                  </ul>
    681686               </li>
    682687            </ul>
    683688         </li>
    684          <li><a href="#rfc.section.7">7.</a>&nbsp;&nbsp;&nbsp;<a href="#response.header.fields">Response Header Fields</a></li>
    685          <li><a href="#rfc.section.8">8.</a>&nbsp;&nbsp;&nbsp;<a href="#protocol.parameters">Protocol Parameters</a><ul>
    686                <li><a href="#rfc.section.8.1">8.1</a>&nbsp;&nbsp;&nbsp;<a href="#http.date">Date/Time Formats</a></li>
    687                <li><a href="#rfc.section.8.2">8.2</a>&nbsp;&nbsp;&nbsp;<a href="#product.tokens">Product Tokens</a></li>
    688                <li><a href="#rfc.section.8.3">8.3</a>&nbsp;&nbsp;&nbsp;<a href="#character.sets">Character Encodings (charset)</a></li>
    689                <li><a href="#rfc.section.8.4">8.4</a>&nbsp;&nbsp;&nbsp;<a href="#content.codings">Content Codings</a></li>
    690                <li><a href="#rfc.section.8.5">8.5</a>&nbsp;&nbsp;&nbsp;<a href="#media.types">Media Types</a><ul>
    691                      <li><a href="#rfc.section.8.5.1">8.5.1</a>&nbsp;&nbsp;&nbsp;<a href="#canonicalization.and.text.defaults">Canonicalization and Text Defaults</a></li>
    692                      <li><a href="#rfc.section.8.5.2">8.5.2</a>&nbsp;&nbsp;&nbsp;<a href="#multipart.types">Multipart Types</a></li>
     689         <li><a href="#rfc.section.8">8.</a>&nbsp;&nbsp;&nbsp;<a href="#response.header.fields">Response Header Fields</a></li>
     690         <li><a href="#rfc.section.9">9.</a>&nbsp;&nbsp;&nbsp;<a href="#protocol.parameters">Protocol Parameters</a><ul>
     691               <li><a href="#rfc.section.9.1">9.1</a>&nbsp;&nbsp;&nbsp;<a href="#http.date">Date/Time Formats</a></li>
     692               <li><a href="#rfc.section.9.2">9.2</a>&nbsp;&nbsp;&nbsp;<a href="#product.tokens">Product Tokens</a></li>
     693               <li><a href="#rfc.section.9.3">9.3</a>&nbsp;&nbsp;&nbsp;<a href="#character.sets">Character Encodings (charset)</a></li>
     694               <li><a href="#rfc.section.9.4">9.4</a>&nbsp;&nbsp;&nbsp;<a href="#content.codings">Content Codings</a></li>
     695               <li><a href="#rfc.section.9.5">9.5</a>&nbsp;&nbsp;&nbsp;<a href="#media.types">Media Types</a><ul>
     696                     <li><a href="#rfc.section.9.5.1">9.5.1</a>&nbsp;&nbsp;&nbsp;<a href="#canonicalization.and.text.defaults">Canonicalization and Text Defaults</a></li>
     697                     <li><a href="#rfc.section.9.5.2">9.5.2</a>&nbsp;&nbsp;&nbsp;<a href="#multipart.types">Multipart Types</a></li>
    693698                  </ul>
    694699               </li>
    695                <li><a href="#rfc.section.8.6">8.6</a>&nbsp;&nbsp;&nbsp;<a href="#language.tags">Language Tags</a></li>
    696             </ul>
    697          </li>
    698          <li><a href="#rfc.section.9">9.</a>&nbsp;&nbsp;&nbsp;<a href="#payload">Payload</a><ul>
    699                <li><a href="#rfc.section.9.1">9.1</a>&nbsp;&nbsp;&nbsp;<a href="#payload.header.fields">Payload Header Fields</a></li>
    700                <li><a href="#rfc.section.9.2">9.2</a>&nbsp;&nbsp;&nbsp;<a href="#payload.body">Payload Body</a></li>
     700               <li><a href="#rfc.section.9.6">9.6</a>&nbsp;&nbsp;&nbsp;<a href="#language.tags">Language Tags</a></li>
    701701            </ul>
    702702         </li>
    … …  
    827827      </p>
    828828      <p id="rfc.section.1.p.2">HTTP provides a uniform interface for interacting with resources regardless of their type, nature, or implementation. HTTP
    829          semantics includes 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 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>).
     829         semantics includes 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 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>).
    830830      </p>
    831831      <p id="rfc.section.1.p.3"><span id="rfc.iref.c.1"></span> In addition, this document defines the payload of messages (a.k.a., content), the associated metadata header fields that define
    … …  
    850850      </p>
    851851      <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
    852          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
     852         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
    853853         effective request URI, unless those semantics are disabled when they are inconsistent with the request method.
    854854      </p>
    … …  
    10801080         fashion.
    10811081      </p>
    1082       <h1 id="rfc.section.4"><a href="#rfc.section.4">4.</a>&nbsp;<a id="methods" href="#methods">Request Methods</a></h1>
    1083       <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>
    1084       <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
    1085          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.
     1082      <h1 id="rfc.section.4"><a href="#rfc.section.4">4.</a>&nbsp;<a id="payload" href="#payload">Payload</a></h1>
     1083      <p id="rfc.section.4.p.1">HTTP messages <em class="bcp14">MAY</em> transfer a payload if not otherwise restricted by the request method or response status code. The payload consists of metadata,
     1084         in the form of header fields, and data, in the form of the sequence of octets in the message body after any transfer-coding
     1085         has been decoded.
     1086      </p>
     1087      <div id="rfc.iref.p.1"></div>
     1088      <p id="rfc.section.4.p.2">A "<dfn>payload</dfn>" in HTTP is always a partial or complete representation of some resource. We use separate terms for payload and representation
     1089         because some messages contain only the associated representation's header fields (e.g., responses to HEAD) or only some part(s)
     1090         of the representation (e.g., the <a href="p5-range.html#status.206" class="smpl">206 (Partial Content)</a> status code).
     1091      </p>
     1092      <h2 id="rfc.section.4.1"><a href="#rfc.section.4.1">4.1</a>&nbsp;<a id="payload.header.fields" href="#payload.header.fields">Payload Header Fields</a></h2>
     1093      <p id="rfc.section.4.1.p.1">HTTP header fields that specifically define the payload, rather than the associated representation, are referred to as "payload
     1094         header fields". The following payload header fields are defined by HTTP/1.1:
     1095      </p>
     1096      <div id="rfc.table.u.3">
     1097         <table class="tt full left" cellpadding="3" cellspacing="0">
     1098            <thead>
     1099               <tr>
     1100                  <th>Header Field Name</th>
     1101                  <th>Defined in...</th>
     1102               </tr>
     1103            </thead>
     1104            <tbody>
     1105               <tr>
     1106                  <td class="left">Content-Length</td>
     1107                  <td class="left"><a href="p1-messaging.html#header.content-length" title="Content-Length">Section 3.3.2</a> of <a href="#Part1" id="rfc.xref.Part1.9"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a></td>
     1108               </tr>
     1109               <tr>
     1110                  <td class="left">Content-Range</td>
     1111                  <td class="left"><a href="p5-range.html#header.content-range" title="Content-Range">Section 5.2</a> of <a href="#Part5" id="rfc.xref.Part5.1"><cite title="HTTP/1.1, part 5: Range Requests">[Part5]</cite></a></td>
     1112               </tr>
     1113            </tbody>
     1114         </table>
     1115      </div>
     1116      <h2 id="rfc.section.4.2"><a href="#rfc.section.4.2">4.2</a>&nbsp;<a id="payload.body" href="#payload.body">Payload Body</a></h2>
     1117      <p id="rfc.section.4.2.p.1">A payload body is only present in a message when a message body is present, as described in <a href="p1-messaging.html#message.body" title="Message Body">Section 3.3</a> of <a href="#Part1" id="rfc.xref.Part1.10"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>. The payload body is obtained from the message body by decoding any <a href="p1-messaging.html#header.transfer-encoding" class="smpl">Transfer-Encoding</a> that might have been applied to ensure safe and proper transfer of the message.
     1118      </p>
     1119      <h1 id="rfc.section.5"><a href="#rfc.section.5">5.</a>&nbsp;<a id="methods" href="#methods">Request Methods</a></h1>
     1120      <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>
     1121      <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
     1122         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.
    10861123      </p>
    10871124      <div id="rfc.figure.u.3"></div><pre class="inline"><span id="rfc.iref.g.3"></span>  <a href="#method.overview" class="smpl">method</a> = <a href="#imported.abnf" class="smpl">token</a>
    1088 </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
     1125</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
    10891126         as applying semantics to a target resource in much the same way as invoking a defined method on an identified object would
    10901127         apply semantics. The method token is case-sensitive because it might be used as a gateway to object-based systems with case-sensitive
    10911128         method names.
    10921129      </p>
    1093       <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
     1130      <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
    10941131         for better visibility and reuse in network-based systems <a href="#REST" id="rfc.xref.REST.1"><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
    10951132         implemented or allowed.
    10961133      </p>
    1097       <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.
     1134      <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.
    10981135         By convention, standardized methods are defined in all-uppercase ASCII letters.
    10991136      </p>
    … …  
    11121149                  <td class="left">GET</td>
    11131150                  <td class="left">Transfer a current representation of the target resource.</td>
    1114                   <td class="left"><a href="#GET" id="rfc.xref.GET.1" title="GET">4.3.1</a></td>
     1151                  <td class="left"><a href="#GET" id="rfc.xref.GET.1" title="GET">5.3.1</a></td>
    11151152               </tr>
    11161153               <tr>
    11171154                  <td class="left">HEAD</td>
    11181155                  <td class="left">Same as GET, but do not include a message body in the response.</td>
    1119                   <td class="left"><a href="#HEAD" id="rfc.xref.HEAD.1" title="HEAD">4.3.2</a></td>
     1156                  <td class="left"><a href="#HEAD" id="rfc.xref.HEAD.1" title="HEAD">5.3.2</a></td>
    11201157               </tr>
    11211158               <tr>
    11221159                  <td class="left">POST</td>
    11231160                  <td class="left">Perform resource-specific processing on the request payload.</td>
    1124                   <td class="left"><a href="#POST" id="rfc.xref.POST.1" title="POST">4.3.3</a></td>
     1161                  <td class="left"><a href="#POST" id="rfc.xref.POST.1" title="POST">5.3.3</a></td>
    11251162               </tr>
    11261163               <tr>
    11271164                  <td class="left">PUT</td>
    11281165                  <td class="left">Replace all current representations of the target resource with the request payload.</td>
    1129                   <td class="left"><a href="#PUT" id="rfc.xref.PUT.1" title="PUT">4.3.4</a></td>
     1166                  <td class="left"><a href="#PUT" id="rfc.xref.PUT.1" title="PUT">5.3.4</a></td>
    11301167               </tr>
    11311168               <tr>
    11321169                  <td class="left">DELETE</td>
    11331170                  <td class="left">Remove all current representations of the target resource.</td>
    1134                   <td class="left"><a href="#DELETE" id="rfc.xref.DELETE.1" title="DELETE">4.3.5</a></td>
     1171                  <td class="left"><a href="#DELETE" id="rfc.xref.DELETE.1" title="DELETE">5.3.5</a></td>
    11351172               </tr>
    11361173               <tr>
    11371174                  <td class="left">CONNECT</td>
    11381175                  <td class="left">Establish a tunnel to the server identified by the target resource.</td>
    1139                   <td class="left"><a href="#CONNECT" id="rfc.xref.CONNECT.1" title="CONNECT">4.3.6</a></td>
     1176                  <td class="left"><a href="#CONNECT" id="rfc.xref.CONNECT.1" title="CONNECT">5.3.6</a></td>
    11401177               </tr>
    11411178               <tr>
    11421179                  <td class="left">OPTIONS</td>
    11431180                  <td class="left">Describe the communication options for the target resource.</td>
    1144                   <td class="left"><a href="#OPTIONS" id="rfc.xref.OPTIONS.1" title="OPTIONS">4.3.7</a></td>
     1181                  <td class="left"><a href="#OPTIONS" id="rfc.xref.OPTIONS.1" title="OPTIONS">5.3.7</a></td>
    11451182               </tr>
    11461183               <tr>
    11471184                  <td class="left">TRACE</td>
    11481185                  <td class="left">Perform a message loop-back test along the path to the target resource.</td>
    1149                   <td class="left"><a href="#TRACE" id="rfc.xref.TRACE.1" title="TRACE">4.3.8</a></td>
     1186                  <td class="left"><a href="#TRACE" id="rfc.xref.TRACE.1" title="TRACE">5.3.8</a></td>
    11501187               </tr>
    11511188            </tbody>
    11521189         </table>
    11531190      </div>
    1154       <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>.
    1155       </p>
    1156       <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 registered within the HTTP
     1191      <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>.
     1192      </p>
     1193      <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 registered within the HTTP
    11571194         Method Registry maintained by IANA, as defined in <a href="#method.registry" title="Method Registry">Section&nbsp;11.1</a>.
    11581195      </p>
    1159       <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;10.5</a>). However, the set of allowed methods can change dynamically. When a request message is received that is unrecognized or
     1196      <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;10.5</a>). However, the set of allowed methods can change dynamically. When a request message is received that is unrecognized or
    11601197         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,
    11611198         the origin server <em class="bcp14">SHOULD</em> respond with the <a href="#status.405" class="smpl">405 (Method Not Allowed)</a> status code.
    11621199      </p>
    1163       <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>
     1200      <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>
    11641201      <div id="rfc.iref.s.2"></div>
    1165       <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>
    1166       <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
     1202      <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>
     1203      <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
    11671204         change on the origin server as a result of applying a safe method to a target resource. Likewise, reasonable use of a safe
    11681205         method is not expected to cause any harm, loss of property, or unusual burden on the origin server.
    11691206      </p>
    1170       <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
     1207      <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
    11711208         entirely read-only, or which causes side-effects while invoking a safe method. What is important, however, is that the client
    11721209         did not request that additional behavior and cannot be held accountable for it. For example, most servers append request information
    … …  
    11751212         the Web will often have the side-effect of charging an advertising account.
    11761213      </p>
    1177       <p id="rfc.section.4.2.1.p.3">The GET, HEAD, OPTIONS, and TRACE request methods are defined to be safe.</p>
    1178       <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
     1214      <p id="rfc.section.5.2.1.p.3">The GET, HEAD, OPTIONS, and TRACE request methods are defined to be safe.</p>
     1215      <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
    11791216         performance optimization (pre-fetching) to work without fear of causing harm. In addition, it allows a user agent to apply
    11801217         appropriate constraints on the automated use of unsafe methods when processing potentially untrusted content.
    11811218      </p>
    1182       <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
     1219      <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
    11831220         of an unsafe action before it is requested.
    11841221      </p>
    1185       <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,
     1222      <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,
    11861223         it is the resource owner's responsibility to ensure that the action is consistent with the request method semantics. For example,
    11871224         it is common for Web-based content editing software to use actions within query parameters, such as "page?do=delete". If the
    … …  
    11911228      </p>
    11921229      <div id="rfc.iref.i.1"></div>
    1193       <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>
    1194       <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
     1230      <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>
     1231      <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
    11951232         methods are idempotent.
    11961233      </p>
    1197       <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
     1234      <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
    11981235         to log each request separately, retain a revision control history, or implement other non-idempotent side-effects for each
    11991236         idempotent request.
    12001237      </p>
    1201       <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
     1238      <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
    12021239         the client is able to read the server's response. For example, if a client sends a PUT request and the underlying connection
    12031240         is closed before any response is received, then it can establish a new connection and retry the idempotent request because
    … …  
    12061243      </p>
    12071244      <div id="rfc.iref.c.2"></div>
    1208       <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>
    1209       <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
     1245      <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>
     1246      <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
    12101247         are defined to be cacheable. In general, safe methods that do not depend on a current or authoritative response are cacheable,
    12111248         though the overwhelming majority of caches only support GET and HEAD. HTTP requirements for cache behavior and cacheable responses
    12121249         are defined in <a href="#Part6" id="rfc.xref.Part6.3"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>.
    12131250      </p>
    1214       <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>
    1215       <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>
     1251      <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>
     1252      <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>
    12161253      <div id="rfc.iref.g.4"></div>
    12171254      <div id="rfc.iref.m.1"></div>
    1218       <p id="rfc.section.4.3.1.p.1">The GET method requests transfer of a current representation of the target resource.</p>
    1219       <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
     1255      <p id="rfc.section.5.3.1.p.1">The GET method requests transfer of a current representation of the target resource.</p>
     1256      <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
    12201257         in the response and not the source text of the process, unless that text happens to be the output of the process.
    12211258      </p>
    1222       <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.3"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>). A conditional GET requests that the representation be transferred only under the circumstances described by the conditional
     1259      <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.3"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>). A conditional GET requests that the representation be transferred only under the circumstances described by the conditional
    12231260         header field(s). The conditional GET request is intended to reduce unnecessary network usage by allowing cached representations
    12241261         to be refreshed without requiring multiple requests or transferring data already held by the client.
    12251262      </p>
    1226       <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.1"><cite title="HTTP/1.1, part 5: 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.2"><cite title="HTTP/1.1, part 5: Range Requests">[Part5]</cite></a>. The partial GET request is intended to reduce unnecessary network usage by allowing partially-retrieved representations
     1263      <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.2"><cite title="HTTP/1.1, part 5: 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.3"><cite title="HTTP/1.1, part 5: Range Requests">[Part5]</cite></a>. The partial GET request is intended to reduce unnecessary network usage by allowing partially-retrieved representations
    12271264         to be completed without transferring data already held by the client.
    12281265      </p>
    1229       <p id="rfc.section.4.3.1.p.5">Bodies on GET requests have no defined semantics. Note that sending a body on a GET request might cause some existing implementations
     1266      <p id="rfc.section.5.3.1.p.5">Bodies on GET requests have no defined semantics. Note that sending a body on a GET request might cause some existing implementations
    12301267         to reject the request.
    12311268      </p>
    1232       <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.4"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>).
    1233       </p>
    1234       <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;12.2</a> for security considerations when used for forms.
    1235       </p>
    1236       <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>
     1269      <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.4"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>).
     1270      </p>
     1271      <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;12.2</a> for security considerations when used for forms.
     1272      </p>
     1273      <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>
    12371274      <div id="rfc.iref.h.1"></div>
    12381275      <div id="rfc.iref.m.2"></div>
    1239       <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
     1276      <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
    12401277         representation implied by the request without transferring the representation body. This method is often used for testing
    12411278         hypertext links for validity, accessibility, and recent modification.
    12421279      </p>
    1243       <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.5"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>.
    1244       </p>
    1245       <p id="rfc.section.4.3.2.p.3">Bodies on HEAD requests have no defined semantics. Note that sending a body on a HEAD request might cause some existing implementations
     1280      <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.5"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>.
     1281      </p>
     1282      <p id="rfc.section.5.3.2.p.3">Bodies on HEAD requests have no defined semantics. Note that sending a body on a HEAD request might cause some existing implementations
    12461283         to reject the request.
    12471284      </p>
    1248       <div id="rfc.iref.p.1"></div>
     1285      <div id="rfc.iref.p.2"></div>
    12491286      <div id="rfc.iref.m.3"></div>
    1250       <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>
    1251       <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
     1287      <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>
     1288      <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
    12521289         by the target resource. POST is designed to allow a uniform method to cover the following functions:
    12531290      </p>
    … …  
    12581295         <li>Extending a database through an append operation.</li>
    12591296      </ul>
    1260       <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
     1297      <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
    12611298         URI.
    12621299      </p>
    1263       <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
     1300      <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
    12641301         the result.
    12651302      </p>
    1266       <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;10.13</a>).
    1267       </p>
    1268       <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.6"><cite title="HTTP/1.1, part 6: 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;10.8</a>) whose value is the effective Request URI <em class="bcp14">MAY</em> be used to satisfy subsequent GET and HEAD requests.
    1269       </p>
    1270       <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.
    1271       </p>
    1272       <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>
    1273       <div id="rfc.iref.p.2"></div>
     1303      <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;10.13</a>).
     1304      </p>
     1305      <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.6"><cite title="HTTP/1.1, part 6: 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;10.8</a>) whose value is the effective Request URI <em class="bcp14">MAY</em> be used to satisfy subsequent GET and HEAD requests.
     1306      </p>
     1307      <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.
     1308      </p>
     1309      <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>
     1310      <div id="rfc.iref.p.3"></div>
    12741311      <div id="rfc.iref.m.4"></div>
    1275       <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
     1312      <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
    12761313         enclosed in the request message payload. A successful PUT of a given representation would suggest that a subsequent GET on
    12771314         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
    … …  
    12801317         by the origin server.
    12811318      </p>
    1282       <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
     1319      <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
    12831320         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.
    12841321      </p>
    1285       <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).
    1286       </p>
    1287       <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
     1322      <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).
     1323      </p>
     1324      <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
    12881325         or will not be changed by the PUT. This is particularly important when the origin server uses internal configuration information
    12891326         related to the URI in order to set the values for representation metadata on GET responses. When a PUT representation is inconsistent
    … …  
    12911328         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.
    12921329      </p>
    1293       <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:
     1330      <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:
    12941331      </p>
    12951332      <ol class="la">
    … …  
    13021339         </li>
    13031340      </ol>
    1304       <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
     1341      <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
    13051342         of the user agent request and the semantics of the origin server response. It does not define what a resource might be, in
    13061343         any sense of that word, beyond the interface provided via HTTP. It does not define how resource state is "stored", nor how
    … …  
    13091346         the server.
    13101347      </p>
    1311       <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.
     1348      <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.
    13121349         The target resource in a POST request is intended to handle the enclosed representation as a data-accepting process, such
    13131350         as for a gateway to some other protocol or a document that accepts annotations. In contrast, the target resource in a PUT
    … …  
    13151352         and visible to intermediaries, even though the exact effect is only known by the origin server.
    13161353      </p>
    1317       <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
     1354      <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
    13181355         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
    13191356         the target resource and instead wishes to have it applied to a different resource, such as when the resource has been moved
    13201357         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.
    13211358      </p>
    1322       <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)
     1359      <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)
    13231360         which is separate from the URIs identifying each particular version (different resources that at one point shared the same
    13241361         state as the current version resource). A successful PUT request on "the current version" URI might therefore create a new
    … …  
    13261363         the related resources.
    13271364      </p>
    1328       <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.3"><cite title="HTTP/1.1, part 5: 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
     1365      <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.4"><cite title="HTTP/1.1, part 5: 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
    13291366         representation). Partial content updates are possible by targeting a separately identified resource with state that overlaps
    13301367         a portion of the larger resource, or by using a different method that has been specifically defined for partial updates (for
    13311368         example, the PATCH method defined in <a href="#RFC5789" id="rfc.xref.RFC5789.1"><cite title="PATCH Method for HTTP">[RFC5789]</cite></a>).
    13321369      </p>
    1333       <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
     1370      <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
    13341371         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="HTTP/1.1, part 6: Caching">[Part6]</cite></a>).
    13351372      </p>
    1336       <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>
     1373      <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>
    13371374      <div id="rfc.iref.d.1"></div>
    13381375      <div id="rfc.iref.m.5"></div>
    1339       <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
     1376      <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
    13401377         has been carried out, even if the status code returned from the origin server indicates that the action has been completed
    13411378         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
    13421379         location.
    13431380      </p>
    1344       <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.
    1345       </p>
    1346       <p id="rfc.section.4.3.5.p.3">Bodies on DELETE requests have no defined semantics. Note that sending a body on a DELETE request might cause some existing
     1381      <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.
     1382      </p>
     1383      <p id="rfc.section.5.3.5.p.3">Bodies on DELETE requests have no defined semantics. Note that sending a body on a DELETE request might cause some existing
    13471384         implementations to reject the request.
    13481385      </p>
    1349       <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
     1386      <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
    13501387         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.8"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>).
    13511388      </p>
    13521389      <div id="rfc.iref.c.3"></div>
    13531390      <div id="rfc.iref.m.6"></div>
    1354       <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>
    1355       <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
     1391      <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>
     1392      <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
    13561393         its behavior to blind forwarding of packets until the connection is closed.
    13571394      </p>
    1358       <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.9"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[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.
     1395      <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.11"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[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.
    13591396         For example,
    13601397      </p>
    … …  
    13621399Host: server.example.com:80
    13631400
    1364 </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
     1401</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
    13651402         switched to tunneling the current connection to that server connection. The tunneled data from the server begins immediately
    13661403         after the blank line that concludes the successful response's header block.
    13671404      </p>
    1368       <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.
    1369       </p>
    1370       <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
     1405      <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.
     1406      </p>
     1407      <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
    13711408         governed by HTTP.
    13721409      </p>
    1373       <p id="rfc.section.4.3.6.p.7">Proxy authentication might be used to establish the authority to create a tunnel:</p>
     1410      <p id="rfc.section.5.3.6.p.7">Proxy authentication might be used to establish the authority to create a tunnel:</p>
    13741411      <div id="rfc.figure.u.5"></div><pre class="text2">CONNECT server.example.com:80 HTTP/1.1
    13751412Host: server.example.com:80
    13761413Proxy-Authorization: basic aGVsbG86d29ybGQ=
    13771414
    1378 </pre><p id="rfc.section.4.3.6.p.9">A message body on a CONNECT request has no defined semantics. Sending a body on a CONNECT request might cause existing implementations
     1415</pre><p id="rfc.section.5.3.6.p.9">A message body on a CONNECT request has no defined semantics. Sending a body on a CONNECT request might cause existing implementations
    13791416         to reject the request.
    13801417      </p>
    1381       <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
     1418      <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
    13821419         if the eventual response is negative, and the connection can be reset with no response if more than one TCP segment is outstanding.
    13831420      </p>
    1384       <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,
     1421      <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,
    13851422         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.
    13861423      </p>
    1387       <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
     1424      <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
    13881425         the other one, and after that also the other connection will be terminated by the proxy. If there is outstanding data to that
    13891426         peer undelivered, that data will be discarded.
    13901427      </p>
    1391       <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.
    1392       </p>
    1393       <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>
     1428      <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.
     1429      </p>
     1430      <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>
    13941431      <div id="rfc.iref.o.1"></div>
    13951432      <div id="rfc.iref.m.7"></div>
    1396       <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
     1433      <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
    13971434         by the effective request URI. This method allows a client to determine the options and/or requirements associated with a resource,
    13981435         or the capabilities of a server, without implying a resource action or initiating a resource retrieval.
    13991436      </p>
    1400       <p id="rfc.section.4.3.7.p.2">Responses to the OPTIONS method are not cacheable.</p>
    1401       <p id="rfc.section.4.3.7.p.3">If the OPTIONS request includes a message body (as indicated by the presence of <a href="p1-messaging.html#header.content-length" class="smpl">Content-Length</a> or <a href="p1-messaging.html#header.transfer-encoding" class="smpl">Transfer-Encoding</a>), 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
     1437      <p id="rfc.section.5.3.7.p.2">Responses to the OPTIONS method are not cacheable.</p>
     1438      <p id="rfc.section.5.3.7.p.3">If the OPTIONS request includes a message body (as indicated by the presence of <a href="p1-messaging.html#header.content-length" class="smpl">Content-Length</a> or <a href="p1-messaging.html#header.transfer-encoding" class="smpl">Transfer-Encoding</a>), 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
    14021439         body to make more detailed queries on the server.
    14031440      </p>
    1404       <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.10"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>) is an asterisk ("*"), the OPTIONS request is intended to apply to the server in general rather than to a specific resource.
     1441      <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.12"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>) is an asterisk ("*"), the OPTIONS request is intended to apply to the server in general rather than to a specific resource.
    14051442         Since a server's communication options typically depend on the resource, the "*" request is only useful as a "ping" or "no-op"
    14061443         type of method; it does nothing beyond allowing the client to test the capabilities of the server. For example, this can be
    14071444         used to test a proxy for HTTP/1.1 conformance (or lack thereof).
    14081445      </p>
    1409       <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
     1446      <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
    14101447         with that resource.
    14111448      </p>
    1412       <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 body, if any, <em class="bcp14">SHOULD</em> also include information about the communication options. The format for such a body is not defined by this specification,
     1449      <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 body, if any, <em class="bcp14">SHOULD</em> also include information about the communication options. The format for such a body is not defined by this specification,
    14131450         but might be defined by future extensions to HTTP. Content negotiation <em class="bcp14">MAY</em> be used to select the appropriate response format. If no response body is included, the response <em class="bcp14">MUST</em> include a <a href="p1-messaging.html#header.content-length" class="smpl">Content-Length</a> field with a field-value of "0".
    14141451      </p>
    1415       <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;10.14</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.
    1416       </p>
    1417       <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>
     1452      <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;10.14</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.
     1453      </p>
     1454      <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>
    14181455      <div id="rfc.iref.t.1"></div>
    14191456      <div id="rfc.iref.m.8"></div>
    1420       <p id="rfc.section.4.3.8.p.1">The TRACE method requests a remote, application-layer loop-back of the request message. The final recipient of the request <em class="bcp14">SHOULD</em> reflect the message received back to the client as the message body of a <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;10.14</a>). A TRACE request <em class="bcp14">MUST NOT</em> include a message body.
    1421       </p>
    1422       <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
    1423          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</a> of <a href="#Part1" id="rfc.xref.Part1.11"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[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
     1457      <p id="rfc.section.5.3.8.p.1">The TRACE method requests a remote, application-layer loop-back of the request message. The final recipient of the request <em class="bcp14">SHOULD</em> reflect the message received back to the client as the message body of a <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;10.14</a>). A TRACE request <em class="bcp14">MUST NOT</em> include a message body.
     1458      </p>
     1459      <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
     1460         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</a> of <a href="#Part1" id="rfc.xref.Part1.13"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[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
    14241461         messages in an infinite loop.
    14251462      </p>
    1426       <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.12"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[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.
    1427       </p>
    1428       <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>
    1429       <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
     1463      <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.14"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[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.
     1464      </p>
     1465      <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>
     1466      <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
    14301467         on the target resource state, suggest preferred formats for the response, supply authentication credentials, or modify the
    14311468         expected request processing. These fields act as request modifiers, similar to the parameters on a programming language method
    14321469         invocation.
    14331470      </p>
    1434       <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>
    1435       <p id="rfc.section.5.1.p.1">Controls are request header fields that direct specific handling of the request.</p>
    1436       <div id="rfc.table.u.3">
     1471      <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>
     1472      <p id="rfc.section.6.1.p.1">Controls are request header fields that direct specific handling of the request.</p>
     1473      <div id="rfc.table.u.4">
    14371474         <table class="tt full left" cellpadding="3" cellspacing="0">
    14381475            <thead>
    … …  
    14451482               <tr>
    14461483                  <td class="left">Host</td>
    1447                   <td class="left"><a href="p1-messaging.html#header.host" title="Host">Section 5.4</a> of <a href="#Part1" id="rfc.xref.Part1.13"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a></td>
     1484                  <td class="left"><a href="p1-messaging.html#header.host" title="Host">Section 5.4</a> of <a href="#Part1" id="rfc.xref.Part1.15"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a></td>
    14481485               </tr>
    14491486               <tr>
    … …  
    14571494               <tr>
    14581495                  <td class="left">Range</td>
    1459                   <td class="left"><a href="p5-range.html#header.range" title="Range">Section 5.4</a> of <a href="#Part5" id="rfc.xref.Part5.4"><cite title="HTTP/1.1, part 5: Range Requests">[Part5]</cite></a></td>
     1496                  <td class="left"><a href="p5-range.html#header.range" title="Range">Section 5.4</a> of <a href="#Part5" id="rfc.xref.Part5.5"><cite title="HTTP/1.1, part 5: Range Requests">[Part5]</cite></a></td>
    14601497               </tr>
    14611498            </tbody>
    14621499         </table>
    14631500      </div>
    1464       <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>
    1465       <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
     1501      <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>
     1502      <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
    14661503         target resource. Each precondition is based on metadata that is expected to change if the selected representation of the target
    14671504         resource is changed. The HTTP/1.1 conditional request mechanisms are defined in <a href="#Part4" id="rfc.xref.Part4.4"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>.
    14681505      </p>
    1469       <div id="rfc.table.u.4">
     1506      <div id="rfc.table.u.5">
    14701507         <table class="tt full left" cellpadding="3" cellspacing="0">
    14711508            <thead>
    … …  
    14941531               <tr>
    14951532                  <td class="left">If-Range</td>
    1496                   <td class="left"><a href="p5-range.html#header.if-range" title="If-Range">Section 5.3</a> of <a href="#Part5" id="rfc.xref.Part5.5"><cite title="HTTP/1.1, part 5: Range Requests">[Part5]</cite></a></td>
     1533                  <td class="left"><a href="p5-range.html#header.if-range" title="If-Range">Section 5.3</a> of <a href="#Part5" id="rfc.xref.Part5.6"><cite title="HTTP/1.1, part 5: Range Requests">[Part5]</cite></a></td>
    14971534               </tr>
    14981535            </tbody>
    14991536         </table>
    15001537      </div>
    1501       <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>
    1502       <div id="rfc.table.u.5">
     1538      <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>
     1539      <div id="rfc.table.u.6">
    15031540         <table class="tt full left" cellpadding="3" cellspacing="0">
    15041541            <thead>
    … …  
    15281565         </table>
    15291566      </div>
    1530       <h2 id="rfc.section.5.4"><a href="#rfc.section.5.4">5.4</a>&nbsp;<a id="request.auth" href="#request.auth">Authentication</a></h2>
    1531       <div id="rfc.table.u.6">
     1567      <h2 id="rfc.section.6.4"><a href="#rfc.section.6.4">6.4</a>&nbsp;<a id="request.auth" href="#request.auth">Authentication</a></h2>
     1568      <div id="rfc.table.u.7">
    15321569         <table class="tt full left" cellpadding="3" cellspacing="0">
    15331570            <thead>
    … …  
    15491586         </table>
    15501587      </div>
    1551       <h2 id="rfc.section.5.5"><a href="#rfc.section.5.5">5.5</a>&nbsp;<a id="request.context" href="#request.context">Context</a></h2>
    1552       <div id="rfc.table.u.7">
     1588      <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>
     1589      <div id="rfc.table.u.8">
    15531590         <table class="tt full left" cellpadding="3" cellspacing="0">
    15541591            <thead>
    … …  
    15691606               <tr>
    15701607                  <td class="left">TE</td>
    1571                   <td class="left"><a href="p1-messaging.html#header.te" title="TE">Section 4.3</a> of <a href="#Part1" id="rfc.xref.Part1.14"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a></td>
     1608                  <td class="left"><a href="p1-messaging.html#header.te" title="TE">Section 4.3</a> of <a href="#Part1" id="rfc.xref.Part1.16"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a></td>
    15721609               </tr>
    15731610               <tr>
    … …  
    15781615         </table>
    15791616      </div>
    1580       <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>
    1581       <p id="rfc.section.6.p.1">The status-code element is a 3-digit integer result code of the attempt to understand and satisfy the request.</p>
    1582       <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,
     1617      <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>
     1618      <p id="rfc.section.7.p.1">The status-code element is a 3-digit integer result code of the attempt to understand and satisfy the request.</p>
     1619      <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,
    15831620         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
    15841621         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
    … …  
    15861623         information which will explain the unusual status.
    15871624      </p>
    1588       <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.
     1625      <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.
    15891626         There are 5 values for the first digit:
    15901627      </p>
    … …  
    16011638         </li>
    16021639      </ul>
    1603       <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.2" title="Content-Type">Section&nbsp;10.9</a>).
    1604       </p>
    1605       <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>
    1606       <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.9"><cite title="HTTP/1.1, part 4: 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.6"><cite title="HTTP/1.1, part 5: 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="HTTP/1.1, part 7: Authentication">[Part7]</cite></a>. The reason phrases listed here are only recommendations — they can be replaced by local equivalents without affecting the
     1640      <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.2" title="Content-Type">Section&nbsp;10.9</a>).
     1641      </p>
     1642      <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>
     1643      <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.9"><cite title="HTTP/1.1, part 4: 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.7"><cite title="HTTP/1.1, part 5: 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="HTTP/1.1, part 7: Authentication">[Part7]</cite></a>. The reason phrases listed here are only recommendations — they can be replaced by local equivalents without affecting the
    16071644         protocol.
    16081645      </p>
    1609       <div id="rfc.table.u.8">
     1646      <div id="rfc.table.u.9">
    16101647         <table class="tt full left" cellpadding="3" cellspacing="0">
    16111648            <thead>
    … …  
    16201657                  <td class="left">100</td>
    16211658                  <td class="left">Continue</td>
    1622                   <td class="left"><a href="#status.100" id="rfc.xref.status.100.1" title="100 Continue">Section&nbsp;6.2.1</a></td>
     1659                  <td class="left"><a href="#status.100" id="rfc.xref.status.100.1" title="100 Continue">Section&nbsp;7.2.1</a></td>
    16231660               </tr>
    16241661               <tr>
    16251662                  <td class="left">101</td>
    16261663                  <td class="left">Switching Protocols</td>
    1627                   <td class="left"><a href="#status.101" id="rfc.xref.status.101.1" title="101 Switching Protocols">Section&nbsp;6.2.2</a></td>
     1664                  <td class="left"><a href="#status.101" id="rfc.xref.status.101.1" title="101 Switching Protocols">Section&nbsp;7.2.2</a></td>
    16281665               </tr>
    16291666               <tr>
    16301667                  <td class="left">200</td>
    16311668                  <td class="left">OK</td>
    1632                   <td class="left"><a href="#status.200" id="rfc.xref.status.200.1" title="200 OK">Section&nbsp;6.3.1</a></td>
     1669                  <td class="left"><a href="#status.200" id="rfc.xref.status.200.1" title="200 OK">Section&nbsp;7.3.1</a></td>
    16331670               </tr>
    16341671               <tr>
    16351672                  <td class="left">201</td>
    16361673                  <td class="left">Created</td>
    1637                   <td class="left"><a href="#status.201" id="rfc.xref.status.201.1" title="201 Created">Section&nbsp;6.3.2</a></td>
     1674                  <td class="left"><a href="#status.201" id="rfc.xref.status.201.1" title="201 Created">Section&nbsp;7.3.2</a></td>
    16381675               </tr>
    16391676               <tr>
    16401677                  <td class="left">202</td>
    16411678                  <td class="left">Accepted</td>
    1642                   <td class="left"><a href="#status.202" id="rfc.xref.status.202.1" title="202 Accepted">Section&nbsp;6.3.3</a></td>
     1679                  <td class="left"><a href="#status.202" id="rfc.xref.status.202.1" title="202 Accepted">Section&nbsp;7.3.3</a></td>
    16431680               </tr>
    16441681               <tr>
    16451682                  <td class="left">203</td>
    16461683                  <td class="left">Non-Authoritative Information</td>
    1647                   <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>
     1684                  <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>
    16481685               </tr>
    16491686               <tr>
    16501687                  <td class="left">204</td>
    16511688                  <td class="left">No Content</td>
    1652                   <td class="left"><a href="#status.204" id="rfc.xref.status.204.1" title="204 No Content">Section&nbsp;6.3.5</a></td>
     1689                  <td class="left"><a href="#status.204" id="rfc.xref.status.204.1" title="204 No Content">Section&nbsp;7.3.5</a></td>
    16531690               </tr>
    16541691               <tr>
    16551692                  <td class="left">205</td>
    16561693                  <td class="left">Reset Content</td>
    1657                   <td class="left"><a href="#status.205" id="rfc.xref.status.205.1" title="205 Reset Content">Section&nbsp;6.3.6</a></td>
     1694                  <td class="left"><a href="#status.205" id="rfc.xref.status.205.1" title="205 Reset Content">Section&nbsp;7.3.6</a></td>
    16581695               </tr>
    16591696               <tr>
    16601697                  <td class="left">206</td>
    16611698                  <td class="left">Partial Content</td>
    1662                   <td id="status.206" class="left"><a href="p5-range.html#status.206" title="206 Partial Content">Section 3.1</a> of <a href="#Part5" id="rfc.xref.Part5.7"><cite title="HTTP/1.1, part 5: Range Requests">[Part5]</cite></a></td>
     1699                  <td id="status.206" class="left"><a href="p5-range.html#status.206" title="206 Partial Content">Section 3.1</a> of <a href="#Part5" id="rfc.xref.Part5.8"><cite title="HTTP/1.1, part 5: Range Requests">[Part5]</cite></a></td>
    16631700               </tr>
    16641701               <tr>
    16651702                  <td class="left">300</td>
    16661703                  <td class="left">Multiple Choices</td>
    1667                   <td class="left"><a href="#status.300" id="rfc.xref.status.300.1" title="300 Multiple Choices">Section&nbsp;6.4.1</a></td>
     1704                  <td class="left"><a href="#status.300" id="rfc.xref.status.300.1" title="300 Multiple Choices">Section&nbsp;7.4.1</a></td>
    16681705               </tr>
    16691706               <tr>
    16701707                  <td class="left">301</td>
    16711708                  <td class="left">Moved Permanently</td>
    1672                   <td class="left"><a href="#status.301" id="rfc.xref.status.301.1" title="301 Moved Permanently">Section&nbsp;6.4.2</a></td>
     1709                  <td class="left"><a href="#status.301" id="rfc.xref.status.301.1" title="301 Moved Permanently">Section&nbsp;7.4.2</a></td>
    16731710               </tr>
    16741711               <tr>
    16751712                  <td class="left">302</td>
    16761713                  <td class="left">Found</td>
    1677                   <td class="left"><a href="#status.302" id="rfc.xref.status.302.1" title="302 Found">Section&nbsp;6.4.3</a></td>
     1714                  <td class="left"><a href="#status.302" id="rfc.xref.status.302.1" title="302 Found">Section&nbsp;7.4.3</a></td>
    16781715               </tr>
    16791716               <tr>
    16801717                  <td class="left">303</td>
    16811718                  <td class="left">See Other</td>
    1682                   <td class="left"><a href="#status.303" id="rfc.xref.status.303.1" title="303 See Other">Section&nbsp;6.4.4</a></td>
     1719                  <td class="left"><a href="#status.303" id="rfc.xref.status.303.1" title="303 See Other">Section&nbsp;7.4.4</a></td>
    16831720               </tr>
    16841721               <tr>
    … …  
    16901727                  <td class="left">305</td>
    16911728                  <td class="left">Use Proxy</td>
    1692                   <td class="left"><a href="#status.305" id="rfc.xref.status.305.1" title="305 Use Proxy">Section&nbsp;6.4.5</a></td>
     1729                  <td class="left"><a href="#status.305" id="rfc.xref.status.305.1" title="305 Use Proxy">Section&nbsp;7.4.5</a></td>
    16931730               </tr>
    16941731               <tr>
    16951732                  <td class="left">307</td>
    16961733                  <td class="left">Temporary Redirect</td>
    1697                   <td class="left"><a href="#status.307" id="rfc.xref.status.307.1" title="307 Temporary Redirect">Section&nbsp;6.4.7</a></td>
     1734                  <td class="left"><a href="#status.307" id="rfc.xref.status.307.1" title="307 Temporary Redirect">Section&nbsp;7.4.7</a></td>
    16981735               </tr>
    16991736               <tr>
    17001737                  <td class="left">400</td>
    17011738                  <td class="left">Bad Request</td>
    1702                   <td class="left"><a href="#status.400" id="rfc.xref.status.400.1" title="400 Bad Request">Section&nbsp;6.5.1</a></td>
     1739                  <td class="left"><a href="#status.400" id="rfc.xref.status.400.1" title="400 Bad Request">Section&nbsp;7.5.1</a></td>
    17031740               </tr>
    17041741               <tr>
    … …  
    17101747                  <td class="left">402</td>
    17111748                  <td class="left">Payment Required</td>
    1712                   <td class="left"><a href="#status.402" id="rfc.xref.status.402.1" title="402 Payment Required">Section&nbsp;6.5.2</a></td>
     1749                  <td class="left"><a href="#status.402" id="rfc.xref.status.402.1" title="402 Payment Required">Section&nbsp;7.5.2</a></td>
    17131750               </tr>
    17141751               <tr>
    17151752                  <td class="left">403</td>
    17161753                  <td class="left">Forbidden</td>
    1717                   <td class="left"><a href="#status.403" id="rfc.xref.status.403.1" title="403 Forbidden">Section&nbsp;6.5.3</a></td>
     1754                  <td class="left"><a href="#status.403" id="rfc.xref.status.403.1" title="403 Forbidden">Section&nbsp;7.5.3</a></td>
    17181755               </tr>
    17191756               <tr>
    17201757                  <td class="left">404</td>
    17211758                  <td class="left">Not Found</td>
    1722                   <td class="left"><a href="#status.404" id="rfc.xref.status.404.1" title="404 Not Found">Section&nbsp;6.5.4</a></td>
     1759                  <td class="left"><a href="#status.404" id="rfc.xref.status.404.1" title="404 Not Found">Section&nbsp;7.5.4</a></td>
    17231760               </tr>
    17241761               <tr>
    17251762                  <td class="left">405</td>
    17261763                  <td class="left">Method Not Allowed</td>
    1727                   <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>
     1764                  <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>
    17281765               </tr>
    17291766               <tr>
    17301767                  <td class="left">406</td>
    17311768                  <td class="left">Not Acceptable</td>
    1732                   <td class="left"><a href="#status.406" id="rfc.xref.status.406.1" title="406 Not Acceptable">Section&nbsp;6.5.6</a></td>
     1769                  <td class="left"><a href="#status.406" id="rfc.xref.status.406.1" title="406 Not Acceptable">Section&nbsp;7.5.6</a></td>
    17331770               </tr>
    17341771               <tr>
    … …  
    17401777                  <td class="left">408</td>
    17411778                  <td class="left">Request Time-out</td>
    1742                   <td class="left"><a href="#status.408" id="rfc.xref.status.408.1" title="408 Request Timeout">Section&nbsp;6.5.7</a></td>
     1779                  <td class="left"><a href="#status.408" id="rfc.xref.status.408.1" title="408 Request Timeout">Section&nbsp;7.5.7</a></td>
    17431780               </tr>
    17441781               <tr>
    17451782                  <td class="left">409</td>
    17461783                  <td class="left">Conflict</td>
    1747                   <td class="left"><a href="#status.409" id="rfc.xref.status.409.1" title="409 Conflict">Section&nbsp;6.5.8</a></td>
     1784                  <td class="left"><a href="#status.409" id="rfc.xref.status.409.1" title="409 Conflict">Section&nbsp;7.5.8</a></td>
    17481785               </tr>
    17491786               <tr>
    17501787                  <td class="left">410</td>
    17511788                  <td class="left">Gone</td>
    1752                   <td class="left"><a href="#status.410" id="rfc.xref.status.410.1" title="410 Gone">Section&nbsp;6.5.9</a></td>
     1789                  <td class="left"><a href="#status.410" id="rfc.xref.status.410.1" title="410 Gone">Section&nbsp;7.5.9</a></td>
    17531790               </tr>
    17541791               <tr>
    17551792                  <td class="left">411</td>
    17561793                  <td class="left">Length Required</td>
    1757                   <td class="left"><a href="#status.411" id="rfc.xref.status.411.1" title="411 Length Required">Section&nbsp;6.5.10</a></td>
     1794                  <td class="left"><a href="#status.411" id="rfc.xref.status.411.1" title="411 Length Required">Section&nbsp;7.5.10</a></td>
    17581795               </tr>
    17591796               <tr>
    … …  
    17651802                  <td class="left">413</td>
    17661803                  <td class="left">Request Representation Too Large</td>
    1767                   <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>
     1804                  <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>
    17681805               </tr>
    17691806               <tr>
    17701807                  <td class="left">414</td>
    17711808                  <td class="left">URI Too Long</td>
    1772                   <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>
     1809                  <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>
    17731810               </tr>
    17741811               <tr>
    17751812                  <td class="left">415</td>
    17761813                  <td class="left">Unsupported Media Type</td>
    1777                   <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>
     1814                  <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>
    17781815               </tr>
    17791816               <tr>
    17801817                  <td class="left">416</td>
    17811818                  <td class="left">Requested range not satisfiable</td>
    1782                   <td id="status.416" class="left"><a href="p5-range.html#status.416" title="416 Requested Range Not Satisfiable">Section 3.2</a> of <a href="#Part5" id="rfc.xref.Part5.8"><cite title="HTTP/1.1, part 5: Range Requests">[Part5]</cite></a></td>
     1819                  <td id="status.416" class="left"><a href="p5-range.html#status.416" title="416 Requested Range Not Satisfiable">Section 3.2</a> of <a href="#Part5" id="rfc.xref.Part5.9"><cite title="HTTP/1.1, part 5: Range Requests">[Part5]</cite></a></td>
    17831820               </tr>
    17841821               <tr>
    17851822                  <td class="left">417</td>
    17861823                  <td class="left">Expectation Failed</td>
    1787                   <td class="left"><a href="#status.417" id="rfc.xref.status.417.1" title="417 Expectation Failed">Section&nbsp;6.5.14</a></td>
     1824                  <td class="left"><a href="#status.417" id="rfc.xref.status.417.1" title="417 Expectation Failed">Section&nbsp;7.5.14</a></td>
    17881825               </tr>
    17891826               <tr>
    17901827                  <td class="left">426</td>
    17911828                  <td class="left">Upgrade Required</td>
    1792                   <td class="left"><a href="#status.426" id="rfc.xref.status.426.1" title="426 Upgrade Required">Section&nbsp;6.5.15</a></td>
     1829                  <td class="left"><a href="#status.426" id="rfc.xref.status.426.1" title="426 Upgrade Required">Section&nbsp;7.5.15</a></td>
    17931830               </tr>
    17941831               <tr>
    17951832                  <td class="left">500</td>
    17961833                  <td class="left">Internal Server Error</td>
    1797                   <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>
     1834                  <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>
    17981835               </tr>
    17991836               <tr>
    18001837                  <td class="left">501</td>
    18011838                  <td class="left">Not Implemented</td>
    1802                   <td class="left"><a href="#status.501" id="rfc.xref.status.501.1" title="501 Not Implemented">Section&nbsp;6.6.2</a></td>
     1839                  <td class="left"><a href="#status.501" id="rfc.xref.status.501.1" title="501 Not Implemented">Section&nbsp;7.6.2</a></td>
    18031840               </tr>
    18041841               <tr>
    18051842                  <td class="left">502</td>
    18061843                  <td class="left">Bad Gateway</td>
    1807                   <td class="left"><a href="#status.502" id="rfc.xref.status.502.1" title="502 Bad Gateway">Section&nbsp;6.6.3</a></td>
     1844                  <td class="left"><a href="#status.502" id="rfc.xref.status.502.1" title="502 Bad Gateway">Section&nbsp;7.6.3</a></td>
    18081845               </tr>
    18091846               <tr>
    18101847                  <td class="left">503</td>
    18111848                  <td class="left">Service Unavailable</td>
    1812                   <td class="left"><a href="#status.503" id="rfc.xref.status.503.1" title="503 Service Unavailable">Section&nbsp;6.6.4</a></td>
     1849                  <td class="left"><a href="#status.503" id="rfc.xref.status.503.1" title="503 Service Unavailable">Section&nbsp;7.6.4</a></td>
    18131850               </tr>
    18141851               <tr>
    18151852                  <td class="left">504</td>
    18161853                  <td class="left">Gateway Time-out</td>
    1817                   <td class="left"><a href="#status.504" id="rfc.xref.status.504.1" title="504 Gateway Timeout">Section&nbsp;6.6.5</a></td>
     1854                  <td class="left"><a href="#status.504" id="rfc.xref.status.504.1" title="504 Gateway Timeout">Section&nbsp;7.6.5</a></td>
    18181855               </tr>
    18191856               <tr>
    18201857                  <td class="left">505</td>
    18211858                  <td class="left">HTTP Version not supported</td>
    1822                   <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>
     1859                  <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>
    18231860               </tr>
    18241861            </tbody>
    18251862         </table>
    18261863      </div>
    1827       <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>
    1828       <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>
    1829       <div id="rfc.iref.25"></div>
     1864      <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>
     1865      <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>
     1866      <div id="rfc.iref.26"></div>
    18301867      <div id="rfc.iref.s.3"></div>
    1831       <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,
     1868      <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,
    18321869         and is terminated by an empty line. There are no required header fields for this class of status code. Since HTTP/1.0 did
    18331870         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.
    18341871      </p>
    1835       <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
     1872      <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
    18361873            (Continue)</a> status message. Unexpected 1xx status responses <em class="bcp14">MAY</em> be ignored by a user agent.
    18371874      </p>
    1838       <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
     1875      <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
    18391876         requested the generation of the 1xx response. (For example, if a proxy adds an "Expect: 100-continue" field when it forwards
    18401877         a request, then it need not forward the corresponding <a href="#status.100" class="smpl">100 (Continue)</a> response(s).)
    18411878      </p>
    1842       <div id="rfc.iref.26"></div>
     1879      <div id="rfc.iref.27"></div>
    18431880      <div id="rfc.iref.s.4"></div>
    1844       <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>
    1845       <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
     1881      <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>
     1882      <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
    18461883         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
    1847          server <em class="bcp14">MUST</em> send a final response after the request has been completed. See <a href="p1-messaging.html#use.of.the.100.status" title="Use of the 100 (Continue) Status">Section 6.3</a> of <a href="#Part1" id="rfc.xref.Part1.15"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a> for detailed discussion of the use and handling of this status code.
    1848       </p>
    1849       <div id="rfc.iref.27"></div>
     1884         server <em class="bcp14">MUST</em> send a final response after the request has been completed. See <a href="p1-messaging.html#use.of.the.100.status" title="Use of the 100 (Continue) Status">Section 6.3</a> of <a href="#Part1" id="rfc.xref.Part1.17"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a> for detailed discussion of the use and handling of this status code.
     1885      </p>
     1886      <div id="rfc.iref.28"></div>
    18501887      <div id="rfc.iref.s.5"></div>
    1851       <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>
    1852       <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.4</a> of <a href="#Part1" id="rfc.xref.Part1.16"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>), for a change in the application protocol being used on this connection. The server will switch protocols to those defined
     1888      <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>
     1889      <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.4</a> of <a href="#Part1" id="rfc.xref.Part1.18"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>), for a change in the application protocol being used on this connection. The server will switch protocols to those defined
    18531890         by the response's Upgrade header field immediately after the empty line which terminates the 101 response.
    18541891      </p>
    1855       <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
     1892      <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
    18561893         older versions, and switching to a real-time, synchronous protocol might be advantageous when delivering resources that use
    18571894         such features.
    18581895      </p>
    1859       <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>
    1860       <div id="rfc.iref.28"></div>
     1896      <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>
     1897      <div id="rfc.iref.29"></div>
    18611898      <div id="rfc.iref.s.6"></div>
    1862       <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>
    1863       <div id="rfc.iref.29"></div>
     1899      <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>
     1900      <div id="rfc.iref.30"></div>
    18641901      <div id="rfc.iref.s.7"></div>
    1865       <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>
    1866       <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>
     1902      <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>
     1903      <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>
    18671904      <dl>
    18681905         <dt>GET</dt>
    … …  
    18751912         <dd>a representation containing the request message as received by the end server.</dd>
    18761913      </dl>
    1877       <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.9"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>) to determine freshness for 200 responses.
    1878       </p>
    1879       <div id="rfc.iref.30"></div>
     1914      <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.9"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>) to determine freshness for 200 responses.
     1915      </p>
     1916      <div id="rfc.iref.31"></div>
    18801917      <div id="rfc.iref.s.8"></div>
    1881       <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>
    1882       <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>
    1883       <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
     1918      <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>
     1919      <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>
     1920      <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
    18841921         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
    18851922         (e.g., in the case of a response to a PUT request).
    18861923      </p>
    1887       <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 href="#status.202" class="smpl">202 (Accepted)</a> response instead.
    1888       </p>
    1889       <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
     1924      <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 href="#status.202" class="smpl">202 (Accepted)</a> response instead.
     1925      </p>
     1926      <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
    18901927         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.12"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>).
    18911928      </p>
    1892       <div id="rfc.iref.31"></div>
     1929      <div id="rfc.iref.32"></div>
    18931930      <div id="rfc.iref.s.9"></div>
    1894       <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>
    1895       <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
     1931      <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>
     1932      <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
    18961933         be acted upon, as it might be disallowed when processing actually takes place. There is no facility for re-sending a status
    18971934         code from an asynchronous operation such as this.
    18981935      </p>
    1899       <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
     1936      <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
    19001937         (perhaps a batch-oriented process that is only run once per day) without requiring that the user agent's connection to the
    19011938         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
    19021939         user can expect the request to be fulfilled.
    19031940      </p>
    1904       <div id="rfc.iref.32"></div>
     1941      <div id="rfc.iref.33"></div>
    19051942      <div id="rfc.iref.s.10"></div>
    1906       <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>
    1907       <p id="rfc.section.6.3.4.p.1">The representation in the response has been transformed or otherwise modified by a transforming proxy (<a href="p1-messaging.html#intermediaries" title="Intermediaries">Section 2.3</a> of <a href="#Part1" id="rfc.xref.Part1.17"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>). Note that the behavior of transforming intermediaries is controlled by the no-transform Cache-Control directive (<a href="p6-cache.html#header.cache-control" title="Cache-Control">Section 7.2</a> of <a href="#Part6" id="rfc.xref.Part6.10"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>).
    1908       </p>
    1909       <p id="rfc.section.6.3.4.p.2">This status code is only appropriate when the response status code would have been <a href="#status.200" class="smpl">200 (OK)</a> otherwise. When the status code before transformation would have been different, the 214 Transformation Applied warn-code
     1943      <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>
     1944      <p id="rfc.section.7.3.4.p.1">The representation in the response has been transformed or otherwise modified by a transforming proxy (<a href="p1-messaging.html#intermediaries" title="Intermediaries">Section 2.3</a> of <a href="#Part1" id="rfc.xref.Part1.19"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>). Note that the behavior of transforming intermediaries is controlled by the no-transform Cache-Control directive (<a href="p6-cache.html#header.cache-control" title="Cache-Control">Section 7.2</a> of <a href="#Part6" id="rfc.xref.Part6.10"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>).
     1945      </p>
     1946      <p id="rfc.section.7.3.4.p.2">This status code is only appropriate when the response status code would have been <a href="#status.200" class="smpl">200 (OK)</a> otherwise. When the status code before transformation would have been different, the 214 Transformation Applied warn-code
    19101947         (<a href="p6-cache.html#header.warning" title="Warning">Section 7.6</a> of <a href="#Part6" id="rfc.xref.Part6.11"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>) is appropriate.
    19111948      </p>
    1912       <p id="rfc.section.6.3.4.p.3">Caches <em class="bcp14">MAY</em> use a heuristic (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 4.1.2</a> of <a href="#Part6" id="rfc.xref.Part6.12"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>) to determine freshness for 203 responses.
    1913       </p>
    1914       <div id="rfc.iref.33"></div>
     1949      <p id="rfc.section.7.3.4.p.3">Caches <em class="bcp14">MAY</em> use a heuristic (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 4.1.2</a> of <a href="#Part6" id="rfc.xref.Part6.12"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>) to determine freshness for 203 responses.
     1950      </p>
     1951      <div id="rfc.iref.34"></div>
    19151952      <div id="rfc.iref.s.11"></div>
    1916       <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>
    1917       <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
     1953      <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>
     1954      <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
    19181955         content to return in the response payload body. Metadata in the response header fields refer to the target resource and its
    19191956         current representation after the requested action.
    19201957      </p>
    1921       <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
     1958      <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
    19221959         target resource.
    19231960      </p>
    1924       <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
     1961      <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
    19251962         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
    19261963         of the success to its user, in accord with its own interface, and apply any new or updated metadata in the response to the
    19271964         active representation.
    19281965      </p>
    1929       <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
     1966      <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
    19301967         the document being saved remains available to the user for editing. It is also frequently used with interfaces that expect
    19311968         automated data transfers to be prevalent, such as within distributed version control systems.
    19321969      </p>
    1933       <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.
    1934       </p>
    1935       <div id="rfc.iref.34"></div>
     1970      <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.
     1971      </p>
     1972      <div id="rfc.iref.35"></div>
    19361973      <div id="rfc.iref.s.12"></div>
    1937       <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>
    1938       <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
     1974      <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>
     1975      <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
    19391976         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
    19401977         another input action.
    19411978      </p>
    1942       <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.18"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>.
    1943       </p>
    1944       <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>
    1945       <div id="rfc.iref.35"></div>
     1979      <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.20"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>.
     1980      </p>
     1981      <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>
     1982      <div id="rfc.iref.36"></div>
    19461983      <div id="rfc.iref.s.13"></div>
    1947       <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.
     1984      <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.
    19481985         If the required action involves a subsequent HTTP request, it <em class="bcp14">MAY</em> be carried out by the user agent without interaction with the user if and only if the method used in the second request is
    1949          known to be "safe", as defined in <a href="#safe.methods" title="Safe Methods">Section&nbsp;4.2.1</a>.
    1950       </p>
    1951       <p id="rfc.section.6.4.p.2">There are several types of redirects: </p>
     1986         known to be "safe", as defined in <a href="#safe.methods" title="Safe Methods">Section&nbsp;5.2.1</a>.
     1987      </p>
     1988      <p id="rfc.section.7.4.p.2">There are several types of redirects: </p>
    19521989      <ol>
    19531990         <li>
    … …  
    19722009         </li>
    19732010      </ol>
    1974       <div class="note" id="rfc.section.6.4.p.3">
     2011      <div class="note" id="rfc.section.7.4.p.3">
    19752012         <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
    19762013            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.1"><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
    … …  
    19782015         </p>
    19792016      </div>
    1980       <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;10.13</a>.
    1981       </p>
    1982       <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
     2017      <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;10.13</a>.
     2018      </p>
     2019      <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
    19832020         issued.
    19842021      </p>
    1985       <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).
    1986       </p>
    1987       <div class="note" id="rfc.section.6.4.p.7">
     2022      <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).
     2023      </p>
     2024      <div class="note" id="rfc.section.7.4.p.7">
    19882025         <p> <b>Note:</b> An earlier version of this specification recommended a maximum of five redirections (<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">Section 10.3</a>). Content developers need to be aware that some clients might implement such a fixed limitation.
    19892026         </p>
    19902027      </div>
    1991       <div id="rfc.iref.36"></div>
     2028      <div id="rfc.iref.37"></div>
    19922029      <div id="rfc.iref.s.14"></div>
    1993       <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>
    1994       <p id="rfc.section.6.4.1.p.1">The target resource has more than one representation, each with its own specific location, and agent-driven negotiation information
     2030      <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>
     2031      <p id="rfc.section.7.4.1.p.1">The target resource has more than one representation, each with its own specific location, and agent-driven negotiation information
    19952032         (<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
    19962033         location.
    19972034      </p>
    1998       <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
     2035      <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
    19992036         choose the one most appropriate. Depending upon the format and the capabilities of the user agent, selection of the most appropriate
    20002037         choice <em class="bcp14">MAY</em> be performed automatically. However, this specification does not define any standard for such automatic selection.
    20012038      </p>
    2002       <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.
    2003       </p>
    2004       <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.13"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>) to determine freshness for 300 responses.
    2005       </p>
    2006       <div id="rfc.iref.37"></div>
     2039      <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.
     2040      </p>
     2041      <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.13"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>) to determine freshness for 300 responses.
     2042      </p>
     2043      <div id="rfc.iref.38"></div>
    20072044      <div id="rfc.iref.s.15"></div>
    2008       <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>
    2009       <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
     2045      <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>
     2046      <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
    20102047         request URI to one or more of the new references returned by the server, where possible.
    20112048      </p>
    2012       <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.14"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>) to determine freshness for 301 responses.
    2013       </p>
    2014       <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).
    2015       </p>
    2016       <div class="note" id="rfc.section.6.4.2.p.4">
    2017          <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.
    2018          </p>
    2019       </div>
    2020       <div id="rfc.iref.38"></div>
    2021       <div id="rfc.iref.s.16"></div>
    2022       <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>
    2023       <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.
    2024       </p>
    2025       <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).
    2026       </p>
    2027       <div class="note" id="rfc.section.6.4.3.p.3">
     2049      <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.14"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>) to determine freshness for 301 responses.
     2050      </p>
     2051      <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).
     2052      </p>
     2053      <div class="note" id="rfc.section.7.4.2.p.4">
    20282054         <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.
    20292055         </p>
    20302056      </div>
    20312057      <div id="rfc.iref.39"></div>
     2058      <div id="rfc.iref.s.16"></div>
     2059      <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>
     2060      <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.
     2061      </p>
     2062      <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).
     2063      </p>
     2064      <div class="note" id="rfc.section.7.4.3.p.3">
     2065         <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.
     2066         </p>
     2067      </div>
     2068      <div id="rfc.iref.40"></div>
    20322069      <div id="rfc.iref.s.17"></div>
    2033       <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>
    2034       <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
     2070      <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>
     2071      <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
    20352072         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,
    20362073         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,
    … …  
    20382075         not considered equivalent to the effective request URI.
    20392076      </p>
    2040       <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
     2077      <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
    20412078         redirect the user agent to a selected resource, since doing so provides the information corresponding to the POST response
    20422079         in a form that can be separately identified, bookmarked, and cached independent of the original request.
    20432080      </p>
    2044       <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
     2081      <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
    20452082         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
    20462083         to recipients without implying that it adequately represents the target resource. Note that answers to the questions of what
    … …  
    20482085         and thus entirely determined by the URI owner(s).
    20492086      </p>
    2050       <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.
    2051       </p>
    2052       <div id="rfc.iref.40"></div>
     2087      <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.
     2088      </p>
     2089      <div id="rfc.iref.41"></div>
    20532090      <div id="rfc.iref.s.18"></div>
    2054       <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>
    2055       <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.
    2056       </p>
    2057       <div id="rfc.iref.41"></div>
     2091      <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>
     2092      <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.
     2093      </p>
     2094      <div id="rfc.iref.42"></div>
    20582095      <div id="rfc.iref.s.19"></div>
    2059       <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>
    2060       <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>
    2061       <div id="rfc.iref.42"></div>
     2096      <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>
     2097      <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>
     2098      <div id="rfc.iref.43"></div>
    20622099      <div id="rfc.iref.s.20"></div>
    2063       <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>
    2064       <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.
    2065       </p>
    2066       <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).
    2067       </p>
    2068       <div class="note" id="rfc.section.6.4.7.p.3">
     2100      <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>
     2101      <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.
     2102      </p>
     2103      <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).
     2104      </p>
     2105      <div class="note" id="rfc.section.7.4.7.p.3">
    20692106         <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
    20702107            for <a href="#status.301" class="smpl">301 (Moved
    … …  
    20722109         </p>
    20732110      </div>
    2074       <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>
    2075       <div id="rfc.iref.43"></div>
     2111      <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>
     2112      <div id="rfc.iref.44"></div>
    20762113      <div id="rfc.iref.s.21"></div>
    2077       <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
     2114      <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
    20782115         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.
    20792116         These status codes are applicable to any request method. User agents <em class="bcp14">SHOULD</em> display any included representation to the user.
    20802117      </p>
    2081       <div id="rfc.iref.44"></div>
     2118      <div id="rfc.iref.45"></div>
    20822119      <div id="rfc.iref.s.22"></div>
    2083       <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>
    2084       <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>
    2085       <div id="rfc.iref.45"></div>
     2120      <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>
     2121      <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>
     2122      <div id="rfc.iref.46"></div>
    20862123      <div id="rfc.iref.s.23"></div>
    2087       <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>
    2088       <p id="rfc.section.6.5.2.p.1">This code is reserved for future use.</p>
    2089       <div id="rfc.iref.46"></div>
     2124      <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>
     2125      <p id="rfc.section.7.5.2.p.1">This code is reserved for future use.</p>
     2126      <div id="rfc.iref.47"></div>
    20902127      <div id="rfc.iref.s.24"></div>
    2091       <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>
    2092       <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
     2128      <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>
     2129      <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
    20932130         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.
    20942131      </p>
    2095       <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
     2132      <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
    20962133         to the client, the status code <a href="#status.404" class="smpl">404
    20972134            (Not Found)</a>  <em class="bcp14">MAY</em> be used instead.
    20982135      </p>
    2099       <div id="rfc.iref.47"></div>
     2136      <div id="rfc.iref.48"></div>
    21002137      <div id="rfc.iref.s.25"></div>
    2101       <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>
    2102       <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
     2138      <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>
     2139      <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
    21032140         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
    21042141         and has no forwarding address. This status code is commonly used when the server does not wish to reveal exactly why the request
    21052142         has been refused, or when no other response is applicable.
    21062143      </p>
    2107       <div id="rfc.iref.48"></div>
     2144      <div id="rfc.iref.49"></div>
    21082145      <div id="rfc.iref.s.26"></div>
    2109       <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>
    2110       <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.
    2111       </p>
    2112       <div id="rfc.iref.49"></div>
     2146      <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>
     2147      <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.
     2148      </p>
     2149      <div id="rfc.iref.50"></div>
    21132150      <div id="rfc.iref.s.27"></div>
    2114       <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>
    2115       <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
     2151      <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>
     2152      <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
    21162153         not acceptable according to the <a href="#header.accept" class="smpl">Accept</a> and Accept-* header fields sent in the request.
    21172154      </p>
    2118       <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
     2155      <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
    21192156         or user agent can choose the one most appropriate. Depending upon the format and the capabilities of the user agent, selection
    21202157         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.
    21212158      </p>
    2122       <div class="note" id="rfc.section.6.5.6.p.3">
     2159      <div class="note" id="rfc.section.7.5.6.p.3">
    21232160         <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
    21242161            request. In some cases, this might even be preferable to sending a 406 response. User agents are encouraged to inspect the
    … …  
    21262163         </p>
    21272164      </div>
    2128       <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.
    2129       </p>
    2130       <div id="rfc.iref.50"></div>
     2165      <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.
     2166      </p>
     2167      <div id="rfc.iref.51"></div>
    21312168      <div id="rfc.iref.s.28"></div>
    2132       <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>
    2133       <p id="rfc.section.6.5.7.p.1">The client did not produce a request within the time that the server was prepared to wait. The client <em class="bcp14">MAY</em> repeat the request without modifications at any later time.
    2134       </p>
    2135       <div id="rfc.iref.51"></div>
     2169      <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>
     2170      <p id="rfc.section.7.5.7.p.1">The client did not produce a request within the time that the server was prepared to wait. The client <em class="bcp14">MAY</em> repeat the request without modifications at any later time.
     2171      </p>
     2172      <div id="rfc.iref.52"></div>
    21362173      <div id="rfc.iref.s.29"></div>
    2137       <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>
    2138       <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
     2174      <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>
     2175      <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
    21392176         situations where it is expected that the user might be able to resolve the conflict and resubmit the request. The response
    21402177         body <em class="bcp14">SHOULD</em> include enough information for the user to recognize the source of the conflict. Ideally, the response representation would
    21412178         include enough information for the user or user agent to fix the problem; however, that might not be possible and is not required.
    21422179      </p>
    2143       <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
     2180      <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
    21442181         being PUT included changes to a resource which conflict with those made by an earlier (third-party) request, the server might
    21452182         use the 409 response to indicate that it can't complete the request. In this case, the response representation would likely
    21462183         contain a list of the differences between the two versions.
    21472184      </p>
    2148       <div id="rfc.iref.52"></div>
     2185      <div id="rfc.iref.53"></div>
    21492186      <div id="rfc.iref.s.30"></div>
    2150       <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>
    2151       <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
     2187      <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>
     2188      <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
    21522189         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,
    21532190         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.
    21542191      </p>
    2155       <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
     2192      <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
    21562193         is intentionally unavailable and that the server owners desire that remote links to that resource be removed. Such an event
    21572194         is common for limited-time, promotional services and for resources belonging to individuals no longer working at the server's
    … …  
    21592196         — that is left to the discretion of the server owner.
    21602197      </p>
    2161       <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.15"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>) to determine freshness for 410 responses.
    2162       </p>
    2163       <div id="rfc.iref.53"></div>
     2198      <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.15"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>) to determine freshness for 410 responses.
     2199      </p>
     2200      <div id="rfc.iref.54"></div>
    21642201      <div id="rfc.iref.s.31"></div>
    2165       <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>
    2166       <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
     2202      <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>
     2203      <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
    21672204         message.
    21682205      </p>
    2169       <div id="rfc.iref.54"></div>
     2206      <div id="rfc.iref.55"></div>
    21702207      <div id="rfc.iref.s.32"></div>
    2171       <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>
    2172       <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
     2208      <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>
     2209      <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
    21732210         to process. The server <em class="bcp14">MAY</em> close the connection to prevent the client from continuing the request.
    21742211      </p>
    2175       <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.
    2176       </p>
    2177       <div id="rfc.iref.55"></div>
     2212      <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.
     2213      </p>
     2214      <div id="rfc.iref.56"></div>
    21782215      <div id="rfc.iref.s.33"></div>
    2179       <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>
    2180       <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.
     2216      <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>
     2217      <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.
    21812218         This rare condition is only likely to occur when a client has improperly converted a POST request to a GET request with long
    21822219         query information, when the client has descended into a URI "black hole" of redirection (e.g., a redirected URI prefix that
    … …  
    21842221         in some servers using fixed-length buffers for reading or manipulating the request-target.
    21852222      </p>
    2186       <div id="rfc.iref.56"></div>
     2223      <div id="rfc.iref.57"></div>
    21872224      <div id="rfc.iref.s.34"></div>
    2188       <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>
    2189       <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
     2225      <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>
     2226      <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
    21902227         on the target resource.
    21912228      </p>
    2192       <div id="rfc.iref.57"></div>
     2229      <div id="rfc.iref.58"></div>
    21932230      <div id="rfc.iref.s.35"></div>
    2194       <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>
    2195       <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;10.11</a>) could not be met by this server, or, if the server is a proxy, the server has unambiguous evidence that the request could
     2231      <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>
     2232      <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;10.11</a>) could not be met by this server, or, if the server is a proxy, the server has unambiguous evidence that the request could
    21962233         not be met by the next-hop server.
    21972234      </p>
    2198       <div id="rfc.iref.58"></div>
     2235      <div id="rfc.iref.59"></div>
    21992236      <div id="rfc.iref.s.36"></div>
    2200       <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>
    2201       <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.4</a> of <a href="#Part1" id="rfc.xref.Part1.19"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>) specifying the required protocols.
     2237      <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>
     2238      <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.4</a> of <a href="#Part1" id="rfc.xref.Part1.21"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>) specifying the required protocols.
    22022239      </p>
    22032240      <div id="rfc.figure.u.6"></div>
    … …  
    22092246
    22102247<span id="s426body">This service requires use of the HTTP/3.0 protocol.
    2211 </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
     2248</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
    22122249         alternative courses which might be available to the user.
    22132250      </p>
    2214       <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>
    2215       <div id="rfc.iref.59"></div>
     2251      <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>
     2252      <div id="rfc.iref.60"></div>
    22162253      <div id="rfc.iref.s.37"></div>
    2217       <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
     2254      <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
    22182255         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.
    22192256         User agents <em class="bcp14">SHOULD</em> display any included representation to the user. These response codes are applicable to any request method.
    22202257      </p>
    2221       <div id="rfc.iref.60"></div>
     2258      <div id="rfc.iref.61"></div>
    22222259      <div id="rfc.iref.s.38"></div>
    2223       <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>
    2224       <p id="rfc.section.6.6.1.p.1">The server encountered an unexpected condition which prevented it from fulfilling the request.</p>
    2225       <div id="rfc.iref.61"></div>
     2260      <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>
     2261      <p id="rfc.section.7.6.1.p.1">The server encountered an unexpected condition which prevented it from fulfilling the request.</p>
     2262      <div id="rfc.iref.62"></div>
    22262263      <div id="rfc.iref.s.39"></div>
    2227       <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>
    2228       <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
     2264      <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>
     2265      <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
    22292266         does not recognize the request method and is not capable of supporting it for any resource.
    22302267      </p>
    2231       <div id="rfc.iref.62"></div>
     2268      <div id="rfc.iref.63"></div>
    22322269      <div id="rfc.iref.s.40"></div>
    2233       <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>
    2234       <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
     2270      <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>
     2271      <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
    22352272         to fulfill the request.
    22362273      </p>
    2237       <div id="rfc.iref.63"></div>
     2274      <div id="rfc.iref.64"></div>
    22382275      <div id="rfc.iref.s.41"></div>
    2239       <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>
    2240       <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>
    2241       <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
     2276      <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>
     2277      <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>
     2278      <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
    22422279         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;10.16</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
    22432280            Server Error)</a> response.
    22442281      </p>
    2245       <div class="note" id="rfc.section.6.6.4.p.3">
     2282      <div class="note" id="rfc.section.7.6.4.p.3">
    22462283         <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
    22472284            wish to simply refuse the connection.
    22482285         </p>
    22492286      </div>
    2250       <div id="rfc.iref.64"></div>
     2287      <div id="rfc.iref.65"></div>
    22512288      <div id="rfc.iref.s.42"></div>
    2252       <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>
    2253       <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
     2289      <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>
     2290      <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
    22542291         URI (e.g., HTTP, FTP, LDAP) or some other auxiliary server (e.g., DNS) it needed to access in attempting to complete the request.
    22552292      </p>
    2256       <div class="note" id="rfc.section.6.6.5.p.2">
     2293      <div class="note" id="rfc.section.7.6.5.p.2">
    22572294         <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
    22582295               Error)</a> when DNS lookups time out.
    22592296         </p>
    22602297      </div>
    2261       <div id="rfc.iref.65"></div>
     2298      <div id="rfc.iref.66"></div>
    22622299      <div id="rfc.iref.s.43"></div>
    2263       <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>
    2264       <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
     2300      <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>
     2301      <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
    22652302         is indicating that it is unable or unwilling to complete the request using the same major version as the client, as described
    2266          in <a href="p1-messaging.html#http.version" title="Protocol Versioning">Section 2.6</a> of <a href="#Part1" id="rfc.xref.Part1.20"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[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.
    2267       </p>
    2268       <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>
    2269       <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
    2270          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.21"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>).
    2271       </p>
    2272       <div id="rfc.table.u.9">
     2303         in <a href="p1-messaging.html#http.version" title="Protocol Versioning">Section 2.6</a> of <a href="#Part1" id="rfc.xref.Part1.22"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[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.
     2304      </p>
     2305      <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>
     2306      <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
     2307         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.23"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>).
     2308      </p>
     2309      <div id="rfc.table.u.10">
    22732310         <table class="tt full left" cellpadding="3" cellspacing="0">
    22742311            <thead>
    … …  
    22812318               <tr>
    22822319                  <td class="left">Accept-Ranges</td>
    2283                   <td class="left"><a href="p5-range.html#header.accept-ranges" title="Accept-Ranges">Section 5.1</a> of <a href="#Part5" id="rfc.xref.Part5.9"><cite title="HTTP/1.1, part 5: Range Requests">[Part5]</cite></a></td>
     2320                  <td class="left"><a href="p5-range.html#header.accept-ranges" title="Accept-Ranges">Section 5.1</a> of <a href="#Part5" id="rfc.xref.Part5.10"><cite title="HTTP/1.1, part 5: Range Requests">[Part5]</cite></a></td>
    22842321               </tr>
    22852322               <tr>
    … …  
    23262363         </table>
    23272364      </div>
    2328       <h1 id="rfc.section.8"><a href="#rfc.section.8">8.</a>&nbsp;<a id="protocol.parameters" href="#protocol.parameters">Protocol Parameters</a></h1>
    2329       <h2 id="rfc.section.8.1"><a href="#rfc.section.8.1">8.1</a>&nbsp;<a id="http.date" href="#http.date">Date/Time Formats</a></h2>
    2330       <p id="rfc.section.8.1.p.1">HTTP applications have historically allowed three different formats for date/time stamps. However, the preferred format is
     2365      <h1 id="rfc.section.9"><a href="#rfc.section.9">9.</a>&nbsp;<a id="protocol.parameters" href="#protocol.parameters">Protocol Parameters</a></h1>
     2366      <h2 id="rfc.section.9.1"><a href="#rfc.section.9.1">9.1</a>&nbsp;<a id="http.date" href="#http.date">Date/Time Formats</a></h2>
     2367      <p id="rfc.section.9.1.p.1">HTTP applications have historically allowed three different formats for date/time stamps. However, the preferred format is
    23312368         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>:
    23322369      </p>
    23332370      <div id="rfc.figure.u.7"></div><pre class="text">Sun, 06 Nov 1994 08:49:37 GMT  ; RFC 1123
    2334 </pre><p id="rfc.section.8.1.p.3">The other formats are described here only for compatibility with obsolete implementations.</p>
     2371</pre><p id="rfc.section.9.1.p.3">The other formats are described here only for compatibility with obsolete implementations.</p>
    23352372      <div id="rfc.figure.u.8"></div><pre class="text">Sunday, 06-Nov-94 08:49:37 GMT ; obsolete RFC 850 format
    23362373Sun Nov  6 08:49:37 1994       ; ANSI C's asctime() format
    2337 </pre><p id="rfc.section.8.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.
    2338       </p>
    2339       <p id="rfc.section.8.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
     2374</pre><p id="rfc.section.9.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.
     2375      </p>
     2376      <p id="rfc.section.9.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
    23402377         Universal Time). This is indicated in the first two formats by the inclusion of "GMT" as the three-letter abbreviation for
    23412378         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.
    … …  
    23432380      <div id="rfc.figure.u.9"></div><pre class="inline"><span id="rfc.iref.g.5"></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>
    23442381</pre><div id="preferred.date.format">
    2345          <p id="rfc.section.8.1.p.8">                    Preferred format:</p>
     2382         <p id="rfc.section.9.1.p.8">                    Preferred format:</p>
    23462383      </div>
    23472384      <div id="rfc.figure.u.10"></div><pre class="inline"><span id="rfc.iref.g.6"></span><span id="rfc.iref.g.7"></span><span id="rfc.iref.g.8"></span><span id="rfc.iref.g.9"></span><span id="rfc.iref.g.10"></span><span id="rfc.iref.g.11"></span><span id="rfc.iref.g.12"></span><span id="rfc.iref.g.13"></span><span id="rfc.iref.g.14"></span><span id="rfc.iref.g.15"></span><span id="rfc.iref.g.16"></span><span id="rfc.iref.g.17"></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>
    … …  
    23832420  <a href="#preferred.date.format" class="smpl">minute</a>       = 2<a href="#imported.abnf" class="smpl">DIGIT</a>               
    23842421  <a href="#preferred.date.format" class="smpl">second</a>       = 2<a href="#imported.abnf" class="smpl">DIGIT</a>               
    2385 </pre><p id="rfc.section.8.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.1"><cite title="Internet Message Format">[RFC5322]</cite></a>, <a href="http://tools.ietf.org/html/rfc5322#section-3.3">Section 3.3</a>).
     2422</pre><p id="rfc.section.9.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.1"><cite title="Internet Message Format">[RFC5322]</cite></a>, <a href="http://tools.ietf.org/html/rfc5322#section-3.3">Section 3.3</a>).
    23862423      </p>
    23872424      <div id="obsolete.date.formats">
    2388          <p id="rfc.section.8.1.p.11">              Obsolete formats:</p>
     2425         <p id="rfc.section.9.1.p.11">              Obsolete formats:</p>
    23892426      </div>
    23902427      <div id="rfc.figure.u.11"></div><pre class="inline"><span id="rfc.iref.g.18"></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>
    … …  
    24032440  <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> ))
    24042441                 ; month day (e.g., Jun  2)
    2405 </pre><div class="note" id="rfc.section.8.1.p.15">
     2442</pre><div class="note" id="rfc.section.9.1.p.15">
    24062443         <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,
    24072444            as is sometimes the case when retrieving or posting messages via proxies/gateways to SMTP or NNTP.
    24082445         </p>
    24092446      </div>
    2410       <div class="note" id="rfc.section.8.1.p.16">
     2447      <div class="note" id="rfc.section.9.1.p.16">
    24112448         <p> <b>Note:</b> HTTP requirements for the date/time stamp format apply only to their usage within the protocol stream. Clients and servers
    24122449            are not required to use these formats for user presentation, request logging, etc.
    24132450         </p>
    24142451      </div>
    2415       <h2 id="rfc.section.8.2"><a href="#rfc.section.8.2">8.2</a>&nbsp;<a id="product.tokens" href="#product.tokens">Product Tokens</a></h2>
    2416       <p id="rfc.section.8.2.p.1">Product tokens are used to allow communicating applications to identify themselves by software name and version. Most fields
     2452      <h2 id="rfc.section.9.2"><a href="#rfc.section.9.2">9.2</a>&nbsp;<a id="product.tokens" href="#product.tokens">Product Tokens</a></h2>
     2453      <p id="rfc.section.9.2.p.1">Product tokens are used to allow communicating applications to identify themselves by software name and version. Most fields
    24172454         using product tokens also allow sub-products which form a significant part of the application to be listed, separated by whitespace.
    24182455         By convention, the products are listed in order of their significance for identifying the application.
    … …  
    24202457      <div id="rfc.figure.u.14"></div><pre class="inline"><span id="rfc.iref.g.21"></span><span id="rfc.iref.g.22"></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>]
    24212458  <a href="#product.tokens" class="smpl">product-version</a> = <a href="#imported.abnf" class="smpl">token</a>
    2422 </pre><p id="rfc.section.8.2.p.3">Examples:</p>
     2459</pre><p id="rfc.section.9.2.p.3">Examples:</p>
    24232460      <div id="rfc.figure.u.15"></div><pre class="text">  User-Agent: CERN-LineMode/2.15 libwww/2.17b3
    24242461  Server: Apache/0.8.4
    2425 </pre><p id="rfc.section.8.2.p.5">Product tokens <em class="bcp14">SHOULD</em> be short and to the point. They <em class="bcp14">MUST NOT</em> be used for advertising or other non-essential information. Although any token octet <em class="bcp14">MAY</em> appear in a product-version, this token <em class="bcp14">SHOULD</em> only be used for a version identifier (i.e., successive versions of the same product <em class="bcp14">SHOULD</em> only differ in the product-version portion of the product value).
    2426       </p>
    2427       <h2 id="rfc.section.8.3"><a href="#rfc.section.8.3">8.3</a>&nbsp;<a id="character.sets" href="#character.sets">Character Encodings (charset)</a></h2>
    2428       <p id="rfc.section.8.3.p.1">HTTP uses charset names to indicate the character encoding of a textual representation.</p>
     2462</pre><p id="rfc.section.9.2.p.5">Product tokens <em class="bcp14">SHOULD</em> be short and to the point. They <em class="bcp14">MUST NOT</em> be used for advertising or other non-essential information. Although any token octet <em class="bcp14">MAY</em> appear in a product-version, this token <em class="bcp14">SHOULD</em> only be used for a version identifier (i.e., successive versions of the same product <em class="bcp14">SHOULD</em> only differ in the product-version portion of the product value).
     2463      </p>
     2464      <h2 id="rfc.section.9.3"><a href="#rfc.section.9.3">9.3</a>&nbsp;<a id="character.sets" href="#character.sets">Character Encodings (charset)</a></h2>
     2465      <p id="rfc.section.9.3.p.1">HTTP uses charset names to indicate the character encoding of a textual representation.</p>
    24292466      <div id="rule.charset">
    2430          <p id="rfc.section.8.3.p.2">  A character encoding is identified by a case-insensitive token. The complete set of tokens is defined by the IANA Character
     2467         <p id="rfc.section.9.3.p.2">  A character encoding is identified by a case-insensitive token. The complete set of tokens is defined by the IANA Character
    24312468            Set registry (&lt;<a href="http://www.iana.org/assignments/character-sets">http://www.iana.org/assignments/character-sets</a>&gt;).
    24322469         </p>
    24332470      </div>
    24342471      <div id="rfc.figure.u.16"></div><pre class="inline"><span id="rfc.iref.g.23"></span>  <a href="#rule.charset" class="smpl">charset</a> = <a href="#imported.abnf" class="smpl">token</a>
    2435 </pre><p id="rfc.section.8.3.p.4">Although HTTP allows an arbitrary token to be used as a charset value, any token that has a predefined value within the IANA
     2472</pre><p id="rfc.section.9.3.p.4">Although HTTP allows an arbitrary token to be used as a charset value, any token that has a predefined value within the IANA
    24362473         Character Set registry <em class="bcp14">MUST</em> represent the character encoding defined by that registry. Applications <em class="bcp14">SHOULD</em> limit their use of character encodings to those defined within the IANA registry.
    24372474      </p>
    2438       <p id="rfc.section.8.3.p.5">HTTP uses charset in two contexts: within an <a href="#header.accept-charset" class="smpl">Accept-Charset</a> request header field (in which the charset value is an unquoted token) and as the value of a parameter in a <a href="#header.content-type" class="smpl">Content-Type</a> header field (within a request or response), in which case the parameter value of the charset parameter can be quoted.
    2439       </p>
    2440       <p id="rfc.section.8.3.p.6">Implementers need to be aware of IETF character set requirements <a href="#RFC3629" id="rfc.xref.RFC3629.1"><cite title="UTF-8, a transformation format of ISO 10646">[RFC3629]</cite></a>  <a href="#RFC2277" id="rfc.xref.RFC2277.1"><cite title="IETF Policy on Character Sets and Languages">[RFC2277]</cite></a>.
    2441       </p>
    2442       <h2 id="rfc.section.8.4"><a href="#rfc.section.8.4">8.4</a>&nbsp;<a id="content.codings" href="#content.codings">Content Codings</a></h2>
    2443       <p id="rfc.section.8.4.p.1">Content coding values indicate an encoding transformation that has been or can be applied to a representation. Content codings
     2475      <p id="rfc.section.9.3.p.5">HTTP uses charset in two contexts: within an <a href="#header.accept-charset" class="smpl">Accept-Charset</a> request header field (in which the charset value is an unquoted token) and as the value of a parameter in a <a href="#header.content-type" class="smpl">Content-Type</a> header field (within a request or response), in which case the parameter value of the charset parameter can be quoted.
     2476      </p>
     2477      <p id="rfc.section.9.3.p.6">Implementers need to be aware of IETF character set requirements <a href="#RFC3629" id="rfc.xref.RFC3629.1"><cite title="UTF-8, a transformation format of ISO 10646">[RFC3629]</cite></a>  <a href="#RFC2277" id="rfc.xref.RFC2277.1"><cite title="IETF Policy on Character Sets and Languages">[RFC2277]</cite></a>.
     2478      </p>
     2479      <h2 id="rfc.section.9.4"><a href="#rfc.section.9.4">9.4</a>&nbsp;<a id="content.codings" href="#content.codings">Content Codings</a></h2>
     2480      <p id="rfc.section.9.4.p.1">Content coding values indicate an encoding transformation that has been or can be applied to a representation. Content codings
    24442481         are primarily used to allow a representation to be compressed or otherwise usefully transformed without losing the identity
    24452482         of its underlying media type and without loss of information. Frequently, the representation is stored in coded form, transmitted
    … …  
    24472484      </p>
    24482485      <div id="rfc.figure.u.17"></div><pre class="inline"><span id="rfc.iref.g.24"></span>  <a href="#content.codings" class="smpl">content-coding</a>   = <a href="#imported.abnf" class="smpl">token</a>
    2449 </pre><p id="rfc.section.8.4.p.3">All content-coding values are case-insensitive. HTTP/1.1 uses content-coding values in the <a href="#header.accept-encoding" class="smpl">Accept-Encoding</a> (<a href="#header.accept-encoding" id="rfc.xref.header.accept-encoding.3" title="Accept-Encoding">Section&nbsp;10.3</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;10.6</a>) header fields. Although the value describes the content-coding, what is more important is that it indicates what decoding
     2486</pre><p id="rfc.section.9.4.p.3">All content-coding values are case-insensitive. HTTP/1.1 uses content-coding values in the <a href="#header.accept-encoding" class="smpl">Accept-Encoding</a> (<a href="#header.accept-encoding" id="rfc.xref.header.accept-encoding.3" title="Accept-Encoding">Section&nbsp;10.3</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;10.6</a>) header fields. Although the value describes the content-coding, what is more important is that it indicates what decoding
    24502487         mechanism will be required to remove the encoding.
    24512488      </p>
    2452       <p id="rfc.section.8.4.p.4">compress<span id="rfc.iref.c.4"></span><span id="rfc.iref.c.5"></span> 
     2489      <p id="rfc.section.9.4.p.4">compress<span id="rfc.iref.c.4"></span><span id="rfc.iref.c.5"></span> 
    24532490      </p>
    24542491      <ul class="empty">
    2455          <li>See <a href="p1-messaging.html#compress.coding" title="Compress Coding">Section 4.2.1</a> of <a href="#Part1" id="rfc.xref.Part1.22"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>.
    2456          </li>
    2457       </ul>
    2458       <p id="rfc.section.8.4.p.5">deflate<span id="rfc.iref.d.2"></span><span id="rfc.iref.c.6"></span> 
     2492         <li>See <a href="p1-messaging.html#compress.coding" title="Compress Coding">Section 4.2.1</a> of <a href="#Part1" id="rfc.xref.Part1.24"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>.
     2493         </li>
     2494      </ul>
     2495      <p id="rfc.section.9.4.p.5">deflate<span id="rfc.iref.d.2"></span><span id="rfc.iref.c.6"></span> 
    24592496      </p>
    24602497      <ul class="empty">
    2461          <li>See <a href="p1-messaging.html#deflate.coding" title="Deflate Coding">Section 4.2.2</a> of <a href="#Part1" id="rfc.xref.Part1.23"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>.
    2462          </li>
    2463       </ul>
    2464       <p id="rfc.section.8.4.p.6">gzip<span id="rfc.iref.g.25"></span><span id="rfc.iref.c.7"></span> 
     2498         <li>See <a href="p1-messaging.html#deflate.coding" title="Deflate Coding">Section 4.2.2</a> of <a href="#Part1" id="rfc.xref.Part1.25"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>.
     2499         </li>
     2500      </ul>
     2501      <p id="rfc.section.9.4.p.6">gzip<span id="rfc.iref.g.25"></span><span id="rfc.iref.c.7"></span> 
    24652502      </p>
    24662503      <ul class="empty">
    2467          <li>See <a href="p1-messaging.html#gzip.coding" title="Gzip Coding">Section 4.2.3</a> of <a href="#Part1" id="rfc.xref.Part1.24"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>.
    2468          </li>
    2469       </ul>
    2470       <h2 id="rfc.section.8.5"><a href="#rfc.section.8.5">8.5</a>&nbsp;<a id="media.types" href="#media.types">Media Types</a></h2>
    2471       <p id="rfc.section.8.5.p.1">HTTP uses Internet Media Types <a href="#RFC2046" id="rfc.xref.RFC2046.2"><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.3" title="Content-Type">Section&nbsp;10.9</a>) and <a href="#header.accept" class="smpl">Accept</a> (<a href="#header.accept" id="rfc.xref.header.accept.3" title="Accept">Section&nbsp;10.1</a>) header fields in order to provide open and extensible data typing and type negotiation.
     2504         <li>See <a href="p1-messaging.html#gzip.coding" title="Gzip Coding">Section 4.2.3</a> of <a href="#Part1" id="rfc.xref.Part1.26"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>.
     2505         </li>
     2506      </ul>
     2507      <h2 id="rfc.section.9.5"><a href="#rfc.section.9.5">9.5</a>&nbsp;<a id="media.types" href="#media.types">Media Types</a></h2>
     2508      <p id="rfc.section.9.5.p.1">HTTP uses Internet Media Types <a href="#RFC2046" id="rfc.xref.RFC2046.2"><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.3" title="Content-Type">Section&nbsp;10.9</a>) and <a href="#header.accept" class="smpl">Accept</a> (<a href="#header.accept" id="rfc.xref.header.accept.3" title="Accept">Section&nbsp;10.1</a>) header fields in order to provide open and extensible data typing and type negotiation.
    24722509      </p>
    24732510      <div id="rfc.figure.u.18"></div><pre class="inline"><span id="rfc.iref.g.26"></span><span id="rfc.iref.g.27"></span><span id="rfc.iref.g.28"></span>  <a href="#media.types" class="smpl">media-type</a> = <a href="#media.types" class="smpl">type</a> "/" <a href="#media.types" class="smpl">subtype</a> *( <a href="#imported.abnf" class="smpl">OWS</a> ";" <a href="#imported.abnf" class="smpl">OWS</a> <a href="#rule.parameter" class="smpl">parameter</a> )
    … …  
    24752512  <a href="#media.types" class="smpl">subtype</a>    = <a href="#imported.abnf" class="smpl">token</a>
    24762513</pre><div id="rule.parameter">
    2477          <p id="rfc.section.8.5.p.3">      The type/subtype <em class="bcp14">MAY</em> be followed by parameters in the form of attribute/value pairs.
     2514         <p id="rfc.section.9.5.p.3">      The type/subtype <em class="bcp14">MAY</em> be followed by parameters in the form of attribute/value pairs.
    24782515         </p>
    24792516      </div>
    … …  
    24812518  <a href="#rule.parameter" class="smpl">attribute</a>      = <a href="#imported.abnf" class="smpl">token</a>
    24822519  <a href="#rule.parameter" class="smpl">value</a>          = <a href="#imported.abnf" class="smpl">word</a>
    2483 </pre><p id="rfc.section.8.5.p.5">The type, subtype, and parameter attribute names are case-insensitive. Parameter values might or might not be case-sensitive,
     2520</pre><p id="rfc.section.9.5.p.5">The type, subtype, and parameter attribute names are case-insensitive. Parameter values might or might not be case-sensitive,
    24842521         depending on the semantics of the parameter name. The presence or absence of a parameter might be significant to the processing
    24852522         of a media-type, depending on its definition within the media type registry.
    24862523      </p>
    2487       <p id="rfc.section.8.5.p.6">A parameter value that matches the <a href="#imported.abnf" class="smpl">token</a> production can be transmitted as either a token or within a quoted-string. The quoted and unquoted values are equivalent.
    2488       </p>
    2489       <p id="rfc.section.8.5.p.7">Note that some older HTTP applications do not recognize media type parameters. When sending data to older HTTP applications,
     2524      <p id="rfc.section.9.5.p.6">A parameter value that matches the <a href="#imported.abnf" class="smpl">token</a> production can be transmitted as either a token or within a quoted-string. The quoted and unquoted values are equivalent.
     2525      </p>
     2526      <p id="rfc.section.9.5.p.7">Note that some older HTTP applications do not recognize media type parameters. When sending data to older HTTP applications,
    24902527         implementations <em class="bcp14">SHOULD</em> only use media type parameters when they are required by that type/subtype definition.
    24912528      </p>
    2492       <p id="rfc.section.8.5.p.8">Media-type values are registered with the Internet Assigned Number Authority (IANA). The media type registration process is
     2529      <p id="rfc.section.9.5.p.8">Media-type values are registered with the Internet Assigned Number Authority (IANA). The media type registration process is
    24932530         outlined in <a href="#RFC4288" id="rfc.xref.RFC4288.1"><cite title="Media Type Specifications and Registration Procedures">[RFC4288]</cite></a>. Use of non-registered media types is discouraged.
    24942531      </p>
    2495       <h3 id="rfc.section.8.5.1"><a href="#rfc.section.8.5.1">8.5.1</a>&nbsp;<a id="canonicalization.and.text.defaults" href="#canonicalization.and.text.defaults">Canonicalization and Text Defaults</a></h3>
    2496       <p id="rfc.section.8.5.1.p.1">Internet media types are registered with a canonical form. A representation transferred via HTTP messages <em class="bcp14">MUST</em> be in the appropriate canonical form prior to its transmission except for "text" types, as defined in the next paragraph.
    2497       </p>
    2498       <p id="rfc.section.8.5.1.p.2">When in canonical form, media subtypes of the "text" type use CRLF as the text line break. HTTP relaxes this requirement and
     2532      <h3 id="rfc.section.9.5.1"><a href="#rfc.section.9.5.1">9.5.1</a>&nbsp;<a id="canonicalization.and.text.defaults" href="#canonicalization.and.text.defaults">Canonicalization and Text Defaults</a></h3>
     2533      <p id="rfc.section.9.5.1.p.1">Internet media types are registered with a canonical form. A representation transferred via HTTP messages <em class="bcp14">MUST</em> be in the appropriate canonical form prior to its transmission except for "text" types, as defined in the next paragraph.
     2534      </p>
     2535      <p id="rfc.section.9.5.1.p.2">When in canonical form, media subtypes of the "text" type use CRLF as the text line break. HTTP relaxes this requirement and
    24992536         allows the transport of text media with plain CR or LF alone representing a line break when it is done consistently for an
    25002537         entire representation. HTTP applications <em class="bcp14">MUST</em> accept CRLF, bare CR, and bare LF as indicating a line break in text media received via HTTP. In addition, if the text is
    … …  
    25042541         body; a bare CR or LF <em class="bcp14">MUST NOT</em> be substituted for CRLF within any of the HTTP control structures (such as header fields and multipart boundaries).
    25052542      </p>
    2506       <p id="rfc.section.8.5.1.p.3">If a representation is encoded with a content-coding, the underlying data <em class="bcp14">MUST</em> be in a form defined above prior to being encoded.
    2507       </p>
    2508       <h3 id="rfc.section.8.5.2"><a href="#rfc.section.8.5.2">8.5.2</a>&nbsp;<a id="multipart.types" href="#multipart.types">Multipart Types</a></h3>
    2509       <p id="rfc.section.8.5.2.p.1">MIME provides for a number of "multipart" types — encapsulations of one or more representations within a single message body.
     2543      <p id="rfc.section.9.5.1.p.3">If a representation is encoded with a content-coding, the underlying data <em class="bcp14">MUST</em> be in a form defined above prior to being encoded.
     2544      </p>
     2545      <h3 id="rfc.section.9.5.2"><a href="#rfc.section.9.5.2">9.5.2</a>&nbsp;<a id="multipart.types" href="#multipart.types">Multipart Types</a></h3>
     2546      <p id="rfc.section.9.5.2.p.1">MIME provides for a number of "multipart" types — encapsulations of one or more representations within a single message body.
    25102547         All multipart types share a common syntax, as defined in <a href="http://tools.ietf.org/html/rfc2046#section-5.1.1">Section 5.1.1</a> of <a href="#RFC2046" id="rfc.xref.RFC2046.3"><cite title="Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types">[RFC2046]</cite></a>, and <em class="bcp14">MUST</em> include a boundary parameter as part of the media type value. The message body is itself a protocol element and <em class="bcp14">MUST</em> therefore use only CRLF to represent line breaks between body-parts.
    25112548      </p>
    2512       <p id="rfc.section.8.5.2.p.2">In general, HTTP treats a multipart message body no differently than any other media type: strictly as payload. HTTP does
     2549      <p id="rfc.section.9.5.2.p.2">In general, HTTP treats a multipart message body no differently than any other media type: strictly as payload. HTTP does
    25132550         not use the multipart boundary as an indicator of message body length.  In all other respects, an HTTP user agent <em class="bcp14">SHOULD</em> follow the same or similar behavior as a MIME user agent would upon receipt of a multipart type. The MIME header fields within
    25142551         each body-part of a multipart message body do not have any significance to HTTP beyond that defined by their MIME semantics.
    25152552      </p>
    2516       <p id="rfc.section.8.5.2.p.3">If an application receives an unrecognized multipart subtype, the application <em class="bcp14">MUST</em> treat it as being equivalent to "multipart/mixed".
    2517       </p>
    2518       <div class="note" id="rfc.section.8.5.2.p.4">
     2553      <p id="rfc.section.9.5.2.p.3">If an application receives an unrecognized multipart subtype, the application <em class="bcp14">MUST</em> treat it as being equivalent to "multipart/mixed".
     2554      </p>
     2555      <div class="note" id="rfc.section.9.5.2.p.4">
    25192556         <p> <b>Note:</b> The "multipart/form-data" type has been specifically defined for carrying form data suitable for processing via the POST request
    25202557            method, as described in <a href="#RFC2388" id="rfc.xref.RFC2388.1"><cite title="Returning Values from Forms: multipart/form-data">[RFC2388]</cite></a>.
    25212558         </p>
    25222559      </div>
    2523       <h2 id="rfc.section.8.6"><a href="#rfc.section.8.6">8.6</a>&nbsp;<a id="language.tags" href="#language.tags">Language Tags</a></h2>
    2524       <p id="rfc.section.8.6.p.1">A language tag, as defined in <a href="#RFC5646" id="rfc.xref.RFC5646.1"><cite title="Tags for Identifying Languages">[RFC5646]</cite></a>, identifies a natural language spoken, written, or otherwise conveyed by human beings for communication of information to
     2560      <h2 id="rfc.section.9.6"><a href="#rfc.section.9.6">9.6</a>&nbsp;<a id="language.tags" href="#language.tags">Language Tags</a></h2>
     2561      <p id="rfc.section.9.6.p.1">A language tag, as defined in <a href="#RFC5646" id="rfc.xref.RFC5646.1"><cite title="Tags for Identifying Languages">[RFC5646]</cite></a>, identifies a natural language spoken, written, or otherwise conveyed by human beings for communication of information to
    25252562         other human beings. Computer languages are explicitly excluded. HTTP uses language tags within the <a href="#header.accept-language" class="smpl">Accept-Language</a> and <a href="#header.content-language" class="smpl">Content-Language</a> fields.
    25262563      </p>
    2527       <p id="rfc.section.8.6.p.2">In summary, a language tag is composed of one or more parts: A primary language subtag followed by a possibly empty series
     2564      <p id="rfc.section.9.6.p.2">In summary, a language tag is composed of one or more parts: A primary language subtag followed by a possibly empty series
    25282565         of subtags:
    25292566      </p>
    25302567      <div id="rfc.figure.u.20"></div><pre class="inline"><span id="rfc.iref.g.32"></span>  <a href="#language.tags" class="smpl">language-tag</a> = &lt;Language-Tag, defined in <a href="#RFC5646" id="rfc.xref.RFC5646.2"><cite title="Tags for Identifying Languages">[RFC5646]</cite></a>, <a href="http://tools.ietf.org/html/rfc5646#section-2.1">Section 2.1</a>&gt;
    2531 </pre><p id="rfc.section.8.6.p.4">White space is not allowed within the tag and all tags are case-insensitive. The name space of language subtags is administered
     2568</pre><p id="rfc.section.9.6.p.4">White space is not allowed within the tag and all tags are case-insensitive. The name space of language subtags is administered
    25322569         by the IANA (see &lt;<a href="http://www.iana.org/assignments/language-subtag-registry">http://www.iana.org/assignments/language-subtag-registry</a>&gt;).
    25332570      </p>
    25342571      <div id="rfc.figure.u.21"></div>
    25352572      <p>Example tags include:</p>  <pre class="text">  en, en-US, es-419, az-Arab, x-pig-latin, man-Nkoo-GN
    2536 </pre> <p id="rfc.section.8.6.p.6">See <a href="#RFC5646" id="rfc.xref.RFC5646.3"><cite title="Tags for Identifying Languages">[RFC5646]</cite></a> for further information.
    2537       </p>
    2538       <h1 id="rfc.section.9"><a href="#rfc.section.9">9.</a>&nbsp;<a id="payload" href="#payload">Payload</a></h1>
    2539       <p id="rfc.section.9.p.1">HTTP messages <em class="bcp14">MAY</em> transfer a payload if not otherwise restricted by the request method or response status code. The payload consists of metadata,
    2540          in the form of header fields, and data, in the form of the sequence of octets in the message body after any transfer-coding
    2541          has been decoded.
    2542       </p>
    2543       <div id="rfc.iref.p.3"></div>
    2544       <p id="rfc.section.9.p.2">A "<dfn>payload</dfn>" in HTTP is always a partial or complete representation of some resource. We use separate terms for payload and representation
    2545          because some messages contain only the associated representation's header fields (e.g., responses to HEAD) or only some part(s)
    2546          of the representation (e.g., the <a href="p5-range.html#status.206" class="smpl">206 (Partial Content)</a> status code).
    2547       </p>
    2548       <h2 id="rfc.section.9.1"><a href="#rfc.section.9.1">9.1</a>&nbsp;<a id="payload.header.fields" href="#payload.header.fields">Payload Header Fields</a></h2>
    2549       <p id="rfc.section.9.1.p.1">HTTP header fields that specifically define the payload, rather than the associated representation, are referred to as "payload
    2550          header fields". The following payload header fields are defined by HTTP/1.1:
    2551       </p>
    2552       <div id="rfc.table.u.10">
    2553          <table class="tt full left" cellpadding="3" cellspacing="0">
    2554             <thead>
    2555                <tr>
    2556                   <th>Header Field Name</th>
    2557                   <th>Defined in...</th>
    2558                </tr>
    2559             </thead>
    2560             <tbody>
    2561                <tr>
    2562                   <td class="left">Content-Length</td>
    2563                   <td class="left"><a href="p1-messaging.html#header.content-length" title="Content-Length">Section 3.3.2</a> of <a href="#Part1" id="rfc.xref.Part1.25"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a></td>
    2564                </tr>
    2565                <tr>
    2566                   <td class="left">Content-Range</td>
    2567                   <td class="left"><a href="p5-range.html#header.content-range" title="Content-Range">Section 5.2</a> of <a href="#Part5" id="rfc.xref.Part5.10"><cite title="HTTP/1.1, part 5: Range Requests">[Part5]</cite></a></td>
    2568                </tr>
    2569             </tbody>
    2570          </table>
    2571       </div>
    2572       <h2 id="rfc.section.9.2"><a href="#rfc.section.9.2">9.2</a>&nbsp;<a id="payload.body" href="#payload.body">Payload Body</a></h2>
    2573       <p id="rfc.section.9.2.p.1">A payload body is only present in a message when a message body is present, as described in <a href="p1-messaging.html#message.body" title="Message Body">Section 3.3</a> of <a href="#Part1" id="rfc.xref.Part1.26"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>. The payload body is obtained from the message body by decoding any <a href="p1-messaging.html#header.transfer-encoding" class="smpl">Transfer-Encoding</a> that might have been applied to ensure safe and proper transfer of the message.
     2573</pre> <p id="rfc.section.9.6.p.6">See <a href="#RFC5646" id="rfc.xref.RFC5646.3"><cite title="Tags for Identifying Languages">[RFC5646]</cite></a> for further information.
    25742574      </p>
    25752575      <h1 id="rfc.section.10"><a href="#rfc.section.10">10.</a>&nbsp;<a id="header.field.definitions" href="#header.field.definitions">Header Field Definitions</a></h1>
    … …  
    26832683      </p>
    26842684      <div id="rfc.figure.u.27"></div><pre class="inline"><span id="rfc.iref.g.37"></span>  <a href="#header.accept-charset" class="smpl">Accept-Charset</a> = 1#( ( <a href="#rule.charset" class="smpl">charset</a> / "*" ) [ <a href="#quality.values" class="smpl">weight</a> ] )
    2685 </pre><p id="rfc.section.10.2.p.3">Character encoding values (a.k.a., charsets) are described in <a href="#character.sets" title="Character Encodings (charset)">Section&nbsp;8.3</a>. Each charset <em class="bcp14">MAY</em> be given an associated quality value which represents the user's preference for that charset, as defined in <a href="#quality.values" title="Quality Values">Section&nbsp;3.4.3</a>. An example is
     2685</pre><p id="rfc.section.10.2.p.3">Character encoding values (a.k.a., charsets) are described in <a href="#character.sets" title="Character Encodings (charset)">Section&nbsp;9.3</a>. Each charset <em class="bcp14">MAY</em> be given an associated quality value which represents the user's preference for that charset, as defined in <a href="#quality.values" title="Quality Values">Section&nbsp;3.4.3</a>. An example is
    26862686      </p>
    26872687      <div id="rfc.figure.u.28"></div><pre class="text">  Accept-Charset: iso-8859-5, unicode-1-1;q=0.8
    … …  
    26972697      <div id="rfc.iref.h.4"></div>
    26982698      <h2 id="rfc.section.10.3"><a href="#rfc.section.10.3">10.3</a>&nbsp;<a id="header.accept-encoding" href="#header.accept-encoding">Accept-Encoding</a></h2>
    2699       <p id="rfc.section.10.3.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;8.4</a>) are acceptable in the response. An "identity" token is used as a synonym for "no encoding" in order to communicate when
     2699      <p id="rfc.section.10.3.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;9.4</a>) are acceptable in the response. An "identity" token is used as a synonym for "no encoding" in order to communicate when
    27002700         no encoding is preferred.
    27012701      </p>
    … …  
    27392739      <h2 id="rfc.section.10.4"><a href="#rfc.section.10.4">10.4</a>&nbsp;<a id="header.accept-language" href="#header.accept-language">Accept-Language</a></h2>
    27402740      <p id="rfc.section.10.4.p.1">The "Accept-Language" header field can be used by user agents to indicate the set of natural languages that are preferred
    2741          in the response. Language tags are defined in <a href="#language.tags" title="Language Tags">Section&nbsp;8.6</a>.
     2741         in the response. Language tags are defined in <a href="#language.tags" title="Language Tags">Section&nbsp;9.6</a>.
    27422742      </p>
    27432743      <div id="rfc.figure.u.31"></div><pre class="inline"><span id="rfc.iref.g.40"></span><span id="rfc.iref.g.41"></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> ] )
    … …  
    27902790      </p>
    27912791      <div id="rfc.figure.u.35"></div><pre class="inline"><span id="rfc.iref.g.43"></span>  <a href="#header.content-encoding" class="smpl">Content-Encoding</a> = 1#<a href="#content.codings" class="smpl">content-coding</a>
    2792 </pre><p id="rfc.section.10.6.p.3">Content codings are defined in <a href="#content.codings" title="Content Codings">Section&nbsp;8.4</a>. An example of its use is
     2792</pre><p id="rfc.section.10.6.p.3">Content codings are defined in <a href="#content.codings" title="Content Codings">Section&nbsp;9.4</a>. An example of its use is
    27932793      </p>
    27942794      <div id="rfc.figure.u.36"></div><pre class="text">  Content-Encoding: gzip
    … …  
    28172817      </p>
    28182818      <div id="rfc.figure.u.37"></div><pre class="inline"><span id="rfc.iref.g.44"></span>  <a href="#header.content-language" class="smpl">Content-Language</a> = 1#<a href="#language.tags" class="smpl">language-tag</a>
    2819 </pre><p id="rfc.section.10.7.p.3">Language tags are defined in <a href="#language.tags" title="Language Tags">Section&nbsp;8.6</a>. The primary purpose of Content-Language is to allow a user to identify and differentiate representations according to the
     2819</pre><p id="rfc.section.10.7.p.3">Language tags are defined in <a href="#language.tags" title="Language Tags">Section&nbsp;9.6</a>. The primary purpose of Content-Language is to allow a user to identify and differentiate representations according to the
    28202820         user's own preferred language. Thus, if the body content is intended only for a Danish-literate audience, the appropriate
    28212821         field is
    … …  
    28832883      </p>
    28842884      <div id="rfc.figure.u.41"></div><pre class="inline"><span id="rfc.iref.g.46"></span>  <a href="#header.content-type" class="smpl">Content-Type</a> = <a href="#media.types" class="smpl">media-type</a>
    2885 </pre><p id="rfc.section.10.9.p.3">Media types are defined in <a href="#media.types" title="Media Types">Section&nbsp;8.5</a>. An example of the field is
     2885</pre><p id="rfc.section.10.9.p.3">Media types are defined in <a href="#media.types" title="Media Types">Section&nbsp;9.5</a>. An example of the field is
    28862886      </p>
    28872887      <div id="rfc.figure.u.42"></div><pre class="text">  Content-Type: text/html; charset=ISO-8859-4
    … …  
    28922892      <h2 id="rfc.section.10.10"><a href="#rfc.section.10.10">10.10</a>&nbsp;<a id="header.date" href="#header.date">Date</a></h2>
    28932893      <p id="rfc.section.10.10.p.1">The "Date" header field represents the date and time at which the message was originated, having the same semantics as the
    2894          Origination Date Field (orig-date) defined in <a href="http://tools.ietf.org/html/rfc5322#section-3.6.1">Section 3.6.1</a> of <a href="#RFC5322" id="rfc.xref.RFC5322.2"><cite title="Internet Message Format">[RFC5322]</cite></a>. The field value is an HTTP-date, as defined in <a href="#http.date" title="Date/Time Formats">Section&nbsp;8.1</a>; it <em class="bcp14">MUST</em> be sent in rfc1123-date format.
     2894         Origination Date Field (orig-date) defined in <a href="http://tools.ietf.org/html/rfc5322#section-3.6.1">Section 3.6.1</a> of <a href="#RFC5322" id="rfc.xref.RFC5322.2"><cite title="Internet Message Format">[RFC5322]</cite></a>. The field value is an HTTP-date, as defined in <a href="#http.date" title="Date/Time Formats">Section&nbsp;9.1</a>; it <em class="bcp14">MUST</em> be sent in rfc1123-date format.
    28952895      </p>
    28962896      <div id="rfc.figure.u.43"></div><pre class="inline"><span id="rfc.iref.g.47"></span>  <a href="#header.date" class="smpl">Date</a> = <a href="#http.date" class="smpl">HTTP-date</a>
    … …  
    30003000      <div id="rfc.iref.h.15"></div>
    30013001      <h2 id="rfc.section.10.14"><a href="#rfc.section.10.14">10.14</a>&nbsp;<a id="header.max-forwards" href="#header.max-forwards">Max-Forwards</a></h2>
    3002       <p id="rfc.section.10.14.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
     3002      <p id="rfc.section.10.14.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
    30033003         to trace a request which appears to be failing or looping mid-chain.
    30043004      </p>
    … …  
    30483048      <h2 id="rfc.section.10.17"><a href="#rfc.section.10.17">10.17</a>&nbsp;<a id="header.server" href="#header.server">Server</a></h2>
    30493049      <p id="rfc.section.10.17.p.1">The "Server" header field contains information about the software used by the origin server to handle the request.</p>
    3050       <p id="rfc.section.10.17.p.2">The field can contain multiple product tokens (<a href="#product.tokens" title="Product Tokens">Section&nbsp;8.2</a>) and comments (<a href="p1-messaging.html#header.fields" title="Header Fields">Section 3.2</a> of <a href="#Part1" id="rfc.xref.Part1.29"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>) identifying the server and any significant subproducts. The product tokens are listed in order of their significance for
     3050      <p id="rfc.section.10.17.p.2">The field can contain multiple product tokens (<a href="#product.tokens" title="Product Tokens">Section&nbsp;9.2</a>) and comments (<a href="p1-messaging.html#header.fields" title="Header Fields">Section 3.2</a> of <a href="#Part1" id="rfc.xref.Part1.29"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>) identifying the server and any significant subproducts. The product tokens are listed in order of their significance for
    30513051         identifying the application.
    30523052      </p>
    … …  
    30703070         user agent limitations.
    30713071      </p>
    3072       <p id="rfc.section.10.18.p.3">The field can contain multiple product tokens (<a href="#product.tokens" title="Product Tokens">Section&nbsp;8.2</a>) and comments (<a href="p1-messaging.html#header.fields" title="Header Fields">Section 3.2</a> of <a href="#Part1" id="rfc.xref.Part1.31"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>) identifying the agent and its significant subproducts. By convention, the product tokens are listed in order of their significance
     3072      <p id="rfc.section.10.18.p.3">The field can contain multiple product tokens (<a href="#product.tokens" title="Product Tokens">Section&nbsp;9.2</a>) and comments (<a href="p1-messaging.html#header.fields" title="Header Fields">Section 3.2</a> of <a href="#Part1" id="rfc.xref.Part1.31"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>) identifying the agent and its significant subproducts. By convention, the product tokens are listed in order of their significance
    30733073         for identifying the application.
    30743074      </p>
    … …  
    30863086</pre><h1 id="rfc.section.11"><a href="#rfc.section.11">11.</a>&nbsp;<a id="IANA.considerations" href="#IANA.considerations">IANA Considerations</a></h1>
    30873087      <h2 id="rfc.section.11.1"><a href="#rfc.section.11.1">11.1</a>&nbsp;<a id="method.registry" href="#method.registry">Method Registry</a></h2>
    3088       <p id="rfc.section.11.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;.
     3088      <p id="rfc.section.11.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;.
    30893089      </p>
    30903090      <h3 id="rfc.section.11.1.1"><a href="#rfc.section.11.1.1">11.1.1</a>&nbsp;<a id="method.procedure" href="#method.procedure">Procedure</a></h3>
    … …  
    30923092      </p>
    30933093      <ul>
    3094          <li>Method Name (see <a href="#methods" title="Request Methods">Section&nbsp;4</a>)
    3095          </li>
    3096          <li>Safe ("yes" or "no", see <a href="#safe.methods" title="Safe Methods">Section&nbsp;4.2.1</a>)
    3097          </li>
    3098          <li>Idempotent ("yes" or "no", see <a href="#idempotent.methods" title="Idempotent Methods">Section&nbsp;4.2.2</a>)
     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>)
    30993099         </li>
    31003100         <li>Pointer to specification text</li>
    … …  
    31123112         a Content-Length header field with a value of "0".
    31133113      </p>
    3114       <p id="rfc.section.11.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 request body if any is present in the request. If a method is cacheable,
     3114      <p id="rfc.section.11.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 request body if any is present in the request. If a method is cacheable,
    31153115         the method definition ought to describe how, and under what conditions, a cache can store a response and use it to satisfy
    31163116         a subsequent request.
    … …  
    31343134                  <td class="left">no</td>
    31353135                  <td class="left">no</td>
    3136                   <td class="left"> <a href="#CONNECT" id="rfc.xref.CONNECT.2" title="CONNECT">Section&nbsp;4.3.6</a>
     3136                  <td class="left"> <a href="#CONNECT" id="rfc.xref.CONNECT.2" title="CONNECT">Section&nbsp;5.3.6</a>
    31373137                  </td>
    31383138               </tr>
    … …  
    31413141                  <td class="left">no</td>
    31423142                  <td class="left">yes</td>
    3143                   <td class="left"> <a href="#DELETE" id="rfc.xref.DELETE.2" title="DELETE">Section&nbsp;4.3.5</a>
     3143                  <td class="left"> <a href="#DELETE" id="rfc.xref.DELETE.2" title="DELETE">Section&nbsp;5.3.5</a>
    31443144                  </td>
    31453145               </tr>
    … …  
    31483148                  <td class="left">yes</td>
    31493149                  <td class="left">yes</td>
    3150                   <td class="left"> <a href="#GET" id="rfc.xref.GET.2" title="GET">Section&nbsp;4.3.1</a>
     3150                  <td class="left"> <a href="#GET" id="rfc.xref.GET.2" title="GET">Section&nbsp;5.3.1</a>
    31513151                  </td>
    31523152               </tr>
    … …  
    31553155                  <td class="left">yes</td>
    31563156                  <td class="left">yes</td>
    3157                   <td class="left"> <a href="#HEAD" id="rfc.xref.HEAD.2" title="HEAD">Section&nbsp;4.3.2</a>
     3157                  <td class="left"> <a href="#HEAD" id="rfc.xref.HEAD.2" title="HEAD">Section&nbsp;5.3.2</a>
    31583158                  </td>
    31593159               </tr>
    … …  
    31623162                  <td class="left">yes</td>
    31633163                  <td class="left">yes</td>
    3164                   <td class="left"> <a href="#OPTIONS" id="rfc.xref.OPTIONS.3" title="OPTIONS">Section&nbsp;4.3.7</a>
     3164                  <td class="left"> <a href="#OPTIONS" id="rfc.xref.OPTIONS.3" title="OPTIONS">Section&nbsp;5.3.7</a>
    31653165                  </td>
    31663166               </tr>
    … …  
    31693169                  <td class="left">no</td>
    31703170                  <td class="left">no</td>
    3171                   <td class="left"> <a href="#POST" id="rfc.xref.POST.2" title="POST">Section&nbsp;4.3.3</a>
     3171                  <td class="left"> <a href="#POST" id="rfc.xref.POST.2" title="POST">Section&nbsp;5.3.3</a>
    31723172                  </td>
    31733173               </tr>
    … …  
    31763176                  <td class="left">no</td>
    31773177                  <td class="left">yes</td>
    3178                   <td class="left"> <a href="#PUT" id="rfc.xref.PUT.2" title="PUT">Section&nbsp;4.3.4</a>
     3178                  <td class="left"> <a href="#PUT" id="rfc.xref.PUT.2" title="PUT">Section&nbsp;5.3.4</a>
    31793179                  </td>
    31803180               </tr>
    … …  
    31833183                  <td class="left">yes</td>
    31843184                  <td class="left">yes</td>
    3185                   <td class="left"> <a href="#TRACE" id="rfc.xref.TRACE.3" title="TRACE">Section&nbsp;4.3.8</a>
     3185                  <td class="left"> <a href="#TRACE" id="rfc.xref.TRACE.3" title="TRACE">Section&nbsp;5.3.8</a>
    31863186                  </td>
    31873187               </tr>
    … …  
    31903190      </div>
    31913191      <h2 id="rfc.section.11.2"><a href="#rfc.section.11.2">11.2</a>&nbsp;<a id="status.code.registry" href="#status.code.registry">Status Code Registry</a></h2>
    3192       <p id="rfc.section.11.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;.
     3192      <p id="rfc.section.11.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;.
    31933193      </p>
    31943194      <p id="rfc.section.11.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>.
    … …  
    32093209         (e.g., those that are required, those that modify the semantics of the response).
    32103210      </p>
    3211       <p id="rfc.section.11.2.2.p.4">New HTTP 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 response body, although they can mandate
     3211      <p id="rfc.section.11.2.2.p.4">New HTTP 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 response body, although they can mandate
    32123212         a zero-length response body. They can require the presence of one or more particular HTTP response header field(s).
    32133213      </p>
    … …  
    32303230                  <td class="left">100</td>
    32313231                  <td class="left">Continue</td>
    3232                   <td class="left"> <a href="#status.100" id="rfc.xref.status.100.2" title="100 Continue">Section&nbsp;6.2.1</a>
     3232                  <td class="left"> <a href="#status.100" id="rfc.xref.status.100.2" title="100 Continue">Section&nbsp;7.2.1</a>
    32333233                  </td>
    32343234               </tr>
    … …  
    32363236                  <td class="left">101</td>
    32373237                  <td class="left">Switching Protocols</td>
    3238                   <td class="left"> <a href="#status.101" id="rfc.xref.status.101.2" title="101 Switching Protocols">Section&nbsp;6.2.2</a>
     3238                  <td class="left"> <a href="#status.101" id="rfc.xref.status.101.2" title="101 Switching Protocols">Section&nbsp;7.2.2</a>
    32393239                  </td>
    32403240               </tr>
    … …  
    32423242                  <td class="left">200</td>
    32433243                  <td class="left">OK</td>
    3244                   <td class="left"> <a href="#status.200" id="rfc.xref.status.200.2" title="200 OK">Section&nbsp;6.3.1</a>
     3244                  <td class="left"> <a href="#status.200" id="rfc.xref.status.200.2" title="200 OK">Section&nbsp;7.3.1</a>
    32453245                  </td>
    32463246               </tr>
    … …  
    32483248                  <td class="left">201</td>
    32493249                  <td class="left">Created</td>
    3250                   <td class="left"> <a href="#status.201" id="rfc.xref.status.201.2" title="201 Created">Section&nbsp;6.3.2</a>
     3250                  <td class="left"> <a href="#status.201" id="rfc.xref.status.201.2" title="201 Created">Section&nbsp;7.3.2</a>
    32513251                  </td>
    32523252               </tr>
    … …  
    32543254                  <td class="left">202</td>
    32553255                  <td class="left">Accepted</td>
    3256                   <td class="left"> <a href="#status.202" id="rfc.xref.status.202.2" title="202 Accepted">Section&nbsp;6.3.3</a>
     3256                  <td class="left"> <a href="#status.202" id="rfc.xref.status.202.2" title="202 Accepted">Section&nbsp;7.3.3</a>
    32573257                  </td>
    32583258               </tr>
    … …  
    32603260                  <td class="left">203</td>
    32613261                  <td class="left">Non-Authoritative Information</td>
    3262                   <td class="left"> <a href="#status.203" id="rfc.xref.status.203.2" title="203 Non-Authoritative Information">Section&nbsp;6.3.4</a>
     3262                  <td class="left"> <a href="#status.203" id="rfc.xref.status.203.2" title="203 Non-Authoritative Information">Section&nbsp;7.3.4</a>
    32633263                  </td>
    32643264               </tr>
    … …  
    32663266                  <td class="left">204</td>
    32673267                  <td class="left">No Content</td>
    3268                   <td class="left"> <a href="#status.204" id="rfc.xref.status.204.2" title="204 No Content">Section&nbsp;6.3.5</a>
     3268                  <td class="left"> <a href="#status.204" id="rfc.xref.status.204.2" title="204 No Content">Section&nbsp;7.3.5</a>
    32693269                  </td>
    32703270               </tr>
    … …  
    32723272                  <td class="left">205</td>
    32733273                  <td class="left">Reset Content</td>
    3274                   <td class="left"> <a href="#status.205" id="rfc.xref.status.205.2" title="205 Reset Content">Section&nbsp;6.3.6</a>
     3274                  <td class="left"> <a href="#status.205" id="rfc.xref.status.205.2" title="205 Reset Content">Section&nbsp;7.3.6</a>
    32753275                  </td>
    32763276               </tr>
    … …  
    32783278                  <td class="left">300</td>
    32793279                  <td class="left">Multiple Choices</td>
    3280                   <td class="left"> <a href="#status.300" id="rfc.xref.status.300.2" title="300 Multiple Choices">Section&nbsp;6.4.1</a>
     3280                  <td class="left"> <a href="#status.300" id="rfc.xref.status.300.2" title="300 Multiple Choices">Section&nbsp;7.4.1</a>
    32813281                  </td>
    32823282               </tr>
    … …  
    32843284                  <td class="left">301</td>
    32853285                  <td class="left">Moved Permanently</td>
    3286                   <td class="left"> <a href="#status.301" id="rfc.xref.status.301.2" title="301 Moved Permanently">Section&nbsp;6.4.2</a>
     3286                  <td class="left"> <a href="#status.301" id="rfc.xref.status.301.2" title="301 Moved Permanently">Section&nbsp;7.4.2</a>
    32873287                  </td>
    32883288               </tr>
    … …  
    32903290                  <td class="left">302</td>
    32913291                  <td class="left">Found</td>
    3292                   <td class="left"> <a href="#status.302" id="rfc.xref.status.302.2" title="302 Found">Section&nbsp;6.4.3</a>
     3292                  <td class="left"> <a href="#status.302" id="rfc.xref.status.302.2" title="302 Found">Section&nbsp;7.4.3</a>
    32933293                  </td>
    32943294               </tr>
    … …  
    32963296                  <td class="left">303</td>
    32973297                  <td class="left">See Other</td>
    3298                   <td class="left"> <a href="#status.303" id="rfc.xref.status.303.2" title="303 See Other">Section&nbsp;6.4.4</a>
     3298                  <td class="left"> <a href="#status.303" id="rfc.xref.status.303.2" title="303 See Other">Section&nbsp;7.4.4</a>
    32993299                  </td>
    33003300               </tr>
    … …  
    33023302                  <td class="left">305</td>
    33033303                  <td class="left">Use Proxy</td>
    3304                   <td class="left"> <a href="#status.305" id="rfc.xref.status.305.2" title="305 Use Proxy">Section&nbsp;6.4.5</a>
     3304                  <td class="left"> <a href="#status.305" id="rfc.xref.status.305.2" title="305 Use Proxy">Section&nbsp;7.4.5</a>
    33053305                  </td>
    33063306               </tr>
    … …  
    33083308                  <td class="left">306</td>
    33093309                  <td class="left">(Unused)</td>
    3310                   <td class="left"> <a href="#status.306" id="rfc.xref.status.306.1" title="306 (Unused)">Section&nbsp;6.4.6</a>
     3310                  <td class="left"> <a href="#status.306" id="rfc.xref.status.306.1" title="306 (Unused)">Section&nbsp;7.4.6</a>
    33113311                  </td>
    33123312               </tr>
    … …  
    33143314                  <td class="left">307</td>
    33153315                  <td class="left">Temporary Redirect</td>
    3316                   <td class="left"> <a href="#status.307" id="rfc.xref.status.307.2" title="307 Temporary Redirect">Section&nbsp;6.4.7</a>
     3316                  <td class="left"> <a href="#status.307" id="rfc.xref.status.307.2" title="307 Temporary Redirect">Section&nbsp;7.4.7</a>
    33173317                  </td>
    33183318               </tr>
    … …  
    33203320                  <td class="left">400</td>
    33213321                  <td class="left">Bad Request</td>
    3322                   <td class="left"> <a href="#status.400" id="rfc.xref.status.400.2" title="400 Bad Request">Section&nbsp;6.5.1</a>
     3322                  <td class="left"> <a href="#status.400" id="rfc.xref.status.400.2" title="400 Bad Request">Section&nbsp;7.5.1</a>
    33233323                  </td>
    33243324               </tr>
    … …  
    33263326                  <td class="left">402</td>
    33273327                  <td class="left">Payment Required</td>
    3328                   <td class="left"> <a href="#status.402" id="rfc.xref.status.402.2" title="402 Payment Required">Section&nbsp;6.5.2</a>
     3328                  <td class="left"> <a href="#status.402" id="rfc.xref.status.402.2" title="402 Payment Required">Section&nbsp;7.5.2</a>
    33293329                  </td>
    33303330               </tr>
    … …  
    33323332                  <td class="left">403</td>
    33333333                  <td class="left">Forbidden</td>
    3334                   <td class="left"> <a href="#status.403" id="rfc.xref.status.403.2" title="403 Forbidden">Section&nbsp;6.5.3</a>
     3334                  <td class="left"> <a href="#status.403" id="rfc.xref.status.403.2" title="403 Forbidden">Section&nbsp;7.5.3</a>
    33353335                  </td>
    33363336               </tr>
    … …  
    33383338                  <td class="left">404</td>
    33393339                  <td class="left">Not Found</td>
    3340                   <td class="left"> <a href="#status.404" id="rfc.xref.status.404.2" title="404 Not Found">Section&nbsp;6.5.4</a>
     3340                  <td class="left"> <a href="#status.404" id="rfc.xref.status.404.2" title="404 Not Found">Section&nbsp;7.5.4</a>
    33413341                  </td>
    33423342               </tr>
    … …  
    33443344                  <td class="left">405</td>
    33453345                  <td class="left">Method Not Allowed</td>
    3346                   <td class="left"> <a href="#status.405" id="rfc.xref.status.405.2" title="405 Method Not Allowed">Section&nbsp;6.5.5</a>
     3346                  <td class="left"> <a href="#status.405" id="rfc.xref.status.405.2" title="405 Method Not Allowed">Section&nbsp;7.5.5</a>
    33473347                  </td>
    33483348               </tr>
    … …  
    33503350                  <td class="left">406</td>
    33513351                  <td class="left">Not Acceptable</td>
    3352                   <td class="left"> <a href="#status.406" id="rfc.xref.status.406.2" title="406 Not Acceptable">Section&nbsp;6.5.6</a>
     3352                  <td class="left"> <a href="#status.406" id="rfc.xref.status.406.2" title="406 Not Acceptable">Section&nbsp;7.5.6</a>
    33533353                  </td>
    33543354               </tr>
    … …  
    33563356                  <td class="left">408</td>
    33573357                  <td class="left">Request Timeout</td>
    3358                   <td class="left"> <a href="#status.408" id="rfc.xref.status.408.2" title="408 Request Timeout">Section&nbsp;6.5.7</a>
     3358                  <td class="left"> <a href="#status.408" id="rfc.xref.status.408.2" title="408 Request Timeout">Section&nbsp;7.5.7</a>
    33593359                  </td>
    33603360               </tr>
    … …  
    33623362                  <td class="left">409</td>
    33633363                  <td class="left">Conflict</td>
    3364                   <td class="left"> <a href="#status.409" id="rfc.xref.status.409.2" title="409 Conflict">Section&nbsp;6.5.8</a>
     3364                  <td class="left"> <a href="#status.409" id="rfc.xref.status.409.2" title="409 Conflict">Section&nbsp;7.5.8</a>
    33653365                  </td>
    33663366               </tr>
    … …  
    33683368                  <td class="left">410</td>
    33693369                  <td class="left">Gone</td>
    3370                   <td class="left"> <a href="#status.410" id="rfc.xref.status.410.2" title="410 Gone">Section&nbsp;6.5.9</a>
     3370                  <td class="left"> <a href="#status.410" id="rfc.xref.status.410.2" title="410 Gone">Section&nbsp;7.5.9</a>
    33713371                  </td>
    33723372               </tr>
    … …  
    33743374                  <td class="left">411</td>
    33753375                  <td class="left">Length Required</td>
    3376                   <td class="left"> <a href="#status.411" id="rfc.xref.status.411.2" title="411 Length Required">Section&nbsp;6.5.10</a>
     3376                  <td class="left"> <a href="#status.411" id="rfc.xref.status.411.2" title="411 Length Required">Section&nbsp;7.5.10</a>
    33773377                  </td>
    33783378               </tr>
    … …  
    33803380                  <td class="left">413</td>
    33813381                  <td class="left">Request Representation Too Large</td>
    3382                   <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>
     3382                  <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>
    33833383                  </td>
    33843384               </tr>
    … …  
    33863386                  <td class="left">414</td>
    33873387                  <td class="left">URI Too Long</td>
    3388                   <td class="left"> <a href="#status.414" id="rfc.xref.status.414.2" title="414 URI Too Long">Section&nbsp;6.5.12</a>
     3388                  <td class="left"> <a href="#status.414" id="rfc.xref.status.414.2" title="414 URI Too Long">Section&nbsp;7.5.12</a>
    33893389                  </td>
    33903390               </tr>
    … …  
    33923392                  <td class="left">415</td>
    33933393                  <td class="left">Unsupported Media Type</td>
    3394                   <td class="left"> <a href="#status.415" id="rfc.xref.status.415.2" title="415 Unsupported Media Type">Section&nbsp;6.5.13</a>
     3394                  <td class="left"> <a href="#status.415" id="rfc.xref.status.415.2" title="415 Unsupported Media Type">Section&nbsp;7.5.13</a>
    33953395                  </td>
    33963396               </tr>
    … …  
    33983398                  <td class="left">417</td>
    33993399                  <td class="left">Expectation Failed</td>
    3400                   <td class="left"> <a href="#status.417" id="rfc.xref.status.417.2" title="417 Expectation Failed">Section&nbsp;6.5.14</a>
     3400                  <td class="left"> <a href="#status.417" id="rfc.xref.status.417.2" title="417 Expectation Failed">Section&nbsp;7.5.14</a>
    34013401                  </td>
    34023402               </tr>
    … …  
    34043404                  <td class="left">426</td>
    34053405                  <td class="left">Upgrade Required</td>
    3406                   <td class="left"> <a href="#status.426" id="rfc.xref.status.426.2" title="426 Upgrade Required">Section&nbsp;6.5.15</a>
     3406                  <td class="left"> <a href="#status.426" id="rfc.xref.status.426.2" title="426 Upgrade Required">Section&nbsp;7.5.15</a>
    34073407                  </td>
    34083408               </tr>
    … …  
    34103410                  <td class="left">500</td>
    34113411                  <td class="left">Internal Server Error</td>
    3412                   <td class="left"> <a href="#status.500" id="rfc.xref.status.500.2" title="500 Internal Server Error">Section&nbsp;6.6.1</a>
     3412                  <td class="left"> <a href="#status.500" id="rfc.xref.status.500.2" title="500 Internal Server Error">Section&nbsp;7.6.1</a>
    34133413                  </td>
    34143414               </tr>
    … …  
    34163416                  <td class="left">501</td>
    34173417                  <td class="left">Not Implemented</td>
    3418                   <td class="left"> <a href="#status.501" id="rfc.xref.status.501.2" title="501 Not Implemented">Section&nbsp;6.6.2</a>
     3418                  <td class="left"> <a href="#status.501" id="rfc.xref.status.501.2" title="501 Not Implemented">Section&nbsp;7.6.2</a>
    34193419                  </td>
    34203420               </tr>
    … …  
    34223422                  <td class="left">502</td>
    34233423                  <td class="left">Bad Gateway</td>
    3424                   <td class="left"> <a href="#status.502" id="rfc.xref.status.502.2" title="502 Bad Gateway">Section&nbsp;6.6.3</a>
     3424                  <td class="left"> <a href="#status.502" id="rfc.xref.status.502.2" title="502 Bad Gateway">Section&nbsp;7.6.3</a>
    34253425                  </td>
    34263426               </tr>
    … …  
    34283428                  <td class="left">503</td>
    34293429                  <td class="left">Service Unavailable</td>
    3430                   <td class="left"> <a href="#status.503" id="rfc.xref.status.503.2" title="503 Service Unavailable">Section&nbsp;6.6.4</a>
     3430                  <td class="left"> <a href="#status.503" id="rfc.xref.status.503.2" title="503 Service Unavailable">Section&nbsp;7.6.4</a>
    34313431                  </td>
    34323432               </tr>
    … …  
    34343434                  <td class="left">504</td>
    34353435                  <td class="left">Gateway Timeout</td>
    3436                   <td class="left"> <a href="#status.504" id="rfc.xref.status.504.2" title="504 Gateway Timeout">Section&nbsp;6.6.5</a>
     3436                  <td class="left"> <a href="#status.504" id="rfc.xref.status.504.2" title="504 Gateway Timeout">Section&nbsp;7.6.5</a>
    34373437                  </td>
    34383438               </tr>
    … …  
    34403440                  <td class="left">505</td>
    34413441                  <td class="left">HTTP Version Not Supported</td>
    3442                   <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>
     3442                  <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>
    34433443                  </td>
    34443444               </tr>
    … …  
    34743474      <p id="rfc.section.11.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;10.9</a>). Allowing both unquoted (token) and quoted (quoted-string) syntax for the parameter value enables recipients to use existing
    34753475         parser components. When allowing both forms, the meaning of a parameter value ought to be independent of the syntax used for
    3476          it (for an example, see the notes on parameter handling for media types in <a href="#media.types" title="Media Types">Section&nbsp;8.5</a>).
     3476         it (for an example, see the notes on parameter handling for media types in <a href="#media.types" title="Media Types">Section&nbsp;9.5</a>).
    34773477      </p>
    34783478      <p id="rfc.section.11.3.1.p.9">Authors of specifications defining new header fields are advised to consider documenting: </p>
    … …  
    37543754         user.
    37553755      </p>
    3756       <p id="rfc.section.12.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
     3756      <p id="rfc.section.12.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
    37573757         to collect data from the client.
    37583758      </p>
    … …  
    40314031      </p>
    40324032      <h2 id="rfc.section.A.2"><a href="#rfc.section.A.2">A.2</a>&nbsp;<a id="conversion.to.canonical.form" href="#conversion.to.canonical.form">Conversion to Canonical Form</a></h2>
    4033       <p id="rfc.section.A.2.p.1">MIME requires that an Internet mail body-part be converted to canonical form prior to being transferred, as described in <a href="http://tools.ietf.org/html/rfc2049#section-4">Section 4</a> of <a href="#RFC2049" id="rfc.xref.RFC2049.1"><cite title="Multipurpose Internet Mail Extensions (MIME) Part Five: Conformance Criteria and Examples">[RFC2049]</cite></a>. <a href="#canonicalization.and.text.defaults" title="Canonicalization and Text Defaults">Section&nbsp;8.5.1</a> of this document describes the forms allowed for subtypes of the "text" media type when transmitted over HTTP. <a href="#RFC2046" id="rfc.xref.RFC2046.4"><cite title="Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types">[RFC2046]</cite></a> requires that content with a type of "text" represent line breaks as CRLF and forbids the use of CR or LF outside of line
     4033      <p id="rfc.section.A.2.p.1">MIME requires that an Internet mail body-part be converted to canonical form prior to being transferred, as described in <a href="http://tools.ietf.org/html/rfc2049#section-4">Section 4</a> of <a href="#RFC2049" id="rfc.xref.RFC2049.1"><cite title="Multipurpose Internet Mail Extensions (MIME) Part Five: Conformance Criteria and Examples">[RFC2049]</cite></a>. <a href="#canonicalization.and.text.defaults" title="Canonicalization and Text Defaults">Section&nbsp;9.5.1</a> of this document describes the forms allowed for subtypes of the "text" media type when transmitted over HTTP. <a href="#RFC2046" id="rfc.xref.RFC2046.4"><cite title="Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types">[RFC2046]</cite></a> requires that content with a type of "text" represent line breaks as CRLF and forbids the use of CR or LF outside of line
    40344034         break sequences. HTTP allows CRLF, bare CR, and bare LF to indicate a line break within text content when a message is transmitted
    40354035         over HTTP.
    40364036      </p>
    4037       <p id="rfc.section.A.2.p.2">Where it is possible, a proxy or gateway from HTTP to a strict MIME environment <em class="bcp14">SHOULD</em> translate all line breaks within the text media types described in <a href="#canonicalization.and.text.defaults" title="Canonicalization and Text Defaults">Section&nbsp;8.5.1</a> of this document to the RFC 2049 canonical form of CRLF. Note, however, that this might be complicated by the presence of
     4037      <p id="rfc.section.A.2.p.2">Where it is possible, a proxy or gateway from HTTP to a strict MIME environment <em class="bcp14">SHOULD</em> translate all line breaks within the text media types described in <a href="#canonicalization.and.text.defaults" title="Canonicalization and Text Defaults">Section&nbsp;9.5.1</a> of this document to the RFC 2049 canonical form of CRLF. Note, however, that this might be complicated by the presence of
    40384038         a <a href="#header.content-encoding" class="smpl">Content-Encoding</a> and by the fact that HTTP allows the use of some character encodings which do not use octets 13 and 10 to represent CR and
    40394039         LF, respectively, as is the case for some multi-byte character encodings.
    … …  
    40434043      </p>
    40444044      <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>
    4045       <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</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.
     4045      <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;9.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.
    40464046      </p>
    40474047      <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>
    … …  
    40634063      <p id="rfc.section.A.6.p.1">HTTP implementations which share code with MHTML <a href="#RFC2557" id="rfc.xref.RFC2557.2"><cite title="MIME Encapsulation of Aggregate Documents, such as HTML (MHTML)">[RFC2557]</cite></a> implementations need to be aware of MIME line length limitations. Since HTTP does not have this limitation, HTTP does not
    40644064         fold long lines. MHTML messages being transported by HTTP follow all conventions of MHTML, including line length limitations
    4065          and folding, canonicalization, etc., since HTTP transports all message-bodies as payload (see <a href="#multipart.types" title="Multipart Types">Section&nbsp;8.5.2</a>) and does not interpret the content or any MIME header lines that might be contained therein.
     4065         and folding, canonicalization, etc., since HTTP transports all message-bodies as payload (see <a href="#multipart.types" title="Multipart Types">Section&nbsp;9.5.2</a>) and does not interpret the content or any MIME header lines that might be contained therein.
    40664066      </p>
    40674067      <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a>&nbsp;<a id="additional.features" href="#additional.features">Additional Features</a></h1>
    … …  
    40764076      <p id="rfc.section.C.p.1">Introduce Method Registry. (<a href="#method.registry" title="Method Registry">Section&nbsp;11.1</a>)
    40774077      </p>
    4078       <p id="rfc.section.C.p.2">Clarify definition of POST. (<a href="#POST" id="rfc.xref.POST.3" title="POST">Section&nbsp;4.3.3</a>)
    4079       </p>
    4080       <p id="rfc.section.C.p.3">Remove requirement to handle all Content-* header fields; ban use of <a href="p5-range.html#header.content-range" class="smpl">Content-Range</a> with PUT. (<a href="#PUT" id="rfc.xref.PUT.3" title="PUT">Section&nbsp;4.3.4</a>)
    4081       </p>
    4082       <p id="rfc.section.C.p.4">Take over definition of CONNECT method from <a href="#RFC2817" id="rfc.xref.RFC2817.2"><cite title="Upgrading to TLS Within HTTP/1.1">[RFC2817]</cite></a>. (<a href="#CONNECT" id="rfc.xref.CONNECT.3" title="CONNECT">Section&nbsp;4.3.6</a>)
     4078      <p id="rfc.section.C.p.2">Clarify definition of POST. (<a href="#POST" id="rfc.xref.POST.3" title="POST">Section&nbsp;5.3.3</a>)
     4079      </p>
     4080      <p id="rfc.section.C.p.3">Remove requirement to handle all Content-* header fields; ban use of <a href="p5-range.html#header.content-range" class="smpl">Content-Range</a> with PUT. (<a href="#PUT" id="rfc.xref.PUT.3" title="PUT">Section&nbsp;5.3.4</a>)
     4081      </p>
     4082      <p id="rfc.section.C.p.4">Take over definition of CONNECT method from <a href="#RFC2817" id="rfc.xref.RFC2817.2"><cite title="Upgrading to TLS Within HTTP/1.1">[RFC2817]</cite></a>. (<a href="#CONNECT" id="rfc.xref.CONNECT.3" title="CONNECT">Section&nbsp;5.3.6</a>)
    40834083      </p>
    40844084      <p id="rfc.section.C.p.5">Take over the Status Code Registry, previously defined in <a href="http://tools.ietf.org/html/rfc2817#section-7.1">Section 7.1</a> of <a href="#RFC2817" id="rfc.xref.RFC2817.3"><cite title="Upgrading to TLS Within HTTP/1.1">[RFC2817]</cite></a>. (<a href="#status.code.registry" title="Status Code Registry">Section&nbsp;11.2</a>)
    40854085      </p>
    4086       <p id="rfc.section.C.p.6">Broadened the definition of <a href="#status.203" class="smpl">203 (Non-Authoritative Information)</a> to include cases of payload transformations as well. (<a href="#status.203" id="rfc.xref.status.203.3" title="203 Non-Authoritative Information">Section&nbsp;6.3.4</a>)
    4087       </p>
    4088       <p id="rfc.section.C.p.7">Status codes <a href="#status.301" class="smpl">301</a>, <a href="#status.302" class="smpl">302</a>, and <a href="#status.307" class="smpl">307</a>: removed the normative requirements on both response payloads and user interaction. (<a href="#status.3xx" id="rfc.xref.status.3xx.1" title="Redirection 3xx">Section&nbsp;6.4</a>)
     4086      <p id="rfc.section.C.p.6">Broadened the definition of <a href="#status.203" class="smpl">203 (Non-Authoritative Information)</a> to include cases of payload transformations as well. (<a href="#status.203" id="rfc.xref.status.203.3" title="203 Non-Authoritative Information">Section&nbsp;7.3.4</a>)
     4087      </p>
     4088      <p id="rfc.section.C.p.7">Status codes <a href="#status.301" class="smpl">301</a>, <a href="#status.302" class="smpl">302</a>, and <a href="#status.307" class="smpl">307</a>: removed the normative requirements on both response payloads and user interaction. (<a href="#status.3xx" id="rfc.xref.status.3xx.1" title="Redirection 3xx">Section&nbsp;7.4</a>)
    40894089      </p>
    40904090      <p id="rfc.section.C.p.8">Failed to consider that there are many other request methods that are safe to automatically redirect, and further that the
    40914091         user agent is able to make that determination based on the request method semantics. Furthermore, allow user agents to rewrite
    4092          the method from POST to GET for status codes <a href="#status.301" class="smpl">301</a> and <a href="#status.302" class="smpl">302</a>. (Sections <a href="#status.301" id="rfc.xref.status.301.3" title="301 Moved Permanently">6.4.2</a>, <a href="#status.302" id="rfc.xref.status.302.3" title="302 Found">6.4.3</a> and <a href="#status.307" id="rfc.xref.status.307.3" title="307 Temporary Redirect">6.4.7</a>)
     4092         the method from POST to GET for status codes <a href="#status.301" class="smpl">301</a> and <a href="#status.302" class="smpl">302</a>. (Sections <a href="#status.301" id="rfc.xref.status.301.3" title="301 Moved Permanently">7.4.2</a>, <a href="#status.302" id="rfc.xref.status.302.3" title="302 Found">7.4.3</a> and <a href="#status.307" id="rfc.xref.status.307.3" title="307 Temporary Redirect">7.4.7</a>)
    40934093      </p>
    40944094      <p id="rfc.section.C.p.9">Deprecate <a href="#status.305" class="smpl">305 (Use Proxy)</a> status code, because user agents did not implement it. It used to indicate that the target resource needs to be accessed through
    40954095         the proxy given by the <a href="#header.location" class="smpl">Location</a> field. The Location field gave the URI of the proxy. The recipient was expected to repeat this single request via the proxy.
    4096          (<a href="#status.305" id="rfc.xref.status.305.3" title="305 Use Proxy">Section&nbsp;6.4.5</a>)
    4097       </p>
    4098       <p id="rfc.section.C.p.10">Define status <a href="#status.426" class="smpl">426 (Upgrade Required)</a> (this was incorporated from <a href="#RFC2817" id="rfc.xref.RFC2817.4"><cite title="Upgrading to TLS Within HTTP/1.1">[RFC2817]</cite></a>). (<a href="#status.426" id="rfc.xref.status.426.3" title="426 Upgrade Required">Section&nbsp;6.5.15</a>)
     4096         (<a href="#status.305" id="rfc.xref.status.305.3" title="305 Use Proxy">Section&nbsp;7.4.5</a>)
     4097      </p>
     4098      <p id="rfc.section.C.p.10">Define status <a href="#status.426" class="smpl">426 (Upgrade Required)</a> (this was incorporated from <a href="#RFC2817" id="rfc.xref.RFC2817.4"><cite title="Upgrading to TLS Within HTTP/1.1">[RFC2817]</cite></a>). (<a href="#status.426" id="rfc.xref.status.426.3" title="426 Upgrade Required">Section&nbsp;7.5.15</a>)
    40994099      </p>
    41004100      <p id="rfc.section.C.p.11">Change ABNF productions for header fields to only define the field value. (<a href="#header.field.definitions" title="Header Field Definitions">Section&nbsp;10</a>)
    … …  
    41154115      <p id="rfc.section.C.p.17">In the description of the <a href="#header.server" class="smpl">Server</a> header field, the <a href="p1-messaging.html#header.via" class="smpl">Via</a> field was described as a SHOULD. The requirement was and is stated correctly in the description of the Via header field in <a href="p1-messaging.html#header.via" title="Via">Section 5.7</a> of <a href="#Part1" id="rfc.xref.Part1.46"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>. (<a href="#header.server" id="rfc.xref.header.server.4" title="Server">Section&nbsp;10.17</a>)
    41164116      </p>
    4117       <p id="rfc.section.C.p.18">Clarify contexts that charset is used in. (<a href="#character.sets" title="Character Encodings (charset)">Section&nbsp;8.3</a>)
     4117      <p id="rfc.section.C.p.18">Clarify contexts that charset is used in. (<a href="#character.sets" title="Character Encodings (charset)">Section&nbsp;9.3</a>)
    41184118      </p>
    41194119      <p id="rfc.section.C.p.19">Registration of Content Codings now requires IETF Review (<a href="#content.coding.registry" title="Content Coding Registry">Section&nbsp;11.4</a>)
    41204120      </p>
    41214121      <p id="rfc.section.C.p.20">Remove the default character encoding of "ISO-8859-1" for text media types; the default now is whatever the media type definition
    4122          says. (<a href="#canonicalization.and.text.defaults" title="Canonicalization and Text Defaults">Section&nbsp;8.5.1</a>)
     4122         says. (<a href="#canonicalization.and.text.defaults" title="Canonicalization and Text Defaults">Section&nbsp;9.5.1</a>)
    41234123      </p>
    41244124      <p id="rfc.section.C.p.21">Change ABNF productions for header fields to only define the field value. (<a href="#header.field.definitions" title="Header Field Definitions">Section&nbsp;10</a>)
    … …  
    48594859         <ul class="ind">
    48604860            <li><a id="rfc.index.1" href="#rfc.index.1"><b>1</b></a><ul>
    4861                   <li>100 Continue (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.100.1">6.1</a>, <a href="#rfc.iref.26"><b>6.2.1</b></a>, <a href="#rfc.xref.status.100.2">11.2.3</a></li>
     4861                  <li>100 Continue (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.100.1">7.1</a>, <a href="#rfc.iref.27"><b>7.2.1</b></a>, <a href="#rfc.xref.status.100.2">11.2.3</a></li>
    48624862                  <li>100-continue (expect value)&nbsp;&nbsp;<a href="#rfc.iref.142"><b>10.11</b></a></li>
    4863                   <li>101 Switching Protocols (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.101.1">6.1</a>, <a href="#rfc.iref.27"><b>6.2.2</b></a>, <a href="#rfc.xref.status.101.2">11.2.3</a></li>
    4864                   <li>1xx Informational (status code class)&nbsp;&nbsp;<a href="#rfc.iref.25"><b>6.2</b></a></li>
     4863                  <li>101 Switching Protocols (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.101.1">7.1</a>, <a href="#rfc.iref.28"><b>7.2.2</b></a>, <a href="#rfc.xref.status.101.2">11.2.3</a></li>
     4864                  <li>1xx Informational (status code class)&nbsp;&nbsp;<a href="#rfc.iref.26"><b>7.2</b></a></li>
    48654865               </ul>
    48664866            </li>
    48674867            <li><a id="rfc.index.2" href="#rfc.index.2"><b>2</b></a><ul>
    4868                   <li>200 OK (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.200.1">6.1</a>, <a href="#rfc.iref.29"><b>6.3.1</b></a>, <a href="#rfc.xref.status.200.2">11.2.3</a></li>
    4869                   <li>201 Created (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.201.1">6.1</a>, <a href="#rfc.iref.30"><b>6.3.2</b></a>, <a href="#rfc.xref.status.201.2">11.2.3</a></li>
    4870                   <li>202 Accepted (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.202.1">6.1</a>, <a href="#rfc.iref.31"><b>6.3.3</b></a>, <a href="#rfc.xref.status.202.2">11.2.3</a></li>
    4871                   <li>203 Non-Authoritative Information (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.203.1">6.1</a>, <a href="#rfc.iref.32"><b>6.3.4</b></a>, <a href="#rfc.xref.status.203.2">11.2.3</a>, <a href="#rfc.xref.status.203.3">C</a></li>
    4872                   <li>204 No Content (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.204.1">6.1</a>, <a href="#rfc.iref.33"><b>6.3.5</b></a>, <a href="#rfc.xref.status.204.2">11.2.3</a></li>
    4873                   <li>205 Reset Content (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.205.1">6.1</a>, <a href="#rfc.iref.34"><b>6.3.6</b></a>, <a href="#rfc.xref.status.205.2">11.2.3</a></li>
    4874                   <li>2xx Successful (status code class)&nbsp;&nbsp;<a href="#rfc.iref.28"><b>6.3</b></a></li>
     4868                  <li>200 OK (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.200.1">7.1</a>, <a href="#rfc.iref.30"><b>7.3.1</b></a>, <a href="#rfc.xref.status.200.2">11.2.3</a></li>
     4869                  <li>201 Created (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.201.1">7.1</a>, <a href="#rfc.iref.31"><b>7.3.2</b></a>, <a href="#rfc.xref.status.201.2">11.2.3</a></li>
     4870                  <li>202 Accepted (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.202.1">7.1</a>, <a href="#rfc.iref.32"><b>7.3.3</b></a>, <a href="#rfc.xref.status.202.2">11.2.3</a></li>
     4871                  <li>203 Non-Authoritative Information (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.203.1">7.1</a>, <a href="#rfc.iref.33"><b>7.3.4</b></a>, <a href="#rfc.xref.status.203.2">11.2.3</a>, <a href="#rfc.xref.status.203.3">C</a></li>
     4872                  <li>204 No Content (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.204.1">7.1</a>, <a href="#rfc.iref.34"><b>7.3.5</b></a>, <a href="#rfc.xref.status.204.2">11.2.3</a></li>
     4873                  <li>205 Reset Content (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.205.1">7.1</a>, <a href="#rfc.iref.35"><b>7.3.6</b></a>, <a href="#rfc.xref.status.205.2">11.2.3</a></li>
     4874                  <li>2xx Successful (status code class)&nbsp;&nbsp;<a href="#rfc.iref.29"><b>7.3</b></a></li>
    48754875               </ul>
    48764876            </li>
    48774877            <li><a id="rfc.index.3" href="#rfc.index.3"><b>3</b></a><ul>
    4878                   <li>300 Multiple Choices (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.300.1">6.1</a>, <a href="#rfc.iref.36"><b>6.4.1</b></a>, <a href="#rfc.xref.status.300.2">11.2.3</a></li>
    4879                   <li>301 Moved Permanently (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.301.1">6.1</a>, <a href="#rfc.iref.37"><b>6.4.2</b></a>, <a href="#rfc.xref.status.301.2">11.2.3</a>, <a href="#rfc.xref.status.301.3">C</a></li>
    4880                   <li>302 Found (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.302.1">6.1</a>, <a href="#rfc.iref.38"><b>6.4.3</b></a>, <a href="#rfc.xref.status.302.2">11.2.3</a>, <a href="#rfc.xref.status.302.3">C</a></li>
    4881                   <li>303 See Other (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.303.1">6.1</a>, <a href="#rfc.iref.39"><b>6.4.4</b></a>, <a href="#rfc.xref.status.303.2">11.2.3</a></li>
    4882                   <li>305 Use Proxy (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.305.1">6.1</a>, <a href="#rfc.iref.40"><b>6.4.5</b></a>, <a href="#rfc.xref.status.305.2">11.2.3</a>, <a href="#rfc.xref.status.305.3">C</a></li>
    4883                   <li>306 (Unused) (status code)&nbsp;&nbsp;<a href="#rfc.iref.41"><b>6.4.6</b></a>, <a href="#rfc.xref.status.306.1">11.2.3</a></li>
    4884                   <li>307 Temporary Redirect (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.307.1">6.1</a>, <a href="#rfc.iref.42"><b>6.4.7</b></a>, <a href="#rfc.xref.status.307.2">11.2.3</a>, <a href="#rfc.xref.status.307.3">C</a></li>
    4885                   <li>3xx Redirection (status code class)&nbsp;&nbsp;<a href="#rfc.iref.35"><b>6.4</b></a>, <a href="#rfc.xref.status.3xx.1">C</a></li>
     4878                  <li>300 Multiple Choices (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.300.1">7.1</a>, <a href="#rfc.iref.37"><b>7.4.1</b></a>, <a href="#rfc.xref.status.300.2">11.2.3</a></li>
     4879                  <li>301 Moved Permanently (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.301.1">7.1</a>, <a href="#rfc.iref.38"><b>7.4.2</b></a>, <a href="#rfc.xref.status.301.2">11.2.3</a>, <a href="#rfc.xref.status.301.3">C</a></li>
     4880                  <li>302 Found (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.302.1">7.1</a>, <a href="#rfc.iref.39"><b>7.4.3</b></a>, <a href="#rfc.xref.status.302.2">11.2.3</a>, <a href="#rfc.xref.status.302.3">C</a></li>
     4881                  <li>303 See Other (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.303.1">7.1</a>, <a href="#rfc.iref.40"><b>7.4.4</b></a>, <a href="#rfc.xref.status.303.2">11.2.3</a></li>
     4882                  <li>305 Use Proxy (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.305.1">7.1</a>, <a href="#rfc.iref.41"><b>7.4.5</b></a>, <a href="#rfc.xref.status.305.2">11.2.3</a>, <a href="#rfc.xref.status.305.3">C</a></li>
     4883                  <li>306 (Unused) (status code)&nbsp;&nbsp;<a href="#rfc.iref.42"><b>7.4.6</b></a>, <a href="#rfc.xref.status.306.1">11.2.3</a></li>
     4884                  <li>307 Temporary Redirect (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.307.1">7.1</a>, <a href="#rfc.iref.43"><b>7.4.7</b></a>, <a href="#rfc.xref.status.307.2">11.2.3</a>, <a href="#rfc.xref.status.307.3">C</a></li>
     4885                  <li>3xx Redirection (status code class)&nbsp;&nbsp;<a href="#rfc.iref.36"><b>7.4</b></a>, <a href="#rfc.xref.status.3xx.1">C</a></li>
    48864886               </ul>
    48874887            </li>
    48884888            <li><a id="rfc.index.4" href="#rfc.index.4"><b>4</b></a><ul>
    4889                   <li>400 Bad Request (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.400.1">6.1</a>, <a href="#rfc.iref.44"><b>6.5.1</b></a>, <a href="#rfc.xref.status.400.2">11.2.3</a></li>
    4890                   <li>402 Payment Required (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.402.1">6.1</a>, <a href="#rfc.iref.45"><b>6.5.2</b></a>, <a href="#rfc.xref.status.402.2">11.2.3</a></li>
    4891                   <li>403 Forbidden (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.403.1">6.1</a>, <a href="#rfc.iref.46"><b>6.5.3</b></a>, <a href="#rfc.xref.status.403.2">11.2.3</a></li>
    4892                   <li>404 Not Found (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.404.1">6.1</a>, <a href="#rfc.iref.47"><b>6.5.4</b></a>, <a href="#rfc.xref.status.404.2">11.2.3</a></li>
    4893                   <li>405 Method Not Allowed (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.405.1">6.1</a>, <a href="#rfc.iref.48"><b>6.5.5</b></a>, <a href="#rfc.xref.status.405.2">11.2.3</a></li>
    4894                   <li>406 Not Acceptable (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.406.1">6.1</a>, <a href="#rfc.iref.49"><b>6.5.6</b></a>, <a href="#rfc.xref.status.406.2">11.2.3</a></li>
    4895                   <li>408 Request Timeout (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.408.1">6.1</a>, <a href="#rfc.iref.50"><b>6.5.7</b></a>, <a href="#rfc.xref.status.408.2">11.2.3</a></li>
    4896                   <li>409 Conflict (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.409.1">6.1</a>, <a href="#rfc.iref.51"><b>6.5.8</b></a>, <a href="#rfc.xref.status.409.2">11.2.3</a></li>
    4897                   <li>410 Gone (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.410.1">6.1</a>, <a href="#rfc.iref.52"><b>6.5.9</b></a>, <a href="#rfc.xref.status.410.2">11.2.3</a></li>
    4898                   <li>411 Length Required (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.411.1">6.1</a>, <a href="#rfc.iref.53"><b>6.5.10</b></a>, <a href="#rfc.xref.status.411.2">11.2.3</a></li>
    4899                   <li>413 Request Representation Too Large (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.413.1">6.1</a>, <a href="#rfc.iref.54"><b>6.5.11</b></a>, <a href="#rfc.xref.status.413.2">11.2.3</a></li>
    4900                   <li>414 URI Too Long (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.414.1">6.1</a>, <a href="#rfc.iref.55"><b>6.5.12</b></a>, <a href="#rfc.xref.status.414.2">11.2.3</a></li>
    4901                   <li>415 Unsupported Media Type (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.415.1">6.1</a>, <a href="#rfc.iref.56"><b>6.5.13</b></a>, <a href="#rfc.xref.status.415.2">11.2.3</a></li>
    4902                   <li>417 Expectation Failed (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.417.1">6.1</a>, <a href="#rfc.iref.57"><b>6.5.14</b></a>, <a href="#rfc.xref.status.417.2">11.2.3</a></li>
    4903                   <li>426 Upgrade Required (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.426.1">6.1</a>, <a href="#rfc.iref.58"><b>6.5.15</b></a>, <a href="#rfc.xref.status.426.2">11.2.3</a>, <a href="#rfc.xref.status.426.3">C</a></li>
    4904                   <li>4xx Client Error (status code class)&nbsp;&nbsp;<a href="#rfc.iref.43"><b>6.5</b></a></li>
     4889                  <li>400 Bad Request (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.400.1">7.1</a>, <a href="#rfc.iref.45"><b>7.5.1</b></a>, <a href="#rfc.xref.status.400.2">11.2.3</a></li>
     4890                  <li>402 Payment Required (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.402.1">7.1</a>, <a href="#rfc.iref.46"><b>7.5.2</b></a>, <a href="#rfc.xref.status.402.2">11.2.3</a></li>
     4891                  <li>403 Forbidden (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.403.1">7.1</a>, <a href="#rfc.iref.47"><b>7.5.3</b></a>, <a href="#rfc.xref.status.403.2">11.2.3</a></li>
     4892                  <li>404 Not Found (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.404.1">7.1</a>, <a href="#rfc.iref.48"><b>7.5.4</b></a>, <a href="#rfc.xref.status.404.2">11.2.3</a></li>
     4893                  <li>405 Method Not Allowed (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.405.1">7.1</a>, <a href="#rfc.iref.49"><b>7.5.5</b></a>, <a href="#rfc.xref.status.405.2">11.2.3</a></li>
     4894                  <li>406 Not Acceptable (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.406.1">7.1</a>, <a href="#rfc.iref.50"><b>7.5.6</b></a>, <a href="#rfc.xref.status.406.2">11.2.3</a></li>
     4895                  <li>408 Request Timeout (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.408.1">7.1</a>, <a href="#rfc.iref.51"><b>7.5.7</b></a>, <a href="#rfc.xref.status.408.2">11.2.3</a></li>
     4896                  <li>409 Conflict (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.409.1">7.1</a>, <a href="#rfc.iref.52"><b>7.5.8</b></a>, <a href="#rfc.xref.status.409.2">11.2.3</a></li>
     4897                  <li>410 Gone (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.410.1">7.1</a>, <a href="#rfc.iref.53"><b>7.5.9</b></a>, <a href="#rfc.xref.status.410.2">11.2.3</a></li>
     4898                  <li>411 Length Required (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.411.1">7.1</a>, <a href="#rfc.iref.54"><b>7.5.10</b></a>, <a href="#rfc.xref.status.411.2">11.2.3</a></li>
     4899                  <li>413 Request Representation Too Large (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.413.1">7.1</a>, <a href="#rfc.iref.55"><b>7.5.11</b></a>, <a href="#rfc.xref.status.413.2">11.2.3</a></li>
     4900                  <li>414 URI Too Long (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.414.1">7.1</a>, <a href="#rfc.iref.56"><b>7.5.12</b></a>, <a href="#rfc.xref.status.414.2">11.2.3</a></li>
     4901                  <li>415 Unsupported Media Type (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.415.1">7.1</a>, <a href="#rfc.iref.57"><b>7.5.13</b></a>, <a href="#rfc.xref.status.415.2">11.2.3</a></li>
     4902                  <li>417 Expectation Failed (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.417.1">7.1</a>, <a href="#rfc.iref.58"><b>7.5.14</b></a>, <a href="#rfc.xref.status.417.2">11.2.3</a></li>
     4903                  <li>426 Upgrade Required (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.426.1">7.1</a>, <a href="#rfc.iref.59"><b>7.5.15</b></a>, <a href="#rfc.xref.status.426.2">11.2.3</a>, <a href="#rfc.xref.status.426.3">C</a></li>
     4904                  <li>4xx Client Error (status code class)&nbsp;&nbsp;<a href="#rfc.iref.44"><b>7.5</b></a></li>
    49054905               </ul>
    49064906            </li>
    49074907            <li><a id="rfc.index.5" href="#rfc.index.5"><b>5</b></a><ul>
    4908                   <li>500 Internal Server Error (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.500.1">6.1</a>, <a href="#rfc.iref.60"><b>6.6.1</b></a>, <a href="#rfc.xref.status.500.2">11.2.3</a></li>
    4909                   <li>501 Not Implemented (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.501.1">6.1</a>, <a href="#rfc.iref.61"><b>6.6.2</b></a>, <a href="#rfc.xref.status.501.2">11.2.3</a></li>
    4910                   <li>502 Bad Gateway (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.502.1">6.1</a>, <a href="#rfc.iref.62"><b>6.6.3</b></a>, <a href="#rfc.xref.status.502.2">11.2.3</a></li>
    4911                   <li>503 Service Unavailable (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.503.1">6.1</a>, <a href="#rfc.iref.63"><b>6.6.4</b></a>, <a href="#rfc.xref.status.503.2">11.2.3</a></li>
    4912                   <li>504 Gateway Timeout (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.504.1">6.1</a>, <a href="#rfc.iref.64"><b>6.6.5</b></a>, <a href="#rfc.xref.status.504.2">11.2.3</a></li>
    4913                   <li>505 HTTP Version Not Supported (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.505.1">6.1</a>, <a href="#rfc.iref.65"><b>6.6.6</b></a>, <a href="#rfc.xref.status.505.2">11.2.3</a></li>
    4914                   <li>5xx Server Error (status code class)&nbsp;&nbsp;<a href="#rfc.iref.59"><b>6.6</b></a></li>
     4908                  <li>500 Internal Server Error (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.500.1">7.1</a>, <a href="#rfc.iref.61"><b>7.6.1</b></a>, <a href="#rfc.xref.status.500.2">11.2.3</a></li>
     4909                  <li>501 Not Implemented (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.501.1">7.1</a>, <a href="#rfc.iref.62"><b>7.6.2</b></a>, <a href="#rfc.xref.status.501.2">11.2.3</a></li>
     4910                  <li>502 Bad Gateway (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.502.1">7.1</a>, <a href="#rfc.iref.63"><b>7.6.3</b></a>, <a href="#rfc.xref.status.502.2">11.2.3</a></li>
     4911                  <li>503 Service Unavailable (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.503.1">7.1</a>, <a href="#rfc.iref.64"><b>7.6.4</b></a>, <a href="#rfc.xref.status.503.2">11.2.3</a></li>
     4912                  <li>504 Gateway Timeout (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.504.1">7.1</a>, <a href="#rfc.iref.65"><b>7.6.5</b></a>, <a href="#rfc.xref.status.504.2">11.2.3</a></li>
     4913                  <li>505 HTTP Version Not Supported (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.505.1">7.1</a>, <a href="#rfc.iref.66"><b>7.6.6</b></a>, <a href="#rfc.xref.status.505.2">11.2.3</a></li>
     4914                  <li>5xx Server Error (status code class)&nbsp;&nbsp;<a href="#rfc.iref.60"><b>7.6</b></a></li>
    49154915               </ul>
    49164916            </li>
    49174917            <li><a id="rfc.index.A" href="#rfc.index.A"><b>A</b></a><ul>
    4918                   <li>Accept header field&nbsp;&nbsp;<a href="#rfc.xref.header.accept.1">3.4.1</a>, <a href="#rfc.xref.header.accept.2">5.3</a>, <a href="#rfc.xref.header.accept.3">8.5</a>, <a href="#rfc.iref.a.1"><b>10.1</b></a>, <a href="#rfc.xref.header.accept.4">11.3.2</a></li>
    4919                   <li>Accept-Charset header field&nbsp;&nbsp;<a href="#rfc.xref.header.accept-charset.1">3.4.1</a>, <a href="#rfc.xref.header.accept-charset.2">5.3</a>, <a href="#rfc.iref.a.2"><b>10.2</b></a>, <a href="#rfc.xref.header.accept-charset.3">11.3.2</a>, <a href="#rfc.xref.header.accept-charset.4">C</a></li>
    4920                   <li>Accept-Encoding header field&nbsp;&nbsp;<a href="#rfc.xref.header.accept-encoding.1">3.4.1</a>, <a href="#rfc.xref.header.accept-encoding.2">5.3</a>, <a href="#rfc.xref.header.accept-encoding.3">8.4</a>, <a href="#rfc.iref.a.3"><b>10.3</b></a>, <a href="#rfc.xref.header.accept-encoding.4">11.3.2</a>, <a href="#rfc.xref.header.accept-encoding.5">11.4.2</a></li>
    4921                   <li>Accept-Language header field&nbsp;&nbsp;<a href="#rfc.xref.header.accept-language.1">3.4.1</a>, <a href="#rfc.xref.header.accept-language.2">5.3</a>, <a href="#rfc.iref.a.4"><b>10.4</b></a>, <a href="#rfc.xref.header.accept-language.3">11.3.2</a></li>
    4922                   <li>Allow header field&nbsp;&nbsp;<a href="#rfc.xref.header.allow.1">4.1</a>, <a href="#rfc.xref.header.allow.2">7</a>, <a href="#rfc.iref.a.5"><b>10.5</b></a>, <a href="#rfc.xref.header.allow.3">11.3.2</a>, <a href="#rfc.xref.header.allow.4">C</a></li>
     4918                  <li>Accept header field&nbsp;&nbsp;<a href="#rfc.xref.header.accept.1">3.4.1</a>, <a href="#rfc.xref.header.accept.2">6.3</a>, <a href="#rfc.xref.header.accept.3">9.5</a>, <a href="#rfc.iref.a.1"><b>10.1</b></a>, <a href="#rfc.xref.header.accept.4">11.3.2</a></li>
     4919                  <li>Accept-Charset header field&nbsp;&nbsp;<a href="#rfc.xref.header.accept-charset.1">3.4.1</a>, <a href="#rfc.xref.header.accept-charset.2">6.3</a>, <a href="#rfc.iref.a.2"><b>10.2</b></a>, <a href="#rfc.xref.header.accept-charset.3">11.3.2</a>, <a href="#rfc.xref.header.accept-charset.4">C</a></li>
     4920                  <li>Accept-Encoding header field&nbsp;&nbsp;<a href="#rfc.xref.header.accept-encoding.1">3.4.1</a>, <a href="#rfc.xref.header.accept-encoding.2">6.3</a>, <a href="#rfc.xref.header.accept-encoding.3">9.4</a>, <a href="#rfc.iref.a.3"><b>10.3</b></a>, <a href="#rfc.xref.header.accept-encoding.4">11.3.2</a>, <a href="#rfc.xref.header.accept-encoding.5">11.4.2</a></li>
     4921                  <li>Accept-Language header field&nbsp;&nbsp;<a href="#rfc.xref.header.accept-language.1">3.4.1</a>, <a href="#rfc.xref.header.accept-language.2">6.3</a>, <a href="#rfc.iref.a.4"><b>10.4</b></a>, <a href="#rfc.xref.header.accept-language.3">11.3.2</a></li>
     4922                  <li>Allow header field&nbsp;&nbsp;<a href="#rfc.xref.header.allow.1">5.1</a>, <a href="#rfc.xref.header.allow.2">8</a>, <a href="#rfc.iref.a.5"><b>10.5</b></a>, <a href="#rfc.xref.header.allow.3">11.3.2</a>, <a href="#rfc.xref.header.allow.4">C</a></li>
    49234923               </ul>
    49244924            </li>
    49254925            <li><a id="rfc.index.C" href="#rfc.index.C"><b>C</b></a><ul>
    4926                   <li>cacheable&nbsp;&nbsp;<a href="#rfc.iref.c.2"><b>4.2.3</b></a></li>
     4926                  <li>cacheable&nbsp;&nbsp;<a href="#rfc.iref.c.2"><b>5.2.3</b></a></li>
    49274927                  <li>Coding Format&nbsp;&nbsp;
    49284928                     <ul>
    4929                         <li>compress&nbsp;&nbsp;<a href="#rfc.iref.c.5">8.4</a></li>
    4930                         <li>deflate&nbsp;&nbsp;<a href="#rfc.iref.c.6">8.4</a></li>
    4931                         <li>gzip&nbsp;&nbsp;<a href="#rfc.iref.c.7">8.4</a></li>
     4929                        <li>compress&nbsp;&nbsp;<a href="#rfc.iref.c.5">9.4</a></li>
     4930                        <li>deflate&nbsp;&nbsp;<a href="#rfc.iref.c.6">9.4</a></li>
     4931                        <li>gzip&nbsp;&nbsp;<a href="#rfc.iref.c.7">9.4</a></li>
    49324932                     </ul>
    49334933                  </li>
    4934                   <li>compress (Coding Format)&nbsp;&nbsp;<a href="#rfc.iref.c.4">8.4</a></li>
    4935                   <li>CONNECT method&nbsp;&nbsp;<a href="#rfc.xref.CONNECT.1">4.1</a>, <a href="#rfc.iref.c.3"><b>4.3.6</b></a>, <a href="#rfc.xref.CONNECT.2">11.1.3</a>, <a href="#rfc.xref.CONNECT.3">C</a></li>
     4934                  <li>compress (Coding Format)&nbsp;&nbsp;<a href="#rfc.iref.c.4">9.4</a></li>
     4935                  <li>CONNECT method&nbsp;&nbsp;<a href="#rfc.xref.CONNECT.1">5.1</a>, <a href="#rfc.iref.c.3"><b>5.3.6</b></a>, <a href="#rfc.xref.CONNECT.2">11.1.3</a>, <a href="#rfc.xref.CONNECT.3">C</a></li>
    49364936                  <li>content negotiation&nbsp;&nbsp;<a href="#rfc.iref.c.1">1</a></li>
    4937                   <li>Content-Encoding header field&nbsp;&nbsp;<a href="#rfc.xref.header.content-encoding.1">3.2</a>, <a href="#rfc.xref.header.content-encoding.2">8.4</a>, <a href="#rfc.iref.c.8"><b>10.6</b></a>, <a href="#rfc.xref.header.content-encoding.3">11.3.2</a></li>
     4937                  <li>Content-Encoding header field&nbsp;&nbsp;<a href="#rfc.xref.header.content-encoding.1">3.2</a>, <a href="#rfc.xref.header.content-encoding.2">9.4</a>, <a href="#rfc.iref.c.8"><b>10.6</b></a>, <a href="#rfc.xref.header.content-encoding.3">11.3.2</a></li>
    49384938                  <li>Content-Language header field&nbsp;&nbsp;<a href="#rfc.xref.header.content-language.1">3.2</a>, <a href="#rfc.iref.c.9"><b>10.7</b></a>, <a href="#rfc.xref.header.content-language.2">11.3.2</a></li>
    4939                   <li>Content-Location header field&nbsp;&nbsp;<a href="#rfc.xref.header.content-location.1">3.2</a>, <a href="#rfc.xref.header.content-location.2">4.3.3</a>, <a href="#rfc.iref.c.10"><b>10.8</b></a>, <a href="#rfc.xref.header.content-location.3">10.13</a>, <a href="#rfc.xref.header.content-location.4">11.3.2</a>, <a href="#rfc.xref.header.content-location.5">C</a></li>
     4939                  <li>Content-Location header field&nbsp;&nbsp;<a href="#rfc.xref.header.content-location.1">3.2</a>, <a href="#rfc.xref.header.content-location.2">5.3.3</a>, <a href="#rfc.iref.c.10"><b>10.8</b></a>, <a href="#rfc.xref.header.content-location.3">10.13</a>, <a href="#rfc.xref.header.content-location.4">11.3.2</a>, <a href="#rfc.xref.header.content-location.5">C</a></li>
    49404940                  <li>Content-Transfer-Encoding header field&nbsp;&nbsp;<a href="#rfc.iref.c.12">A.5</a>, <a href="#rfc.xref.no.content-transfer-encoding.1">C</a></li>
    4941                   <li>Content-Type header field&nbsp;&nbsp;<a href="#rfc.xref.header.content-type.1">3.2</a>, <a href="#rfc.xref.header.content-type.2">6</a>, <a href="#rfc.xref.header.content-type.3">8.5</a>, <a href="#rfc.iref.c.11"><b>10.9</b></a>, <a href="#rfc.xref.header.content-type.4">11.3.1</a>, <a href="#rfc.xref.header.content-type.5">11.3.2</a></li>
     4941                  <li>Content-Type header field&nbsp;&nbsp;<a href="#rfc.xref.header.content-type.1">3.2</a>, <a href="#rfc.xref.header.content-type.2">7</a>, <a href="#rfc.xref.header.content-type.3">9.5</a>, <a href="#rfc.iref.c.11"><b>10.9</b></a>, <a href="#rfc.xref.header.content-type.4">11.3.1</a>, <a href="#rfc.xref.header.content-type.5">11.3.2</a></li>
    49424942               </ul>
    49434943            </li>
    49444944            <li><a id="rfc.index.D" href="#rfc.index.D"><b>D</b></a><ul>
    4945                   <li>Date header field&nbsp;&nbsp;<a href="#rfc.xref.header.date.1">7</a>, <a href="#rfc.iref.d.3"><b>10.10</b></a>, <a href="#rfc.xref.header.date.2">11.3.2</a></li>
    4946                   <li>deflate (Coding Format)&nbsp;&nbsp;<a href="#rfc.iref.d.2">8.4</a></li>
    4947                   <li>DELETE method&nbsp;&nbsp;<a href="#rfc.xref.DELETE.1">4.1</a>, <a href="#rfc.iref.d.1"><b>4.3.5</b></a>, <a href="#rfc.xref.DELETE.2">11.1.3</a></li>
     4945                  <li>Date header field&nbsp;&nbsp;<a href="#rfc.xref.header.date.1">8</a>, <a href="#rfc.iref.d.3"><b>10.10</b></a>, <a href="#rfc.xref.header.date.2">11.3.2</a></li>
     4946                  <li>deflate (Coding Format)&nbsp;&nbsp;<a href="#rfc.iref.d.2">9.4</a></li>
     4947                  <li>DELETE method&nbsp;&nbsp;<a href="#rfc.xref.DELETE.1">5.1</a>, <a href="#rfc.iref.d.1"><b>5.3.5</b></a>, <a href="#rfc.xref.DELETE.2">11.1.3</a></li>
    49484948               </ul>
    49494949            </li>
    49504950            <li><a id="rfc.index.E" href="#rfc.index.E"><b>E</b></a><ul>
    4951                   <li>Expect header field&nbsp;&nbsp;<a href="#rfc.xref.header.expect.1">5.1</a>, <a href="#rfc.xref.header.expect.2">6.5.14</a>, <a href="#rfc.iref.e.1"><b>10.11</b></a>, <a href="#rfc.xref.header.expect.3">11.3.2</a>, <a href="#rfc.xref.header.expect.4">C</a></li>
     4951                  <li>Expect header field&nbsp;&nbsp;<a href="#rfc.xref.header.expect.1">6.1</a>, <a href="#rfc.xref.header.expect.2">7.5.14</a>, <a href="#rfc.iref.e.1"><b>10.11</b></a>, <a href="#rfc.xref.header.expect.3">11.3.2</a>, <a href="#rfc.xref.header.expect.4">C</a></li>
    49524952                  <li>Expect Values&nbsp;&nbsp;
    49534953                     <ul>
    … …  
    49584958            </li>
    49594959            <li><a id="rfc.index.F" href="#rfc.index.F"><b>F</b></a><ul>
    4960                   <li>From header field&nbsp;&nbsp;<a href="#rfc.xref.header.from.1">5.5</a>, <a href="#rfc.iref.f.1"><b>10.12</b></a>, <a href="#rfc.xref.header.from.2">11.3.2</a></li>
     4960                  <li>From header field&nbsp;&nbsp;<a href="#rfc.xref.header.from.1">6.5</a>, <a href="#rfc.iref.f.1"><b>10.12</b></a>, <a href="#rfc.xref.header.from.2">11.3.2</a></li>
    49614961               </ul>
    49624962            </li>
    49634963            <li><a id="rfc.index.G" href="#rfc.index.G"><b>G</b></a><ul>
    4964                   <li>GET method&nbsp;&nbsp;<a href="#rfc.xref.GET.1">4.1</a>, <a href="#rfc.iref.g.4"><b>4.3.1</b></a>, <a href="#rfc.xref.GET.2">11.1.3</a></li>
     4964                  <li>GET method&nbsp;&nbsp;<a href="#rfc.xref.GET.1">5.1</a>, <a href="#rfc.iref.g.4"><b>5.3.1</b></a>, <a href="#rfc.xref.GET.2">11.1.3</a></li>
    49654965                  <li><tt>Grammar</tt>&nbsp;&nbsp;
    49664966                     <ul>
    … …  
    49724972                        <li><tt>accept-params</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.35"><b>10.1</b></a></li>
    49734973                        <li><tt>Allow</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.42"><b>10.5</b></a></li>
    4974                         <li><tt>asctime-date</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.20"><b>8.1</b></a></li>
    4975                         <li><tt>attribute</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.30"><b>8.5</b></a></li>
    4976                         <li><tt>charset</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.23"><b>8.3</b></a></li>
     4974                        <li><tt>asctime-date</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.20"><b>9.1</b></a></li>
     4975                        <li><tt>attribute</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.30"><b>9.5</b></a></li>
     4976                        <li><tt>charset</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.23"><b>9.3</b></a></li>
    49774977                        <li><tt>codings</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.39"><b>10.3</b></a></li>
    4978                         <li><tt>content-coding</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.24"><b>8.4</b></a></li>
     4978                        <li><tt>content-coding</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.24"><b>9.4</b></a></li>
    49794979                        <li><tt>Content-Encoding</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.43"><b>10.6</b></a></li>
    49804980                        <li><tt>Content-Language</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.44"><b>10.7</b></a></li>
    … …  
    49824982                        <li><tt>Content-Type</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.46"><b>10.9</b></a></li>
    49834983                        <li><tt>Date</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.47"><b>10.10</b></a></li>
    4984                         <li><tt>date1</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.7"><b>8.1</b></a></li>
    4985                         <li><tt>day</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.14"><b>8.1</b></a></li>
    4986                         <li><tt>day-name</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.12"><b>8.1</b></a></li>
    4987                         <li><tt>day-name-l</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.13"><b>8.1</b></a></li>
     4984                        <li><tt>date1</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.7"><b>9.1</b></a></li>
     4985                        <li><tt>day</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.14"><b>9.1</b></a></li>
     4986                        <li><tt>day-name</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.12"><b>9.1</b></a></li>
     4987                        <li><tt>day-name-l</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.13"><b>9.1</b></a></li>
    49884988                        <li><tt>delta-seconds</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.58"><b>10.16</b></a></li>
    49894989                        <li><tt>Expect</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.48"><b>10.11</b></a></li>
    … …  
    49934993                        <li><tt>expectation</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.49"><b>10.11</b></a></li>
    49944994                        <li><tt>From</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.53"><b>10.12</b></a></li>
    4995                         <li><tt>GMT</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.17"><b>8.1</b></a></li>
    4996                         <li><tt>hour</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.9"><b>8.1</b></a></li>
    4997                         <li><tt>HTTP-date</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.5"><b>8.1</b></a></li>
     4995                        <li><tt>GMT</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.17"><b>9.1</b></a></li>
     4996                        <li><tt>hour</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.9"><b>9.1</b></a></li>
     4997                        <li><tt>HTTP-date</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.5"><b>9.1</b></a></li>
    49984998                        <li><tt>language-range</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.41"><b>10.4</b></a></li>
    4999                         <li><tt>language-tag</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.32"><b>8.6</b></a></li>
     4999                        <li><tt>language-tag</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.32"><b>9.6</b></a></li>
    50005000                        <li><tt>Location</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.54"><b>10.13</b></a></li>
    50015001                        <li><tt>Max-Forwards</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.55"><b>10.14</b></a></li>
    50025002                        <li><tt>media-range</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.34"><b>10.1</b></a></li>
    5003                         <li><tt>media-type</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.26"><b>8.5</b></a></li>
    5004                         <li><tt>method</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.3"><b>4.1</b></a></li>
     5003                        <li><tt>media-type</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.26"><b>9.5</b></a></li>
     5004                        <li><tt>method</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.3"><b>5.1</b></a></li>
    50055005                        <li><tt>MIME-Version</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.61"><b>A.1</b></a></li>
    5006                         <li><tt>minute</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.10"><b>8.1</b></a></li>
    5007                         <li><tt>month</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.15"><b>8.1</b></a></li>
    5008                         <li><tt>obs-date</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.18"><b>8.1</b></a></li>
    5009                         <li><tt>parameter</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.29"><b>8.5</b></a></li>
    5010                         <li><tt>product</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.21"><b>8.2</b></a></li>
    5011                         <li><tt>product-version</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.22"><b>8.2</b></a></li>
     5006                        <li><tt>minute</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.10"><b>9.1</b></a></li>
     5007                        <li><tt>month</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.15"><b>9.1</b></a></li>
     5008                        <li><tt>obs-date</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.18"><b>9.1</b></a></li>
     5009                        <li><tt>parameter</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.29"><b>9.5</b></a></li>
     5010                        <li><tt>product</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.21"><b>9.2</b></a></li>
     5011                        <li><tt>product-version</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.22"><b>9.2</b></a></li>
    50125012                        <li><tt>qvalue</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.2"><b>3.4.3</b></a></li>
    50135013                        <li><tt>Referer</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.56"><b>10.15</b></a></li>
    50145014                        <li><tt>Retry-After</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.57"><b>10.16</b></a></li>
    5015                         <li><tt>rfc1123-date</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.6"><b>8.1</b></a></li>
    5016                         <li><tt>rfc850-date</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.19"><b>8.1</b></a></li>
    5017                         <li><tt>second</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.11"><b>8.1</b></a></li>
     5015                        <li><tt>rfc1123-date</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.6"><b>9.1</b></a></li>
     5016                        <li><tt>rfc850-date</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.19"><b>9.1</b></a></li>
     5017                        <li><tt>second</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.11"><b>9.1</b></a></li>
    50185018                        <li><tt>Server</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.59"><b>10.17</b></a></li>
    5019                         <li><tt>subtype</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.28"><b>8.5</b></a></li>
    5020                         <li><tt>time-of-day</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.8"><b>8.1</b></a></li>
    5021                         <li><tt>type</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.27"><b>8.5</b></a></li>
     5019                        <li><tt>subtype</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.28"><b>9.5</b></a></li>
     5020                        <li><tt>time-of-day</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.8"><b>9.1</b></a></li>
     5021                        <li><tt>type</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.27"><b>9.5</b></a></li>
    50225022                        <li><tt>User-Agent</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.60"><b>10.18</b></a></li>
    5023                         <li><tt>value</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.31"><b>8.5</b></a></li>
     5023                        <li><tt>value</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.31"><b>9.5</b></a></li>
    50245024                        <li><tt>weight</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.1"><b>3.4.3</b></a></li>
    5025                         <li><tt>year</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.16"><b>8.1</b></a></li>
     5025                        <li><tt>year</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.16"><b>9.1</b></a></li>
    50265026                     </ul>
    50275027                  </li>
    5028                   <li>gzip (Coding Format)&nbsp;&nbsp;<a href="#rfc.iref.g.25">8.4</a></li>
     5028                  <li>gzip (Coding Format)&nbsp;&nbsp;<a href="#rfc.iref.g.25">9.4</a></li>
    50295029               </ul>
    50305030            </li>
    50315031            <li><a id="rfc.index.H" href="#rfc.index.H"><b>H</b></a><ul>
    5032                   <li>HEAD method&nbsp;&nbsp;<a href="#rfc.xref.HEAD.1">4.1</a>, <a href="#rfc.iref.h.1"><b>4.3.2</b></a>, <a href="#rfc.xref.HEAD.2">11.1.3</a></li>
     5032                  <li>HEAD method&nbsp;&nbsp;<a href="#rfc.xref.HEAD.1">5.1</a>, <a href="#rfc.iref.h.1"><b>5.3.2</b></a>, <a href="#rfc.xref.HEAD.2">11.1.3</a></li>
    50335033                  <li>Header Fields&nbsp;&nbsp;
    50345034                     <ul>
    5035                         <li>Accept&nbsp;&nbsp;<a href="#rfc.xref.header.accept.1">3.4.1</a>, <a href="#rfc.xref.header.accept.2">5.3</a>, <a href="#rfc.xref.header.accept.3">8.5</a>, <a href="#rfc.iref.h.2"><b>10.1</b></a>, <a href="#rfc.xref.header.accept.4">11.3.2</a></li>
    5036                         <li>Accept-Charset&nbsp;&nbsp;<a href="#rfc.xref.header.accept-charset.1">3.4.1</a>, <a href="#rfc.xref.header.accept-charset.2">5.3</a>, <a href="#rfc.iref.h.3"><b>10.2</b></a>, <a href="#rfc.xref.header.accept-charset.3">11.3.2</a>, <a href="#rfc.xref.header.accept-charset.4">C</a></li>
    5037                         <li>Accept-Encoding&nbsp;&nbsp;<a href="#rfc.xref.header.accept-encoding.1">3.4.1</a>, <a href="#rfc.xref.header.accept-encoding.2">5.3</a>, <a href="#rfc.xref.header.accept-encoding.3">8.4</a>, <a href="#rfc.iref.h.4"><b>10.3</b></a>, <a href="#rfc.xref.header.accept-encoding.4">11.3.2</a>, <a href="#rfc.xref.header.accept-encoding.5">11.4.2</a></li>
    5038                         <li>Accept-Language&nbsp;&nbsp;<a href="#rfc.xref.header.accept-language.1">3.4.1</a>, <a href="#rfc.xref.header.accept-language.2">5.3</a>, <a href="#rfc.iref.h.5"><b>10.4</b></a>, <a href="#rfc.xref.header.accept-language.3">11.3.2</a></li>
    5039                         <li>Allow&nbsp;&nbsp;<a href="#rfc.xref.header.allow.1">4.1</a>, <a href="#rfc.xref.header.allow.2">7</a>, <a href="#rfc.iref.h.6"><b>10.5</b></a>, <a href="#rfc.xref.header.allow.3">11.3.2</a>, <a href="#rfc.xref.header.allow.4">C</a></li>
    5040                         <li>Content-Encoding&nbsp;&nbsp;<a href="#rfc.xref.header.content-encoding.1">3.2</a>, <a href="#rfc.xref.header.content-encoding.2">8.4</a>, <a href="#rfc.iref.h.7"><b>10.6</b></a>, <a href="#rfc.xref.header.content-encoding.3">11.3.2</a></li>
     5035                        <li>Accept&nbsp;&nbsp;<a href="#rfc.xref.header.accept.1">3.4.1</a>, <a href="#rfc.xref.header.accept.2">6.3</a>, <a href="#rfc.xref.header.accept.3">9.5</a>, <a href="#rfc.iref.h.2"><b>10.1</b></a>, <a href="#rfc.xref.header.accept.4">11.3.2</a></li>
     5036                        <li>Accept-Charset&nbsp;&nbsp;<a href="#rfc.xref.header.accept-charset.1">3.4.1</a>, <a href="#rfc.xref.header.accept-charset.2">6.3</a>, <a href="#rfc.iref.h.3"><b>10.2</b></a>, <a href="#rfc.xref.header.accept-charset.3">11.3.2</a>, <a href="#rfc.xref.header.accept-charset.4">C</a></li>
     5037                        <li>Accept-Encoding&nbsp;&nbsp;<a href="#rfc.xref.header.accept-encoding.1">3.4.1</a>, <a href="#rfc.xref.header.accept-encoding.2">6.3</a>, <a href="#rfc.xref.header.accept-encoding.3">9.4</a>, <a href="#rfc.iref.h.4"><b>10.3</b></a>, <a href="#rfc.xref.header.accept-encoding.4">11.3.2</a>, <a href="#rfc.xref.header.accept-encoding.5">11.4.2</a></li>
     5038                        <li>Accept-Language&nbsp;&nbsp;<a href="#rfc.xref.header.accept-language.1">3.4.1</a>, <a href="#rfc.xref.header.accept-language.2">6.3</a>, <a href="#rfc.iref.h.5"><b>10.4</b></a>, <a href="#rfc.xref.header.accept-language.3">11.3.2</a></li>
     5039                        <li>Allow&nbsp;&nbsp;<a href="#rfc.xref.header.allow.1">5.1</a>, <a href="#rfc.xref.header.allow.2">8</a>, <a href="#rfc.iref.h.6"><b>10.5</b></a>, <a href="#rfc.xref.header.allow.3">11.3.2</a>, <a href="#rfc.xref.header.allow.4">C</a></li>
     5040                        <li>Content-Encoding&nbsp;&nbsp;<a href="#rfc.xref.header.content-encoding.1">3.2</a>, <a href="#rfc.xref.header.content-encoding.2">9.4</a>, <a href="#rfc.iref.h.7"><b>10.6</b></a>, <a href="#rfc.xref.header.content-encoding.3">11.3.2</a></li>
    50415041                        <li>Content-Language&nbsp;&nbsp;<a href="#rfc.xref.header.content-language.1">3.2</a>, <a href="#rfc.iref.h.8"><b>10.7</b></a>, <a href="#rfc.xref.header.content-language.2">11.3.2</a></li>
    5042                         <li>Content-Location&nbsp;&nbsp;<a href="#rfc.xref.header.content-location.1">3.2</a>, <a href="#rfc.xref.header.content-location.2">4.3.3</a>, <a href="#rfc.iref.h.9"><b>10.8</b></a>, <a href="#rfc.xref.header.content-location.3">10.13</a>, <a href="#rfc.xref.header.content-location.4">11.3.2</a>, <a href="#rfc.xref.header.content-location.5">C</a></li>
     5042                        <li>Content-Location&nbsp;&nbsp;<a href="#rfc.xref.header.content-location.1">3.2</a>, <a href="#rfc.xref.header.content-location.2">5.3.3</a>, <a href="#rfc.iref.h.9"><b>10.8</b></a>, <a href="#rfc.xref.header.content-location.3">10.13</a>, <a href="#rfc.xref.header.content-location.4">11.3.2</a>, <a href="#rfc.xref.header.content-location.5">C</a></li>
    50435043                        <li>Content-Transfer-Encoding&nbsp;&nbsp;<a href="#rfc.iref.h.21">A.5</a>, <a href="#rfc.xref.no.content-transfer-encoding.1">C</a></li>
    5044                         <li>Content-Type&nbsp;&nbsp;<a href="#rfc.xref.header.content-type.1">3.2</a>, <a href="#rfc.xref.header.content-type.2">6</a>, <a href="#rfc.xref.header.content-type.3">8.5</a>, <a href="#rfc.iref.h.10"><b>10.9</b></a>, <a href="#rfc.xref.header.content-type.4">11.3.1</a>, <a href="#rfc.xref.header.content-type.5">11.3.2</a></li>
    5045                         <li>Date&nbsp;&nbsp;<a href="#rfc.xref.header.date.1">7</a>, <a href="#rfc.iref.h.11"><b>10.10</b></a>, <a href="#rfc.xref.header.date.2">11.3.2</a></li>
    5046                         <li>Expect&nbsp;&nbsp;<a href="#rfc.xref.header.expect.1">5.1</a>, <a href="#rfc.xref.header.expect.2">6.5.14</a>, <a href="#rfc.iref.h.12"><b>10.11</b></a>, <a href="#rfc.xref.header.expect.3">11.3.2</a>, <a href="#rfc.xref.header.expect.4">C</a></li>
    5047                         <li>From&nbsp;&nbsp;<a href="#rfc.xref.header.from.1">5.5</a>, <a href="#rfc.iref.h.13"><b>10.12</b></a>, <a href="#rfc.xref.header.from.2">11.3.2</a></li>
    5048                         <li>Location&nbsp;&nbsp;<a href="#rfc.xref.header.location.1">4.3.3</a>, <a href="#rfc.xref.header.location.2">6.4</a>, <a href="#rfc.xref.header.location.3">7</a>, <a href="#rfc.iref.h.14"><b>10.13</b></a>, <a href="#rfc.xref.header.location.4">11.3.2</a>, <a href="#rfc.xref.header.location.5">C</a></li>
    5049                         <li>Max-Forwards&nbsp;&nbsp;<a href="#rfc.xref.header.max-forwards.1">4.3.7</a>, <a href="#rfc.xref.header.max-forwards.2">4.3.8</a>, <a href="#rfc.xref.header.max-forwards.3">5.1</a>, <a href="#rfc.iref.h.15"><b>10.14</b></a>, <a href="#rfc.xref.header.max-forwards.4">11.3.2</a>, <a href="#rfc.xref.header.max-forwards.5">C</a></li>
     5044                        <li>Content-Type&nbsp;&nbsp;<a href="#rfc.xref.header.content-type.1">3.2</a>, <a href="#rfc.xref.header.content-type.2">7</a>, <a href="#rfc.xref.header.content-type.3">9.5</a>, <a href="#rfc.iref.h.10"><b>10.9</b></a>, <a href="#rfc.xref.header.content-type.4">11.3.1</a>, <a href="#rfc.xref.header.content-type.5">11.3.2</a></li>
     5045                        <li>Date&nbsp;&nbsp;<a href="#rfc.xref.header.date.1">8</a>, <a href="#rfc.iref.h.11"><b>10.10</b></a>, <a href="#rfc.xref.header.date.2">11.3.2</a></li>
     5046                        <li>Expect&nbsp;&nbsp;<a href="#rfc.xref.header.expect.1">6.1</a>, <a href="#rfc.xref.header.expect.2">7.5.14</a>, <a href="#rfc.iref.h.12"><b>10.11</b></a>, <a href="#rfc.xref.header.expect.3">11.3.2</a>, <a href="#rfc.xref.header.expect.4">C</a></li>
     5047                        <li>From&nbsp;&nbsp;<a href="#rfc.xref.header.from.1">6.5</a>, <a href="#rfc.iref.h.13"><b>10.12</b></a>, <a href="#rfc.xref.header.from.2">11.3.2</a></li>
     5048                        <li>Location&nbsp;&nbsp;<a href="#rfc.xref.header.location.1">5.3.3</a>, <a href="#rfc.xref.header.location.2">7.4</a>, <a href="#rfc.xref.header.location.3">8</a>, <a href="#rfc.iref.h.14"><b>10.13</b></a>, <a href="#rfc.xref.header.location.4">11.3.2</a>, <a href="#rfc.xref.header.location.5">C</a></li>
     5049                        <li>Max-Forwards&nbsp;&nbsp;<a href="#rfc.xref.header.max-forwards.1">5.3.7</a>, <a href="#rfc.xref.header.max-forwards.2">5.3.8</a>, <a href="#rfc.xref.header.max-forwards.3">6.1</a>, <a href="#rfc.iref.h.15"><b>10.14</b></a>, <a href="#rfc.xref.header.max-forwards.4">11.3.2</a>, <a href="#rfc.xref.header.max-forwards.5">C</a></li>
    50505050                        <li>MIME-Version&nbsp;&nbsp;<a href="#rfc.xref.mime-version.1">11.3.2</a>, <a href="#rfc.iref.h.20"><b>A.1</b></a></li>
    5051                         <li>Referer&nbsp;&nbsp;<a href="#rfc.xref.header.referer.1">5.5</a>, <a href="#rfc.iref.h.16"><b>10.15</b></a>, <a href="#rfc.xref.header.referer.2">11.3.2</a>, <a href="#rfc.xref.header.referer.3">C</a></li>
    5052                         <li>Retry-After&nbsp;&nbsp;<a href="#rfc.xref.header.retry-after.1">6.6.4</a>, <a href="#rfc.xref.header.retry-after.2">7</a>, <a href="#rfc.iref.h.17"><b>10.16</b></a>, <a href="#rfc.xref.header.retry-after.3">11.3.2</a></li>
    5053                         <li>Server&nbsp;&nbsp;<a href="#rfc.xref.header.server.1">7</a>, <a href="#rfc.iref.h.18"><b>10.17</b></a>, <a href="#rfc.xref.header.server.2">11.3.2</a>, <a href="#rfc.xref.header.server.3">12.1</a>, <a href="#rfc.xref.header.server.4">C</a></li>
    5054                         <li>User-Agent&nbsp;&nbsp;<a href="#rfc.xref.header.user-agent.1">3.4.1</a>, <a href="#rfc.xref.header.user-agent.2">5.5</a>, <a href="#rfc.iref.h.19"><b>10.18</b></a>, <a href="#rfc.xref.header.user-agent.3">11.3.2</a>, <a href="#rfc.xref.header.user-agent.4">12.1</a></li>
     5051                        <li>Referer&nbsp;&nbsp;<a href="#rfc.xref.header.referer.1">6.5</a>, <a href="#rfc.iref.h.16"><b>10.15</b></a>, <a href="#rfc.xref.header.referer.2">11.3.2</a>, <a href="#rfc.xref.header.referer.3">C</a></li>
     5052                        <li>Retry-After&nbsp;&nbsp;<a href="#rfc.xref.header.retry-after.1">7.6.4</a>, <a href="#rfc.xref.header.retry-after.2">8</a>, <a href="#rfc.iref.h.17"><b>10.16</b></a>, <a href="#rfc.xref.header.retry-after.3">11.3.2</a></li>
     5053                        <li>Server&nbsp;&nbsp;<a href="#rfc.xref.header.server.1">8</a>, <a href="#rfc.iref.h.18"><b>10.17</b></a>, <a href="#rfc.xref.header.server.2">11.3.2</a>, <a href="#rfc.xref.header.server.3">12.1</a>, <a href="#rfc.xref.header.server.4">C</a></li>
     5054                        <li>User-Agent&nbsp;&nbsp;<a href="#rfc.xref.header.user-agent.1">3.4.1</a>, <a href="#rfc.xref.header.user-agent.2">6.5</a>, <a href="#rfc.iref.h.19"><b>10.18</b></a>, <a href="#rfc.xref.header.user-agent.3">11.3.2</a>, <a href="#rfc.xref.header.user-agent.4">12.1</a></li>
    50555055                     </ul>
    50565056                  </li>
    … …  
    50585058            </li>
    50595059            <li><a id="rfc.index.I" href="#rfc.index.I"><b>I</b></a><ul>
    5060                   <li>idempotent&nbsp;&nbsp;<a href="#rfc.iref.i.1"><b>4.2.2</b></a></li>
     5060                  <li>idempotent&nbsp;&nbsp;<a href="#rfc.iref.i.1"><b>5.2.2</b></a></li>
    50615061               </ul>
    50625062            </li>
    50635063            <li><a id="rfc.index.L" href="#rfc.index.L"><b>L</b></a><ul>
    5064                   <li>Location header field&nbsp;&nbsp;<a href="#rfc.xref.header.location.1">4.3.3</a>, <a href="#rfc.xref.header.location.2">6.4</a>, <a href="#rfc.xref.header.location.3">7</a>, <a href="#rfc.iref.l.1"><b>10.13</b></a>, <a href="#rfc.xref.header.location.4">11.3.2</a>, <a href="#rfc.xref.header.location.5">C</a></li>
     5064                  <li>Location header field&nbsp;&nbsp;<a href="#rfc.xref.header.location.1">5.3.3</a>, <a href="#rfc.xref.header.location.2">7.4</a>, <a href="#rfc.xref.header.location.3">8</a>, <a href="#rfc.iref.l.1"><b>10.13</b></a>, <a href="#rfc.xref.header.location.4">11.3.2</a>, <a href="#rfc.xref.header.location.5">C</a></li>
    50655065               </ul>
    50665066            </li>
    50675067            <li><a id="rfc.index.M" href="#rfc.index.M"><b>M</b></a><ul>
    5068                   <li>Max-Forwards header field&nbsp;&nbsp;<a href="#rfc.xref.header.max-forwards.1">4.3.7</a>, <a href="#rfc.xref.header.max-forwards.2">4.3.8</a>, <a href="#rfc.xref.header.max-forwards.3">5.1</a>, <a href="#rfc.iref.m.9"><b>10.14</b></a>, <a href="#rfc.xref.header.max-forwards.4">11.3.2</a>, <a href="#rfc.xref.header.max-forwards.5">C</a></li>
     5068                  <li>Max-Forwards header field&nbsp;&nbsp;<a href="#rfc.xref.header.max-forwards.1">5.3.7</a>, <a href="#rfc.xref.header.max-forwards.2">5.3.8</a>, <a href="#rfc.xref.header.max-forwards.3">6.1</a>, <a href="#rfc.iref.m.9"><b>10.14</b></a>, <a href="#rfc.xref.header.max-forwards.4">11.3.2</a>, <a href="#rfc.xref.header.max-forwards.5">C</a></li>
    50695069                  <li>Methods&nbsp;&nbsp;
    50705070                     <ul>
    5071                         <li>CONNECT&nbsp;&nbsp;<a href="#rfc.xref.CONNECT.1">4.1</a>, <a href="#rfc.iref.m.6"><b>4.3.6</b></a>, <a href="#rfc.xref.CONNECT.2">11.1.3</a>, <a href="#rfc.xref.CONNECT.3">C</a></li>
    5072                         <li>DELETE&nbsp;&nbsp;<a href="#rfc.xref.DELETE.1">4.1</a>, <a href="#rfc.iref.m.5"><b>4.3.5</b></a>, <a href="#rfc.xref.DELETE.2">11.1.3</a></li>
    5073                         <li>GET&nbsp;&nbsp;<a href="#rfc.xref.GET.1">4.1</a>, <a href="#rfc.iref.m.1"><b>4.3.1</b></a>, <a href="#rfc.xref.GET.2">11.1.3</a></li>
    5074                         <li>HEAD&nbsp;&nbsp;<a href="#rfc.xref.HEAD.1">4.1</a>, <a href="#rfc.iref.m.2"><b>4.3.2</b></a>, <a href="#rfc.xref.HEAD.2">11.1.3</a></li>
    5075                         <li>OPTIONS&nbsp;&nbsp;<a href="#rfc.xref.OPTIONS.1">4.1</a>, <a href="#rfc.iref.m.7"><b>4.3.7</b></a>, <a href="#rfc.xref.OPTIONS.2">10.14</a>, <a href="#rfc.xref.OPTIONS.3">11.1.3</a></li>
    5076                         <li>POST&nbsp;&nbsp;<a href="#rfc.xref.POST.1">4.1</a>, <a href="#rfc.iref.m.3"><b>4.3.3</b></a>, <a href="#rfc.xref.POST.2">11.1.3</a>, <a href="#rfc.xref.POST.3">C</a></li>
    5077                         <li>PUT&nbsp;&nbsp;<a href="#rfc.xref.PUT.1">4.1</a>, <a href="#rfc.iref.m.4"><b>4.3.4</b></a>, <a href="#rfc.xref.PUT.2">11.1.3</a>, <a href="#rfc.xref.PUT.3">C</a></li>
    5078                         <li>TRACE&nbsp;&nbsp;<a href="#rfc.xref.TRACE.1">4.1</a>, <a href="#rfc.iref.m.8"><b>4.3.8</b></a>, <a href="#rfc.xref.TRACE.2">10.14</a>, <a href="#rfc.xref.TRACE.3">11.1.3</a>, <a href="#rfc.xref.TRACE.4">12.1</a></li>
     5071                        <li>CONNECT&nbsp;&nbsp;<a href="#rfc.xref.CONNECT.1">5.1</a>, <a href="#rfc.iref.m.6"><b>5.3.6</b></a>, <a href="#rfc.xref.CONNECT.2">11.1.3</a>, <a href="#rfc.xref.CONNECT.3">C</a></li>
     5072                        <li>DELETE&nbsp;&nbsp;<a href="#rfc.xref.DELETE.1">5.1</a>, <a href="#rfc.iref.m.5"><b>5.3.5</b></a>, <a href="#rfc.xref.DELETE.2">11.1.3</a></li>
     5073                        <li>GET&nbsp;&nbsp;<a href="#rfc.xref.GET.1">5.1</a>, <a href="#rfc.iref.m.1"><b>5.3.1</b></a>, <a href="#rfc.xref.GET.2">11.1.3</a></li>
     5074                        <li>HEAD&nbsp;&nbsp;<a href="#rfc.xref.HEAD.1">5.1</a>, <a href="#rfc.iref.m.2"><b>5.3.2</b></a>, <a href="#rfc.xref.HEAD.2">11.1.3</a></li>
     5075                        <li>OPTIONS&nbsp;&nbsp;<a href="#rfc.xref.OPTIONS.1">5.1</a>, <a href="#rfc.iref.m.7"><b>5.3.7</b></a>, <a href="#rfc.xref.OPTIONS.2">10.14</a>, <a href="#rfc.xref.OPTIONS.3">11.1.3</a></li>
     5076                        <li>POST&nbsp;&nbsp;<a href="#rfc.xref.POST.1">5.1</a>, <a href="#rfc.iref.m.3"><b>5.3.3</b></a>, <a href="#rfc.xref.POST.2">11.1.3</a>, <a href="#rfc.xref.POST.3">C</a></li>
     5077                        <li>PUT&nbsp;&nbsp;<a href="#rfc.xref.PUT.1">5.1</a>, <a href="#rfc.iref.m.4"><b>5.3.4</b></a>, <a href="#rfc.xref.PUT.2">11.1.3</a>, <a href="#rfc.xref.PUT.3">C</a></li>
     5078                        <li>TRACE&nbsp;&nbsp;<a href="#rfc.xref.TRACE.1">5.1</a>, <a href="#rfc.iref.m.8"><b>5.3.8</b></a>, <a href="#rfc.xref.TRACE.2">10.14</a>, <a href="#rfc.xref.TRACE.3">11.1.3</a>, <a href="#rfc.xref.TRACE.4">12.1</a></li>
    50795079                     </ul>
    50805080                  </li>
    … …  
    50835083            </li>
    50845084            <li><a id="rfc.index.O" href="#rfc.index.O"><b>O</b></a><ul>
    5085                   <li>OPTIONS method&nbsp;&nbsp;<a href="#rfc.xref.OPTIONS.1">4.1</a>, <a href="#rfc.iref.o.1"><b>4.3.7</b></a>, <a href="#rfc.xref.OPTIONS.2">10.14</a>, <a href="#rfc.xref.OPTIONS.3">11.1.3</a></li>
     5085                  <li>OPTIONS method&nbsp;&nbsp;<a href="#rfc.xref.OPTIONS.1">5.1</a>, <a href="#rfc.iref.o.1"><b>5.3.7</b></a>, <a href="#rfc.xref.OPTIONS.2">10.14</a>, <a href="#rfc.xref.OPTIONS.3">11.1.3</a></li>
    50865086               </ul>
    50875087            </li>
    50885088            <li><a id="rfc.index.P" href="#rfc.index.P"><b>P</b></a><ul>
    5089                   <li><em>Part1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.1">1</a>, <a href="#rfc.xref.Part1.2">1.1</a>, <a href="#rfc.xref.Part1.3">1.2</a>, <a href="#rfc.xref.Part1.4">2</a>, <a href="#rfc.xref.Part1.5">2</a>, <a href="#rfc.xref.Part1.6">2</a>, <a href="#rfc.xref.Part1.7">3</a>, <a href="#rfc.xref.Part1.8">3.1</a>, <a href="#rfc.xref.Part1.9">4.3.6</a>, <a href="#rfc.xref.Part1.10">4.3.7</a>, <a href="#rfc.xref.Part1.11">4.3.8</a>, <a href="#rfc.xref.Part1.12">4.3.8</a>, <a href="#rfc.xref.Part1.13">5.1</a>, <a href="#rfc.xref.Part1.14">5.5</a>, <a href="#rfc.xref.Part1.15">6.2.1</a>, <a href="#rfc.xref.Part1.16">6.2.2</a>, <a href="#rfc.xref.Part1.17">6.3.4</a>, <a href="#rfc.xref.Part1.18">6.3.6</a>, <a href="#rfc.xref.Part1.19">6.5.15</a>, <a href="#rfc.xref.Part1.20">6.6.6</a>, <a href="#rfc.xref.Part1.21">7</a>, <a href="#rfc.xref.Part1.22">8.4</a>, <a href="#rfc.xref.Part1.23">8.4</a>, <a href="#rfc.xref.Part1.24">8.4</a>, <a href="#rfc.xref.Part1.25">9.1</a>, <a href="#rfc.xref.Part1.26">9.2</a>, <a href="#rfc.xref.Part1.27">10.8</a>, <a href="#rfc.xref.Part1.28">10.11</a>, <a href="#rfc.xref.Part1.29">10.17</a>, <a href="#rfc.xref.Part1.30">10.17</a>, <a href="#rfc.xref.Part1.31">10.18</a>, <a href="#rfc.xref.Part1.32">11.1.2</a>, <a href="#rfc.xref.Part1.33">11.3.1</a>, <a href="#rfc.xref.Part1.34">11.3.1</a>, <a href="#rfc.xref.Part1.35">11.3.1</a>, <a href="#rfc.xref.Part1.36">11.3.1</a>, <a href="#rfc.xref.Part1.37">11.3.1</a>, <a href="#rfc.xref.Part1.38">11.3.1</a>, <a href="#rfc.xref.Part1.39">11.4</a>, <a href="#rfc.xref.Part1.40">11.4.1</a>, <a href="#rfc.xref.Part1.41">11.4.1</a>, <a href="#rfc.xref.Part1.42">11.4.2</a>, <a href="#rfc.xref.Part1.43">11.4.2</a>, <a href="#rfc.xref.Part1.44">11.4.2</a>, <a href="#rfc.xref.Part1.45">13</a>, <a href="#Part1"><b>14.1</b></a>, <a href="#rfc.xref.Part1.46">C</a>, <a href="#rfc.xref.Part1.47">D</a>, <a href="#rfc.xref.Part1.48">D</a>, <a href="#rfc.xref.Part1.49">D</a>, <a href="#rfc.xref.Part1.50">D</a>, <a href="#rfc.xref.Part1.51">D</a>, <a href="#rfc.xref.Part1.52">D</a>, <a href="#rfc.xref.Part1.53">D</a>, <a href="#rfc.xref.Part1.54">D</a>, <a href="#rfc.xref.Part1.55">D</a>, <a href="#rfc.xref.Part1.56">D</a>, <a href="#rfc.xref.Part1.57">D</a><ul>
     5089                  <li><em>Part1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.1">1</a>, <a href="#rfc.xref.Part1.2">1.1</a>, <a href="#rfc.xref.Part1.3">1.2</a>, <a href="#rfc.xref.Part1.4">2</a>, <a href="#rfc.xref.Part1.5">2</a>, <a href="#rfc.xref.Part1.6">2</a>, <a href="#rfc.xref.Part1.7">3</a>, <a href="#rfc.xref.Part1.8">3.1</a>, <a href="#rfc.xref.Part1.9">4.1</a>, <a href="#rfc.xref.Part1.10">4.2</a>, <a href="#rfc.xref.Part1.11">5.3.6</a>, <a href="#rfc.xref.Part1.12">5.3.7</a>, <a href="#rfc.xref.Part1.13">5.3.8</a>, <a href="#rfc.xref.Part1.14">5.3.8</a>, <a href="#rfc.xref.Part1.15">6.1</a>, <a href="#rfc.xref.Part1.16">6.5</a>, <a href="#rfc.xref.Part1.17">7.2.1</a>, <a href="#rfc.xref.Part1.18">7.2.2</a>, <a href="#rfc.xref.Part1.19">7.3.4</a>, <a href="#rfc.xref.Part1.20">7.3.6</a>, <a href="#rfc.xref.Part1.21">7.5.15</a>, <a href="#rfc.xref.Part1.22">7.6.6</a>, <a href="#rfc.xref.Part1.23">8</a>, <a href="#rfc.xref.Part1.24">9.4</a>, <a href="#rfc.xref.Part1.25">9.4</a>, <a href="#rfc.xref.Part1.26">9.4</a>, <a href="#rfc.xref.Part1.27">10.8</a>, <a href="#rfc.xref.Part1.28">10.11</a>, <a href="#rfc.xref.Part1.29">10.17</a>, <a href="#rfc.xref.Part1.30">10.17</a>, <a href="#rfc.xref.Part1.31">10.18</a>, <a href="#rfc.xref.Part1.32">11.1.2</a>, <a href="#rfc.xref.Part1.33">11.3.1</a>, <a href="#rfc.xref.Part1.34">11.3.1</a>, <a href="#rfc.xref.Part1.35">11.3.1</a>, <a href="#rfc.xref.Part1.36">11.3.1</a>, <a href="#rfc.xref.Part1.37">11.3.1</a>, <a href="#rfc.xref.Part1.38">11.3.1</a>, <a href="#rfc.xref.Part1.39">11.4</a>, <a href="#rfc.xref.Part1.40">11.4.1</a>, <a href="#rfc.xref.Part1.41">11.4.1</a>, <a href="#rfc.xref.Part1.42">11.4.2</a>, <a href="#rfc.xref.Part1.43">11.4.2</a>, <a href="#rfc.xref.Part1.44">11.4.2</a>, <a href="#rfc.xref.Part1.45">13</a>, <a href="#Part1"><b>14.1</b></a>, <a href="#rfc.xref.Part1.46">C</a>, <a href="#rfc.xref.Part1.47">D</a>, <a href="#rfc.xref.Part1.48">D</a>, <a href="#rfc.xref.Part1.49">D</a>, <a href="#rfc.xref.Part1.50">D</a>, <a href="#rfc.xref.Part1.51">D</a>, <a href="#rfc.xref.Part1.52">D</a>, <a href="#rfc.xref.Part1.53">D</a>, <a href="#rfc.xref.Part1.54">D</a>, <a href="#rfc.xref.Part1.55">D</a>, <a href="#rfc.xref.Part1.56">D</a>, <a href="#rfc.xref.Part1.57">D</a><ul>
    50905090                        <li><em>Section 1.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.3">1.2</a></li>
    5091                         <li><em>Section 2.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.17">6.3.4</a></li>
     5091                        <li><em>Section 2.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.19">7.3.4</a></li>
    50925092                        <li><em>Section 2.5</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.2">1.1</a></li>
    5093                         <li><em>Section 2.6</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.20">6.6.6</a></li>
     5093                        <li><em>Section 2.6</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.22">7.6.6</a></li>
    50945094                        <li><em>Section 2.7</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.4">2</a>, <a href="#rfc.xref.Part1.54">D</a>, <a href="#rfc.xref.Part1.56">D</a>, <a href="#rfc.xref.Part1.57">D</a></li>
    50955095                        <li><em>Section 3.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.29">10.17</a>, <a href="#rfc.xref.Part1.31">10.18</a>, <a href="#rfc.xref.Part1.33">11.3.1</a>, <a href="#rfc.xref.Part1.36">11.3.1</a></li>
    50965096                        <li><em>Section 3.2.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.48">D</a>, <a href="#rfc.xref.Part1.49">D</a>, <a href="#rfc.xref.Part1.50">D</a></li>
    50975097                        <li><em>Section 3.2.4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.35">11.3.1</a>, <a href="#rfc.xref.Part1.51">D</a>, <a href="#rfc.xref.Part1.52">D</a>, <a href="#rfc.xref.Part1.53">D</a>, <a href="#rfc.xref.Part1.55">D</a></li>
    5098                         <li><em>Section 3.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.7">3</a>, <a href="#rfc.xref.Part1.18">6.3.6</a>, <a href="#rfc.xref.Part1.26">9.2</a>, <a href="#rfc.xref.Part1.32">11.1.2</a></li>
    5099                         <li><em>Section 3.3.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.25">9.1</a></li>
     5098                        <li><em>Section 3.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.7">3</a>, <a href="#rfc.xref.Part1.10">4.2</a>, <a href="#rfc.xref.Part1.20">7.3.6</a>, <a href="#rfc.xref.Part1.32">11.1.2</a></li>
     5099                        <li><em>Section 3.3.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.9">4.1</a></li>
    51005100                        <li><em>Section 4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.40">11.4.1</a></li>
    51015101                        <li><em>Section 4.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.38">11.3.1</a></li>
    5102                         <li><em>Section 4.2.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.22">8.4</a>, <a href="#rfc.xref.Part1.42">11.4.2</a></li>
     5102                        <li><em>Section 4.2.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.24">9.4</a>, <a href="#rfc.xref.Part1.42">11.4.2</a></li>
    51035103                        <li><em>Section 4.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.39">11.4</a>, <a href="#rfc.xref.Part1.41">11.4.1</a></li>
    5104                         <li><em>Section 4.2.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.23">8.4</a>, <a href="#rfc.xref.Part1.43">11.4.2</a></li>
    5105                         <li><em>Section 4.2.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.24">8.4</a>, <a href="#rfc.xref.Part1.44">11.4.2</a></li>
    5106                         <li><em>Section 4.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.14">5.5</a></li>
    5107                         <li><em>Section 5.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.5">2</a>, <a href="#rfc.xref.Part1.9">4.3.6</a>, <a href="#rfc.xref.Part1.10">4.3.7</a></li>
    5108                         <li><em>Section 5.4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.13">5.1</a></li>
    5109                         <li><em>Section 5.5</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.6">2</a>, <a href="#rfc.xref.Part1.8">3.1</a>, <a href="#rfc.xref.Part1.21">7</a>, <a href="#rfc.xref.Part1.27">10.8</a></li>
    5110                         <li><em>Section 5.7</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.11">4.3.8</a>, <a href="#rfc.xref.Part1.30">10.17</a>, <a href="#rfc.xref.Part1.46">C</a></li>
     5104                        <li><em>Section 4.2.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.25">9.4</a>, <a href="#rfc.xref.Part1.43">11.4.2</a></li>
     5105                        <li><em>Section 4.2.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.26">9.4</a>, <a href="#rfc.xref.Part1.44">11.4.2</a></li>
     5106                        <li><em>Section 4.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.16">6.5</a></li>
     5107                        <li><em>Section 5.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.5">2</a>, <a href="#rfc.xref.Part1.11">5.3.6</a>, <a href="#rfc.xref.Part1.12">5.3.7</a></li>
     5108                        <li><em>Section 5.4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.15">6.1</a></li>
     5109                        <li><em>Section 5.5</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.6">2</a>, <a href="#rfc.xref.Part1.8">3.1</a>, <a href="#rfc.xref.Part1.23">8</a>, <a href="#rfc.xref.Part1.27">10.8</a></li>
     5110                        <li><em>Section 5.7</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.13">5.3.8</a>, <a href="#rfc.xref.Part1.30">10.17</a>, <a href="#rfc.xref.Part1.46">C</a></li>
    51115111                        <li><em>Section 6.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.37">11.3.1</a></li>
    5112                         <li><em>Section 6.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.15">6.2.1</a>, <a href="#rfc.xref.Part1.28">10.11</a></li>
    5113                         <li><em>Section 6.4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.16">6.2.2</a>, <a href="#rfc.xref.Part1.19">6.5.15</a></li>
    5114                         <li><em>Section 7.3.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.12">4.3.8</a></li>
     5112                        <li><em>Section 6.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.17">7.2.1</a>, <a href="#rfc.xref.Part1.28">10.11</a></li>
     5113                        <li><em>Section 6.4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.18">7.2.2</a>, <a href="#rfc.xref.Part1.21">7.5.15</a></li>
     5114                        <li><em>Section 7.3.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.14">5.3.8</a></li>
    51155115                        <li><em>Section 9</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.45">13</a></li>
    51165116                        <li><em>Appendix B</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.34">11.3.1</a></li>
    51175117                     </ul>
    51185118                  </li>
    5119                   <li><em>Part4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part4.1">3.2</a>, <a href="#rfc.xref.Part4.2">3.2</a>, <a href="#rfc.xref.Part4.3">4.3.1</a>, <a href="#rfc.xref.Part4.4">5.2</a>, <a href="#rfc.xref.Part4.5">5.2</a>, <a href="#rfc.xref.Part4.6">5.2</a>, <a href="#rfc.xref.Part4.7">5.2</a>, <a href="#rfc.xref.Part4.8">5.2</a>, <a href="#rfc.xref.Part4.9">6.1</a>, <a href="#rfc.xref.Part4.10">6.1</a>, <a href="#rfc.xref.Part4.11">6.1</a>, <a href="#rfc.xref.Part4.12">6.3.2</a>, <a href="#rfc.xref.Part4.13">6.4</a>, <a href="#rfc.xref.Part4.14">7</a>, <a href="#Part4"><b>14.1</b></a>, <a href="#rfc.xref.Part4.15">F.2</a><ul>
     5119                  <li><em>Part4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part4.1">3.2</a>, <a href="#rfc.xref.Part4.2">3.2</a>, <a href="#rfc.xref.Part4.3">5.3.1</a>, <a href="#rfc.xref.Part4.4">6.2</a>, <a href="#rfc.xref.Part4.5">6.2</a>, <a href="#rfc.xref.Part4.6">6.2</a>, <a href="#rfc.xref.Part4.7">6.2</a>, <a href="#rfc.xref.Part4.8">6.2</a>, <a href="#rfc.xref.Part4.9">7.1</a>, <a href="#rfc.xref.Part4.10">7.1</a>, <a href="#rfc.xref.Part4.11">7.1</a>, <a href="#rfc.xref.Part4.12">7.3.2</a>, <a href="#rfc.xref.Part4.13">7.4</a>, <a href="#rfc.xref.Part4.14">8</a>, <a href="#Part4"><b>14.1</b></a>, <a href="#rfc.xref.Part4.15">F.2</a><ul>
    51205120                        <li><em>Section 2.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part4.2">3.2</a></li>
    5121                         <li><em>Section 2.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part4.1">3.2</a>, <a href="#rfc.xref.Part4.12">6.3.2</a>, <a href="#rfc.xref.Part4.14">7</a></li>
    5122                         <li><em>Section 3.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part4.5">5.2</a></li>
    5123                         <li><em>Section 3.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part4.6">5.2</a></li>
    5124                         <li><em>Section 3.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part4.7">5.2</a></li>
    5125                         <li><em>Section 3.4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part4.8">5.2</a></li>
    5126                         <li><em>Section 4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part4.9">6.1</a></li>
    5127                         <li><em>Section 4.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part4.10">6.1</a>, <a href="#rfc.xref.Part4.13">6.4</a></li>
    5128                         <li><em>Section 4.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part4.11">6.1</a></li>
     5121                        <li><em>Section 2.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part4.1">3.2</a>, <a href="#rfc.xref.Part4.12">7.3.2</a>, <a href="#rfc.xref.Part4.14">8</a></li>
     5122                        <li><em>Section 3.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part4.5">6.2</a></li>
     5123                        <li><em>Section 3.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part4.6">6.2</a></li>
     5124                        <li><em>Section 3.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part4.7">6.2</a></li>
     5125                        <li><em>Section 3.4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part4.8">6.2</a></li>
     5126                        <li><em>Section 4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part4.9">7.1</a></li>
     5127                        <li><em>Section 4.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part4.10">7.1</a>, <a href="#rfc.xref.Part4.13">7.4</a></li>
     5128                        <li><em>Section 4.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part4.11">7.1</a></li>
    51295129                     </ul>
    51305130                  </li>
    5131                   <li><em>Part5</em>&nbsp;&nbsp;<a href="#rfc.xref.Part5.1">4.3.1</a>, <a href="#rfc.xref.Part5.2">4.3.1</a>, <a href="#rfc.xref.Part5.3">4.3.4</a>, <a href="#rfc.xref.Part5.4">5.1</a>, <a href="#rfc.xref.Part5.5">5.2</a>, <a href="#rfc.xref.Part5.6">6.1</a>, <a href="#rfc.xref.Part5.7">6.1</a>, <a href="#rfc.xref.Part5.8">6.1</a>, <a href="#rfc.xref.Part5.9">7</a>, <a href="#rfc.xref.Part5.10">9.1</a>, <a href="#Part5"><b>14.1</b></a><ul>
    5132                         <li><em>Section 3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part5.6">6.1</a></li>
    5133                         <li><em>Section 3.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part5.7">6.1</a></li>
    5134                         <li><em>Section 3.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part5.8">6.1</a></li>
    5135                         <li><em>Section 5.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part5.9">7</a></li>
    5136                         <li><em>Section 5.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part5.3">4.3.4</a>, <a href="#rfc.xref.Part5.10">9.1</a></li>
    5137                         <li><em>Section 5.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part5.5">5.2</a></li>
    5138                         <li><em>Section 5.4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part5.2">4.3.1</a>, <a href="#rfc.xref.Part5.4">5.1</a></li>
     5131                  <li><em>Part5</em>&nbsp;&nbsp;<a href="#rfc.xref.Part5.1">4.1</a>, <a href="#rfc.xref.Part5.2">5.3.1</a>, <a href="#rfc.xref.Part5.3">5.3.1</a>, <a href="#rfc.xref.Part5.4">5.3.4</a>, <a href="#rfc.xref.Part5.5">6.1</a>, <a href="#rfc.xref.Part5.6">6.2</a>, <a href="#rfc.xref.Part5.7">7.1</a>, <a href="#rfc.xref.Part5.8">7.1</a>, <a href="#rfc.xref.Part5.9">7.1</a>, <a href="#rfc.xref.Part5.10">8</a>, <a href="#Part5"><b>14.1</b></a><ul>
     5132                        <li><em>Section 3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part5.7">7.1</a></li>
     5133                        <li><em>Section 3.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part5.8">7.1</a></li>
     5134                        <li><em>Section 3.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part5.9">7.1</a></li>
     5135                        <li><em>Section 5.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part5.10">8</a></li>
     5136                        <li><em>Section 5.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part5.1">4.1</a>, <a href="#rfc.xref.Part5.4">5.3.4</a></li>
     5137                        <li><em>Section 5.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part5.6">6.2</a></li>
     5138                        <li><em>Section 5.4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part5.3">5.3.1</a>, <a href="#rfc.xref.Part5.5">6.1</a></li>
    51395139                     </ul>
    51405140                  </li>
    5141                   <li><em>Part6</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.1">3.2</a>, <a href="#rfc.xref.Part6.2">3.4.1</a>, <a href="#rfc.xref.Part6.3">4.2.3</a>, <a href="#rfc.xref.Part6.4">4.3.1</a>, <a href="#rfc.xref.Part6.5">4.3.2</a>, <a href="#rfc.xref.Part6.6">4.3.3</a>, <a href="#rfc.xref.Part6.7">4.3.4</a>, <a href="#rfc.xref.Part6.8">4.3.5</a>, <a href="#rfc.xref.Part6.9">6.3.1</a>, <a href="#rfc.xref.Part6.10">6.3.4</a>, <a href="#rfc.xref.Part6.11">6.3.4</a>, <a href="#rfc.xref.Part6.12">6.3.4</a>, <a href="#rfc.xref.Part6.13">6.4.1</a>, <a href="#rfc.xref.Part6.14">6.4.2</a>, <a href="#rfc.xref.Part6.15">6.5.9</a>, <a href="#rfc.xref.Part6.16">7</a>, <a href="#rfc.xref.Part6.17">7</a>, <a href="#rfc.xref.Part6.18">11.2.2</a>, <a href="#rfc.xref.Part6.19">11.3.1</a>, <a href="#Part6"><b>14.1</b></a><ul>
    5142                         <li><em>Section 4.1.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.6">4.3.3</a></li>
    5143                         <li><em>Section 4.1.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.9">6.3.1</a>, <a href="#rfc.xref.Part6.12">6.3.4</a>, <a href="#rfc.xref.Part6.13">6.4.1</a>, <a href="#rfc.xref.Part6.14">6.4.2</a>, <a href="#rfc.xref.Part6.15">6.5.9</a></li>
    5144                         <li><em>Section 5</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.5">4.3.2</a></li>
    5145                         <li><em>Section 6</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.7">4.3.4</a>, <a href="#rfc.xref.Part6.8">4.3.5</a></li>
    5146                         <li><em>Section 7.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.16">7</a></li>
    5147                         <li><em>Section 7.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.10">6.3.4</a></li>
     5141                  <li><em>Part6</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.1">3.2</a>, <a href="#rfc.xref.Part6.2">3.4.1</a>, <a href="#rfc.xref.Part6.3">5.2.3</a>, <a href="#rfc.xref.Part6.4">5.3.1</a>, <a href="#rfc.xref.Part6.5">5.3.2</a>, <a href="#rfc.xref.Part6.6">5.3.3</a>, <a href="#rfc.xref.Part6.7">5.3.4</a>, <a href="#rfc.xref.Part6.8">5.3.5</a>, <a href="#rfc.xref.Part6.9">7.3.1</a>, <a href="#rfc.xref.Part6.10">7.3.4</a>, <a href="#rfc.xref.Part6.11">7.3.4</a>, <a href="#rfc.xref.Part6.12">7.3.4</a>, <a href="#rfc.xref.Part6.13">7.4.1</a>, <a href="#rfc.xref.Part6.14">7.4.2</a>, <a href="#rfc.xref.Part6.15">7.5.9</a>, <a href="#rfc.xref.Part6.16">8</a>, <a href="#rfc.xref.Part6.17">8</a>, <a href="#rfc.xref.Part6.18">11.2.2</a>, <a href="#rfc.xref.Part6.19">11.3.1</a>, <a href="#Part6"><b>14.1</b></a><ul>
     5142                        <li><em>Section 4.1.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.6">5.3.3</a></li>
     5143                        <li><em>Section 4.1.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.9">7.3.1</a>, <a href="#rfc.xref.Part6.12">7.3.4</a>, <a href="#rfc.xref.Part6.13">7.4.1</a>, <a href="#rfc.xref.Part6.14">7.4.2</a>, <a href="#rfc.xref.Part6.15">7.5.9</a></li>
     5144                        <li><em>Section 5</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.5">5.3.2</a></li>
     5145                        <li><em>Section 6</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.7">5.3.4</a>, <a href="#rfc.xref.Part6.8">5.3.5</a></li>
     5146                        <li><em>Section 7.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.16">8</a></li>
     5147                        <li><em>Section 7.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.10">7.3.4</a></li>
    51485148                        <li><em>Section 7.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.1">3.2</a></li>
    5149                         <li><em>Section 7.5</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.2">3.4.1</a>, <a href="#rfc.xref.Part6.17">7</a></li>
    5150                         <li><em>Section 7.6</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.11">6.3.4</a></li>
     5149                        <li><em>Section 7.5</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.2">3.4.1</a>, <a href="#rfc.xref.Part6.17">8</a></li>
     5150                        <li><em>Section 7.6</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.11">7.3.4</a></li>
    51515151                     </ul>
    51525152                  </li>
    5153                   <li><em>Part7</em>&nbsp;&nbsp;<a href="#rfc.xref.Part7.1">5.4</a>, <a href="#rfc.xref.Part7.2">5.4</a>, <a href="#rfc.xref.Part7.3">6.1</a>, <a href="#rfc.xref.Part7.4">6.1</a>, <a href="#rfc.xref.Part7.5">6.1</a>, <a href="#rfc.xref.Part7.6">7</a>, <a href="#rfc.xref.Part7.7">7</a>, <a href="#Part7"><b>14.1</b></a><ul>
    5154                         <li><em>Section 3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part7.3">6.1</a></li>
    5155                         <li><em>Section 3.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part7.4">6.1</a></li>
    5156                         <li><em>Section 3.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part7.5">6.1</a></li>
    5157                         <li><em>Section 4.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part7.1">5.4</a></li>
    5158                         <li><em>Section 4.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part7.6">7</a></li>
    5159                         <li><em>Section 4.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part7.2">5.4</a></li>
    5160                         <li><em>Section 4.4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part7.7">7</a></li>
     5153                  <li><em>Part7</em>&nbsp;&nbsp;<a href="#rfc.xref.Part7.1">6.4</a>, <a href="#rfc.xref.Part7.2">6.4</a>, <a href="#rfc.xref.Part7.3">7.1</a>, <a href="#rfc.xref.Part7.4">7.1</a>, <a href="#rfc.xref.Part7.5">7.1</a>, <a href="#rfc.xref.Part7.6">8</a>, <a href="#rfc.xref.Part7.7">8</a>, <a href="#Part7"><b>14.1</b></a><ul>
     5154                        <li><em>Section 3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part7.3">7.1</a></li>
     5155                        <li><em>Section 3.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part7.4">7.1</a></li>
     5156                        <li><em>Section 3.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part7.5">7.1</a></li>
     5157                        <li><em>Section 4.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part7.1">6.4</a></li>
     5158                        <li><em>Section 4.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part7.6">8</a></li>
     5159                        <li><em>Section 4.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part7.2">6.4</a></li>
     5160                        <li><em>Section 4.4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part7.7">8</a></li>
    51615161                     </ul>
    51625162                  </li>
    5163                   <li>payload&nbsp;&nbsp;<a href="#rfc.iref.p.3">9</a></li>
    5164                   <li>POST method&nbsp;&nbsp;<a href="#rfc.xref.POST.1">4.1</a>, <a href="#rfc.iref.p.1"><b>4.3.3</b></a>, <a href="#rfc.xref.POST.2">11.1.3</a>, <a href="#rfc.xref.POST.3">C</a></li>
    5165                   <li>PUT method&nbsp;&nbsp;<a href="#rfc.xref.PUT.1">4.1</a>, <a href="#rfc.iref.p.2"><b>4.3.4</b></a>, <a href="#rfc.xref.PUT.2">11.1.3</a>, <a href="#rfc.xref.PUT.3">C</a></li>
     5163                  <li>payload&nbsp;&nbsp;<a href="#rfc.iref.p.1">4</a></li>
     5164                  <li>POST method&nbsp;&nbsp;<a href="#rfc.xref.POST.1">5.1</a>, <a href="#rfc.iref.p.2"><b>5.3.3</b></a>, <a href="#rfc.xref.POST.2">11.1.3</a>, <a href="#rfc.xref.POST.3">C</a></li>
     5165                  <li>PUT method&nbsp;&nbsp;<a href="#rfc.xref.PUT.1">5.1</a>, <a href="#rfc.iref.p.3"><b>5.3.4</b></a>, <a href="#rfc.xref.PUT.2">11.1.3</a>, <a href="#rfc.xref.PUT.3">C</a></li>
    51665166               </ul>
    51675167            </li>
    51685168            <li><a id="rfc.index.R" href="#rfc.index.R"><b>R</b></a><ul>
    5169                   <li>Referer header field&nbsp;&nbsp;<a href="#rfc.xref.header.referer.1">5.5</a>, <a href="#rfc.iref.r.2"><b>10.15</b></a>, <a href="#rfc.xref.header.referer.2">11.3.2</a>, <a href="#rfc.xref.header.referer.3">C</a></li>
     5169                  <li>Referer header field&nbsp;&nbsp;<a href="#rfc.xref.header.referer.1">6.5</a>, <a href="#rfc.iref.r.2"><b>10.15</b></a>, <a href="#rfc.xref.header.referer.2">11.3.2</a>, <a href="#rfc.xref.header.referer.3">C</a></li>
    51705170                  <li>representation&nbsp;&nbsp;<a href="#rfc.iref.r.1">3</a></li>
    5171                   <li><em>REST</em>&nbsp;&nbsp;<a href="#rfc.xref.REST.1">4.1</a>, <a href="#REST"><b>14.2</b></a></li>
    5172                   <li>Retry-After header field&nbsp;&nbsp;<a href="#rfc.xref.header.retry-after.1">6.6.4</a>, <a href="#rfc.xref.header.retry-after.2">7</a>, <a href="#rfc.iref.r.3"><b>10.16</b></a>, <a href="#rfc.xref.header.retry-after.3">11.3.2</a></li>
    5173                   <li><em>RFC1123</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC1123.1">8.1</a>, <a href="#rfc.xref.RFC1123.2">8.1</a>, <a href="#RFC1123"><b>14.2</b></a><ul>
    5174                         <li><em>Section 5.2.14</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC1123.2">8.1</a></li>
     5171                  <li><em>REST</em>&nbsp;&nbsp;<a href="#rfc.xref.REST.1">5.1</a>, <a href="#REST"><b>14.2</b></a></li>
     5172                  <li>Retry-After header field&nbsp;&nbsp;<a href="#rfc.xref.header.retry-after.1">7.6.4</a>, <a href="#rfc.xref.header.retry-after.2">8</a>, <a href="#rfc.iref.r.3"><b>10.16</b></a>, <a href="#rfc.xref.header.retry-after.3">11.3.2</a></li>
     5173                  <li><em>RFC1123</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC1123.1">9.1</a>, <a href="#rfc.xref.RFC1123.2">9.1</a>, <a href="#RFC1123"><b>14.2</b></a><ul>
     5174                        <li><em>Section 5.2.14</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC1123.2">9.1</a></li>
    51755175                     </ul>
    51765176                  </li>
    5177                   <li><em>RFC1945</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC1945.1">6.4</a>, <a href="#RFC1945"><b>14.2</b></a>, <a href="#rfc.xref.RFC1945.2">B</a><ul>
    5178                         <li><em>Section 9.3</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC1945.1">6.4</a></li>
     5177                  <li><em>RFC1945</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC1945.1">7.4</a>, <a href="#RFC1945"><b>14.2</b></a>, <a href="#rfc.xref.RFC1945.2">B</a><ul>
     5178                        <li><em>Section 9.3</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC1945.1">7.4</a></li>
    51795179                     </ul>
    51805180                  </li>
    … …  
    51835183                  <li><em>RFC1952</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC1952.1">11.4.2</a>, <a href="#RFC1952"><b>14.1</b></a></li>
    51845184                  <li><em>RFC2045</em>&nbsp;&nbsp;<a href="#RFC2045"><b>14.1</b></a>, <a href="#rfc.xref.RFC2045.1">A</a>, <a href="#rfc.xref.RFC2045.2">A.1</a></li>
    5185                   <li><em>RFC2046</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2046.1">3.3</a>, <a href="#rfc.xref.RFC2046.2">8.5</a>, <a href="#rfc.xref.RFC2046.3">8.5.2</a>, <a href="#RFC2046"><b>14.1</b></a>, <a href="#rfc.xref.RFC2046.4">A.2</a><ul>
     5185                  <li><em>RFC2046</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2046.1">3.3</a>, <a href="#rfc.xref.RFC2046.2">9.5</a>, <a href="#rfc.xref.RFC2046.3">9.5.2</a>, <a href="#RFC2046"><b>14.1</b></a>, <a href="#rfc.xref.RFC2046.4">A.2</a><ul>
    51865186                        <li><em>Section 4.5.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2046.1">3.3</a></li>
    5187                         <li><em>Section 5.1.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2046.3">8.5.2</a></li>
     5187                        <li><em>Section 5.1.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2046.3">9.5.2</a></li>
    51885188                     </ul>
    51895189                  </li>
    … …  
    51925192                     </ul>
    51935193                  </li>
    5194                   <li><em>RFC2068</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2068.1">6.4</a>, <a href="#rfc.xref.RFC2068.2">6.4</a>, <a href="#RFC2068"><b>14.2</b></a>, <a href="#rfc.xref.RFC2068.3">B</a><ul>
    5195                         <li><em>Section 10.3</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2068.2">6.4</a></li>
    5196                         <li><em>Section 10.3.4</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2068.1">6.4</a></li>
     5194                  <li><em>RFC2068</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2068.1">7.4</a>, <a href="#rfc.xref.RFC2068.2">7.4</a>, <a href="#RFC2068"><b>14.2</b></a>, <a href="#rfc.xref.RFC2068.3">B</a><ul>
     5195                        <li><em>Section 10.3</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2068.2">7.4</a></li>
     5196                        <li><em>Section 10.3.4</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2068.1">7.4</a></li>
    51975197                     </ul>
    51985198                  </li>
    51995199                  <li><em>RFC2076</em>&nbsp;&nbsp;<a href="#RFC2076"><b>14.2</b></a>, <a href="#rfc.xref.RFC2076.1">B</a></li>
    52005200                  <li><em>RFC2119</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2119.1">1.1</a>, <a href="#RFC2119"><b>14.1</b></a></li>
    5201                   <li><em>RFC2277</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2277.1">8.3</a>, <a href="#RFC2277"><b>14.2</b></a></li>
     5201                  <li><em>RFC2277</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2277.1">9.3</a>, <a href="#RFC2277"><b>14.2</b></a></li>
    52025202                  <li><em>RFC2295</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2295.1">3.4</a>, <a href="#RFC2295"><b>14.2</b></a></li>
    5203                   <li><em>RFC2388</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2388.1">8.5.2</a>, <a href="#RFC2388"><b>14.2</b></a></li>
     5203                  <li><em>RFC2388</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2388.1">9.5.2</a>, <a href="#RFC2388"><b>14.2</b></a></li>
    52045204                  <li><em>RFC2557</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2557.1">10.8</a>, <a href="#RFC2557"><b>14.2</b></a>, <a href="#rfc.xref.RFC2557.2">A.6</a><ul>
    52055205                        <li><em>Section 4</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2557.1">10.8</a></li>
    52065206                     </ul>
    52075207                  </li>
    5208                   <li><em>RFC2616</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2616.1">6.4</a>, <a href="#rfc.xref.RFC2616.2">10.4</a>, <a href="#RFC2616"><b>14.2</b></a>, <a href="#rfc.xref.RFC2616.3">F.1</a><ul>
    5209                         <li><em>Section 10.3.8</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2616.1">6.4</a></li>
     5208                  <li><em>RFC2616</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2616.1">7.4</a>, <a href="#rfc.xref.RFC2616.2">10.4</a>, <a href="#RFC2616"><b>14.2</b></a>, <a href="#rfc.xref.RFC2616.3">F.1</a><ul>
     5209                        <li><em>Section 10.3.8</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2616.1">7.4</a></li>
    52105210                        <li><em>Section 14.4</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2616.2">10.4</a></li>
    52115211                     </ul>
    … …  
    52155215                     </ul>
    52165216                  </li>
    5217                   <li><em>RFC3629</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC3629.1">8.3</a>, <a href="#RFC3629"><b>14.2</b></a></li>
     5217                  <li><em>RFC3629</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC3629.1">9.3</a>, <a href="#RFC3629"><b>14.2</b></a></li>
    52185218                  <li><em>RFC3864</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC3864.1">11.3</a>, <a href="#rfc.xref.RFC3864.2">11.3.1</a>, <a href="#RFC3864"><b>14.2</b></a><ul>
    52195219                        <li><em>Section 4.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC3864.2">11.3.1</a></li>
    … …  
    52255225                     </ul>
    52265226                  </li>
    5227                   <li><em>RFC4288</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC4288.1">8.5</a>, <a href="#RFC4288"><b>14.2</b></a></li>
     5227                  <li><em>RFC4288</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC4288.1">9.5</a>, <a href="#RFC4288"><b>14.2</b></a></li>
    52285228                  <li><em>RFC4647</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC4647.1">10.4</a>, <a href="#rfc.xref.RFC4647.2">10.4</a>, <a href="#rfc.xref.RFC4647.3">10.4</a>, <a href="#rfc.xref.RFC4647.4">10.4</a>, <a href="#RFC4647"><b>14.1</b></a><ul>
    52295229                        <li><em>Section 2.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC4647.1">10.4</a></li>
    … …  
    52415241                     </ul>
    52425242                  </li>
    5243                   <li><em>RFC5322</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5322.1">8.1</a>, <a href="#rfc.xref.RFC5322.2">10.10</a>, <a href="#rfc.xref.RFC5322.3">10.12</a>, <a href="#rfc.xref.RFC5322.4">10.12</a>, <a href="#RFC5322"><b>14.2</b></a>, <a href="#rfc.xref.RFC5322.5">A</a><ul>
    5244                         <li><em>Section 3.3</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5322.1">8.1</a></li>
     5243                  <li><em>RFC5322</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5322.1">9.1</a>, <a href="#rfc.xref.RFC5322.2">10.10</a>, <a href="#rfc.xref.RFC5322.3">10.12</a>, <a href="#rfc.xref.RFC5322.4">10.12</a>, <a href="#RFC5322"><b>14.2</b></a>, <a href="#rfc.xref.RFC5322.5">A</a><ul>
     5244                        <li><em>Section 3.3</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5322.1">9.1</a></li>
    52455245                        <li><em>Section 3.4</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5322.3">10.12</a>, <a href="#rfc.xref.RFC5322.4">10.12</a></li>
    52465246                        <li><em>Section 3.6.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5322.2">10.10</a></li>
    52475247                     </ul>
    52485248                  </li>
    5249                   <li><em>RFC5646</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5646.1">8.6</a>, <a href="#rfc.xref.RFC5646.2">8.6</a>, <a href="#rfc.xref.RFC5646.3">8.6</a>, <a href="#RFC5646"><b>14.1</b></a><ul>
    5250                         <li><em>Section 2.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5646.2">8.6</a></li>
     5249                  <li><em>RFC5646</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5646.1">9.6</a>, <a href="#rfc.xref.RFC5646.2">9.6</a>, <a href="#rfc.xref.RFC5646.3">9.6</a>, <a href="#RFC5646"><b>14.1</b></a><ul>
     5250                        <li><em>Section 2.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5646.2">9.6</a></li>
    52515251                     </ul>
    52525252                  </li>
    5253                   <li><em>RFC5789</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5789.1">4.3.4</a>, <a href="#RFC5789"><b>14.2</b></a></li>
     5253                  <li><em>RFC5789</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5789.1">5.3.4</a>, <a href="#RFC5789"><b>14.2</b></a></li>
    52545254                  <li><em>RFC5987</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5987.1">11.3.1</a>, <a href="#RFC5987"><b>14.2</b></a></li>
    52555255                  <li><em>RFC6151</em>&nbsp;&nbsp;<a href="#RFC6151"><b>14.2</b></a>, <a href="#rfc.xref.RFC6151.1">C</a></li>
    … …  
    52585258            </li>
    52595259            <li><a id="rfc.index.S" href="#rfc.index.S"><b>S</b></a><ul>
    5260                   <li>safe&nbsp;&nbsp;<a href="#rfc.iref.s.2"><b>4.2.1</b></a></li>
     5260                  <li>safe&nbsp;&nbsp;<a href="#rfc.iref.s.2"><b>5.2.1</b></a></li>
    52615261                  <li>selected representation&nbsp;&nbsp;<a href="#rfc.iref.s.1"><b>3.2</b></a></li>
    5262                   <li>Server header field&nbsp;&nbsp;<a href="#rfc.xref.header.server.1">7</a>, <a href="#rfc.iref.s.44"><b>10.17</b></a>, <a href="#rfc.xref.header.server.2">11.3.2</a>, <a href="#rfc.xref.header.server.3">12.1</a>, <a href="#rfc.xref.header.server.4">C</a></li>
     5262                  <li>Server header field&nbsp;&nbsp;<a href="#rfc.xref.header.server.1">8</a>, <a href="#rfc.iref.s.44"><b>10.17</b></a>, <a href="#rfc.xref.header.server.2">11.3.2</a>, <a href="#rfc.xref.header.server.3">12.1</a>, <a href="#rfc.xref.header.server.4">C</a></li>
    52635263                  <li>Status Codes&nbsp;&nbsp;
    52645264                     <ul>
    5265                         <li>100 Continue&nbsp;&nbsp;<a href="#rfc.xref.status.100.1">6.1</a>, <a href="#rfc.iref.s.4"><b>6.2.1</b></a>, <a href="#rfc.xref.status.100.2">11.2.3</a></li>
    5266                         <li>101 Switching Protocols&nbsp;&nbsp;<a href="#rfc.xref.status.101.1">6.1</a>, <a href="#rfc.iref.s.5"><b>6.2.2</b></a>, <a href="#rfc.xref.status.101.2">11.2.3</a></li>
    5267                         <li>200 OK&nbsp;&nbsp;<a href="#rfc.xref.status.200.1">6.1</a>, <a href="#rfc.iref.s.7"><b>6.3.1</b></a>, <a href="#rfc.xref.status.200.2">11.2.3</a></li>
    5268                         <li>201 Created&nbsp;&nbsp;<a href="#rfc.xref.status.201.1">6.1</a>, <a href="#rfc.iref.s.8"><b>6.3.2</b></a>, <a href="#rfc.xref.status.201.2">11.2.3</a></li>
    5269                         <li>202 Accepted&nbsp;&nbsp;<a href="#rfc.xref.status.202.1">6.1</a>, <a href="#rfc.iref.s.9"><b>6.3.3</b></a>, <a href="#rfc.xref.status.202.2">11.2.3</a></li>
    5270                         <li>203 Non-Authoritative Information&nbsp;&nbsp;<a href="#rfc.xref.status.203.1">6.1</a>, <a href="#rfc.iref.s.10"><b>6.3.4</b></a>, <a href="#rfc.xref.status.203.2">11.2.3</a>, <a href="#rfc.xref.status.203.3">C</a></li>
    5271                         <li>204 No Content&nbsp;&nbsp;<a href="#rfc.xref.status.204.1">6.1</a>, <a href="#rfc.iref.s.11"><b>6.3.5</b></a>, <a href="#rfc.xref.status.204.2">11.2.3</a></li>
    5272                         <li>205 Reset Content&nbsp;&nbsp;<a href="#rfc.xref.status.205.1">6.1</a>, <a href="#rfc.iref.s.12"><b>6.3.6</b></a>, <a href="#rfc.xref.status.205.2">11.2.3</a></li>
    5273                         <li>300 Multiple Choices&nbsp;&nbsp;<a href="#rfc.xref.status.300.1">6.1</a>, <a href="#rfc.iref.s.14"><b>6.4.1</b></a>, <a href="#rfc.xref.status.300.2">11.2.3</a></li>
    5274                         <li>301 Moved Permanently&nbsp;&nbsp;<a href="#rfc.xref.status.301.1">6.1</a>, <a href="#rfc.iref.s.15"><b>6.4.2</b></a>, <a href="#rfc.xref.status.301.2">11.2.3</a>, <a href="#rfc.xref.status.301.3">C</a></li>
    5275                         <li>302 Found&nbsp;&nbsp;<a href="#rfc.xref.status.302.1">6.1</a>, <a href="#rfc.iref.s.16"><b>6.4.3</b></a>, <a href="#rfc.xref.status.302.2">11.2.3</a>, <a href="#rfc.xref.status.302.3">C</a></li>
    5276                         <li>303 See Other&nbsp;&nbsp;<a href="#rfc.xref.status.303.1">6.1</a>, <a href="#rfc.iref.s.17"><b>6.4.4</b></a>, <a href="#rfc.xref.status.303.2">11.2.3</a></li>
    5277                         <li>305 Use Proxy&nbsp;&nbsp;<a href="#rfc.xref.status.305.1">6.1</a>, <a href="#rfc.iref.s.18"><b>6.4.5</b></a>, <a href="#rfc.xref.status.305.2">11.2.3</a>, <a href="#rfc.xref.status.305.3">C</a></li>
    5278                         <li>306 (Unused)&nbsp;&nbsp;<a href="#rfc.iref.s.19"><b>6.4.6</b></a>, <a href="#rfc.xref.status.306.1">11.2.3</a></li>
    5279                         <li>307 Temporary Redirect&nbsp;&nbsp;<a href="#rfc.xref.status.307.1">6.1</a>, <a href="#rfc.iref.s.20"><b>6.4.7</b></a>, <a href="#rfc.xref.status.307.2">11.2.3</a>, <a href="#rfc.xref.status.307.3">C</a></li>
    5280                         <li>400 Bad Request&nbsp;&nbsp;<a href="#rfc.xref.status.400.1">6.1</a>, <a href="#rfc.iref.s.22"><b>6.5.1</b></a>, <a href="#rfc.xref.status.400.2">11.2.3</a></li>
    5281                         <li>402 Payment Required&nbsp;&nbsp;<a href="#rfc.xref.status.402.1">6.1</a>, <a href="#rfc.iref.s.23"><b>6.5.2</b></a>, <a href="#rfc.xref.status.402.2">11.2.3</a></li>
    5282                         <li>403 Forbidden&nbsp;&nbsp;<a href="#rfc.xref.status.403.1">6.1</a>, <a href="#rfc.iref.s.24"><b>6.5.3</b></a>, <a href="#rfc.xref.status.403.2">11.2.3</a></li>
    5283                         <li>404 Not Found&nbsp;&nbsp;<a href="#rfc.xref.status.404.1">6.1</a>, <a href="#rfc.iref.s.25"><b>6.5.4</b></a>, <a href="#rfc.xref.status.404.2">11.2.3</a></li>
    5284                         <li>405 Method Not Allowed&nbsp;&nbsp;<a href="#rfc.xref.status.405.1">6.1</a>, <a href="#rfc.iref.s.26"><b>6.5.5</b></a>, <a href="#rfc.xref.status.405.2">11.2.3</a></li>
    5285                         <li>406 Not Acceptable&nbsp;&nbsp;<a href="#rfc.xref.status.406.1">6.1</a>, <a href="#rfc.iref.s.27"><b>6.5.6</b></a>, <a href="#rfc.xref.status.406.2">11.2.3</a></li>
    5286                         <li>408 Request Timeout&nbsp;&nbsp;<a href="#rfc.xref.status.408.1">6.1</a>, <a href="#rfc.iref.s.28"><b>6.5.7</b></a>, <a href="#rfc.xref.status.408.2">11.2.3</a></li>
    5287                         <li>409 Conflict&nbsp;&nbsp;<a href="#rfc.xref.status.409.1">6.1</a>, <a href="#rfc.iref.s.29"><b>6.5.8</b></a>, <a href="#rfc.xref.status.409.2">11.2.3</a></li>
    5288                         <li>410 Gone&nbsp;&nbsp;<a href="#rfc.xref.status.410.1">6.1</a>, <a href="#rfc.iref.s.30"><b>6.5.9</b></a>, <a href="#rfc.xref.status.410.2">11.2.3</a></li>
    5289                         <li>411 Length Required&nbsp;&nbsp;<a href="#rfc.xref.status.411.1">6.1</a>, <a href="#rfc.iref.s.31"><b>6.5.10</b></a>, <a href="#rfc.xref.status.411.2">11.2.3</a></li>
    5290                         <li>413 Request Representation Too Large&nbsp;&nbsp;<a href="#rfc.xref.status.413.1">6.1</a>, <a href="#rfc.iref.s.32"><b>6.5.11</b></a>, <a href="#rfc.xref.status.413.2">11.2.3</a></li>
    5291                         <li>414 URI Too Long&nbsp;&nbsp;<a href="#rfc.xref.status.414.1">6.1</a>, <a href="#rfc.iref.s.33"><b>6.5.12</b></a>, <a href="#rfc.xref.status.414.2">11.2.3</a></li>
    5292                         <li>415 Unsupported Media Type&nbsp;&nbsp;<a href="#rfc.xref.status.415.1">6.1</a>, <a href="#rfc.iref.s.34"><b>6.5.13</b></a>, <a href="#rfc.xref.status.415.2">11.2.3</a></li>
    5293                         <li>417 Expectation Failed&nbsp;&nbsp;<a href="#rfc.xref.status.417.1">6.1</a>, <a href="#rfc.iref.s.35"><b>6.5.14</b></a>, <a href="#rfc.xref.status.417.2">11.2.3</a></li>
    5294                         <li>426 Upgrade Required&nbsp;&nbsp;<a href="#rfc.xref.status.426.1">6.1</a>, <a href="#rfc.iref.s.36"><b>6.5.15</b></a>, <a href="#rfc.xref.status.426.2">11.2.3</a>, <a href="#rfc.xref.status.426.3">C</a></li>
    5295                         <li>500 Internal Server Error&nbsp;&nbsp;<a href="#rfc.xref.status.500.1">6.1</a>, <a href="#rfc.iref.s.38"><b>6.6.1</b></a>, <a href="#rfc.xref.status.500.2">11.2.3</a></li>
    5296                         <li>501 Not Implemented&nbsp;&nbsp;<a href="#rfc.xref.status.501.1">6.1</a>, <a href="#rfc.iref.s.39"><b>6.6.2</b></a>, <a href="#rfc.xref.status.501.2">11.2.3</a></li>
    5297                         <li>502 Bad Gateway&nbsp;&nbsp;<a href="#rfc.xref.status.502.1">6.1</a>, <a href="#rfc.iref.s.40"><b>6.6.3</b></a>, <a href="#rfc.xref.status.502.2">11.2.3</a></li>
    5298                         <li>503 Service Unavailable&nbsp;&nbsp;<a href="#rfc.xref.status.503.1">6.1</a>, <a href="#rfc.iref.s.41"><b>6.6.4</b></a>, <a href="#rfc.xref.status.503.2">11.2.3</a></li>
    5299                         <li>504 Gateway Timeout&nbsp;&nbsp;<a href="#rfc.xref.status.504.1">6.1</a>, <a href="#rfc.iref.s.42"><b>6.6.5</b></a>, <a href="#rfc.xref.status.504.2">11.2.3</a></li>
    5300                         <li>505 HTTP Version Not Supported&nbsp;&nbsp;<a href="#rfc.xref.status.505.1">6.1</a>, <a href="#rfc.iref.s.43"><b>6.6.6</b></a>, <a href="#rfc.xref.status.505.2">11.2.3</a></li>
     5265                        <li>100 Continue&nbsp;&nbsp;<a href="#rfc.xref.status.100.1">7.1</a>, <a href="#rfc.iref.s.4"><b>7.2.1</b></a>, <a href="#rfc.xref.status.100.2">11.2.3</a></li>
     5266                        <li>101 Switching Protocols&nbsp;&nbsp;<a href="#rfc.xref.status.101.1">7.1</a>, <a href="#rfc.iref.s.5"><b>7.2.2</b></a>, <a href="#rfc.xref.status.101.2">11.2.3</a></li>
     5267                        <li>200 OK&nbsp;&nbsp;<a href="#rfc.xref.status.200.1">7.1</a>, <a href="#rfc.iref.s.7"><b>7.3.1</b></a>, <a href="#rfc.xref.status.200.2">11.2.3</a></li>
     5268                        <li>201 Created&nbsp;&nbsp;<a href="#rfc.xref.status.201.1">7.1</a>, <a href="#rfc.iref.s.8"><b>7.3.2</b></a>, <a href="#rfc.xref.status.201.2">11.2.3</a></li>
     5269                        <li>202 Accepted&nbsp;&nbsp;<a href="#rfc.xref.status.202.1">7.1</a>, <a href="#rfc.iref.s.9"><b>7.3.3</b></a>, <a href="#rfc.xref.status.202.2">11.2.3</a></li>
     5270                        <li>203 Non-Authoritative Information&nbsp;&nbsp;<a href="#rfc.xref.status.203.1">7.1</a>, <a href="#rfc.iref.s.10"><b>7.3.4</b></a>, <a href="#rfc.xref.status.203.2">11.2.3</a>, <a href="#rfc.xref.status.203.3">C</a></li>
     5271                        <li>204 No Content&nbsp;&nbsp;<a href="#rfc.xref.status.204.1">7.1</a>, <a href="#rfc.iref.s.11"><b>7.3.5</b></a>, <a href="#rfc.xref.status.204.2">11.2.3</a></li>
     5272                        <li>205 Reset Content&nbsp;&nbsp;<a href="#rfc.xref.status.205.1">7.1</a>, <a href="#rfc.iref.s.12"><b>7.3.6</b></a>, <a href="#rfc.xref.status.205.2">11.2.3</a></li>
     5273                        <li>300 Multiple Choices&nbsp;&nbsp;<a href="#rfc.xref.status.300.1">7.1</a>, <a href="#rfc.iref.s.14"><b>7.4.1</b></a>, <a href="#rfc.xref.status.300.2">11.2.3</a></li>
     5274                        <li>301 Moved Permanently&nbsp;&nbsp;<a href="#rfc.xref.status.301.1">7.1</a>, <a href="#rfc.iref.s.15"><b>7.4.2</b></a>, <a href="#rfc.xref.status.301.2">11.2.3</a>, <a href="#rfc.xref.status.301.3">C</a></li>
     5275                        <li>302 Found&nbsp;&nbsp;<a href="#rfc.xref.status.302.1">7.1</a>, <a href="#rfc.iref.s.16"><b>7.4.3</b></a>, <a href="#rfc.xref.status.302.2">11.2.3</a>, <a href="#rfc.xref.status.302.3">C</a></li>
     5276                        <li>303 See Other&nbsp;&nbsp;<a href="#rfc.xref.status.303.1">7.1</a>, <a href="#rfc.iref.s.17"><b>7.4.4</b></a>, <a href="#rfc.xref.status.303.2">11.2.3</a></li>
     5277                        <li>305 Use Proxy&nbsp;&nbsp;<a href="#rfc.xref.status.305.1">7.1</a>, <a href="#rfc.iref.s.18"><b>7.4.5</b></a>, <a href="#rfc.xref.status.305.2">11.2.3</a>, <a href="#rfc.xref.status.305.3">C</a></li>
     5278                        <li>306 (Unused)&nbsp;&nbsp;<a href="#rfc.iref.s.19"><b>7.4.6</b></a>, <a href="#rfc.xref.status.306.1">11.2.3</a></li>
     5279                        <li>307 Temporary Redirect&nbsp;&nbsp;<a href="#rfc.xref.status.307.1">7.1</a>, <a href="#rfc.iref.s.20"><b>7.4.7</b></a>, <a href="#rfc.xref.status.307.2">11.2.3</a>, <a href="#rfc.xref.status.307.3">C</a></li>
     5280                        <li>400 Bad Request&nbsp;&nbsp;<a href="#rfc.xref.status.400.1">7.1</a>, <a href="#rfc.iref.s.22"><b>7.5.1</b></a>, <a href="#rfc.xref.status.400.2">11.2.3</a></li>
     5281                        <li>402 Payment Required&nbsp;&nbsp;<a href="#rfc.xref.status.402.1">7.1</a>, <a href="#rfc.iref.s.23"><b>7.5.2</b></a>, <a href="#rfc.xref.status.402.2">11.2.3</a></li>
     5282                        <li>403 Forbidden&nbsp;&nbsp;<a href="#rfc.xref.status.403.1">7.1</a>, <a href="#rfc.iref.s.24"><b>7.5.3</b></a>, <a href="#rfc.xref.status.403.2">11.2.3</a></li>
     5283                        <li>404 Not Found&nbsp;&nbsp;<a href="#rfc.xref.status.404.1">7.1</a>, <a href="#rfc.iref.s.25"><b>7.5.4</b></a>, <a href="#rfc.xref.status.404.2">11.2.3</a></li>
     5284                        <li>405 Method Not Allowed&nbsp;&nbsp;<a href="#rfc.xref.status.405.1">7.1</a>, <a href="#rfc.iref.s.26"><b>7.5.5</b></a>, <a href="#rfc.xref.status.405.2">11.2.3</a></li>
     5285                        <li>406 Not Acceptable&nbsp;&nbsp;<a href="#rfc.xref.status.406.1">7.1</a>, <a href="#rfc.iref.s.27"><b>7.5.6</b></a>, <a href="#rfc.xref.status.406.2">11.2.3</a></li>
     5286                        <li>408 Request Timeout&nbsp;&nbsp;<a href="#rfc.xref.status.408.1">7.1</a>, <a href="#rfc.iref.s.28"><b>7.5.7</b></a>, <a href="#rfc.xref.status.408.2">11.2.3</a></li>
     5287                        <li>409 Conflict&nbsp;&nbsp;<a href="#rfc.xref.status.409.1">7.1</a>, <a href="#rfc.iref.s.29"><b>7.5.8</b></a>, <a href="#rfc.xref.status.409.2">11.2.3</a></li>
     5288                        <li>410 Gone&nbsp;&nbsp;<a href="#rfc.xref.status.410.1">7.1</a>, <a href="#rfc.iref.s.30"><b>7.5.9</b></a>, <a href="#rfc.xref.status.410.2">11.2.3</a></li>
     5289                        <li>411 Length Required&nbsp;&nbsp;<a href="#rfc.xref.status.411.1">7.1</a>, <a href="#rfc.iref.s.31"><b>7.5.10</b></a>, <a href="#rfc.xref.status.411.2">11.2.3</a></li>
     5290                        <li>413 Request Representation Too Large&nbsp;&nbsp;<a href="#rfc.xref.status.413.1">7.1</a>, <a href="#rfc.iref.s.32"><b>7.5.11</b></a>, <a href="#rfc.xref.status.413.2">11.2.3</a></li>
     5291                        <li>414 URI Too Long&nbsp;&nbsp;<a href="#rfc.xref.status.414.1">7.1</a>, <a href="#rfc.iref.s.33"><b>7.5.12</b></a>, <a href="#rfc.xref.status.414.2">11.2.3</a></li>
     5292                        <li>415 Unsupported Media Type&nbsp;&nbsp;<a href="#rfc.xref.status.415.1">7.1</a>, <a href="#rfc.iref.s.34"><b>7.5.13</b></a>, <a href="#rfc.xref.status.415.2">11.2.3</a></li>
     5293                        <li>417 Expectation Failed&nbsp;&nbsp;<a href="#rfc.xref.status.417.1">7.1</a>, <a href="#rfc.iref.s.35"><b>7.5.14</b></a>, <a href="#rfc.xref.status.417.2">11.2.3</a></li>
     5294                        <li>426 Upgrade Required&nbsp;&nbsp;<a href="#rfc.xref.status.426.1">7.1</a>, <a href="#rfc.iref.s.36"><b>7.5.15</b></a>, <a href="#rfc.xref.status.426.2">11.2.3</a>, <a href="#rfc.xref.status.426.3">C</a></li>
     5295                        <li>500 Internal Server Error&nbsp;&nbsp;<a href="#rfc.xref.status.500.1">7.1</a>, <a href="#rfc.iref.s.38"><b>7.6.1</b></a>, <a href="#rfc.xref.status.500.2">11.2.3</a></li>
     5296                        <li>501 Not Implemented&nbsp;&nbsp;<a href="#rfc.xref.status.501.1">7.1</a>, <a href="#rfc.iref.s.39"><b>7.6.2</b></a>, <a href="#rfc.xref.status.501.2">11.2.3</a></li>
     5297                        <li>502 Bad Gateway&nbsp;&nbsp;<a href="#rfc.xref.status.502.1">7.1</a>, <a href="#rfc.iref.s.40"><b>7.6.3</b></a>, <a href="#rfc.xref.status.502.2">11.2.3</a></li>
     5298                        <li>503 Service Unavailable&nbsp;&nbsp;<a href="#rfc.xref.status.503.1">7.1</a>, <a href="#rfc.iref.s.41"><b>7.6.4</b></a>, <a href="#rfc.xref.status.503.2">11.2.3</a></li>
     5299                        <li>504 Gateway Timeout&nbsp;&nbsp;<a href="#rfc.xref.status.504.1">7.1</a>, <a href="#rfc.iref.s.42"><b>7.6.5</b></a>, <a href="#rfc.xref.status.504.2">11.2.3</a></li>
     5300                        <li>505 HTTP Version Not Supported&nbsp;&nbsp;<a href="#rfc.xref.status.505.1">7.1</a>, <a href="#rfc.iref.s.43"><b>7.6.6</b></a>, <a href="#rfc.xref.status.505.2">11.2.3</a></li>
    53015301                     </ul>
    53025302                  </li>
    53035303                  <li>Status Codes Classes&nbsp;&nbsp;
    53045304                     <ul>
    5305                         <li>1xx Informational&nbsp;&nbsp;<a href="#rfc.iref.s.3"><b>6.2</b></a></li>
    5306                         <li>2xx Successful&nbsp;&nbsp;<a href="#rfc.iref.s.6"><b>6.3</b></a></li>
    5307                         <li>3xx Redirection&nbsp;&nbsp;<a href="#rfc.iref.s.13"><b>6.4</b></a>, <a href="#rfc.xref.status.3xx.1">C</a></li>
    5308                         <li>4xx Client Error&nbsp;&nbsp;<a href="#rfc.iref.s.21"><b>6.5</b></a></li>
    5309                         <li>5xx Server Error&nbsp;&nbsp;<a href="#rfc.iref.s.37"><b>6.6</b></a></li>
     5305                        <li>1xx Informational&nbsp;&nbsp;<a href="#rfc.iref.s.3"><b>7.2</b></a></li>
     5306                        <li>2xx Successful&nbsp;&nbsp;<a href="#rfc.iref.s.6"><b>7.3</b></a></li>
     5307                        <li>3xx Redirection&nbsp;&nbsp;<a href="#rfc.iref.s.13"><b>7.4</b></a>, <a href="#rfc.xref.status.3xx.1">C</a></li>
     5308                        <li>4xx Client Error&nbsp;&nbsp;<a href="#rfc.iref.s.21"><b>7.5</b></a></li>
     5309                        <li>5xx Server Error&nbsp;&nbsp;<a href="#rfc.iref.s.37"><b>7.6</b></a></li>
    53105310                     </ul>
    53115311                  </li>
    5312                   <li><em>status-308</em>&nbsp;&nbsp;<a href="#rfc.xref.status-308.1">6.4.7</a>, <a href="#status-308"><b>14.2</b></a></li>
     5312                  <li><em>status-308</em>&nbsp;&nbsp;<a href="#rfc.xref.status-308.1">7.4.7</a>, <a href="#status-308"><b>14.2</b></a></li>
    53135313               </ul>
    53145314            </li>
    53155315            <li><a id="rfc.index.T" href="#rfc.index.T"><b>T</b></a><ul>
    5316                   <li>TRACE method&nbsp;&nbsp;<a href="#rfc.xref.TRACE.1">4.1</a>, <a href="#rfc.iref.t.1"><b>4.3.8</b></a>, <a href="#rfc.xref.TRACE.2">10.14</a>, <a href="#rfc.xref.TRACE.3">11.1.3</a>, <a href="#rfc.xref.TRACE.4">12.1</a></li>
     5316                  <li>TRACE method&nbsp;&nbsp;<a href="#rfc.xref.TRACE.1">5.1</a>, <a href="#rfc.iref.t.1"><b>5.3.8</b></a>, <a href="#rfc.xref.TRACE.2">10.14</a>, <a href="#rfc.xref.TRACE.3">11.1.3</a>, <a href="#rfc.xref.TRACE.4">12.1</a></li>
    53175317               </ul>
    53185318            </li>
    53195319            <li><a id="rfc.index.U" href="#rfc.index.U"><b>U</b></a><ul>
    5320                   <li>User-Agent header field&nbsp;&nbsp;<a href="#rfc.xref.header.user-agent.1">3.4.1</a>, <a href="#rfc.xref.header.user-agent.2">5.5</a>, <a href="#rfc.iref.u.1"><b>10.18</b></a>, <a href="#rfc.xref.header.user-agent.3">11.3.2</a>, <a href="#rfc.xref.header.user-agent.4">12.1</a></li>
     5320                  <li>User-Agent header field&nbsp;&nbsp;<a href="#rfc.xref.header.user-agent.1">3.4.1</a>, <a href="#rfc.xref.header.user-agent.2">6.5</a>, <a href="#rfc.iref.u.1"><b>10.18</b></a>, <a href="#rfc.xref.header.user-agent.3">11.3.2</a>, <a href="#rfc.xref.header.user-agent.4">12.1</a></li>
    53215321               </ul>
    53225322            </li>

  • draft-ietf-httpbis/latest/p2-semantics.xml

    r1854 r1855  
    655655</section>
    656656
     657<section title="Payload" anchor="payload">
     658<t>
     659   HTTP messages &MAY; transfer a payload if not otherwise restricted by
     660   the request method or response status code.  The payload consists of
     661   metadata, in the form of header fields, and data, in the form of the
     662   sequence of octets in the message body after any transfer-coding has