Ignore:
Timestamp:
Aug 31, 2012, 11:20:46 PM (7 years ago)
Author:
fielding@…
Message:

(editorial) section moves only -- registries belong in IANA considerations

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

Legend:

Unmodified
Added
Removed

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

    r1842 r1843  
    619619         <li><a href="#rfc.section.5">5.</a>&nbsp;&nbsp;&nbsp;<a href="#status.codes">Response Status Codes</a><ul>
    620620               <li><a href="#rfc.section.5.1">5.1</a>&nbsp;&nbsp;&nbsp;<a href="#overview.of.status.codes">Overview of Status Codes</a></li>
    621                <li><a href="#rfc.section.5.2">5.2</a>&nbsp;&nbsp;&nbsp;<a href="#status.code.registry">Status Code Registry</a><ul>
    622                      <li><a href="#rfc.section.5.2.1">5.2.1</a>&nbsp;&nbsp;&nbsp;<a href="#considerations.for.new.status.codes">Considerations for New Status Codes</a></li>
     621               <li><a href="#rfc.section.5.2">5.2</a>&nbsp;&nbsp;&nbsp;<a href="#status.1xx">Informational 1xx</a><ul>
     622                     <li><a href="#rfc.section.5.2.1">5.2.1</a>&nbsp;&nbsp;&nbsp;<a href="#status.100">100 Continue</a></li>
     623                     <li><a href="#rfc.section.5.2.2">5.2.2</a>&nbsp;&nbsp;&nbsp;<a href="#status.101">101 Switching Protocols</a></li>
    623624                  </ul>
    624625               </li>
    625                <li><a href="#rfc.section.5.3">5.3</a>&nbsp;&nbsp;&nbsp;<a href="#status.1xx">Informational 1xx</a><ul>
    626                      <li><a href="#rfc.section.5.3.1">5.3.1</a>&nbsp;&nbsp;&nbsp;<a href="#status.100">100 Continue</a></li>
    627                      <li><a href="#rfc.section.5.3.2">5.3.2</a>&nbsp;&nbsp;&nbsp;<a href="#status.101">101 Switching Protocols</a></li>
     626               <li><a href="#rfc.section.5.3">5.3</a>&nbsp;&nbsp;&nbsp;<a href="#status.2xx">Successful 2xx</a><ul>
     627                     <li><a href="#rfc.section.5.3.1">5.3.1</a>&nbsp;&nbsp;&nbsp;<a href="#status.200">200 OK</a></li>
     628                     <li><a href="#rfc.section.5.3.2">5.3.2</a>&nbsp;&nbsp;&nbsp;<a href="#status.201">201 Created</a></li>
     629                     <li><a href="#rfc.section.5.3.3">5.3.3</a>&nbsp;&nbsp;&nbsp;<a href="#status.202">202 Accepted</a></li>
     630                     <li><a href="#rfc.section.5.3.4">5.3.4</a>&nbsp;&nbsp;&nbsp;<a href="#status.203">203 Non-Authoritative Information</a></li>
     631                     <li><a href="#rfc.section.5.3.5">5.3.5</a>&nbsp;&nbsp;&nbsp;<a href="#status.204">204 No Content</a></li>
     632                     <li><a href="#rfc.section.5.3.6">5.3.6</a>&nbsp;&nbsp;&nbsp;<a href="#status.205">205 Reset Content</a></li>
    628633                  </ul>
    629634               </li>
    630                <li><a href="#rfc.section.5.4">5.4</a>&nbsp;&nbsp;&nbsp;<a href="#status.2xx">Successful 2xx</a><ul>
    631                      <li><a href="#rfc.section.5.4.1">5.4.1</a>&nbsp;&nbsp;&nbsp;<a href="#status.200">200 OK</a></li>
    632                      <li><a href="#rfc.section.5.4.2">5.4.2</a>&nbsp;&nbsp;&nbsp;<a href="#status.201">201 Created</a></li>
    633                      <li><a href="#rfc.section.5.4.3">5.4.3</a>&nbsp;&nbsp;&nbsp;<a href="#status.202">202 Accepted</a></li>
    634                      <li><a href="#rfc.section.5.4.4">5.4.4</a>&nbsp;&nbsp;&nbsp;<a href="#status.203">203 Non-Authoritative Information</a></li>
    635                      <li><a href="#rfc.section.5.4.5">5.4.5</a>&nbsp;&nbsp;&nbsp;<a href="#status.204">204 No Content</a></li>
    636                      <li><a href="#rfc.section.5.4.6">5.4.6</a>&nbsp;&nbsp;&nbsp;<a href="#status.205">205 Reset Content</a></li>
     635               <li><a href="#rfc.section.5.4">5.4</a>&nbsp;&nbsp;&nbsp;<a href="#status.3xx">Redirection 3xx</a><ul>
     636                     <li><a href="#rfc.section.5.4.1">5.4.1</a>&nbsp;&nbsp;&nbsp;<a href="#status.300">300 Multiple Choices</a></li>
     637                     <li><a href="#rfc.section.5.4.2">5.4.2</a>&nbsp;&nbsp;&nbsp;<a href="#status.301">301 Moved Permanently</a></li>
     638                     <li><a href="#rfc.section.5.4.3">5.4.3</a>&nbsp;&nbsp;&nbsp;<a href="#status.302">302 Found</a></li>
     639                     <li><a href="#rfc.section.5.4.4">5.4.4</a>&nbsp;&nbsp;&nbsp;<a href="#status.303">303 See Other</a></li>
     640                     <li><a href="#rfc.section.5.4.5">5.4.5</a>&nbsp;&nbsp;&nbsp;<a href="#status.305">305 Use Proxy</a></li>
     641                     <li><a href="#rfc.section.5.4.6">5.4.6</a>&nbsp;&nbsp;&nbsp;<a href="#status.306">306 (Unused)</a></li>
     642                     <li><a href="#rfc.section.5.4.7">5.4.7</a>&nbsp;&nbsp;&nbsp;<a href="#status.307">307 Temporary Redirect</a></li>
    637643                  </ul>
    638644               </li>
    639                <li><a href="#rfc.section.5.5">5.5</a>&nbsp;&nbsp;&nbsp;<a href="#status.3xx">Redirection 3xx</a><ul>
    640                      <li><a href="#rfc.section.5.5.1">5.5.1</a>&nbsp;&nbsp;&nbsp;<a href="#status.300">300 Multiple Choices</a></li>
    641                      <li><a href="#rfc.section.5.5.2">5.5.2</a>&nbsp;&nbsp;&nbsp;<a href="#status.301">301 Moved Permanently</a></li>
    642                      <li><a href="#rfc.section.5.5.3">5.5.3</a>&nbsp;&nbsp;&nbsp;<a href="#status.302">302 Found</a></li>
    643                      <li><a href="#rfc.section.5.5.4">5.5.4</a>&nbsp;&nbsp;&nbsp;<a href="#status.303">303 See Other</a></li>
    644                      <li><a href="#rfc.section.5.5.5">5.5.5</a>&nbsp;&nbsp;&nbsp;<a href="#status.305">305 Use Proxy</a></li>
    645                      <li><a href="#rfc.section.5.5.6">5.5.6</a>&nbsp;&nbsp;&nbsp;<a href="#status.306">306 (Unused)</a></li>
    646                      <li><a href="#rfc.section.5.5.7">5.5.7</a>&nbsp;&nbsp;&nbsp;<a href="#status.307">307 Temporary Redirect</a></li>
     645               <li><a href="#rfc.section.5.5">5.5</a>&nbsp;&nbsp;&nbsp;<a href="#status.4xx">Client Error 4xx</a><ul>
     646                     <li><a href="#rfc.section.5.5.1">5.5.1</a>&nbsp;&nbsp;&nbsp;<a href="#status.400">400 Bad Request</a></li>
     647                     <li><a href="#rfc.section.5.5.2">5.5.2</a>&nbsp;&nbsp;&nbsp;<a href="#status.402">402 Payment Required</a></li>
     648                     <li><a href="#rfc.section.5.5.3">5.5.3</a>&nbsp;&nbsp;&nbsp;<a href="#status.403">403 Forbidden</a></li>
     649                     <li><a href="#rfc.section.5.5.4">5.5.4</a>&nbsp;&nbsp;&nbsp;<a href="#status.404">404 Not Found</a></li>
     650                     <li><a href="#rfc.section.5.5.5">5.5.5</a>&nbsp;&nbsp;&nbsp;<a href="#status.405">405 Method Not Allowed</a></li>
     651                     <li><a href="#rfc.section.5.5.6">5.5.6</a>&nbsp;&nbsp;&nbsp;<a href="#status.406">406 Not Acceptable</a></li>
     652                     <li><a href="#rfc.section.5.5.7">5.5.7</a>&nbsp;&nbsp;&nbsp;<a href="#status.408">408 Request Timeout</a></li>
     653                     <li><a href="#rfc.section.5.5.8">5.5.8</a>&nbsp;&nbsp;&nbsp;<a href="#status.409">409 Conflict</a></li>
     654                     <li><a href="#rfc.section.5.5.9">5.5.9</a>&nbsp;&nbsp;&nbsp;<a href="#status.410">410 Gone</a></li>
     655                     <li><a href="#rfc.section.5.5.10">5.5.10</a>&nbsp;&nbsp;&nbsp;<a href="#status.411">411 Length Required</a></li>
     656                     <li><a href="#rfc.section.5.5.11">5.5.11</a>&nbsp;&nbsp;&nbsp;<a href="#status.413">413 Request Representation Too Large</a></li>
     657                     <li><a href="#rfc.section.5.5.12">5.5.12</a>&nbsp;&nbsp;&nbsp;<a href="#status.414">414 URI Too Long</a></li>
     658                     <li><a href="#rfc.section.5.5.13">5.5.13</a>&nbsp;&nbsp;&nbsp;<a href="#status.415">415 Unsupported Media Type</a></li>
     659                     <li><a href="#rfc.section.5.5.14">5.5.14</a>&nbsp;&nbsp;&nbsp;<a href="#status.417">417 Expectation Failed</a></li>
     660                     <li><a href="#rfc.section.5.5.15">5.5.15</a>&nbsp;&nbsp;&nbsp;<a href="#status.426">426 Upgrade Required</a></li>
    647661                  </ul>
    648662               </li>
    649                <li><a href="#rfc.section.5.6">5.6</a>&nbsp;&nbsp;&nbsp;<a href="#status.4xx">Client Error 4xx</a><ul>
    650                      <li><a href="#rfc.section.5.6.1">5.6.1</a>&nbsp;&nbsp;&nbsp;<a href="#status.400">400 Bad Request</a></li>
    651                      <li><a href="#rfc.section.5.6.2">5.6.2</a>&nbsp;&nbsp;&nbsp;<a href="#status.402">402 Payment Required</a></li>
    652                      <li><a href="#rfc.section.5.6.3">5.6.3</a>&nbsp;&nbsp;&nbsp;<a href="#status.403">403 Forbidden</a></li>
    653                      <li><a href="#rfc.section.5.6.4">5.6.4</a>&nbsp;&nbsp;&nbsp;<a href="#status.404">404 Not Found</a></li>
    654                      <li><a href="#rfc.section.5.6.5">5.6.5</a>&nbsp;&nbsp;&nbsp;<a href="#status.405">405 Method Not Allowed</a></li>
    655                      <li><a href="#rfc.section.5.6.6">5.6.6</a>&nbsp;&nbsp;&nbsp;<a href="#status.406">406 Not Acceptable</a></li>
    656                      <li><a href="#rfc.section.5.6.7">5.6.7</a>&nbsp;&nbsp;&nbsp;<a href="#status.408">408 Request Timeout</a></li>
    657                      <li><a href="#rfc.section.5.6.8">5.6.8</a>&nbsp;&nbsp;&nbsp;<a href="#status.409">409 Conflict</a></li>
    658                      <li><a href="#rfc.section.5.6.9">5.6.9</a>&nbsp;&nbsp;&nbsp;<a href="#status.410">410 Gone</a></li>
    659                      <li><a href="#rfc.section.5.6.10">5.6.10</a>&nbsp;&nbsp;&nbsp;<a href="#status.411">411 Length Required</a></li>
    660                      <li><a href="#rfc.section.5.6.11">5.6.11</a>&nbsp;&nbsp;&nbsp;<a href="#status.413">413 Request Representation Too Large</a></li>
    661                      <li><a href="#rfc.section.5.6.12">5.6.12</a>&nbsp;&nbsp;&nbsp;<a href="#status.414">414 URI Too Long</a></li>
    662                      <li><a href="#rfc.section.5.6.13">5.6.13</a>&nbsp;&nbsp;&nbsp;<a href="#status.415">415 Unsupported Media Type</a></li>
    663                      <li><a href="#rfc.section.5.6.14">5.6.14</a>&nbsp;&nbsp;&nbsp;<a href="#status.417">417 Expectation Failed</a></li>
    664                      <li><a href="#rfc.section.5.6.15">5.6.15</a>&nbsp;&nbsp;&nbsp;<a href="#status.426">426 Upgrade Required</a></li>
    665                   </ul>
    666                </li>
    667                <li><a href="#rfc.section.5.7">5.7</a>&nbsp;&nbsp;&nbsp;<a href="#status.5xx">Server Error 5xx</a><ul>
    668                      <li><a href="#rfc.section.5.7.1">5.7.1</a>&nbsp;&nbsp;&nbsp;<a href="#status.500">500 Internal Server Error</a></li>
    669                      <li><a href="#rfc.section.5.7.2">5.7.2</a>&nbsp;&nbsp;&nbsp;<a href="#status.501">501 Not Implemented</a></li>
    670                      <li><a href="#rfc.section.5.7.3">5.7.3</a>&nbsp;&nbsp;&nbsp;<a href="#status.502">502 Bad Gateway</a></li>
    671                      <li><a href="#rfc.section.5.7.4">5.7.4</a>&nbsp;&nbsp;&nbsp;<a href="#status.503">503 Service Unavailable</a></li>
    672                      <li><a href="#rfc.section.5.7.5">5.7.5</a>&nbsp;&nbsp;&nbsp;<a href="#status.504">504 Gateway Timeout</a></li>
    673                      <li><a href="#rfc.section.5.7.6">5.7.6</a>&nbsp;&nbsp;&nbsp;<a href="#status.505">505 HTTP Version Not Supported</a></li>
     663               <li><a href="#rfc.section.5.6">5.6</a>&nbsp;&nbsp;&nbsp;<a href="#status.5xx">Server Error 5xx</a><ul>
     664                     <li><a href="#rfc.section.5.6.1">5.6.1</a>&nbsp;&nbsp;&nbsp;<a href="#status.500">500 Internal Server Error</a></li>
     665                     <li><a href="#rfc.section.5.6.2">5.6.2</a>&nbsp;&nbsp;&nbsp;<a href="#status.501">501 Not Implemented</a></li>
     666                     <li><a href="#rfc.section.5.6.3">5.6.3</a>&nbsp;&nbsp;&nbsp;<a href="#status.502">502 Bad Gateway</a></li>
     667                     <li><a href="#rfc.section.5.6.4">5.6.4</a>&nbsp;&nbsp;&nbsp;<a href="#status.503">503 Service Unavailable</a></li>
     668                     <li><a href="#rfc.section.5.6.5">5.6.5</a>&nbsp;&nbsp;&nbsp;<a href="#status.504">504 Gateway Timeout</a></li>
     669                     <li><a href="#rfc.section.5.6.6">5.6.6</a>&nbsp;&nbsp;&nbsp;<a href="#status.505">505 HTTP Version Not Supported</a></li>
    674670                  </ul>
    675671               </li>
    … …  
    680676               <li><a href="#rfc.section.6.2">6.2</a>&nbsp;&nbsp;&nbsp;<a href="#product.tokens">Product Tokens</a></li>
    681677               <li><a href="#rfc.section.6.3">6.3</a>&nbsp;&nbsp;&nbsp;<a href="#character.sets">Character Encodings (charset)</a></li>
    682                <li><a href="#rfc.section.6.4">6.4</a>&nbsp;&nbsp;&nbsp;<a href="#content.codings">Content Codings</a><ul>
    683                      <li><a href="#rfc.section.6.4.1">6.4.1</a>&nbsp;&nbsp;&nbsp;<a href="#content.coding.registry">Content Coding Registry</a></li>
    684                   </ul>
    685                </li>
     678               <li><a href="#rfc.section.6.4">6.4</a>&nbsp;&nbsp;&nbsp;<a href="#content.codings">Content Codings</a></li>
    686679               <li><a href="#rfc.section.6.5">6.5</a>&nbsp;&nbsp;&nbsp;<a href="#media.types">Media Types</a><ul>
    687680                     <li><a href="#rfc.section.6.5.1">6.5.1</a>&nbsp;&nbsp;&nbsp;<a href="#canonicalization.and.text.defaults">Canonicalization and Text Defaults</a></li>
    … …  
    732725         <li><a href="#rfc.section.11">11.</a>&nbsp;&nbsp;&nbsp;<a href="#IANA.considerations">IANA Considerations</a><ul>
    733726               <li><a href="#rfc.section.11.1">11.1</a>&nbsp;&nbsp;&nbsp;<a href="#method.registry">Method Registry</a><ul>
    734                      <li><a href="#rfc.section.11.1.1">11.1.1</a>&nbsp;&nbsp;&nbsp;<a href="#considerations.for.new.methods">Considerations for New Methods</a></li>
    735                      <li><a href="#rfc.section.11.1.2">11.1.2</a>&nbsp;&nbsp;&nbsp;<a href="#method.registration">Registrations</a></li>
     727                     <li><a href="#rfc.section.11.1.1">11.1.1</a>&nbsp;&nbsp;&nbsp;<a href="#method.procedure">Procedure</a></li>
     728                     <li><a href="#rfc.section.11.1.2">11.1.2</a>&nbsp;&nbsp;&nbsp;<a href="#considerations.for.new.methods">Considerations for New Methods</a></li>
     729                     <li><a href="#rfc.section.11.1.3">11.1.3</a>&nbsp;&nbsp;&nbsp;<a href="#method.registration">Registrations</a></li>
    736730                  </ul>
    737731               </li>
    738                <li><a href="#rfc.section.11.2">11.2</a>&nbsp;&nbsp;&nbsp;<a href="#status.code.registration">Status Code Registry</a></li>
     732               <li><a href="#rfc.section.11.2">11.2</a>&nbsp;&nbsp;&nbsp;<a href="#status.code.registry">Status Code Registry</a><ul>
     733                     <li><a href="#rfc.section.11.2.1">11.2.1</a>&nbsp;&nbsp;&nbsp;<a href="#status.code.procedure">Procedure</a></li>
     734                     <li><a href="#rfc.section.11.2.2">11.2.2</a>&nbsp;&nbsp;&nbsp;<a href="#considerations.for.new.status.codes">Considerations for New Status Codes</a></li>
     735                     <li><a href="#rfc.section.11.2.3">11.2.3</a>&nbsp;&nbsp;&nbsp;<a href="#status.code.registration">Registrations</a></li>
     736                  </ul>
     737               </li>
    739738               <li><a href="#rfc.section.11.3">11.3</a>&nbsp;&nbsp;&nbsp;<a href="#header.field.registration">Header Field Registration</a></li>
    740                <li><a href="#rfc.section.11.4">11.4</a>&nbsp;&nbsp;&nbsp;<a href="#content.coding.registration">Content Coding Registry</a></li>
     739               <li><a href="#rfc.section.11.4">11.4</a>&nbsp;&nbsp;&nbsp;<a href="#content.coding.registry">Content Coding Registry</a><ul>
     740                     <li><a href="#rfc.section.11.4.1">11.4.1</a>&nbsp;&nbsp;&nbsp;<a href="#content.coding.procedure">Procedure</a></li>
     741                     <li><a href="#rfc.section.11.4.2">11.4.2</a>&nbsp;&nbsp;&nbsp;<a href="#content.coding.registration">Registrations</a></li>
     742                  </ul>
     743               </li>
    741744            </ul>
    742745         </li>
    … …  
    14591462                  <td class="left">100</td>
    14601463                  <td class="left">Continue</td>
    1461                   <td class="left"><a href="#status.100" id="rfc.xref.status.100.1" title="100 Continue">Section&nbsp;5.3.1</a></td>
     1464                  <td class="left"><a href="#status.100" id="rfc.xref.status.100.1" title="100 Continue">Section&nbsp;5.2.1</a></td>
    14621465               </tr>
    14631466               <tr>
    14641467                  <td class="left">101</td>
    14651468                  <td class="left">Switching Protocols</td>
    1466                   <td class="left"><a href="#status.101" id="rfc.xref.status.101.1" title="101 Switching Protocols">Section&nbsp;5.3.2</a></td>
     1469                  <td class="left"><a href="#status.101" id="rfc.xref.status.101.1" title="101 Switching Protocols">Section&nbsp;5.2.2</a></td>
    14671470               </tr>
    14681471               <tr>
    14691472                  <td class="left">200</td>
    14701473                  <td class="left">OK</td>
    1471                   <td class="left"><a href="#status.200" id="rfc.xref.status.200.1" title="200 OK">Section&nbsp;5.4.1</a></td>
     1474                  <td class="left"><a href="#status.200" id="rfc.xref.status.200.1" title="200 OK">Section&nbsp;5.3.1</a></td>
    14721475               </tr>
    14731476               <tr>
    14741477                  <td class="left">201</td>
    14751478                  <td class="left">Created</td>
    1476                   <td class="left"><a href="#status.201" id="rfc.xref.status.201.1" title="201 Created">Section&nbsp;5.4.2</a></td>
     1479                  <td class="left"><a href="#status.201" id="rfc.xref.status.201.1" title="201 Created">Section&nbsp;5.3.2</a></td>
    14771480               </tr>
    14781481               <tr>
    14791482                  <td class="left">202</td>
    14801483                  <td class="left">Accepted</td>
    1481                   <td class="left"><a href="#status.202" id="rfc.xref.status.202.1" title="202 Accepted">Section&nbsp;5.4.3</a></td>
     1484                  <td class="left"><a href="#status.202" id="rfc.xref.status.202.1" title="202 Accepted">Section&nbsp;5.3.3</a></td>
    14821485               </tr>
    14831486               <tr>
    14841487                  <td class="left">203</td>
    14851488                  <td class="left">Non-Authoritative Information</td>
    1486                   <td class="left"><a href="#status.203" id="rfc.xref.status.203.1" title="203 Non-Authoritative Information">Section&nbsp;5.4.4</a></td>
     1489                  <td class="left"><a href="#status.203" id="rfc.xref.status.203.1" title="203 Non-Authoritative Information">Section&nbsp;5.3.4</a></td>
    14871490               </tr>
    14881491               <tr>
    14891492                  <td class="left">204</td>
    14901493                  <td class="left">No Content</td>
    1491                   <td class="left"><a href="#status.204" id="rfc.xref.status.204.1" title="204 No Content">Section&nbsp;5.4.5</a></td>
     1494                  <td class="left"><a href="#status.204" id="rfc.xref.status.204.1" title="204 No Content">Section&nbsp;5.3.5</a></td>
    14921495               </tr>
    14931496               <tr>
    14941497                  <td class="left">205</td>
    14951498                  <td class="left">Reset Content</td>
    1496                   <td class="left"><a href="#status.205" id="rfc.xref.status.205.1" title="205 Reset Content">Section&nbsp;5.4.6</a></td>
     1499                  <td class="left"><a href="#status.205" id="rfc.xref.status.205.1" title="205 Reset Content">Section&nbsp;5.3.6</a></td>
    14971500               </tr>
    14981501               <tr>
    … …  
    15041507                  <td class="left">300</td>
    15051508                  <td class="left">Multiple Choices</td>
    1506                   <td class="left"><a href="#status.300" id="rfc.xref.status.300.1" title="300 Multiple Choices">Section&nbsp;5.5.1</a></td>
     1509                  <td class="left"><a href="#status.300" id="rfc.xref.status.300.1" title="300 Multiple Choices">Section&nbsp;5.4.1</a></td>
    15071510               </tr>
    15081511               <tr>
    15091512                  <td class="left">301</td>
    15101513                  <td class="left">Moved Permanently</td>
    1511                   <td class="left"><a href="#status.301" id="rfc.xref.status.301.1" title="301 Moved Permanently">Section&nbsp;5.5.2</a></td>
     1514                  <td class="left"><a href="#status.301" id="rfc.xref.status.301.1" title="301 Moved Permanently">Section&nbsp;5.4.2</a></td>
    15121515               </tr>
    15131516               <tr>
    15141517                  <td class="left">302</td>
    15151518                  <td class="left">Found</td>
    1516                   <td class="left"><a href="#status.302" id="rfc.xref.status.302.1" title="302 Found">Section&nbsp;5.5.3</a></td>
     1519                  <td class="left"><a href="#status.302" id="rfc.xref.status.302.1" title="302 Found">Section&nbsp;5.4.3</a></td>
    15171520               </tr>
    15181521               <tr>
    15191522                  <td class="left">303</td>
    15201523                  <td class="left">See Other</td>
    1521                   <td class="left"><a href="#status.303" id="rfc.xref.status.303.1" title="303 See Other">Section&nbsp;5.5.4</a></td>
     1524                  <td class="left"><a href="#status.303" id="rfc.xref.status.303.1" title="303 See Other">Section&nbsp;5.4.4</a></td>
    15221525               </tr>
    15231526               <tr>
    … …  
    15291532                  <td class="left">305</td>
    15301533                  <td class="left">Use Proxy</td>
    1531                   <td class="left"><a href="#status.305" id="rfc.xref.status.305.1" title="305 Use Proxy">Section&nbsp;5.5.5</a></td>
     1534                  <td class="left"><a href="#status.305" id="rfc.xref.status.305.1" title="305 Use Proxy">Section&nbsp;5.4.5</a></td>
    15321535               </tr>
    15331536               <tr>
    15341537                  <td class="left">307</td>
    15351538                  <td class="left">Temporary Redirect</td>
    1536                   <td class="left"><a href="#status.307" id="rfc.xref.status.307.1" title="307 Temporary Redirect">Section&nbsp;5.5.7</a></td>
     1539                  <td class="left"><a href="#status.307" id="rfc.xref.status.307.1" title="307 Temporary Redirect">Section&nbsp;5.4.7</a></td>
    15371540               </tr>
    15381541               <tr>
    15391542                  <td class="left">400</td>
    15401543                  <td class="left">Bad Request</td>
    1541                   <td class="left"><a href="#status.400" id="rfc.xref.status.400.1" title="400 Bad Request">Section&nbsp;5.6.1</a></td>
     1544                  <td class="left"><a href="#status.400" id="rfc.xref.status.400.1" title="400 Bad Request">Section&nbsp;5.5.1</a></td>
    15421545               </tr>
    15431546               <tr>
    … …  
    15491552                  <td class="left">402</td>
    15501553                  <td class="left">Payment Required</td>
    1551                   <td class="left"><a href="#status.402" id="rfc.xref.status.402.1" title="402 Payment Required">Section&nbsp;5.6.2</a></td>
     1554                  <td class="left"><a href="#status.402" id="rfc.xref.status.402.1" title="402 Payment Required">Section&nbsp;5.5.2</a></td>
    15521555               </tr>
    15531556               <tr>
    15541557                  <td class="left">403</td>
    15551558                  <td class="left">Forbidden</td>
    1556                   <td class="left"><a href="#status.403" id="rfc.xref.status.403.1" title="403 Forbidden">Section&nbsp;5.6.3</a></td>
     1559                  <td class="left"><a href="#status.403" id="rfc.xref.status.403.1" title="403 Forbidden">Section&nbsp;5.5.3</a></td>
    15571560               </tr>
    15581561               <tr>
    15591562                  <td class="left">404</td>
    15601563                  <td class="left">Not Found</td>
    1561                   <td class="left"><a href="#status.404" id="rfc.xref.status.404.1" title="404 Not Found">Section&nbsp;5.6.4</a></td>
     1564                  <td class="left"><a href="#status.404" id="rfc.xref.status.404.1" title="404 Not Found">Section&nbsp;5.5.4</a></td>
    15621565               </tr>
    15631566               <tr>
    15641567                  <td class="left">405</td>
    15651568                  <td class="left">Method Not Allowed</td>
    1566                   <td class="left"><a href="#status.405" id="rfc.xref.status.405.1" title="405 Method Not Allowed">Section&nbsp;5.6.5</a></td>
     1569                  <td class="left"><a href="#status.405" id="rfc.xref.status.405.1" title="405 Method Not Allowed">Section&nbsp;5.5.5</a></td>
    15671570               </tr>
    15681571               <tr>
    15691572                  <td class="left">406</td>
    15701573                  <td class="left">Not Acceptable</td>
    1571                   <td class="left"><a href="#status.406" id="rfc.xref.status.406.1" title="406 Not Acceptable">Section&nbsp;5.6.6</a></td>
     1574                  <td class="left"><a href="#status.406" id="rfc.xref.status.406.1" title="406 Not Acceptable">Section&nbsp;5.5.6</a></td>
    15721575               </tr>
    15731576               <tr>
    … …  
    15791582                  <td class="left">408</td>
    15801583                  <td class="left">Request Time-out</td>
    1581                   <td class="left"><a href="#status.408" id="rfc.xref.status.408.1" title="408 Request Timeout">Section&nbsp;5.6.7</a></td>
     1584                  <td class="left"><a href="#status.408" id="rfc.xref.status.408.1" title="408 Request Timeout">Section&nbsp;5.5.7</a></td>
    15821585               </tr>
    15831586               <tr>
    15841587                  <td class="left">409</td>
    15851588                  <td class="left">Conflict</td>
    1586                   <td class="left"><a href="#status.409" id="rfc.xref.status.409.1" title="409 Conflict">Section&nbsp;5.6.8</a></td>
     1589                  <td class="left"><a href="#status.409" id="rfc.xref.status.409.1" title="409 Conflict">Section&nbsp;5.5.8</a></td>
    15871590               </tr>
    15881591               <tr>
    15891592                  <td class="left">410</td>
    15901593                  <td class="left">Gone</td>
    1591                   <td class="left"><a href="#status.410" id="rfc.xref.status.410.1" title="410 Gone">Section&nbsp;5.6.9</a></td>
     1594                  <td class="left"><a href="#status.410" id="rfc.xref.status.410.1" title="410 Gone">Section&nbsp;5.5.9</a></td>
    15921595               </tr>
    15931596               <tr>
    15941597                  <td class="left">411</td>
    15951598                  <td class="left">Length Required</td>
    1596                   <td class="left"><a href="#status.411" id="rfc.xref.status.411.1" title="411 Length Required">Section&nbsp;5.6.10</a></td>
     1599                  <td class="left"><a href="#status.411" id="rfc.xref.status.411.1" title="411 Length Required">Section&nbsp;5.5.10</a></td>
    15971600               </tr>
    15981601               <tr>
    … …  
    16041607                  <td class="left">413</td>
    16051608                  <td class="left">Request Representation Too Large</td>
    1606                   <td class="left"><a href="#status.413" id="rfc.xref.status.413.1" title="413 Request Representation Too Large">Section&nbsp;5.6.11</a></td>
     1609                  <td class="left"><a href="#status.413" id="rfc.xref.status.413.1" title="413 Request Representation Too Large">Section&nbsp;5.5.11</a></td>
    16071610               </tr>
    16081611               <tr>
    16091612                  <td class="left">414</td>
    16101613                  <td class="left">URI Too Long</td>
    1611                   <td class="left"><a href="#status.414" id="rfc.xref.status.414.1" title="414 URI Too Long">Section&nbsp;5.6.12</a></td>
     1614                  <td class="left"><a href="#status.414" id="rfc.xref.status.414.1" title="414 URI Too Long">Section&nbsp;5.5.12</a></td>
    16121615               </tr>
    16131616               <tr>
    16141617                  <td class="left">415</td>
    16151618                  <td class="left">Unsupported Media Type</td>
    1616                   <td class="left"><a href="#status.415" id="rfc.xref.status.415.1" title="415 Unsupported Media Type">Section&nbsp;5.6.13</a></td>
     1619                  <td class="left"><a href="#status.415" id="rfc.xref.status.415.1" title="415 Unsupported Media Type">Section&nbsp;5.5.13</a></td>
    16171620               </tr>
    16181621               <tr>
    … …  
    16241627                  <td class="left">417</td>
    16251628                  <td class="left">Expectation Failed</td>
    1626                   <td class="left"><a href="#status.417" id="rfc.xref.status.417.1" title="417 Expectation Failed">Section&nbsp;5.6.14</a></td>
     1629                  <td class="left"><a href="#status.417" id="rfc.xref.status.417.1" title="417 Expectation Failed">Section&nbsp;5.5.14</a></td>
    16271630               </tr>
    16281631               <tr>
    16291632                  <td class="left">426</td>
    16301633                  <td class="left">Upgrade Required</td>
    1631                   <td class="left"><a href="#status.426" id="rfc.xref.status.426.1" title="426 Upgrade Required">Section&nbsp;5.6.15</a></td>
     1634                  <td class="left"><a href="#status.426" id="rfc.xref.status.426.1" title="426 Upgrade Required">Section&nbsp;5.5.15</a></td>
    16321635               </tr>
    16331636               <tr>
    16341637                  <td class="left">500</td>
    16351638                  <td class="left">Internal Server Error</td>
    1636                   <td class="left"><a href="#status.500" id="rfc.xref.status.500.1" title="500 Internal Server Error">Section&nbsp;5.7.1</a></td>
     1639                  <td class="left"><a href="#status.500" id="rfc.xref.status.500.1" title="500 Internal Server Error">Section&nbsp;5.6.1</a></td>
    16371640               </tr>
    16381641               <tr>
    16391642                  <td class="left">501</td>
    16401643                  <td class="left">Not Implemented</td>
    1641                   <td class="left"><a href="#status.501" id="rfc.xref.status.501.1" title="501 Not Implemented">Section&nbsp;5.7.2</a></td>
     1644                  <td class="left"><a href="#status.501" id="rfc.xref.status.501.1" title="501 Not Implemented">Section&nbsp;5.6.2</a></td>
    16421645               </tr>
    16431646               <tr>
    16441647                  <td class="left">502</td>
    16451648                  <td class="left">Bad Gateway</td>
    1646                   <td class="left"><a href="#status.502" id="rfc.xref.status.502.1" title="502 Bad Gateway">Section&nbsp;5.7.3</a></td>
     1649                  <td class="left"><a href="#status.502" id="rfc.xref.status.502.1" title="502 Bad Gateway">Section&nbsp;5.6.3</a></td>
    16471650               </tr>
    16481651               <tr>
    16491652                  <td class="left">503</td>
    16501653                  <td class="left">Service Unavailable</td>
    1651                   <td class="left"><a href="#status.503" id="rfc.xref.status.503.1" title="503 Service Unavailable">Section&nbsp;5.7.4</a></td>
     1654                  <td class="left"><a href="#status.503" id="rfc.xref.status.503.1" title="503 Service Unavailable">Section&nbsp;5.6.4</a></td>
    16521655               </tr>
    16531656               <tr>
    16541657                  <td class="left">504</td>
    16551658                  <td class="left">Gateway Time-out</td>
    1656                   <td class="left"><a href="#status.504" id="rfc.xref.status.504.1" title="504 Gateway Timeout">Section&nbsp;5.7.5</a></td>
     1659                  <td class="left"><a href="#status.504" id="rfc.xref.status.504.1" title="504 Gateway Timeout">Section&nbsp;5.6.5</a></td>
    16571660               </tr>
    16581661               <tr>
    16591662                  <td class="left">505</td>
    16601663                  <td class="left">HTTP Version not supported</td>
    1661                   <td class="left"><a href="#status.505" id="rfc.xref.status.505.1" title="505 HTTP Version Not Supported">Section&nbsp;5.7.6</a></td>
     1664                  <td class="left"><a href="#status.505" id="rfc.xref.status.505.1" title="505 HTTP Version Not Supported">Section&nbsp;5.6.6</a></td>
    16621665               </tr>
    16631666            </tbody>
    … …  
    16651668      </div>
    16661669      <p id="rfc.section.5.1.p.2">Note that this list is not exhaustive — it does not include extension status codes defined in other specifications.</p>
    1667       <h2 id="rfc.section.5.2"><a href="#rfc.section.5.2">5.2</a>&nbsp;<a id="status.code.registry" href="#status.code.registry">Status Code Registry</a></h2>
    1668       <p id="rfc.section.5.2.p.1">The HTTP Status Code Registry defines the name space for the status-code token in the status-line of an HTTP response.</p>
    1669       <p id="rfc.section.5.2.p.2">Values to be added to this name space require IETF Review (see <a href="#RFC5226" id="rfc.xref.RFC5226.1"><cite title="Guidelines for Writing an IANA Considerations Section in RFCs">[RFC5226]</cite></a>, <a href="http://tools.ietf.org/html/rfc5226#section-4.1">Section 4.1</a>).
    1670       </p>
    1671       <p id="rfc.section.5.2.p.3">The registry itself is maintained at &lt;<a href="http://www.iana.org/assignments/http-status-codes">http://www.iana.org/assignments/http-status-codes</a>&gt;.
    1672       </p>
    1673       <h3 id="rfc.section.5.2.1"><a href="#rfc.section.5.2.1">5.2.1</a>&nbsp;<a id="considerations.for.new.status.codes" href="#considerations.for.new.status.codes">Considerations for New Status Codes</a></h3>
    1674       <p id="rfc.section.5.2.1.p.1">When it is necessary to express new semantics for a HTTP response that aren't specific to a single application or media type,
    1675          and currently defined status codes are inadequate, a new status code can be registered.
    1676       </p>
    1677       <p id="rfc.section.5.2.1.p.2">HTTP status codes are generic; that is, they are potentially applicable to any resource, not just one particular media type,
    1678          "type" of resource, or application. As such, it is preferred that new HTTP status codes be registered in a document that isn't
    1679          specific to a single application, so that this is clear.
    1680       </p>
    1681       <p id="rfc.section.5.2.1.p.3">Definitions of new HTTP status codes typically explain the request conditions that produce a response containing the status
    1682          code (e.g., combinations of request header fields and/or method(s)), along with any interactions with response header fields
    1683          (e.g., those that are required, those that modify the semantics of the response).
    1684       </p>
    1685       <p id="rfc.section.5.2.1.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;5</a>. To allow existing parsers to properly handle them, new status codes cannot disallow a response body, although they can mandate
    1686          a zero-length response body. They can require the presence of one or more particular HTTP response header field(s).
    1687       </p>
    1688       <p id="rfc.section.5.2.1.p.5">Likewise, their definitions can specify that caches are allowed to use heuristics to determine their freshness (see <a href="#Part6" id="rfc.xref.Part6.10"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>; by default, it is not allowed), and can define how to determine the resource which they carry a representation for (see <a href="#identifying.response.associated.with.representation" title="Identifying the Resource Associated with a Representation">Section&nbsp;8.1</a>; by default, it is anonymous).
    1689       </p>
    1690       <h2 id="rfc.section.5.3"><a href="#rfc.section.5.3">5.3</a>&nbsp;<a id="status.1xx" href="#status.1xx">Informational 1xx</a></h2>
     1670      <h2 id="rfc.section.5.2"><a href="#rfc.section.5.2">5.2</a>&nbsp;<a id="status.1xx" href="#status.1xx">Informational 1xx</a></h2>
    16911671      <div id="rfc.iref.21"></div>
    16921672      <div id="rfc.iref.s.2"></div>
    1693       <p id="rfc.section.5.3.p.1">This class of status code indicates a provisional response, consisting only of the status-line and optional header fields,
     1673      <p id="rfc.section.5.2.p.1">This class of status code indicates a provisional response, consisting only of the status-line and optional header fields,
    16941674         and is terminated by an empty line. There are no required header fields for this class of status code. Since HTTP/1.0 did
    16951675         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.
    16961676      </p>
    1697       <p id="rfc.section.5.3.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
     1677      <p id="rfc.section.5.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
    16981678            (Continue)</a> status message. Unexpected 1xx status responses <em class="bcp14">MAY</em> be ignored by a user agent.
    16991679      </p>
    1700       <p id="rfc.section.5.3.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
     1680      <p id="rfc.section.5.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
    17011681         requested the generation of the 1xx response. (For example, if a proxy adds an "Expect: 100-continue" field when it forwards
    17021682         a request, then it need not forward the corresponding <a href="#status.100" class="smpl">100 (Continue)</a> response(s).)
    … …  
    17041684      <div id="rfc.iref.22"></div>
    17051685      <div id="rfc.iref.s.3"></div>
    1706       <h3 id="rfc.section.5.3.1"><a href="#rfc.section.5.3.1">5.3.1</a>&nbsp;<a id="status.100" href="#status.100">100 Continue</a></h3>
    1707       <p id="rfc.section.5.3.1.p.1">The client <em class="bcp14">SHOULD</em> continue with its request. This interim response is used to inform the client that the initial part of the request has been
     1686      <h3 id="rfc.section.5.2.1"><a href="#rfc.section.5.2.1">5.2.1</a>&nbsp;<a id="status.100" href="#status.100">100 Continue</a></h3>
     1687      <p id="rfc.section.5.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
    17081688         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
    17091689         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.20"><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.
    … …  
    17111691      <div id="rfc.iref.23"></div>
    17121692      <div id="rfc.iref.s.4"></div>
    1713       <h3 id="rfc.section.5.3.2"><a href="#rfc.section.5.3.2">5.3.2</a>&nbsp;<a id="status.101" href="#status.101">101 Switching Protocols</a></h3>
    1714       <p id="rfc.section.5.3.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.21"><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
     1693      <h3 id="rfc.section.5.2.2"><a href="#rfc.section.5.2.2">5.2.2</a>&nbsp;<a id="status.101" href="#status.101">101 Switching Protocols</a></h3>
     1694      <p id="rfc.section.5.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.21"><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
    17151695         by the response's Upgrade header field immediately after the empty line which terminates the 101 response.
    17161696      </p>
    1717       <p id="rfc.section.5.3.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
     1697      <p id="rfc.section.5.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
    17181698         older versions, and switching to a real-time, synchronous protocol might be advantageous when delivering resources that use
    17191699         such features.
    17201700      </p>
    1721       <h2 id="rfc.section.5.4"><a href="#rfc.section.5.4">5.4</a>&nbsp;<a id="status.2xx" href="#status.2xx">Successful 2xx</a></h2>
     1701      <h2 id="rfc.section.5.3"><a href="#rfc.section.5.3">5.3</a>&nbsp;<a id="status.2xx" href="#status.2xx">Successful 2xx</a></h2>
    17221702      <div id="rfc.iref.24"></div>
    17231703      <div id="rfc.iref.s.5"></div>
    1724       <p id="rfc.section.5.4.p.1">This class of status code indicates that the client's request was successfully received, understood, and accepted.</p>
     1704      <p id="rfc.section.5.3.p.1">This class of status code indicates that the client's request was successfully received, understood, and accepted.</p>
    17251705      <div id="rfc.iref.25"></div>
    17261706      <div id="rfc.iref.s.6"></div>
    1727       <h3 id="rfc.section.5.4.1"><a href="#rfc.section.5.4.1">5.4.1</a>&nbsp;<a id="status.200" href="#status.200">200 OK</a></h3>
    1728       <p id="rfc.section.5.4.1.p.1">The request has succeeded. The payload returned with the response is dependent on the method used in the request, for example: </p>
     1707      <h3 id="rfc.section.5.3.1"><a href="#rfc.section.5.3.1">5.3.1</a>&nbsp;<a id="status.200" href="#status.200">200 OK</a></h3>
     1708      <p id="rfc.section.5.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>
    17291709      <dl>
    17301710         <dt>GET</dt>
    … …  
    17371717         <dd>a representation containing the request message as received by the end server.</dd>
    17381718      </dl>
    1739       <p id="rfc.section.5.4.1.p.2">Caches <em class="bcp14">MAY</em> use a heuristic (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 4.1.2</a> of <a href="#Part6" id="rfc.xref.Part6.11"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>) to determine freshness for 200 responses.
     1719      <p id="rfc.section.5.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.10"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>) to determine freshness for 200 responses.
    17401720      </p>
    17411721      <div id="rfc.iref.26"></div>
    17421722      <div id="rfc.iref.s.7"></div>
    1743       <h3 id="rfc.section.5.4.2"><a href="#rfc.section.5.4.2">5.4.2</a>&nbsp;<a id="status.201" href="#status.201">201 Created</a></h3>
    1744       <p id="rfc.section.5.4.2.p.1">The request has been fulfilled and has resulted in one or more new resources being created.</p>
    1745       <p id="rfc.section.5.4.2.p.2">Newly created resources are typically linked to from the response payload, with the most relevant URI also being carried in
     1723      <h3 id="rfc.section.5.3.2"><a href="#rfc.section.5.3.2">5.3.2</a>&nbsp;<a id="status.201" href="#status.201">201 Created</a></h3>
     1724      <p id="rfc.section.5.3.2.p.1">The request has been fulfilled and has resulted in one or more new resources being created.</p>
     1725      <p id="rfc.section.5.3.2.p.2">Newly created resources are typically linked to from the response payload, with the most relevant URI also being carried in
    17461726         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
    17471727         (e.g., in the case of a response to a PUT request).
    17481728      </p>
    1749       <p id="rfc.section.5.4.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.
    1750       </p>
    1751       <p id="rfc.section.5.4.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
     1729      <p id="rfc.section.5.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.
     1730      </p>
     1731      <p id="rfc.section.5.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
    17521732         the <a href="#header.location" class="smpl">Location</a> header field or, in case the Location header field was omitted, by the Effective Request URI (see <a href="p4-conditional.html#header.etag" title="ETag">Section 2.3</a> of <a href="#Part4" id="rfc.xref.Part4.10"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>).
    17531733      </p>
    17541734      <div id="rfc.iref.27"></div>
    17551735      <div id="rfc.iref.s.8"></div>
    1756       <h3 id="rfc.section.5.4.3"><a href="#rfc.section.5.4.3">5.4.3</a>&nbsp;<a id="status.202" href="#status.202">202 Accepted</a></h3>
    1757       <p id="rfc.section.5.4.3.p.1">The request has been accepted for processing, but the processing has not been completed. The request might or might not eventually
     1736      <h3 id="rfc.section.5.3.3"><a href="#rfc.section.5.3.3">5.3.3</a>&nbsp;<a id="status.202" href="#status.202">202 Accepted</a></h3>
     1737      <p id="rfc.section.5.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
    17581738         be acted upon, as it might be disallowed when processing actually takes place. There is no facility for re-sending a status
    17591739         code from an asynchronous operation such as this.
    17601740      </p>
    1761       <p id="rfc.section.5.4.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
     1741      <p id="rfc.section.5.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
    17621742         (perhaps a batch-oriented process that is only run once per day) without requiring that the user agent's connection to the
    17631743         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
    … …  
    17661746      <div id="rfc.iref.28"></div>
    17671747      <div id="rfc.iref.s.9"></div>
    1768       <h3 id="rfc.section.5.4.4"><a href="#rfc.section.5.4.4">5.4.4</a>&nbsp;<a id="status.203" href="#status.203">203 Non-Authoritative Information</a></h3>
    1769       <p id="rfc.section.5.4.4.p.1">The representation in the response has been transformed or otherwise modified by a transforming proxy (<a href="p1-messaging.html#intermediaries" title="Intermediaries">Section 2.3</a> of <a href="#Part1" id="rfc.xref.Part1.22"><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.12"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>).
    1770       </p>
    1771       <p id="rfc.section.5.4.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
    1772          (<a href="p6-cache.html#header.warning" title="Warning">Section 7.6</a> of <a href="#Part6" id="rfc.xref.Part6.13"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>) is appropriate.
    1773       </p>
    1774       <p id="rfc.section.5.4.4.p.3">Caches <em class="bcp14">MAY</em> use a heuristic (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 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 203 responses.
     1748      <h3 id="rfc.section.5.3.4"><a href="#rfc.section.5.3.4">5.3.4</a>&nbsp;<a id="status.203" href="#status.203">203 Non-Authoritative Information</a></h3>
     1749      <p id="rfc.section.5.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.22"><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.11"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>).
     1750      </p>
     1751      <p id="rfc.section.5.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
     1752         (<a href="p6-cache.html#header.warning" title="Warning">Section 7.6</a> of <a href="#Part6" id="rfc.xref.Part6.12"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>) is appropriate.
     1753      </p>
     1754      <p id="rfc.section.5.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.13"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>) to determine freshness for 203 responses.
    17751755      </p>
    17761756      <div id="rfc.iref.29"></div>
    17771757      <div id="rfc.iref.s.10"></div>
    1778       <h3 id="rfc.section.5.4.5"><a href="#rfc.section.5.4.5">5.4.5</a>&nbsp;<a id="status.204" href="#status.204">204 No Content</a></h3>
    1779       <p id="rfc.section.5.4.5.p.1">The 204 (No Content) status code indicates that the server has successfully fulfilled the request and that there is no additional
     1758      <h3 id="rfc.section.5.3.5"><a href="#rfc.section.5.3.5">5.3.5</a>&nbsp;<a id="status.204" href="#status.204">204 No Content</a></h3>
     1759      <p id="rfc.section.5.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
    17801760         content to return in the response payload body. Metadata in the response header fields refer to the target resource and its
    17811761         current representation after the requested action.
    17821762      </p>
    1783       <p id="rfc.section.5.4.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
     1763      <p id="rfc.section.5.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
    17841764         target resource.
    17851765      </p>
    1786       <p id="rfc.section.5.4.5.p.3">The 204 response allows a server to indicate that the action has been successfully applied to the target resource while implying
     1766      <p id="rfc.section.5.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
    17871767         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
    17881768         of the success to its user, in accord with its own interface, and apply any new or updated metadata in the response to the
    17891769         active representation.
    17901770      </p>
    1791       <p id="rfc.section.5.4.5.p.4">For example, a 204 status code is commonly used with document editing interfaces corresponding to a "save" action, such that
     1771      <p id="rfc.section.5.3.5.p.4">For example, a 204 status code is commonly used with document editing interfaces corresponding to a "save" action, such that
    17921772         the document being saved remains available to the user for editing. It is also frequently used with interfaces that expect
    17931773         automated data transfers to be prevalent, such as within distributed version control systems.
    17941774      </p>
    1795       <p id="rfc.section.5.4.5.p.5">The 204 response <em class="bcp14">MUST NOT</em> include a message body, and thus is always terminated by the first empty line after the header fields.
     1775      <p id="rfc.section.5.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.
    17961776      </p>
    17971777      <div id="rfc.iref.30"></div>
    17981778      <div id="rfc.iref.s.11"></div>
    1799       <h3 id="rfc.section.5.4.6"><a href="#rfc.section.5.4.6">5.4.6</a>&nbsp;<a id="status.205" href="#status.205">205 Reset Content</a></h3>
    1800       <p id="rfc.section.5.4.6.p.1">The server has fulfilled the request and the user agent <em class="bcp14">SHOULD</em> reset the document view which caused the request to be sent. This response is primarily intended to allow input for actions
     1779      <h3 id="rfc.section.5.3.6"><a href="#rfc.section.5.3.6">5.3.6</a>&nbsp;<a id="status.205" href="#status.205">205 Reset Content</a></h3>
     1780      <p id="rfc.section.5.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
    18011781         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
    18021782         another input action.
    18031783      </p>
    1804       <p id="rfc.section.5.4.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.23"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>.
    1805       </p>
    1806       <h2 id="rfc.section.5.5"><a href="#rfc.section.5.5">5.5</a>&nbsp;<a id="status.3xx" href="#status.3xx">Redirection 3xx</a></h2>
     1784      <p id="rfc.section.5.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.23"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>.
     1785      </p>
     1786      <h2 id="rfc.section.5.4"><a href="#rfc.section.5.4">5.4</a>&nbsp;<a id="status.3xx" href="#status.3xx">Redirection 3xx</a></h2>
    18071787      <div id="rfc.iref.31"></div>
    18081788      <div id="rfc.iref.s.12"></div>
    1809       <p id="rfc.section.5.5.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.
     1789      <p id="rfc.section.5.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.
    18101790         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
    18111791         known to be "safe", as defined in <a href="#safe.methods" title="Safe Methods">Section&nbsp;3.2.1</a>.
    18121792      </p>
    1813       <p id="rfc.section.5.5.p.2">There are several types of redirects: </p>
     1793      <p id="rfc.section.5.4.p.2">There are several types of redirects: </p>
    18141794      <ol>
    18151795         <li>
    … …  
    18341814         </li>
    18351815      </ol>
    1836       <div class="note" id="rfc.section.5.5.p.3">
     1816      <div class="note" id="rfc.section.5.4.p.3">
    18371817         <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
    18381818            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
    … …  
    18401820         </p>
    18411821      </div>
    1842       <p id="rfc.section.5.5.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.3" title="Location">Section&nbsp;10.13</a>.
    1843       </p>
    1844       <p id="rfc.section.5.5.p.5">Note that for methods not known to be "safe", as defined in <a href="#safe.methods" title="Safe Methods">Section&nbsp;3.2.1</a>, automatic redirection needs to done with care, since the redirect might change the conditions under which the request was
     1822      <p id="rfc.section.5.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.3" title="Location">Section&nbsp;10.13</a>.
     1823      </p>
     1824      <p id="rfc.section.5.4.p.5">Note that for methods not known to be "safe", as defined in <a href="#safe.methods" title="Safe Methods">Section&nbsp;3.2.1</a>, automatic redirection needs to done with care, since the redirect might change the conditions under which the request was
    18451825         issued.
    18461826      </p>
    1847       <p id="rfc.section.5.5.p.6">Clients <em class="bcp14">SHOULD</em> detect and intervene in cyclical redirections (i.e., "infinite" redirection loops).
    1848       </p>
    1849       <div class="note" id="rfc.section.5.5.p.7">
     1827      <p id="rfc.section.5.4.p.6">Clients <em class="bcp14">SHOULD</em> detect and intervene in cyclical redirections (i.e., "infinite" redirection loops).
     1828      </p>
     1829      <div class="note" id="rfc.section.5.4.p.7">
    18501830         <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.
    18511831         </p>
    … …  
    18531833      <div id="rfc.iref.32"></div>
    18541834      <div id="rfc.iref.s.13"></div>
    1855       <h3 id="rfc.section.5.5.1"><a href="#rfc.section.5.5.1">5.5.1</a>&nbsp;<a id="status.300" href="#status.300">300 Multiple Choices</a></h3>
    1856       <p id="rfc.section.5.5.1.p.1">The target resource has more than one representation, each with its own specific location, and agent-driven negotiation information
     1835      <h3 id="rfc.section.5.4.1"><a href="#rfc.section.5.4.1">5.4.1</a>&nbsp;<a id="status.300" href="#status.300">300 Multiple Choices</a></h3>
     1836      <p id="rfc.section.5.4.1.p.1">The target resource has more than one representation, each with its own specific location, and agent-driven negotiation information
    18571837         (<a href="#content.negotiation" title="Content Negotiation">Section&nbsp;9</a>) is being provided so that the user (or user agent) can select a preferred representation by redirecting its request to that
    18581838         location.
    18591839      </p>
    1860       <p id="rfc.section.5.5.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
     1840      <p id="rfc.section.5.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
    18611841         choose the one most appropriate. Depending upon the format and the capabilities of the user agent, selection of the most appropriate
    18621842         choice <em class="bcp14">MAY</em> be performed automatically. However, this specification does not define any standard for such automatic selection.
    18631843      </p>
    1864       <p id="rfc.section.5.5.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.
    1865       </p>
    1866       <p id="rfc.section.5.5.1.p.4">Caches <em class="bcp14">MAY</em> use a heuristic (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 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 300 responses.
     1844      <p id="rfc.section.5.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.
     1845      </p>
     1846      <p id="rfc.section.5.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.14"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>) to determine freshness for 300 responses.
    18671847      </p>
    18681848      <div id="rfc.iref.33"></div>
    18691849      <div id="rfc.iref.s.14"></div>
    1870       <h3 id="rfc.section.5.5.2"><a href="#rfc.section.5.5.2">5.5.2</a>&nbsp;<a id="status.301" href="#status.301">301 Moved Permanently</a></h3>
    1871       <p id="rfc.section.5.5.2.p.1">The target resource has been assigned a new permanent URI and any future references to this resource <em class="bcp14">SHOULD</em> use one of the returned URIs. Clients with link editing capabilities ought to automatically re-link references to the effective
     1850      <h3 id="rfc.section.5.4.2"><a href="#rfc.section.5.4.2">5.4.2</a>&nbsp;<a id="status.301" href="#status.301">301 Moved Permanently</a></h3>
     1851      <p id="rfc.section.5.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
    18721852         request URI to one or more of the new references returned by the server, where possible.
    18731853      </p>
    1874       <p id="rfc.section.5.5.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.16"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>) to determine freshness for 301 responses.
    1875       </p>
    1876       <p id="rfc.section.5.5.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).
    1877       </p>
    1878       <div class="note" id="rfc.section.5.5.2.p.4">
     1854      <p id="rfc.section.5.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.15"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>) to determine freshness for 301 responses.
     1855      </p>
     1856      <p id="rfc.section.5.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).
     1857      </p>
     1858      <div class="note" id="rfc.section.5.4.2.p.4">
    18791859         <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.
    18801860         </p>
    … …  
    18821862      <div id="rfc.iref.34"></div>
    18831863      <div id="rfc.iref.s.15"></div>
    1884       <h3 id="rfc.section.5.5.3"><a href="#rfc.section.5.5.3">5.5.3</a>&nbsp;<a id="status.302" href="#status.302">302 Found</a></h3>
    1885       <p id="rfc.section.5.5.3.p.1">The target resource resides temporarily under a different URI. Since the redirection might be altered on occasion, the client <em class="bcp14">SHOULD</em> continue to use the effective request URI for future requests.
    1886       </p>
    1887       <p id="rfc.section.5.5.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).
    1888       </p>
    1889       <div class="note" id="rfc.section.5.5.3.p.3">
     1864      <h3 id="rfc.section.5.4.3"><a href="#rfc.section.5.4.3">5.4.3</a>&nbsp;<a id="status.302" href="#status.302">302 Found</a></h3>
     1865      <p id="rfc.section.5.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.
     1866      </p>
     1867      <p id="rfc.section.5.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).
     1868      </p>
     1869      <div class="note" id="rfc.section.5.4.3.p.3">
    18901870         <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.
    18911871         </p>
    … …  
    18931873      <div id="rfc.iref.35"></div>
    18941874      <div id="rfc.iref.s.16"></div>
    1895       <h3 id="rfc.section.5.5.4"><a href="#rfc.section.5.5.4">5.5.4</a>&nbsp;<a id="status.303" href="#status.303">303 See Other</a></h3>
    1896       <p id="rfc.section.5.5.4.p.1">The 303 status code indicates that the server is redirecting the user agent to a different resource, as indicated by a URI
     1875      <h3 id="rfc.section.5.4.4"><a href="#rfc.section.5.4.4">5.4.4</a>&nbsp;<a id="status.303" href="#status.303">303 See Other</a></h3>
     1876      <p id="rfc.section.5.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
    18971877         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,
    18981878         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,
    … …  
    19001880         not considered equivalent to the effective request URI.
    19011881      </p>
    1902       <p id="rfc.section.5.5.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
     1882      <p id="rfc.section.5.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
    19031883         redirect the user agent to a selected resource, since doing so provides the information corresponding to the POST response
    19041884         in a form that can be separately identified, bookmarked, and cached independent of the original request.
    19051885      </p>
    1906       <p id="rfc.section.5.5.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
     1886      <p id="rfc.section.5.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
    19071887         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
    19081888         to recipients without implying that it adequately represents the target resource. Note that answers to the questions of what
    … …  
    19101890         and thus entirely determined by the URI owner(s).
    19111891      </p>
    1912       <p id="rfc.section.5.5.4.p.4">Except for responses to a HEAD request, the representation of a 303 response <em class="bcp14">SHOULD</em> contain a short hypertext note with a hyperlink to the <a href="#header.location" class="smpl">Location</a> URI.
     1892      <p id="rfc.section.5.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.
    19131893      </p>
    19141894      <div id="rfc.iref.36"></div>
    19151895      <div id="rfc.iref.s.17"></div>
    1916       <h3 id="rfc.section.5.5.5"><a href="#rfc.section.5.5.5">5.5.5</a>&nbsp;<a id="status.305" href="#status.305">305 Use Proxy</a></h3>
    1917       <p id="rfc.section.5.5.5.p.1">The 305 status code was defined in a previous version of this specification (see <a href="#changes.from.rfc.2616" title="Changes from RFC 2616">Appendix&nbsp;C</a>), and is now deprecated.
     1896      <h3 id="rfc.section.5.4.5"><a href="#rfc.section.5.4.5">5.4.5</a>&nbsp;<a id="status.305" href="#status.305">305 Use Proxy</a></h3>
     1897      <p id="rfc.section.5.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.
    19181898      </p>
    19191899      <div id="rfc.iref.37"></div>
    19201900      <div id="rfc.iref.s.18"></div>
    1921       <h3 id="rfc.section.5.5.6"><a href="#rfc.section.5.5.6">5.5.6</a>&nbsp;<a id="status.306" href="#status.306">306 (Unused)</a></h3>
    1922       <p id="rfc.section.5.5.6.p.1">The 306 status code was used in a previous version of the specification, is no longer used, and the code is reserved.</p>
     1901      <h3 id="rfc.section.5.4.6"><a href="#rfc.section.5.4.6">5.4.6</a>&nbsp;<a id="status.306" href="#status.306">306 (Unused)</a></h3>
     1902      <p id="rfc.section.5.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>
    19231903      <div id="rfc.iref.38"></div>
    19241904      <div id="rfc.iref.s.19"></div>
    1925       <h3 id="rfc.section.5.5.7"><a href="#rfc.section.5.5.7">5.5.7</a>&nbsp;<a id="status.307" href="#status.307">307 Temporary Redirect</a></h3>
    1926       <p id="rfc.section.5.5.7.p.1">The target resource resides temporarily under a different URI. Since the redirection can change over time, the client <em class="bcp14">SHOULD</em> continue to use the effective request URI for future requests.
    1927       </p>
    1928       <p id="rfc.section.5.5.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).
    1929       </p>
    1930       <div class="note" id="rfc.section.5.5.7.p.3">
     1905      <h3 id="rfc.section.5.4.7"><a href="#rfc.section.5.4.7">5.4.7</a>&nbsp;<a id="status.307" href="#status.307">307 Temporary Redirect</a></h3>
     1906      <p id="rfc.section.5.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.
     1907      </p>
     1908      <p id="rfc.section.5.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).
     1909      </p>
     1910      <div class="note" id="rfc.section.5.4.7.p.3">
    19311911         <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
    19321912            for <a href="#status.301" class="smpl">301 (Moved
    … …  
    19341914         </p>
    19351915      </div>
    1936       <h2 id="rfc.section.5.6"><a href="#rfc.section.5.6">5.6</a>&nbsp;<a id="status.4xx" href="#status.4xx">Client Error 4xx</a></h2>
     1916      <h2 id="rfc.section.5.5"><a href="#rfc.section.5.5">5.5</a>&nbsp;<a id="status.4xx" href="#status.4xx">Client Error 4xx</a></h2>
    19371917      <div id="rfc.iref.39"></div>
    19381918      <div id="rfc.iref.s.20"></div>
    1939       <p id="rfc.section.5.6.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
     1919      <p id="rfc.section.5.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
    19401920         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.
    19411921         These status codes are applicable to any request method. User agents <em class="bcp14">SHOULD</em> display any included representation to the user.
    … …  
    19431923      <div id="rfc.iref.40"></div>
    19441924      <div id="rfc.iref.s.21"></div>
    1945       <h3 id="rfc.section.5.6.1"><a href="#rfc.section.5.6.1">5.6.1</a>&nbsp;<a id="status.400" href="#status.400">400 Bad Request</a></h3>
    1946       <p id="rfc.section.5.6.1.p.1">The server cannot or will not process the request, due to a client error (e.g., malformed syntax).</p>
     1925      <h3 id="rfc.section.5.5.1"><a href="#rfc.section.5.5.1">5.5.1</a>&nbsp;<a id="status.400" href="#status.400">400 Bad Request</a></h3>
     1926      <p id="rfc.section.5.5.1.p.1">The server cannot or will not process the request, due to a client error (e.g., malformed syntax).</p>
    19471927      <div id="rfc.iref.41"></div>
    19481928      <div id="rfc.iref.s.22"></div>
    1949       <h3 id="rfc.section.5.6.2"><a href="#rfc.section.5.6.2">5.6.2</a>&nbsp;<a id="status.402" href="#status.402">402 Payment Required</a></h3>
    1950       <p id="rfc.section.5.6.2.p.1">This code is reserved for future use.</p>
     1929      <h3 id="rfc.section.5.5.2"><a href="#rfc.section.5.5.2">5.5.2</a>&nbsp;<a id="status.402" href="#status.402">402 Payment Required</a></h3>
     1930      <p id="rfc.section.5.5.2.p.1">This code is reserved for future use.</p>
    19511931      <div id="rfc.iref.42"></div>
    19521932      <div id="rfc.iref.s.23"></div>
    1953       <h3 id="rfc.section.5.6.3"><a href="#rfc.section.5.6.3">5.6.3</a>&nbsp;<a id="status.403" href="#status.403">403 Forbidden</a></h3>
    1954       <p id="rfc.section.5.6.3.p.1">The server understood the request, but refuses to authorize it. Providing different user authentication credentials might
     1933      <h3 id="rfc.section.5.5.3"><a href="#rfc.section.5.5.3">5.5.3</a>&nbsp;<a id="status.403" href="#status.403">403 Forbidden</a></h3>
     1934      <p id="rfc.section.5.5.3.p.1">The server understood the request, but refuses to authorize it. Providing different user authentication credentials might
    19551935         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.
    19561936      </p>
    1957       <p id="rfc.section.5.6.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
     1937      <p id="rfc.section.5.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
    19581938         to the client, the status code <a href="#status.404" class="smpl">404
    19591939            (Not Found)</a>  <em class="bcp14">MAY</em> be used instead.
    … …  
    19611941      <div id="rfc.iref.43"></div>
    19621942      <div id="rfc.iref.s.24"></div>
    1963       <h3 id="rfc.section.5.6.4"><a href="#rfc.section.5.6.4">5.6.4</a>&nbsp;<a id="status.404" href="#status.404">404 Not Found</a></h3>
    1964       <p id="rfc.section.5.6.4.p.1">The server has not found anything matching the effective request URI. No indication is given of whether the condition is temporary
     1943      <h3 id="rfc.section.5.5.4"><a href="#rfc.section.5.5.4">5.5.4</a>&nbsp;<a id="status.404" href="#status.404">404 Not Found</a></h3>
     1944      <p id="rfc.section.5.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
    19651945         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
    19661946         and has no forwarding address. This status code is commonly used when the server does not wish to reveal exactly why the request
    … …  
    19691949      <div id="rfc.iref.44"></div>
    19701950      <div id="rfc.iref.s.25"></div>
    1971       <h3 id="rfc.section.5.6.5"><a href="#rfc.section.5.6.5">5.6.5</a>&nbsp;<a id="status.405" href="#status.405">405 Method Not Allowed</a></h3>
    1972       <p id="rfc.section.5.6.5.p.1">The method specified in the request-line is not allowed for the target resource. The response <em class="bcp14">MUST</em> include an <a href="#header.allow" class="smpl">Allow</a> header field containing a list of valid methods for the requested resource.
     1951      <h3 id="rfc.section.5.5.5"><a href="#rfc.section.5.5.5">5.5.5</a>&nbsp;<a id="status.405" href="#status.405">405 Method Not Allowed</a></h3>
     1952      <p id="rfc.section.5.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.
    19731953      </p>
    19741954      <div id="rfc.iref.45"></div>
    19751955      <div id="rfc.iref.s.26"></div>
    1976       <h3 id="rfc.section.5.6.6"><a href="#rfc.section.5.6.6">5.6.6</a>&nbsp;<a id="status.406" href="#status.406">406 Not Acceptable</a></h3>
    1977       <p id="rfc.section.5.6.6.p.1">The resource identified by the request is only capable of generating response representations which have content characteristics
     1956      <h3 id="rfc.section.5.5.6"><a href="#rfc.section.5.5.6">5.5.6</a>&nbsp;<a id="status.406" href="#status.406">406 Not Acceptable</a></h3>
     1957      <p id="rfc.section.5.5.6.p.1">The resource identified by the request is only capable of generating response representations which have content characteristics
    19781958         not acceptable according to the <a href="#header.accept" class="smpl">Accept</a> and Accept-* header fields sent in the request.
    19791959      </p>
    1980       <p id="rfc.section.5.6.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
     1960      <p id="rfc.section.5.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
    19811961         or user agent can choose the one most appropriate. Depending upon the format and the capabilities of the user agent, selection
    19821962         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.
    19831963      </p>
    1984       <div class="note" id="rfc.section.5.6.6.p.3">
     1964      <div class="note" id="rfc.section.5.5.6.p.3">
    19851965         <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
    19861966            request. In some cases, this might even be preferable to sending a 406 response. User agents are encouraged to inspect the
    … …  
    19881968         </p>
    19891969      </div>
    1990       <p id="rfc.section.5.6.6.p.4">If the response could be unacceptable, a user agent <em class="bcp14">SHOULD</em> temporarily stop receipt of more data and query the user for a decision on further actions.
     1970      <p id="rfc.section.5.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.
    19911971      </p>
    19921972      <div id="rfc.iref.46"></div>
    19931973      <div id="rfc.iref.s.27"></div>
    1994       <h3 id="rfc.section.5.6.7"><a href="#rfc.section.5.6.7">5.6.7</a>&nbsp;<a id="status.408" href="#status.408">408 Request Timeout</a></h3>
    1995       <p id="rfc.section.5.6.7.p.1">The client did not produce a request within the time that the server was prepared to wait. The client <em class="bcp14">MAY</em> repeat the request without modifications at any later time.
     1974      <h3 id="rfc.section.5.5.7"><a href="#rfc.section.5.5.7">5.5.7</a>&nbsp;<a id="status.408" href="#status.408">408 Request Timeout</a></h3>
     1975      <p id="rfc.section.5.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.
    19961976      </p>
    19971977      <div id="rfc.iref.47"></div>
    19981978      <div id="rfc.iref.s.28"></div>
    1999       <h3 id="rfc.section.5.6.8"><a href="#rfc.section.5.6.8">5.6.8</a>&nbsp;<a id="status.409" href="#status.409">409 Conflict</a></h3>
    2000       <p id="rfc.section.5.6.8.p.1">The request could not be completed due to a conflict with the current state of the resource. This code is only allowed in
     1979      <h3 id="rfc.section.5.5.8"><a href="#rfc.section.5.5.8">5.5.8</a>&nbsp;<a id="status.409" href="#status.409">409 Conflict</a></h3>
     1980      <p id="rfc.section.5.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
    20011981         situations where it is expected that the user might be able to resolve the conflict and resubmit the request. The response
    20021982         body <em class="bcp14">SHOULD</em> include enough information for the user to recognize the source of the conflict. Ideally, the response representation would
    20031983         include enough information for the user or user agent to fix the problem; however, that might not be possible and is not required.
    20041984      </p>
    2005       <p id="rfc.section.5.6.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
     1985      <p id="rfc.section.5.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
    20061986         being PUT included changes to a resource which conflict with those made by an earlier (third-party) request, the server might
    20071987         use the 409 response to indicate that it can't complete the request. In this case, the response representation would likely
    … …  
    20101990      <div id="rfc.iref.48"></div>
    20111991      <div id="rfc.iref.s.29"></div>
    2012       <h3 id="rfc.section.5.6.9"><a href="#rfc.section.5.6.9">5.6.9</a>&nbsp;<a id="status.410" href="#status.410">410 Gone</a></h3>
    2013       <p id="rfc.section.5.6.9.p.1">The target resource is no longer available at the server and no forwarding address is known. This condition is expected to
     1992      <h3 id="rfc.section.5.5.9"><a href="#rfc.section.5.5.9">5.5.9</a>&nbsp;<a id="status.410" href="#status.410">410 Gone</a></h3>
     1993      <p id="rfc.section.5.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
    20141994         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,
    20151995         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.
    20161996      </p>
    2017       <p id="rfc.section.5.6.9.p.2">The 410 response is primarily intended to assist the task of web maintenance by notifying the recipient that the resource
     1997      <p id="rfc.section.5.5.9.p.2">The 410 response is primarily intended to assist the task of web maintenance by notifying the recipient that the resource
    20181998         is intentionally unavailable and that the server owners desire that remote links to that resource be removed. Such an event
    20191999         is common for limited-time, promotional services and for resources belonging to individuals no longer working at the server's
    … …  
    20212001         — that is left to the discretion of the server owner.
    20222002      </p>
    2023       <p id="rfc.section.5.6.9.p.3">Caches <em class="bcp14">MAY</em> use a heuristic (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 4.1.2</a> of <a href="#Part6" id="rfc.xref.Part6.17"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>) to determine freshness for 410 responses.
     2003      <p id="rfc.section.5.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.16"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>) to determine freshness for 410 responses.
    20242004      </p>
    20252005      <div id="rfc.iref.49"></div>
    20262006      <div id="rfc.iref.s.30"></div>
    2027       <h3 id="rfc.section.5.6.10"><a href="#rfc.section.5.6.10">5.6.10</a>&nbsp;<a id="status.411" href="#status.411">411 Length Required</a></h3>
    2028       <p id="rfc.section.5.6.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
     2007      <h3 id="rfc.section.5.5.10"><a href="#rfc.section.5.5.10">5.5.10</a>&nbsp;<a id="status.411" href="#status.411">411 Length Required</a></h3>
     2008      <p id="rfc.section.5.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
    20292009         message.
    20302010      </p>
    20312011      <div id="rfc.iref.50"></div>
    20322012      <div id="rfc.iref.s.31"></div>
    2033       <h3 id="rfc.section.5.6.11"><a href="#rfc.section.5.6.11">5.6.11</a>&nbsp;<a id="status.413" href="#status.413">413 Request Representation Too Large</a></h3>
    2034       <p id="rfc.section.5.6.11.p.1">The server is refusing to process a request because the request representation is larger than the server is willing or able
     2013      <h3 id="rfc.section.5.5.11"><a href="#rfc.section.5.5.11">5.5.11</a>&nbsp;<a id="status.413" href="#status.413">413 Request Representation Too Large</a></h3>
     2014      <p id="rfc.section.5.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
    20352015         to process. The server <em class="bcp14">MAY</em> close the connection to prevent the client from continuing the request.
    20362016      </p>
    2037       <p id="rfc.section.5.6.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.
     2017      <p id="rfc.section.5.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.
    20382018      </p>
    20392019      <div id="rfc.iref.51"></div>
    20402020      <div id="rfc.iref.s.32"></div>
    2041       <h3 id="rfc.section.5.6.12"><a href="#rfc.section.5.6.12">5.6.12</a>&nbsp;<a id="status.414" href="#status.414">414 URI Too Long</a></h3>
    2042       <p id="rfc.section.5.6.12.p.1">The server is refusing to service the request because the effective request URI is longer than the server is willing to interpret.
     2021      <h3 id="rfc.section.5.5.12"><a href="#rfc.section.5.5.12">5.5.12</a>&nbsp;<a id="status.414" href="#status.414">414 URI Too Long</a></h3>
     2022      <p id="rfc.section.5.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.
    20432023         This rare condition is only likely to occur when a client has improperly converted a POST request to a GET request with long
    20442024         query information, when the client has descended into a URI "black hole" of redirection (e.g., a redirected URI prefix that
    … …  
    20482028      <div id="rfc.iref.52"></div>
    20492029      <div id="rfc.iref.s.33"></div>
    2050       <h3 id="rfc.section.5.6.13"><a href="#rfc.section.5.6.13">5.6.13</a>&nbsp;<a id="status.415" href="#status.415">415 Unsupported Media Type</a></h3>
    2051       <p id="rfc.section.5.6.13.p.1">The server is refusing to service the request because the request payload is in a format not supported by this request method
     2030      <h3 id="rfc.section.5.5.13"><a href="#rfc.section.5.5.13">5.5.13</a>&nbsp;<a id="status.415" href="#status.415">415 Unsupported Media Type</a></h3>
     2031      <p id="rfc.section.5.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
    20522032         on the target resource.
    20532033      </p>
    20542034      <div id="rfc.iref.53"></div>
    20552035      <div id="rfc.iref.s.34"></div>
    2056       <h3 id="rfc.section.5.6.14"><a href="#rfc.section.5.6.14">5.6.14</a>&nbsp;<a id="status.417" href="#status.417">417 Expectation Failed</a></h3>
    2057       <p id="rfc.section.5.6.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
     2036      <h3 id="rfc.section.5.5.14"><a href="#rfc.section.5.5.14">5.5.14</a>&nbsp;<a id="status.417" href="#status.417">417 Expectation Failed</a></h3>
     2037      <p id="rfc.section.5.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
    20582038         not be met by the next-hop server.
    20592039      </p>
    20602040      <div id="rfc.iref.54"></div>
    20612041      <div id="rfc.iref.s.35"></div>
    2062       <h3 id="rfc.section.5.6.15"><a href="#rfc.section.5.6.15">5.6.15</a>&nbsp;<a id="status.426" href="#status.426">426 Upgrade Required</a></h3>
    2063       <p id="rfc.section.5.6.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.24"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>) specifying the required protocols.
     2042      <h3 id="rfc.section.5.5.15"><a href="#rfc.section.5.5.15">5.5.15</a>&nbsp;<a id="status.426" href="#status.426">426 Upgrade Required</a></h3>
     2043      <p id="rfc.section.5.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.24"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>) specifying the required protocols.
    20642044      </p>
    20652045      <div id="rfc.figure.u.5"></div>
    … …  
    20712051
    20722052<span id="s426body">This service requires use of the HTTP/3.0 protocol.
    2073 </span></pre><p id="rfc.section.5.6.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
     2053</span></pre><p id="rfc.section.5.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
    20742054         alternative courses which might be available to the user.
    20752055      </p>
    2076       <h2 id="rfc.section.5.7"><a href="#rfc.section.5.7">5.7</a>&nbsp;<a id="status.5xx" href="#status.5xx">Server Error 5xx</a></h2>
     2056      <h2 id="rfc.section.5.6"><a href="#rfc.section.5.6">5.6</a>&nbsp;<a id="status.5xx" href="#status.5xx">Server Error 5xx</a></h2>
    20772057      <div id="rfc.iref.55"></div>
    20782058      <div id="rfc.iref.s.36"></div>
    2079       <p id="rfc.section.5.7.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
     2059      <p id="rfc.section.5.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
    20802060         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.
    20812061         User agents <em class="bcp14">SHOULD</em> display any included representation to the user. These response codes are applicable to any request method.
    … …  
    20832063      <div id="rfc.iref.56"></div>
    20842064      <div id="rfc.iref.s.37"></div>
    2085       <h3 id="rfc.section.5.7.1"><a href="#rfc.section.5.7.1">5.7.1</a>&nbsp;<a id="status.500" href="#status.500">500 Internal Server Error</a></h3>
    2086       <p id="rfc.section.5.7.1.p.1">The server encountered an unexpected condition which prevented it from fulfilling the request.</p>
     2065      <h3 id="rfc.section.5.6.1"><a href="#rfc.section.5.6.1">5.6.1</a>&nbsp;<a id="status.500" href="#status.500">500 Internal Server Error</a></h3>
     2066      <p id="rfc.section.5.6.1.p.1">The server encountered an unexpected condition which prevented it from fulfilling the request.</p>
    20872067      <div id="rfc.iref.57"></div>
    20882068      <div id="rfc.iref.s.38"></div>
    2089       <h3 id="rfc.section.5.7.2"><a href="#rfc.section.5.7.2">5.7.2</a>&nbsp;<a id="status.501" href="#status.501">501 Not Implemented</a></h3>
    2090       <p id="rfc.section.5.7.2.p.1">The server does not support the functionality required to fulfill the request. This is the appropriate response when the server
     2069      <h3 id="rfc.section.5.6.2"><a href="#rfc.section.5.6.2">5.6.2</a>&nbsp;<a id="status.501" href="#status.501">501 Not Implemented</a></h3>
     2070      <p id="rfc.section.5.6.2.p.1">The server does not support the functionality required to fulfill the request. This is the appropriate response when the server
    20912071         does not recognize the request method and is not capable of supporting it for any resource.
    20922072      </p>
    20932073      <div id="rfc.iref.58"></div>
    20942074      <div id="rfc.iref.s.39"></div>
    2095       <h3 id="rfc.section.5.7.3"><a href="#rfc.section.5.7.3">5.7.3</a>&nbsp;<a id="status.502" href="#status.502">502 Bad Gateway</a></h3>
    2096       <p id="rfc.section.5.7.3.p.1">The server, while acting as a gateway or proxy, received an invalid response from the upstream server it accessed in attempting
     2075      <h3 id="rfc.section.5.6.3"><a href="#rfc.section.5.6.3">5.6.3</a>&nbsp;<a id="status.502" href="#status.502">502 Bad Gateway</a></h3>
     2076      <p id="rfc.section.5.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
    20972077         to fulfill the request.
    20982078      </p>
    20992079      <div id="rfc.iref.59"></div>
    21002080      <div id="rfc.iref.s.40"></div>
    2101       <h3 id="rfc.section.5.7.4"><a href="#rfc.section.5.7.4">5.7.4</a>&nbsp;<a id="status.503" href="#status.503">503 Service Unavailable</a></h3>
    2102       <p id="rfc.section.5.7.4.p.1">The server is currently unable to handle the request due to a temporary overloading or maintenance of the server.</p>
    2103       <p id="rfc.section.5.7.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
     2081      <h3 id="rfc.section.5.6.4"><a href="#rfc.section.5.6.4">5.6.4</a>&nbsp;<a id="status.503" href="#status.503">503 Service Unavailable</a></h3>
     2082      <p id="rfc.section.5.6.4.p.1">The server is currently unable to handle the request due to a temporary overloading or maintenance of the server.</p>
     2083      <p id="rfc.section.5.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
    21042084         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.2" 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
    21052085            Server Error)</a> response.
    21062086      </p>
    2107       <div class="note" id="rfc.section.5.7.4.p.3">
     2087      <div class="note" id="rfc.section.5.6.4.p.3">
    21082088         <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
    21092089            wish to simply refuse the connection.
    … …  
    21122092      <div id="rfc.iref.60"></div>
    21132093      <div id="rfc.iref.s.41"></div>
    2114       <h3 id="rfc.section.5.7.5"><a href="#rfc.section.5.7.5">5.7.5</a>&nbsp;<a id="status.504" href="#status.504">504 Gateway Timeout</a></h3>
    2115       <p id="rfc.section.5.7.5.p.1">The server, while acting as a gateway or proxy, did not receive a timely response from the upstream server specified by the
     2094      <h3 id="rfc.section.5.6.5"><a href="#rfc.section.5.6.5">5.6.5</a>&nbsp;<a id="status.504" href="#status.504">504 Gateway Timeout</a></h3>
     2095      <p id="rfc.section.5.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
    21162096         URI (e.g., HTTP, FTP, LDAP) or some other auxiliary server (e.g., DNS) it needed to access in attempting to complete the request.
    21172097      </p>
    2118       <div class="note" id="rfc.section.5.7.5.p.2">
     2098      <div class="note" id="rfc.section.5.6.5.p.2">
    21192099         <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
    21202100               Error)</a> when DNS lookups time out.
    … …  
    21232103      <div id="rfc.iref.61"></div>
    21242104      <div id="rfc.iref.s.42"></div>
    2125       <h3 id="rfc.section.5.7.6"><a href="#rfc.section.5.7.6">5.7.6</a>&nbsp;<a id="status.505" href="#status.505">505 HTTP Version Not Supported</a></h3>
    2126       <p id="rfc.section.5.7.6.p.1">The server does not support, or refuses to support, the protocol version that was used in the request message. The server
     2105      <h3 id="rfc.section.5.6.6"><a href="#rfc.section.5.6.6">5.6.6</a>&nbsp;<a id="status.505" href="#status.505">505 HTTP Version Not Supported</a></h3>
     2106      <p id="rfc.section.5.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
    21272107         is indicating that it is unable or unwilling to complete the request using the same major version as the client, as described
    21282108         in <a href="p1-messaging.html#http.version" title="Protocol Versioning">Section 2.6</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>, 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.
    … …  
    22702250         </li>
    22712251      </ul>
    2272       <h3 id="rfc.section.6.4.1"><a href="#rfc.section.6.4.1">6.4.1</a>&nbsp;<a id="content.coding.registry" href="#content.coding.registry">Content Coding Registry</a></h3>
    2273       <p id="rfc.section.6.4.1.p.1">The HTTP Content Coding Registry defines the name space for the content coding names.</p>
    2274       <p id="rfc.section.6.4.1.p.2">Registrations <em class="bcp14">MUST</em> include the following fields:
    2275       </p>
    2276       <ul>
    2277          <li>Name</li>
    2278          <li>Description</li>
    2279          <li>Pointer to specification text</li>
    2280       </ul>
    2281       <p id="rfc.section.6.4.1.p.3">Names of content codings <em class="bcp14">MUST NOT</em> overlap with names of transfer codings (<a href="p1-messaging.html#transfer.codings" title="Transfer Codings">Section 4</a> of <a href="#Part1" id="rfc.xref.Part1.29"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>), unless the encoding transformation is identical (as is the case for the compression codings defined in <a href="p1-messaging.html#compression.codings" title="Compression Codings">Section 4.2</a> of <a href="#Part1" id="rfc.xref.Part1.30"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>).
    2282       </p>
    2283       <p id="rfc.section.6.4.1.p.4">Values to be added to this name space require IETF Review (see <a href="http://tools.ietf.org/html/rfc5226#section-4.1">Section 4.1</a> of <a href="#RFC5226" id="rfc.xref.RFC5226.2"><cite title="Guidelines for Writing an IANA Considerations Section in RFCs">[RFC5226]</cite></a>), and <em class="bcp14">MUST</em> conform to the purpose of content coding defined in this section.
    2284       </p>
    2285       <p id="rfc.section.6.4.1.p.5">The registry itself is maintained at &lt;<a href="http://www.iana.org/assignments/http-parameters">http://www.iana.org/assignments/http-parameters</a>&gt;.
    2286       </p>
    22872252      <h2 id="rfc.section.6.5"><a href="#rfc.section.6.5">6.5</a>&nbsp;<a id="media.types" href="#media.types">Media Types</a></h2>
    22882253      <p id="rfc.section.6.5.p.1">HTTP uses Internet Media Types <a href="#RFC2046" id="rfc.xref.RFC2046.1"><cite title="Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types">[RFC2046]</cite></a> in the <a href="#header.content-type" class="smpl">Content-Type</a> (<a href="#header.content-type" id="rfc.xref.header.content-type.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.2" title="Accept">Section&nbsp;10.1</a>) header fields in order to provide open and extensible data typing and type negotiation.
    … …  
    23782343               <tr>
    23792344                  <td class="left">Content-Length</td>
    2380                   <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.31"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a></td>
     2345                  <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.29"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a></td>
    23812346               </tr>
    23822347               <tr>
    … …  
    23882353      </div>
    23892354      <h2 id="rfc.section.7.2"><a href="#rfc.section.7.2">7.2</a>&nbsp;<a id="payload.body" href="#payload.body">Payload Body</a></h2>
    2390       <p id="rfc.section.7.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.32"><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.
     2355      <p id="rfc.section.7.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.30"><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.
    23912356      </p>
    23922357      <div id="rfc.iref.r.1"></div>
    … …  
    24072372         in an HTTP message, it is referred to as the payload of the message.
    24082373      </p>
    2409       <p id="rfc.section.8.p.4">A representation 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.33"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>. The representation 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.
     2374      <p id="rfc.section.8.p.4">A representation 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.31"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>. The representation 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.
    24102375      </p>
    24112376      <h2 id="rfc.section.8.1"><a href="#rfc.section.8.1">8.1</a>&nbsp;<a id="identifying.response.associated.with.representation" href="#identifying.response.associated.with.representation">Identifying the Resource Associated with a Representation</a></h2>
    24122377      <p id="rfc.section.8.1.p.1">It is sometimes necessary to determine an identifier for the resource associated with a representation.</p>
    24132378      <p id="rfc.section.8.1.p.2">An HTTP request representation, when present, is always associated with an anonymous (i.e., unidentified) resource.</p>
    2414       <p id="rfc.section.8.1.p.3">In the common case, an HTTP response is a representation of the target resource (see <a href="p1-messaging.html#effective.request.uri" title="Effective Request URI">Section 5.5</a> of <a href="#Part1" id="rfc.xref.Part1.34"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>). However, this is not always the case. To determine the URI of the resource a response is associated with, the following
     2379      <p id="rfc.section.8.1.p.3">In the common case, an HTTP response is a representation of the target resource (see <a href="p1-messaging.html#effective.request.uri" title="Effective Request URI">Section 5.5</a> of <a href="#Part1" id="rfc.xref.Part1.32"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>). However, this is not always the case. To determine the URI of the resource a response is associated with, the following
    24152380         rules are used (with the first applicable one being selected):
    24162381      </p>
    … …  
    24652430               <tr>
    24662431                  <td class="left">Expires</td>
    2467                   <td class="left"><a href="p6-cache.html#header.expires" title="Expires">Section 7.3</a> of <a href="#Part6" id="rfc.xref.Part6.18"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a></td>
     2432                  <td class="left"><a href="p6-cache.html#header.expires" title="Expires">Section 7.3</a> of <a href="#Part6" id="rfc.xref.Part6.17"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a></td>
    24682433               </tr>
    24692434            </tbody>
    … …  
    25812546         </p>
    25822547      </div>
    2583       <p id="rfc.section.9.1.p.7">The <a href="p6-cache.html#header.vary" class="smpl">Vary</a> header field (<a href="p6-cache.html#header.vary" title="Vary">Section 7.5</a> of <a href="#Part6" id="rfc.xref.Part6.19"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>) can be used to express the parameters the server uses to select a representation that is subject to server-driven negotiation.
     2548      <p id="rfc.section.9.1.p.7">The <a href="p6-cache.html#header.vary" class="smpl">Vary</a> header field (<a href="p6-cache.html#header.vary" title="Vary">Section 7.5</a> of <a href="#Part6" id="rfc.xref.Part6.18"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>) can be used to express the parameters the server uses to select a representation that is subject to server-driven negotiation.
    25842549      </p>
    25852550      <h2 id="rfc.section.9.2"><a href="#rfc.section.9.2">9.2</a>&nbsp;<a id="agent-driven.negotiation" href="#agent-driven.negotiation">Agent-driven Negotiation</a></h2>
    … …  
    28872852      </p>
    28882853      <div id="rfc.figure.u.41"></div><pre class="inline"><span id="rfc.iref.g.45"></span>  <a href="#header.content-location" class="smpl">Content-Location</a> = <a href="#imported.abnf" class="smpl">absolute-URI</a> / <a href="#imported.abnf" class="smpl">partial-URI</a>
    2889 </pre><p id="rfc.section.10.8.p.3">The Content-Location value is not a replacement for the effective Request URI (<a href="p1-messaging.html#effective.request.uri" title="Effective Request URI">Section 5.5</a> of <a href="#Part1" id="rfc.xref.Part1.35"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>). It is representation metadata. It has the same syntax and semantics as the header field of the same name defined for MIME
     2854</pre><p id="rfc.section.10.8.p.3">The Content-Location value is not a replacement for the effective Request URI (<a href="p1-messaging.html#effective.request.uri" title="Effective Request URI">Section 5.5</a> of <a href="#Part1" id="rfc.xref.Part1.33"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>). It is representation metadata. It has the same syntax and semantics as the header field of the same name defined for MIME
    28902855         body parts in <a href="http://tools.ietf.org/html/rfc2557#section-4">Section 4</a> of <a href="#RFC2557" id="rfc.xref.RFC2557.1"><cite title="MIME Encapsulation of Aggregate Documents, such as HTML (MHTML)">[RFC2557]</cite></a>. However, its appearance in an HTTP message has some special implications for HTTP recipients.
    28912856      </p>
    … …  
    29812946      </p>
    29822947      <ul class="empty">
    2983          <li>The "100-continue" expectation is defined <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.36"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>. It does not support any expect-params.
     2948         <li>The "100-continue" expectation is defined <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.34"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>. It does not support any expect-params.
    29842949         </li>
    29852950      </ul>
    … …  
    30923057      <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>
    30933058      <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>
    3094       <p id="rfc.section.10.17.p.2">The field can contain multiple product tokens (<a href="#product.tokens" title="Product Tokens">Section&nbsp;6.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.37"><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
     3059      <p id="rfc.section.10.17.p.2">The field can contain multiple product tokens (<a href="#product.tokens" title="Product Tokens">Section&nbsp;6.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.35"><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
    30953060         identifying the application.
    30963061      </p>
    … …  
    30983063</pre><p id="rfc.section.10.17.p.4">Example:</p>
    30993064      <div id="rfc.figure.u.59"></div><pre class="text">  Server: CERN/3.0 libwww/2.17
    3100 </pre><p id="rfc.section.10.17.p.6">If the response is being forwarded through a proxy, the proxy application <em class="bcp14">MUST NOT</em> modify the <a href="#header.server" class="smpl">Server</a> header field. Instead, it <em class="bcp14">MUST</em> include a <a href="p1-messaging.html#header.via" class="smpl">Via</a> field (as described in <a href="p1-messaging.html#header.via" title="Via">Section 5.7</a> of <a href="#Part1" id="rfc.xref.Part1.38"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>).
     3065</pre><p id="rfc.section.10.17.p.6">If the response is being forwarded through a proxy, the proxy application <em class="bcp14">MUST NOT</em> modify the <a href="#header.server" class="smpl">Server</a> header field. Instead, it <em class="bcp14">MUST</em> include a <a href="p1-messaging.html#header.via" class="smpl">Via</a> field (as described in <a href="p1-messaging.html#header.via" title="Via">Section 5.7</a> of <a href="#Part1" id="rfc.xref.Part1.36"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>).
    31013066      </p>
    31023067      <div class="note" id="rfc.section.10.17.p.7">
    … …  
    31143079         user agent limitations.
    31153080      </p>
    3116       <p id="rfc.section.10.18.p.3">The field can contain multiple product tokens (<a href="#product.tokens" title="Product Tokens">Section&nbsp;6.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.39"><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
     3081      <p id="rfc.section.10.18.p.3">The field can contain multiple product tokens (<a href="#product.tokens" title="Product Tokens">Section&nbsp;6.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.37"><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
    31173082         for identifying the application.
    31183083      </p>
    … …  
    31313096      <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>
    31323097      <p id="rfc.section.11.1.p.1">The HTTP Method Registry defines the name space for the method token in the Request line of an HTTP request.</p>
    3133       <p id="rfc.section.11.1.p.2">Registrations <em class="bcp14">MUST</em> include the following fields:
     3098      <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>
     3099      <p id="rfc.section.11.1.1.p.1">Registrations <em class="bcp14">MUST</em> include the following fields:
    31343100      </p>
    31353101      <ul>
    … …  
    31423108         <li>Pointer to specification text</li>
    31433109      </ul>
    3144       <p id="rfc.section.11.1.p.3">Values to be added to this name space require IETF Review (see <a href="#RFC5226" id="rfc.xref.RFC5226.3"><cite title="Guidelines for Writing an IANA Considerations Section in RFCs">[RFC5226]</cite></a>, <a href="http://tools.ietf.org/html/rfc5226#section-4.1">Section 4.1</a>).
    3145       </p>
    3146       <p id="rfc.section.11.1.p.4">The registry itself is maintained at &lt;<a href="http://www.iana.org/assignments/http-methods">http://www.iana.org/assignments/http-methods</a>&gt;.
    3147       </p>
    3148       <h3 id="rfc.section.11.1.1"><a href="#rfc.section.11.1.1">11.1.1</a>&nbsp;<a id="considerations.for.new.methods" href="#considerations.for.new.methods">Considerations for New Methods</a></h3>
    3149       <p id="rfc.section.11.1.1.p.1">Standardized HTTP methods are generic; that is, they are potentially applicable to any resource, not just one particular media
     3110      <p id="rfc.section.11.1.1.p.2">Values to be added to this name space require IETF Review (see <a href="#RFC5226" id="rfc.xref.RFC5226.1"><cite title="Guidelines for Writing an IANA Considerations Section in RFCs">[RFC5226]</cite></a>, <a href="http://tools.ietf.org/html/rfc5226#section-4.1">Section 4.1</a>).
     3111      </p>
     3112      <p id="rfc.section.11.1.1.p.3">The registry itself is maintained at &lt;<a href="http://www.iana.org/assignments/http-methods">http://www.iana.org/assignments/http-methods</a>&gt;.
     3113      </p>
     3114      <h3 id="rfc.section.11.1.2"><a href="#rfc.section.11.1.2">11.1.2</a>&nbsp;<a id="considerations.for.new.methods" href="#considerations.for.new.methods">Considerations for New Methods</a></h3>
     3115      <p id="rfc.section.11.1.2.p.1">Standardized HTTP methods are generic; that is, they are potentially applicable to any resource, not just one particular media
    31503116         type, kind of resource, or application. As such, it is preferred that new HTTP methods be registered in a document that isn't
    31513117         specific to a single application or data format, since orthogonal technologies deserve orthogonal specification.
    31523118      </p>
    3153       <p id="rfc.section.11.1.1.p.2">Since HTTP message parsing (<a href="p1-messaging.html#message.body" title="Message Body">Section 3.3</a> of <a href="#Part1" id="rfc.xref.Part1.40"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>) is independent of method semantics (aside from responses to HEAD), definitions of new HTTP methods cannot change the parsing
     3119      <p id="rfc.section.11.1.2.p.2">Since HTTP message parsing (<a href="p1-messaging.html#message.body" title="Message Body">Section 3.3</a> of <a href="#Part1" id="rfc.xref.Part1.38"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>) is independent of method semantics (aside from responses to HEAD), definitions of new HTTP methods cannot change the parsing
    31543120         algorithm or prohibit the presence of a message body on either the request or the response message. Definitions of new methods
    31553121         can specify that only zero-length bodies are allowed, which would imply that each such messages would be required to contain
    31563122         a Content-Length header field with a value of "0".
    31573123      </p>
    3158       <p id="rfc.section.11.1.1.p.3">New method definitions need to indicate whether they are safe (<a href="#safe.methods" title="Safe Methods">Section&nbsp;3.2.1</a>), idempotent (<a href="#idempotent.methods" title="Idempotent Methods">Section&nbsp;3.2.2</a>), or cacheable (<a href="#cacheable.methods" title="Cacheable Methods">Section&nbsp;3.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,
     3124      <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;3.2.1</a>), idempotent (<a href="#idempotent.methods" title="Idempotent Methods">Section&nbsp;3.2.2</a>), or cacheable (<a href="#cacheable.methods" title="Cacheable Methods">Section&nbsp;3.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,
    31593125         the method definition ought to describe how, and under what conditions, a cache can store a response and use it to satisfy
    31603126         a subsequent request.
    31613127      </p>
    3162       <h3 id="rfc.section.11.1.2"><a href="#rfc.section.11.1.2">11.1.2</a>&nbsp;<a id="method.registration" href="#method.registration">Registrations</a></h3>
    3163       <p id="rfc.section.11.1.2.p.1">The HTTP Method Registry shall be created at &lt;<a href="http://www.iana.org/assignments/http-methods">http://www.iana.org/assignments/http-methods</a>&gt; and be populated with the registrations below:
     3128      <h3 id="rfc.section.11.1.3"><a href="#rfc.section.11.1.3">11.1.3</a>&nbsp;<a id="method.registration" href="#method.registration">Registrations</a></h3>
     3129      <p id="rfc.section.11.1.3.p.1">The HTTP Method Registry shall be created at &lt;<a href="http://www.iana.org/assignments/http-methods">http://www.iana.org/assignments/http-methods</a>&gt; and be populated with the registrations below:
    31643130      </p>
    31653131      <div id="rfc.table.2">
    … …  
    32343200         </table>
    32353201      </div>
    3236       <h2 id="rfc.section.11.2"><a href="#rfc.section.11.2">11.2</a>&nbsp;<a id="status.code.registration" href="#status.code.registration">Status Code Registry</a></h2>
    3237       <p id="rfc.section.11.2.p.1">The registration procedure for HTTP Status Codes — previously defined in <a href="http://tools.ietf.org/html/rfc2817#section-7.1">Section 7.1</a> of <a href="#RFC2817" id="rfc.xref.RFC2817.1"><cite title="Upgrading to TLS Within HTTP/1.1">[RFC2817]</cite></a> — is now defined by <a href="#status.code.registry" title="Status Code Registry">Section&nbsp;5.2</a> of this document.
    3238       </p>
    3239       <p id="rfc.section.11.2.p.2">The HTTP Status Code Registry located at &lt;<a href="http://www.iana.org/assignments/http-status-codes">http://www.iana.org/assignments/http-status-codes</a>&gt; shall be updated with the registrations below:
     3202      <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>
     3203      <p id="rfc.section.11.2.p.1">The HTTP Status Code Registry defines the name space for the status-code token in the status-line of an HTTP response (<a href="#status.codes" title="Response Status Codes">Section&nbsp;5</a>).
     3204      </p>
     3205      <h3 id="rfc.section.11.2.1"><a href="#rfc.section.11.2.1">11.2.1</a>&nbsp;<a id="status.code.procedure" href="#status.code.procedure">Procedure</a></h3>
     3206      <p id="rfc.section.11.2.1.p.1">Values to be added to this name space require IETF Review (see <a href="#RFC5226" id="rfc.xref.RFC5226.2"><cite title="Guidelines for Writing an IANA Considerations Section in RFCs">[RFC5226]</cite></a>, <a href="http://tools.ietf.org/html/rfc5226#section-4.1">Section 4.1</a>).
     3207      </p>
     3208      <p id="rfc.section.11.2.1.p.2">The registry itself is maintained at &lt;<a href="http://www.iana.org/assignments/http-status-codes">http://www.iana.org/assignments/http-status-codes</a>&gt;.
     3209      </p>
     3210      <h3 id="rfc.section.11.2.2"><a href="#rfc.section.11.2.2">11.2.2</a>&nbsp;<a id="considerations.for.new.status.codes" href="#considerations.for.new.status.codes">Considerations for New Status Codes</a></h3>
     3211      <p id="rfc.section.11.2.2.p.1">When it is necessary to express new semantics for a HTTP response that aren't specific to a single application or media type,
     3212         and currently defined status codes are inadequate, a new status code can be registered.
     3213      </p>
     3214      <p id="rfc.section.11.2.2.p.2">HTTP status codes are generic; that is, they are potentially applicable to any resource, not just one particular media type,
     3215         "type" of resource, or application. As such, it is preferred that new HTTP status codes be registered in a document that isn't
     3216         specific to a single application, so that this is clear.
     3217      </p>
     3218      <p id="rfc.section.11.2.2.p.3">Definitions of new HTTP status codes typically explain the request conditions that produce a response containing the status
     3219         code (e.g., combinations of request header fields and/or method(s)), along with any interactions with response header fields
     3220         (e.g., those that are required, those that modify the semantics of the response).
     3221      </p>
     3222      <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;5</a>. To allow existing parsers to properly handle them, new status codes cannot disallow a response body, although they can mandate
     3223         a zero-length response body. They can require the presence of one or more particular HTTP response header field(s).
     3224      </p>
     3225      <p id="rfc.section.11.2.2.p.5">Likewise, their definitions can specify that caches are allowed to use heuristics to determine their freshness (see <a href="#Part6" id="rfc.xref.Part6.19"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>; by default, it is not allowed), and can define how to determine the resource which they carry a representation for (see <a href="#identifying.response.associated.with.representation" title="Identifying the Resource Associated with a Representation">Section&nbsp;8.1</a>; by default, it is anonymous).
     3226      </p>
     3227      <h3 id="rfc.section.11.2.3"><a href="#rfc.section.11.2.3">11.2.3</a>&nbsp;<a id="status.code.registration" href="#status.code.registration">Registrations</a></h3>
     3228      <p id="rfc.section.11.2.3.p.1">The registration procedure for HTTP Status Codes — previously defined in <a href="http://tools.ietf.org/html/rfc2817#section-7.1">Section 7.1</a> of <a href="#RFC2817" id="rfc.xref.RFC2817.1"><cite title="Upgrading to TLS Within HTTP/1.1">[RFC2817]</cite></a> — is now defined by <a href="#status.code.registry" title="Status Code Registry">Section&nbsp;11.2</a> of this document.
     3229      </p>
     3230      <p id="rfc.section.11.2.3.p.2">The HTTP Status Code Registry located at &lt;<a href="http://www.iana.org/assignments/http-status-codes">http://www.iana.org/assignments/http-status-codes</a>&gt; shall be updated with the registrations below:
    32403231      </p>
    32413232      <div id="rfc.table.3">
    … …  
    32533244                  <td class="left">100</td>
    32543245                  <td class="left">Continue</td>
    3255                   <td class="left"> <a href="#status.100" id="rfc.xref.status.100.2" title="100 Continue">Section&nbsp;5.3.1</a>
     3246                  <td class="left"> <a href="#status.100" id="rfc.xref.status.100.2" title="100 Continue">Section&nbsp;5.2.1</a>
    32563247                  </td>
    32573248               </tr>
    … …  
    32593250                  <td class="left">101</td>
    32603251                  <td class="left">Switching Protocols</td>
    3261                   <td class="left"> <a href="#status.101" id="rfc.xref.status.101.2" title="101 Switching Protocols">Section&nbsp;5.3.2</a>
     3252                  <td class="left"> <a href="#status.101" id="rfc.xref.status.101.2" title="101 Switching Protocols">Section&nbsp;5.2.2</a>
    32623253                  </td>
    32633254               </tr>
    … …  
    32653256                  <td class="left">200</td>
    32663257                  <td class="left">OK</td>
    3267                   <td class="left"> <a href="#status.200" id="rfc.xref.status.200.2" title="200 OK">Section&nbsp;5.4.1</a>
     3258                  <td class="left"> <a href="#status.200" id="rfc.xref.status.200.2" title="200 OK">Section&nbsp;5.3.1</a>
    32683259                  </td>
    32693260               </tr>
    … …  
    32713262                  <td class="left">201</td>
    32723263                  <td class="left">Created</td>
    3273                   <td class="left"> <a href="#status.201" id="rfc.xref.status.201.2" title="201 Created">Section&nbsp;5.4.2</a>
     3264                  <td class="left"> <a href="#status.201" id="rfc.xref.status.201.2" title="201 Created">Section&nbsp;5.3.2</a>
    32743265                  </td>
    32753266               </tr>
    … …  
    32773268                  <td class="left">202</td>
    32783269                  <td class="left">Accepted</td>
    3279                   <td class="left"> <a href="#status.202" id="rfc.xref.status.202.2" title="202 Accepted">Section&nbsp;5.4.3</a>
     3270                  <td class="left"> <a href="#status.202" id="rfc.xref.status.202.2" title="202 Accepted">Section&nbsp;5.3.3</a>
    32803271                  </td>
    32813272               </tr>
    … …  
    32833274                  <td class="left">203</td>
    32843275                  <td class="left">Non-Authoritative Information</td>
    3285                   <td class="left"> <a href="#status.203" id="rfc.xref.status.203.2" title="203 Non-Authoritative Information">Section&nbsp;5.4.4</a>
     3276                  <td class="left"> <a href="#status.203" id="rfc.xref.status.203.2" title="203 Non-Authoritative Information">Section&nbsp;5.3.4</a>
    32863277                  </td>
    32873278               </tr>
    … …  
    32893280                  <td class="left">204</td>
    32903281                  <td class="left">No Content</td>
    3291                   <td class="left"> <a href="#status.204" id="rfc.xref.status.204.2" title="204 No Content">Section&nbsp;5.4.5</a>
     3282                  <td class="left"> <a href="#status.204" id="rfc.xref.status.204.2" title="204 No Content">Section&nbsp;5.3.5</a>
    32923283                  </td>
    32933284               </tr>
    … …  
    32953286                  <td class="left">205</td>
    32963287                  <td class="left">Reset Content</td>
    3297                   <td class="left"> <a href="#status.205" id="rfc.xref.status.205.2" title="205 Reset Content">Section&nbsp;5.4.6</a>
     3288                  <td class="left"> <a href="#status.205" id="rfc.xref.status.205.2" title="205 Reset Content">Section&nbsp;5.3.6</a>
    32983289                  </td>
    32993290               </tr>
    … …  
    33013292                  <td class="left">300</td>
    33023293                  <td class="left">Multiple Choices</td>
    3303                   <td class="left"> <a href="#status.300" id="rfc.xref.status.300.2" title="300 Multiple Choices">Section&nbsp;5.5.1</a>
     3294                  <td class="left"> <a href="#status.300" id="rfc.xref.status.300.2" title="300 Multiple Choices">Section&nbsp;5.4.1</a>
    33043295                  </td>
    33053296               </tr>
    … …  
    33073298                  <td class="left">301</td>
    33083299                  <td class="left">Moved Permanently</td>
    3309                   <td class="left"> <a href="#status.301" id="rfc.xref.status.301.2" title="301 Moved Permanently">Section&nbsp;5.5.2</a>
     3300                  <td class="left"> <a href="#status.301" id="rfc.xref.status.301.2" title="301 Moved Permanently">Section&nbsp;5.4.2</a>
    33103301                  </td>
    33113302               </tr>
    … …  
    33133304                  <td class="left">302</td>
    33143305                  <td class="left">Found</td>
    3315                   <td class="left"> <a href="#status.302" id="rfc.xref.status.302.2" title="302 Found">Section&nbsp;5.5.3</a>
     3306                  <td class="left"> <a href="#status.302" id="rfc.xref.status.302.2" title="302 Found">Section&nbsp;5.4.3</a>
    33163307                  </td>
    33173308               </tr>
    … …  
    33193310                  <td class="left">303</td>
    33203311                  <td class="left">See Other</td>
    3321                   <td class="left"> <a href="#status.303" id="rfc.xref.status.303.2" title="303 See Other">Section&nbsp;5.5.4</a>
     3312                  <td class="left"> <a href="#status.303" id="rfc.xref.status.303.2" title="303 See Other">Section&nbsp;5.4.4</a>
    33223313                  </td>
    33233314               </tr>
    … …  
    33253316                  <td class="left">305</td>
    33263317                  <td class="left">Use Proxy</td>
    3327                   <td class="left"> <a href="#status.305" id="rfc.xref.status.305.2" title="305 Use Proxy">Section&nbsp;5.5.5</a>
     3318                  <td class="left"> <a href="#status.305" id="rfc.xref.status.305.2" title="305 Use Proxy">Section&nbsp;5.4.5</a>
    33283319                  </td>
    33293320               </tr>
    … …  
    33313322                  <td class="left">306</td>
    33323323                  <td class="left">(Unused)</td>
    3333                   <td class="left"> <a href="#status.306" id="rfc.xref.status.306.1" title="306 (Unused)">Section&nbsp;5.5.6</a>
     3324                  <td class="left"> <a href="#status.306" id="rfc.xref.status.306.1" title="306 (Unused)">Section&nbsp;5.4.6</a>
    33343325                  </td>
    33353326               </tr>
    … …  
    33373328                  <td class="left">307</td>
    33383329                  <td class="left">Temporary Redirect</td>
    3339                   <td class="left"> <a href="#status.307" id="rfc.xref.status.307.2" title="307 Temporary Redirect">Section&nbsp;5.5.7</a>
     3330                  <td class="left"> <a href="#status.307" id="rfc.xref.status.307.2" title="307 Temporary Redirect">Section&nbsp;5.4.7</a>
    33403331                  </td>
    33413332               </tr>
    … …  
    33433334                  <td class="left">400</td>
    33443335                  <td class="left">Bad Request</td>
    3345                   <td class="left"> <a href="#status.400" id="rfc.xref.status.400.2" title="400 Bad Request">Section&nbsp;5.6.1</a>
     3336                  <td class="left"> <a href="#status.400" id="rfc.xref.status.400.2" title="400 Bad Request">Section&nbsp;5.5.1</a>
    33463337                  </td>
    33473338               </tr>
    … …  
    33493340                  <td class="left">402</td>
    33503341                  <td class="left">Payment Required</td>
    3351                   <td class="left"> <a href="#status.402" id="rfc.xref.status.402.2" title="402 Payment Required">Section&nbsp;5.6.2</a>
     3342                  <td class="left"> <a href="#status.402" id="rfc.xref.status.402.2" title="402 Payment Required">Section&nbsp;5.5.2</a>
    33523343                  </td>
    33533344               </tr>
    … …  
    33553346                  <td class="left">403</td>
    33563347                  <td class="left">Forbidden</td>
    3357                   <td class="left"> <a href="#status.403" id="rfc.xref.status.403.2" title="403 Forbidden">Section&nbsp;5.6.3</a>
     3348                  <td class="left"> <a href="#status.403" id="rfc.xref.status.403.2" title="403 Forbidden">Section&nbsp;5.5.3</a>
    33583349                  </td>
    33593350               </tr>
    … …  
    33613352                  <td class="left">404</td>
    33623353                  <td class="left">Not Found</td>
    3363                   <td class="left"> <a href="#status.404" id="rfc.xref.status.404.2" title="404 Not Found">Section&nbsp;5.6.4</a>
     3354                  <td class="left"> <a href="#status.404" id="rfc.xref.status.404.2" title="404 Not Found">Section&nbsp;5.5.4</a>
    33643355                  </td>
    33653356               </tr>
    … …  
    33673358                  <td class="left">405</td>
    33683359                  <td class="left">Method Not Allowed</td>
    3369                   <td class="left"> <a href="#status.405" id="rfc.xref.status.405.2" title="405 Method Not Allowed">Section&nbsp;5.6.5</a>
     3360                  <td class="left"> <a href="#status.405" id="rfc.xref.status.405.2" title="405 Method Not Allowed">Section&nbsp;5.5.5</a>
    33703361                  </td>
    33713362               </tr>
    … …  
    33733364                  <td class="left">406</td>
    33743365                  <td class="left">Not Acceptable</td>
    3375                   <td class="left"> <a href="#status.406" id="rfc.xref.status.406.2" title="406 Not Acceptable">Section&nbsp;5.6.6</a>
     3366                  <td class="left"> <a href="#status.406" id="rfc.xref.status.406.2" title="406 Not Acceptable">Section&nbsp;5.5.6</a>
    33763367                  </td>
    33773368               </tr>
    … …  
    33793370                  <td class="left">408</td>
    33803371                  <td class="left">Request Timeout</td>
    3381                   <td class="left"> <a href="#status.408" id="rfc.xref.status.408.2" title="408 Request Timeout">Section&nbsp;5.6.7</a>
     3372                  <td class="left"> <a href="#status.408" id="rfc.xref.status.408.2" title="408 Request Timeout">Section&nbsp;5.5.7</a>
    33823373                  </td>
    33833374               </tr>
    … …  
    33853376                  <td class="left">409</td>
    33863377                  <td class="left">Conflict</td>
    3387                   <td class="left"> <a href="#status.409" id="rfc.xref.status.409.2" title="409 Conflict">Section&nbsp;5.6.8</a>
     3378                  <td class="left"> <a href="#status.409" id="rfc.xref.status.409.2" title="409 Conflict">Section&nbsp;5.5.8</a>
    33883379                  </td>
    33893380               </tr>
    … …  
    33913382                  <td class="left">410</td>
    33923383                  <td class="left">Gone</td>
    3393                   <td class="left"> <a href="#status.410" id="rfc.xref.status.410.2" title="410 Gone">Section&nbsp;5.6.9</a>
     3384                  <td class="left"> <a href="#status.410" id="rfc.xref.status.410.2" title="410 Gone">Section&nbsp;5.5.9</a>
    33943385                  </td>
    33953386               </tr>
    … …  
    33973388                  <td class="left">411</td>
    33983389                  <td class="left">Length Required</td>
    3399                   <td class="left"> <a href="#status.411" id="rfc.xref.status.411.2" title="411 Length Required">Section&nbsp;5.6.10</a>
     3390                  <td class="left"> <a href="#status.411" id="rfc.xref.status.411.2" title="411 Length Required">Section&nbsp;5.5.10</a>
    34003391                  </td>
    34013392               </tr>
    … …  
    34033394                  <td class="left">413</td>
    34043395                  <td class="left">Request Representation Too Large</td>
    3405                   <td class="left"> <a href="#status.413" id="rfc.xref.status.413.2" title="413 Request Representation Too Large">Section&nbsp;5.6.11</a>
     3396                  <td class="left"> <a href="#status.413" id="rfc.xref.status.413.2" title="413 Request Representation Too Large">Section&nbsp;5.5.11</a>
    34063397                  </td>
    34073398               </tr>
    … …  
    34093400                  <td class="left">414</td>
    34103401                  <td class="left">URI Too Long</td>
    3411                   <td class="left"> <a href="#status.414" id="rfc.xref.status.414.2" title="414 URI Too Long">Section&nbsp;5.6.12</a>
     3402                  <td class="left"> <a href="#status.414" id="rfc.xref.status.414.2" title="414 URI Too Long">Section&nbsp;5.5.12</a>
    34123403                  </td>
    34133404               </tr>
    … …  
    34153406                  <td class="left">415</td>
    34163407                  <td class="left">Unsupported Media Type</td>
    3417                   <td class="left"> <a href="#status.415" id="rfc.xref.status.415.2" title="415 Unsupported Media Type">Section&nbsp;5.6.13</a>
     3408                  <td class="left"> <a href="#status.415" id="rfc.xref.status.415.2" title="415 Unsupported Media Type">Section&nbsp;5.5.13</a>
    34183409                  </td>
    34193410               </tr>
    … …  
    34213412                  <td class="left">417</td>
    34223413                  <td class="left">Expectation Failed</td>
    3423                   <td class="left"> <a href="#status.417" id="rfc.xref.status.417.2" title="417 Expectation Failed">Section&nbsp;5.6.14</a>
     3414                  <td class="left"> <a href="#status.417" id="rfc.xref.status.417.2" title="417 Expectation Failed">Section&nbsp;5.5.14</a>
    34243415                  </td>
    34253416               </tr>
    … …  
    34273418                  <td class="left">426</td>
    34283419                  <td class="left">Upgrade Required</td>
    3429                   <td class="left"> <a href="#status.426" id="rfc.xref.status.426.2" title="426 Upgrade Required">Section&nbsp;5.6.15</a>
     3420                  <td class="left"> <a href="#status.426" id="rfc.xref.status.426.2" title="426 Upgrade Required">Section&nbsp;5.5.15</a>
    34303421                  </td>
    34313422               </tr>
    … …  
    34333424                  <td class="left">500</td>
    34343425                  <td class="left">Internal Server Error</td>
    3435                   <td class="left"> <a href="#status.500" id="rfc.xref.status.500.2" title="500 Internal Server Error">Section&nbsp;5.7.1</a>
     3426                  <td class="left"> <a href="#status.500" id="rfc.xref.status.500.2" title="500 Internal Server Error">Section&nbsp;5.6.1</a>
    34363427                  </td>
    34373428               </tr>
    … …  
    34393430                  <td class="left">501</td>
    34403431                  <td class="left">Not Implemented</td>
    3441                   <td class="left"> <a href="#status.501" id="rfc.xref.status.501.2" title="501 Not Implemented">Section&nbsp;5.7.2</a>
     3432                  <td class="left"> <a href="#status.501" id="rfc.xref.status.501.2" title="501 Not Implemented">Section&nbsp;5.6.2</a>
    34423433                  </td>
    34433434               </tr>
    … …  
    34453436                  <td class="left">502</td>
    34463437                  <td class="left">Bad Gateway</td>
    3447                   <td class="left"> <a href="#status.502" id="rfc.xref.status.502.2" title="502 Bad Gateway">Section&nbsp;5.7.3</a>
     3438                  <td class="left"> <a href="#status.502" id="rfc.xref.status.502.2" title="502 Bad Gateway">Section&nbsp;5.6.3</a>
    34483439                  </td>
    34493440               </tr>
    … …  
    34513442                  <td class="left">503</td>
    34523443                  <td class="left">Service Unavailable</td>
    3453                   <td class="left"> <a href="#status.503" id="rfc.xref.status.503.2" title="503 Service Unavailable">Section&nbsp;5.7.4</a>
     3444                  <td class="left"> <a href="#status.503" id="rfc.xref.status.503.2" title="503 Service Unavailable">Section&nbsp;5.6.4</a>
    34543445                  </td>
    34553446               </tr>
    … …  
    34573448                  <td class="left">504</td>
    34583449                  <td class="left">Gateway Timeout</td>
    3459                   <td class="left"> <a href="#status.504" id="rfc.xref.status.504.2" title="504 Gateway Timeout">Section&nbsp;5.7.5</a>
     3450                  <td class="left"> <a href="#status.504" id="rfc.xref.status.504.2" title="504 Gateway Timeout">Section&nbsp;5.6.5</a>
    34603451                  </td>
    34613452               </tr>
    … …  
    34633454                  <td class="left">505</td>
    34643455                  <td class="left">HTTP Version Not Supported</td>
    3465                   <td class="left"> <a href="#status.505" id="rfc.xref.status.505.2" title="505 HTTP Version Not Supported">Section&nbsp;5.7.6</a>
     3456                  <td class="left"> <a href="#status.505" id="rfc.xref.status.505.2" title="505 HTTP Version Not Supported">Section&nbsp;5.6.6</a>
    34663457                  </td>
    34673458               </tr>
    … …  
    36213612      </div>
    36223613      <p id="rfc.section.11.3.p.2">The change controller is: "IETF (iesg@ietf.org) - Internet Engineering Task Force".</p>
    3623       <h2 id="rfc.section.11.4"><a href="#rfc.section.11.4">11.4</a>&nbsp;<a id="content.coding.registration" href="#content.coding.registration">Content Coding Registry</a></h2>
    3624       <p id="rfc.section.11.4.p.1">The registration procedure for HTTP Content Codings is now defined by <a href="#content.coding.registry" title="Content Coding Registry">Section&nbsp;6.4.1</a> of this document.
    3625       </p>
    3626       <p id="rfc.section.11.4.p.2">The HTTP Content Codings Registry located at &lt;<a href="http://www.iana.org/assignments/http-parameters">http://www.iana.org/assignments/http-parameters</a>&gt; shall be updated with the registration below:
     3614      <h2 id="rfc.section.11.4"><a href="#rfc.section.11.4">11.4</a>&nbsp;<a id="content.coding.registry" href="#content.coding.registry">Content Coding Registry</a></h2>
     3615      <p id="rfc.section.11.4.p.1">The HTTP Content Coding Registry defines the name space for the content coding names.</p>
     3616      <h3 id="rfc.section.11.4.1"><a href="#rfc.section.11.4.1">11.4.1</a>&nbsp;<a id="content.coding.procedure" href="#content.coding.procedure">Procedure</a></h3>
     3617      <p id="rfc.section.11.4.1.p.1">Registrations <em class="bcp14">MUST</em> include the following fields:
     3618      </p>
     3619      <ul>
     3620         <li>Name</li>
     3621         <li>Description</li>
     3622         <li>Pointer to specification text</li>
     3623      </ul>
     3624      <p id="rfc.section.11.4.1.p.2">Names of content codings <em class="bcp14">MUST NOT</em> overlap with names of transfer codings (<a href="p1-messaging.html#transfer.codings" title="Transfer Codings">Section 4</a> of <a href="#Part1" id="rfc.xref.Part1.39"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>), unless the encoding transformation is identical (as is the case for the compression codings defined in <a href="p1-messaging.html#compression.codings" title="Compression Codings">Section 4.2</a> of <a href="#Part1" id="rfc.xref.Part1.40"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>).
     3625      </p>
     3626      <p id="rfc.section.11.4.1.p.3">Values to be added to this name space require IETF Review (see <a href="http://tools.ietf.org/html/rfc5226#section-4.1">Section 4.1</a> of <a href="#RFC5226" id="rfc.xref.RFC5226.3"><cite title="Guidelines for Writing an IANA Considerations Section in RFCs">[RFC5226]</cite></a>), and <em class="bcp14">MUST</em> conform to the purpose of content coding defined in this section.
     3627      </p>
     3628      <p id="rfc.section.11.4.1.p.4">The registry itself is maintained at &lt;<a href="http://www.iana.org/assignments/http-parameters">http://www.iana.org/assignments/http-parameters</a>&gt;.
     3629      </p>
     3630      <h3 id="rfc.section.11.4.2"><a href="#rfc.section.11.4.2">11.4.2</a>&nbsp;<a id="content.coding.registration" href="#content.coding.registration">Registrations</a></h3>
     3631      <p id="rfc.section.11.4.2.p.1">The registration procedure for HTTP Content Codings is now defined by <a href="#content.coding.registry" title="Content Coding Registry">Section&nbsp;11.4</a> of this document.
     3632      </p>
     3633      <p id="rfc.section.11.4.2.p.2">The HTTP Content Codings Registry located at &lt;<a href="http://www.iana.org/assignments/http-parameters">http://www.iana.org/assignments/http-parameters</a>&gt; shall be updated with the registration below:
    36273634      </p>
    36283635      <div id="rfc.table.5">
    … …  
    40274034      <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;3.3.8</a>)
    40284035      </p>
    4029       <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;5.2</a>)
    4030       </p>
    4031       <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;5.4.4</a>)
    4032       </p>
    4033       <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;5.5</a>)
     4036      <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>)
     4037      </p>
     4038      <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;5.3.4</a>)
     4039      </p>
     4040      <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;5.4</a>)
    40344041      </p>
    40354042      <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
    40364043         user agent is able to make that determination based on the request method semantics. Furthermore, allow user agents to rewrite
    4037          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">5.5.2</a>, <a href="#status.302" id="rfc.xref.status.302.3" title="302 Found">5.5.3</a> and <a href="#status.307" id="rfc.xref.status.307.3" title="307 Temporary Redirect">5.5.7</a>)
     4044         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">5.4.2</a>, <a href="#status.302" id="rfc.xref.status.302.3" title="302 Found">5.4.3</a> and <a href="#status.307" id="rfc.xref.status.307.3" title="307 Temporary Redirect">5.4.7</a>)
    40384045      </p>
    40394046      <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
    40404047         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.
    4041          (<a href="#status.305" id="rfc.xref.status.305.3" title="305 Use Proxy">Section&nbsp;5.5.5</a>)
    4042       </p>
    4043       <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;5.6.15</a>)
     4048         (<a href="#status.305" id="rfc.xref.status.305.3" title="305 Use Proxy">Section&nbsp;5.4.5</a>)
     4049      </p>
     4050      <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;5.5.15</a>)
    40444051      </p>
    40454052      <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>)
    … …  
    40624069      <p id="rfc.section.C.p.18">Clarify contexts that charset is used in. (<a href="#character.sets" title="Character Encodings (charset)">Section&nbsp;6.3</a>)
    40634070      </p>
    4064       <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;6.4.1</a>)
     4071      <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>)
    40654072      </p>
    40664073      <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
    … …  
    48044811         <ul class="ind">
    48054812            <li><a id="rfc.index.1" href="#rfc.index.1"><b>1</b></a><ul>
    4806                   <li>100 Continue (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.100.1">5.1</a>, <a href="#rfc.iref.22"><b>5.3.1</b></a>, <a href="#rfc.xref.status.100.2">11.2</a></li>
     4813                  <li>100 Continue (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.100.1">5.1</a>, <a href="#rfc.iref.22"><b>5.2.1</b></a>, <a href="#rfc.xref.status.100.2">11.2.3</a></li>
    48074814                  <li>100-continue (expect value)&nbsp;&nbsp;<a href="#rfc.iref.142"><b>10.11</b></a></li>
    4808                   <li>101 Switching Protocols (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.101.1">5.1</a>, <a href="#rfc.iref.23"><b>5.3.2</b></a>, <a href="#rfc.xref.status.101.2">11.2</a></li>
    4809                   <li>1xx Informational (status code class)&nbsp;&nbsp;<a href="#rfc.iref.21"><b>5.3</b></a></li>
     4815                  <li>101 Switching Protocols (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.101.1">5.1</a>, <a href="#rfc.iref.23"><b>5.2.2</b></a>, <a href="#rfc.xref.status.101.2">11.2.3</a></li>
     4816                  <li>1xx Informational (status code class)&nbsp;&nbsp;<a href="#rfc.iref.21"><b>5.2</b></a></li>
    48104817               </ul>
    48114818            </li>
    48124819            <li><a id="rfc.index.2" href="#rfc.index.2"><b>2</b></a><ul>
    4813                   <li>200 OK (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.200.1">5.1</a>, <a href="#rfc.iref.25"><b>5.4.1</b></a>, <a href="#rfc.xref.status.200.2">11.2</a></li>
    4814                   <li>201 Created (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.201.1">5.1</a>, <a href="#rfc.iref.26"><b>5.4.2</b></a>, <a href="#rfc.xref.status.201.2">11.2</a></li>
    4815                   <li>202 Accepted (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.202.1">5.1</a>, <a href="#rfc.iref.27"><b>5.4.3</b></a>, <a href="#rfc.xref.status.202.2">11.2</a></li>
    4816                   <li>203 Non-Authoritative Information (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.203.1">5.1</a>, <a href="#rfc.iref.28"><b>5.4.4</b></a>, <a href="#rfc.xref.status.203.2">11.2</a>, <a href="#rfc.xref.status.203.3">C</a></li>
    4817                   <li>204 No Content (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.204.1">5.1</a>, <a href="#rfc.iref.29"><b>5.4.5</b></a>, <a href="#rfc.xref.status.204.2">11.2</a></li>
    4818                   <li>205 Reset Content (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.205.1">5.1</a>, <a href="#rfc.iref.30"><b>5.4.6</b></a>, <a href="#rfc.xref.status.205.2">11.2</a></li>
    4819                   <li>2xx Successful (status code class)&nbsp;&nbsp;<a href="#rfc.iref.24"><b>5.4</b></a></li>
     4820                  <li>200 OK (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.200.1">5.1</a>, <a href="#rfc.iref.25"><b>5.3.1</b></a>, <a href="#rfc.xref.status.200.2">11.2.3</a></li>
     4821                  <li>201 Created (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.201.1">5.1</a>, <a href="#rfc.iref.26"><b>5.3.2</b></a>, <a href="#rfc.xref.status.201.2">11.2.3</a></li>
     4822                  <li>202 Accepted (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.202.1">5.1</a>, <a href="#rfc.iref.27"><b>5.3.3</b></a>, <a href="#rfc.xref.status.202.2">11.2.3</a></li>
     4823                  <li>203 Non-Authoritative Information (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.203.1">5.1</a>, <a href="#rfc.iref.28"><b>5.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>
     4824                  <li>204 No Content (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.204.1">5.1</a>, <a href="#rfc.iref.29"><b>5.3.5</b></a>, <a href="#rfc.xref.status.204.2">11.2.3</a></li>
     4825                  <li>205 Reset Content (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.205.1">5.1</a>, <a href="#rfc.iref.30"><b>5.3.6</b></a>, <a href="#rfc.xref.status.205.2">11.2.3</a></li>
     4826                  <li>2xx Successful (status code class)&nbsp;&nbsp;<a href="#rfc.iref.24"><b>5.3</b></a></li>
    48204827               </ul>
    48214828            </li>
    48224829            <li><a id="rfc.index.3" href="#rfc.index.3"><b>3</b></a><ul>
    4823                   <li>300 Multiple Choices (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.300.1">5.1</a>, <a href="#rfc.iref.32"><b>5.5.1</b></a>, <a href="#rfc.xref.status.300.2">11.2</a></li>
    4824                   <li>301 Moved Permanently (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.301.1">5.1</a>, <a href="#rfc.iref.33"><b>5.5.2</b></a>, <a href="#rfc.xref.status.301.2">11.2</a>, <a href="#rfc.xref.status.301.3">C</a></li>
    4825                   <li>302 Found (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.302.1">5.1</a>, <a href="#rfc.iref.34"><b>5.5.3</b></a>, <a href="#rfc.xref.status.302.2">11.2</a>, <a href="#rfc.xref.status.302.3">C</a></li>
    4826                   <li>303 See Other (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.303.1">5.1</a>, <a href="#rfc.iref.35"><b>5.5.4</b></a>, <a href="#rfc.xref.status.303.2">11.2</a></li>
    4827                   <li>305 Use Proxy (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.305.1">5.1</a>, <a href="#rfc.iref.36"><b>5.5.5</b></a>, <a href="#rfc.xref.status.305.2">11.2</a>, <a href="#rfc.xref.status.305.3">C</a></li>
    4828                   <li>306 (Unused) (status code)&nbsp;&nbsp;<a href="#rfc.iref.37"><b>5.5.6</b></a>, <a href="#rfc.xref.status.306.1">11.2</a></li>
    4829                   <li>307 Temporary Redirect (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.307.1">5.1</a>, <a href="#rfc.iref.38"><b>5.5.7</b></a>, <a href="#rfc.xref.status.307.2">11.2</a>, <a href="#rfc.xref.status.307.3">C</a></li>
    4830                   <li>3xx Redirection (status code class)&nbsp;&nbsp;<a href="#rfc.iref.31"><b>5.5</b></a>, <a href="#rfc.xref.status.3xx.1">C</a></li>
     4830                  <li>300 Multiple Choices (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.300.1">5.1</a>, <a href="#rfc.iref.32"><b>5.4.1</b></a>, <a href="#rfc.xref.status.300.2">11.2.3</a></li>
     4831                  <li>301 Moved Permanently (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.301.1">5.1</a>, <a href="#rfc.iref.33"><b>5.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>
     4832                  <li>302 Found (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.302.1">5.1</a>, <a href="#rfc.iref.34"><b>5.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>
     4833                  <li>303 See Other (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.303.1">5.1</a>, <a href="#rfc.iref.35"><b>5.4.4</b></a>, <a href="#rfc.xref.status.303.2">11.2.3</a></li>
     4834                  <li>305 Use Proxy (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.305.1">5.1</a>, <a href="#rfc.iref.36"><b>5.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>
     4835                  <li>306 (Unused) (status code)&nbsp;&nbsp;<a href="#rfc.iref.37"><b>5.4.6</b></a>, <a href="#rfc.xref.status.306.1">11.2.3</a></li>
     4836                  <li>307 Temporary Redirect (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.307.1">5.1</a>, <a href="#rfc.iref.38"><b>5.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>
     4837                  <li>3xx Redirection (status code class)&nbsp;&nbsp;<a href="#rfc.iref.31"><b>5.4</b></a>, <a href="#rfc.xref.status.3xx.1">C</a></li>
    48314838               </ul>
    48324839            </li>
    48334840            <li><a id="rfc.index.4" href="#rfc.index.4"><b>4</b></a><ul>
    4834                   <li>400 Bad Request (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.400.1">5.1</a>, <a href="#rfc.iref.40"><b>5.6.1</b></a>, <a href="#rfc.xref.status.400.2">11.2</a></li>
    4835                   <li>402 Payment Required (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.402.1">5.1</a>, <a href="#rfc.iref.41"><b>5.6.2</b></a>, <a href="#rfc.xref.status.402.2">11.2</a></li>
    4836                   <li>403 Forbidden (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.403.1">5.1</a>, <a href="#rfc.iref.42"><b>5.6.3</b></a>, <a href="#rfc.xref.status.403.2">11.2</a></li>
    4837                   <li>404 Not Found (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.404.1">5.1</a>, <a href="#rfc.iref.43"><b>5.6.4</b></a>, <a href="#rfc.xref.status.404.2">11.2</a></li>
    4838                   <li>405 Method Not Allowed (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.405.1">5.1</a>, <a href="#rfc.iref.44"><b>5.6.5</b></a>, <a href="#rfc.xref.status.405.2">11.2</a></li>
    4839                   <li>406 Not Acceptable (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.406.1">5.1</a>, <a href="#rfc.iref.45"><b>5.6.6</b></a>, <a href="#rfc.xref.status.406.2">11.2</a></li>
    4840                   <li>408 Request Timeout (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.408.1">5.1</a>, <a href="#rfc.iref.46"><b>5.6.7</b></a>, <a href="#rfc.xref.status.408.2">11.2</a></li>
    4841                   <li>409 Conflict (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.409.1">5.1</a>, <a href="#rfc.iref.47"><b>5.6.8</b></a>, <a href="#rfc.xref.status.409.2">11.2</a></li>
    4842                   <li>410 Gone (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.410.1">5.1</a>, <a href="#rfc.iref.48"><b>5.6.9</b></a>, <a href="#rfc.xref.status.410.2">11.2</a></li>
    4843                   <li>411 Length Required (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.411.1">5.1</a>, <a href="#rfc.iref.49"><b>5.6.10</b></a>, <a href="#rfc.xref.status.411.2">11.2</a></li>
    4844                   <li>413 Request Representation Too Large (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.413.1">5.1</a>, <a href="#rfc.iref.50"><b>5.6.11</b></a>, <a href="#rfc.xref.status.413.2">11.2</a></li>
    4845                   <li>414 URI Too Long (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.414.1">5.1</a>, <a href="#rfc.iref.51"><b>5.6.12</b></a>, <a href="#rfc.xref.status.414.2">11.2</a></li>
    4846                   <li>415 Unsupported Media Type (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.415.1">5.1</a>, <a href="#rfc.iref.52"><b>5.6.13</b></a>, <a href="#rfc.xref.status.415.2">11.2</a></li>
    4847                   <li>417 Expectation Failed (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.417.1">5.1</a>, <a href="#rfc.iref.53"><b>5.6.14</b></a>, <a href="#rfc.xref.status.417.2">11.2</a></li>
    4848                   <li>426 Upgrade Required (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.426.1">5.1</a>, <a href="#rfc.iref.54"><b>5.6.15</b></a>, <a href="#rfc.xref.status.426.2">11.2</a>, <a href="#rfc.xref.status.426.3">C</a></li>
    4849                   <li>4xx Client Error (status code class)&nbsp;&nbsp;<a href="#rfc.iref.39"><b>5.6</b></a></li>
     4841                  <li>400 Bad Request (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.400.1">5.1</a>, <a href="#rfc.iref.40"><b>5.5.1</b></a>, <a href="#rfc.xref.status.400.2">11.2.3</a></li>
     4842                  <li>402 Payment Required (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.402.1">5.1</a>, <a href="#rfc.iref.41"><b>5.5.2</b></a>, <a href="#rfc.xref.status.402.2">11.2.3</a></li>
     4843                  <li>403 Forbidden (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.403.1">5.1</a>, <a href="#rfc.iref.42"><b>5.5.3</b></a>, <a href="#rfc.xref.status.403.2">11.2.3</a></li>
     4844                  <li>404 Not Found (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.404.1">5.1</a>, <a href="#rfc.iref.43"><b>5.5.4</b></a>, <a href="#rfc.xref.status.404.2">11.2.3</a></li>
     4845                  <li>405 Method Not Allowed (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.405.1">5.1</a>, <a href="#rfc.iref.44"><b>5.5.5</b></a>, <a href="#rfc.xref.status.405.2">11.2.3</a></li>
     4846                  <li>406 Not Acceptable (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.406.1">5.1</a>, <a href="#rfc.iref.45"><b>5.5.6</b></a>, <a href="#rfc.xref.status.406.2">11.2.3</a></li>
     4847                  <li>408 Request Timeout (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.408.1">5.1</a>, <a href="#rfc.iref.46"><b>5.5.7</b></a>, <a href="#rfc.xref.status.408.2">11.2.3</a></li>
     4848                  <li>409 Conflict (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.409.1">5.1</a>, <a href="#rfc.iref.47"><b>5.5.8</b></a>, <a href="#rfc.xref.status.409.2">11.2.3</a></li>
     4849                  <li>410 Gone (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.410.1">5.1</a>, <a href="#rfc.iref.48"><b>5.5.9</b></a>, <a href="#rfc.xref.status.410.2">11.2.3</a></li>
     4850                  <li>411 Length Required (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.411.1">5.1</a>, <a href="#rfc.iref.49"><b>5.5.10</b></a>, <a href="#rfc.xref.status.411.2">11.2.3</a></li>
     4851                  <li>413 Request Representation Too Large (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.413.1">5.1</a>, <a href="#rfc.iref.50"><b>5.5.11</b></a>, <a href="#rfc.xref.status.413.2">11.2.3</a></li>
     4852                  <li>414 URI Too Long (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.414.1">5.1</a>, <a href="#rfc.iref.51"><b>5.5.12</b></a>, <a href="#rfc.xref.status.414.2">11.2.3</a></li>
     4853                  <li>415 Unsupported Media Type (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.415.1">5.1</a>, <a href="#rfc.iref.52"><b>5.5.13</b></a>, <a href="#rfc.xref.status.415.2">11.2.3</a></li>
     4854                  <li>417 Expectation Failed (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.417.1">5.1</a>, <a href="#rfc.iref.53"><b>5.5.14</b></a>, <a href="#rfc.xref.status.417.2">11.2.3</a></li>
     4855                  <li>426 Upgrade Required (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.426.1">5.1</a>, <a href="#rfc.iref.54"><b>5.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>
     4856                  <li>4xx Client Error (status code class)&nbsp;&nbsp;<a href="#rfc.iref.39"><b>5.5</b></a></li>
    48504857               </ul>
    48514858            </li>
    48524859            <li><a id="rfc.index.5" href="#rfc.index.5"><b>5</b></a><ul>
    4853                   <li>500 Internal Server Error (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.500.1">5.1</a>, <a href="#rfc.iref.56"><b>5.7.1</b></a>, <a href="#rfc.xref.status.500.2">11.2</a></li>
    4854                   <li>501 Not Implemented (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.501.1">5.1</a>, <a href="#rfc.iref.57"><b>5.7.2</b></a>, <a href="#rfc.xref.status.501.2">11.2</a></li>
    4855                   <li>502 Bad Gateway (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.502.1">5.1</a>, <a href="#rfc.iref.58"><b>5.7.3</b></a>, <a href="#rfc.xref.status.502.2">11.2</a></li>
    4856                   <li>503 Service Unavailable (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.503.1">5.1</a>, <a href="#rfc.iref.59"><b>5.7.4</b></a>, <a href="#rfc.xref.status.503.2">11.2</a></li>
    4857                   <li>504 Gateway Timeout (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.504.1">5.1</a>, <a href="#rfc.iref.60"><b>5.7.5</b></a>, <a href="#rfc.xref.status.504.2">11.2</a></li>
    4858                   <li>505 HTTP Version Not Supported (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.505.1">5.1</a>, <a href="#rfc.iref.61"><b>5.7.6</b></a>, <a href="#rfc.xref.status.505.2">11.2</a></li>
    4859                   <li>5xx Server Error (status code class)&nbsp;&nbsp;<a href="#rfc.iref.55"><b>5.7</b></a></li>
     4860                  <li>500 Internal Server Error (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.500.1">5.1</a>, <a href="#rfc.iref.56"><b>5.6.1</b></a>, <a href="#rfc.xref.status.500.2">11.2.3</a></li>
     4861                  <li>501 Not Implemented (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.501.1">5.1</a>, <a href="#rfc.iref.57"><b>5.6.2</b></a>, <a href="#rfc.xref.status.501.2">11.2.3</a></li>
     4862                  <li>502 Bad Gateway (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.502.1">5.1</a>, <a href="#rfc.iref.58"><b>5.6.3</b></a>, <a href="#rfc.xref.status.502.2">11.2.3</a></li>
     4863                  <li>503 Service Unavailable (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.503.1">5.1</a>, <a href="#rfc.iref.59"><b>5.6.4</b></a>, <a href="#rfc.xref.status.503.2">11.2.3</a></li>
     4864                  <li>504 Gateway Timeout (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.504.1">5.1</a>, <a href="#rfc.iref.60"><b>5.6.5</b></a>, <a href="#rfc.xref.status.504.2">11.2.3</a></li>
     4865                  <li>505 HTTP Version Not Supported (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.505.1">5.1</a>, <a href="#rfc.iref.61"><b>5.6.6</b></a>, <a href="#rfc.xref.status.505.2">11.2.3</a></li>
     4866                  <li>5xx Server Error (status code class)&nbsp;&nbsp;<a href="#rfc.iref.55"><b>5.6</b></a></li>
    48604867               </ul>
    48614868            </li>
    … …  
    48634870                  <li>Accept header field&nbsp;&nbsp;<a href="#rfc.xref.header.accept.1">4.6</a>, <a href="#rfc.xref.header.accept.2">6.5</a>, <a href="#rfc.xref.header.accept.3">9.1</a>, <a href="#rfc.iref.a.1"><b>10.1</b></a>, <a href="#rfc.xref.header.accept.4">11.3</a></li>
    48644871                  <li>Accept-Charset header field&nbsp;&nbsp;<a href="#rfc.xref.header.accept-charset.1">4.6</a>, <a href="#rfc.xref.header.accept-charset.2">9.1</a>, <a href="#rfc.iref.a.2"><b>10.2</b></a>, <a href="#rfc.xref.header.accept-charset.3">11.3</a>, <a href="#rfc.xref.header.accept-charset.4">C</a></li>
    4865                   <li>Accept-Encoding header field&nbsp;&nbsp;<a href="#rfc.xref.header.accept-encoding.1">4.6</a>, <a href="#rfc.xref.header.accept-encoding.2">6.4</a>, <a href="#rfc.xref.header.accept-encoding.3">9.1</a>, <a href="#rfc.iref.a.3"><b>10.3</b></a>, <a href="#rfc.xref.header.accept-encoding.4">11.3</a>, <a href="#rfc.xref.header.accept-encoding.5">11.4</a></li>
     4872                  <li>Accept-Encoding header field&nbsp;&nbsp;<a href="#rfc.xref.header.accept-encoding.1">4.6</a>, <a href="#rfc.xref.header.accept-encoding.2">6.4</a>, <a href="#rfc.xref.header.accept-encoding.3">9.1</a>, <a href="#rfc.iref.a.3"><b>10.3</b></a>, <a href="#rfc.xref.header.accept-encoding.4">11.3</a>, <a href="#rfc.xref.header.accept-encoding.5">11.4.2</a></li>
    48664873                  <li>Accept-Language header field&nbsp;&nbsp;<a href="#rfc.xref.header.accept-language.1">4.6</a>, <a href="#rfc.xref.header.accept-language.2">9.1</a>, <a href="#rfc.iref.a.4"><b>10.4</b></a>, <a href="#rfc.xref.header.accept-language.3">11.3</a></li>
    48674874                  <li>Allow header field&nbsp;&nbsp;<a href="#rfc.xref.header.allow.1">3.1</a>, <a href="#rfc.xref.header.allow.2">4.7</a>, <a href="#rfc.iref.a.5"><b>10.5</b></a>, <a href="#rfc.xref.header.allow.3">11.3</a>, <a href="#rfc.xref.header.allow.4">C</a></li>
    … …  
    48784885                  </li>
    48794886                  <li>compress (Coding Format)&nbsp;&nbsp;<a href="#rfc.iref.c.4">6.4</a></li>
    4880                   <li>CONNECT method&nbsp;&nbsp;<a href="#rfc.xref.CONNECT.1">3.1</a>, <a href="#rfc.iref.c.3"><b>3.3.8</b></a>, <a href="#rfc.xref.CONNECT.2">11.1.2</a>, <a href="#rfc.xref.CONNECT.3">C</a></li>
     4887                  <li>CONNECT method&nbsp;&nbsp;<a href="#rfc.xref.CONNECT.1">3.1</a>, <a href="#rfc.iref.c.3"><b>3.3.8</b></a>, <a href="#rfc.xref.CONNECT.2">11.1.3</a>, <a href="#rfc.xref.CONNECT.3">C</a></li>
    48814888                  <li>content negotiation&nbsp;&nbsp;<a href="#rfc.iref.c.1">1</a></li>
    48824889                  <li>Content-Encoding header field&nbsp;&nbsp;<a href="#rfc.xref.header.content-encoding.1">6.4</a>, <a href="#rfc.xref.header.content-encoding.2">8.2</a>, <a href="#rfc.iref.c.8"><b>10.6</b></a>, <a href="#rfc.xref.header.content-encoding.3">11.3</a></li>
    … …  
    48904897                  <li>Date header field&nbsp;&nbsp;<a href="#rfc.xref.header.date.1">4.7</a>, <a href="#rfc.iref.d.3"><b>10.10</b></a>, <a href="#rfc.xref.header.date.2">11.3</a></li>
    48914898                  <li>deflate (Coding Format)&nbsp;&nbsp;<a href="#rfc.iref.d.2">6.4</a></li>
    4892                   <li>DELETE method&nbsp;&nbsp;<a href="#rfc.xref.DELETE.1">3.1</a>, <a href="#rfc.iref.d.1"><b>3.3.6</b></a>, <a href="#rfc.xref.DELETE.2">11.1.2</a></li>
     4899                  <li>DELETE method&nbsp;&nbsp;<a href="#rfc.xref.DELETE.1">3.1</a>, <a href="#rfc.iref.d.1"><b>3.3.6</b></a>, <a href="#rfc.xref.DELETE.2">11.1.3</a></li>
    48934900               </ul>
    48944901            </li>
    48954902            <li><a id="rfc.index.E" href="#rfc.index.E"><b>E</b></a><ul>
    4896                   <li>Expect header field&nbsp;&nbsp;<a href="#rfc.xref.header.expect.1">4.6</a>, <a href="#rfc.xref.header.expect.2">5.6.14</a>, <a href="#rfc.iref.e.1"><b>10.11</b></a>, <a href="#rfc.xref.header.expect.3">11.3</a>, <a href="#rfc.xref.header.expect.4">C</a></li>
     4903                  <li>Expect header field&nbsp;&nbsp;<a href="#rfc.xref.header.expect.1">4.6</a>, <a href="#rfc.xref.header.expect.2">5.5.14</a>, <a href="#rfc.iref.e.1"><b>10.11</b></a>, <a href="#rfc.xref.header.expect.3">11.3</a>, <a href="#rfc.xref.header.expect.4">C</a></li>
    48974904                  <li>Expect Values&nbsp;&nbsp;
    48984905                     <ul>
    … …  
    49074914            </li>
    49084915            <li><a id="rfc.index.G" href="#rfc.index.G"><b>G</b></a><ul>
    4909                   <li>GET method&nbsp;&nbsp;<a href="#rfc.xref.GET.1">3.1</a>, <a href="#rfc.iref.g.2"><b>3.3.2</b></a>, <a href="#rfc.xref.GET.2">11.1.2</a></li>
     4916                  <li>GET method&nbsp;&nbsp;<a href="#rfc.xref.GET.1">3.1</a>, <a href="#rfc.iref.g.2"><b>3.3.2</b></a>, <a href="#rfc.xref.GET.2">11.1.3</a></li>
    49104917                  <li><tt>Grammar</tt>&nbsp;&nbsp;
    49114918                     <ul>
    … …  
    49754982            </li>
    49764983            <li><a id="rfc.index.H" href="#rfc.index.H"><b>H</b></a><ul>
    4977                   <li>HEAD method&nbsp;&nbsp;<a href="#rfc.xref.HEAD.1">3.1</a>, <a href="#rfc.iref.h.1"><b>3.3.3</b></a>, <a href="#rfc.xref.HEAD.2">11.1.2</a></li>
     4984                  <li>HEAD method&nbsp;&nbsp;<a href="#rfc.xref.HEAD.1">3.1</a>, <a href="#rfc.iref.h.1"><b>3.3.3</b></a>, <a href="#rfc.xref.HEAD.2">11.1.3</a></li>
    49784985                  <li>Header Fields&nbsp;&nbsp;
    49794986                     <ul>
    49804987                        <li>Accept&nbsp;&nbsp;<a href="#rfc.xref.header.accept.1">4.6</a>, <a href="#rfc.xref.header.accept.2">6.5</a>, <a href="#rfc.xref.header.accept.3">9.1</a>, <a href="#rfc.iref.h.2"><b>10.1</b></a>, <a href="#rfc.xref.header.accept.4">11.3</a></li>
    49814988                        <li>Accept-Charset&nbsp;&nbsp;<a href="#rfc.xref.header.accept-charset.1">4.6</a>, <a href="#rfc.xref.header.accept-charset.2">9.1</a>, <a href="#rfc.iref.h.3"><b>10.2</b></a>, <a href="#rfc.xref.header.accept-charset.3">11.3</a>, <a href="#rfc.xref.header.accept-charset.4">C</a></li>
    4982                         <li>Accept-Encoding&nbsp;&nbsp;<a href="#rfc.xref.header.accept-encoding.1">4.6</a>, <a href="#rfc.xref.header.accept-encoding.2">6.4</a>, <a href="#rfc.xref.header.accept-encoding.3">9.1</a>, <a href="#rfc.iref.h.4"><b>10.3</b></a>, <a href="#rfc.xref.header.accept-encoding.4">11.3</a>, <a href="#rfc.xref.header.accept-encoding.5">11.4</a></li>
     4989                        <li>Accept-Encoding&nbsp;&nbsp;<a href="#rfc.xref.header.accept-encoding.1">4.6</a>, <a href="#rfc.xref.header.accept-encoding.2">6.4</a>, <a href="#rfc.xref.header.accept-encoding.3">9.1</a>, <a href="#rfc.iref.h.4"><b>10.3</b></a>, <a href="#rfc.xref.header.accept-encoding.4">11.3</a>, <a href="#rfc.xref.header.accept-encoding.5">11.4.2</a></li>
    49834990                        <li>Accept-Language&nbsp;&nbsp;<a href="#rfc.xref.header.accept-language.1">4.6</a>, <a href="#rfc.xref.header.accept-language.2">9.1</a>, <a href="#rfc.iref.h.5"><b>10.4</b></a>, <a href="#rfc.xref.header.accept-language.3">11.3</a></li>
    49844991                        <li>Allow&nbsp;&nbsp;<a href="#rfc.xref.header.allow.1">3.1</a>, <a href="#rfc.xref.header.allow.2">4.7</a>, <a href="#rfc.iref.h.6"><b>10.5</b></a>, <a href="#rfc.xref.header.allow.3">11.3</a>, <a href="#rfc.xref.header.allow.4">C</a></li>
    … …  
    49894996                        <li>Content-Type&nbsp;&nbsp;<a href="#rfc.xref.header.content-type.1">4.5</a>, <a href="#rfc.xref.header.content-type.2">5</a>, <a href="#rfc.xref.header.content-type.3">6.5</a>, <a href="#rfc.xref.header.content-type.4">8.2</a>, <a href="#rfc.iref.h.10"><b>10.9</b></a>, <a href="#rfc.xref.header.content-type.5">11.3</a></li>
    49904997                        <li>Date&nbsp;&nbsp;<a href="#rfc.xref.header.date.1">4.7</a>, <a href="#rfc.iref.h.11"><b>10.10</b></a>, <a href="#rfc.xref.header.date.2">11.3</a></li>
    4991                         <li>Expect&nbsp;&nbsp;<a href="#rfc.xref.header.expect.1">4.6</a>, <a href="#rfc.xref.header.expect.2">5.6.14</a>, <a href="#rfc.iref.h.12"><b>10.11</b></a>, <a href="#rfc.xref.header.expect.3">11.3</a>, <a href="#rfc.xref.header.expect.4">C</a></li>
     4998                        <li>Expect&nbsp;&nbsp;<a href="#rfc.xref.header.expect.1">4.6</a>, <a href="#rfc.xref.header.expect.2">5.5.14</a>, <a href="#rfc.iref.h.12"><b>10.11</b></a>, <a href="#rfc.xref.header.expect.3">11.3</a>, <a href="#rfc.xref.header.expect.4">C</a></li>
    49924999                        <li>From&nbsp;&nbsp;<a href="#rfc.xref.header.from.1">4.6</a>, <a href="#rfc.iref.h.13"><b>10.12</b></a>, <a href="#rfc.xref.header.from.2">11.3</a></li>
    4993                         <li>Location&nbsp;&nbsp;<a href="#rfc.xref.header.location.1">3.3.4</a>, <a href="#rfc.xref.header.location.2">4.7</a>, <a href="#rfc.xref.header.location.3">5.5</a>, <a href="#rfc.iref.h.14"><b>10.13</b></a>, <a href="#rfc.xref.header.location.4">11.3</a>, <a href="#rfc.xref.header.location.5">C</a></li>
     5000                        <li>Location&nbsp;&nbsp;<a href="#rfc.xref.header.location.1">3.3.4</a>, <a href="#rfc.xref.header.location.2">4.7</a>, <a href="#rfc.xref.header.location.3">5.4</a>, <a href="#rfc.iref.h.14"><b>10.13</b></a>, <a href="#rfc.xref.header.location.4">11.3</a>, <a href="#rfc.xref.header.location.5">C</a></li>
    49945001                        <li>Max-Forwards&nbsp;&nbsp;<a href="#rfc.xref.header.max-forwards.1">3.3.1</a>, <a href="#rfc.xref.header.max-forwards.2">3.3.7</a>, <a href="#rfc.xref.header.max-forwards.3">4.6</a>, <a href="#rfc.iref.h.15"><b>10.14</b></a>, <a href="#rfc.xref.header.max-forwards.4">11.3</a>, <a href="#rfc.xref.header.max-forwards.5">C</a></li>
    49955002                        <li>MIME-Version&nbsp;&nbsp;<a href="#rfc.xref.mime-version.1">11.3</a>, <a href="#rfc.iref.h.20"><b>A.1</b></a></li>
    49965003                        <li>Referer&nbsp;&nbsp;<a href="#rfc.xref.header.referer.1">4.6</a>, <a href="#rfc.iref.h.16"><b>10.15</b></a>, <a href="#rfc.xref.header.referer.2">11.3</a>, <a href="#rfc.xref.header.referer.3">C</a></li>
    4997                         <li>Retry-After&nbsp;&nbsp;<a href="#rfc.xref.header.retry-after.1">4.7</a>, <a href="#rfc.xref.header.retry-after.2">5.7.4</a>, <a href="#rfc.iref.h.17"><b>10.16</b></a>, <a href="#rfc.xref.header.retry-after.3">11.3</a></li>
     5004                        <li>Retry-After&nbsp;&nbsp;<a href="#rfc.xref.header.retry-after.1">4.7</a>, <a href="#rfc.xref.header.retry-after.2">5.6.4</a>, <a href="#rfc.iref.h.17"><b>10.16</b></a>, <a href="#rfc.xref.header.retry-after.3">11.3</a></li>
    49985005                        <li>Server&nbsp;&nbsp;<a href="#rfc.xref.header.server.1">4.7</a>, <a href="#rfc.iref.h.18"><b>10.17</b></a>, <a href="#rfc.xref.header.server.2">11.3</a>, <a href="#rfc.xref.header.server.3">12.1</a>, <a href="#rfc.xref.header.server.4">C</a></li>
    49995006                        <li>User-Agent&nbsp;&nbsp;<a href="#rfc.xref.header.user-agent.1">4.6</a>, <a href="#rfc.xref.header.user-agent.2">9.1</a>, <a href="#rfc.iref.h.19"><b>10.18</b></a>, <a href="#rfc.xref.header.user-agent.3">11.3</a>, <a href="#rfc.xref.header.user-agent.4">12.1</a></li>
    … …  
    50075014            </li>
    50085015            <li><a id="rfc.index.L" href="#rfc.index.L"><b>L</b></a><ul>
    5009                   <li>Location header field&nbsp;&nbsp;<a href="#rfc.xref.header.location.1">3.3.4</a>, <a href="#rfc.xref.header.location.2">4.7</a>, <a href="#rfc.xref.header.location.3">5.5</a>, <a href="#rfc.iref.l.1"><b>10.13</b></a>, <a href="#rfc.xref.header.location.4">11.3</a>, <a href="#rfc.xref.header.location.5">C</a></li>
     5016                  <li>Location header field&nbsp;&nbsp;<a href="#rfc.xref.header.location.1">3.3.4</a>, <a href="#rfc.xref.header.location.2">4.7</a>, <a href="#rfc.xref.header.location.3">5.4</a>, <a href="#rfc.iref.l.1"><b>10.13</b></a>, <a href="#rfc.xref.header.location.4">11.3</a>, <a href="#rfc.xref.header.location.5">C</a></li>
    50105017               </ul>
    50115018            </li>
    … …  
    50145021                  <li>Methods&nbsp;&nbsp;
    50155022                     <ul>
    5016                         <li>CONNECT&nbsp;&nbsp;<a href="#rfc.xref.CONNECT.1">3.1</a>, <a href="#rfc.iref.m.8"><b>3.3.8</b></a>, <a href="#rfc.xref.CONNECT.2">11.1.2</a>, <a href="#rfc.xref.CONNECT.3">C</a></li>
    5017                         <li>DELETE&nbsp;&nbsp;<a href="#rfc.xref.DELETE.1">3.1</a>, <a href="#rfc.iref.m.6"><b>3.3.6</b></a>, <a href="#rfc.xref.DELETE.2">11.1.2</a></li>
    5018                         <li>GET&nbsp;&nbsp;<a href="#rfc.xref.GET.1">3.1</a>, <a href="#rfc.iref.m.2"><b>3.3.2</b></a>, <a href="#rfc.xref.GET.2">11.1.2</a></li>
    5019                         <li>HEAD&nbsp;&nbsp;<a href="#rfc.xref.HEAD.1">3.1</a>, <a href="#rfc.iref.m.3"><b>3.3.3</b></a>, <a href="#rfc.xref.HEAD.2">11.1.2</a></li>
    5020                         <li>OPTIONS&nbsp;&nbsp;<a href="#rfc.xref.OPTIONS.1">3.1</a>, <a href="#rfc.iref.m.1"><b>3.3.1</b></a>, <a href="#rfc.xref.OPTIONS.2">10.14</a>, <a href="#rfc.xref.OPTIONS.3">11.1.2</a></li>
    5021                         <li>POST&nbsp;&nbsp;<a href="#rfc.xref.POST.1">3.1</a>, <a href="#rfc.iref.m.4"><b>3.3.4</b></a>, <a href="#rfc.xref.POST.2">11.1.2</a>, <a href="#rfc.xref.POST.3">C</a></li>
    5022                         <li>PUT&nbsp;&nbsp;<a href="#rfc.xref.PUT.1">3.1</a>, <a href="#rfc.iref.m.5"><b>3.3.5</b></a>, <a href="#rfc.xref.PUT.2">11.1.2</a>, <a href="#rfc.xref.PUT.3">C</a></li>
    5023                         <li>TRACE&nbsp;&nbsp;<a href="#rfc.xref.TRACE.1">3.1</a>, <a href="#rfc.iref.m.7"><b>3.3.7</b></a>, <a href="#rfc.xref.TRACE.2">10.14</a>, <a href="#rfc.xref.TRACE.3">11.1.2</a>, <a href="#rfc.xref.TRACE.4">12.1</a></li>
     5023                        <li>CONNECT&nbsp;&nbsp;<a href="#rfc.xref.CONNECT.1">3.1</a>, <a href="#rfc.iref.m.8"><b>3.3.8</b></a>, <a href="#rfc.xref.CONNECT.2">11.1.3</a>, <a href="#rfc.xref.CONNECT.3">C</a></li>
     5024                        <li>DELETE&nbsp;&nbsp;<a href="#rfc.xref.DELETE.1">3.1</a>, <a href="#rfc.iref.m.6"><b>3.3.6</b></a>, <a href="#rfc.xref.DELETE.2">11.1.3</a></li>
     5025                        <li>GET&nbsp;&nbsp;<a href="#rfc.xref.GET.1">3.1</a>, <a href="#rfc.iref.m.2"><b>3.3.2</b></a>, <a href="#rfc.xref.GET.2">11.1.3</a></li>
     5026                        <li>HEAD&nbsp;&nbsp;<a href="#rfc.xref.HEAD.1">3.1</a>, <a href="#rfc.iref.m.3"><b>3.3.3</b></a>, <a href="#rfc.xref.HEAD.2">11.1.3</a></li>
     5027                        <li>OPTIONS&nbsp;&nbsp;<a href="#rfc.xref.OPTIONS.1">3.1</a>, <a href="#rfc.iref.m.1"><b>3.3.1</b></a>, <a href="#rfc.xref.OPTIONS.2">10.14</a>, <a href="#rfc.xref.OPTIONS.3">11.1.3</a></li>
     5028                        <li>POST&nbsp;&nbsp;<a href="#rfc.xref.POST.1">3.1</a>, <a href="#rfc.iref.m.4"><b>3.3.4</b></a>, <a href="#rfc.xref.POST.2">11.1.3</a>, <a href="#rfc.xref.POST.3">C</a></li>
     5029                        <li>PUT&nbsp;&nbsp;<a href="#rfc.xref.PUT.1">3.1</a>, <a href="#rfc.iref.m.5"><b>3.3.5</b></a>, <a href="#rfc.xref.PUT.2">11.1.3</a>, <a href="#rfc.xref.PUT.3">C</a></li>
     5030                        <li>TRACE&nbsp;&nbsp;<a href="#rfc.xref.TRACE.1">3.1</a>, <a href="#rfc.iref.m.7"><b>3.3.7</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>
    50245031                     </ul>
    50255032                  </li>
    … …  
    50285035            </li>
    50295036            <li><a id="rfc.index.O" href="#rfc.index.O"><b>O</b></a><ul>
    5030                   <li>OPTIONS method&nbsp;&nbsp;<a href="#rfc.xref.OPTIONS.1">3.1</a>, <a href="#rfc.iref.o.1"><b>3.3.1</b></a>, <a href="#rfc.xref.OPTIONS.2">10.14</a>, <a href="#rfc.xref.OPTIONS.3">11.1.2</a></li>
     5037                  <li>OPTIONS method&nbsp;&nbsp;<a href="#rfc.xref.OPTIONS.1">3.1</a>, <a href="#rfc.iref.o.1"><b>3.3.1</b></a>, <a href="#rfc.xref.OPTIONS.2">10.14</a>, <a href="#rfc.xref.OPTIONS.3">11.1.3</a></li>
    50315038               </ul>
    50325039            </li>
    50335040            <li><a id="rfc.index.P" href="#rfc.index.P"><b>P</b></a><ul>
    5034                   <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.3.1</a>, <a href="#rfc.xref.Part1.8">3.3.7</a>, <a href="#rfc.xref.Part1.9">3.3.7</a>, <a href="#rfc.xref.Part1.10">3.3.8</a>, <a href="#rfc.xref.Part1.11">4</a>, <a href="#rfc.xref.Part1.12">4.5</a>, <a href="#rfc.xref.Part1.13">4.5</a>, <a href="#rfc.xref.Part1.14">4.5</a>, <a href="#rfc.xref.Part1.15">4.5</a>, <a href="#rfc.xref.Part1.16">4.5</a>, <a href="#rfc.xref.Part1.17">4.6</a>, <a href="#rfc.xref.Part1.18">4.6</a>, <a href="#rfc.xref.Part1.19">4.7</a>, <a href="#rfc.xref.Part1.20">5.3.1</a>, <a href="#rfc.xref.Part1.21">5.3.2</a>, <a href="#rfc.xref.Part1.22">5.4.4</a>, <a href="#rfc.xref.Part1.23">5.4.6</a>, <a href="#rfc.xref.Part1.24">5.6.15</a>, <a href="#rfc.xref.Part1.25">5.7.6</a>, <a href="#rfc.xref.Part1.26">6.4</a>, <a href="#rfc.xref.Part1.27">6.4</a>, <a href="#rfc.xref.Part1.28">6.4</a>, <a href="#rfc.xref.Part1.29">6.4.1</a>, <a href="#rfc.xref.Part1.30">6.4.1</a>, <a href="#rfc.xref.Part1.31">7.1</a>, <a href="#rfc.xref.Part1.32">7.2</a>, <a href="#rfc.xref.Part1.33">8</a>, <a href="#rfc.xref.Part1.34">8.1</a>, <a href="#rfc.xref.Part1.35">10.8</a>, <a href="#rfc.xref.Part1.36">10.11</a>, <a href="#rfc.xref.Part1.37">10.17</a>, <a href="#rfc.xref.Part1.38">10.17</a>, <a href="#rfc.xref.Part1.39">10.18</a>, <a href="#rfc.xref.Part1.40">11.1.1</a>, <a href="#rfc.xref.Part1.41">11.4</a>, <a href="#rfc.xref.Part1.42">11.4</a>, <a href="#rfc.xref.Part1.43">11.4</a>, <a href="#rfc.xref.Part1.44">13</a>, <a href="#Part1"><b>14.1</b></a>, <a href="#rfc.xref.Part1.45">C</a>, <a href="#rfc.xref.Part1.46">D</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><ul>
     5041                  <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.3.1</a>, <a href="#rfc.xref.Part1.8">3.3.7</a>, <a href="#rfc.xref.Part1.9">3.3.7</a>, <a href="#rfc.xref.Part1.10">3.3.8</a>, <a href="#rfc.xref.Part1.11">4</a>, <a href="#rfc.xref.Part1.12">4.5</a>, <a href="#rfc.xref.Part1.13">4.5</a>, <a href="#rfc.xref.Part1.14">4.5</a>, <a href="#rfc.xref.Part1.15">4.5</a>, <a href="#rfc.xref.Part1.16">4.5</a>, <a href="#rfc.xref.Part1.17">4.6</a>, <a href="#rfc.xref.Part1.18">4.6</a>, <a href="#rfc.xref.Part1.19">4.7</a>, <a href="#rfc.xref.Part1.20">5.2.1</a>, <a href="#rfc.xref.Part1.21">5.2.2</a>, <a href="#rfc.xref.Part1.22">5.3.4</a>, <a href="#rfc.xref.Part1.23">5.3.6</a>, <a href="#rfc.xref.Part1.24">5.5.15</a>, <a href="#rfc.xref.Part1.25">5.6.6</a>, <a href="#rfc.xref.Part1.26">6.4</a>, <a href="#rfc.xref.Part1.27">6.4</a>, <a href="#rfc.xref.Part1.28">6.4</a>, <a href="#rfc.xref.Part1.29">7.1</a>, <a href="#rfc.xref.Part1.30">7.2</a>, <a href="#rfc.xref.Part1.31">8</a>, <a href="#rfc.xref.Part1.32">8.1</a>, <a href="#rfc.xref.Part1.33">10.8</a>, <a href="#rfc.xref.Part1.34">10.11</a>, <a href="#rfc.xref.Part1.35">10.17</a>, <a href="#rfc.xref.Part1.36">10.17</a>, <a href="#rfc.xref.Part1.37">10.18</a>, <a href="#rfc.xref.Part1.38">11.1.2</a>, <a href="#rfc.xref.Part1.39">11.4.1</a>, <a href="#rfc.xref.Part1.40">11.4.1</a>, <a href="#rfc.xref.Part1.41">11.4.2</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">13</a>, <a href="#Part1"><b>14.1</b></a>, <a href="#rfc.xref.Part1.45">C</a>, <a href="#rfc.xref.Part1.46">D</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><ul>
    50355042                        <li><em>Section 1.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.3">1.2</a></li>
    5036                         <li><em>Section 2.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.22">5.4.4</a></li>
     5043                        <li><em>Section 2.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.22">5.3.4</a></li>
    50375044                        <li><em>Section 2.5</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.2">1.1</a></li>
    5038                         <li><em>Section 2.6</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.25">5.7.6</a></li>
     5045                        <li><em>Section 2.6</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.25">5.6.6</a></li>
    50395046                        <li><em>Section 2.7</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.4">2</a>, <a href="#rfc.xref.Part1.53">D</a>, <a href="#rfc.xref.Part1.55">D</a>, <a href="#rfc.xref.Part1.56">D</a></li>
    5040                         <li><em>Section 3.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.11">4</a>, <a href="#rfc.xref.Part1.14">4.5</a>, <a href="#rfc.xref.Part1.37">10.17</a>, <a href="#rfc.xref.Part1.39">10.18</a></li>
     5047                        <li><em>Section 3.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.11">4</a>, <a href="#rfc.xref.Part1.14">4.5</a>, <a href="#rfc.xref.Part1.35">10.17</a>, <a href="#rfc.xref.Part1.37">10.18</a></li>
    50415048                        <li><em>Section 3.2.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.47">D</a>, <a href="#rfc.xref.Part1.48">D</a>, <a href="#rfc.xref.Part1.49">D</a></li>
    50425049                        <li><em>Section 3.2.4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.13">4.5</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.54">D</a></li>
    5043                         <li><em>Section 3.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.23">5.4.6</a>, <a href="#rfc.xref.Part1.32">7.2</a>, <a href="#rfc.xref.Part1.33">8</a>, <a href="#rfc.xref.Part1.40">11.1.1</a></li>
    5044                         <li><em>Section 3.3.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.31">7.1</a></li>
    5045                         <li><em>Section 4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.29">6.4.1</a></li>
     5050                        <li><em>Section 3.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.23">5.3.6</a>, <a href="#rfc.xref.Part1.30">7.2</a>, <a href="#rfc.xref.Part1.31">8</a>, <a href="#rfc.xref.Part1.38">11.1.2</a></li>
     5051                        <li><em>Section 3.3.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.29">7.1</a></li>
     5052                        <li><em>Section 4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.39">11.4.1</a></li>
    50465053                        <li><em>Section 4.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.16">4.5</a></li>
    5047                         <li><em>Section 4.2.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.26">6.4</a>, <a href="#rfc.xref.Part1.41">11.4</a></li>
    5048                         <li><em>Section 4.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.30">6.4.1</a></li>
    5049                         <li><em>Section 4.2.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.27">6.4</a>, <a href="#rfc.xref.Part1.42">11.4</a></li>
    5050                         <li><em>Section 4.2.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.28">6.4</a>, <a href="#rfc.xref.Part1.43">11.4</a></li>
     5054                        <li><em>Section 4.2.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.26">6.4</a>, <a href="#rfc.xref.Part1.41">11.4.2</a></li>
     5055                        <li><em>Section 4.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.40">11.4.1</a></li>
     5056                        <li><em>Section 4.2.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.27">6.4</a>, <a href="#rfc.xref.Part1.42">11.4.2</a></li>
     5057                        <li><em>Section 4.2.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.28">6.4</a>, <a href="#rfc.xref.Part1.43">11.4.2</a></li>
    50515058                        <li><em>Section 4.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.18">4.6</a></li>
    50525059                        <li><em>Section 5.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.5">2</a>, <a href="#rfc.xref.Part1.7">3.3.1</a>, <a href="#rfc.xref.Part1.10">3.3.8</a></li>
    50535060                        <li><em>Section 5.4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.17">4.6</a></li>
    5054                         <li><em>Section 5.5</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.6">2</a>, <a href="#rfc.xref.Part1.19">4.7</a>, <a href="#rfc.xref.Part1.34">8.1</a>, <a href="#rfc.xref.Part1.35">10.8</a></li>
    5055                         <li><em>Section 5.7</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.8">3.3.7</a>, <a href="#rfc.xref.Part1.38">10.17</a>, <a href="#rfc.xref.Part1.45">C</a></li>
     5061                        <li><em>Section 5.5</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.6">2</a>, <a href="#rfc.xref.Part1.19">4.7</a>, <a href="#rfc.xref.Part1.32">8.1</a>, <a href="#rfc.xref.Part1.33">10.8</a></li>
     5062                        <li><em>Section 5.7</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.8">3.3.7</a>, <a href="#rfc.xref.Part1.36">10.17</a>, <a href="#rfc.xref.Part1.45">C</a></li>
    50565063                        <li><em>Section 6.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.15">4.5</a></li>
    5057                         <li><em>Section 6.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.20">5.3.1</a>, <a href="#rfc.xref.Part1.36">10.11</a></li>
    5058                         <li><em>Section 6.4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.21">5.3.2</a>, <a href="#rfc.xref.Part1.24">5.6.15</a></li>
     5064                        <li><em>Section 6.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.20">5.2.1</a>, <a href="#rfc.xref.Part1.34">10.11</a></li>
     5065                        <li><em>Section 6.4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.21">5.2.2</a>, <a href="#rfc.xref.Part1.24">5.5.15</a></li>
    50595066                        <li><em>Section 7.3.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.9">3.3.7</a></li>
    50605067                        <li><em>Section 9</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.44">13</a></li>
    … …  
    50625069                     </ul>
    50635070                  </li>
    5064                   <li><em>Part4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part4.1">3.3.2</a>, <a href="#rfc.xref.Part4.2">4.6</a>, <a href="#rfc.xref.Part4.3">4.6</a>, <a href="#rfc.xref.Part4.4">4.6</a>, <a href="#rfc.xref.Part4.5">4.6</a>, <a href="#rfc.xref.Part4.6">4.7</a>, <a href="#rfc.xref.Part4.7">5.1</a>, <a href="#rfc.xref.Part4.8">5.1</a>, <a href="#rfc.xref.Part4.9">5.1</a>, <a href="#rfc.xref.Part4.10">5.4.2</a>, <a href="#rfc.xref.Part4.11">5.5</a>, <a href="#rfc.xref.Part4.12">8.2</a>, <a href="#rfc.xref.Part4.13">8.2</a>, <a href="#Part4"><b>14.1</b></a>, <a href="#rfc.xref.Part4.14">F.2</a><ul>
     5071                  <li><em>Part4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part4.1">3.3.2</a>, <a href="#rfc.xref.Part4.2">4.6</a>, <a href="#rfc.xref.Part4.3">4.6</a>, <a href="#rfc.xref.Part4.4">4.6</a>, <a href="#rfc.xref.Part4.5">4.6</a>, <a href="#rfc.xref.Part4.6">4.7</a>, <a href="#rfc.xref.Part4.7">5.1</a>, <a href="#rfc.xref.Part4.8">5.1</a>, <a href="#rfc.xref.Part4.9">5.1</a>, <a href="#rfc.xref.Part4.10">5.3.2</a>, <a href="#rfc.xref.Part4.11">5.4</a>, <a href="#rfc.xref.Part4.12">8.2</a>, <a href="#rfc.xref.Part4.13">8.2</a>, <a href="#Part4"><b>14.1</b></a>, <a href="#rfc.xref.Part4.14">F.2</a><ul>
    50655072                        <li><em>Section 2.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part4.13">8.2</a></li>
    5066                         <li><em>Section 2.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part4.6">4.7</a>, <a href="#rfc.xref.Part4.10">5.4.2</a>, <a href="#rfc.xref.Part4.12">8.2</a></li>
     5073                        <li><em>Section 2.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part4.6">4.7</a>, <a href="#rfc.xref.Part4.10">5.3.2</a>, <a href="#rfc.xref.Part4.12">8.2</a></li>
    50675074                        <li><em>Section 3.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part4.2">4.6</a></li>
    50685075                        <li><em>Section 3.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part4.4">4.6</a></li>
    … …  
    50705077                        <li><em>Section 3.4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part4.5">4.6</a></li>
    50715078                        <li><em>Section 4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part4.7">5.1</a></li>
    5072                         <li><em>Section 4.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part4.8">5.1</a>, <a href="#rfc.xref.Part4.11">5.5</a></li>
     5079                        <li><em>Section 4.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part4.8">5.1</a>, <a href="#rfc.xref.Part4.11">5.4</a></li>
    50735080                        <li><em>Section 4.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part4.9">5.1</a></li>
    50745081                     </ul>
    … …  
    50845091                     </ul>
    50855092                  </li>
    5086                   <li><em>Part6</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.1">3.2.3</a>, <a href="#rfc.xref.Part6.2">3.3.2</a>, <a href="#rfc.xref.Part6.3">3.3.3</a>, <a href="#rfc.xref.Part6.4">3.3.4</a>, <a href="#rfc.xref.Part6.5">3.3.5</a>, <a href="#rfc.xref.Part6.6">3.3.6</a>, <a href="#rfc.xref.Part6.7">4.5</a>, <a href="#rfc.xref.Part6.8">4.7</a>, <a href="#rfc.xref.Part6.9">4.7</a>, <a href="#rfc.xref.Part6.10">5.2.1</a>, <a href="#rfc.xref.Part6.11">5.4.1</a>, <a href="#rfc.xref.Part6.12">5.4.4</a>, <a href="#rfc.xref.Part6.13">5.4.4</a>, <a href="#rfc.xref.Part6.14">5.4.4</a>, <a href="#rfc.xref.Part6.15">5.5.1</a>, <a href="#rfc.xref.Part6.16">5.5.2</a>, <a href="#rfc.xref.Part6.17">5.6.9</a>, <a href="#rfc.xref.Part6.18">8.2</a>, <a href="#rfc.xref.Part6.19">9.1</a>, <a href="#Part6"><b>14.1</b></a><ul>
     5093                  <li><em>Part6</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.1">3.2.3</a>, <a href="#rfc.xref.Part6.2">3.3.2</a>, <a href="#rfc.xref.Part6.3">3.3.3</a>, <a href="#rfc.xref.Part6.4">3.3.4</a>, <a href="#rfc.xref.Part6.5">3.3.5</a>, <a href="#rfc.xref.Part6.6">3.3.6</a>, <a href="#rfc.xref.Part6.7">4.5</a>, <a href="#rfc.xref.Part6.8">4.7</a>, <a href="#rfc.xref.Part6.9">4.7</a>, <a href="#rfc.xref.Part6.10">5.3.1</a>, <a href="#rfc.xref.Part6.11">5.3.4</a>, <a href="#rfc.xref.Part6.12">5.3.4</a>, <a href="#rfc.xref.Part6.13">5.3.4</a>, <a href="#rfc.xref.Part6.14">5.4.1</a>, <a href="#rfc.xref.Part6.15">5.4.2</a>, <a href="#rfc.xref.Part6.16">5.5.9</a>, <a href="#rfc.xref.Part6.17">8.2</a>, <a href="#rfc.xref.Part6.18">9.1</a>, <a href="#rfc.xref.Part6.19">11.2.2</a>, <a href="#Part6"><b>14.1</b></a><ul>
    50875094                        <li><em>Section 4.1.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.4">3.3.4</a></li>
    5088                         <li><em>Section 4.1.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.11">5.4.1</a>, <a href="#rfc.xref.Part6.14">5.4.4</a>, <a href="#rfc.xref.Part6.15">5.5.1</a>, <a href="#rfc.xref.Part6.16">5.5.2</a>, <a href="#rfc.xref.Part6.17">5.6.9</a></li>
     5095                        <li><em>Section 4.1.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.10">5.3.1</a>, <a href="#rfc.xref.Part6.13">5.3.4</a>, <a href="#rfc.xref.Part6.14">5.4.1</a>, <a href="#rfc.xref.Part6.15">5.4.2</a>, <a href="#rfc.xref.Part6.16">5.5.9</a></li>
    50895096                        <li><em>Section 5</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.3">3.3.3</a></li>
    50905097                        <li><em>Section 6</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.5">3.3.5</a>, <a href="#rfc.xref.Part6.6">3.3.6</a></li>
    50915098                        <li><em>Section 7.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.8">4.7</a></li>
    5092                         <li><em>Section 7.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.12">5.4.4</a></li>
    5093                         <li><em>Section 7.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.18">8.2</a></li>
    5094                         <li><em>Section 7.5</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.9">4.7</a>, <a href="#rfc.xref.Part6.19">9.1</a></li>
    5095                         <li><em>Section 7.6</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.13">5.4.4</a></li>
     5099                        <li><em>Section 7.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.11">5.3.4</a></li>
     5100                        <li><em>Section 7.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.17">8.2</a></li>
     5101                        <li><em>Section 7.5</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.9">4.7</a>, <a href="#rfc.xref.Part6.18">9.1</a></li>
     5102                        <li><em>Section 7.6</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.12">5.3.4</a></li>
    50965103                     </ul>
    50975104                  </li>
    … …  
    51075114                  </li>
    51085115                  <li>payload&nbsp;&nbsp;<a href="#rfc.iref.p.3">7</a></li>
    5109                   <li>POST method&nbsp;&nbsp;<a href="#rfc.xref.POST.1">3.1</a>, <a href="#rfc.iref.p.1"><b>3.3.4</b></a>, <a href="#rfc.xref.POST.2">11.1.2</a>, <a href="#rfc.xref.POST.3">C</a></li>
    5110                   <li>PUT method&nbsp;&nbsp;<a href="#rfc.xref.PUT.1">3.1</a>, <a href="#rfc.iref.p.2"><b>3.3.5</b></a>, <a href="#rfc.xref.PUT.2">11.1.2</a>, <a href="#rfc.xref.PUT.3">C</a></li>
     5116                  <li>POST method&nbsp;&nbsp;<a href="#rfc.xref.POST.1">3.1</a>, <a href="#rfc.iref.p.1"><b>3.3.4</b></a>, <a href="#rfc.xref.POST.2">11.1.3</a>, <a href="#rfc.xref.POST.3">C</a></li>
     5117                  <li>PUT method&nbsp;&nbsp;<a href="#rfc.xref.PUT.1">3.1</a>, <a href="#rfc.iref.p.2"><b>3.3.5</b></a>, <a href="#rfc.xref.PUT.2">11.1.3</a>, <a href="#rfc.xref.PUT.3">C</a></li>
    51115118               </ul>
    51125119            </li>
    … …  
    51155122                  <li>representation&nbsp;&nbsp;<a href="#rfc.iref.r.1">8</a></li>
    51165123                  <li><em>REST</em>&nbsp;&nbsp;<a href="#rfc.xref.REST.1">3.1</a>, <a href="#REST"><b>14.2</b></a></li>
    5117                   <li>Retry-After header field&nbsp;&nbsp;<a href="#rfc.xref.header.retry-after.1">4.7</a>, <a href="#rfc.xref.header.retry-after.2">5.7.4</a>, <a href="#rfc.iref.r.3"><b>10.16</b></a>, <a href="#rfc.xref.header.retry-after.3">11.3</a></li>
     5124                  <li>Retry-After header field&nbsp;&nbsp;<a href="#rfc.xref.header.retry-after.1">4.7</a>, <a href="#rfc.xref.header.retry-after.2">5.6.4</a>, <a href="#rfc.iref.r.3"><b>10.16</b></a>, <a href="#rfc.xref.header.retry-after.3">11.3</a></li>
    51185125                  <li><em>RFC1123</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC1123.1">6.1</a>, <a href="#rfc.xref.RFC1123.2">6.1</a>, <a href="#RFC1123"><b>14.2</b></a><ul>
    51195126                        <li><em>Section 5.2.14</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC1123.2">6.1</a></li>
    51205127                     </ul>
    51215128                  </li>
    5122                   <li><em>RFC1945</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC1945.1">5.5</a>, <a href="#RFC1945"><b>14.2</b></a>, <a href="#rfc.xref.RFC1945.2">B</a><ul>
    5123                         <li><em>Section 9.3</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC1945.1">5.5</a></li>
     5129                  <li><em>RFC1945</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC1945.1">5.4</a>, <a href="#RFC1945"><b>14.2</b></a>, <a href="#rfc.xref.RFC1945.2">B</a><ul>
     5130                        <li><em>Section 9.3</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC1945.1">5.4</a></li>
    51245131                     </ul>
    51255132                  </li>
    5126                   <li><em>RFC1950</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC1950.1">11.4</a>, <a href="#RFC1950"><b>14.1</b></a></li>
    5127                   <li><em>RFC1951</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC1951.1">11.4</a>, <a href="#RFC1951"><b>14.1</b></a></li>
    5128                   <li><em>RFC1952</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC1952.1">11.4</a>, <a href="#RFC1952"><b>14.1</b></a></li>
     5133                  <li><em>RFC1950</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC1950.1">11.4.2</a>, <a href="#RFC1950"><b>14.1</b></a></li>
     5134                  <li><em>RFC1951</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC1951.1">11.4.2</a>, <a href="#RFC1951"><b>14.1</b></a></li>
     5135                  <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>
    51295136                  <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>
    51305137                  <li><em>RFC2046</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2046.1">6.5</a>, <a href="#rfc.xref.RFC2046.2">6.5.2</a>, <a href="#rfc.xref.RFC2046.3">8.3</a>, <a href="#RFC2046"><b>14.1</b></a>, <a href="#rfc.xref.RFC2046.4">A.2</a><ul>
    … …  
    51375144                     </ul>
    51385145                  </li>
    5139                   <li><em>RFC2068</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2068.1">5.5</a>, <a href="#rfc.xref.RFC2068.2">5.5</a>, <a href="#RFC2068"><b>14.2</b></a>, <a href="#rfc.xref.RFC2068.3">B</a><ul>
    5140                         <li><em>Section 10.3</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2068.2">5.5</a></li>
    5141                         <li><em>Section 10.3.4</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2068.1">5.5</a></li>
     5146                  <li><em>RFC2068</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2068.1">5.4</a>, <a href="#rfc.xref.RFC2068.2">5.4</a>, <a href="#RFC2068"><b>14.2</b></a>, <a href="#rfc.xref.RFC2068.3">B</a><ul>
     5147                        <li><em>Section 10.3</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2068.2">5.4</a></li>
     5148                        <li><em>Section 10.3.4</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2068.1">5.4</a></li>
    51425149                     </ul>
    51435150                  </li>
    … …  
    51515158                     </ul>
    51525159                  </li>
    5153                   <li><em>RFC2616</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2616.1">5.5</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>
    5154                         <li><em>Section 10.3.8</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2616.1">5.5</a></li>
     5160                  <li><em>RFC2616</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2616.1">5.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>
     5161                        <li><em>Section 10.3.8</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2616.1">5.4</a></li>
    51555162                        <li><em>Section 14.4</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2616.2">10.4</a></li>
    51565163                     </ul>
    51575164                  </li>
    5158                   <li><em>RFC2817</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2817.1">11.2</a>, <a href="#RFC2817"><b>14.2</b></a>, <a href="#rfc.xref.RFC2817.2">C</a>, <a href="#rfc.xref.RFC2817.3">C</a>, <a href="#rfc.xref.RFC2817.4">C</a><ul>
    5159                         <li><em>Section 7.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2817.1">11.2</a>, <a href="#rfc.xref.RFC2817.3">C</a></li>
     5165                  <li><em>RFC2817</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2817.1">11.2.3</a>, <a href="#RFC2817"><b>14.2</b></a>, <a href="#rfc.xref.RFC2817.2">C</a>, <a href="#rfc.xref.RFC2817.3">C</a>, <a href="#rfc.xref.RFC2817.4">C</a><ul>
     5166                        <li><em>Section 7.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2817.1">11.2.3</a>, <a href="#rfc.xref.RFC2817.3">C</a></li>
    51605167                     </ul>
    51615168                  </li>
    … …  
    51785185                     </ul>
    51795186                  </li>
    5180                   <li><em>RFC5226</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5226.1">5.2</a>, <a href="#rfc.xref.RFC5226.2">6.4.1</a>, <a href="#rfc.xref.RFC5226.3">11.1</a>, <a href="#RFC5226"><b>14.2</b></a><ul>
    5181                         <li><em>Section 4.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5226.1">5.2</a>, <a href="#rfc.xref.RFC5226.2">6.4.1</a>, <a href="#rfc.xref.RFC5226.3">11.1</a></li>
     5187                  <li><em>RFC5226</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5226.1">11.1.1</a>, <a href="#rfc.xref.RFC5226.2">11.2.1</a>, <a href="#rfc.xref.RFC5226.3">11.4.1</a>, <a href="#RFC5226"><b>14.2</b></a><ul>
     5188                        <li><em>Section 4.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5226.1">11.1.1</a>, <a href="#rfc.xref.RFC5226.2">11.2.1</a>, <a href="#rfc.xref.RFC5226.3">11.4.1</a></li>
    51825189                     </ul>
    51835190                  </li>
    … …  
    52085215                  <li>Status Codes&nbsp;&nbsp;
    52095216                     <ul>
    5210                         <li>100 Continue&nbsp;&nbsp;<a href="#rfc.xref.status.100.1">5.1</a>, <a href="#rfc.iref.s.3"><b>5.3.1</b></a>, <a href="#rfc.xref.status.100.2">11.2</a></li>
    5211                         <li>101 Switching Protocols&nbsp;&nbsp;<a href="#rfc.xref.status.101.1">5.1</a>, <a href="#rfc.iref.s.4"><b>5.3.2</b></a>, <a href="#rfc.xref.status.101.2">11.2</a></li>
    5212                         <li>200 OK&nbsp;&nbsp;<a href="#rfc.xref.status.200.1">5.1</a>, <a href="#rfc.iref.s.6"><b>5.4.1</b></a>, <a href="#rfc.xref.status.200.2">11.2</a></li>
    5213                         <li>201 Created&nbsp;&nbsp;<a href="#rfc.xref.status.201.1">5.1</a>, <a href="#rfc.iref.s.7"><b>5.4.2</b></a>, <a href="#rfc.xref.status.201.2">11.2</a></li>
    5214                         <li>202 Accepted&nbsp;&nbsp;<a href="#rfc.xref.status.202.1">5.1</a>, <a href="#rfc.iref.s.8"><b>5.4.3</b></a>, <a href="#rfc.xref.status.202.2">11.2</a></li>
    5215                         <li>203 Non-Authoritative Information&nbsp;&nbsp;<a href="#rfc.xref.status.203.1">5.1</a>, <a href="#rfc.iref.s.9"><b>5.4.4</b></a>, <a href="#rfc.xref.status.203.2">11.2</a>, <a href="#rfc.xref.status.203.3">C</a></li>
    5216                         <li>204 No Content&nbsp;&nbsp;<a href="#rfc.xref.status.204.1">5.1</a>, <a href="#rfc.iref.s.10"><b>5.4.5</b></a>, <a href="#rfc.xref.status.204.2">11.2</a></li>
    5217                         <li>205 Reset Content&nbsp;&nbsp;<a href="#rfc.xref.status.205.1">5.1</a>, <a href="#rfc.iref.s.11"><b>5.4.6</b></a>, <a href="#rfc.xref.status.205.2">11.2</a></li>
    5218                         <li>300 Multiple Choices&nbsp;&nbsp;<a href="#rfc.xref.status.300.1">5.1</a>, <a href="#rfc.iref.s.13"><b>5.5.1</b></a>, <a href="#rfc.xref.status.300.2">11.2</a></li>
    5219                         <li>301 Moved Permanently&nbsp;&nbsp;<a href="#rfc.xref.status.301.1">5.1</a>, <a href="#rfc.iref.s.14"><b>5.5.2</b></a>, <a href="#rfc.xref.status.301.2">11.2</a>, <a href="#rfc.xref.status.301.3">C</a></li>
    5220                         <li>302 Found&nbsp;&nbsp;<a href="#rfc.xref.status.302.1">5.1</a>, <a href="#rfc.iref.s.15"><b>5.5.3</b></a>, <a href="#rfc.xref.status.302.2">11.2</a>, <a href="#rfc.xref.status.302.3">C</a></li>
    5221                         <li>303 See Other&nbsp;&nbsp;<a href="#rfc.xref.status.303.1">5.1</a>, <a href="#rfc.iref.s.16"><b>5.5.4</b></a>, <a href="#rfc.xref.status.303.2">11.2</a></li>
    5222                         <li>305 Use Proxy&nbsp;&nbsp;<a href="#rfc.xref.status.305.1">5.1</a>, <a href="#rfc.iref.s.17"><b>5.5.5</b></a>, <a href="#rfc.xref.status.305.2">11.2</a>, <a href="#rfc.xref.status.305.3">C</a></li>
    5223                         <li>306 (Unused)&nbsp;&nbsp;<a href="#rfc.iref.s.18"><b>5.5.6</b></a>, <a href="#rfc.xref.status.306.1">11.2</a></li>
    5224                         <li>307 Temporary Redirect&nbsp;&nbsp;<a href="#rfc.xref.status.307.1">5.1</a>, <a href="#rfc.iref.s.19"><b>5.5.7</b></a>, <a href="#rfc.xref.status.307.2">11.2</a>, <a href="#rfc.xref.status.307.3">C</a></li>
    5225                         <li>400 Bad Request&nbsp;&nbsp;<a href="#rfc.xref.status.400.1">5.1</a>, <a href="#rfc.iref.s.21"><b>5.6.1</b></a>, <a href="#rfc.xref.status.400.2">11.2</a></li>
    5226                         <li>402 Payment Required&nbsp;&nbsp;<a href="#rfc.xref.status.402.1">5.1</a>, <a href="#rfc.iref.s.22"><b>5.6.2</b></a>, <a href="#rfc.xref.status.402.2">11.2</a></li>
    5227                         <li>403 Forbidden&nbsp;&nbsp;<a href="#rfc.xref.status.403.1">5.1</a>, <a href="#rfc.iref.s.23"><b>5.6.3</b></a>, <a href="#rfc.xref.status.403.2">11.2</a></li>
    5228                         <li>404 Not Found&nbsp;&nbsp;<a href="#rfc.xref.status.404.1">5.1</a>, <a href="#rfc.iref.s.24"><b>5.6.4</b></a>, <a href="#rfc.xref.status.404.2">11.2</a></li>
    5229                         <li>405 Method Not Allowed&nbsp;&nbsp;<a href="#rfc.xref.status.405.1">5.1</a>, <a href="#rfc.iref.s.25"><b>5.6.5</b></a>, <a href="#rfc.xref.status.405.2">11.2</a></li>
    5230                         <li>406 Not Acceptable&nbsp;&nbsp;<a href="#rfc.xref.status.406.1">5.1</a>, <a href="#rfc.iref.s.26"><b>5.6.6</b></a>, <a href="#rfc.xref.status.406.2">11.2</a></li>
    5231                         <li>408 Request Timeout&nbsp;&nbsp;<a href="#rfc.xref.status.408.1">5.1</a>, <a href="#rfc.iref.s.27"><b>5.6.7</b></a>, <a href="#rfc.xref.status.408.2">11.2</a></li>
    5232                         <li>409 Conflict&nbsp;&nbsp;<a href="#rfc.xref.status.409.1">5.1</a>, <a href="#rfc.iref.s.28"><b>5.6.8</b></a>, <a href="#rfc.xref.status.409.2">11.2</a></li>
    5233                         <li>410 Gone&nbsp;&nbsp;<a href="#rfc.xref.status.410.1">5.1</a>, <a href="#rfc.iref.s.29"><b>5.6.9</b></a>, <a href="#rfc.xref.status.410.2">11.2</a></li>
    5234                         <li>411 Length Required&nbsp;&nbsp;<a href="#rfc.xref.status.411.1">5.1</a>, <a href="#rfc.iref.s.30"><b>5.6.10</b></a>, <a href="#rfc.xref.status.411.2">11.2</a></li>
    5235                         <li>413 Request Representation Too Large&nbsp;&nbsp;<a href="#rfc.xref.status.413.1">5.1</a>, <a href="#rfc.iref.s.31"><b>5.6.11</b></a>, <a href="#rfc.xref.status.413.2">11.2</a></li>
    5236                         <li>414 URI Too Long&nbsp;&nbsp;<a href="#rfc.xref.status.414.1">5.1</a>, <a href="#rfc.iref.s.32"><b>5.6.12</b></a>, <a href="#rfc.xref.status.414.2">11.2</a></li>
    5237                         <li>415 Unsupported Media Type&nbsp;&nbsp;<a href="#rfc.xref.status.415.1">5.1</a>, <a href="#rfc.iref.s.33"><b>5.6.13</b></a>, <a href="#rfc.xref.status.415.2">11.2</a></li>
    5238                         <li>417 Expectation Failed&nbsp;&nbsp;<a href="#rfc.xref.status.417.1">5.1</a>, <a href="#rfc.iref.s.34"><b>5.6.14</b></a>, <a href="#rfc.xref.status.417.2">11.2</a></li>
    5239                         <li>426 Upgrade Required&nbsp;&nbsp;<a href="#rfc.xref.status.426.1">5.1</a>, <a href="#rfc.iref.s.35"><b>5.6.15</b></a>, <a href="#rfc.xref.status.426.2">11.2</a>, <a href="#rfc.xref.status.426.3">C</a></li>
    5240                         <li>500 Internal Server Error&nbsp;&nbsp;<a href="#rfc.xref.status.500.1">5.1</a>, <a href="#rfc.iref.s.37"><b>5.7.1</b></a>, <a href="#rfc.xref.status.500.2">11.2</a></li>
    5241                         <li>501 Not Implemented&nbsp;&nbsp;<a href="#rfc.xref.status.501.1">5.1</a>, <a href="#rfc.iref.s.38"><b>5.7.2</b></a>, <a href="#rfc.xref.status.501.2">11.2</a></li>
    5242                         <li>502 Bad Gateway&nbsp;&nbsp;<a href="#rfc.xref.status.502.1">5.1</a>, <a href="#rfc.iref.s.39"><b>5.7.3</b></a>, <a href="#rfc.xref.status.502.2">11.2</a></li>
    5243                         <li>503 Service Unavailable&nbsp;&nbsp;<a href="#rfc.xref.status.503.1">5.1</a>, <a href="#rfc.iref.s.40"><b>5.7.4</b></a>, <a href="#rfc.xref.status.503.2">11.2</a></li>
    5244                         <li>504 Gateway Timeout&nbsp;&nbsp;<a href="#rfc.xref.status.504.1">5.1</a>, <a href="#rfc.iref.s.41"><b>5.7.5</b></a>, <a href="#rfc.xref.status.504.2">11.2</a></li>
    5245                         <li>505 HTTP Version Not Supported&nbsp;&nbsp;<a href="#rfc.xref.status.505.1">5.1</a>, <a href="#rfc.iref.s.42"><b>5.7.6</b></a>, <a href="#rfc.xref.status.505.2">11.2</a></li>
     5217                        <li>100 Continue&nbsp;&nbsp;<a href="#rfc.xref.status.100.1">5.1</a>, <a href="#rfc.iref.s.3"><b>5.2.1</b></a>, <a href="#rfc.xref.status.100.2">11.2.3</a></li>
     5218                        <li>101 Switching Protocols&nbsp;&nbsp;<a href="#rfc.xref.status.101.1">5.1</a>, <a href="#rfc.iref.s.4"><b>5.2.2</b></a>, <a href="#rfc.xref.status.101.2">11.2.3</a></li>
     5219                        <li>200 OK&nbsp;&nbsp;<a href="#rfc.xref.status.200.1">5.1</a>, <a href="#rfc.iref.s.6"><b>5.3.1</b></a>, <a href="#rfc.xref.status.200.2">11.2.3</a></li>
     5220                        <li>201 Created&nbsp;&nbsp;<a href="#rfc.xref.status.201.1">5.1</a>, <a href="#rfc.iref.s.7"><b>5.3.2</b></a>, <a href="#rfc.xref.status.201.2">11.2.3</a></li>
     5221                        <li>202 Accepted&nbsp;&nbsp;<a href="#rfc.xref.status.202.1">5.1</a>, <a href="#rfc.iref.s.8"><b>5.3.3</b></a>, <a href="#rfc.xref.status.202.2">11.2.3</a></li>
     5222                        <li>203 Non-Authoritative Information&nbsp;&nbsp;<a href="#rfc.xref.status.203.1">5.1</a>, <a href="#rfc.iref.s.9"><b>5.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>
     5223                        <li>204 No Content&nbsp;&nbsp;<a href="#rfc.xref.status.204.1">5.1</a>, <a href="#rfc.iref.s.10"><b>5.3.5</b></a>, <a href="#rfc.xref.status.204.2">11.2.3</a></li>
     5224                        <li>205 Reset Content&nbsp;&nbsp;<a href="#rfc.xref.status.205.1">5.1</a>, <a href="#rfc.iref.s.11"><b>5.3.6</b></a>, <a href="#rfc.xref.status.205.2">11.2.3</a></li>
     5225                        <li>300 Multiple Choices&nbsp;&nbsp;<a href="#rfc.xref.status.300.1">5.1</a>, <a href="#rfc.iref.s.13"><b>5.4.1</b></a>, <a href="#rfc.xref.status.300.2">11.2.3</a></li>
     5226                        <li>301 Moved Permanently&nbsp;&nbsp;<a href="#rfc.xref.status.301.1">5.1</a>, <a href="#rfc.iref.s.14"><b>5.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>
     5227                        <li>302 Found&nbsp;&nbsp;<a href="#rfc.xref.status.302.1">5.1</a>, <a href="#rfc.iref.s.15"><b>5.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>
     5228                        <li>303 See Other&nbsp;&nbsp;<a href="#rfc.xref.status.303.1">5.1</a>, <a href="#rfc.iref.s.16"><b>5.4.4</b></a>, <a href="#rfc.xref.status.303.2">11.2.3</a></li>
     5229                        <li>305 Use Proxy&nbsp;&nbsp;<a href="#rfc.xref.status.305.1">5.1</a>, <a href="#rfc.iref.s.17"><b>5.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>
     5230                        <li>306 (Unused)&nbsp;&nbsp;<a href="#rfc.iref.s.18"><b>5.4.6</b></a>, <a href="#rfc.xref.status.306.1">11.2.3</a></li>
     5231                        <li>307 Temporary Redirect&nbsp;&nbsp;<a href="#rfc.xref.status.307.1">5.1</a>, <a href="#rfc.iref.s.19"><b>5.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>
     5232                        <li>400 Bad Request&nbsp;&nbsp;<a href="#rfc.xref.status.400.1">5.1</a>, <a href="#rfc.iref.s.21"><b>5.5.1</b></a>, <a href="#rfc.xref.status.400.2">11.2.3</a></li>
     5233                        <li>402 Payment Required&nbsp;&nbsp;<a href="#rfc.xref.status.402.1">5.1</a>, <a href="#rfc.iref.s.22"><b>5.5.2</b></a>, <a href="#rfc.xref.status.402.2">11.2.3</a></li>
     5234                        <li>403 Forbidden&nbsp;&nbsp;<a href="#rfc.xref.status.403.1">5.1</a>, <a href="#rfc.iref.s.23"><b>5.5.3</b></a>, <a href="#rfc.xref.status.403.2">11.2.3</a></li>
     5235                        <li>404 Not Found&nbsp;&nbsp;<a href="#rfc.xref.status.404.1">5.1</a>, <a href="#rfc.iref.s.24"><b>5.5.4</b></a>, <a href="#rfc.xref.status.404.2">11.2.3</a></li>
     5236                        <li>405 Method Not Allowed&nbsp;&nbsp;<a href="#rfc.xref.status.405.1">5.1</a>, <a href="#rfc.iref.s.25"><b>5.5.5</b></a>, <a href="#rfc.xref.status.405.2">11.2.3</a></li>
     5237                        <li>406 Not Acceptable&nbsp;&nbsp;<a href="#rfc.xref.status.406.1">5.1</a>, <a href="#rfc.iref.s.26"><b>5.5.6</b></a>, <a href="#rfc.xref.status.406.2">11.2.3</a></li>
     5238                        <li>408 Request Timeout&nbsp;&nbsp;<a href="#rfc.xref.status.408.1">5.1</a>, <a href="#rfc.iref.s.27"><b>5.5.7</b></a>, <a href="#rfc.xref.status.408.2">11.2.3</a></li>
     5239                        <li>409 Conflict&nbsp;&nbsp;<a href="#rfc.xref.status.409.1">5.1</a>, <a href="#rfc.iref.s.28"><b>5.5.8</b></a>, <a href="#rfc.xref.status.409.2">11.2.3</a></li>
     5240                        <li>410 Gone&nbsp;&nbsp;<a href="#rfc.xref.status.410.1">5.1</a>, <a href="#rfc.iref.s.29"><b>5.5.9</b></a>, <a href="#rfc.xref.status.410.2">11.2.3</a></li>
     5241                        <li>411 Length Required&nbsp;&nbsp;<a href="#rfc.xref.status.411.1">5.1</a>, <a href="#rfc.iref.s.30"><b>5.5.10</b></a>, <a href="#rfc.xref.status.411.2">11.2.3</a></li>
     5242                        <li>413 Request Representation Too Large&nbsp;&nbsp;<a href="#rfc.xref.status.413.1">5.1</a>, <a href="#rfc.iref.s.31"><b>5.5.11</b></a>, <a href="#rfc.xref.status.413.2">11.2.3</a></li>
     5243                        <li>414 URI Too Long&nbsp;&nbsp;<a href="#rfc.xref.status.414.1">5.1</a>, <a href="#rfc.iref.s.32"><b>5.5.12</b></a>, <a href="#rfc.xref.status.414.2">11.2.3</a></li>
     5244                        <li>415 Unsupported Media Type&nbsp;&nbsp;<a href="#rfc.xref.status.415.1">5.1</a>, <a href="#rfc.iref.s.33"><b>5.5.13</b></a>, <a href="#rfc.xref.status.415.2">11.2.3</a></li>
     5245                        <li>417 Expectation Failed&nbsp;&nbsp;<a href="#rfc.xref.status.417.1">5.1</a>, <a href="#rfc.iref.s.34"><b>5.5.14</b></a>, <a href="#rfc.xref.status.417.2">11.2.3</a></li>
     5246                        <li>426 Upgrade Required&nbsp;&nbsp;<a href="#rfc.xref.status.426.1">5.1</a>, <a href="#rfc.iref.s.35"><b>5.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>
     5247                        <li>500 Internal Server Error&nbsp;&nbsp;<a href="#rfc.xref.status.500.1">5.1</a>, <a href="#rfc.iref.s.37"><b>5.6.1</b></a>, <a href="#rfc.xref.status.500.2">11.2.3</a></li>
     5248                        <li>501 Not Implemented&nbsp;&nbsp;<a href="#rfc.xref.status.501.1">5.1</a>, <a href="#rfc.iref.s.38"><b>5.6.2</b></a>, <a href="#rfc.xref.status.501.2">11.2.3</a></li>
     5249                        <li>502 Bad Gateway&nbsp;&nbsp;<a href="#rfc.xref.status.502.1">5.1</a>, <a href="#rfc.iref.s.39"><b>5.6.3</b></a>, <a href="#rfc.xref.status.502.2">11.2.3</a></li>
     5250                        <li>503 Service Unavailable&nbsp;&nbsp;<a href="#rfc.xref.status.503.1">5.1</a>, <a href="#rfc.iref.s.40"><b>5.6.4</b></a>, <a href="#rfc.xref.status.503.2">11.2.3</a></li>
     5251                        <li>504 Gateway Timeout&nbsp;&nbsp;<a href="#rfc.xref.status.504.1">5.1</a>, <a href="#rfc.iref.s.41"><b>5.6.5</b></a>, <a href="#rfc.xref.status.504.2">11.2.3</a></li>
     5252                        <li>505 HTTP Version Not Supported&nbsp;&nbsp;<a href="#rfc.xref.status.505.1">5.1</a>, <a href="#rfc.iref.s.42"><b>5.6.6</b></a>, <a href="#rfc.xref.status.505.2">11.2.3</a></li>
    52465253                     </ul>
    52475254                  </li>
    52485255                  <li>Status Codes Classes&nbsp;&nbsp;
    52495256                     <ul>
    5250                         <li>1xx Informational&nbsp;&nbsp;<a href="#rfc.iref.s.2"><b>5.3</b></a></li>
    5251                         <li>2xx Successful&nbsp;&nbsp;<a href="#rfc.iref.s.5"><b>5.4</b></a></li>
    5252                         <li>3xx Redirection&nbsp;&nbsp;<a href="#rfc.iref.s.12"><b>5.5</b></a>, <a href="#rfc.xref.status.3xx.1">C</a></li>
    5253                         <li>4xx Client Error&nbsp;&nbsp;<a href="#rfc.iref.s.20"><b>5.6</b></a></li>
    5254                         <li>5xx Server Error&nbsp;&nbsp;<a href="#rfc.iref.s.36"><b>5.7</b></a></li>
     5257                        <li>1xx Informational&nbsp;&nbsp;<a href="#rfc.iref.s.2"><b>5.2</b></a></li>
     5258                        <li>2xx Successful&nbsp;&nbsp;<a href="#rfc.iref.s.5"><b>5.3</b></a></li>
     5259                        <li>3xx Redirection&nbsp;&nbsp;<a href="#rfc.iref.s.12"><b>5.4</b></a>, <a href="#rfc.xref.status.3xx.1">C</a></li>
     5260                        <li>4xx Client Error&nbsp;&nbsp;<a href="#rfc.iref.s.20"><b>5.5</b></a></li>
     5261                        <li>5xx Server Error&nbsp;&nbsp;<a href="#rfc.iref.s.36"><b>5.6</b></a></li>
    52555262                     </ul>
    52565263                  </li>
    5257                   <li><em>status-308</em>&nbsp;&nbsp;<a href="#rfc.xref.status-308.1">5.5.7</a>, <a href="#status-308"><b>14.2</b></a></li>
     5264                  <li><em>status-308</em>&nbsp;&nbsp;<a href="#rfc.xref.status-308.1">5.4.7</a>, <a href="#status-308"><b>14.2</b></a></li>
    52585265               </ul>
    52595266            </li>
    52605267            <li><a id="rfc.index.T" href="#rfc.index.T"><b>T</b></a><ul>
    5261                   <li>TRACE method&nbsp;&nbsp;<a href="#rfc.xref.TRACE.1">3.1</a>, <a href="#rfc.iref.t.1"><b>3.3.7</b></a>, <a href="#rfc.xref.TRACE.2">10.14</a>, <a href="#rfc.xref.TRACE.3">11.1.2</a>, <a href="#rfc.xref.TRACE.4">12.1</a></li>
     5268                  <li>TRACE method&nbsp;&nbsp;<a href="#rfc.xref.TRACE.1">3.1</a>, <a href="#rfc.iref.t.1"><b>3.3.7</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>
    52625269               </ul>
    52635270            </li>

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

    r1842 r1843  
    12401240</section>
    12411241
    1242 <section title="Status Code Registry" anchor="status.code.registry">
    1243 <t>
    1244   The HTTP Status Code Registry defines the name space for the status-code
    1245   token in the status-line of an HTTP response.
    1246 </t>
    1247 <t>
    1248   Values to be added to this name space require IETF Review
    1249   (see <xref target="RFC5226" x:fmt="," x:sec="4.1"/>).
    1250 </t>
    1251 <t>
    1252   The registry itself is maintained at <eref target="http://www.iana.org/assignments/http-status-codes"/>.
    1253 </t>
    1254 
    1255 <section title="Considerations for New Status Codes" anchor="considerations.for.new.status.codes">
    1256 <t>
    1257    When it is necessary to express new semantics for a HTTP response that
    1258    aren't specific to a single application or media type, and currently defined
    1259    status codes are inadequate, a new status code can be registered.
    1260 </t>
    1261 <t>
    1262    HTTP status codes are generic; that is, they are potentially applicable to
    1263    any resource, not just one particular media type, "type" of resource, or
    1264    application. As such, it is preferred that new HTTP status codes be
    1265    registered in a document that isn't specific to a single application, so
    1266    that this is clear.
    1267 </t>
    1268 <t>
    1269    Definitions of new HTTP status codes typically explain the request
    1270    conditions that produce a response containing the status code (e.g.,
    1271    combinations of request header fields and/or method(s)), along with any
    1272    interactions with response header fields (e.g., those that are required,
    1273    those that modify the semantics of the response).
    1274 </t>
    1275 <t>
    1276    New HTTP status codes are required to fall under one of the categories
    1277    defined in <xref target="status.codes"/>. To allow existing parsers to
    1278    properly handle them, new status codes cannot disallow a response body,
    1279    although they can mandate a zero-length response body. They can require the
    1280    presence of one or more particular HTTP response header field(s).
    1281 </t>
    1282 <t>
    1283    Likewise, their definitions can specify that caches are allowed to use
    1284    heuristics to determine their freshness (see &caching;; by default, it is
    1285    not allowed), and can define how to determine the resource which they
    1286    carry a representation for (see <xref
    1287    target="identifying.response.associated.with.representation"/>; by default,
    1288    it is anonymous).
    1289 </t>
    1290 </section>
    1291 
    1292 </section>
    1293 
    12941242<section title="Informational 1xx" anchor="status.1xx">
    12951243  <x:anchor-alias value="1xx"/>
    … …  
    24362384  </list>
    24372385</t>
    2438 
    2439 <section title="Content Coding Registry" anchor="content.coding.registry">
    2440 <t>
    2441    The HTTP Content Coding Registry defines the name space for the content
    2442    coding names.
    2443 </t>
    2444 <t>
    2445    Registrations &MUST; include the following fields:
    2446    <list style="symbols">
    2447      <t>Name</t>
    2448      <t>Description</t>
    2449      <t>Pointer to specification text</t>
    2450    </list>
    2451 </t>
    2452 <t>
    2453    Names of content codings &MUST-NOT; overlap with names of transfer codings
    2454    (&transfer-codings;), unless the encoding transformation is identical (as
    2455    is the case for the compression codings defined in
    2456    &compression-codings;).
    2457 </t>
    2458 <t>
    2459    Values to be added to this name space require IETF Review
    2460    (see <xref target="RFC5226" x:fmt="of" x:sec="4.1"/>), and &MUST;
    2461    conform to the purpose of content coding defined in this section.
    2462 </t>
    2463 <t>
    2464    The registry itself is maintained at
    2465    <eref target="http://www.iana.org/assignments/http-parameters"/>.
    2466 </t>
    2467 </section>
    2468 
    24692386</section>
    24702387
    … …  
    40303947  Request line of an HTTP request.
    40313948</t>
     3949<section title="Procedure" anchor="method.procedure">
    40323950<t>
    40333951  Registrations &MUST; include the following fields:
    … …  
    40463964  The registry itself is maintained at <eref target="http://www.iana.org/assignments/http-methods"/>.
    40473965</t>
     3966</section>
    40483967
    40493968<section title="Considerations for New Methods" anchor="considerations.for.new.methods">
    … …  
    41414060</section>
    41424061
    4143 <section title="Status Code Registry" anchor="status.code.registration">
     4062<section title="Status Code Registry" anchor="status.code.registry">
     4063<t>
     4064  The HTTP Status Code Registry defines the name space for the status-code
     4065  token in the status-line of an HTTP response (<xref target="status.codes"/>).
     4066</t>
     4067
     4068<section title="Procedure" anchor="status.code.procedure">
     4069<t>
     4070  Values to be added to this name space require IETF Review
     4071  (see <xref target="RFC5226" x:fmt="," x:sec="4.1"/>).
     4072</t>
     4073<t>
     4074  The registry itself is maintained at <eref target="http://www.iana.org/assignments/http-status-codes"/>.
     4075</t>
     4076</section>
     4077
     4078<section title="Considerations for New Status Codes" anchor="considerations.for.new.status.codes">
     4079<t>
     4080   When it is necessary to express new semantics for a HTTP response that
     4081   aren't specific to a single application or media type, and currently defined
     4082   status codes are inadequate, a new status code can be registered.
     4083</t>
     4084<t>
     4085   HTTP status codes are generic; that is, they are potentially applicable to
     4086   any resource, not just one particular media type, "type" of resource, or
     4087   application. As such, it is preferred that new HTTP status codes be
     4088   registered in a document that isn't specific to a single application, so
     4089   that this is clear.
     4090</t>
     4091<t>
     4092   Definitions of new HTTP status codes typically explain the request
     4093   conditions that produce a response containing the status code (e.g.,
     4094   combinations of request header fields and/or method(s)), along with any
     4095   interactions with response header fields (e.g., those that are required,
     4096   those that modify the semantics of the response).
     4097</t>
     4098<t>
     4099   New HTTP status codes are required to fall under one of the categories
     4100   defined in <xref target="status.codes"/>. To allow existing parsers to
     4101   properly handle them, new status codes cannot disallow a response body,
     4102   although they can mandate a zero-length response body. They can require the
     4103   presence of one or more particular HTTP response header field(s).
     4104</t>
     4105<t>
     4106   Likewise, their definitions can specify that caches are allowed to use
     4107   heuristics to determine their freshness (see &caching;; by default, it is
     4108   not allowed), and can define how to determine the resource which they
     4109   carry a representation for (see <xref
     4110   target="identifying.response.associated.with.representation"/>; by default,
     4111   it is anonymous).
     4112</t>
     4113</section>
     4114
     4115<section title="Registrations" anchor="status.code.registration">
    41444116<t>
    41454117   The registration procedure for HTTP Status Codes &mdash; previously defined
    … …  
    43414313<?ENDINC p2-semantics.iana-status-codes ?>
    43424314</section>
     4315</section>
     4316
    43434317<section title="Header Field Registration" anchor="header.field.registration">
    43444318<t>
    … …  
    44764450</section>
    44774451
    4478 <section title="Content Coding Registry" anchor="content.coding.registration">
     4452<section title="Content Coding Registry" anchor="content.coding.registry">
     4453<t>
     4454   The HTTP Content Coding Registry defines the name space for the content
     4455   coding names.
     4456</t>
     4457
     4458<section title="Procedure" anchor="content.coding.procedure">
     4459<t>
     4460   Registrations &MUST; include the following fields:
     4461   <list style="symbols">
     4462     <t>Name</t>
     4463     <t>Description</t>
     4464     <t>Pointer to specification text</t>
     4465   </list>
     4466</t>
     4467<t>
     4468   Names of content codings &MUST-NOT; overlap with names of transfer codings
     4469   (&transfer-codings;), unless the encoding transformation is identical (as
     4470   is the case for the compression codings defined in
     4471   &compression-codings;).
     4472</t>
     4473<t>
     4474   Values to be added to this name space require IETF Review
     4475   (see <xref target="RFC5226" x:fmt="of" x:sec="4.1"/>), and &MUST;
     4476   conform to the purpose of content coding defined in this section.
     4477</t>
     4478<t>
     4479   The registry itself is maintained at
     4480   <eref target="http://www.iana.org/assignments/http-parameters"/>.
     4481</t>
     4482</section>
     4483
     4484<section title="Registrations" anchor="content.coding.registration">
    44794485<t>
    44804486   The registration procedure for HTTP Content Codings is now defined
    … …  
    45144520</texttable>
    45154521</section>
    4516 
     4522</section>
    45174523</section>
    45184524
Note: See TracChangeset for help on using the changeset viewer.