Changeset 1621
- Timestamp:
- 26/03/12 14:56:26 (10 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p2-semantics.html
r1619 r1621 632 632 </ul> 633 633 </li> 634 <li>4.3 <a href="#status.codes">Status Code Definitions</a><ul> 635 <li>4.3.1 <a href="#status.1xx">Informational 1xx</a><ul> 636 <li>4.3.1.1 <a href="#status.100">100 Continue</a></li> 637 <li>4.3.1.2 <a href="#status.101">101 Switching Protocols</a></li> 638 </ul> 639 </li> 640 <li>4.3.2 <a href="#status.2xx">Successful 2xx</a><ul> 641 <li>4.3.2.1 <a href="#status.200">200 OK</a></li> 642 <li>4.3.2.2 <a href="#status.201">201 Created</a></li> 643 <li>4.3.2.3 <a href="#status.202">202 Accepted</a></li> 644 <li>4.3.2.4 <a href="#status.203">203 Non-Authoritative Information</a></li> 645 <li>4.3.2.5 <a href="#status.204">204 No Content</a></li> 646 <li>4.3.2.6 <a href="#status.205">205 Reset Content</a></li> 647 </ul> 648 </li> 649 <li>4.3.3 <a href="#status.3xx">Redirection 3xx</a><ul> 650 <li>4.3.3.1 <a href="#status.300">300 Multiple Choices</a></li> 651 <li>4.3.3.2 <a href="#status.301">301 Moved Permanently</a></li> 652 <li>4.3.3.3 <a href="#status.302">302 Found</a></li> 653 <li>4.3.3.4 <a href="#status.303">303 See Other</a></li> 654 <li>4.3.3.5 <a href="#status.305">305 Use Proxy</a></li> 655 <li>4.3.3.6 <a href="#status.306">306 (Unused)</a></li> 656 <li>4.3.3.7 <a href="#status.307">307 Temporary Redirect</a></li> 657 </ul> 658 </li> 659 <li>4.3.4 <a href="#status.4xx">Client Error 4xx</a><ul> 660 <li>4.3.4.1 <a href="#status.400">400 Bad Request</a></li> 661 <li>4.3.4.2 <a href="#status.402">402 Payment Required</a></li> 662 <li>4.3.4.3 <a href="#status.403">403 Forbidden</a></li> 663 <li>4.3.4.4 <a href="#status.404">404 Not Found</a></li> 664 <li>4.3.4.5 <a href="#status.405">405 Method Not Allowed</a></li> 665 <li>4.3.4.6 <a href="#status.406">406 Not Acceptable</a></li> 666 <li>4.3.4.7 <a href="#status.408">408 Request Timeout</a></li> 667 <li>4.3.4.8 <a href="#status.409">409 Conflict</a></li> 668 <li>4.3.4.9 <a href="#status.410">410 Gone</a></li> 669 <li>4.3.4.10 <a href="#status.411">411 Length Required</a></li> 670 <li>4.3.4.11 <a href="#status.413">413 Request Representation Too Large</a></li> 671 <li>4.3.4.12 <a href="#status.414">414 URI Too Long</a></li> 672 <li>4.3.4.13 <a href="#status.415">415 Unsupported Media Type</a></li> 673 <li>4.3.4.14 <a href="#status.417">417 Expectation Failed</a></li> 674 <li>4.3.4.15 <a href="#status.426">426 Upgrade Required</a></li> 675 </ul> 676 </li> 677 <li>4.3.5 <a href="#status.5xx">Server Error 5xx</a><ul> 678 <li>4.3.5.1 <a href="#status.500">500 Internal Server Error</a></li> 679 <li>4.3.5.2 <a href="#status.501">501 Not Implemented</a></li> 680 <li>4.3.5.3 <a href="#status.502">502 Bad Gateway</a></li> 681 <li>4.3.5.4 <a href="#status.503">503 Service Unavailable</a></li> 682 <li>4.3.5.5 <a href="#status.504">504 Gateway Timeout</a></li> 683 <li>4.3.5.6 <a href="#status.505">505 HTTP Version Not Supported</a></li> 684 </ul> 685 </li> 634 <li>4.3 <a href="#status.1xx">Informational 1xx</a><ul> 635 <li>4.3.1 <a href="#status.100">100 Continue</a></li> 636 <li>4.3.2 <a href="#status.101">101 Switching Protocols</a></li> 637 </ul> 638 </li> 639 <li>4.4 <a href="#status.2xx">Successful 2xx</a><ul> 640 <li>4.4.1 <a href="#status.200">200 OK</a></li> 641 <li>4.4.2 <a href="#status.201">201 Created</a></li> 642 <li>4.4.3 <a href="#status.202">202 Accepted</a></li> 643 <li>4.4.4 <a href="#status.203">203 Non-Authoritative Information</a></li> 644 <li>4.4.5 <a href="#status.204">204 No Content</a></li> 645 <li>4.4.6 <a href="#status.205">205 Reset Content</a></li> 646 </ul> 647 </li> 648 <li>4.5 <a href="#status.3xx">Redirection 3xx</a><ul> 649 <li>4.5.1 <a href="#status.300">300 Multiple Choices</a></li> 650 <li>4.5.2 <a href="#status.301">301 Moved Permanently</a></li> 651 <li>4.5.3 <a href="#status.302">302 Found</a></li> 652 <li>4.5.4 <a href="#status.303">303 See Other</a></li> 653 <li>4.5.5 <a href="#status.305">305 Use Proxy</a></li> 654 <li>4.5.6 <a href="#status.306">306 (Unused)</a></li> 655 <li>4.5.7 <a href="#status.307">307 Temporary Redirect</a></li> 656 </ul> 657 </li> 658 <li>4.6 <a href="#status.4xx">Client Error 4xx</a><ul> 659 <li>4.6.1 <a href="#status.400">400 Bad Request</a></li> 660 <li>4.6.2 <a href="#status.402">402 Payment Required</a></li> 661 <li>4.6.3 <a href="#status.403">403 Forbidden</a></li> 662 <li>4.6.4 <a href="#status.404">404 Not Found</a></li> 663 <li>4.6.5 <a href="#status.405">405 Method Not Allowed</a></li> 664 <li>4.6.6 <a href="#status.406">406 Not Acceptable</a></li> 665 <li>4.6.7 <a href="#status.408">408 Request Timeout</a></li> 666 <li>4.6.8 <a href="#status.409">409 Conflict</a></li> 667 <li>4.6.9 <a href="#status.410">410 Gone</a></li> 668 <li>4.6.10 <a href="#status.411">411 Length Required</a></li> 669 <li>4.6.11 <a href="#status.413">413 Request Representation Too Large</a></li> 670 <li>4.6.12 <a href="#status.414">414 URI Too Long</a></li> 671 <li>4.6.13 <a href="#status.415">415 Unsupported Media Type</a></li> 672 <li>4.6.14 <a href="#status.417">417 Expectation Failed</a></li> 673 <li>4.6.15 <a href="#status.426">426 Upgrade Required</a></li> 674 </ul> 675 </li> 676 <li>4.7 <a href="#status.5xx">Server Error 5xx</a><ul> 677 <li>4.7.1 <a href="#status.500">500 Internal Server Error</a></li> 678 <li>4.7.2 <a href="#status.501">501 Not Implemented</a></li> 679 <li>4.7.3 <a href="#status.502">502 Bad Gateway</a></li> 680 <li>4.7.4 <a href="#status.503">503 Service Unavailable</a></li> 681 <li>4.7.5 <a href="#status.504">504 Gateway Timeout</a></li> 682 <li>4.7.6 <a href="#status.505">505 HTTP Version Not Supported</a></li> 686 683 </ul> 687 684 </li> … … 1334 1331 <li>5xx: Server Error - The server failed to fulfill an apparently valid request</li> 1335 1332 </ul> 1333 <p id="rfc.section.4.p.6">For most status codes the response can carry a payload, in which case a Content-Type header field indicates the payload's 1334 media type (<a href="p3-payload.html#header.content-type" title="Content-Type">Section 6.8</a> of <a href="#Part3" id="rfc.xref.Part3.8"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>). 1335 </p> 1336 1336 <h2 id="rfc.section.4.1"><a href="#rfc.section.4.1">4.1</a> <a id="overview.of.status.codes" href="#overview.of.status.codes">Overview of Status Codes</a></h2> 1337 <p id="rfc.section.4.1.p.1">The status codes listed below are defined in <a href="#status.codes" title="Status Code Definitions">Section 4.3</a> ofthis specification, <a href="p4-conditional.html#status.code.definitions" title="Status Code Definitions">Section 4</a> of <a href="#Part4" id="rfc.xref.Part4.6"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>, <a href="p5-range.html#status.code.definitions" title="Status Code Definitions">Section 3</a> of <a href="#Part5" id="rfc.xref.Part5.5"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>, and <a href="p7-auth.html#status.code.definitions" title="Status Code Definitions">Section 3</a> of <a href="#Part7" id="rfc.xref.Part7.5"><cite title="HTTP/1.1, part 7: Authentication">[Part7]</cite></a>. The reason phrases listed here are only recommendations — they can be replaced by local equivalents without affecting the1337 <p id="rfc.section.4.1.p.1">The status codes listed below are defined in this specification, <a href="p4-conditional.html#status.code.definitions" title="Status Code Definitions">Section 4</a> of <a href="#Part4" id="rfc.xref.Part4.6"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>, <a href="p5-range.html#status.code.definitions" title="Status Code Definitions">Section 3</a> of <a href="#Part5" id="rfc.xref.Part5.5"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>, and <a href="p7-auth.html#status.code.definitions" title="Status Code Definitions">Section 3</a> of <a href="#Part7" id="rfc.xref.Part7.5"><cite title="HTTP/1.1, part 7: Authentication">[Part7]</cite></a>. The reason phrases listed here are only recommendations — they can be replaced by local equivalents without affecting the 1338 1338 protocol. 1339 1339 </p> … … 1351 1351 <td class="left">100</td> 1352 1352 <td class="left">Continue</td> 1353 <td class="left"><a href="#status.100" id="rfc.xref.status.100.1" title="100 Continue">Section 4.3.1 .1</a></td>1353 <td class="left"><a href="#status.100" id="rfc.xref.status.100.1" title="100 Continue">Section 4.3.1</a></td> 1354 1354 </tr> 1355 1355 <tr> 1356 1356 <td class="left">101</td> 1357 1357 <td class="left">Switching Protocols</td> 1358 <td class="left"><a href="#status.101" id="rfc.xref.status.101.1" title="101 Switching Protocols">Section 4.3. 1.2</a></td>1358 <td class="left"><a href="#status.101" id="rfc.xref.status.101.1" title="101 Switching Protocols">Section 4.3.2</a></td> 1359 1359 </tr> 1360 1360 <tr> 1361 1361 <td class="left">200</td> 1362 1362 <td class="left">OK</td> 1363 <td class="left"><a href="#status.200" id="rfc.xref.status.200.1" title="200 OK">Section 4. 3.2.1</a></td>1363 <td class="left"><a href="#status.200" id="rfc.xref.status.200.1" title="200 OK">Section 4.4.1</a></td> 1364 1364 </tr> 1365 1365 <tr> 1366 1366 <td class="left">201</td> 1367 1367 <td class="left">Created</td> 1368 <td class="left"><a href="#status.201" id="rfc.xref.status.201.1" title="201 Created">Section 4. 3.2.2</a></td>1368 <td class="left"><a href="#status.201" id="rfc.xref.status.201.1" title="201 Created">Section 4.4.2</a></td> 1369 1369 </tr> 1370 1370 <tr> 1371 1371 <td class="left">202</td> 1372 1372 <td class="left">Accepted</td> 1373 <td class="left"><a href="#status.202" id="rfc.xref.status.202.1" title="202 Accepted">Section 4. 3.2.3</a></td>1373 <td class="left"><a href="#status.202" id="rfc.xref.status.202.1" title="202 Accepted">Section 4.4.3</a></td> 1374 1374 </tr> 1375 1375 <tr> 1376 1376 <td class="left">203</td> 1377 1377 <td class="left">Non-Authoritative Information</td> 1378 <td class="left"><a href="#status.203" id="rfc.xref.status.203.1" title="203 Non-Authoritative Information">Section 4. 3.2.4</a></td>1378 <td class="left"><a href="#status.203" id="rfc.xref.status.203.1" title="203 Non-Authoritative Information">Section 4.4.4</a></td> 1379 1379 </tr> 1380 1380 <tr> 1381 1381 <td class="left">204</td> 1382 1382 <td class="left">No Content</td> 1383 <td class="left"><a href="#status.204" id="rfc.xref.status.204.1" title="204 No Content">Section 4. 3.2.5</a></td>1383 <td class="left"><a href="#status.204" id="rfc.xref.status.204.1" title="204 No Content">Section 4.4.5</a></td> 1384 1384 </tr> 1385 1385 <tr> 1386 1386 <td class="left">205</td> 1387 1387 <td class="left">Reset Content</td> 1388 <td class="left"><a href="#status.205" id="rfc.xref.status.205.1" title="205 Reset Content">Section 4. 3.2.6</a></td>1388 <td class="left"><a href="#status.205" id="rfc.xref.status.205.1" title="205 Reset Content">Section 4.4.6</a></td> 1389 1389 </tr> 1390 1390 <tr> … … 1396 1396 <td class="left">300</td> 1397 1397 <td class="left">Multiple Choices</td> 1398 <td class="left"><a href="#status.300" id="rfc.xref.status.300.1" title="300 Multiple Choices">Section 4. 3.3.1</a></td>1398 <td class="left"><a href="#status.300" id="rfc.xref.status.300.1" title="300 Multiple Choices">Section 4.5.1</a></td> 1399 1399 </tr> 1400 1400 <tr> 1401 1401 <td class="left">301</td> 1402 1402 <td class="left">Moved Permanently</td> 1403 <td class="left"><a href="#status.301" id="rfc.xref.status.301.1" title="301 Moved Permanently">Section 4. 3.3.2</a></td>1403 <td class="left"><a href="#status.301" id="rfc.xref.status.301.1" title="301 Moved Permanently">Section 4.5.2</a></td> 1404 1404 </tr> 1405 1405 <tr> 1406 1406 <td class="left">302</td> 1407 1407 <td class="left">Found</td> 1408 <td class="left"><a href="#status.302" id="rfc.xref.status.302.1" title="302 Found">Section 4. 3.3.3</a></td>1408 <td class="left"><a href="#status.302" id="rfc.xref.status.302.1" title="302 Found">Section 4.5.3</a></td> 1409 1409 </tr> 1410 1410 <tr> 1411 1411 <td class="left">303</td> 1412 1412 <td class="left">See Other</td> 1413 <td class="left"><a href="#status.303" id="rfc.xref.status.303.1" title="303 See Other">Section 4. 3.3.4</a></td>1413 <td class="left"><a href="#status.303" id="rfc.xref.status.303.1" title="303 See Other">Section 4.5.4</a></td> 1414 1414 </tr> 1415 1415 <tr> … … 1421 1421 <td class="left">305</td> 1422 1422 <td class="left">Use Proxy</td> 1423 <td class="left"><a href="#status.305" id="rfc.xref.status.305.1" title="305 Use Proxy">Section 4. 3.3.5</a></td>1423 <td class="left"><a href="#status.305" id="rfc.xref.status.305.1" title="305 Use Proxy">Section 4.5.5</a></td> 1424 1424 </tr> 1425 1425 <tr> 1426 1426 <td class="left">307</td> 1427 1427 <td class="left">Temporary Redirect</td> 1428 <td class="left"><a href="#status.307" id="rfc.xref.status.307.1" title="307 Temporary Redirect">Section 4. 3.3.7</a></td>1428 <td class="left"><a href="#status.307" id="rfc.xref.status.307.1" title="307 Temporary Redirect">Section 4.5.7</a></td> 1429 1429 </tr> 1430 1430 <tr> 1431 1431 <td class="left">400</td> 1432 1432 <td class="left">Bad Request</td> 1433 <td class="left"><a href="#status.400" id="rfc.xref.status.400.1" title="400 Bad Request">Section 4. 3.4.1</a></td>1433 <td class="left"><a href="#status.400" id="rfc.xref.status.400.1" title="400 Bad Request">Section 4.6.1</a></td> 1434 1434 </tr> 1435 1435 <tr> … … 1441 1441 <td class="left">402</td> 1442 1442 <td class="left">Payment Required</td> 1443 <td class="left"><a href="#status.402" id="rfc.xref.status.402.1" title="402 Payment Required">Section 4. 3.4.2</a></td>1443 <td class="left"><a href="#status.402" id="rfc.xref.status.402.1" title="402 Payment Required">Section 4.6.2</a></td> 1444 1444 </tr> 1445 1445 <tr> 1446 1446 <td class="left">403</td> 1447 1447 <td class="left">Forbidden</td> 1448 <td class="left"><a href="#status.403" id="rfc.xref.status.403.1" title="403 Forbidden">Section 4. 3.4.3</a></td>1448 <td class="left"><a href="#status.403" id="rfc.xref.status.403.1" title="403 Forbidden">Section 4.6.3</a></td> 1449 1449 </tr> 1450 1450 <tr> 1451 1451 <td class="left">404</td> 1452 1452 <td class="left">Not Found</td> 1453 <td class="left"><a href="#status.404" id="rfc.xref.status.404.1" title="404 Not Found">Section 4. 3.4.4</a></td>1453 <td class="left"><a href="#status.404" id="rfc.xref.status.404.1" title="404 Not Found">Section 4.6.4</a></td> 1454 1454 </tr> 1455 1455 <tr> 1456 1456 <td class="left">405</td> 1457 1457 <td class="left">Method Not Allowed</td> 1458 <td class="left"><a href="#status.405" id="rfc.xref.status.405.1" title="405 Method Not Allowed">Section 4. 3.4.5</a></td>1458 <td class="left"><a href="#status.405" id="rfc.xref.status.405.1" title="405 Method Not Allowed">Section 4.6.5</a></td> 1459 1459 </tr> 1460 1460 <tr> 1461 1461 <td class="left">406</td> 1462 1462 <td class="left">Not Acceptable</td> 1463 <td class="left"><a href="#status.406" id="rfc.xref.status.406.1" title="406 Not Acceptable">Section 4. 3.4.6</a></td>1463 <td class="left"><a href="#status.406" id="rfc.xref.status.406.1" title="406 Not Acceptable">Section 4.6.6</a></td> 1464 1464 </tr> 1465 1465 <tr> … … 1471 1471 <td class="left">408</td> 1472 1472 <td class="left">Request Time-out</td> 1473 <td class="left"><a href="#status.408" id="rfc.xref.status.408.1" title="408 Request Timeout">Section 4. 3.4.7</a></td>1473 <td class="left"><a href="#status.408" id="rfc.xref.status.408.1" title="408 Request Timeout">Section 4.6.7</a></td> 1474 1474 </tr> 1475 1475 <tr> 1476 1476 <td class="left">409</td> 1477 1477 <td class="left">Conflict</td> 1478 <td class="left"><a href="#status.409" id="rfc.xref.status.409.1" title="409 Conflict">Section 4. 3.4.8</a></td>1478 <td class="left"><a href="#status.409" id="rfc.xref.status.409.1" title="409 Conflict">Section 4.6.8</a></td> 1479 1479 </tr> 1480 1480 <tr> 1481 1481 <td class="left">410</td> 1482 1482 <td class="left">Gone</td> 1483 <td class="left"><a href="#status.410" id="rfc.xref.status.410.1" title="410 Gone">Section 4. 3.4.9</a></td>1483 <td class="left"><a href="#status.410" id="rfc.xref.status.410.1" title="410 Gone">Section 4.6.9</a></td> 1484 1484 </tr> 1485 1485 <tr> 1486 1486 <td class="left">411</td> 1487 1487 <td class="left">Length Required</td> 1488 <td class="left"><a href="#status.411" id="rfc.xref.status.411.1" title="411 Length Required">Section 4. 3.4.10</a></td>1488 <td class="left"><a href="#status.411" id="rfc.xref.status.411.1" title="411 Length Required">Section 4.6.10</a></td> 1489 1489 </tr> 1490 1490 <tr> … … 1496 1496 <td class="left">413</td> 1497 1497 <td class="left">Request Representation Too Large</td> 1498 <td class="left"><a href="#status.413" id="rfc.xref.status.413.1" title="413 Request Representation Too Large">Section 4. 3.4.11</a></td>1498 <td class="left"><a href="#status.413" id="rfc.xref.status.413.1" title="413 Request Representation Too Large">Section 4.6.11</a></td> 1499 1499 </tr> 1500 1500 <tr> 1501 1501 <td class="left">414</td> 1502 1502 <td class="left">URI Too Long</td> 1503 <td class="left"><a href="#status.414" id="rfc.xref.status.414.1" title="414 URI Too Long">Section 4. 3.4.12</a></td>1503 <td class="left"><a href="#status.414" id="rfc.xref.status.414.1" title="414 URI Too Long">Section 4.6.12</a></td> 1504 1504 </tr> 1505 1505 <tr> 1506 1506 <td class="left">415</td> 1507 1507 <td class="left">Unsupported Media Type</td> 1508 <td class="left"><a href="#status.415" id="rfc.xref.status.415.1" title="415 Unsupported Media Type">Section 4. 3.4.13</a></td>1508 <td class="left"><a href="#status.415" id="rfc.xref.status.415.1" title="415 Unsupported Media Type">Section 4.6.13</a></td> 1509 1509 </tr> 1510 1510 <tr> … … 1516 1516 <td class="left">417</td> 1517 1517 <td class="left">Expectation Failed</td> 1518 <td class="left"><a href="#status.417" id="rfc.xref.status.417.1" title="417 Expectation Failed">Section 4. 3.4.14</a></td>1518 <td class="left"><a href="#status.417" id="rfc.xref.status.417.1" title="417 Expectation Failed">Section 4.6.14</a></td> 1519 1519 </tr> 1520 1520 <tr> 1521 1521 <td class="left">426</td> 1522 1522 <td class="left">Upgrade Required</td> 1523 <td class="left"><a href="#status.426" id="rfc.xref.status.426.1" title="426 Upgrade Required">Section 4. 3.4.15</a></td>1523 <td class="left"><a href="#status.426" id="rfc.xref.status.426.1" title="426 Upgrade Required">Section 4.6.15</a></td> 1524 1524 </tr> 1525 1525 <tr> 1526 1526 <td class="left">500</td> 1527 1527 <td class="left">Internal Server Error</td> 1528 <td class="left"><a href="#status.500" id="rfc.xref.status.500.1" title="500 Internal Server Error">Section 4. 3.5.1</a></td>1528 <td class="left"><a href="#status.500" id="rfc.xref.status.500.1" title="500 Internal Server Error">Section 4.7.1</a></td> 1529 1529 </tr> 1530 1530 <tr> 1531 1531 <td class="left">501</td> 1532 1532 <td class="left">Not Implemented</td> 1533 <td class="left"><a href="#status.501" id="rfc.xref.status.501.1" title="501 Not Implemented">Section 4. 3.5.2</a></td>1533 <td class="left"><a href="#status.501" id="rfc.xref.status.501.1" title="501 Not Implemented">Section 4.7.2</a></td> 1534 1534 </tr> 1535 1535 <tr> 1536 1536 <td class="left">502</td> 1537 1537 <td class="left">Bad Gateway</td> 1538 <td class="left"><a href="#status.502" id="rfc.xref.status.502.1" title="502 Bad Gateway">Section 4. 3.5.3</a></td>1538 <td class="left"><a href="#status.502" id="rfc.xref.status.502.1" title="502 Bad Gateway">Section 4.7.3</a></td> 1539 1539 </tr> 1540 1540 <tr> 1541 1541 <td class="left">503</td> 1542 1542 <td class="left">Service Unavailable</td> 1543 <td class="left"><a href="#status.503" id="rfc.xref.status.503.1" title="503 Service Unavailable">Section 4. 3.5.4</a></td>1543 <td class="left"><a href="#status.503" id="rfc.xref.status.503.1" title="503 Service Unavailable">Section 4.7.4</a></td> 1544 1544 </tr> 1545 1545 <tr> 1546 1546 <td class="left">504</td> 1547 1547 <td class="left">Gateway Time-out</td> 1548 <td class="left"><a href="#status.504" id="rfc.xref.status.504.1" title="504 Gateway Timeout">Section 4. 3.5.5</a></td>1548 <td class="left"><a href="#status.504" id="rfc.xref.status.504.1" title="504 Gateway Timeout">Section 4.7.5</a></td> 1549 1549 </tr> 1550 1550 <tr> 1551 1551 <td class="left">505</td> 1552 1552 <td class="left">HTTP Version not supported</td> 1553 <td class="left"><a href="#status.505" id="rfc.xref.status.505.1" title="505 HTTP Version Not Supported">Section 4. 3.5.6</a></td>1553 <td class="left"><a href="#status.505" id="rfc.xref.status.505.1" title="505 HTTP Version Not Supported">Section 4.7.6</a></td> 1554 1554 </tr> 1555 1555 </tbody> … … 1575 1575 that are required, those that modify the semantics of the response). 1576 1576 </p> 1577 <p id="rfc.section.4.2.1.p.4">New HTTP status codes are required to fall under one of the categories defined in <a href="#status.code s" title="Status Code Definitions">Section 4.3</a>. To allow existing parsers to properly handle them, new status codes cannot disallow a response body, although they can mandate1577 <p id="rfc.section.4.2.1.p.4">New HTTP status codes are required to fall under one of the categories defined in <a href="#status.code.and.reason.phrase" title="Status Code and Reason Phrase">Section 4</a>. To allow existing parsers to properly handle them, new status codes cannot disallow a response body, although they can mandate 1578 1578 a zero-length response body. They can require the presence of one or more particular HTTP response header(s). 1579 1579 </p> 1580 1580 <p id="rfc.section.4.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 5.1</a>; by default, it is anonymous). 1581 1581 </p> 1582 <h2 id="rfc.section.4.3"><a href="#rfc.section.4.3">4.3</a> <a id="status.codes" href="#status.codes">Status Code Definitions</a></h2> 1583 <p id="rfc.section.4.3.p.1">Each status-code is described below, including any metadata required in the response.</p> 1584 <p id="rfc.section.4.3.p.2">For most status codes the response can carry a payload, in which case a Content-Type header field indicates the payload's 1585 media type (<a href="p3-payload.html#header.content-type" title="Content-Type">Section 6.8</a> of <a href="#Part3" id="rfc.xref.Part3.8"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>). 1586 </p> 1587 <h3 id="rfc.section.4.3.1"><a href="#rfc.section.4.3.1">4.3.1</a> <a id="status.1xx" href="#status.1xx">Informational 1xx</a></h3> 1588 <p id="rfc.section.4.3.1.p.1">This class of status code indicates a provisional response, consisting only of the status-line and optional header fields, 1582 <h2 id="rfc.section.4.3"><a href="#rfc.section.4.3">4.3</a> <a id="status.1xx" href="#status.1xx">Informational 1xx</a></h2> 1583 <p id="rfc.section.4.3.p.1">This class of status code indicates a provisional response, consisting only of the status-line and optional header fields, 1589 1584 and is terminated by an empty line. There are no required header fields for this class of status code. Since HTTP/1.0 did 1590 1585 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. 1591 1586 </p> 1592 <p id="rfc.section.4.3. 1.p.2">A client <em class="bcp14">MUST</em> be prepared to accept one or more 1xx status responses prior to a regular response, even if the client does not expect a 1001587 <p id="rfc.section.4.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 100 1593 1588 (Continue) status message. Unexpected 1xx status responses <em class="bcp14">MAY</em> be ignored by a user agent. 1594 1589 </p> 1595 <p id="rfc.section.4.3. 1.p.3">Proxies <em class="bcp14">MUST</em> forward 1xx responses, unless the connection between the proxy and its client has been closed, or unless the proxy itself1590 <p id="rfc.section.4.3.p.3">Proxies <em class="bcp14">MUST</em> forward 1xx responses, unless the connection between the proxy and its client has been closed, or unless the proxy itself 1596 1591 requested the generation of the 1xx response. (For example, if a proxy adds a "Expect: 100-continue" field when it forwards 1597 1592 a request, then it need not forward the corresponding 100 (Continue) response(s).) … … 1599 1594 <div id="rfc.iref.22"></div> 1600 1595 <div id="rfc.iref.s.2"></div> 1601 <h 4 id="rfc.section.4.3.1.1"><a href="#rfc.section.4.3.1.1">4.3.1.1</a> <a id="status.100" href="#status.100">100 Continue</a></h4>1602 <p id="rfc.section.4.3.1. 1.p.1">The client <em class="bcp14">SHOULD</em> continue with its request. This interim response is used to inform the client that the initial part of the request has been1596 <h3 id="rfc.section.4.3.1"><a href="#rfc.section.4.3.1">4.3.1</a> <a id="status.100" href="#status.100">100 Continue</a></h3> 1597 <p id="rfc.section.4.3.1.p.1">The client <em class="bcp14">SHOULD</em> continue with its request. This interim response is used to inform the client that the initial part of the request has been 1603 1598 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 1604 1599 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.4.3</a> of <a href="#Part1" id="rfc.xref.Part1.30"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a> for detailed discussion of the use and handling of this status code. … … 1606 1601 <div id="rfc.iref.23"></div> 1607 1602 <div id="rfc.iref.s.3"></div> 1608 <h 4 id="rfc.section.4.3.1.2"><a href="#rfc.section.4.3.1.2">4.3.1.2</a> <a id="status.101" href="#status.101">101 Switching Protocols</a></h4>1609 <p id="rfc.section.4.3. 1.2.p.1">The server understands and is willing to comply with the client's request, via the Upgrade message header field (<a href="p1-messaging.html#header.upgrade" title="Upgrade">Section 6.5</a> of <a href="#Part1" id="rfc.xref.Part1.31"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>), for a change in the application protocol being used on this connection. The server will switch protocols to those defined1603 <h3 id="rfc.section.4.3.2"><a href="#rfc.section.4.3.2">4.3.2</a> <a id="status.101" href="#status.101">101 Switching Protocols</a></h3> 1604 <p id="rfc.section.4.3.2.p.1">The server understands and is willing to comply with the client's request, via the Upgrade message header field (<a href="p1-messaging.html#header.upgrade" title="Upgrade">Section 6.5</a> of <a href="#Part1" id="rfc.xref.Part1.31"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>), for a change in the application protocol being used on this connection. The server will switch protocols to those defined 1610 1605 by the response's Upgrade header field immediately after the empty line which terminates the 101 response. 1611 1606 </p> 1612 <p id="rfc.section.4.3. 1.2.p.2">The protocol <em class="bcp14">SHOULD</em> be switched only when it is advantageous to do so. For example, switching to a newer version of HTTP is advantageous over1607 <p id="rfc.section.4.3.2.p.2">The protocol <em class="bcp14">SHOULD</em> be switched only when it is advantageous to do so. For example, switching to a newer version of HTTP is advantageous over 1613 1608 older versions, and switching to a real-time, synchronous protocol might be advantageous when delivering resources that use 1614 1609 such features. 1615 1610 </p> 1616 <h 3 id="rfc.section.4.3.2"><a href="#rfc.section.4.3.2">4.3.2</a> <a id="status.2xx" href="#status.2xx">Successful 2xx</a></h3>1617 <p id="rfc.section.4. 3.2.p.1">This class of status code indicates that the client's request was successfully received, understood, and accepted.</p>1611 <h2 id="rfc.section.4.4"><a href="#rfc.section.4.4">4.4</a> <a id="status.2xx" href="#status.2xx">Successful 2xx</a></h2> 1612 <p id="rfc.section.4.4.p.1">This class of status code indicates that the client's request was successfully received, understood, and accepted.</p> 1618 1613 <div id="rfc.iref.24"></div> 1619 1614 <div id="rfc.iref.s.4"></div> 1620 <h 4 id="rfc.section.4.3.2.1"><a href="#rfc.section.4.3.2.1">4.3.2.1</a> <a id="status.200" href="#status.200">200 OK</a></h4>1621 <p id="rfc.section.4. 3.2.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>1615 <h3 id="rfc.section.4.4.1"><a href="#rfc.section.4.4.1">4.4.1</a> <a id="status.200" href="#status.200">200 OK</a></h3> 1616 <p id="rfc.section.4.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> 1622 1617 <dl> 1623 1618 <dt>GET</dt> … … 1630 1625 <dd>a representation containing the request message as received by the end server.</dd> 1631 1626 </dl> 1632 <p id="rfc.section.4. 3.2.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 2.3.1.1</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.1627 <p id="rfc.section.4.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 2.3.1.1</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. 1633 1628 </p> 1634 1629 <div id="rfc.iref.25"></div> 1635 1630 <div id="rfc.iref.s.5"></div> 1636 <h 4 id="rfc.section.4.3.2.2"><a href="#rfc.section.4.3.2.2">4.3.2.2</a> <a id="status.201" href="#status.201">201 Created</a></h4>1637 <p id="rfc.section.4. 3.2.2.p.1">The request has been fulfilled and has resulted in a new resource being created.</p>1638 <p id="rfc.section.4. 3.2.2.p.2">The newly created resource is typically linked to from the response payload, with the most relevant URI also being carried1631 <h3 id="rfc.section.4.4.2"><a href="#rfc.section.4.4.2">4.4.2</a> <a id="status.201" href="#status.201">201 Created</a></h3> 1632 <p id="rfc.section.4.4.2.p.1">The request has been fulfilled and has resulted in a new resource being created.</p> 1633 <p id="rfc.section.4.4.2.p.2">The newly created resource is typically linked to from the response payload, with the most relevant URI also being carried 1639 1634 in the Location header field. If the newly created resource's URI is the same as the Effective Request URI, this information 1640 1635 can be omitted (e.g., in the case of a response to a PUT request). 1641 1636 </p> 1642 <p id="rfc.section.4. 3.2.2.p.3">The origin server <em class="bcp14">MUST</em> create the resource before returning the 201 status code. If the action cannot be carried out immediately, the server <em class="bcp14">SHOULD</em> respond with 202 (Accepted) response instead.1643 </p> 1644 <p id="rfc.section.4. 3.2.2.p.4">A 201 response <em class="bcp14">MAY</em> contain an ETag response header field indicating the current value of the entity-tag for the representation of the resource1637 <p id="rfc.section.4.4.2.p.3">The origin server <em class="bcp14">MUST</em> create the resource before returning the 201 status code. If the action cannot be carried out immediately, the server <em class="bcp14">SHOULD</em> respond with 202 (Accepted) response instead. 1638 </p> 1639 <p id="rfc.section.4.4.2.p.4">A 201 response <em class="bcp14">MAY</em> contain an ETag response header field indicating the current value of the entity-tag for the representation of the resource 1645 1640 just created (see <a href="p4-conditional.html#header.etag" title="ETag">Section 2.3</a> of <a href="#Part4" id="rfc.xref.Part4.9"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>). 1646 1641 </p> 1647 1642 <div id="rfc.iref.26"></div> 1648 1643 <div id="rfc.iref.s.6"></div> 1649 <h 4 id="rfc.section.4.3.2.3"><a href="#rfc.section.4.3.2.3">4.3.2.3</a> <a id="status.202" href="#status.202">202 Accepted</a></h4>1650 <p id="rfc.section.4. 3.2.3.p.1">The request has been accepted for processing, but the processing has not been completed. The request might or might not eventually1644 <h3 id="rfc.section.4.4.3"><a href="#rfc.section.4.4.3">4.4.3</a> <a id="status.202" href="#status.202">202 Accepted</a></h3> 1645 <p id="rfc.section.4.4.3.p.1">The request has been accepted for processing, but the processing has not been completed. The request might or might not eventually 1651 1646 be acted upon, as it might be disallowed when processing actually takes place. There is no facility for re-sending a status 1652 1647 code from an asynchronous operation such as this. 1653 1648 </p> 1654 <p id="rfc.section.4. 3.2.3.p.2">The 202 response is intentionally non-committal. Its purpose is to allow a server to accept a request for some other process1649 <p id="rfc.section.4.4.3.p.2">The 202 response is intentionally non-committal. Its purpose is to allow a server to accept a request for some other process 1655 1650 (perhaps a batch-oriented process that is only run once per day) without requiring that the user agent's connection to the 1656 1651 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 … … 1659 1654 <div id="rfc.iref.27"></div> 1660 1655 <div id="rfc.iref.s.7"></div> 1661 <h 4 id="rfc.section.4.3.2.4"><a href="#rfc.section.4.3.2.4">4.3.2.4</a> <a id="status.203" href="#status.203">203 Non-Authoritative Information</a></h4>1662 <p id="rfc.section.4. 3.2.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.32"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[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 3.2</a> of <a href="#Part6" id="rfc.xref.Part6.12"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>).1663 </p> 1664 <p id="rfc.section.4. 3.2.4.p.2">This status code is only appropriate when the response status code would have been 200 (OK) otherwise. When the status code1656 <h3 id="rfc.section.4.4.4"><a href="#rfc.section.4.4.4">4.4.4</a> <a id="status.203" href="#status.203">203 Non-Authoritative Information</a></h3> 1657 <p id="rfc.section.4.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.32"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[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 3.2</a> of <a href="#Part6" id="rfc.xref.Part6.12"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>). 1658 </p> 1659 <p id="rfc.section.4.4.4.p.2">This status code is only appropriate when the response status code would have been 200 (OK) otherwise. When the status code 1665 1660 before transformation would have been different, the 214 Transformation Applied warn-code (<a href="p6-cache.html#header.warning" title="Warning">Section 3.6</a> of <a href="#Part6" id="rfc.xref.Part6.13"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>) is appropriate. 1666 1661 </p> 1667 <p id="rfc.section.4. 3.2.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 2.3.1.1</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.1662 <p id="rfc.section.4.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 2.3.1.1</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. 1668 1663 </p> 1669 1664 <div id="rfc.iref.28"></div> 1670 1665 <div id="rfc.iref.s.8"></div> 1671 <h 4 id="rfc.section.4.3.2.5"><a href="#rfc.section.4.3.2.5">4.3.2.5</a> <a id="status.204" href="#status.204">204 No Content</a></h4>1672 <p id="rfc.section.4. 3.2.5.p.1">The 204 (No Content) status code indicates that the server has successfully fulfilled the request and that there is no additional1666 <h3 id="rfc.section.4.4.5"><a href="#rfc.section.4.4.5">4.4.5</a> <a id="status.204" href="#status.204">204 No Content</a></h3> 1667 <p id="rfc.section.4.4.5.p.1">The 204 (No Content) status code indicates that the server has successfully fulfilled the request and that there is no additional 1673 1668 content to return in the response payload body. Metadata in the response header fields refer to the target resource and its 1674 1669 current representation after the requested action. 1675 1670 </p> 1676 <p id="rfc.section.4. 3.2.5.p.2">For example, if a 204 status code is received in response to a PUT request and the response contains an ETag header field,1671 <p id="rfc.section.4.4.5.p.2">For example, if a 204 status code is received in response to a PUT request and the response contains an ETag header field, 1677 1672 then the PUT was successful and the ETag field-value contains the entity-tag for the new representation of that target resource. 1678 1673 </p> 1679 <p id="rfc.section.4. 3.2.5.p.3">The 204 response allows a server to indicate that the action has been successfully applied to the target resource while implying1674 <p id="rfc.section.4.4.5.p.3">The 204 response allows a server to indicate that the action has been successfully applied to the target resource while implying 1680 1675 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 1681 1676 of the success to its user, in accord with its own interface, and apply any new or updated metadata in the response to the 1682 1677 active representation. 1683 1678 </p> 1684 <p id="rfc.section.4. 3.2.5.p.4">For example, a 204 status code is commonly used with document editing interfaces corresponding to a "save" action, such that1679 <p id="rfc.section.4.4.5.p.4">For example, a 204 status code is commonly used with document editing interfaces corresponding to a "save" action, such that 1685 1680 the document being saved remains available to the user for editing. It is also frequently used with interfaces that expect 1686 1681 automated data transfers to be prevalent, such as within distributed version control systems. 1687 1682 </p> 1688 <p id="rfc.section.4. 3.2.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.1683 <p id="rfc.section.4.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. 1689 1684 </p> 1690 1685 <div id="rfc.iref.29"></div> 1691 1686 <div id="rfc.iref.s.9"></div> 1692 <h 4 id="rfc.section.4.3.2.6"><a href="#rfc.section.4.3.2.6">4.3.2.6</a> <a id="status.205" href="#status.205">205 Reset Content</a></h4>1693 <p id="rfc.section.4. 3.2.6.p.1">The server has fulfilled the request and the user agent <em class="bcp14">SHOULD</em> reset the document view which caused the request to be sent. This response is primarily intended to allow input for actions1687 <h3 id="rfc.section.4.4.6"><a href="#rfc.section.4.4.6">4.4.6</a> <a id="status.205" href="#status.205">205 Reset Content</a></h3> 1688 <p id="rfc.section.4.4.6.p.1">The server has fulfilled the request and the user agent <em class="bcp14">SHOULD</em> reset the document view which caused the request to be sent. This response is primarily intended to allow input for actions 1694 1689 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 1695 1690 another input action. 1696 1691 </p> 1697 <p id="rfc.section.4. 3.2.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.33"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>.1698 </p> 1699 <h 3 id="rfc.section.4.3.3"><a href="#rfc.section.4.3.3">4.3.3</a> <a id="status.3xx" href="#status.3xx">Redirection 3xx</a></h3>1700 <p id="rfc.section.4. 3.3.p.1">This class of status code indicates that further action needs to be taken by the user agent in order to fulfill the request.1692 <p id="rfc.section.4.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.33"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>. 1693 </p> 1694 <h2 id="rfc.section.4.5"><a href="#rfc.section.4.5">4.5</a> <a id="status.3xx" href="#status.3xx">Redirection 3xx</a></h2> 1695 <p id="rfc.section.4.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. 1701 1696 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 1702 1697 known to be "safe", as defined in <a href="#safe.methods" title="Safe Methods">Section 2.1.1</a>. 1703 1698 </p> 1704 <p id="rfc.section.4. 3.3.p.2">There are several types of redirects: </p>1699 <p id="rfc.section.4.5.p.2">There are several types of redirects: </p> 1705 1700 <ol> 1706 1701 <li> … … 1724 1719 </li> 1725 1720 </ol> 1726 <div class="note" id="rfc.section.4. 3.3.p.3">1721 <div class="note" id="rfc.section.4.5.p.3"> 1727 1722 <p> <b>Note:</b> In HTTP/1.0, only the status codes 301 (Moved Permanently) and 302 (Found) were defined for the first type of redirect, and 1728 1723 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 … … 1733 1728 </p> 1734 1729 </div> 1735 <p id="rfc.section.4. 3.3.p.4">A Location 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 7.5</a>.1736 </p> 1737 <p id="rfc.section.4. 3.3.p.5">Note that for methods not known to be "safe", as defined in <a href="#safe.methods" title="Safe Methods">Section 2.1.1</a>, automatic redirection needs to done with care, since the redirect might change the conditions under which the request was1730 <p id="rfc.section.4.5.p.4">A Location 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 7.5</a>. 1731 </p> 1732 <p id="rfc.section.4.5.p.5">Note that for methods not known to be "safe", as defined in <a href="#safe.methods" title="Safe Methods">Section 2.1.1</a>, automatic redirection needs to done with care, since the redirect might change the conditions under which the request was 1738 1733 issued. 1739 1734 </p> 1740 <p id="rfc.section.4. 3.3.p.6">Clients <em class="bcp14">SHOULD</em> detect and intervene in cyclical redirections (i.e., "infinite" redirection loops).1741 </p> 1742 <div class="note" id="rfc.section.4. 3.3.p.7">1735 <p id="rfc.section.4.5.p.6">Clients <em class="bcp14">SHOULD</em> detect and intervene in cyclical redirections (i.e., "infinite" redirection loops). 1736 </p> 1737 <div class="note" id="rfc.section.4.5.p.7"> 1743 1738 <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. 1744 1739 </p> … … 1746 1741 <div id="rfc.iref.30"></div> 1747 1742 <div id="rfc.iref.s.10"></div> 1748 <h 4 id="rfc.section.4.3.3.1"><a href="#rfc.section.4.3.3.1">4.3.3.1</a> <a id="status.300" href="#status.300">300 Multiple Choices</a></h4>1749 <p id="rfc.section.4. 3.3.1.p.1">The target resource has more than one representation, each with its own specific location, and agent-driven negotiation information1743 <h3 id="rfc.section.4.5.1"><a href="#rfc.section.4.5.1">4.5.1</a> <a id="status.300" href="#status.300">300 Multiple Choices</a></h3> 1744 <p id="rfc.section.4.5.1.p.1">The target resource has more than one representation, each with its own specific location, and agent-driven negotiation information 1750 1745 (<a href="p3-payload.html#content.negotiation" title="Content Negotiation">Section 5</a> of <a href="#Part3" id="rfc.xref.Part3.10"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>) is being provided so that the user (or user agent) can select a preferred representation by redirecting its request to that 1751 1746 location. 1752 1747 </p> 1753 <p id="rfc.section.4. 3.3.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 can1748 <p id="rfc.section.4.5.1.p.2">Unless it was a HEAD request, the response <em class="bcp14">SHOULD</em> include a representation containing a list of representation metadata and location(s) from which the user or user agent can 1754 1749 choose the one most appropriate. Depending upon the format and the capabilities of the user agent, selection of the most appropriate 1755 1750 choice <em class="bcp14">MAY</em> be performed automatically. However, this specification does not define any standard for such automatic selection. 1756 1751 </p> 1757 <p id="rfc.section.4. 3.3.1.p.3">If the server has a preferred choice of representation, it <em class="bcp14">SHOULD</em> include the specific URI for that representation in the Location field; user agents <em class="bcp14">MAY</em> use the Location field value for automatic redirection.1758 </p> 1759 <p id="rfc.section.4. 3.3.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 2.3.1.1</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.1752 <p id="rfc.section.4.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 Location field; user agents <em class="bcp14">MAY</em> use the Location field value for automatic redirection. 1753 </p> 1754 <p id="rfc.section.4.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 2.3.1.1</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. 1760 1755 </p> 1761 1756 <div id="rfc.iref.31"></div> 1762 1757 <div id="rfc.iref.s.11"></div> 1763 <h 4 id="rfc.section.4.3.3.2"><a href="#rfc.section.4.3.3.2">4.3.3.2</a> <a id="status.301" href="#status.301">301 Moved Permanently</a></h4>1764 <p id="rfc.section.4. 3.3.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 effective1758 <h3 id="rfc.section.4.5.2"><a href="#rfc.section.4.5.2">4.5.2</a> <a id="status.301" href="#status.301">301 Moved Permanently</a></h3> 1759 <p id="rfc.section.4.5.2.p.1">The target resource has been assigned a new permanent URI and any future references to this resource <em class="bcp14">SHOULD</em> use one of the returned URIs. Clients with link editing capabilities ought to automatically re-link references to the effective 1765 1760 request URI to one or more of the new references returned by the server, where possible. 1766 1761 </p> 1767 <p id="rfc.section.4. 3.3.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 2.3.1.1</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.1768 </p> 1769 <p id="rfc.section.4. 3.3.2.p.3">The new permanent URI <em class="bcp14">SHOULD</em> be given by the Location field in the response. A response payload can contain a short hypertext note with a hyperlink to1762 <p id="rfc.section.4.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 2.3.1.1</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. 1763 </p> 1764 <p id="rfc.section.4.5.2.p.3">The new permanent URI <em class="bcp14">SHOULD</em> be given by the Location field in the response. A response payload can contain a short hypertext note with a hyperlink to 1770 1765 the new URI(s). 1771 1766 </p> 1772 <div class="note" id="rfc.section.4. 3.3.2.p.4">1767 <div class="note" id="rfc.section.4.5.2.p.4"> 1773 1768 <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 307 (Temporary 1774 1769 Redirect) can be used instead. … … 1777 1772 <div id="rfc.iref.32"></div> 1778 1773 <div id="rfc.iref.s.12"></div> 1779 <h 4 id="rfc.section.4.3.3.3"><a href="#rfc.section.4.3.3.3">4.3.3.3</a> <a id="status.302" href="#status.302">302 Found</a></h4>1780 <p id="rfc.section.4. 3.3.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.1781 </p> 1782 <p id="rfc.section.4. 3.3.3.p.2">The temporary URI <em class="bcp14">SHOULD</em> be given by the Location field in the response. A response payload can contain a short hypertext note with a hyperlink to1774 <h3 id="rfc.section.4.5.3"><a href="#rfc.section.4.5.3">4.5.3</a> <a id="status.302" href="#status.302">302 Found</a></h3> 1775 <p id="rfc.section.4.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. 1776 </p> 1777 <p id="rfc.section.4.5.3.p.2">The temporary URI <em class="bcp14">SHOULD</em> be given by the Location field in the response. A response payload can contain a short hypertext note with a hyperlink to 1783 1778 the new URI(s). 1784 1779 </p> 1785 <div class="note" id="rfc.section.4. 3.3.3.p.3">1780 <div class="note" id="rfc.section.4.5.3.p.3"> 1786 1781 <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 307 (Temporary 1787 1782 Redirect) can be used instead. … … 1790 1785 <div id="rfc.iref.33"></div> 1791 1786 <div id="rfc.iref.s.13"></div> 1792 <h 4 id="rfc.section.4.3.3.4"><a href="#rfc.section.4.3.3.4">4.3.3.4</a> <a id="status.303" href="#status.303">303 See Other</a></h4>1793 <p id="rfc.section.4. 3.3.4.p.1">The 303 status code indicates that the server is redirecting the user agent to a different resource, as indicated by a URI1787 <h3 id="rfc.section.4.5.4"><a href="#rfc.section.4.5.4">4.5.4</a> <a id="status.303" href="#status.303">303 See Other</a></h3> 1788 <p id="rfc.section.4.5.4.p.1">The 303 status code indicates that the server is redirecting the user agent to a different resource, as indicated by a URI 1794 1789 in the Location header field, that is intended to provide an indirect response to the original request. In order to satisfy 1795 1790 the original request, 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 may itself be redirected further, … … 1797 1792 not considered equivalent to the effective request URI. 1798 1793 </p> 1799 <p id="rfc.section.4. 3.3.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 to1794 <p id="rfc.section.4.5.4.p.2">This status code is generally applicable to any HTTP method. It is primarily used to allow the output of a POST action to 1800 1795 redirect the user agent to a selected resource, since doing so provides the information corresponding to the POST response 1801 1796 in a form that can be separately identified, bookmarked, and cached independent of the original request. 1802 1797 </p> 1803 <p id="rfc.section.4. 3.3.4.p.3">A 303 response to a GET request indicates that the requested resource does not have a representation of its own that can be1798 <p id="rfc.section.4.5.4.p.3">A 303 response to a GET request indicates that the requested resource does not have a representation of its own that can be 1804 1799 transferred by the server over HTTP. The Location URI indicates a resource that is descriptive of the target resource, such 1805 1800 that the follow-on representation might be useful to recipients without implying that it adequately represents the target … … 1807 1802 be a useful description are outside the scope of HTTP and thus entirely determined by the URI owner(s). 1808 1803 </p> 1809 <p id="rfc.section.4. 3.3.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 Location URI.1804 <p id="rfc.section.4.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 Location URI. 1810 1805 </p> 1811 1806 <div id="rfc.iref.34"></div> 1812 1807 <div id="rfc.iref.s.14"></div> 1813 <h 4 id="rfc.section.4.3.3.5"><a href="#rfc.section.4.3.3.5">4.3.3.5</a> <a id="status.305" href="#status.305">305 Use Proxy</a></h4>1814 <p id="rfc.section.4. 3.3.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 A</a>), and is now deprecated.1808 <h3 id="rfc.section.4.5.5"><a href="#rfc.section.4.5.5">4.5.5</a> <a id="status.305" href="#status.305">305 Use Proxy</a></h3> 1809 <p id="rfc.section.4.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 A</a>), and is now deprecated. 1815 1810 </p> 1816 1811 <div id="rfc.iref.35"></div> 1817 1812 <div id="rfc.iref.s.15"></div> 1818 <h 4 id="rfc.section.4.3.3.6"><a href="#rfc.section.4.3.3.6">4.3.3.6</a> <a id="status.306" href="#status.306">306 (Unused)</a></h4>1819 <p id="rfc.section.4. 3.3.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>1813 <h3 id="rfc.section.4.5.6"><a href="#rfc.section.4.5.6">4.5.6</a> <a id="status.306" href="#status.306">306 (Unused)</a></h3> 1814 <p id="rfc.section.4.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> 1820 1815 <div id="rfc.iref.36"></div> 1821 1816 <div id="rfc.iref.s.16"></div> 1822 <h 4 id="rfc.section.4.3.3.7"><a href="#rfc.section.4.3.3.7">4.3.3.7</a> <a id="status.307" href="#status.307">307 Temporary Redirect</a></h4>1823 <p id="rfc.section.4. 3.3.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.1824 </p> 1825 <p id="rfc.section.4. 3.3.7.p.2">The temporary URI <em class="bcp14">SHOULD</em> be given by the Location field in the response. A response payload can contain a short hypertext note with a hyperlink to1817 <h3 id="rfc.section.4.5.7"><a href="#rfc.section.4.5.7">4.5.7</a> <a id="status.307" href="#status.307">307 Temporary Redirect</a></h3> 1818 <p id="rfc.section.4.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. 1819 </p> 1820 <p id="rfc.section.4.5.7.p.2">The temporary URI <em class="bcp14">SHOULD</em> be given by the Location field in the response. A response payload can contain a short hypertext note with a hyperlink to 1826 1821 the new URI(s). 1827 1822 </p> 1828 <div class="note" id="rfc.section.4. 3.3.7.p.3">1823 <div class="note" id="rfc.section.4.5.7.p.3"> 1829 1824 <p> <b>Note:</b> This status code is similar to 302 Found, except that it does not allow rewriting the request method from POST to GET. This 1830 1825 specification defines no equivalent counterpart for 301 Moved Permanently (<a href="#draft-reschke-http-status-308" id="rfc.xref.draft-reschke-http-status-308.1"><cite title="The Hypertext Transfer Protocol (HTTP) Status Code 308 (Permanent Redirect)">[draft-reschke-http-status-308]</cite></a>, however, defines the status code 308 Permanent Redirect for this purpose). 1831 1826 </p> 1832 1827 </div> 1833 <h 3 id="rfc.section.4.3.4"><a href="#rfc.section.4.3.4">4.3.4</a> <a id="status.4xx" href="#status.4xx">Client Error 4xx</a></h3>1834 <p id="rfc.section.4. 3.4.p.1">The 4xx class of status code is intended for cases in which the client seems to have erred. Except when responding to a HEAD1828 <h2 id="rfc.section.4.6"><a href="#rfc.section.4.6">4.6</a> <a id="status.4xx" href="#status.4xx">Client Error 4xx</a></h2> 1829 <p id="rfc.section.4.6.p.1">The 4xx class of status code is intended for cases in which the client seems to have erred. Except when responding to a HEAD 1835 1830 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. 1836 1831 These status codes are applicable to any request method. User agents <em class="bcp14">SHOULD</em> display any included representation to the user. … … 1838 1833 <div id="rfc.iref.37"></div> 1839 1834 <div id="rfc.iref.s.17"></div> 1840 <h 4 id="rfc.section.4.3.4.1"><a href="#rfc.section.4.3.4.1">4.3.4.1</a> <a id="status.400" href="#status.400">400 Bad Request</a></h4>1841 <p id="rfc.section.4. 3.4.1.p.1">The server cannot or will not process the request, due to a client error (e.g., malformed syntax).</p>1835 <h3 id="rfc.section.4.6.1"><a href="#rfc.section.4.6.1">4.6.1</a> <a id="status.400" href="#status.400">400 Bad Request</a></h3> 1836 <p id="rfc.section.4.6.1.p.1">The server cannot or will not process the request, due to a client error (e.g., malformed syntax).</p> 1842 1837 <div id="rfc.iref.38"></div> 1843 1838 <div id="rfc.iref.s.18"></div> 1844 <h 4 id="rfc.section.4.3.4.2"><a href="#rfc.section.4.3.4.2">4.3.4.2</a> <a id="status.402" href="#status.402">402 Payment Required</a></h4>1845 <p id="rfc.section.4. 3.4.2.p.1">This code is reserved for future use.</p>1839 <h3 id="rfc.section.4.6.2"><a href="#rfc.section.4.6.2">4.6.2</a> <a id="status.402" href="#status.402">402 Payment Required</a></h3> 1840 <p id="rfc.section.4.6.2.p.1">This code is reserved for future use.</p> 1846 1841 <div id="rfc.iref.39"></div> 1847 1842 <div id="rfc.iref.s.19"></div> 1848 <h 4 id="rfc.section.4.3.4.3"><a href="#rfc.section.4.3.4.3">4.3.4.3</a> <a id="status.403" href="#status.403">403 Forbidden</a></h4>1849 <p id="rfc.section.4. 3.4.3.p.1">The server understood the request, but refuses to authorize it. Providing different user authentication credentials might1843 <h3 id="rfc.section.4.6.3"><a href="#rfc.section.4.6.3">4.6.3</a> <a id="status.403" href="#status.403">403 Forbidden</a></h3> 1844 <p id="rfc.section.4.6.3.p.1">The server understood the request, but refuses to authorize it. Providing different user authentication credentials might 1850 1845 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. 1851 1846 </p> 1852 <p id="rfc.section.4. 3.4.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 available1847 <p id="rfc.section.4.6.3.p.2">If the request method was not HEAD and the server wishes to make public why the request has not been fulfilled, it <em class="bcp14">SHOULD</em> describe the reason for the refusal in the representation. If the server does not wish to make this information available 1853 1848 to the client, the status code 404 (Not Found) <em class="bcp14">MAY</em> be used instead. 1854 1849 </p> 1855 1850 <div id="rfc.iref.40"></div> 1856 1851 <div id="rfc.iref.s.20"></div> 1857 <h 4 id="rfc.section.4.3.4.4"><a href="#rfc.section.4.3.4.4">4.3.4.4</a> <a id="status.404" href="#status.404">404 Not Found</a></h4>1858 <p id="rfc.section.4. 3.4.4.p.1">The server has not found anything matching the effective request URI. No indication is given of whether the condition is temporary1852 <h3 id="rfc.section.4.6.4"><a href="#rfc.section.4.6.4">4.6.4</a> <a id="status.404" href="#status.404">404 Not Found</a></h3> 1853 <p id="rfc.section.4.6.4.p.1">The server has not found anything matching the effective request URI. No indication is given of whether the condition is temporary 1859 1854 or permanent. The 410 (Gone) status code <em class="bcp14">SHOULD</em> be used if the server knows, through some internally configurable mechanism, that an old resource is permanently unavailable 1860 1855 and has no forwarding address. This status code is commonly used when the server does not wish to reveal exactly why the request … … 1863 1858 <div id="rfc.iref.41"></div> 1864 1859 <div id="rfc.iref.s.21"></div> 1865 <h 4 id="rfc.section.4.3.4.5"><a href="#rfc.section.4.3.4.5">4.3.4.5</a> <a id="status.405" href="#status.405">405 Method Not Allowed</a></h4>1866 <p id="rfc.section.4. 3.4.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 Allow header field containing a list of valid methods for the requested resource.1860 <h3 id="rfc.section.4.6.5"><a href="#rfc.section.4.6.5">4.6.5</a> <a id="status.405" href="#status.405">405 Method Not Allowed</a></h3> 1861 <p id="rfc.section.4.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 Allow header field containing a list of valid methods for the requested resource. 1867 1862 </p> 1868 1863 <div id="rfc.iref.42"></div> 1869 1864 <div id="rfc.iref.s.22"></div> 1870 <h 4 id="rfc.section.4.3.4.6"><a href="#rfc.section.4.3.4.6">4.3.4.6</a> <a id="status.406" href="#status.406">406 Not Acceptable</a></h4>1871 <p id="rfc.section.4. 3.4.6.p.1">The resource identified by the request is only capable of generating response representations which have content characteristics1865 <h3 id="rfc.section.4.6.6"><a href="#rfc.section.4.6.6">4.6.6</a> <a id="status.406" href="#status.406">406 Not Acceptable</a></h3> 1866 <p id="rfc.section.4.6.6.p.1">The resource identified by the request is only capable of generating response representations which have content characteristics 1872 1867 not acceptable according to the Accept and Accept-* header fields sent in the request (see <a href="p3-payload.html#header.field.definitions" title="Header Field Definitions">Section 6</a> of <a href="#Part3" id="rfc.xref.Part3.11"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>). 1873 1868 </p> 1874 <p id="rfc.section.4. 3.4.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 user1869 <p id="rfc.section.4.6.6.p.2">Unless it was a HEAD request, the response <em class="bcp14">SHOULD</em> include a representation containing a list of available representation characteristics and location(s) from which the user 1875 1870 or user agent can choose the one most appropriate. Depending upon the format and the capabilities of the user agent, selection 1876 1871 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. 1877 1872 </p> 1878 <div class="note" id="rfc.section.4. 3.4.6.p.3">1873 <div class="note" id="rfc.section.4.6.6.p.3"> 1879 1874 <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 1880 1875 request. In some cases, this might even be preferable to sending a 406 response. User agents are encouraged to inspect the … … 1882 1877 </p> 1883 1878 </div> 1884 <p id="rfc.section.4. 3.4.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.1879 <p id="rfc.section.4.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. 1885 1880 </p> 1886 1881 <div id="rfc.iref.43"></div> 1887 1882 <div id="rfc.iref.s.23"></div> 1888 <h 4 id="rfc.section.4.3.4.7"><a href="#rfc.section.4.3.4.7">4.3.4.7</a> <a id="status.408" href="#status.408">408 Request Timeout</a></h4>1889 <p id="rfc.section.4. 3.4.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.1883 <h3 id="rfc.section.4.6.7"><a href="#rfc.section.4.6.7">4.6.7</a> <a id="status.408" href="#status.408">408 Request Timeout</a></h3> 1884 <p id="rfc.section.4.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. 1890 1885 </p> 1891 1886 <div id="rfc.iref.44"></div> 1892 1887 <div id="rfc.iref.s.24"></div> 1893 <h 4 id="rfc.section.4.3.4.8"><a href="#rfc.section.4.3.4.8">4.3.4.8</a> <a id="status.409" href="#status.409">409 Conflict</a></h4>1894 <p id="rfc.section.4. 3.4.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 in1888 <h3 id="rfc.section.4.6.8"><a href="#rfc.section.4.6.8">4.6.8</a> <a id="status.409" href="#status.409">409 Conflict</a></h3> 1889 <p id="rfc.section.4.6.8.p.1">The request could not be completed due to a conflict with the current state of the resource. This code is only allowed in 1895 1890 situations where it is expected that the user might be able to resolve the conflict and resubmit the request. The response 1896 1891 body <em class="bcp14">SHOULD</em> include enough information for the user to recognize the source of the conflict. Ideally, the response representation would 1897 1892 include enough information for the user or user agent to fix the problem; however, that might not be possible and is not required. 1898 1893 </p> 1899 <p id="rfc.section.4. 3.4.8.p.2">Conflicts are most likely to occur in response to a PUT request. For example, if versioning were being used and the representation1894 <p id="rfc.section.4.6.8.p.2">Conflicts are most likely to occur in response to a PUT request. For example, if versioning were being used and the representation 1900 1895 being PUT included changes to a resource which conflict with those made by an earlier (third-party) request, the server might 1901 1896 use the 409 response to indicate that it can't complete the request. In this case, the response representation would likely … … 1904 1899 <div id="rfc.iref.45"></div> 1905 1900 <div id="rfc.iref.s.25"></div> 1906 <h 4 id="rfc.section.4.3.4.9"><a href="#rfc.section.4.3.4.9">4.3.4.9</a> <a id="status.410" href="#status.410">410 Gone</a></h4>1907 <p id="rfc.section.4. 3.4.9.p.1">The target resource is no longer available at the server and no forwarding address is known. This condition is expected to1901 <h3 id="rfc.section.4.6.9"><a href="#rfc.section.4.6.9">4.6.9</a> <a id="status.410" href="#status.410">410 Gone</a></h3> 1902 <p id="rfc.section.4.6.9.p.1">The target resource is no longer available at the server and no forwarding address is known. This condition is expected to 1908 1903 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, 1909 1904 whether or not the condition is permanent, the status code 404 (Not Found) <em class="bcp14">SHOULD</em> be used instead. 1910 1905 </p> 1911 <p id="rfc.section.4. 3.4.9.p.2">The 410 response is primarily intended to assist the task of web maintenance by notifying the recipient that the resource1906 <p id="rfc.section.4.6.9.p.2">The 410 response is primarily intended to assist the task of web maintenance by notifying the recipient that the resource 1912 1907 is intentionally unavailable and that the server owners desire that remote links to that resource be removed. Such an event 1913 1908 is common for limited-time, promotional services and for resources belonging to individuals no longer working at the server's … … 1915 1910 — that is left to the discretion of the server owner. 1916 1911 </p> 1917 <p id="rfc.section.4. 3.4.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 2.3.1.1</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.1912 <p id="rfc.section.4.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 2.3.1.1</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. 1918 1913 </p> 1919 1914 <div id="rfc.iref.46"></div> 1920 1915 <div id="rfc.iref.s.26"></div> 1921 <h 4 id="rfc.section.4.3.4.10"><a href="#rfc.section.4.3.4.10">4.3.4.10</a> <a id="status.411" href="#status.411">411 Length Required</a></h4>1922 <p id="rfc.section.4. 3.4.10.p.1">The server refuses to accept the request without a defined Content-Length. The client <em class="bcp14">MAY</em> repeat the request if it adds a valid Content-Length header field containing the length of the message body in the request1916 <h3 id="rfc.section.4.6.10"><a href="#rfc.section.4.6.10">4.6.10</a> <a id="status.411" href="#status.411">411 Length Required</a></h3> 1917 <p id="rfc.section.4.6.10.p.1">The server refuses to accept the request without a defined Content-Length. The client <em class="bcp14">MAY</em> repeat the request if it adds a valid Content-Length header field containing the length of the message body in the request 1923 1918 message. 1924 1919 </p> 1925 1920 <div id="rfc.iref.47"></div> 1926 1921 <div id="rfc.iref.s.27"></div> 1927 <h 4 id="rfc.section.4.3.4.11"><a href="#rfc.section.4.3.4.11">4.3.4.11</a> <a id="status.413" href="#status.413">413 Request Representation Too Large</a></h4>1928 <p id="rfc.section.4. 3.4.11.p.1">The server is refusing to process a request because the request representation is larger than the server is willing or able1922 <h3 id="rfc.section.4.6.11"><a href="#rfc.section.4.6.11">4.6.11</a> <a id="status.413" href="#status.413">413 Request Representation Too Large</a></h3> 1923 <p id="rfc.section.4.6.11.p.1">The server is refusing to process a request because the request representation is larger than the server is willing or able 1929 1924 to process. The server <em class="bcp14">MAY</em> close the connection to prevent the client from continuing the request. 1930 1925 </p> 1931 <p id="rfc.section.4. 3.4.11.p.2">If the condition is temporary, the server <em class="bcp14">SHOULD</em> include a Retry-After header field to indicate that it is temporary and after what time the client <em class="bcp14">MAY</em> try again.1926 <p id="rfc.section.4.6.11.p.2">If the condition is temporary, the server <em class="bcp14">SHOULD</em> include a Retry-After header field to indicate that it is temporary and after what time the client <em class="bcp14">MAY</em> try again. 1932 1927 </p> 1933 1928 <div id="rfc.iref.48"></div> 1934 1929 <div id="rfc.iref.s.28"></div> 1935 <h 4 id="rfc.section.4.3.4.12"><a href="#rfc.section.4.3.4.12">4.3.4.12</a> <a id="status.414" href="#status.414">414 URI Too Long</a></h4>1936 <p id="rfc.section.4. 3.4.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.1930 <h3 id="rfc.section.4.6.12"><a href="#rfc.section.4.6.12">4.6.12</a> <a id="status.414" href="#status.414">414 URI Too Long</a></h3> 1931 <p id="rfc.section.4.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. 1937 1932 This rare condition is only likely to occur when a client has improperly converted a POST request to a GET request with long 1938 1933 query information, when the client has descended into a URI "black hole" of redirection (e.g., a redirected URI prefix that … … 1942 1937 <div id="rfc.iref.49"></div> 1943 1938 <div id="rfc.iref.s.29"></div> 1944 <h 4 id="rfc.section.4.3.4.13"><a href="#rfc.section.4.3.4.13">4.3.4.13</a> <a id="status.415" href="#status.415">415 Unsupported Media Type</a></h4>1945 <p id="rfc.section.4. 3.4.13.p.1">The server is refusing to service the request because the request payload is in a format not supported by this request method1939 <h3 id="rfc.section.4.6.13"><a href="#rfc.section.4.6.13">4.6.13</a> <a id="status.415" href="#status.415">415 Unsupported Media Type</a></h3> 1940 <p id="rfc.section.4.6.13.p.1">The server is refusing to service the request because the request payload is in a format not supported by this request method 1946 1941 on the target resource. 1947 1942 </p> 1948 1943 <div id="rfc.iref.50"></div> 1949 1944 <div id="rfc.iref.s.30"></div> 1950 <h 4 id="rfc.section.4.3.4.14"><a href="#rfc.section.4.3.4.14">4.3.4.14</a> <a id="status.417" href="#status.417">417 Expectation Failed</a></h4>1951 <p id="rfc.section.4. 3.4.14.p.1">The expectation given in an Expect header field (see <a href="#header.expect" id="rfc.xref.header.expect.2" title="Expect">Section 7.3</a>) could not be met by this server, or, if the server is a proxy, the server has unambiguous evidence that the request could1945 <h3 id="rfc.section.4.6.14"><a href="#rfc.section.4.6.14">4.6.14</a> <a id="status.417" href="#status.417">417 Expectation Failed</a></h3> 1946 <p id="rfc.section.4.6.14.p.1">The expectation given in an Expect header field (see <a href="#header.expect" id="rfc.xref.header.expect.2" title="Expect">Section 7.3</a>) could not be met by this server, or, if the server is a proxy, the server has unambiguous evidence that the request could 1952 1947 not be met by the next-hop server. 1953 1948 </p> 1954 1949 <div id="rfc.iref.51"></div> 1955 1950 <div id="rfc.iref.s.31"></div> 1956 <h 4 id="rfc.section.4.3.4.15"><a href="#rfc.section.4.3.4.15">4.3.4.15</a> <a id="status.426" href="#status.426">426 Upgrade Required</a></h4>1957 <p id="rfc.section.4. 3.4.15.p.1">The request can not be completed without a prior protocol upgrade. This response <em class="bcp14">MUST</em> include an Upgrade header field (<a href="p1-messaging.html#header.upgrade" title="Upgrade">Section 6.5</a> of <a href="#Part1" id="rfc.xref.Part1.34"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) specifying the required protocols.1951 <h3 id="rfc.section.4.6.15"><a href="#rfc.section.4.6.15">4.6.15</a> <a id="status.426" href="#status.426">426 Upgrade Required</a></h3> 1952 <p id="rfc.section.4.6.15.p.1">The request can not be completed without a prior protocol upgrade. This response <em class="bcp14">MUST</em> include an Upgrade header field (<a href="p1-messaging.html#header.upgrade" title="Upgrade">Section 6.5</a> of <a href="#Part1" id="rfc.xref.Part1.34"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) specifying the required protocols. 1958 1953 </p> 1959 1954 <div id="rfc.figure.u.8"></div> … … 1965 1960 1966 1961 <span id="s426body">This service requires use of the HTTP/3.0 protocol. 1967 </span></pre><p id="rfc.section.4. 3.4.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 any1962 </span></pre><p id="rfc.section.4.6.15.p.3">The server <em class="bcp14">SHOULD</em> include a message body in the 426 response which indicates in human readable form the reason for the error and describes any 1968 1963 alternative courses which may be available to the user. 1969 1964 </p> 1970 <h 3 id="rfc.section.4.3.5"><a href="#rfc.section.4.3.5">4.3.5</a> <a id="status.5xx" href="#status.5xx">Server Error 5xx</a></h3>1971 <p id="rfc.section.4. 3.5.p.1">Response status codes beginning with the digit "5" indicate cases in which the server is aware that it has erred or is incapable1965 <h2 id="rfc.section.4.7"><a href="#rfc.section.4.7">4.7</a> <a id="status.5xx" href="#status.5xx">Server Error 5xx</a></h2> 1966 <p id="rfc.section.4.7.p.1">Response status codes beginning with the digit "5" indicate cases in which the server is aware that it has erred or is incapable 1972 1967 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. 1973 1968 User agents <em class="bcp14">SHOULD</em> display any included representation to the user. These response codes are applicable to any request method. … … 1975 1970 <div id="rfc.iref.52"></div> 1976 1971 <div id="rfc.iref.s.32"></div> 1977 <h 4 id="rfc.section.4.3.5.1"><a href="#rfc.section.4.3.5.1">4.3.5.1</a> <a id="status.500" href="#status.500">500 Internal Server Error</a></h4>1978 <p id="rfc.section.4. 3.5.1.p.1">The server encountered an unexpected condition which prevented it from fulfilling the request.</p>1972 <h3 id="rfc.section.4.7.1"><a href="#rfc.section.4.7.1">4.7.1</a> <a id="status.500" href="#status.500">500 Internal Server Error</a></h3> 1973 <p id="rfc.section.4.7.1.p.1">The server encountered an unexpected condition which prevented it from fulfilling the request.</p> 1979 1974 <div id="rfc.iref.53"></div> 1980 1975 <div id="rfc.iref.s.33"></div> 1981 <h 4 id="rfc.section.4.3.5.2"><a href="#rfc.section.4.3.5.2">4.3.5.2</a> <a id="status.501" href="#status.501">501 Not Implemented</a></h4>1982 <p id="rfc.section.4. 3.5.2.p.1">The server does not support the functionality required to fulfill the request. This is the appropriate response when the server1976 <h3 id="rfc.section.4.7.2"><a href="#rfc.section.4.7.2">4.7.2</a> <a id="status.501" href="#status.501">501 Not Implemented</a></h3> 1977 <p id="rfc.section.4.7.2.p.1">The server does not support the functionality required to fulfill the request. This is the appropriate response when the server 1983 1978 does not recognize the request method and is not capable of supporting it for any resource. 1984 1979 </p> 1985 1980 <div id="rfc.iref.54"></div> 1986 1981 <div id="rfc.iref.s.34"></div> 1987 <h 4 id="rfc.section.4.3.5.3"><a href="#rfc.section.4.3.5.3">4.3.5.3</a> <a id="status.502" href="#status.502">502 Bad Gateway</a></h4>1988 <p id="rfc.section.4. 3.5.3.p.1">The server, while acting as a gateway or proxy, received an invalid response from the upstream server it accessed in attempting1982 <h3 id="rfc.section.4.7.3"><a href="#rfc.section.4.7.3">4.7.3</a> <a id="status.502" href="#status.502">502 Bad Gateway</a></h3> 1983 <p id="rfc.section.4.7.3.p.1">The server, while acting as a gateway or proxy, received an invalid response from the upstream server it accessed in attempting 1989 1984 to fulfill the request. 1990 1985 </p> 1991 1986 <div id="rfc.iref.55"></div> 1992 1987 <div id="rfc.iref.s.35"></div> 1993 <h 4 id="rfc.section.4.3.5.4"><a href="#rfc.section.4.3.5.4">4.3.5.4</a> <a id="status.503" href="#status.503">503 Service Unavailable</a></h4>1994 <p id="rfc.section.4. 3.5.4.p.1">The server is currently unable to handle the request due to a temporary overloading or maintenance of the server.</p>1995 <p id="rfc.section.4. 3.5.4.p.2">The implication is that this is a temporary condition which will be alleviated after some delay. If known, the length of the1988 <h3 id="rfc.section.4.7.4"><a href="#rfc.section.4.7.4">4.7.4</a> <a id="status.503" href="#status.503">503 Service Unavailable</a></h3> 1989 <p id="rfc.section.4.7.4.p.1">The server is currently unable to handle the request due to a temporary overloading or maintenance of the server.</p> 1990 <p id="rfc.section.4.7.4.p.2">The implication is that this is a temporary condition which will be alleviated after some delay. If known, the length of the 1996 1991 delay <em class="bcp14">MAY</em> be indicated in a Retry-After header field (<a href="#header.retry-after" id="rfc.xref.header.retry-after.2" title="Retry-After">Section 7.8</a>). If no Retry-After is given, the client <em class="bcp14">SHOULD</em> handle the response as it would for a 500 response. 1997 1992 </p> 1998 <div class="note" id="rfc.section.4. 3.5.4.p.3">1993 <div class="note" id="rfc.section.4.7.4.p.3"> 1999 1994 <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 2000 1995 wish to simply refuse the connection. … … 2003 1998 <div id="rfc.iref.56"></div> 2004 1999 <div id="rfc.iref.s.36"></div> 2005 <h 4 id="rfc.section.4.3.5.5"><a href="#rfc.section.4.3.5.5">4.3.5.5</a> <a id="status.504" href="#status.504">504 Gateway Timeout</a></h4>2006 <p id="rfc.section.4. 3.5.5.p.1">The server, while acting as a gateway or proxy, did not receive a timely response from the upstream server specified by the2000 <h3 id="rfc.section.4.7.5"><a href="#rfc.section.4.7.5">4.7.5</a> <a id="status.504" href="#status.504">504 Gateway Timeout</a></h3> 2001 <p id="rfc.section.4.7.5.p.1">The server, while acting as a gateway or proxy, did not receive a timely response from the upstream server specified by the 2007 2002 URI (e.g., HTTP, FTP, LDAP) or some other auxiliary server (e.g., DNS) it needed to access in attempting to complete the request. 2008 2003 </p> 2009 <div class="note" id="rfc.section.4. 3.5.5.p.2">2004 <div class="note" id="rfc.section.4.7.5.p.2"> 2010 2005 <p> <b>Note</b> to implementors: some deployed proxies are known to return 400 or 500 when DNS lookups time out. 2011 2006 </p> … … 2013 2008 <div id="rfc.iref.57"></div> 2014 2009 <div id="rfc.iref.s.37"></div> 2015 <h 4 id="rfc.section.4.3.5.6"><a href="#rfc.section.4.3.5.6">4.3.5.6</a> <a id="status.505" href="#status.505">505 HTTP Version Not Supported</a></h4>2016 <p id="rfc.section.4. 3.5.6.p.1">The server does not support, or refuses to support, the protocol version that was used in the request message. The server2010 <h3 id="rfc.section.4.7.6"><a href="#rfc.section.4.7.6">4.7.6</a> <a id="status.505" href="#status.505">505 HTTP Version Not Supported</a></h3> 2011 <p id="rfc.section.4.7.6.p.1">The server does not support, or refuses to support, the protocol version that was used in the request message. The server 2017 2012 is indicating that it is unable or unwilling to complete the request using the same major version as the client, as described 2018 2013 in <a href="p1-messaging.html#http.version" title="Protocol Versioning">Section 2.6</a> of <a href="#Part1" id="rfc.xref.Part1.35"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, other than with this error message. The response <em class="bcp14">SHOULD</em> contain a representation describing why that version is not supported and what other protocols are supported by that server. … … 2449 2444 <td class="left">100</td> 2450 2445 <td class="left">Continue</td> 2451 <td class="left"> <a href="#status.100" id="rfc.xref.status.100.2" title="100 Continue">Section 4.3.1 .1</a>2446 <td class="left"> <a href="#status.100" id="rfc.xref.status.100.2" title="100 Continue">Section 4.3.1</a> 2452 2447 </td> 2453 2448 </tr> … … 2455 2450 <td class="left">101</td> 2456 2451 <td class="left">Switching Protocols</td> 2457 <td class="left"> <a href="#status.101" id="rfc.xref.status.101.2" title="101 Switching Protocols">Section 4.3. 1.2</a>2452 <td class="left"> <a href="#status.101" id="rfc.xref.status.101.2" title="101 Switching Protocols">Section 4.3.2</a> 2458 2453 </td> 2459 2454 </tr> … … 2461 2456 <td class="left">200</td> 2462 2457 <td class="left">OK</td> 2463 <td class="left"> <a href="#status.200" id="rfc.xref.status.200.2" title="200 OK">Section 4. 3.2.1</a>2458 <td class="left"> <a href="#status.200" id="rfc.xref.status.200.2" title="200 OK">Section 4.4.1</a> 2464 2459 </td> 2465 2460 </tr> … … 2467 2462 <td class="left">201</td> 2468 2463 <td class="left">Created</td> 2469 <td class="left"> <a href="#status.201" id="rfc.xref.status.201.2" title="201 Created">Section 4. 3.2.2</a>2464 <td class="left"> <a href="#status.201" id="rfc.xref.status.201.2" title="201 Created">Section 4.4.2</a> 2470 2465 </td> 2471 2466 </tr> … … 2473 2468 <td class="left">202</td> 2474 2469 <td class="left">Accepted</td> 2475 <td class="left"> <a href="#status.202" id="rfc.xref.status.202.2" title="202 Accepted">Section 4. 3.2.3</a>2470 <td class="left"> <a href="#status.202" id="rfc.xref.status.202.2" title="202 Accepted">Section 4.4.3</a> 2476 2471 </td> 2477 2472 </tr> … … 2479 2474 <td class="left">203</td> 2480 2475 <td class="left">Non-Authoritative Information</td> 2481 <td class="left"> <a href="#status.203" id="rfc.xref.status.203.2" title="203 Non-Authoritative Information">Section 4. 3.2.4</a>2476 <td class="left"> <a href="#status.203" id="rfc.xref.status.203.2" title="203 Non-Authoritative Information">Section 4.4.4</a> 2482 2477 </td> 2483 2478 </tr> … … 2485 2480 <td class="left">204</td> 2486 2481 <td class="left">No Content</td> 2487 <td class="left"> <a href="#status.204" id="rfc.xref.status.204.2" title="204 No Content">Section 4. 3.2.5</a>2482 <td class="left"> <a href="#status.204" id="rfc.xref.status.204.2" title="204 No Content">Section 4.4.5</a> 2488 2483 </td> 2489 2484 </tr> … … 2491 2486 <td class="left">205</td> 2492 2487 <td class="left">Reset Content</td> 2493 <td class="left"> <a href="#status.205" id="rfc.xref.status.205.2" title="205 Reset Content">Section 4. 3.2.6</a>2488 <td class="left"> <a href="#status.205" id="rfc.xref.status.205.2" title="205 Reset Content">Section 4.4.6</a> 2494 2489 </td> 2495 2490 </tr> … … 2497 2492 <td class="left">300</td> 2498 2493 <td class="left">Multiple Choices</td> 2499 <td class="left"> <a href="#status.300" id="rfc.xref.status.300.2" title="300 Multiple Choices">Section 4. 3.3.1</a>2494 <td class="left"> <a href="#status.300" id="rfc.xref.status.300.2" title="300 Multiple Choices">Section 4.5.1</a> 2500 2495 </td> 2501 2496 </tr> … … 2503 2498 <td class="left">301</td> 2504 2499 <td class="left">Moved Permanently</td> 2505 <td class="left"> <a href="#status.301" id="rfc.xref.status.301.2" title="301 Moved Permanently">Section 4. 3.3.2</a>2500 <td class="left"> <a href="#status.301" id="rfc.xref.status.301.2" title="301 Moved Permanently">Section 4.5.2</a> 2506 2501 </td> 2507 2502 </tr> … … 2509 2504 <td class="left">302</td> 2510 2505 <td class="left">Found</td> 2511 <td class="left"> <a href="#status.302" id="rfc.xref.status.302.2" title="302 Found">Section 4. 3.3.3</a>2506 <td class="left"> <a href="#status.302" id="rfc.xref.status.302.2" title="302 Found">Section 4.5.3</a> 2512 2507 </td> 2513 2508 </tr> … … 2515 2510 <td class="left">303</td> 2516 2511 <td class="left">See Other</td> 2517 <td class="left"> <a href="#status.303" id="rfc.xref.status.303.2" title="303 See Other">Section 4. 3.3.4</a>2512 <td class="left"> <a href="#status.303" id="rfc.xref.status.303.2" title="303 See Other">Section 4.5.4</a> 2518 2513 </td> 2519 2514 </tr> … … 2521 2516 <td class="left">305</td> 2522 2517 <td class="left">Use Proxy</td> 2523 <td class="left"> <a href="#status.305" id="rfc.xref.status.305.2" title="305 Use Proxy">Section 4. 3.3.5</a>2518 <td class="left"> <a href="#status.305" id="rfc.xref.status.305.2" title="305 Use Proxy">Section 4.5.5</a> 2524 2519 </td> 2525 2520 </tr> … … 2527 2522 <td class="left">306</td> 2528 2523 <td class="left">(Unused)</td> 2529 <td class="left"> <a href="#status.306" id="rfc.xref.status.306.1" title="306 (Unused)">Section 4. 3.3.6</a>2524 <td class="left"> <a href="#status.306" id="rfc.xref.status.306.1" title="306 (Unused)">Section 4.5.6</a> 2530 2525 </td> 2531 2526 </tr> … … 2533 2528 <td class="left">307</td> 2534 2529 <td class="left">Temporary Redirect</td> 2535 <td class="left"> <a href="#status.307" id="rfc.xref.status.307.2" title="307 Temporary Redirect">Section 4. 3.3.7</a>2530 <td class="left"> <a href="#status.307" id="rfc.xref.status.307.2" title="307 Temporary Redirect">Section 4.5.7</a> 2536 2531 </td> 2537 2532 </tr> … … 2539 2534 <td class="left">400</td> 2540 2535 <td class="left">Bad Request</td> 2541 <td class="left"> <a href="#status.400" id="rfc.xref.status.400.2" title="400 Bad Request">Section 4. 3.4.1</a>2536 <td class="left"> <a href="#status.400" id="rfc.xref.status.400.2" title="400 Bad Request">Section 4.6.1</a> 2542 2537 </td> 2543 2538 </tr> … … 2545 2540 <td class="left">402</td> 2546 2541 <td class="left">Payment Required</td> 2547 <td class="left"> <a href="#status.402" id="rfc.xref.status.402.2" title="402 Payment Required">Section 4. 3.4.2</a>2542 <td class="left"> <a href="#status.402" id="rfc.xref.status.402.2" title="402 Payment Required">Section 4.6.2</a> 2548 2543 </td> 2549 2544 </tr> … … 2551 2546 <td class="left">403</td> 2552 2547 <td class="left">Forbidden</td> 2553 <td class="left"> <a href="#status.403" id="rfc.xref.status.403.2" title="403 Forbidden">Section 4. 3.4.3</a>2548 <td class="left"> <a href="#status.403" id="rfc.xref.status.403.2" title="403 Forbidden">Section 4.6.3</a> 2554 2549 </td> 2555 2550 </tr> … … 2557 2552 <td class="left">404</td> 2558 2553 <td class="left">Not Found</td> 2559 <td class="left"> <a href="#status.404" id="rfc.xref.status.404.2" title="404 Not Found">Section 4. 3.4.4</a>2554 <td class="left"> <a href="#status.404" id="rfc.xref.status.404.2" title="404 Not Found">Section 4.6.4</a> 2560 2555 </td> 2561 2556 </tr> … … 2563 2558 <td class="left">405</td> 2564 2559 <td class="left">Method Not Allowed</td> 2565 <td class="left"> <a href="#status.405" id="rfc.xref.status.405.2" title="405 Method Not Allowed">Section 4. 3.4.5</a>2560 <td class="left"> <a href="#status.405" id="rfc.xref.status.405.2" title="405 Method Not Allowed">Section 4.6.5</a> 2566 2561 </td> 2567 2562 </tr> … … 2569 2564 <td class="left">406</td> 2570 2565 <td class="left">Not Acceptable</td> 2571 <td class="left"> <a href="#status.406" id="rfc.xref.status.406.2" title="406 Not Acceptable">Section 4. 3.4.6</a>2566 <td class="left"> <a href="#status.406" id="rfc.xref.status.406.2" title="406 Not Acceptable">Section 4.6.6</a> 2572 2567 </td> 2573 2568 </tr> … … 2575 2570 <td class="left">408</td> 2576 2571 <td class="left">Request Timeout</td> 2577 <td class="left"> <a href="#status.408" id="rfc.xref.status.408.2" title="408 Request Timeout">Section 4. 3.4.7</a>2572 <td class="left"> <a href="#status.408" id="rfc.xref.status.408.2" title="408 Request Timeout">Section 4.6.7</a> 2578 2573 </td> 2579 2574 </tr> … … 2581 2576 <td class="left">409</td> 2582 2577 <td class="left">Conflict</td> 2583 <td class="left"> <a href="#status.409" id="rfc.xref.status.409.2" title="409 Conflict">Section 4. 3.4.8</a>2578 <td class="left"> <a href="#status.409" id="rfc.xref.status.409.2" title="409 Conflict">Section 4.6.8</a> 2584 2579 </td> 2585 2580 </tr> … … 2587 2582 <td class="left">410</td> 2588 2583 <td class="left">Gone</td> 2589 <td class="left"> <a href="#status.410" id="rfc.xref.status.410.2" title="410 Gone">Section 4. 3.4.9</a>2584 <td class="left"> <a href="#status.410" id="rfc.xref.status.410.2" title="410 Gone">Section 4.6.9</a> 2590 2585 </td> 2591 2586 </tr> … … 2593 2588 <td class="left">411</td> 2594 2589 <td class="left">Length Required</td> 2595 <td class="left"> <a href="#status.411" id="rfc.xref.status.411.2" title="411 Length Required">Section 4. 3.4.10</a>2590 <td class="left"> <a href="#status.411" id="rfc.xref.status.411.2" title="411 Length Required">Section 4.6.10</a> 2596 2591 </td> 2597 2592 </tr> … … 2599 2594 <td class="left">413</td> 2600 2595 <td class="left">Request Representation Too Large</td> 2601 <td class="left"> <a href="#status.413" id="rfc.xref.status.413.2" title="413 Request Representation Too Large">Section 4. 3.4.11</a>2596 <td class="left"> <a href="#status.413" id="rfc.xref.status.413.2" title="413 Request Representation Too Large">Section 4.6.11</a> 2602 2597 </td> 2603 2598 </tr> … … 2605 2600 <td class="left">414</td> 2606 2601 <td class="left">URI Too Long</td> 2607 <td class="left"> <a href="#status.414" id="rfc.xref.status.414.2" title="414 URI Too Long">Section 4. 3.4.12</a>2602 <td class="left"> <a href="#status.414" id="rfc.xref.status.414.2" title="414 URI Too Long">Section 4.6.12</a> 2608 2603 </td> 2609 2604 </tr> … … 2611 2606 <td class="left">415</td> 2612 2607 <td class="left">Unsupported Media Type</td> 2613 <td class="left"> <a href="#status.415" id="rfc.xref.status.415.2" title="415 Unsupported Media Type">Section 4. 3.4.13</a>2608 <td class="left"> <a href="#status.415" id="rfc.xref.status.415.2" title="415 Unsupported Media Type">Section 4.6.13</a> 2614 2609 </td> 2615 2610 </tr> … … 2617 2612 <td class="left">417</td> 2618 2613 <td class="left">Expectation Failed</td> 2619 <td class="left"> <a href="#status.417" id="rfc.xref.status.417.2" title="417 Expectation Failed">Section 4. 3.4.14</a>2614 <td class="left"> <a href="#status.417" id="rfc.xref.status.417.2" title="417 Expectation Failed">Section 4.6.14</a> 2620 2615 </td> 2621 2616 </tr> … … 2623 2618 <td class="left">426</td> 2624 2619 <td class="left">Upgrade Required</td> 2625 <td class="left"> <a href="#status.426" id="rfc.xref.status.426.2" title="426 Upgrade Required">Section 4. 3.4.15</a>2620 <td class="left"> <a href="#status.426" id="rfc.xref.status.426.2" title="426 Upgrade Required">Section 4.6.15</a> 2626 2621 </td> 2627 2622 </tr> … … 2629 2624 <td class="left">500</td> 2630 2625 <td class="left">Internal Server Error</td> 2631 <td class="left"> <a href="#status.500" id="rfc.xref.status.500.2" title="500 Internal Server Error">Section 4. 3.5.1</a>2626 <td class="left"> <a href="#status.500" id="rfc.xref.status.500.2" title="500 Internal Server Error">Section 4.7.1</a> 2632 2627 </td> 2633 2628 </tr> … … 2635 2630 <td class="left">501</td> 2636 2631 <td class="left">Not Implemented</td> 2637 <td class="left"> <a href="#status.501" id="rfc.xref.status.501.2" title="501 Not Implemented">Section 4. 3.5.2</a>2632 <td class="left"> <a href="#status.501" id="rfc.xref.status.501.2" title="501 Not Implemented">Section 4.7.2</a> 2638 2633 </td> 2639 2634 </tr> … … 2641 2636 <td class="left">502</td> 2642 2637 <td class="left">Bad Gateway</td> 2643 <td class="left"> <a href="#status.502" id="rfc.xref.status.502.2" title="502 Bad Gateway">Section 4. 3.5.3</a>2638 <td class="left"> <a href="#status.502" id="rfc.xref.status.502.2" title="502 Bad Gateway">Section 4.7.3</a> 2644 2639 </td> 2645 2640 </tr> … … 2647 2642 <td class="left">503</td> 2648 2643 <td class="left">Service Unavailable</td> 2649 <td class="left"> <a href="#status.503" id="rfc.xref.status.503.2" title="503 Service Unavailable">Section 4. 3.5.4</a>2644 <td class="left"> <a href="#status.503" id="rfc.xref.status.503.2" title="503 Service Unavailable">Section 4.7.4</a> 2650 2645 </td> 2651 2646 </tr> … … 2653 2648 <td class="left">504</td> 2654 2649 <td class="left">Gateway Timeout</td> 2655 <td class="left"> <a href="#status.504" id="rfc.xref.status.504.2" title="504 Gateway Timeout">Section 4. 3.5.5</a>2650 <td class="left"> <a href="#status.504" id="rfc.xref.status.504.2" title="504 Gateway Timeout">Section 4.7.5</a> 2656 2651 </td> 2657 2652 </tr> … … 2659 2654 <td class="left">505</td> 2660 2655 <td class="left">HTTP Version Not Supported</td> 2661 <td class="left"> <a href="#status.505" id="rfc.xref.status.505.2" title="505 HTTP Version Not Supported">Section 4. 3.5.6</a>2656 <td class="left"> <a href="#status.505" id="rfc.xref.status.505.2" title="505 HTTP Version Not Supported">Section 4.7.6</a> 2662 2657 </td> 2663 2658 </tr> … … 2951 2946 <p id="rfc.section.A.p.4">This document takes over the Status Code Registry, previously defined in <a href="http://tools.ietf.org/html/rfc2817#section-7.1">Section 7.1</a> of <a href="#RFC2817" id="rfc.xref.RFC2817.3"><cite title="Upgrading to TLS Within HTTP/1.1">[RFC2817]</cite></a>. (<a href="#status.code.registry" title="Status Code Registry">Section 4.2</a>) 2952 2947 </p> 2953 <p id="rfc.section.A.p.5">Broadened the definition of 203 (Non-Authoritative Information) to include cases of payload transformations as well. (<a href="#status.203" id="rfc.xref.status.203.3" title="203 Non-Authoritative Information">Section 4. 3.2.4</a>)2954 </p> 2955 <p id="rfc.section.A.p.6">Status codes 301, 302, and 307: removed the normative requirements on both response payloads and user interaction. (<a href="#status.3xx" title="Redirection 3xx">Section 4. 3.3</a>)2948 <p id="rfc.section.A.p.5">Broadened the definition of 203 (Non-Authoritative Information) to include cases of payload transformations as well. (<a href="#status.203" id="rfc.xref.status.203.3" title="203 Non-Authoritative Information">Section 4.4.4</a>) 2949 </p> 2950 <p id="rfc.section.A.p.6">Status codes 301, 302, and 307: removed the normative requirements on both response payloads and user interaction. (<a href="#status.3xx" title="Redirection 3xx">Section 4.5</a>) 2956 2951 </p> 2957 2952 <p id="rfc.section.A.p.7">Failed to consider that there are many other request methods that are safe to automatically redirect, and further that the 2958 2953 user agent is able to make that determination based on the request method semantics. Furthermore, allow user agents to rewrite 2959 the method from POST to GET for status codes 301 and 302. (Sections <a href="#status.301" id="rfc.xref.status.301.3" title="301 Moved Permanently">4. 3.3.2</a>, <a href="#status.302" id="rfc.xref.status.302.3" title="302 Found">4.3.3.3</a> and <a href="#status.307" id="rfc.xref.status.307.3" title="307 Temporary Redirect">4.3.3.7</a>)2954 the method from POST to GET for status codes 301 and 302. (Sections <a href="#status.301" id="rfc.xref.status.301.3" title="301 Moved Permanently">4.5.2</a>, <a href="#status.302" id="rfc.xref.status.302.3" title="302 Found">4.5.3</a> and <a href="#status.307" id="rfc.xref.status.307.3" title="307 Temporary Redirect">4.5.7</a>) 2960 2955 </p> 2961 2956 <p id="rfc.section.A.p.8">Deprecate 305 Use Proxy status code, because user agents did not implement it. It used to indicate that the target resource 2962 2957 needs to be accessed through the proxy given by the Location field. The Location field gave the URI of the proxy. The recipient 2963 was expected to repeat this single request via the proxy. (<a href="#status.305" id="rfc.xref.status.305.3" title="305 Use Proxy">Section 4. 3.3.5</a>)2964 </p> 2965 <p id="rfc.section.A.p.9">Define status 426 (Upgrade Required) (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 4. 3.4.15</a>)2958 was expected to repeat this single request via the proxy. (<a href="#status.305" id="rfc.xref.status.305.3" title="305 Use Proxy">Section 4.5.5</a>) 2959 </p> 2960 <p id="rfc.section.A.p.9">Define status 426 (Upgrade Required) (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 4.6.15</a>) 2966 2961 </p> 2967 2962 <p id="rfc.section.A.p.10">Change ABNF productions for header fields to only define the field value. (<a href="#header.field.definitions" title="Header Field Definitions">Section 7</a>) … … 3425 3420 <ul class="ind"> 3426 3421 <li><a id="rfc.index.1" href="#rfc.index.1"><b>1</b></a><ul> 3427 <li>100 Continue (status code) <a href="#rfc.xref.status.100.1">4.1</a>, <a href="#rfc.iref.22"><b>4.3.1 .1</b></a>, <a href="#rfc.xref.status.100.2">8.2</a></li>3422 <li>100 Continue (status code) <a href="#rfc.xref.status.100.1">4.1</a>, <a href="#rfc.iref.22"><b>4.3.1</b></a>, <a href="#rfc.xref.status.100.2">8.2</a></li> 3428 3423 <li>100-continue (expect value) <a href="#rfc.iref.89"><b>7.3</b></a></li> 3429 <li>101 Switching Protocols (status code) <a href="#rfc.xref.status.101.1">4.1</a>, <a href="#rfc.iref.23"><b>4.3. 1.2</b></a>, <a href="#rfc.xref.status.101.2">8.2</a></li>3424 <li>101 Switching Protocols (status code) <a href="#rfc.xref.status.101.1">4.1</a>, <a href="#rfc.iref.23"><b>4.3.2</b></a>, <a href="#rfc.xref.status.101.2">8.2</a></li> 3430 3425 </ul> 3431 3426 </li> 3432 3427 <li><a id="rfc.index.2" href="#rfc.index.2"><b>2</b></a><ul> 3433 <li>200 OK (status code) <a href="#rfc.xref.status.200.1">4.1</a>, <a href="#rfc.iref.24"><b>4. 3.2.1</b></a>, <a href="#rfc.xref.status.200.2">8.2</a></li>3434 <li>201 Created (status code) <a href="#rfc.xref.status.201.1">4.1</a>, <a href="#rfc.iref.25"><b>4. 3.2.2</b></a>, <a href="#rfc.xref.status.201.2">8.2</a></li>3435 <li>202 Accepted (status code) <a href="#rfc.xref.status.202.1">4.1</a>, <a href="#rfc.iref.26"><b>4. 3.2.3</b></a>, <a href="#rfc.xref.status.202.2">8.2</a></li>3436 <li>203 Non-Authoritative Information (status code) <a href="#rfc.xref.status.203.1">4.1</a>, <a href="#rfc.iref.27"><b>4. 3.2.4</b></a>, <a href="#rfc.xref.status.203.2">8.2</a>, <a href="#rfc.xref.status.203.3">A</a></li>3437 <li>204 No Content (status code) <a href="#rfc.xref.status.204.1">4.1</a>, <a href="#rfc.iref.28"><b>4. 3.2.5</b></a>, <a href="#rfc.xref.status.204.2">8.2</a></li>3438 <li>205 Reset Content (status code) <a href="#rfc.xref.status.205.1">4.1</a>, <a href="#rfc.iref.29"><b>4. 3.2.6</b></a>, <a href="#rfc.xref.status.205.2">8.2</a></li>3428 <li>200 OK (status code) <a href="#rfc.xref.status.200.1">4.1</a>, <a href="#rfc.iref.24"><b>4.4.1</b></a>, <a href="#rfc.xref.status.200.2">8.2</a></li> 3429 <li>201 Created (status code) <a href="#rfc.xref.status.201.1">4.1</a>, <a href="#rfc.iref.25"><b>4.4.2</b></a>, <a href="#rfc.xref.status.201.2">8.2</a></li> 3430 <li>202 Accepted (status code) <a href="#rfc.xref.status.202.1">4.1</a>, <a href="#rfc.iref.26"><b>4.4.3</b></a>, <a href="#rfc.xref.status.202.2">8.2</a></li> 3431 <li>203 Non-Authoritative Information (status code) <a href="#rfc.xref.status.203.1">4.1</a>, <a href="#rfc.iref.27"><b>4.4.4</b></a>, <a href="#rfc.xref.status.203.2">8.2</a>, <a href="#rfc.xref.status.203.3">A</a></li> 3432 <li>204 No Content (status code) <a href="#rfc.xref.status.204.1">4.1</a>, <a href="#rfc.iref.28"><b>4.4.5</b></a>, <a href="#rfc.xref.status.204.2">8.2</a></li> 3433 <li>205 Reset Content (status code) <a href="#rfc.xref.status.205.1">4.1</a>, <a href="#rfc.iref.29"><b>4.4.6</b></a>, <a href="#rfc.xref.status.205.2">8.2</a></li> 3439 3434 </ul> 3440 3435 </li> 3441 3436 <li><a id="rfc.index.3" href="#rfc.index.3"><b>3</b></a><ul> 3442 <li>300 Multiple Choices (status code) <a href="#rfc.xref.status.300.1">4.1</a>, <a href="#rfc.iref.30"><b>4. 3.3.1</b></a>, <a href="#rfc.xref.status.300.2">8.2</a></li>3443 <li>301 Moved Permanently (status code) <a href="#rfc.xref.status.301.1">4.1</a>, <a href="#rfc.iref.31"><b>4. 3.3.2</b></a>, <a href="#rfc.xref.status.301.2">8.2</a>, <a href="#rfc.xref.status.301.3">A</a></li>3444 <li>302 Found (status code) <a href="#rfc.xref.status.302.1">4.1</a>, <a href="#rfc.iref.32"><b>4. 3.3.3</b></a>, <a href="#rfc.xref.status.302.2">8.2</a>, <a href="#rfc.xref.status.302.3">A</a></li>3445 <li>303 See Other (status code) <a href="#rfc.xref.status.303.1">4.1</a>, <a href="#rfc.iref.33"><b>4. 3.3.4</b></a>, <a href="#rfc.xref.status.303.2">8.2</a></li>3446 <li>305 Use Proxy (status code) <a href="#rfc.xref.status.305.1">4.1</a>, <a href="#rfc.iref.34"><b>4. 3.3.5</b></a>, <a href="#rfc.xref.status.305.2">8.2</a>, <a href="#rfc.xref.status.305.3">A</a></li>3447 <li>306 (Unused) (status code) <a href="#rfc.iref.35"><b>4. 3.3.6</b></a>, <a href="#rfc.xref.status.306.1">8.2</a></li>3448 <li>307 Temporary Redirect (status code) <a href="#rfc.xref.status.307.1">4.1</a>, <a href="#rfc.iref.36"><b>4. 3.3.7</b></a>, <a href="#rfc.xref.status.307.2">8.2</a>, <a href="#rfc.xref.status.307.3">A</a></li>3437 <li>300 Multiple Choices (status code) <a href="#rfc.xref.status.300.1">4.1</a>, <a href="#rfc.iref.30"><b>4.5.1</b></a>, <a href="#rfc.xref.status.300.2">8.2</a></li> 3438 <li>301 Moved Permanently (status code) <a href="#rfc.xref.status.301.1">4.1</a>, <a href="#rfc.iref.31"><b>4.5.2</b></a>, <a href="#rfc.xref.status.301.2">8.2</a>, <a href="#rfc.xref.status.301.3">A</a></li> 3439 <li>302 Found (status code) <a href="#rfc.xref.status.302.1">4.1</a>, <a href="#rfc.iref.32"><b>4.5.3</b></a>, <a href="#rfc.xref.status.302.2">8.2</a>, <a href="#rfc.xref.status.302.3">A</a></li> 3440 <li>303 See Other (status code) <a href="#rfc.xref.status.303.1">4.1</a>, <a href="#rfc.iref.33"><b>4.5.4</b></a>, <a href="#rfc.xref.status.303.2">8.2</a></li> 3441 <li>305 Use Proxy (status code) <a href="#rfc.xref.status.305.1">4.1</a>, <a href="#rfc.iref.34"><b>4.5.5</b></a>, <a href="#rfc.xref.status.305.2">8.2</a>, <a href="#rfc.xref.status.305.3">A</a></li> 3442 <li>306 (Unused) (status code) <a href="#rfc.iref.35"><b>4.5.6</b></a>, <a href="#rfc.xref.status.306.1">8.2</a></li> 3443 <li>307 Temporary Redirect (status code) <a href="#rfc.xref.status.307.1">4.1</a>, <a href="#rfc.iref.36"><b>4.5.7</b></a>, <a href="#rfc.xref.status.307.2">8.2</a>, <a href="#rfc.xref.status.307.3">A</a></li> 3449 3444 </ul> 3450 3445 </li> 3451 3446 <li><a id="rfc.index.4" href="#rfc.index.4"><b>4</b></a><ul> 3452 <li>400 Bad Request (status code) <a href="#rfc.xref.status.400.1">4.1</a>, <a href="#rfc.iref.37"><b>4. 3.4.1</b></a>, <a href="#rfc.xref.status.400.2">8.2</a></li>3453 <li>402 Payment Required (status code) <a href="#rfc.xref.status.402.1">4.1</a>, <a href="#rfc.iref.38"><b>4. 3.4.2</b></a>, <a href="#rfc.xref.status.402.2">8.2</a></li>3454 <li>403 Forbidden (status code) <a href="#rfc.xref.status.403.1">4.1</a>, <a href="#rfc.iref.39"><b>4. 3.4.3</b></a>, <a href="#rfc.xref.status.403.2">8.2</a></li>3455 <li>404 Not Found (status code) <a href="#rfc.xref.status.404.1">4.1</a>, <a href="#rfc.iref.40"><b>4. 3.4.4</b></a>, <a href="#rfc.xref.status.404.2">8.2</a></li>3456 <li>405 Method Not Allowed (status code) <a href="#rfc.xref.status.405.1">4.1</a>, <a href="#rfc.iref.41"><b>4. 3.4.5</b></a>, <a href="#rfc.xref.status.405.2">8.2</a></li>3457 <li>406 Not Acceptable (status code) <a href="#rfc.xref.status.406.1">4.1</a>, <a href="#rfc.iref.42"><b>4. 3.4.6</b></a>, <a href="#rfc.xref.status.406.2">8.2</a></li>3458 <li>408 Request Timeout (status code) <a href="#rfc.xref.status.408.1">4.1</a>, <a href="#rfc.iref.43"><b>4. 3.4.7</b></a>, <a href="#rfc.xref.status.408.2">8.2</a></li>3459 <li>409 Conflict (status code) <a href="#rfc.xref.status.409.1">4.1</a>, <a href="#rfc.iref.44"><b>4. 3.4.8</b></a>, <a href="#rfc.xref.status.409.2">8.2</a></li>3460 <li>410 Gone (status code) <a href="#rfc.xref.status.410.1">4.1</a>, <a href="#rfc.iref.45"><b>4. 3.4.9</b></a>, <a href="#rfc.xref.status.410.2">8.2</a></li>3461 <li>411 Length Required (status code) <a href="#rfc.xref.status.411.1">4.1</a>, <a href="#rfc.iref.46"><b>4. 3.4.10</b></a>, <a href="#rfc.xref.status.411.2">8.2</a></li>3462 <li>413 Request Representation Too Large (status code) <a href="#rfc.xref.status.413.1">4.1</a>, <a href="#rfc.iref.47"><b>4. 3.4.11</b></a>, <a href="#rfc.xref.status.413.2">8.2</a></li>3463 <li>414 URI Too Long (status code) <a href="#rfc.xref.status.414.1">4.1</a>, <a href="#rfc.iref.48"><b>4. 3.4.12</b></a>, <a href="#rfc.xref.status.414.2">8.2</a></li>3464 <li>415 Unsupported Media Type (status code) <a href="#rfc.xref.status.415.1">4.1</a>, <a href="#rfc.iref.49"><b>4. 3.4.13</b></a>, <a href="#rfc.xref.status.415.2">8.2</a></li>3465 <li>417 Expectation Failed (status code) <a href="#rfc.xref.status.417.1">4.1</a>, <a href="#rfc.iref.50"><b>4. 3.4.14</b></a>, <a href="#rfc.xref.status.417.2">8.2</a></li>3466 <li>426 Upgrade Required (status code) <a href="#rfc.xref.status.426.1">4.1</a>, <a href="#rfc.iref.51"><b>4. 3.4.15</b></a>, <a href="#rfc.xref.status.426.2">8.2</a>, <a href="#rfc.xref.status.426.3">A</a></li>3447 <li>400 Bad Request (status code) <a href="#rfc.xref.status.400.1">4.1</a>, <a href="#rfc.iref.37"><b>4.6.1</b></a>, <a href="#rfc.xref.status.400.2">8.2</a></li> 3448 <li>402 Payment Required (status code) <a href="#rfc.xref.status.402.1">4.1</a>, <a href="#rfc.iref.38"><b>4.6.2</b></a>, <a href="#rfc.xref.status.402.2">8.2</a></li> 3449 <li>403 Forbidden (status code) <a href="#rfc.xref.status.403.1">4.1</a>, <a href="#rfc.iref.39"><b>4.6.3</b></a>, <a href="#rfc.xref.status.403.2">8.2</a></li> 3450 <li>404 Not Found (status code) <a href="#rfc.xref.status.404.1">4.1</a>, <a href="#rfc.iref.40"><b>4.6.4</b></a>, <a href="#rfc.xref.status.404.2">8.2</a></li> 3451 <li>405 Method Not Allowed (status code) <a href="#rfc.xref.status.405.1">4.1</a>, <a href="#rfc.iref.41"><b>4.6.5</b></a>, <a href="#rfc.xref.status.405.2">8.2</a></li> 3452 <li>406 Not Acceptable (status code) <a href="#rfc.xref.status.406.1">4.1</a>, <a href="#rfc.iref.42"><b>4.6.6</b></a>, <a href="#rfc.xref.status.406.2">8.2</a></li> 3453 <li>408 Request Timeout (status code) <a href="#rfc.xref.status.408.1">4.1</a>, <a href="#rfc.iref.43"><b>4.6.7</b></a>, <a href="#rfc.xref.status.408.2">8.2</a></li> 3454 <li>409 Conflict (status code) <a href="#rfc.xref.status.409.1">4.1</a>, <a href="#rfc.iref.44"><b>4.6.8</b></a>, <a href="#rfc.xref.status.409.2">8.2</a></li> 3455 <li>410 Gone (status code) <a href="#rfc.xref.status.410.1">4.1</a>, <a href="#rfc.iref.45"><b>4.6.9</b></a>, <a href="#rfc.xref.status.410.2">8.2</a></li> 3456 <li>411 Length Required (status code) <a href="#rfc.xref.status.411.1">4.1</a>, <a href="#rfc.iref.46"><b>4.6.10</b></a>, <a href="#rfc.xref.status.411.2">8.2</a></li> 3457 <li>413 Request Representation Too Large (status code) <a href="#rfc.xref.status.413.1">4.1</a>, <a href="#rfc.iref.47"><b>4.6.11</b></a>, <a href="#rfc.xref.status.413.2">8.2</a></li> 3458 <li>414 URI Too Long (status code) <a href="#rfc.xref.status.414.1">4.1</a>, <a href="#rfc.iref.48"><b>4.6.12</b></a>, <a href="#rfc.xref.status.414.2">8.2</a></li> 3459 <li>415 Unsupported Media Type (status code) <a href="#rfc.xref.status.415.1">4.1</a>, <a href="#rfc.iref.49"><b>4.6.13</b></a>, <a href="#rfc.xref.status.415.2">8.2</a></li> 3460 <li>417 Expectation Failed (status code) <a href="#rfc.xref.status.417.1">4.1</a>, <a href="#rfc.iref.50"><b>4.6.14</b></a>, <a href="#rfc.xref.status.417.2">8.2</a></li> 3461 <li>426 Upgrade Required (status code) <a href="#rfc.xref.status.426.1">4.1</a>, <a href="#rfc.iref.51"><b>4.6.15</b></a>, <a href="#rfc.xref.status.426.2">8.2</a>, <a href="#rfc.xref.status.426.3">A</a></li> 3467 3462 </ul> 3468 3463 </li> 3469 3464 <li><a id="rfc.index.5" href="#rfc.index.5"><b>5</b></a><ul> 3470 <li>500 Internal Server Error (status code) <a href="#rfc.xref.status.500.1">4.1</a>, <a href="#rfc.iref.52"><b>4. 3.5.1</b></a>, <a href="#rfc.xref.status.500.2">8.2</a></li>3471 <li>501 Not Implemented (status code) <a href="#rfc.xref.status.501.1">4.1</a>, <a href="#rfc.iref.53"><b>4. 3.5.2</b></a>, <a href="#rfc.xref.status.501.2">8.2</a></li>3472 <li>502 Bad Gateway (status code) <a href="#rfc.xref.status.502.1">4.1</a>, <a href="#rfc.iref.54"><b>4. 3.5.3</b></a>, <a href="#rfc.xref.status.502.2">8.2</a></li>3473 <li>503 Service Unavailable (status code) <a href="#rfc.xref.status.503.1">4.1</a>, <a href="#rfc.iref.55"><b>4. 3.5.4</b></a>, <a href="#rfc.xref.status.503.2">8.2</a></li>3474 <li>504 Gateway Timeout (status code) <a href="#rfc.xref.status.504.1">4.1</a>, <a href="#rfc.iref.56"><b>4. 3.5.5</b></a>, <a href="#rfc.xref.status.504.2">8.2</a></li>3475 <li>505 HTTP Version Not Supported (status code) <a href="#rfc.xref.status.505.1">4.1</a>, <a href="#rfc.iref.57"><b>4. 3.5.6</b></a>, <a href="#rfc.xref.status.505.2">8.2</a></li>3465 <li>500 Internal Server Error (status code) <a href="#rfc.xref.status.500.1">4.1</a>, <a href="#rfc.iref.52"><b>4.7.1</b></a>, <a href="#rfc.xref.status.500.2">8.2</a></li> 3466 <li>501 Not Implemented (status code) <a href="#rfc.xref.status.501.1">4.1</a>, <a href="#rfc.iref.53"><b>4.7.2</b></a>, <a href="#rfc.xref.status.501.2">8.2</a></li> 3467 <li>502 Bad Gateway (status code) <a href="#rfc.xref.status.502.1">4.1</a>, <a href="#rfc.iref.54"><b>4.7.3</b></a>, <a href="#rfc.xref.status.502.2">8.2</a></li> 3468 <li>503 Service Unavailable (status code) <a href="#rfc.xref.status.503.1">4.1</a>, <a href="#rfc.iref.55"><b>4.7.4</b></a>, <a href="#rfc.xref.status.503.2">8.2</a></li> 3469 <li>504 Gateway Timeout (status code) <a href="#rfc.xref.status.504.1">4.1</a>, <a href="#rfc.iref.56"><b>4.7.5</b></a>, <a href="#rfc.xref.status.504.2">8.2</a></li> 3470 <li>505 HTTP Version Not Supported (status code) <a href="#rfc.xref.status.505.1">4.1</a>, <a href="#rfc.iref.57"><b>4.7.6</b></a>, <a href="#rfc.xref.status.505.2">8.2</a></li> 3476 3471 </ul> 3477 3472 </li> … … 3487 3482 <li>Date header field <a href="#rfc.xref.header.date.1">3.3</a>, <a href="#rfc.iref.d.2"><b>7.2</b></a>, <a href="#rfc.xref.header.date.2">8.3</a></li> 3488 3483 <li>DELETE method <a href="#rfc.iref.d.1"><b>2.3.6</b></a>, <a href="#rfc.xref.DELETE.1">8.1</a></li> 3489 <li><em>draft-reschke-http-status-308</em> <a href="#rfc.xref.draft-reschke-http-status-308.1">4. 3.3.7</a>, <a href="#draft-reschke-http-status-308"><b>11.2</b></a></li>3484 <li><em>draft-reschke-http-status-308</em> <a href="#rfc.xref.draft-reschke-http-status-308.1">4.5.7</a>, <a href="#draft-reschke-http-status-308"><b>11.2</b></a></li> 3490 3485 </ul> 3491 3486 </li> 3492 3487 <li><a id="rfc.index.E" href="#rfc.index.E"><b>E</b></a><ul> 3493 <li>Expect header field <a href="#rfc.xref.header.expect.1">3.2</a>, <a href="#rfc.xref.header.expect.2">4. 3.4.14</a>, <a href="#rfc.iref.e.1"><b>7.3</b></a>, <a href="#rfc.xref.header.expect.3">8.3</a>, <a href="#rfc.xref.header.expect.4">A</a></li>3488 <li>Expect header field <a href="#rfc.xref.header.expect.1">3.2</a>, <a href="#rfc.xref.header.expect.2">4.6.14</a>, <a href="#rfc.iref.e.1"><b>7.3</b></a>, <a href="#rfc.xref.header.expect.3">8.3</a>, <a href="#rfc.xref.header.expect.4">A</a></li> 3494 3489 <li>Expect Values 3495 3490 <ul> … … 3554 3549 <li>Allow <a href="#rfc.xref.header.allow.1">2</a>, <a href="#rfc.xref.header.allow.2">3.3</a>, <a href="#rfc.iref.h.2"><b>7.1</b></a>, <a href="#rfc.xref.header.allow.3">8.3</a>, <a href="#rfc.xref.header.allow.4">A</a></li> 3555 3550 <li>Date <a href="#rfc.xref.header.date.1">3.3</a>, <a href="#rfc.iref.h.3"><b>7.2</b></a>, <a href="#rfc.xref.header.date.2">8.3</a></li> 3556 <li>Expect <a href="#rfc.xref.header.expect.1">3.2</a>, <a href="#rfc.xref.header.expect.2">4. 3.4.14</a>, <a href="#rfc.iref.h.4"><b>7.3</b></a>, <a href="#rfc.xref.header.expect.3">8.3</a>, <a href="#rfc.xref.header.expect.4">A</a></li>3551 <li>Expect <a href="#rfc.xref.header.expect.1">3.2</a>, <a href="#rfc.xref.header.expect.2">4.6.14</a>, <a href="#rfc.iref.h.4"><b>7.3</b></a>, <a href="#rfc.xref.header.expect.3">8.3</a>, <a href="#rfc.xref.header.expect.4">A</a></li> 3557 3552 <li>From <a href="#rfc.xref.header.from.1">3.2</a>, <a href="#rfc.iref.h.5"><b>7.4</b></a>, <a href="#rfc.xref.header.from.2">8.3</a></li> 3558 <li>Location <a href="#rfc.xref.header.location.1">2.3.4</a>, <a href="#rfc.xref.header.location.2">3.3</a>, <a href="#rfc.xref.header.location.3">4. 3.3</a>, <a href="#rfc.iref.h.6"><b>7.5</b></a>, <a href="#rfc.xref.header.location.4">8.3</a>, <a href="#rfc.xref.header.location.5">A</a></li>3553 <li>Location <a href="#rfc.xref.header.location.1">2.3.4</a>, <a href="#rfc.xref.header.location.2">3.3</a>, <a href="#rfc.xref.header.location.3">4.5</a>, <a href="#rfc.iref.h.6"><b>7.5</b></a>, <a href="#rfc.xref.header.location.4">8.3</a>, <a href="#rfc.xref.header.location.5">A</a></li> 3559 3554 <li>Max-Forwards <a href="#rfc.xref.header.max-forwards.1">2.3.1</a>, <a href="#rfc.xref.header.max-forwards.2">2.3.7</a>, <a href="#rfc.xref.header.max-forwards.3">3.2</a>, <a href="#rfc.iref.h.7"><b>7.6</b></a>, <a href="#rfc.xref.header.max-forwards.4">8.3</a>, <a href="#rfc.xref.header.max-forwards.5">A</a></li> 3560 3555 <li>Referer <a href="#rfc.xref.header.referer.1">3.2</a>, <a href="#rfc.iref.h.8"><b>7.7</b></a>, <a href="#rfc.xref.header.referer.2">8.3</a>, <a href="#rfc.xref.header.referer.3">A</a></li> 3561 <li>Retry-After <a href="#rfc.xref.header.retry-after.1">3.3</a>, <a href="#rfc.xref.header.retry-after.2">4. 3.5.4</a>, <a href="#rfc.iref.h.9"><b>7.8</b></a>, <a href="#rfc.xref.header.retry-after.3">8.3</a></li>3556 <li>Retry-After <a href="#rfc.xref.header.retry-after.1">3.3</a>, <a href="#rfc.xref.header.retry-after.2">4.7.4</a>, <a href="#rfc.iref.h.9"><b>7.8</b></a>, <a href="#rfc.xref.header.retry-after.3">8.3</a></li> 3562 3557 <li>Server <a href="#rfc.xref.header.server.1">3.3</a>, <a href="#rfc.iref.h.10"><b>7.9</b></a>, <a href="#rfc.xref.header.server.2">8.3</a>, <a href="#rfc.xref.header.server.3">9.1</a>, <a href="#rfc.xref.header.server.4">A</a></li> 3563 3558 <li>User-Agent <a href="#rfc.xref.header.user-agent.1">3.2</a>, <a href="#rfc.iref.h.11"><b>7.10</b></a>, <a href="#rfc.xref.header.user-agent.2">8.3</a>, <a href="#rfc.xref.header.user-agent.3">9.1</a></li> … … 3571 3566 </li> 3572 3567 <li><a id="rfc.index.L" href="#rfc.index.L"><b>L</b></a><ul> 3573 <li>Location header field <a href="#rfc.xref.header.location.1">2.3.4</a>, <a href="#rfc.xref.header.location.2">3.3</a>, <a href="#rfc.xref.header.location.3">4. 3.3</a>, <a href="#rfc.iref.l.1"><b>7.5</b></a>, <a href="#rfc.xref.header.location.4">8.3</a>, <a href="#rfc.xref.header.location.5">A</a></li>3568 <li>Location header field <a href="#rfc.xref.header.location.1">2.3.4</a>, <a href="#rfc.xref.header.location.2">3.3</a>, <a href="#rfc.xref.header.location.3">4.5</a>, <a href="#rfc.iref.l.1"><b>7.5</b></a>, <a href="#rfc.xref.header.location.4">8.3</a>, <a href="#rfc.xref.header.location.5">A</a></li> 3574 3569 </ul> 3575 3570 </li> … … 3595 3590 </li> 3596 3591 <li><a id="rfc.index.P" href="#rfc.index.P"><b>P</b></a><ul> 3597 <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">1.2.1</a>, <a href="#rfc.xref.Part1.5">1.2.1</a>, <a href="#rfc.xref.Part1.6">1.2.1</a>, <a href="#rfc.xref.Part1.7">1.2.1</a>, <a href="#rfc.xref.Part1.8">1.2.1</a>, <a href="#rfc.xref.Part1.9">1.2.1</a>, <a href="#rfc.xref.Part1.10">1.2.1</a>, <a href="#rfc.xref.Part1.11">1.2.2</a>, <a href="#rfc.xref.Part1.12">1.2.2</a>, <a href="#rfc.xref.Part1.13">1.2.2</a>, <a href="#rfc.xref.Part1.14">1.2.2</a>, <a href="#rfc.xref.Part1.15">2</a>, <a href="#rfc.xref.Part1.16">2.2.1</a>, <a href="#rfc.xref.Part1.17">2.3.1</a>, <a href="#rfc.xref.Part1.18">2.3.7</a>, <a href="#rfc.xref.Part1.19">2.3.7</a>, <a href="#rfc.xref.Part1.20">2.3.8</a>, <a href="#rfc.xref.Part1.21">3</a>, <a href="#rfc.xref.Part1.22">3.1</a>, <a href="#rfc.xref.Part1.23">3.1</a>, <a href="#rfc.xref.Part1.24">3.1</a>, <a href="#rfc.xref.Part1.25">3.1</a>, <a href="#rfc.xref.Part1.26">3.1</a>, <a href="#rfc.xref.Part1.27">3.2</a>, <a href="#rfc.xref.Part1.28">3.2</a>, <a href="#rfc.xref.Part1.29">3.3</a>, <a href="#rfc.xref.Part1.30">4.3.1 .1</a>, <a href="#rfc.xref.Part1.31">4.3.1.2</a>, <a href="#rfc.xref.Part1.32">4.3.2.4</a>, <a href="#rfc.xref.Part1.33">4.3.2.6</a>, <a href="#rfc.xref.Part1.34">4.3.4.15</a>, <a href="#rfc.xref.Part1.35">4.3.5.6</a>, <a href="#rfc.xref.Part1.36">5</a>, <a href="#rfc.xref.Part1.37">5.1</a>, <a href="#rfc.xref.Part1.38">7.3</a>, <a href="#rfc.xref.Part1.39">7.9</a>, <a href="#rfc.xref.Part1.40">7.9</a>, <a href="#rfc.xref.Part1.41">7.10</a>, <a href="#rfc.xref.Part1.42">10</a>, <a href="#Part1"><b>11.1</b></a>, <a href="#rfc.xref.Part1.43">A</a><ul>3592 <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">1.2.1</a>, <a href="#rfc.xref.Part1.5">1.2.1</a>, <a href="#rfc.xref.Part1.6">1.2.1</a>, <a href="#rfc.xref.Part1.7">1.2.1</a>, <a href="#rfc.xref.Part1.8">1.2.1</a>, <a href="#rfc.xref.Part1.9">1.2.1</a>, <a href="#rfc.xref.Part1.10">1.2.1</a>, <a href="#rfc.xref.Part1.11">1.2.2</a>, <a href="#rfc.xref.Part1.12">1.2.2</a>, <a href="#rfc.xref.Part1.13">1.2.2</a>, <a href="#rfc.xref.Part1.14">1.2.2</a>, <a href="#rfc.xref.Part1.15">2</a>, <a href="#rfc.xref.Part1.16">2.2.1</a>, <a href="#rfc.xref.Part1.17">2.3.1</a>, <a href="#rfc.xref.Part1.18">2.3.7</a>, <a href="#rfc.xref.Part1.19">2.3.7</a>, <a href="#rfc.xref.Part1.20">2.3.8</a>, <a href="#rfc.xref.Part1.21">3</a>, <a href="#rfc.xref.Part1.22">3.1</a>, <a href="#rfc.xref.Part1.23">3.1</a>, <a href="#rfc.xref.Part1.24">3.1</a>, <a href="#rfc.xref.Part1.25">3.1</a>, <a href="#rfc.xref.Part1.26">3.1</a>, <a href="#rfc.xref.Part1.27">3.2</a>, <a href="#rfc.xref.Part1.28">3.2</a>, <a href="#rfc.xref.Part1.29">3.3</a>, <a href="#rfc.xref.Part1.30">4.3.1</a>, <a href="#rfc.xref.Part1.31">4.3.2</a>, <a href="#rfc.xref.Part1.32">4.4.4</a>, <a href="#rfc.xref.Part1.33">4.4.6</a>, <a href="#rfc.xref.Part1.34">4.6.15</a>, <a href="#rfc.xref.Part1.35">4.7.6</a>, <a href="#rfc.xref.Part1.36">5</a>, <a href="#rfc.xref.Part1.37">5.1</a>, <a href="#rfc.xref.Part1.38">7.3</a>, <a href="#rfc.xref.Part1.39">7.9</a>, <a href="#rfc.xref.Part1.40">7.9</a>, <a href="#rfc.xref.Part1.41">7.10</a>, <a href="#rfc.xref.Part1.42">10</a>, <a href="#Part1"><b>11.1</b></a>, <a href="#rfc.xref.Part1.43">A</a><ul> 3598 3593 <li><em>Section 1.2</em> <a href="#rfc.xref.Part1.3">1.2</a></li> 3599 3594 <li><em>Section 2</em> <a href="#rfc.xref.Part1.2">1.1</a></li> 3600 <li><em>Section 2.3</em> <a href="#rfc.xref.Part1.32">4. 3.2.4</a></li>3601 <li><em>Section 2.6</em> <a href="#rfc.xref.Part1.35">4. 3.5.6</a></li>3595 <li><em>Section 2.3</em> <a href="#rfc.xref.Part1.32">4.4.4</a></li> 3596 <li><em>Section 2.6</em> <a href="#rfc.xref.Part1.35">4.7.6</a></li> 3602 3597 <li><em>Section 2.7</em> <a href="#rfc.xref.Part1.11">1.2.2</a>, <a href="#rfc.xref.Part1.13">1.2.2</a>, <a href="#rfc.xref.Part1.14">1.2.2</a></li> 3603 3598 <li><em>Section 3.2.1</em> <a href="#rfc.xref.Part1.5">1.2.1</a>, <a href="#rfc.xref.Part1.6">1.2.1</a>, <a href="#rfc.xref.Part1.7">1.2.1</a></li> … … 3605 3600 <li><em>Section 3.2.4</em> <a href="#rfc.xref.Part1.8">1.2.1</a>, <a href="#rfc.xref.Part1.9">1.2.1</a>, <a href="#rfc.xref.Part1.10">1.2.1</a>, <a href="#rfc.xref.Part1.12">1.2.2</a>, <a href="#rfc.xref.Part1.23">3.1</a></li> 3606 3601 <li><em>Section 3.2.5</em> <a href="#rfc.xref.Part1.22">3.1</a></li> 3607 <li><em>Section 3.3</em> <a href="#rfc.xref.Part1.16">2.2.1</a>, <a href="#rfc.xref.Part1.33">4. 3.2.6</a>, <a href="#rfc.xref.Part1.36">5</a></li>3602 <li><em>Section 3.3</em> <a href="#rfc.xref.Part1.16">2.2.1</a>, <a href="#rfc.xref.Part1.33">4.4.6</a>, <a href="#rfc.xref.Part1.36">5</a></li> 3608 3603 <li><em>Section 4.1</em> <a href="#rfc.xref.Part1.26">3.1</a></li> 3609 3604 <li><em>Section 4.3</em> <a href="#rfc.xref.Part1.28">3.2</a></li> … … 3613 3608 <li><em>Section 6.1</em> <a href="#rfc.xref.Part1.25">3.1</a></li> 3614 3609 <li><em>Section 6.2</em> <a href="#rfc.xref.Part1.18">2.3.7</a>, <a href="#rfc.xref.Part1.40">7.9</a>, <a href="#rfc.xref.Part1.43">A</a></li> 3615 <li><em>Section 6.4.3</em> <a href="#rfc.xref.Part1.30">4.3.1 .1</a>, <a href="#rfc.xref.Part1.38">7.3</a></li>3616 <li><em>Section 6.5</em> <a href="#rfc.xref.Part1.31">4.3. 1.2</a>, <a href="#rfc.xref.Part1.34">4.3.4.15</a></li>3610 <li><em>Section 6.4.3</em> <a href="#rfc.xref.Part1.30">4.3.1</a>, <a href="#rfc.xref.Part1.38">7.3</a></li> 3611 <li><em>Section 6.5</em> <a href="#rfc.xref.Part1.31">4.3.2</a>, <a href="#rfc.xref.Part1.34">4.6.15</a></li> 3617 3612 <li><em>Section 7.3.1</em> <a href="#rfc.xref.Part1.19">2.3.7</a></li> 3618 3613 <li><em>Section 9</em> <a href="#rfc.xref.Part1.42">10</a></li> 3619 3614 </ul> 3620 3615 </li> 3621 <li><em>Part3</em> <a href="#rfc.xref.Part3.1">2.3.4</a>, <a href="#rfc.xref.Part3.2">3.1</a>, <a href="#rfc.xref.Part3.3">3.1</a>, <a href="#rfc.xref.Part3.4">3.2</a>, <a href="#rfc.xref.Part3.5">3.2</a>, <a href="#rfc.xref.Part3.6">3.2</a>, <a href="#rfc.xref.Part3.7">3.2</a>, <a href="#rfc.xref.Part3.8">4 .3</a>, <a href="#rfc.xref.Part3.9">4.3.3</a>, <a href="#rfc.xref.Part3.10">4.3.3.1</a>, <a href="#rfc.xref.Part3.11">4.3.4.6</a>, <a href="#rfc.xref.Part3.12">5</a>, <a href="#rfc.xref.Part3.13">7.5</a>, <a href="#Part3"><b>11.1</b></a><ul>3616 <li><em>Part3</em> <a href="#rfc.xref.Part3.1">2.3.4</a>, <a href="#rfc.xref.Part3.2">3.1</a>, <a href="#rfc.xref.Part3.3">3.1</a>, <a href="#rfc.xref.Part3.4">3.2</a>, <a href="#rfc.xref.Part3.5">3.2</a>, <a href="#rfc.xref.Part3.6">3.2</a>, <a href="#rfc.xref.Part3.7">3.2</a>, <a href="#rfc.xref.Part3.8">4</a>, <a href="#rfc.xref.Part3.9">4.5</a>, <a href="#rfc.xref.Part3.10">4.5.1</a>, <a href="#rfc.xref.Part3.11">4.6.6</a>, <a href="#rfc.xref.Part3.12">5</a>, <a href="#rfc.xref.Part3.13">7.5</a>, <a href="#Part3"><b>11.1</b></a><ul> 3622 3617 <li><em>Section 2.3</em> <a href="#rfc.xref.Part3.3">3.1</a></li> 3623 <li><em>Section 5</em> <a href="#rfc.xref.Part3.10">4. 3.3.1</a></li>3624 <li><em>Section 5.2</em> <a href="#rfc.xref.Part3.9">4. 3.3</a></li>3618 <li><em>Section 5</em> <a href="#rfc.xref.Part3.10">4.5.1</a></li> 3619 <li><em>Section 5.2</em> <a href="#rfc.xref.Part3.9">4.5</a></li> 3625 3620 <li><em>Section 6.1</em> <a href="#rfc.xref.Part3.4">3.2</a></li> 3626 <li><em>Section 6</em> <a href="#rfc.xref.Part3.11">4. 3.4.6</a></li>3621 <li><em>Section 6</em> <a href="#rfc.xref.Part3.11">4.6.6</a></li> 3627 3622 <li><em>Section 6.2</em> <a href="#rfc.xref.Part3.5">3.2</a></li> 3628 3623 <li><em>Section 6.3</em> <a href="#rfc.xref.Part3.6">3.2</a></li> 3629 3624 <li><em>Section 6.4</em> <a href="#rfc.xref.Part3.7">3.2</a></li> 3630 3625 <li><em>Section 6.7</em> <a href="#rfc.xref.Part3.1">2.3.4</a>, <a href="#rfc.xref.Part3.13">7.5</a></li> 3631 <li><em>Section 6.8</em> <a href="#rfc.xref.Part3.2">3.1</a>, <a href="#rfc.xref.Part3.8">4 .3</a></li>3626 <li><em>Section 6.8</em> <a href="#rfc.xref.Part3.2">3.1</a>, <a href="#rfc.xref.Part3.8">4</a></li> 3632 3627 </ul> 3633 3628 </li> 3634 <li><em>Part4</em> <a href="#rfc.xref.Part4.1">3.2</a>, <a href="#rfc.xref.Part4.2">3.2</a>, <a href="#rfc.xref.Part4.3">3.2</a>, <a href="#rfc.xref.Part4.4">3.2</a>, <a href="#rfc.xref.Part4.5">3.3</a>, <a href="#rfc.xref.Part4.6">4.1</a>, <a href="#rfc.xref.Part4.7">4.1</a>, <a href="#rfc.xref.Part4.8">4.1</a>, <a href="#rfc.xref.Part4.9">4. 3.2.2</a>, <a href="#rfc.xref.Part4.10">4.3.3</a>, <a href="#Part4"><b>11.1</b></a>, <a href="#rfc.xref.Part4.11">C.2</a><ul>3635 <li><em>Section 2.3</em> <a href="#rfc.xref.Part4.5">3.3</a>, <a href="#rfc.xref.Part4.9">4. 3.2.2</a></li>3629 <li><em>Part4</em> <a href="#rfc.xref.Part4.1">3.2</a>, <a href="#rfc.xref.Part4.2">3.2</a>, <a href="#rfc.xref.Part4.3">3.2</a>, <a href="#rfc.xref.Part4.4">3.2</a>, <a href="#rfc.xref.Part4.5">3.3</a>, <a href="#rfc.xref.Part4.6">4.1</a>, <a href="#rfc.xref.Part4.7">4.1</a>, <a href="#rfc.xref.Part4.8">4.1</a>, <a href="#rfc.xref.Part4.9">4.4.2</a>, <a href="#rfc.xref.Part4.10">4.5</a>, <a href="#Part4"><b>11.1</b></a>, <a href="#rfc.xref.Part4.11">C.2</a><ul> 3630 <li><em>Section 2.3</em> <a href="#rfc.xref.Part4.5">3.3</a>, <a href="#rfc.xref.Part4.9">4.4.2</a></li> 3636 3631 <li><em>Section 3.1</em> <a href="#rfc.xref.Part4.1">3.2</a></li> 3637 3632 <li><em>Section 3.2</em> <a href="#rfc.xref.Part4.3">3.2</a></li> … … 3639 3634 <li><em>Section 3.4</em> <a href="#rfc.xref.Part4.4">3.2</a></li> 3640 3635 <li><em>Section 4</em> <a href="#rfc.xref.Part4.6">4.1</a></li> 3641 <li><em>Section 4.1</em> <a href="#rfc.xref.Part4.7">4.1</a>, <a href="#rfc.xref.Part4.10">4. 3.3</a></li>3636 <li><em>Section 4.1</em> <a href="#rfc.xref.Part4.7">4.1</a>, <a href="#rfc.xref.Part4.10">4.5</a></li> 3642 3637 <li><em>Section 4.2</em> <a href="#rfc.xref.Part4.8">4.1</a></li> 3643 3638 </ul> … … 3652 3647 </ul> 3653 3648 </li> 3654 <li><em>Part6</em> <a href="#rfc.xref.Part6.1">2.2.1</a>, <a href="#rfc.xref.Part6.2">2.3.2</a>, <a href="#rfc.xref.Part6.3">2.3.3</a>, <a href="#rfc.xref.Part6.4">2.3.4</a>, <a href="#rfc.xref.Part6.5">2.3.5</a>, <a href="#rfc.xref.Part6.6">2.3.6</a>, <a href="#rfc.xref.Part6.7">3.1</a>, <a href="#rfc.xref.Part6.8">3.3</a>, <a href="#rfc.xref.Part6.9">3.3</a>, <a href="#rfc.xref.Part6.10">4.2.1</a>, <a href="#rfc.xref.Part6.11">4. 3.2.1</a>, <a href="#rfc.xref.Part6.12">4.3.2.4</a>, <a href="#rfc.xref.Part6.13">4.3.2.4</a>, <a href="#rfc.xref.Part6.14">4.3.2.4</a>, <a href="#rfc.xref.Part6.15">4.3.3.1</a>, <a href="#rfc.xref.Part6.16">4.3.3.2</a>, <a href="#rfc.xref.Part6.17">4.3.4.9</a>, <a href="#Part6"><b>11.1</b></a><ul>3649 <li><em>Part6</em> <a href="#rfc.xref.Part6.1">2.2.1</a>, <a href="#rfc.xref.Part6.2">2.3.2</a>, <a href="#rfc.xref.Part6.3">2.3.3</a>, <a href="#rfc.xref.Part6.4">2.3.4</a>, <a href="#rfc.xref.Part6.5">2.3.5</a>, <a href="#rfc.xref.Part6.6">2.3.6</a>, <a href="#rfc.xref.Part6.7">3.1</a>, <a href="#rfc.xref.Part6.8">3.3</a>, <a href="#rfc.xref.Part6.9">3.3</a>, <a href="#rfc.xref.Part6.10">4.2.1</a>, <a href="#rfc.xref.Part6.11">4.4.1</a>, <a href="#rfc.xref.Part6.12">4.4.4</a>, <a href="#rfc.xref.Part6.13">4.4.4</a>, <a href="#rfc.xref.Part6.14">4.4.4</a>, <a href="#rfc.xref.Part6.15">4.5.1</a>, <a href="#rfc.xref.Part6.16">4.5.2</a>, <a href="#rfc.xref.Part6.17">4.6.9</a>, <a href="#Part6"><b>11.1</b></a><ul> 3655 3650 <li><em>Section 2.3.1</em> <a href="#rfc.xref.Part6.4">2.3.4</a></li> 3656 <li><em>Section 2.3.1.1</em> <a href="#rfc.xref.Part6.11">4. 3.2.1</a>, <a href="#rfc.xref.Part6.14">4.3.2.4</a>, <a href="#rfc.xref.Part6.15">4.3.3.1</a>, <a href="#rfc.xref.Part6.16">4.3.3.2</a>, <a href="#rfc.xref.Part6.17">4.3.4.9</a></li>3651 <li><em>Section 2.3.1.1</em> <a href="#rfc.xref.Part6.11">4.4.1</a>, <a href="#rfc.xref.Part6.14">4.4.4</a>, <a href="#rfc.xref.Part6.15">4.5.1</a>, <a href="#rfc.xref.Part6.16">4.5.2</a>, <a href="#rfc.xref.Part6.17">4.6.9</a></li> 3657 3652 <li><em>Section 2.5</em> <a href="#rfc.xref.Part6.3">2.3.3</a></li> 3658 3653 <li><em>Section 2.6</em> <a href="#rfc.xref.Part6.5">2.3.5</a>, <a href="#rfc.xref.Part6.6">2.3.6</a></li> 3659 3654 <li><em>Section 3.1</em> <a href="#rfc.xref.Part6.8">3.3</a></li> 3660 <li><em>Section 3.2</em> <a href="#rfc.xref.Part6.12">4. 3.2.4</a></li>3655 <li><em>Section 3.2</em> <a href="#rfc.xref.Part6.12">4.4.4</a></li> 3661 3656 <li><em>Section 3.5</em> <a href="#rfc.xref.Part6.9">3.3</a></li> 3662 <li><em>Section 3.6</em> <a href="#rfc.xref.Part6.13">4. 3.2.4</a></li>3657 <li><em>Section 3.6</em> <a href="#rfc.xref.Part6.13">4.4.4</a></li> 3663 3658 </ul> 3664 3659 </li> … … 3679 3674 <li><a id="rfc.index.R" href="#rfc.index.R"><b>R</b></a><ul> 3680 3675 <li>Referer header field <a href="#rfc.xref.header.referer.1">3.2</a>, <a href="#rfc.iref.r.1"><b>7.7</b></a>, <a href="#rfc.xref.header.referer.2">8.3</a>, <a href="#rfc.xref.header.referer.3">A</a></li> 3681 <li>Retry-After header field <a href="#rfc.xref.header.retry-after.1">3.3</a>, <a href="#rfc.xref.header.retry-after.2">4. 3.5.4</a>, <a href="#rfc.iref.r.2"><b>7.8</b></a>, <a href="#rfc.xref.header.retry-after.3">8.3</a></li>3676 <li>Retry-After header field <a href="#rfc.xref.header.retry-after.1">3.3</a>, <a href="#rfc.xref.header.retry-after.2">4.7.4</a>, <a href="#rfc.iref.r.2"><b>7.8</b></a>, <a href="#rfc.xref.header.retry-after.3">8.3</a></li> 3682 3677 <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>11.2</b></a><ul> 3683 3678 <li><em>Section 5.2.14</em> <a href="#rfc.xref.RFC1123.2">6.1</a></li> 3684 3679 </ul> 3685 3680 </li> 3686 <li><em>RFC1945</em> <a href="#rfc.xref.RFC1945.1">4. 3.3</a>, <a href="#RFC1945"><b>11.2</b></a><ul>3687 <li><em>Section 9.3</em> <a href="#rfc.xref.RFC1945.1">4. 3.3</a></li>3681 <li><em>RFC1945</em> <a href="#rfc.xref.RFC1945.1">4.5</a>, <a href="#RFC1945"><b>11.2</b></a><ul> 3682 <li><em>Section 9.3</em> <a href="#rfc.xref.RFC1945.1">4.5</a></li> 3688 3683 </ul> 3689 3684 </li> 3690 <li><em>RFC2068</em> <a href="#rfc.xref.RFC2068.1">4. 3.3</a>, <a href="#rfc.xref.RFC2068.2">4.3.3</a>, <a href="#RFC2068"><b>11.2</b></a><ul>3691 <li><em>Section 10.3</em> <a href="#rfc.xref.RFC2068.2">4. 3.3</a></li>3692 <li><em>Section 10.3.4</em> <a href="#rfc.xref.RFC2068.1">4. 3.3</a></li>3685 <li><em>RFC2068</em> <a href="#rfc.xref.RFC2068.1">4.5</a>, <a href="#rfc.xref.RFC2068.2">4.5</a>, <a href="#RFC2068"><b>11.2</b></a><ul> 3686 <li><em>Section 10.3</em> <a href="#rfc.xref.RFC2068.2">4.5</a></li> 3687 <li><em>Section 10.3.4</em> <a href="#rfc.xref.RFC2068.1">4.5</a></li> 3693 3688 </ul> 3694 3689 </li> 3695 3690 <li><em>RFC2119</em> <a href="#rfc.xref.RFC2119.1">1.1</a>, <a href="#RFC2119"><b>11.1</b></a></li> 3696 <li><em>RFC2616</em> <a href="#rfc.xref.RFC2616.1">1</a>, <a href="#rfc.xref.RFC2616.2">4. 3.3</a>, <a href="#RFC2616"><b>11.2</b></a>, <a href="#rfc.xref.RFC2616.3">C.1</a><ul>3697 <li><em>Section 10.3.8</em> <a href="#rfc.xref.RFC2616.2">4. 3.3</a></li>3691 <li><em>RFC2616</em> <a href="#rfc.xref.RFC2616.1">1</a>, <a href="#rfc.xref.RFC2616.2">4.5</a>, <a href="#RFC2616"><b>11.2</b></a>, <a href="#rfc.xref.RFC2616.3">C.1</a><ul> 3692 <li><em>Section 10.3.8</em> <a href="#rfc.xref.RFC2616.2">4.5</a></li> 3698 3693 </ul> 3699 3694 </li> … … 3734 3729 <li>Status Codes 3735 3730 <ul> 3736 <li>100 Continue <a href="#rfc.xref.status.100.1">4.1</a>, <a href="#rfc.iref.s.2"><b>4.3.1 .1</b></a>, <a href="#rfc.xref.status.100.2">8.2</a></li>3737 <li>101 Switching Protocols <a href="#rfc.xref.status.101.1">4.1</a>, <a href="#rfc.iref.s.3"><b>4.3. 1.2</b></a>, <a href="#rfc.xref.status.101.2">8.2</a></li>3738 <li>200 OK <a href="#rfc.xref.status.200.1">4.1</a>, <a href="#rfc.iref.s.4"><b>4. 3.2.1</b></a>, <a href="#rfc.xref.status.200.2">8.2</a></li>3739 <li>201 Created <a href="#rfc.xref.status.201.1">4.1</a>, <a href="#rfc.iref.s.5"><b>4. 3.2.2</b></a>, <a href="#rfc.xref.status.201.2">8.2</a></li>3740 <li>202 Accepted <a href="#rfc.xref.status.202.1">4.1</a>, <a href="#rfc.iref.s.6"><b>4. 3.2.3</b></a>, <a href="#rfc.xref.status.202.2">8.2</a></li>3741 <li>203 Non-Authoritative Information <a href="#rfc.xref.status.203.1">4.1</a>, <a href="#rfc.iref.s.7"><b>4. 3.2.4</b></a>, <a href="#rfc.xref.status.203.2">8.2</a>, <a href="#rfc.xref.status.203.3">A</a></li>3742 <li>204 No Content <a href="#rfc.xref.status.204.1">4.1</a>, <a href="#rfc.iref.s.8"><b>4. 3.2.5</b></a>, <a href="#rfc.xref.status.204.2">8.2</a></li>3743 <li>205 Reset Content <a href="#rfc.xref.status.205.1">4.1</a>, <a href="#rfc.iref.s.9"><b>4. 3.2.6</b></a>, <a href="#rfc.xref.status.205.2">8.2</a></li>3744 <li>300 Multiple Choices <a href="#rfc.xref.status.300.1">4.1</a>, <a href="#rfc.iref.s.10"><b>4. 3.3.1</b></a>, <a href="#rfc.xref.status.300.2">8.2</a></li>3745 <li>301 Moved Permanently <a href="#rfc.xref.status.301.1">4.1</a>, <a href="#rfc.iref.s.11"><b>4. 3.3.2</b></a>, <a href="#rfc.xref.status.301.2">8.2</a>, <a href="#rfc.xref.status.301.3">A</a></li>3746 <li>302 Found <a href="#rfc.xref.status.302.1">4.1</a>, <a href="#rfc.iref.s.12"><b>4. 3.3.3</b></a>, <a href="#rfc.xref.status.302.2">8.2</a>, <a href="#rfc.xref.status.302.3">A</a></li>3747 <li>303 See Other <a href="#rfc.xref.status.303.1">4.1</a>, <a href="#rfc.iref.s.13"><b>4. 3.3.4</b></a>, <a href="#rfc.xref.status.303.2">8.2</a></li>3748 <li>305 Use Proxy <a href="#rfc.xref.status.305.1">4.1</a>, <a href="#rfc.iref.s.14"><b>4. 3.3.5</b></a>, <a href="#rfc.xref.status.305.2">8.2</a>, <a href="#rfc.xref.status.305.3">A</a></li>3749 <li>306 (Unused) <a href="#rfc.iref.s.15"><b>4. 3.3.6</b></a>, <a href="#rfc.xref.status.306.1">8.2</a></li>3750 <li>307 Temporary Redirect <a href="#rfc.xref.status.307.1">4.1</a>, <a href="#rfc.iref.s.16"><b>4. 3.3.7</b></a>, <a href="#rfc.xref.status.307.2">8.2</a>, <a href="#rfc.xref.status.307.3">A</a></li>3751 <li>400 Bad Request <a href="#rfc.xref.status.400.1">4.1</a>, <a href="#rfc.iref.s.17"><b>4. 3.4.1</b></a>, <a href="#rfc.xref.status.400.2">8.2</a></li>3752 <li>402 Payment Required <a href="#rfc.xref.status.402.1">4.1</a>, <a href="#rfc.iref.s.18"><b>4. 3.4.2</b></a>, <a href="#rfc.xref.status.402.2">8.2</a></li>3753 <li>403 Forbidden <a href="#rfc.xref.status.403.1">4.1</a>, <a href="#rfc.iref.s.19"><b>4. 3.4.3</b></a>, <a href="#rfc.xref.status.403.2">8.2</a></li>3754 <li>404 Not Found <a href="#rfc.xref.status.404.1">4.1</a>, <a href="#rfc.iref.s.20"><b>4. 3.4.4</b></a>, <a href="#rfc.xref.status.404.2">8.2</a></li>3755 <li>405 Method Not Allowed <a href="#rfc.xref.status.405.1">4.1</a>, <a href="#rfc.iref.s.21"><b>4. 3.4.5</b></a>, <a href="#rfc.xref.status.405.2">8.2</a></li>3756 <li>406 Not Acceptable <a href="#rfc.xref.status.406.1">4.1</a>, <a href="#rfc.iref.s.22"><b>4. 3.4.6</b></a>, <a href="#rfc.xref.status.406.2">8.2</a></li>3757 <li>408 Request Timeout <a href="#rfc.xref.status.408.1">4.1</a>, <a href="#rfc.iref.s.23"><b>4. 3.4.7</b></a>, <a href="#rfc.xref.status.408.2">8.2</a></li>3758 <li>409 Conflict <a href="#rfc.xref.status.409.1">4.1</a>, <a href="#rfc.iref.s.24"><b>4. 3.4.8</b></a>, <a href="#rfc.xref.status.409.2">8.2</a></li>3759 <li>410 Gone <a href="#rfc.xref.status.410.1">4.1</a>, <a href="#rfc.iref.s.25"><b>4. 3.4.9</b></a>, <a href="#rfc.xref.status.410.2">8.2</a></li>3760 <li>411 Length Required <a href="#rfc.xref.status.411.1">4.1</a>, <a href="#rfc.iref.s.26"><b>4. 3.4.10</b></a>, <a href="#rfc.xref.status.411.2">8.2</a></li>3761 <li>413 Request Representation Too Large <a href="#rfc.xref.status.413.1">4.1</a>, <a href="#rfc.iref.s.27"><b>4. 3.4.11</b></a>, <a href="#rfc.xref.status.413.2">8.2</a></li>3762 <li>414 URI Too Long <a href="#rfc.xref.status.414.1">4.1</a>, <a href="#rfc.iref.s.28"><b>4. 3.4.12</b></a>, <a href="#rfc.xref.status.414.2">8.2</a></li>3763 <li>415 Unsupported Media Type <a href="#rfc.xref.status.415.1">4.1</a>, <a href="#rfc.iref.s.29"><b>4. 3.4.13</b></a>, <a href="#rfc.xref.status.415.2">8.2</a></li>3764 <li>417 Expectation Failed <a href="#rfc.xref.status.417.1">4.1</a>, <a href="#rfc.iref.s.30"><b>4. 3.4.14</b></a>, <a href="#rfc.xref.status.417.2">8.2</a></li>3765 <li>426 Upgrade Required <a href="#rfc.xref.status.426.1">4.1</a>, <a href="#rfc.iref.s.31"><b>4. 3.4.15</b></a>, <a href="#rfc.xref.status.426.2">8.2</a>, <a href="#rfc.xref.status.426.3">A</a></li>3766 <li>500 Internal Server Error <a href="#rfc.xref.status.500.1">4.1</a>, <a href="#rfc.iref.s.32"><b>4. 3.5.1</b></a>, <a href="#rfc.xref.status.500.2">8.2</a></li>3767 <li>501 Not Implemented <a href="#rfc.xref.status.501.1">4.1</a>, <a href="#rfc.iref.s.33"><b>4. 3.5.2</b></a>, <a href="#rfc.xref.status.501.2">8.2</a></li>3768 <li>502 Bad Gateway <a href="#rfc.xref.status.502.1">4.1</a>, <a href="#rfc.iref.s.34"><b>4. 3.5.3</b></a>, <a href="#rfc.xref.status.502.2">8.2</a></li>3769 <li>503 Service Unavailable <a href="#rfc.xref.status.503.1">4.1</a>, <a href="#rfc.iref.s.35"><b>4. 3.5.4</b></a>, <a href="#rfc.xref.status.503.2">8.2</a></li>3770 <li>504 Gateway Timeout <a href="#rfc.xref.status.504.1">4.1</a>, <a href="#rfc.iref.s.36"><b>4. 3.5.5</b></a>, <a href="#rfc.xref.status.504.2">8.2</a></li>3771 <li>505 HTTP Version Not Supported <a href="#rfc.xref.status.505.1">4.1</a>, <a href="#rfc.iref.s.37"><b>4. 3.5.6</b></a>, <a href="#rfc.xref.status.505.2">8.2</a></li>3731 <li>100 Continue <a href="#rfc.xref.status.100.1">4.1</a>, <a href="#rfc.iref.s.2"><b>4.3.1</b></a>, <a href="#rfc.xref.status.100.2">8.2</a></li> 3732 <li>101 Switching Protocols <a href="#rfc.xref.status.101.1">4.1</a>, <a href="#rfc.iref.s.3"><b>4.3.2</b></a>, <a href="#rfc.xref.status.101.2">8.2</a></li> 3733 <li>200 OK <a href="#rfc.xref.status.200.1">4.1</a>, <a href="#rfc.iref.s.4"><b>4.4.1</b></a>, <a href="#rfc.xref.status.200.2">8.2</a></li> 3734 <li>201 Created <a href="#rfc.xref.status.201.1">4.1</a>, <a href="#rfc.iref.s.5"><b>4.4.2</b></a>, <a href="#rfc.xref.status.201.2">8.2</a></li> 3735 <li>202 Accepted <a href="#rfc.xref.status.202.1">4.1</a>, <a href="#rfc.iref.s.6"><b>4.4.3</b></a>, <a href="#rfc.xref.status.202.2">8.2</a></li> 3736 <li>203 Non-Authoritative Information <a href="#rfc.xref.status.203.1">4.1</a>, <a href="#rfc.iref.s.7"><b>4.4.4</b></a>, <a href="#rfc.xref.status.203.2">8.2</a>, <a href="#rfc.xref.status.203.3">A</a></li> 3737 <li>204 No Content <a href="#rfc.xref.status.204.1">4.1</a>, <a href="#rfc.iref.s.8"><b>4.4.5</b></a>, <a href="#rfc.xref.status.204.2">8.2</a></li> 3738 <li>205 Reset Content <a href="#rfc.xref.status.205.1">4.1</a>, <a href="#rfc.iref.s.9"><b>4.4.6</b></a>, <a href="#rfc.xref.status.205.2">8.2</a></li> 3739 <li>300 Multiple Choices <a href="#rfc.xref.status.300.1">4.1</a>, <a href="#rfc.iref.s.10"><b>4.5.1</b></a>, <a href="#rfc.xref.status.300.2">8.2</a></li> 3740 <li>301 Moved Permanently <a href="#rfc.xref.status.301.1">4.1</a>, <a href="#rfc.iref.s.11"><b>4.5.2</b></a>, <a href="#rfc.xref.status.301.2">8.2</a>, <a href="#rfc.xref.status.301.3">A</a></li> 3741 <li>302 Found <a href="#rfc.xref.status.302.1">4.1</a>, <a href="#rfc.iref.s.12"><b>4.5.3</b></a>, <a href="#rfc.xref.status.302.2">8.2</a>, <a href="#rfc.xref.status.302.3">A</a></li> 3742 <li>303 See Other <a href="#rfc.xref.status.303.1">4.1</a>, <a href="#rfc.iref.s.13"><b>4.5.4</b></a>, <a href="#rfc.xref.status.303.2">8.2</a></li> 3743 <li>305 Use Proxy <a href="#rfc.xref.status.305.1">4.1</a>, <a href="#rfc.iref.s.14"><b>4.5.5</b></a>, <a href="#rfc.xref.status.305.2">8.2</a>, <a href="#rfc.xref.status.305.3">A</a></li> 3744 <li>306 (Unused) <a href="#rfc.iref.s.15"><b>4.5.6</b></a>, <a href="#rfc.xref.status.306.1">8.2</a></li> 3745 <li>307 Temporary Redirect <a href="#rfc.xref.status.307.1">4.1</a>, <a href="#rfc.iref.s.16"><b>4.5.7</b></a>, <a href="#rfc.xref.status.307.2">8.2</a>, <a href="#rfc.xref.status.307.3">A</a></li> 3746 <li>400 Bad Request <a href="#rfc.xref.status.400.1">4.1</a>, <a href="#rfc.iref.s.17"><b>4.6.1</b></a>, <a href="#rfc.xref.status.400.2">8.2</a></li> 3747 <li>402 Payment Required <a href="#rfc.xref.status.402.1">4.1</a>, <a href="#rfc.iref.s.18"><b>4.6.2</b></a>, <a href="#rfc.xref.status.402.2">8.2</a></li> 3748 <li>403 Forbidden <a href="#rfc.xref.status.403.1">4.1</a>, <a href="#rfc.iref.s.19"><b>4.6.3</b></a>, <a href="#rfc.xref.status.403.2">8.2</a></li> 3749 <li>404 Not Found <a href="#rfc.xref.status.404.1">4.1</a>, <a href="#rfc.iref.s.20"><b>4.6.4</b></a>, <a href="#rfc.xref.status.404.2">8.2</a></li> 3750 <li>405 Method Not Allowed <a href="#rfc.xref.status.405.1">4.1</a>, <a href="#rfc.iref.s.21"><b>4.6.5</b></a>, <a href="#rfc.xref.status.405.2">8.2</a></li> 3751 <li>406 Not Acceptable <a href="#rfc.xref.status.406.1">4.1</a>, <a href="#rfc.iref.s.22"><b>4.6.6</b></a>, <a href="#rfc.xref.status.406.2">8.2</a></li> 3752 <li>408 Request Timeout <a href="#rfc.xref.status.408.1">4.1</a>, <a href="#rfc.iref.s.23"><b>4.6.7</b></a>, <a href="#rfc.xref.status.408.2">8.2</a></li> 3753 <li>409 Conflict <a href="#rfc.xref.status.409.1">4.1</a>, <a href="#rfc.iref.s.24"><b>4.6.8</b></a>, <a href="#rfc.xref.status.409.2">8.2</a></li> 3754 <li>410 Gone <a href="#rfc.xref.status.410.1">4.1</a>, <a href="#rfc.iref.s.25"><b>4.6.9</b></a>, <a href="#rfc.xref.status.410.2">8.2</a></li> 3755 <li>411 Length Required <a href="#rfc.xref.status.411.1">4.1</a>, <a href="#rfc.iref.s.26"><b>4.6.10</b></a>, <a href="#rfc.xref.status.411.2">8.2</a></li> 3756 <li>413 Request Representation Too Large <a href="#rfc.xref.status.413.1">4.1</a>, <a href="#rfc.iref.s.27"><b>4.6.11</b></a>, <a href="#rfc.xref.status.413.2">8.2</a></li> 3757 <li>414 URI Too Long <a href="#rfc.xref.status.414.1">4.1</a>, <a href="#rfc.iref.s.28"><b>4.6.12</b></a>, <a href="#rfc.xref.status.414.2">8.2</a></li> 3758 <li>415 Unsupported Media Type <a href="#rfc.xref.status.415.1">4.1</a>, <a href="#rfc.iref.s.29"><b>4.6.13</b></a>, <a href="#rfc.xref.status.415.2">8.2</a></li> 3759 <li>417 Expectation Failed <a href="#rfc.xref.status.417.1">4.1</a>, <a href="#rfc.iref.s.30"><b>4.6.14</b></a>, <a href="#rfc.xref.status.417.2">8.2</a></li> 3760 <li>426 Upgrade Required <a href="#rfc.xref.status.426.1">4.1</a>, <a href="#rfc.iref.s.31"><b>4.6.15</b></a>, <a href="#rfc.xref.status.426.2">8.2</a>, <a href="#rfc.xref.status.426.3">A</a></li> 3761 <li>500 Internal Server Error <a href="#rfc.xref.status.500.1">4.1</a>, <a href="#rfc.iref.s.32"><b>4.7.1</b></a>, <a href="#rfc.xref.status.500.2">8.2</a></li> 3762 <li>501 Not Implemented <a href="#rfc.xref.status.501.1">4.1</a>, <a href="#rfc.iref.s.33"><b>4.7.2</b></a>, <a href="#rfc.xref.status.501.2">8.2</a></li> 3763 <li>502 Bad Gateway <a href="#rfc.xref.status.502.1">4.1</a>, <a href="#rfc.iref.s.34"><b>4.7.3</b></a>, <a href="#rfc.xref.status.502.2">8.2</a></li> 3764 <li>503 Service Unavailable <a href="#rfc.xref.status.503.1">4.1</a>, <a href="#rfc.iref.s.35"><b>4.7.4</b></a>, <a href="#rfc.xref.status.503.2">8.2</a></li> 3765 <li>504 Gateway Timeout <a href="#rfc.xref.status.504.1">4.1</a>, <a href="#rfc.iref.s.36"><b>4.7.5</b></a>, <a href="#rfc.xref.status.504.2">8.2</a></li> 3766 <li>505 HTTP Version Not Supported <a href="#rfc.xref.status.505.1">4.1</a>, <a href="#rfc.iref.s.37"><b>4.7.6</b></a>, <a href="#rfc.xref.status.505.2">8.2</a></li> 3772 3767 </ul> 3773 3768 </li> -
draft-ietf-httpbis/latest/p2-semantics.xml
r1619 r1621 1104 1104 </list> 1105 1105 </t> 1106 <t> 1107 For most status codes the response can carry a payload, in which case a 1108 Content-Type header field indicates the payload's media type 1109 (&header-content-type;). 1110 </t> 1106 1111 1107 1112 <section title="Overview of Status Codes" anchor="overview.of.status.codes"> 1108 1113 <t> 1109 The status codes listed below are defined in <xref target="status.codes"/>1110 of this specification,&p4-status-codes;, &p5-status-codes;, and &p7-status-codes;.1114 The status codes listed below are defined in this specification, 1115 &p4-status-codes;, &p5-status-codes;, and &p7-status-codes;. 1111 1116 The reason phrases listed here are only recommendations — they can be 1112 1117 replaced by local equivalents without affecting the protocol. … … 1204 1209 <t> 1205 1210 New HTTP status codes are required to fall under one of the categories 1206 defined in <xref target="status.code s"/>. To allow existing parsers to1211 defined in <xref target="status.code.and.reason.phrase"/>. To allow existing parsers to 1207 1212 properly handle them, new status codes cannot disallow a response body, 1208 1213 although they can mandate a zero-length response body. They can require the … … 1220 1225 1221 1226 </section> 1222 1223 <section title="Status Code Definitions" anchor="status.codes">1224 <t>1225 Each status-code is described below, including any metadata required1226 in the response.1227 </t>1228 <t>1229 For most status codes the response can carry a payload, in which case a1230 Content-Type header field indicates the payload's media type1231 (&header-content-type;).1232 </t>1233 1227 1234 1228 <section title="Informational 1xx" anchor="status.1xx"> … … 2056 2050 </section> 2057 2051 </section> 2058 </section>2059 2052 2060 2053 </section>
Note: See TracChangeset
for help on using the changeset viewer.