Changeset 1843 for draft-ietf-httpbis/latest
- Timestamp:
- 01/09/12 06:20:46 (10 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p2-semantics.html
r1842 r1843 619 619 <li><a href="#rfc.section.5">5.</a> <a href="#status.codes">Response Status Codes</a><ul> 620 620 <li><a href="#rfc.section.5.1">5.1</a> <a href="#overview.of.status.codes">Overview of Status Codes</a></li> 621 <li><a href="#rfc.section.5.2">5.2</a> <a href="#status.code.registry">Status Code Registry</a><ul> 622 <li><a href="#rfc.section.5.2.1">5.2.1</a> <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> <a href="#status.1xx">Informational 1xx</a><ul> 622 <li><a href="#rfc.section.5.2.1">5.2.1</a> <a href="#status.100">100 Continue</a></li> 623 <li><a href="#rfc.section.5.2.2">5.2.2</a> <a href="#status.101">101 Switching Protocols</a></li> 623 624 </ul> 624 625 </li> 625 <li><a href="#rfc.section.5.3">5.3</a> <a href="#status.1xx">Informational 1xx</a><ul> 626 <li><a href="#rfc.section.5.3.1">5.3.1</a> <a href="#status.100">100 Continue</a></li> 627 <li><a href="#rfc.section.5.3.2">5.3.2</a> <a href="#status.101">101 Switching Protocols</a></li> 626 <li><a href="#rfc.section.5.3">5.3</a> <a href="#status.2xx">Successful 2xx</a><ul> 627 <li><a href="#rfc.section.5.3.1">5.3.1</a> <a href="#status.200">200 OK</a></li> 628 <li><a href="#rfc.section.5.3.2">5.3.2</a> <a href="#status.201">201 Created</a></li> 629 <li><a href="#rfc.section.5.3.3">5.3.3</a> <a href="#status.202">202 Accepted</a></li> 630 <li><a href="#rfc.section.5.3.4">5.3.4</a> <a href="#status.203">203 Non-Authoritative Information</a></li> 631 <li><a href="#rfc.section.5.3.5">5.3.5</a> <a href="#status.204">204 No Content</a></li> 632 <li><a href="#rfc.section.5.3.6">5.3.6</a> <a href="#status.205">205 Reset Content</a></li> 628 633 </ul> 629 634 </li> 630 <li><a href="#rfc.section.5.4">5.4</a> <a href="#status.2xx">Successful 2xx</a><ul> 631 <li><a href="#rfc.section.5.4.1">5.4.1</a> <a href="#status.200">200 OK</a></li> 632 <li><a href="#rfc.section.5.4.2">5.4.2</a> <a href="#status.201">201 Created</a></li> 633 <li><a href="#rfc.section.5.4.3">5.4.3</a> <a href="#status.202">202 Accepted</a></li> 634 <li><a href="#rfc.section.5.4.4">5.4.4</a> <a href="#status.203">203 Non-Authoritative Information</a></li> 635 <li><a href="#rfc.section.5.4.5">5.4.5</a> <a href="#status.204">204 No Content</a></li> 636 <li><a href="#rfc.section.5.4.6">5.4.6</a> <a href="#status.205">205 Reset Content</a></li> 635 <li><a href="#rfc.section.5.4">5.4</a> <a href="#status.3xx">Redirection 3xx</a><ul> 636 <li><a href="#rfc.section.5.4.1">5.4.1</a> <a href="#status.300">300 Multiple Choices</a></li> 637 <li><a href="#rfc.section.5.4.2">5.4.2</a> <a href="#status.301">301 Moved Permanently</a></li> 638 <li><a href="#rfc.section.5.4.3">5.4.3</a> <a href="#status.302">302 Found</a></li> 639 <li><a href="#rfc.section.5.4.4">5.4.4</a> <a href="#status.303">303 See Other</a></li> 640 <li><a href="#rfc.section.5.4.5">5.4.5</a> <a href="#status.305">305 Use Proxy</a></li> 641 <li><a href="#rfc.section.5.4.6">5.4.6</a> <a href="#status.306">306 (Unused)</a></li> 642 <li><a href="#rfc.section.5.4.7">5.4.7</a> <a href="#status.307">307 Temporary Redirect</a></li> 637 643 </ul> 638 644 </li> 639 <li><a href="#rfc.section.5.5">5.5</a> <a href="#status.3xx">Redirection 3xx</a><ul> 640 <li><a href="#rfc.section.5.5.1">5.5.1</a> <a href="#status.300">300 Multiple Choices</a></li> 641 <li><a href="#rfc.section.5.5.2">5.5.2</a> <a href="#status.301">301 Moved Permanently</a></li> 642 <li><a href="#rfc.section.5.5.3">5.5.3</a> <a href="#status.302">302 Found</a></li> 643 <li><a href="#rfc.section.5.5.4">5.5.4</a> <a href="#status.303">303 See Other</a></li> 644 <li><a href="#rfc.section.5.5.5">5.5.5</a> <a href="#status.305">305 Use Proxy</a></li> 645 <li><a href="#rfc.section.5.5.6">5.5.6</a> <a href="#status.306">306 (Unused)</a></li> 646 <li><a href="#rfc.section.5.5.7">5.5.7</a> <a href="#status.307">307 Temporary Redirect</a></li> 645 <li><a href="#rfc.section.5.5">5.5</a> <a href="#status.4xx">Client Error 4xx</a><ul> 646 <li><a href="#rfc.section.5.5.1">5.5.1</a> <a href="#status.400">400 Bad Request</a></li> 647 <li><a href="#rfc.section.5.5.2">5.5.2</a> <a href="#status.402">402 Payment Required</a></li> 648 <li><a href="#rfc.section.5.5.3">5.5.3</a> <a href="#status.403">403 Forbidden</a></li> 649 <li><a href="#rfc.section.5.5.4">5.5.4</a> <a href="#status.404">404 Not Found</a></li> 650 <li><a href="#rfc.section.5.5.5">5.5.5</a> <a href="#status.405">405 Method Not Allowed</a></li> 651 <li><a href="#rfc.section.5.5.6">5.5.6</a> <a href="#status.406">406 Not Acceptable</a></li> 652 <li><a href="#rfc.section.5.5.7">5.5.7</a> <a href="#status.408">408 Request Timeout</a></li> 653 <li><a href="#rfc.section.5.5.8">5.5.8</a> <a href="#status.409">409 Conflict</a></li> 654 <li><a href="#rfc.section.5.5.9">5.5.9</a> <a href="#status.410">410 Gone</a></li> 655 <li><a href="#rfc.section.5.5.10">5.5.10</a> <a href="#status.411">411 Length Required</a></li> 656 <li><a href="#rfc.section.5.5.11">5.5.11</a> <a href="#status.413">413 Request Representation Too Large</a></li> 657 <li><a href="#rfc.section.5.5.12">5.5.12</a> <a href="#status.414">414 URI Too Long</a></li> 658 <li><a href="#rfc.section.5.5.13">5.5.13</a> <a href="#status.415">415 Unsupported Media Type</a></li> 659 <li><a href="#rfc.section.5.5.14">5.5.14</a> <a href="#status.417">417 Expectation Failed</a></li> 660 <li><a href="#rfc.section.5.5.15">5.5.15</a> <a href="#status.426">426 Upgrade Required</a></li> 647 661 </ul> 648 662 </li> 649 <li><a href="#rfc.section.5.6">5.6</a> <a href="#status.4xx">Client Error 4xx</a><ul> 650 <li><a href="#rfc.section.5.6.1">5.6.1</a> <a href="#status.400">400 Bad Request</a></li> 651 <li><a href="#rfc.section.5.6.2">5.6.2</a> <a href="#status.402">402 Payment Required</a></li> 652 <li><a href="#rfc.section.5.6.3">5.6.3</a> <a href="#status.403">403 Forbidden</a></li> 653 <li><a href="#rfc.section.5.6.4">5.6.4</a> <a href="#status.404">404 Not Found</a></li> 654 <li><a href="#rfc.section.5.6.5">5.6.5</a> <a href="#status.405">405 Method Not Allowed</a></li> 655 <li><a href="#rfc.section.5.6.6">5.6.6</a> <a href="#status.406">406 Not Acceptable</a></li> 656 <li><a href="#rfc.section.5.6.7">5.6.7</a> <a href="#status.408">408 Request Timeout</a></li> 657 <li><a href="#rfc.section.5.6.8">5.6.8</a> <a href="#status.409">409 Conflict</a></li> 658 <li><a href="#rfc.section.5.6.9">5.6.9</a> <a href="#status.410">410 Gone</a></li> 659 <li><a href="#rfc.section.5.6.10">5.6.10</a> <a href="#status.411">411 Length Required</a></li> 660 <li><a href="#rfc.section.5.6.11">5.6.11</a> <a href="#status.413">413 Request Representation Too Large</a></li> 661 <li><a href="#rfc.section.5.6.12">5.6.12</a> <a href="#status.414">414 URI Too Long</a></li> 662 <li><a href="#rfc.section.5.6.13">5.6.13</a> <a href="#status.415">415 Unsupported Media Type</a></li> 663 <li><a href="#rfc.section.5.6.14">5.6.14</a> <a href="#status.417">417 Expectation Failed</a></li> 664 <li><a href="#rfc.section.5.6.15">5.6.15</a> <a href="#status.426">426 Upgrade Required</a></li> 665 </ul> 666 </li> 667 <li><a href="#rfc.section.5.7">5.7</a> <a href="#status.5xx">Server Error 5xx</a><ul> 668 <li><a href="#rfc.section.5.7.1">5.7.1</a> <a href="#status.500">500 Internal Server Error</a></li> 669 <li><a href="#rfc.section.5.7.2">5.7.2</a> <a href="#status.501">501 Not Implemented</a></li> 670 <li><a href="#rfc.section.5.7.3">5.7.3</a> <a href="#status.502">502 Bad Gateway</a></li> 671 <li><a href="#rfc.section.5.7.4">5.7.4</a> <a href="#status.503">503 Service Unavailable</a></li> 672 <li><a href="#rfc.section.5.7.5">5.7.5</a> <a href="#status.504">504 Gateway Timeout</a></li> 673 <li><a href="#rfc.section.5.7.6">5.7.6</a> <a href="#status.505">505 HTTP Version Not Supported</a></li> 663 <li><a href="#rfc.section.5.6">5.6</a> <a href="#status.5xx">Server Error 5xx</a><ul> 664 <li><a href="#rfc.section.5.6.1">5.6.1</a> <a href="#status.500">500 Internal Server Error</a></li> 665 <li><a href="#rfc.section.5.6.2">5.6.2</a> <a href="#status.501">501 Not Implemented</a></li> 666 <li><a href="#rfc.section.5.6.3">5.6.3</a> <a href="#status.502">502 Bad Gateway</a></li> 667 <li><a href="#rfc.section.5.6.4">5.6.4</a> <a href="#status.503">503 Service Unavailable</a></li> 668 <li><a href="#rfc.section.5.6.5">5.6.5</a> <a href="#status.504">504 Gateway Timeout</a></li> 669 <li><a href="#rfc.section.5.6.6">5.6.6</a> <a href="#status.505">505 HTTP Version Not Supported</a></li> 674 670 </ul> 675 671 </li> … … 680 676 <li><a href="#rfc.section.6.2">6.2</a> <a href="#product.tokens">Product Tokens</a></li> 681 677 <li><a href="#rfc.section.6.3">6.3</a> <a href="#character.sets">Character Encodings (charset)</a></li> 682 <li><a href="#rfc.section.6.4">6.4</a> <a href="#content.codings">Content Codings</a><ul> 683 <li><a href="#rfc.section.6.4.1">6.4.1</a> <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> <a href="#content.codings">Content Codings</a></li> 686 679 <li><a href="#rfc.section.6.5">6.5</a> <a href="#media.types">Media Types</a><ul> 687 680 <li><a href="#rfc.section.6.5.1">6.5.1</a> <a href="#canonicalization.and.text.defaults">Canonicalization and Text Defaults</a></li> … … 732 725 <li><a href="#rfc.section.11">11.</a> <a href="#IANA.considerations">IANA Considerations</a><ul> 733 726 <li><a href="#rfc.section.11.1">11.1</a> <a href="#method.registry">Method Registry</a><ul> 734 <li><a href="#rfc.section.11.1.1">11.1.1</a> <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> <a href="#method.registration">Registrations</a></li> 727 <li><a href="#rfc.section.11.1.1">11.1.1</a> <a href="#method.procedure">Procedure</a></li> 728 <li><a href="#rfc.section.11.1.2">11.1.2</a> <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> <a href="#method.registration">Registrations</a></li> 736 730 </ul> 737 731 </li> 738 <li><a href="#rfc.section.11.2">11.2</a> <a href="#status.code.registration">Status Code Registry</a></li> 732 <li><a href="#rfc.section.11.2">11.2</a> <a href="#status.code.registry">Status Code Registry</a><ul> 733 <li><a href="#rfc.section.11.2.1">11.2.1</a> <a href="#status.code.procedure">Procedure</a></li> 734 <li><a href="#rfc.section.11.2.2">11.2.2</a> <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> <a href="#status.code.registration">Registrations</a></li> 736 </ul> 737 </li> 739 738 <li><a href="#rfc.section.11.3">11.3</a> <a href="#header.field.registration">Header Field Registration</a></li> 740 <li><a href="#rfc.section.11.4">11.4</a> <a href="#content.coding.registration">Content Coding Registry</a></li> 739 <li><a href="#rfc.section.11.4">11.4</a> <a href="#content.coding.registry">Content Coding Registry</a><ul> 740 <li><a href="#rfc.section.11.4.1">11.4.1</a> <a href="#content.coding.procedure">Procedure</a></li> 741 <li><a href="#rfc.section.11.4.2">11.4.2</a> <a href="#content.coding.registration">Registrations</a></li> 742 </ul> 743 </li> 741 744 </ul> 742 745 </li> … … 1459 1462 <td class="left">100</td> 1460 1463 <td class="left">Continue</td> 1461 <td class="left"><a href="#status.100" id="rfc.xref.status.100.1" title="100 Continue">Section 5. 3.1</a></td>1464 <td class="left"><a href="#status.100" id="rfc.xref.status.100.1" title="100 Continue">Section 5.2.1</a></td> 1462 1465 </tr> 1463 1466 <tr> 1464 1467 <td class="left">101</td> 1465 1468 <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 5. 3.2</a></td>1469 <td class="left"><a href="#status.101" id="rfc.xref.status.101.1" title="101 Switching Protocols">Section 5.2.2</a></td> 1467 1470 </tr> 1468 1471 <tr> 1469 1472 <td class="left">200</td> 1470 1473 <td class="left">OK</td> 1471 <td class="left"><a href="#status.200" id="rfc.xref.status.200.1" title="200 OK">Section 5. 4.1</a></td>1474 <td class="left"><a href="#status.200" id="rfc.xref.status.200.1" title="200 OK">Section 5.3.1</a></td> 1472 1475 </tr> 1473 1476 <tr> 1474 1477 <td class="left">201</td> 1475 1478 <td class="left">Created</td> 1476 <td class="left"><a href="#status.201" id="rfc.xref.status.201.1" title="201 Created">Section 5. 4.2</a></td>1479 <td class="left"><a href="#status.201" id="rfc.xref.status.201.1" title="201 Created">Section 5.3.2</a></td> 1477 1480 </tr> 1478 1481 <tr> 1479 1482 <td class="left">202</td> 1480 1483 <td class="left">Accepted</td> 1481 <td class="left"><a href="#status.202" id="rfc.xref.status.202.1" title="202 Accepted">Section 5. 4.3</a></td>1484 <td class="left"><a href="#status.202" id="rfc.xref.status.202.1" title="202 Accepted">Section 5.3.3</a></td> 1482 1485 </tr> 1483 1486 <tr> 1484 1487 <td class="left">203</td> 1485 1488 <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 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 5.3.4</a></td> 1487 1490 </tr> 1488 1491 <tr> 1489 1492 <td class="left">204</td> 1490 1493 <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 5. 4.5</a></td>1494 <td class="left"><a href="#status.204" id="rfc.xref.status.204.1" title="204 No Content">Section 5.3.5</a></td> 1492 1495 </tr> 1493 1496 <tr> 1494 1497 <td class="left">205</td> 1495 1498 <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 5. 4.6</a></td>1499 <td class="left"><a href="#status.205" id="rfc.xref.status.205.1" title="205 Reset Content">Section 5.3.6</a></td> 1497 1500 </tr> 1498 1501 <tr> … … 1504 1507 <td class="left">300</td> 1505 1508 <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 5. 5.1</a></td>1509 <td class="left"><a href="#status.300" id="rfc.xref.status.300.1" title="300 Multiple Choices">Section 5.4.1</a></td> 1507 1510 </tr> 1508 1511 <tr> 1509 1512 <td class="left">301</td> 1510 1513 <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 5. 5.2</a></td>1514 <td class="left"><a href="#status.301" id="rfc.xref.status.301.1" title="301 Moved Permanently">Section 5.4.2</a></td> 1512 1515 </tr> 1513 1516 <tr> 1514 1517 <td class="left">302</td> 1515 1518 <td class="left">Found</td> 1516 <td class="left"><a href="#status.302" id="rfc.xref.status.302.1" title="302 Found">Section 5. 5.3</a></td>1519 <td class="left"><a href="#status.302" id="rfc.xref.status.302.1" title="302 Found">Section 5.4.3</a></td> 1517 1520 </tr> 1518 1521 <tr> 1519 1522 <td class="left">303</td> 1520 1523 <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 5. 5.4</a></td>1524 <td class="left"><a href="#status.303" id="rfc.xref.status.303.1" title="303 See Other">Section 5.4.4</a></td> 1522 1525 </tr> 1523 1526 <tr> … … 1529 1532 <td class="left">305</td> 1530 1533 <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 5. 5.5</a></td>1534 <td class="left"><a href="#status.305" id="rfc.xref.status.305.1" title="305 Use Proxy">Section 5.4.5</a></td> 1532 1535 </tr> 1533 1536 <tr> 1534 1537 <td class="left">307</td> 1535 1538 <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 5. 5.7</a></td>1539 <td class="left"><a href="#status.307" id="rfc.xref.status.307.1" title="307 Temporary Redirect">Section 5.4.7</a></td> 1537 1540 </tr> 1538 1541 <tr> 1539 1542 <td class="left">400</td> 1540 1543 <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 5. 6.1</a></td>1544 <td class="left"><a href="#status.400" id="rfc.xref.status.400.1" title="400 Bad Request">Section 5.5.1</a></td> 1542 1545 </tr> 1543 1546 <tr> … … 1549 1552 <td class="left">402</td> 1550 1553 <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 5. 6.2</a></td>1554 <td class="left"><a href="#status.402" id="rfc.xref.status.402.1" title="402 Payment Required">Section 5.5.2</a></td> 1552 1555 </tr> 1553 1556 <tr> 1554 1557 <td class="left">403</td> 1555 1558 <td class="left">Forbidden</td> 1556 <td class="left"><a href="#status.403" id="rfc.xref.status.403.1" title="403 Forbidden">Section 5. 6.3</a></td>1559 <td class="left"><a href="#status.403" id="rfc.xref.status.403.1" title="403 Forbidden">Section 5.5.3</a></td> 1557 1560 </tr> 1558 1561 <tr> 1559 1562 <td class="left">404</td> 1560 1563 <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 5. 6.4</a></td>1564 <td class="left"><a href="#status.404" id="rfc.xref.status.404.1" title="404 Not Found">Section 5.5.4</a></td> 1562 1565 </tr> 1563 1566 <tr> 1564 1567 <td class="left">405</td> 1565 1568 <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 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 5.5.5</a></td> 1567 1570 </tr> 1568 1571 <tr> 1569 1572 <td class="left">406</td> 1570 1573 <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 5. 6.6</a></td>1574 <td class="left"><a href="#status.406" id="rfc.xref.status.406.1" title="406 Not Acceptable">Section 5.5.6</a></td> 1572 1575 </tr> 1573 1576 <tr> … … 1579 1582 <td class="left">408</td> 1580 1583 <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 5. 6.7</a></td>1584 <td class="left"><a href="#status.408" id="rfc.xref.status.408.1" title="408 Request Timeout">Section 5.5.7</a></td> 1582 1585 </tr> 1583 1586 <tr> 1584 1587 <td class="left">409</td> 1585 1588 <td class="left">Conflict</td> 1586 <td class="left"><a href="#status.409" id="rfc.xref.status.409.1" title="409 Conflict">Section 5. 6.8</a></td>1589 <td class="left"><a href="#status.409" id="rfc.xref.status.409.1" title="409 Conflict">Section 5.5.8</a></td> 1587 1590 </tr> 1588 1591 <tr> 1589 1592 <td class="left">410</td> 1590 1593 <td class="left">Gone</td> 1591 <td class="left"><a href="#status.410" id="rfc.xref.status.410.1" title="410 Gone">Section 5. 6.9</a></td>1594 <td class="left"><a href="#status.410" id="rfc.xref.status.410.1" title="410 Gone">Section 5.5.9</a></td> 1592 1595 </tr> 1593 1596 <tr> 1594 1597 <td class="left">411</td> 1595 1598 <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 5. 6.10</a></td>1599 <td class="left"><a href="#status.411" id="rfc.xref.status.411.1" title="411 Length Required">Section 5.5.10</a></td> 1597 1600 </tr> 1598 1601 <tr> … … 1604 1607 <td class="left">413</td> 1605 1608 <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 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 5.5.11</a></td> 1607 1610 </tr> 1608 1611 <tr> 1609 1612 <td class="left">414</td> 1610 1613 <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 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 5.5.12</a></td> 1612 1615 </tr> 1613 1616 <tr> 1614 1617 <td class="left">415</td> 1615 1618 <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 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 5.5.13</a></td> 1617 1620 </tr> 1618 1621 <tr> … … 1624 1627 <td class="left">417</td> 1625 1628 <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 5. 6.14</a></td>1629 <td class="left"><a href="#status.417" id="rfc.xref.status.417.1" title="417 Expectation Failed">Section 5.5.14</a></td> 1627 1630 </tr> 1628 1631 <tr> 1629 1632 <td class="left">426</td> 1630 1633 <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 5. 6.15</a></td>1634 <td class="left"><a href="#status.426" id="rfc.xref.status.426.1" title="426 Upgrade Required">Section 5.5.15</a></td> 1632 1635 </tr> 1633 1636 <tr> 1634 1637 <td class="left">500</td> 1635 1638 <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 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 5.6.1</a></td> 1637 1640 </tr> 1638 1641 <tr> 1639 1642 <td class="left">501</td> 1640 1643 <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 5. 7.2</a></td>1644 <td class="left"><a href="#status.501" id="rfc.xref.status.501.1" title="501 Not Implemented">Section 5.6.2</a></td> 1642 1645 </tr> 1643 1646 <tr> 1644 1647 <td class="left">502</td> 1645 1648 <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 5. 7.3</a></td>1649 <td class="left"><a href="#status.502" id="rfc.xref.status.502.1" title="502 Bad Gateway">Section 5.6.3</a></td> 1647 1650 </tr> 1648 1651 <tr> 1649 1652 <td class="left">503</td> 1650 1653 <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 5. 7.4</a></td>1654 <td class="left"><a href="#status.503" id="rfc.xref.status.503.1" title="503 Service Unavailable">Section 5.6.4</a></td> 1652 1655 </tr> 1653 1656 <tr> 1654 1657 <td class="left">504</td> 1655 1658 <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 5. 7.5</a></td>1659 <td class="left"><a href="#status.504" id="rfc.xref.status.504.1" title="504 Gateway Timeout">Section 5.6.5</a></td> 1657 1660 </tr> 1658 1661 <tr> 1659 1662 <td class="left">505</td> 1660 1663 <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 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 5.6.6</a></td> 1662 1665 </tr> 1663 1666 </tbody> … … 1665 1668 </div> 1666 1669 <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> <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 <<a href="http://www.iana.org/assignments/http-status-codes">http://www.iana.org/assignments/http-status-codes</a>>. 1672 </p> 1673 <h3 id="rfc.section.5.2.1"><a href="#rfc.section.5.2.1">5.2.1</a> <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 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 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> <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> <a id="status.1xx" href="#status.1xx">Informational 1xx</a></h2> 1691 1671 <div id="rfc.iref.21"></div> 1692 1672 <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, 1694 1674 and is terminated by an empty line. There are no required header fields for this class of status code. Since HTTP/1.0 did 1695 1675 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. 1696 1676 </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">1001677 <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 1698 1678 (Continue)</a> status message. Unexpected 1xx status responses <em class="bcp14">MAY</em> be ignored by a user agent. 1699 1679 </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 itself1680 <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 1701 1681 requested the generation of the 1xx response. (For example, if a proxy adds an "Expect: 100-continue" field when it forwards 1702 1682 a request, then it need not forward the corresponding <a href="#status.100" class="smpl">100 (Continue)</a> response(s).) … … 1704 1684 <div id="rfc.iref.22"></div> 1705 1685 <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> <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 been1686 <h3 id="rfc.section.5.2.1"><a href="#rfc.section.5.2.1">5.2.1</a> <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 1708 1688 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 1709 1689 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"">[Part1]</cite></a> for detailed discussion of the use and handling of this status code. … … 1711 1691 <div id="rfc.iref.23"></div> 1712 1692 <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> <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"">[Part1]</cite></a>), for a change in the application protocol being used on this connection. The server will switch protocols to those defined1693 <h3 id="rfc.section.5.2.2"><a href="#rfc.section.5.2.2">5.2.2</a> <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"">[Part1]</cite></a>), for a change in the application protocol being used on this connection. The server will switch protocols to those defined 1715 1695 by the response's Upgrade header field immediately after the empty line which terminates the 101 response. 1716 1696 </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 over1697 <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 1718 1698 older versions, and switching to a real-time, synchronous protocol might be advantageous when delivering resources that use 1719 1699 such features. 1720 1700 </p> 1721 <h2 id="rfc.section.5. 4"><a href="#rfc.section.5.4">5.4</a> <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> <a id="status.2xx" href="#status.2xx">Successful 2xx</a></h2> 1722 1702 <div id="rfc.iref.24"></div> 1723 1703 <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> 1725 1705 <div id="rfc.iref.25"></div> 1726 1706 <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> <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> <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> 1729 1709 <dl> 1730 1710 <dt>GET</dt> … … 1737 1717 <dd>a representation containing the request message as received by the end server.</dd> 1738 1718 </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. 1740 1720 </p> 1741 1721 <div id="rfc.iref.26"></div> 1742 1722 <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> <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 in1723 <h3 id="rfc.section.5.3.2"><a href="#rfc.section.5.3.2">5.3.2</a> <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 1746 1726 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 1747 1727 (e.g., in the case of a response to a PUT request). 1748 1728 </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 by1729 <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 1752 1732 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>). 1753 1733 </p> 1754 1734 <div id="rfc.iref.27"></div> 1755 1735 <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> <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 eventually1736 <h3 id="rfc.section.5.3.3"><a href="#rfc.section.5.3.3">5.3.3</a> <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 1758 1738 be acted upon, as it might be disallowed when processing actually takes place. There is no facility for re-sending a status 1759 1739 code from an asynchronous operation such as this. 1760 1740 </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 process1741 <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 1762 1742 (perhaps a batch-oriented process that is only run once per day) without requiring that the user agent's connection to the 1763 1743 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 … … 1766 1746 <div id="rfc.iref.28"></div> 1767 1747 <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> <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"">[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-code1772 (<a href="p6-cache.html#header.warning" title="Warning">Section 7.6</a> of <a href="#Part6" id="rfc.xref.Part6.1 3"><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> <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"">[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. 1775 1755 </p> 1776 1756 <div id="rfc.iref.29"></div> 1777 1757 <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> <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 additional1758 <h3 id="rfc.section.5.3.5"><a href="#rfc.section.5.3.5">5.3.5</a> <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 1780 1760 content to return in the response payload body. Metadata in the response header fields refer to the target resource and its 1781 1761 current representation after the requested action. 1782 1762 </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 that1763 <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 1784 1764 target resource. 1785 1765 </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 implying1766 <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 1787 1767 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 1788 1768 of the success to its user, in accord with its own interface, and apply any new or updated metadata in the response to the 1789 1769 active representation. 1790 1770 </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 that1771 <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 1792 1772 the document being saved remains available to the user for editing. It is also frequently used with interfaces that expect 1793 1773 automated data transfers to be prevalent, such as within distributed version control systems. 1794 1774 </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. 1796 1776 </p> 1797 1777 <div id="rfc.iref.30"></div> 1798 1778 <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> <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 actions1779 <h3 id="rfc.section.5.3.6"><a href="#rfc.section.5.3.6">5.3.6</a> <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 1801 1781 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 1802 1782 another input action. 1803 1783 </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"">[Part1]</cite></a>.1805 </p> 1806 <h2 id="rfc.section.5. 5"><a href="#rfc.section.5.5">5.5</a> <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"">[Part1]</cite></a>. 1785 </p> 1786 <h2 id="rfc.section.5.4"><a href="#rfc.section.5.4">5.4</a> <a id="status.3xx" href="#status.3xx">Redirection 3xx</a></h2> 1807 1787 <div id="rfc.iref.31"></div> 1808 1788 <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. 1810 1790 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 1811 1791 known to be "safe", as defined in <a href="#safe.methods" title="Safe Methods">Section 3.2.1</a>. 1812 1792 </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> 1814 1794 <ol> 1815 1795 <li> … … 1834 1814 </li> 1835 1815 </ol> 1836 <div class="note" id="rfc.section.5. 5.p.3">1816 <div class="note" id="rfc.section.5.4.p.3"> 1837 1817 <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 1838 1818 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 … … 1840 1820 </p> 1841 1821 </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 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 3.2.1</a>, automatic redirection needs to done with care, since the redirect might change the conditions under which the request was1822 <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 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 3.2.1</a>, automatic redirection needs to done with care, since the redirect might change the conditions under which the request was 1845 1825 issued. 1846 1826 </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"> 1850 1830 <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. 1851 1831 </p> … … 1853 1833 <div id="rfc.iref.32"></div> 1854 1834 <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> <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 information1835 <h3 id="rfc.section.5.4.1"><a href="#rfc.section.5.4.1">5.4.1</a> <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 1857 1837 (<a href="#content.negotiation" title="Content Negotiation">Section 9</a>) is being provided so that the user (or user agent) can select a preferred representation by redirecting its request to that 1858 1838 location. 1859 1839 </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 can1840 <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 1861 1841 choose the one most appropriate. Depending upon the format and the capabilities of the user agent, selection of the most appropriate 1862 1842 choice <em class="bcp14">MAY</em> be performed automatically. However, this specification does not define any standard for such automatic selection. 1863 1843 </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. 1867 1847 </p> 1868 1848 <div id="rfc.iref.33"></div> 1869 1849 <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> <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 effective1850 <h3 id="rfc.section.5.4.2"><a href="#rfc.section.5.4.2">5.4.2</a> <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 1872 1852 request URI to one or more of the new references returned by the server, where possible. 1873 1853 </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"> 1879 1859 <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. 1880 1860 </p> … … 1882 1862 <div id="rfc.iref.34"></div> 1883 1863 <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> <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> <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"> 1890 1870 <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. 1891 1871 </p> … … 1893 1873 <div id="rfc.iref.35"></div> 1894 1874 <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> <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 URI1875 <h3 id="rfc.section.5.4.4"><a href="#rfc.section.5.4.4">5.4.4</a> <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 1897 1877 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, 1898 1878 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, … … 1900 1880 not considered equivalent to the effective request URI. 1901 1881 </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 to1882 <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 1903 1883 redirect the user agent to a selected resource, since doing so provides the information corresponding to the POST response 1904 1884 in a form that can be separately identified, bookmarked, and cached independent of the original request. 1905 1885 </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 be1886 <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 1907 1887 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 1908 1888 to recipients without implying that it adequately represents the target resource. Note that answers to the questions of what … … 1910 1890 and thus entirely determined by the URI owner(s). 1911 1891 </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. 1913 1893 </p> 1914 1894 <div id="rfc.iref.36"></div> 1915 1895 <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> <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 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> <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 C</a>), and is now deprecated. 1918 1898 </p> 1919 1899 <div id="rfc.iref.37"></div> 1920 1900 <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> <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> <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> 1923 1903 <div id="rfc.iref.38"></div> 1924 1904 <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> <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> <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"> 1931 1911 <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 1932 1912 for <a href="#status.301" class="smpl">301 (Moved … … 1934 1914 </p> 1935 1915 </div> 1936 <h2 id="rfc.section.5. 6"><a href="#rfc.section.5.6">5.6</a> <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> <a id="status.4xx" href="#status.4xx">Client Error 4xx</a></h2> 1937 1917 <div id="rfc.iref.39"></div> 1938 1918 <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 HEAD1919 <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 1940 1920 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. 1941 1921 These status codes are applicable to any request method. User agents <em class="bcp14">SHOULD</em> display any included representation to the user. … … 1943 1923 <div id="rfc.iref.40"></div> 1944 1924 <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> <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> <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> 1947 1927 <div id="rfc.iref.41"></div> 1948 1928 <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> <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> <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> 1951 1931 <div id="rfc.iref.42"></div> 1952 1932 <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> <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 might1933 <h3 id="rfc.section.5.5.3"><a href="#rfc.section.5.5.3">5.5.3</a> <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 1955 1935 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. 1956 1936 </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 available1937 <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 1958 1938 to the client, the status code <a href="#status.404" class="smpl">404 1959 1939 (Not Found)</a> <em class="bcp14">MAY</em> be used instead. … … 1961 1941 <div id="rfc.iref.43"></div> 1962 1942 <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> <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 temporary1943 <h3 id="rfc.section.5.5.4"><a href="#rfc.section.5.5.4">5.5.4</a> <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 1965 1945 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 1966 1946 and has no forwarding address. This status code is commonly used when the server does not wish to reveal exactly why the request … … 1969 1949 <div id="rfc.iref.44"></div> 1970 1950 <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> <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> <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. 1973 1953 </p> 1974 1954 <div id="rfc.iref.45"></div> 1975 1955 <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> <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 characteristics1956 <h3 id="rfc.section.5.5.6"><a href="#rfc.section.5.5.6">5.5.6</a> <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 1978 1958 not acceptable according to the <a href="#header.accept" class="smpl">Accept</a> and Accept-* header fields sent in the request. 1979 1959 </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 user1960 <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 1981 1961 or user agent can choose the one most appropriate. Depending upon the format and the capabilities of the user agent, selection 1982 1962 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. 1983 1963 </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"> 1985 1965 <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 1986 1966 request. In some cases, this might even be preferable to sending a 406 response. User agents are encouraged to inspect the … … 1988 1968 </p> 1989 1969 </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. 1991 1971 </p> 1992 1972 <div id="rfc.iref.46"></div> 1993 1973 <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> <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> <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. 1996 1976 </p> 1997 1977 <div id="rfc.iref.47"></div> 1998 1978 <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> <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 in1979 <h3 id="rfc.section.5.5.8"><a href="#rfc.section.5.5.8">5.5.8</a> <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 2001 1981 situations where it is expected that the user might be able to resolve the conflict and resubmit the request. The response 2002 1982 body <em class="bcp14">SHOULD</em> include enough information for the user to recognize the source of the conflict. Ideally, the response representation would 2003 1983 include enough information for the user or user agent to fix the problem; however, that might not be possible and is not required. 2004 1984 </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 representation1985 <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 2006 1986 being PUT included changes to a resource which conflict with those made by an earlier (third-party) request, the server might 2007 1987 use the 409 response to indicate that it can't complete the request. In this case, the response representation would likely … … 2010 1990 <div id="rfc.iref.48"></div> 2011 1991 <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> <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 to1992 <h3 id="rfc.section.5.5.9"><a href="#rfc.section.5.5.9">5.5.9</a> <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 2014 1994 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, 2015 1995 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. 2016 1996 </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 resource1997 <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 2018 1998 is intentionally unavailable and that the server owners desire that remote links to that resource be removed. Such an event 2019 1999 is common for limited-time, promotional services and for resources belonging to individuals no longer working at the server's … … 2021 2001 — that is left to the discretion of the server owner. 2022 2002 </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. 2024 2004 </p> 2025 2005 <div id="rfc.iref.49"></div> 2026 2006 <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> <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 request2007 <h3 id="rfc.section.5.5.10"><a href="#rfc.section.5.5.10">5.5.10</a> <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 2029 2009 message. 2030 2010 </p> 2031 2011 <div id="rfc.iref.50"></div> 2032 2012 <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> <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 able2013 <h3 id="rfc.section.5.5.11"><a href="#rfc.section.5.5.11">5.5.11</a> <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 2035 2015 to process. The server <em class="bcp14">MAY</em> close the connection to prevent the client from continuing the request. 2036 2016 </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. 2038 2018 </p> 2039 2019 <div id="rfc.iref.51"></div> 2040 2020 <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> <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> <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. 2043 2023 This rare condition is only likely to occur when a client has improperly converted a POST request to a GET request with long 2044 2024 query information, when the client has descended into a URI "black hole" of redirection (e.g., a redirected URI prefix that … … 2048 2028 <div id="rfc.iref.52"></div> 2049 2029 <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> <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 method2030 <h3 id="rfc.section.5.5.13"><a href="#rfc.section.5.5.13">5.5.13</a> <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 2052 2032 on the target resource. 2053 2033 </p> 2054 2034 <div id="rfc.iref.53"></div> 2055 2035 <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> <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 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 could2036 <h3 id="rfc.section.5.5.14"><a href="#rfc.section.5.5.14">5.5.14</a> <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 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 2058 2038 not be met by the next-hop server. 2059 2039 </p> 2060 2040 <div id="rfc.iref.54"></div> 2061 2041 <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> <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"">[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> <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"">[Part1]</cite></a>) specifying the required protocols. 2064 2044 </p> 2065 2045 <div id="rfc.figure.u.5"></div> … … 2071 2051 2072 2052 <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 any2053 </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 2074 2054 alternative courses which might be available to the user. 2075 2055 </p> 2076 <h2 id="rfc.section.5. 7"><a href="#rfc.section.5.7">5.7</a> <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> <a id="status.5xx" href="#status.5xx">Server Error 5xx</a></h2> 2077 2057 <div id="rfc.iref.55"></div> 2078 2058 <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 incapable2059 <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 2080 2060 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. 2081 2061 User agents <em class="bcp14">SHOULD</em> display any included representation to the user. These response codes are applicable to any request method. … … 2083 2063 <div id="rfc.iref.56"></div> 2084 2064 <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> <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> <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> 2087 2067 <div id="rfc.iref.57"></div> 2088 2068 <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> <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 server2069 <h3 id="rfc.section.5.6.2"><a href="#rfc.section.5.6.2">5.6.2</a> <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 2091 2071 does not recognize the request method and is not capable of supporting it for any resource. 2092 2072 </p> 2093 2073 <div id="rfc.iref.58"></div> 2094 2074 <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> <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 attempting2075 <h3 id="rfc.section.5.6.3"><a href="#rfc.section.5.6.3">5.6.3</a> <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 2097 2077 to fulfill the request. 2098 2078 </p> 2099 2079 <div id="rfc.iref.59"></div> 2100 2080 <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> <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 the2081 <h3 id="rfc.section.5.6.4"><a href="#rfc.section.5.6.4">5.6.4</a> <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 2104 2084 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 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 2105 2085 Server Error)</a> response. 2106 2086 </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"> 2108 2088 <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 2109 2089 wish to simply refuse the connection. … … 2112 2092 <div id="rfc.iref.60"></div> 2113 2093 <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> <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 the2094 <h3 id="rfc.section.5.6.5"><a href="#rfc.section.5.6.5">5.6.5</a> <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 2116 2096 URI (e.g., HTTP, FTP, LDAP) or some other auxiliary server (e.g., DNS) it needed to access in attempting to complete the request. 2117 2097 </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"> 2119 2099 <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 2120 2100 Error)</a> when DNS lookups time out. … … 2123 2103 <div id="rfc.iref.61"></div> 2124 2104 <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> <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 server2105 <h3 id="rfc.section.5.6.6"><a href="#rfc.section.5.6.6">5.6.6</a> <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 2127 2107 is indicating that it is unable or unwilling to complete the request using the same major version as the client, as described 2128 2108 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"">[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. … … 2270 2250 </li> 2271 2251 </ul> 2272 <h3 id="rfc.section.6.4.1"><a href="#rfc.section.6.4.1">6.4.1</a> <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"">[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"">[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 <<a href="http://www.iana.org/assignments/http-parameters">http://www.iana.org/assignments/http-parameters</a>>.2286 </p>2287 2252 <h2 id="rfc.section.6.5"><a href="#rfc.section.6.5">6.5</a> <a id="media.types" href="#media.types">Media Types</a></h2> 2288 2253 <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 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 10.1</a>) header fields in order to provide open and extensible data typing and type negotiation. … … 2378 2343 <tr> 2379 2344 <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"">[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"">[Part1]</cite></a></td> 2381 2346 </tr> 2382 2347 <tr> … … 2388 2353 </div> 2389 2354 <h2 id="rfc.section.7.2"><a href="#rfc.section.7.2">7.2</a> <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.3 2"><cite title="HTTP/1.1, part 1: Message Routing and Syntax"">[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"">[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. 2391 2356 </p> 2392 2357 <div id="rfc.iref.r.1"></div> … … 2407 2372 in an HTTP message, it is referred to as the payload of the message. 2408 2373 </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.3 3"><cite title="HTTP/1.1, part 1: Message Routing and Syntax"">[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"">[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. 2410 2375 </p> 2411 2376 <h2 id="rfc.section.8.1"><a href="#rfc.section.8.1">8.1</a> <a id="identifying.response.associated.with.representation" href="#identifying.response.associated.with.representation">Identifying the Resource Associated with a Representation</a></h2> 2412 2377 <p id="rfc.section.8.1.p.1">It is sometimes necessary to determine an identifier for the resource associated with a representation.</p> 2413 2378 <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.3 4"><cite title="HTTP/1.1, part 1: Message Routing and Syntax"">[Part1]</cite></a>). However, this is not always the case. To determine the URI of the resource a response is associated with, the following2379 <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"">[Part1]</cite></a>). However, this is not always the case. To determine the URI of the resource a response is associated with, the following 2415 2380 rules are used (with the first applicable one being selected): 2416 2381 </p> … … 2465 2430 <tr> 2466 2431 <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.1 8"><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> 2468 2433 </tr> 2469 2434 </tbody> … … 2581 2546 </p> 2582 2547 </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.1 9"><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. 2584 2549 </p> 2585 2550 <h2 id="rfc.section.9.2"><a href="#rfc.section.9.2">9.2</a> <a id="agent-driven.negotiation" href="#agent-driven.negotiation">Agent-driven Negotiation</a></h2> … … 2887 2852 </p> 2888 2853 <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.3 5"><cite title="HTTP/1.1, part 1: Message Routing and Syntax"">[Part1]</cite></a>). It is representation metadata. It has the same syntax and semantics as the header field of the same name defined for MIME2854 </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"">[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 2890 2855 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. 2891 2856 </p> … … 2981 2946 </p> 2982 2947 <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.3 6"><cite title="HTTP/1.1, part 1: Message Routing and Syntax"">[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"">[Part1]</cite></a>. It does not support any expect-params. 2984 2949 </li> 2985 2950 </ul> … … 3092 3057 <h2 id="rfc.section.10.17"><a href="#rfc.section.10.17">10.17</a> <a id="header.server" href="#header.server">Server</a></h2> 3093 3058 <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 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.3 7"><cite title="HTTP/1.1, part 1: Message Routing and Syntax"">[Part1]</cite></a>) identifying the server and any significant subproducts. The product tokens are listed in order of their significance for3059 <p id="rfc.section.10.17.p.2">The field can contain multiple product tokens (<a href="#product.tokens" title="Product Tokens">Section 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"">[Part1]</cite></a>) identifying the server and any significant subproducts. The product tokens are listed in order of their significance for 3095 3060 identifying the application. 3096 3061 </p> … … 3098 3063 </pre><p id="rfc.section.10.17.p.4">Example:</p> 3099 3064 <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.3 8"><cite title="HTTP/1.1, part 1: Message Routing and Syntax"">[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"">[Part1]</cite></a>). 3101 3066 </p> 3102 3067 <div class="note" id="rfc.section.10.17.p.7"> … … 3114 3079 user agent limitations. 3115 3080 </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 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.3 9"><cite title="HTTP/1.1, part 1: Message Routing and Syntax"">[Part1]</cite></a>) identifying the agent and its significant subproducts. By convention, the product tokens are listed in order of their significance3081 <p id="rfc.section.10.18.p.3">The field can contain multiple product tokens (<a href="#product.tokens" title="Product Tokens">Section 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"">[Part1]</cite></a>) identifying the agent and its significant subproducts. By convention, the product tokens are listed in order of their significance 3117 3082 for identifying the application. 3118 3083 </p> … … 3131 3096 <h2 id="rfc.section.11.1"><a href="#rfc.section.11.1">11.1</a> <a id="method.registry" href="#method.registry">Method Registry</a></h2> 3132 3097 <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> <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: 3134 3100 </p> 3135 3101 <ul> … … 3142 3108 <li>Pointer to specification text</li> 3143 3109 </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 <<a href="http://www.iana.org/assignments/http-methods">http://www.iana.org/assignments/http-methods</a>>.3147 </p> 3148 <h3 id="rfc.section.11.1. 1"><a href="#rfc.section.11.1.1">11.1.1</a> <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 media3110 <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 <<a href="http://www.iana.org/assignments/http-methods">http://www.iana.org/assignments/http-methods</a>>. 3113 </p> 3114 <h3 id="rfc.section.11.1.2"><a href="#rfc.section.11.1.2">11.1.2</a> <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 3150 3116 type, kind of resource, or application. As such, it is preferred that new HTTP methods be registered in a document that isn't 3151 3117 specific to a single application or data format, since orthogonal technologies deserve orthogonal specification. 3152 3118 </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"">[Part1]</cite></a>) is independent of method semantics (aside from responses to HEAD), definitions of new HTTP methods cannot change the parsing3119 <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"">[Part1]</cite></a>) is independent of method semantics (aside from responses to HEAD), definitions of new HTTP methods cannot change the parsing 3154 3120 algorithm or prohibit the presence of a message body on either the request or the response message. Definitions of new methods 3155 3121 can specify that only zero-length bodies are allowed, which would imply that each such messages would be required to contain 3156 3122 a Content-Length header field with a value of "0". 3157 3123 </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 3.2.1</a>), idempotent (<a href="#idempotent.methods" title="Idempotent Methods">Section 3.2.2</a>), or cacheable (<a href="#cacheable.methods" title="Cacheable Methods">Section 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 3.2.1</a>), idempotent (<a href="#idempotent.methods" title="Idempotent Methods">Section 3.2.2</a>), or cacheable (<a href="#cacheable.methods" title="Cacheable Methods">Section 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, 3159 3125 the method definition ought to describe how, and under what conditions, a cache can store a response and use it to satisfy 3160 3126 a subsequent request. 3161 3127 </p> 3162 <h3 id="rfc.section.11.1. 2"><a href="#rfc.section.11.1.2">11.1.2</a> <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 <<a href="http://www.iana.org/assignments/http-methods">http://www.iana.org/assignments/http-methods</a>> 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> <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 <<a href="http://www.iana.org/assignments/http-methods">http://www.iana.org/assignments/http-methods</a>> and be populated with the registrations below: 3164 3130 </p> 3165 3131 <div id="rfc.table.2"> … … 3234 3200 </table> 3235 3201 </div> 3236 <h2 id="rfc.section.11.2"><a href="#rfc.section.11.2">11.2</a> <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 5.2</a> of this document. 3238 </p> 3239 <p id="rfc.section.11.2.p.2">The HTTP Status Code Registry located at <<a href="http://www.iana.org/assignments/http-status-codes">http://www.iana.org/assignments/http-status-codes</a>> shall be updated with the registrations below: 3202 <h2 id="rfc.section.11.2"><a href="#rfc.section.11.2">11.2</a> <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 5</a>). 3204 </p> 3205 <h3 id="rfc.section.11.2.1"><a href="#rfc.section.11.2.1">11.2.1</a> <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 <<a href="http://www.iana.org/assignments/http-status-codes">http://www.iana.org/assignments/http-status-codes</a>>. 3209 </p> 3210 <h3 id="rfc.section.11.2.2"><a href="#rfc.section.11.2.2">11.2.2</a> <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 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 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> <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 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 <<a href="http://www.iana.org/assignments/http-status-codes">http://www.iana.org/assignments/http-status-codes</a>> shall be updated with the registrations below: 3240 3231 </p> 3241 3232 <div id="rfc.table.3"> … … 3253 3244 <td class="left">100</td> 3254 3245 <td class="left">Continue</td> 3255 <td class="left"> <a href="#status.100" id="rfc.xref.status.100.2" title="100 Continue">Section 5. 3.1</a>3246 <td class="left"> <a href="#status.100" id="rfc.xref.status.100.2" title="100 Continue">Section 5.2.1</a> 3256 3247 </td> 3257 3248 </tr> … … 3259 3250 <td class="left">101</td> 3260 3251 <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 5. 3.2</a>3252 <td class="left"> <a href="#status.101" id="rfc.xref.status.101.2" title="101 Switching Protocols">Section 5.2.2</a> 3262 3253 </td> 3263 3254 </tr> … … 3265 3256 <td class="left">200</td> 3266 3257 <td class="left">OK</td> 3267 <td class="left"> <a href="#status.200" id="rfc.xref.status.200.2" title="200 OK">Section 5. 4.1</a>3258 <td class="left"> <a href="#status.200" id="rfc.xref.status.200.2" title="200 OK">Section 5.3.1</a> 3268 3259 </td> 3269 3260 </tr> … … 3271 3262 <td class="left">201</td> 3272 3263 <td class="left">Created</td> 3273 <td class="left"> <a href="#status.201" id="rfc.xref.status.201.2" title="201 Created">Section 5. 4.2</a>3264 <td class="left"> <a href="#status.201" id="rfc.xref.status.201.2" title="201 Created">Section 5.3.2</a> 3274 3265 </td> 3275 3266 </tr> … … 3277 3268 <td class="left">202</td> 3278 3269 <td class="left">Accepted</td> 3279 <td class="left"> <a href="#status.202" id="rfc.xref.status.202.2" title="202 Accepted">Section 5. 4.3</a>3270 <td class="left"> <a href="#status.202" id="rfc.xref.status.202.2" title="202 Accepted">Section 5.3.3</a> 3280 3271 </td> 3281 3272 </tr> … … 3283 3274 <td class="left">203</td> 3284 3275 <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 5. 4.4</a>3276 <td class="left"> <a href="#status.203" id="rfc.xref.status.203.2" title="203 Non-Authoritative Information">Section 5.3.4</a> 3286 3277 </td> 3287 3278 </tr> … … 3289 3280 <td class="left">204</td> 3290 3281 <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 5. 4.5</a>3282 <td class="left"> <a href="#status.204" id="rfc.xref.status.204.2" title="204 No Content">Section 5.3.5</a> 3292 3283 </td> 3293 3284 </tr> … … 3295 3286 <td class="left">205</td> 3296 3287 <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 5. 4.6</a>3288 <td class="left"> <a href="#status.205" id="rfc.xref.status.205.2" title="205 Reset Content">Section 5.3.6</a> 3298 3289 </td> 3299 3290 </tr> … … 3301 3292 <td class="left">300</td> 3302 3293 <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 5. 5.1</a>3294 <td class="left"> <a href="#status.300" id="rfc.xref.status.300.2" title="300 Multiple Choices">Section 5.4.1</a> 3304 3295 </td> 3305 3296 </tr> … … 3307 3298 <td class="left">301</td> 3308 3299 <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 5. 5.2</a>3300 <td class="left"> <a href="#status.301" id="rfc.xref.status.301.2" title="301 Moved Permanently">Section 5.4.2</a> 3310 3301 </td> 3311 3302 </tr> … … 3313 3304 <td class="left">302</td> 3314 3305 <td class="left">Found</td> 3315 <td class="left"> <a href="#status.302" id="rfc.xref.status.302.2" title="302 Found">Section 5. 5.3</a>3306 <td class="left"> <a href="#status.302" id="rfc.xref.status.302.2" title="302 Found">Section 5.4.3</a> 3316 3307 </td> 3317 3308 </tr> … … 3319 3310 <td class="left">303</td> 3320 3311 <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 5. 5.4</a>3312 <td class="left"> <a href="#status.303" id="rfc.xref.status.303.2" title="303 See Other">Section 5.4.4</a> 3322 3313 </td> 3323 3314 </tr> … … 3325 3316 <td class="left">305</td> 3326 3317 <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 5. 5.5</a>3318 <td class="left"> <a href="#status.305" id="rfc.xref.status.305.2" title="305 Use Proxy">Section 5.4.5</a> 3328 3319 </td> 3329 3320 </tr> … … 3331 3322 <td class="left">306</td> 3332 3323 <td class="left">(Unused)</td> 3333 <td class="left"> <a href="#status.306" id="rfc.xref.status.306.1" title="306 (Unused)">Section 5. 5.6</a>3324 <td class="left"> <a href="#status.306" id="rfc.xref.status.306.1" title="306 (Unused)">Section 5.4.6</a> 3334 3325 </td> 3335 3326 </tr> … … 3337 3328 <td class="left">307</td> 3338 3329 <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 5. 5.7</a>3330 <td class="left"> <a href="#status.307" id="rfc.xref.status.307.2" title="307 Temporary Redirect">Section 5.4.7</a> 3340 3331 </td> 3341 3332 </tr> … … 3343 3334 <td class="left">400</td> 3344 3335 <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 5. 6.1</a>3336 <td class="left"> <a href="#status.400" id="rfc.xref.status.400.2" title="400 Bad Request">Section 5.5.1</a> 3346 3337 </td> 3347 3338 </tr> … … 3349 3340 <td class="left">402</td> 3350 3341 <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 5. 6.2</a>3342 <td class="left"> <a href="#status.402" id="rfc.xref.status.402.2" title="402 Payment Required">Section 5.5.2</a> 3352 3343 </td> 3353 3344 </tr> … … 3355 3346 <td class="left">403</td> 3356 3347 <td class="left">Forbidden</td> 3357 <td class="left"> <a href="#status.403" id="rfc.xref.status.403.2" title="403 Forbidden">Section 5. 6.3</a>3348 <td class="left"> <a href="#status.403" id="rfc.xref.status.403.2" title="403 Forbidden">Section 5.5.3</a> 3358 3349 </td> 3359 3350 </tr> … … 3361 3352 <td class="left">404</td> 3362 3353 <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 5. 6.4</a>3354 <td class="left"> <a href="#status.404" id="rfc.xref.status.404.2" title="404 Not Found">Section 5.5.4</a> 3364 3355 </td> 3365 3356 </tr> … … 3367 3358 <td class="left">405</td> 3368 3359 <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 5. 6.5</a>3360 <td class="left"> <a href="#status.405" id="rfc.xref.status.405.2" title="405 Method Not Allowed">Section 5.5.5</a> 3370 3361 </td> 3371 3362 </tr> … … 3373 3364 <td class="left">406</td> 3374 3365 <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 5. 6.6</a>3366 <td class="left"> <a href="#status.406" id="rfc.xref.status.406.2" title="406 Not Acceptable">Section 5.5.6</a> 3376 3367 </td> 3377 3368 </tr> … … 3379 3370 <td class="left">408</td> 3380 3371 <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 5. 6.7</a>3372 <td class="left"> <a href="#status.408" id="rfc.xref.status.408.2" title="408 Request Timeout">Section 5.5.7</a> 3382 3373 </td> 3383 3374 </tr> … … 3385 3376 <td class="left">409</td> 3386 3377 <td class="left">Conflict</td> 3387 <td class="left"> <a href="#status.409" id="rfc.xref.status.409.2" title="409 Conflict">Section 5. 6.8</a>3378 <td class="left"> <a href="#status.409" id="rfc.xref.status.409.2" title="409 Conflict">Section 5.5.8</a> 3388 3379 </td> 3389 3380 </tr> … … 3391 3382 <td class="left">410</td> 3392 3383 <td class="left">Gone</td> 3393 <td class="left"> <a href="#status.410" id="rfc.xref.status.410.2" title="410 Gone">Section 5. 6.9</a>3384 <td class="left"> <a href="#status.410" id="rfc.xref.status.410.2" title="410 Gone">Section 5.5.9</a> 3394 3385 </td> 3395 3386 </tr> … … 3397 3388 <td class="left">411</td> 3398 3389 <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 5. 6.10</a>3390 <td class="left"> <a href="#status.411" id="rfc.xref.status.411.2" title="411 Length Required">Section 5.5.10</a> 3400 3391 </td> 3401 3392 </tr> … … 3403 3394 <td class="left">413</td> 3404 3395 <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 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 5.5.11</a> 3406 3397 </td> 3407 3398 </tr> … … 3409 3400 <td class="left">414</td> 3410 3401 <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 5. 6.12</a>3402 <td class="left"> <a href="#status.414" id="rfc.xref.status.414.2" title="414 URI Too Long">Section 5.5.12</a> 3412 3403 </td> 3413 3404 </tr> … … 3415 3406 <td class="left">415</td> 3416 3407 <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 5. 6.13</a>3408 <td class="left"> <a href="#status.415" id="rfc.xref.status.415.2" title="415 Unsupported Media Type">Section 5.5.13</a> 3418 3409 </td> 3419 3410 </tr> … … 3421 3412 <td class="left">417</td> 3422 3413 <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 5. 6.14</a>3414 <td class="left"> <a href="#status.417" id="rfc.xref.status.417.2" title="417 Expectation Failed">Section 5.5.14</a> 3424 3415 </td> 3425 3416 </tr> … … 3427 3418 <td class="left">426</td> 3428 3419 <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 5. 6.15</a>3420 <td class="left"> <a href="#status.426" id="rfc.xref.status.426.2" title="426 Upgrade Required">Section 5.5.15</a> 3430 3421 </td> 3431 3422 </tr> … … 3433 3424 <td class="left">500</td> 3434 3425 <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 5. 7.1</a>3426 <td class="left"> <a href="#status.500" id="rfc.xref.status.500.2" title="500 Internal Server Error">Section 5.6.1</a> 3436 3427 </td> 3437 3428 </tr> … … 3439 3430 <td class="left">501</td> 3440 3431 <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 5. 7.2</a>3432 <td class="left"> <a href="#status.501" id="rfc.xref.status.501.2" title="501 Not Implemented">Section 5.6.2</a> 3442 3433 </td> 3443 3434 </tr> … … 3445 3436 <td class="left">502</td> 3446 3437 <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 5. 7.3</a>3438 <td class="left"> <a href="#status.502" id="rfc.xref.status.502.2" title="502 Bad Gateway">Section 5.6.3</a> 3448 3439 </td> 3449 3440 </tr> … … 3451 3442 <td class="left">503</td> 3452 3443 <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 5. 7.4</a>3444 <td class="left"> <a href="#status.503" id="rfc.xref.status.503.2" title="503 Service Unavailable">Section 5.6.4</a> 3454 3445 </td> 3455 3446 </tr> … … 3457 3448 <td class="left">504</td> 3458 3449 <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 5. 7.5</a>3450 <td class="left"> <a href="#status.504" id="rfc.xref.status.504.2" title="504 Gateway Timeout">Section 5.6.5</a> 3460 3451 </td> 3461 3452 </tr> … … 3463 3454 <td class="left">505</td> 3464 3455 <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 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 5.6.6</a> 3466 3457 </td> 3467 3458 </tr> … … 3621 3612 </div> 3622 3613 <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> <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 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 <<a href="http://www.iana.org/assignments/http-parameters">http://www.iana.org/assignments/http-parameters</a>> shall be updated with the registration below: 3614 <h2 id="rfc.section.11.4"><a href="#rfc.section.11.4">11.4</a> <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> <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"">[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"">[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 <<a href="http://www.iana.org/assignments/http-parameters">http://www.iana.org/assignments/http-parameters</a>>. 3629 </p> 3630 <h3 id="rfc.section.11.4.2"><a href="#rfc.section.11.4.2">11.4.2</a> <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 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 <<a href="http://www.iana.org/assignments/http-parameters">http://www.iana.org/assignments/http-parameters</a>> shall be updated with the registration below: 3627 3634 </p> 3628 3635 <div id="rfc.table.5"> … … 4027 4034 <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 3.3.8</a>) 4028 4035 </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 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 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 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 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 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 5.4</a>) 4034 4041 </p> 4035 4042 <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 4036 4043 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>) 4038 4045 </p> 4039 4046 <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 4040 4047 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 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 5. 6.15</a>)4048 (<a href="#status.305" id="rfc.xref.status.305.3" title="305 Use Proxy">Section 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 5.5.15</a>) 4044 4051 </p> 4045 4052 <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 10</a>) … … 4062 4069 <p id="rfc.section.C.p.18">Clarify contexts that charset is used in. (<a href="#character.sets" title="Character Encodings (charset)">Section 6.3</a>) 4063 4070 </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 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 11.4</a>) 4065 4072 </p> 4066 4073 <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 … … 4804 4811 <ul class="ind"> 4805 4812 <li><a id="rfc.index.1" href="#rfc.index.1"><b>1</b></a><ul> 4806 <li>100 Continue (status code) <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) <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> 4807 4814 <li>100-continue (expect value) <a href="#rfc.iref.142"><b>10.11</b></a></li> 4808 <li>101 Switching Protocols (status code) <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) <a href="#rfc.iref.21"><b>5. 3</b></a></li>4815 <li>101 Switching Protocols (status code) <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) <a href="#rfc.iref.21"><b>5.2</b></a></li> 4810 4817 </ul> 4811 4818 </li> 4812 4819 <li><a id="rfc.index.2" href="#rfc.index.2"><b>2</b></a><ul> 4813 <li>200 OK (status code) <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) <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) <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) <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) <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) <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) <a href="#rfc.iref.24"><b>5. 4</b></a></li>4820 <li>200 OK (status code) <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) <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) <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) <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) <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) <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) <a href="#rfc.iref.24"><b>5.3</b></a></li> 4820 4827 </ul> 4821 4828 </li> 4822 4829 <li><a id="rfc.index.3" href="#rfc.index.3"><b>3</b></a><ul> 4823 <li>300 Multiple Choices (status code) <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) <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) <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) <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) <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) <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) <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) <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) <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) <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) <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) <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) <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) <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) <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) <a href="#rfc.iref.31"><b>5.4</b></a>, <a href="#rfc.xref.status.3xx.1">C</a></li> 4831 4838 </ul> 4832 4839 </li> 4833 4840 <li><a id="rfc.index.4" href="#rfc.index.4"><b>4</b></a><ul> 4834 <li>400 Bad Request (status code) <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) <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) <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) <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) <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) <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) <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) <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) <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) <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) <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) <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) <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) <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) <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) <a href="#rfc.iref.39"><b>5. 6</b></a></li>4841 <li>400 Bad Request (status code) <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) <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) <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) <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) <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) <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) <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) <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) <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) <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) <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) <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) <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) <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) <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) <a href="#rfc.iref.39"><b>5.5</b></a></li> 4850 4857 </ul> 4851 4858 </li> 4852 4859 <li><a id="rfc.index.5" href="#rfc.index.5"><b>5</b></a><ul> 4853 <li>500 Internal Server Error (status code) <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) <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) <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) <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) <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) <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) <a href="#rfc.iref.55"><b>5. 7</b></a></li>4860 <li>500 Internal Server Error (status code) <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) <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) <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) <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) <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) <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) <a href="#rfc.iref.55"><b>5.6</b></a></li> 4860 4867 </ul> 4861 4868 </li> … … 4863 4870 <li>Accept header field <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> 4864 4871 <li>Accept-Charset header field <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 <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 <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> 4866 4873 <li>Accept-Language header field <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> 4867 4874 <li>Allow header field <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> … … 4878 4885 </li> 4879 4886 <li>compress (Coding Format) <a href="#rfc.iref.c.4">6.4</a></li> 4880 <li>CONNECT method <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 <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> 4881 4888 <li>content negotiation <a href="#rfc.iref.c.1">1</a></li> 4882 4889 <li>Content-Encoding header field <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> … … 4890 4897 <li>Date header field <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> 4891 4898 <li>deflate (Coding Format) <a href="#rfc.iref.d.2">6.4</a></li> 4892 <li>DELETE method <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 <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> 4893 4900 </ul> 4894 4901 </li> 4895 4902 <li><a id="rfc.index.E" href="#rfc.index.E"><b>E</b></a><ul> 4896 <li>Expect header field <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 <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> 4897 4904 <li>Expect Values 4898 4905 <ul> … … 4907 4914 </li> 4908 4915 <li><a id="rfc.index.G" href="#rfc.index.G"><b>G</b></a><ul> 4909 <li>GET method <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 <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> 4910 4917 <li><tt>Grammar</tt> 4911 4918 <ul> … … 4975 4982 </li> 4976 4983 <li><a id="rfc.index.H" href="#rfc.index.H"><b>H</b></a><ul> 4977 <li>HEAD method <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 <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> 4978 4985 <li>Header Fields 4979 4986 <ul> 4980 4987 <li>Accept <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> 4981 4988 <li>Accept-Charset <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 <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 <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> 4983 4990 <li>Accept-Language <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> 4984 4991 <li>Allow <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> … … 4989 4996 <li>Content-Type <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> 4990 4997 <li>Date <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 <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 <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> 4992 4999 <li>From <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 <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 <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> 4994 5001 <li>Max-Forwards <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> 4995 5002 <li>MIME-Version <a href="#rfc.xref.mime-version.1">11.3</a>, <a href="#rfc.iref.h.20"><b>A.1</b></a></li> 4996 5003 <li>Referer <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 <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 <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> 4998 5005 <li>Server <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> 4999 5006 <li>User-Agent <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> … … 5007 5014 </li> 5008 5015 <li><a id="rfc.index.L" href="#rfc.index.L"><b>L</b></a><ul> 5009 <li>Location header field <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 <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> 5010 5017 </ul> 5011 5018 </li> … … 5014 5021 <li>Methods 5015 5022 <ul> 5016 <li>CONNECT <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 <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 <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 <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 <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 <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 <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 <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 <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 <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 <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 <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 <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 <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 <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 <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> 5024 5031 </ul> 5025 5032 </li> … … 5028 5035 </li> 5029 5036 <li><a id="rfc.index.O" href="#rfc.index.O"><b>O</b></a><ul> 5030 <li>OPTIONS method <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 <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> 5031 5038 </ul> 5032 5039 </li> 5033 5040 <li><a id="rfc.index.P" href="#rfc.index.P"><b>P</b></a><ul> 5034 <li><em>Part1</em> <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> <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> 5035 5042 <li><em>Section 1.2</em> <a href="#rfc.xref.Part1.3">1.2</a></li> 5036 <li><em>Section 2.3</em> <a href="#rfc.xref.Part1.22">5. 4.4</a></li>5043 <li><em>Section 2.3</em> <a href="#rfc.xref.Part1.22">5.3.4</a></li> 5037 5044 <li><em>Section 2.5</em> <a href="#rfc.xref.Part1.2">1.1</a></li> 5038 <li><em>Section 2.6</em> <a href="#rfc.xref.Part1.25">5. 7.6</a></li>5045 <li><em>Section 2.6</em> <a href="#rfc.xref.Part1.25">5.6.6</a></li> 5039 5046 <li><em>Section 2.7</em> <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> <a href="#rfc.xref.Part1.11">4</a>, <a href="#rfc.xref.Part1.14">4.5</a>, <a href="#rfc.xref.Part1.3 7">10.17</a>, <a href="#rfc.xref.Part1.39">10.18</a></li>5047 <li><em>Section 3.2</em> <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> 5041 5048 <li><em>Section 3.2.1</em> <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> 5042 5049 <li><em>Section 3.2.4</em> <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> <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> <a href="#rfc.xref.Part1. 31">7.1</a></li>5045 <li><em>Section 4</em> <a href="#rfc.xref.Part1. 29">6.4.1</a></li>5050 <li><em>Section 3.3</em> <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> <a href="#rfc.xref.Part1.29">7.1</a></li> 5052 <li><em>Section 4</em> <a href="#rfc.xref.Part1.39">11.4.1</a></li> 5046 5053 <li><em>Section 4.1</em> <a href="#rfc.xref.Part1.16">4.5</a></li> 5047 <li><em>Section 4.2.1</em> <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> <a href="#rfc.xref.Part1. 30">6.4.1</a></li>5049 <li><em>Section 4.2.2</em> <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> <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> <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> <a href="#rfc.xref.Part1.40">11.4.1</a></li> 5056 <li><em>Section 4.2.2</em> <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> <a href="#rfc.xref.Part1.28">6.4</a>, <a href="#rfc.xref.Part1.43">11.4.2</a></li> 5051 5058 <li><em>Section 4.3</em> <a href="#rfc.xref.Part1.18">4.6</a></li> 5052 5059 <li><em>Section 5.3</em> <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> 5053 5060 <li><em>Section 5.4</em> <a href="#rfc.xref.Part1.17">4.6</a></li> 5054 <li><em>Section 5.5</em> <a href="#rfc.xref.Part1.6">2</a>, <a href="#rfc.xref.Part1.19">4.7</a>, <a href="#rfc.xref.Part1.3 4">8.1</a>, <a href="#rfc.xref.Part1.35">10.8</a></li>5055 <li><em>Section 5.7</em> <a href="#rfc.xref.Part1.8">3.3.7</a>, <a href="#rfc.xref.Part1.3 8">10.17</a>, <a href="#rfc.xref.Part1.45">C</a></li>5061 <li><em>Section 5.5</em> <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> <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> 5056 5063 <li><em>Section 6.1</em> <a href="#rfc.xref.Part1.15">4.5</a></li> 5057 <li><em>Section 6.3</em> <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> <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> <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> <a href="#rfc.xref.Part1.21">5.2.2</a>, <a href="#rfc.xref.Part1.24">5.5.15</a></li> 5059 5066 <li><em>Section 7.3.1</em> <a href="#rfc.xref.Part1.9">3.3.7</a></li> 5060 5067 <li><em>Section 9</em> <a href="#rfc.xref.Part1.44">13</a></li> … … 5062 5069 </ul> 5063 5070 </li> 5064 <li><em>Part4</em> <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> <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> 5065 5072 <li><em>Section 2.2</em> <a href="#rfc.xref.Part4.13">8.2</a></li> 5066 <li><em>Section 2.3</em> <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> <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> 5067 5074 <li><em>Section 3.1</em> <a href="#rfc.xref.Part4.2">4.6</a></li> 5068 5075 <li><em>Section 3.2</em> <a href="#rfc.xref.Part4.4">4.6</a></li> … … 5070 5077 <li><em>Section 3.4</em> <a href="#rfc.xref.Part4.5">4.6</a></li> 5071 5078 <li><em>Section 4</em> <a href="#rfc.xref.Part4.7">5.1</a></li> 5072 <li><em>Section 4.1</em> <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> <a href="#rfc.xref.Part4.8">5.1</a>, <a href="#rfc.xref.Part4.11">5.4</a></li> 5073 5080 <li><em>Section 4.2</em> <a href="#rfc.xref.Part4.9">5.1</a></li> 5074 5081 </ul> … … 5084 5091 </ul> 5085 5092 </li> 5086 <li><em>Part6</em> <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> <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> 5087 5094 <li><em>Section 4.1.1</em> <a href="#rfc.xref.Part6.4">3.3.4</a></li> 5088 <li><em>Section 4.1.2</em> <a href="#rfc.xref.Part6.1 1">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> <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> 5089 5096 <li><em>Section 5</em> <a href="#rfc.xref.Part6.3">3.3.3</a></li> 5090 5097 <li><em>Section 6</em> <a href="#rfc.xref.Part6.5">3.3.5</a>, <a href="#rfc.xref.Part6.6">3.3.6</a></li> 5091 5098 <li><em>Section 7.1</em> <a href="#rfc.xref.Part6.8">4.7</a></li> 5092 <li><em>Section 7.2</em> <a href="#rfc.xref.Part6.1 2">5.4.4</a></li>5093 <li><em>Section 7.3</em> <a href="#rfc.xref.Part6.1 8">8.2</a></li>5094 <li><em>Section 7.5</em> <a href="#rfc.xref.Part6.9">4.7</a>, <a href="#rfc.xref.Part6.1 9">9.1</a></li>5095 <li><em>Section 7.6</em> <a href="#rfc.xref.Part6.1 3">5.4.4</a></li>5099 <li><em>Section 7.2</em> <a href="#rfc.xref.Part6.11">5.3.4</a></li> 5100 <li><em>Section 7.3</em> <a href="#rfc.xref.Part6.17">8.2</a></li> 5101 <li><em>Section 7.5</em> <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> <a href="#rfc.xref.Part6.12">5.3.4</a></li> 5096 5103 </ul> 5097 5104 </li> … … 5107 5114 </li> 5108 5115 <li>payload <a href="#rfc.iref.p.3">7</a></li> 5109 <li>POST method <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 <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 <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 <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> 5111 5118 </ul> 5112 5119 </li> … … 5115 5122 <li>representation <a href="#rfc.iref.r.1">8</a></li> 5116 5123 <li><em>REST</em> <a href="#rfc.xref.REST.1">3.1</a>, <a href="#REST"><b>14.2</b></a></li> 5117 <li>Retry-After header field <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 <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> 5118 5125 <li><em>RFC1123</em> <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> 5119 5126 <li><em>Section 5.2.14</em> <a href="#rfc.xref.RFC1123.2">6.1</a></li> 5120 5127 </ul> 5121 5128 </li> 5122 <li><em>RFC1945</em> <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> <a href="#rfc.xref.RFC1945.1">5. 5</a></li>5129 <li><em>RFC1945</em> <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> <a href="#rfc.xref.RFC1945.1">5.4</a></li> 5124 5131 </ul> 5125 5132 </li> 5126 <li><em>RFC1950</em> <a href="#rfc.xref.RFC1950.1">11.4 </a>, <a href="#RFC1950"><b>14.1</b></a></li>5127 <li><em>RFC1951</em> <a href="#rfc.xref.RFC1951.1">11.4 </a>, <a href="#RFC1951"><b>14.1</b></a></li>5128 <li><em>RFC1952</em> <a href="#rfc.xref.RFC1952.1">11.4 </a>, <a href="#RFC1952"><b>14.1</b></a></li>5133 <li><em>RFC1950</em> <a href="#rfc.xref.RFC1950.1">11.4.2</a>, <a href="#RFC1950"><b>14.1</b></a></li> 5134 <li><em>RFC1951</em> <a href="#rfc.xref.RFC1951.1">11.4.2</a>, <a href="#RFC1951"><b>14.1</b></a></li> 5135 <li><em>RFC1952</em> <a href="#rfc.xref.RFC1952.1">11.4.2</a>, <a href="#RFC1952"><b>14.1</b></a></li> 5129 5136 <li><em>RFC2045</em> <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> 5130 5137 <li><em>RFC2046</em> <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> … … 5137 5144 </ul> 5138 5145 </li> 5139 <li><em>RFC2068</em> <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> <a href="#rfc.xref.RFC2068.2">5. 5</a></li>5141 <li><em>Section 10.3.4</em> <a href="#rfc.xref.RFC2068.1">5. 5</a></li>5146 <li><em>RFC2068</em> <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> <a href="#rfc.xref.RFC2068.2">5.4</a></li> 5148 <li><em>Section 10.3.4</em> <a href="#rfc.xref.RFC2068.1">5.4</a></li> 5142 5149 </ul> 5143 5150 </li> … … 5151 5158 </ul> 5152 5159 </li> 5153 <li><em>RFC2616</em> <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> <a href="#rfc.xref.RFC2616.1">5. 5</a></li>5160 <li><em>RFC2616</em> <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> <a href="#rfc.xref.RFC2616.1">5.4</a></li> 5155 5162 <li><em>Section 14.4</em> <a href="#rfc.xref.RFC2616.2">10.4</a></li> 5156 5163 </ul> 5157 5164 </li> 5158 <li><em>RFC2817</em> <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> <a href="#rfc.xref.RFC2817.1">11.2 </a>, <a href="#rfc.xref.RFC2817.3">C</a></li>5165 <li><em>RFC2817</em> <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> <a href="#rfc.xref.RFC2817.1">11.2.3</a>, <a href="#rfc.xref.RFC2817.3">C</a></li> 5160 5167 </ul> 5161 5168 </li> … … 5178 5185 </ul> 5179 5186 </li> 5180 <li><em>RFC5226</em> <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> <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> <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> <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> 5182 5189 </ul> 5183 5190 </li> … … 5208 5215 <li>Status Codes 5209 5216 <ul> 5210 <li>100 Continue <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 <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 <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 <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 <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 <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 <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 <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 <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 <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 <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 <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 <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) <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 <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 <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 <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 <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 <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 <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 <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 <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 <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 <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 <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 <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 <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 <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 <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 <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 <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 <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 <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 <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 <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 <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 <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 <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 <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 <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 <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 <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 <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 <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 <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 <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 <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 <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 <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) <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 <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 <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 <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 <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 <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 <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 <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 <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 <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 <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 <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 <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 <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 <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 <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 <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 <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 <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 <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 <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 <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 <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> 5246 5253 </ul> 5247 5254 </li> 5248 5255 <li>Status Codes Classes 5249 5256 <ul> 5250 <li>1xx Informational <a href="#rfc.iref.s.2"><b>5. 3</b></a></li>5251 <li>2xx Successful <a href="#rfc.iref.s.5"><b>5. 4</b></a></li>5252 <li>3xx Redirection <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 <a href="#rfc.iref.s.20"><b>5. 6</b></a></li>5254 <li>5xx Server Error <a href="#rfc.iref.s.36"><b>5. 7</b></a></li>5257 <li>1xx Informational <a href="#rfc.iref.s.2"><b>5.2</b></a></li> 5258 <li>2xx Successful <a href="#rfc.iref.s.5"><b>5.3</b></a></li> 5259 <li>3xx Redirection <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 <a href="#rfc.iref.s.20"><b>5.5</b></a></li> 5261 <li>5xx Server Error <a href="#rfc.iref.s.36"><b>5.6</b></a></li> 5255 5262 </ul> 5256 5263 </li> 5257 <li><em>status-308</em> <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> <a href="#rfc.xref.status-308.1">5.4.7</a>, <a href="#status-308"><b>14.2</b></a></li> 5258 5265 </ul> 5259 5266 </li> 5260 5267 <li><a id="rfc.index.T" href="#rfc.index.T"><b>T</b></a><ul> 5261 <li>TRACE method <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 <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> 5262 5269 </ul> 5263 5270 </li> -
draft-ietf-httpbis/latest/p2-semantics.xml
r1842 r1843 1240 1240 </section> 1241 1241 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-code1245 token in the status-line of an HTTP response.1246 </t>1247 <t>1248 Values to be added to this name space require IETF Review1249 (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 that1258 aren't specific to a single application or media type, and currently defined1259 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 to1263 any resource, not just one particular media type, "type" of resource, or1264 application. As such, it is preferred that new HTTP status codes be1265 registered in a document that isn't specific to a single application, so1266 that this is clear.1267 </t>1268 <t>1269 Definitions of new HTTP status codes typically explain the request1270 conditions that produce a response containing the status code (e.g.,1271 combinations of request header fields and/or method(s)), along with any1272 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 categories1277 defined in <xref target="status.codes"/>. To allow existing parsers to1278 properly handle them, new status codes cannot disallow a response body,1279 although they can mandate a zero-length response body. They can require the1280 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 use1284 heuristics to determine their freshness (see &caching;; by default, it is1285 not allowed), and can define how to determine the resource which they1286 carry a representation for (see <xref1287 target="identifying.response.associated.with.representation"/>; by default,1288 it is anonymous).1289 </t>1290 </section>1291 1292 </section>1293 1294 1242 <section title="Informational 1xx" anchor="status.1xx"> 1295 1243 <x:anchor-alias value="1xx"/> … … 2436 2384 </list> 2437 2385 </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 content2442 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 codings2454 (&transfer-codings;), unless the encoding transformation is identical (as2455 is the case for the compression codings defined in2456 &compression-codings;).2457 </t>2458 <t>2459 Values to be added to this name space require IETF Review2460 (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 at2465 <eref target="http://www.iana.org/assignments/http-parameters"/>.2466 </t>2467 </section>2468 2469 2386 </section> 2470 2387 … … 4030 3947 Request line of an HTTP request. 4031 3948 </t> 3949 <section title="Procedure" anchor="method.procedure"> 4032 3950 <t> 4033 3951 Registrations &MUST; include the following fields: … … 4046 3964 The registry itself is maintained at <eref target="http://www.iana.org/assignments/http-methods"/>. 4047 3965 </t> 3966 </section> 4048 3967 4049 3968 <section title="Considerations for New Methods" anchor="considerations.for.new.methods"> … … 4141 4060 </section> 4142 4061 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"> 4144 4116 <t> 4145 4117 The registration procedure for HTTP Status Codes — previously defined … … 4341 4313 <?ENDINC p2-semantics.iana-status-codes ?> 4342 4314 </section> 4315 </section> 4316 4343 4317 <section title="Header Field Registration" anchor="header.field.registration"> 4344 4318 <t> … … 4476 4450 </section> 4477 4451 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"> 4479 4485 <t> 4480 4486 The registration procedure for HTTP Content Codings is now defined … … 4514 4520 </texttable> 4515 4521 </section> 4516 4522 </section> 4517 4523 </section> 4518 4524
Note: See TracChangeset
for help on using the changeset viewer.