Changeset 1617 for draft-ietf-httpbis/latest/p2-semantics.html
- Timestamp:
- 26/03/12 13:49:01 (9 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p2-semantics.html
r1615 r1617 489 489 <link rel="Chapter" title="6 Method Definitions" href="#rfc.section.6"> 490 490 <link rel="Chapter" title="7 Status Code Definitions" href="#rfc.section.7"> 491 <link rel="Chapter" title="8 Date/Time Formats" href="#rfc.section.8"> 492 <link rel="Chapter" title="9 Product Tokens" href="#rfc.section.9"> 493 <link rel="Chapter" title="10 Header Field Definitions" href="#rfc.section.10"> 494 <link rel="Chapter" title="11 IANA Considerations" href="#rfc.section.11"> 495 <link rel="Chapter" title="12 Security Considerations" href="#rfc.section.12"> 496 <link rel="Chapter" title="13 Acknowledgments" href="#rfc.section.13"> 497 <link rel="Chapter" href="#rfc.section.14" title="14 References"> 491 <link rel="Chapter" title="8 Common Protocol Parameters" href="#rfc.section.8"> 492 <link rel="Chapter" title="9 Header Field Definitions" href="#rfc.section.9"> 493 <link rel="Chapter" title="10 IANA Considerations" href="#rfc.section.10"> 494 <link rel="Chapter" title="11 Security Considerations" href="#rfc.section.11"> 495 <link rel="Chapter" title="12 Acknowledgments" href="#rfc.section.12"> 496 <link rel="Chapter" href="#rfc.section.13" title="13 References"> 498 497 <link rel="Appendix" title="A Changes from RFC 2616" href="#rfc.section.A"> 499 498 <link rel="Appendix" title="B Collected ABNF" href="#rfc.section.B"> … … 696 695 </ul> 697 696 </li> 698 <li>8. <a href="#http.date">Date/Time Formats</a></li> 699 <li>9. <a href="#product.tokens">Product Tokens</a></li> 700 <li>10. <a href="#header.field.definitions">Header Field Definitions</a><ul> 701 <li>10.1 <a href="#header.allow">Allow</a></li> 702 <li>10.2 <a href="#header.date">Date</a></li> 703 <li>10.3 <a href="#header.expect">Expect</a></li> 704 <li>10.4 <a href="#header.from">From</a></li> 705 <li>10.5 <a href="#header.location">Location</a></li> 706 <li>10.6 <a href="#header.max-forwards">Max-Forwards</a></li> 707 <li>10.7 <a href="#header.referer">Referer</a></li> 708 <li>10.8 <a href="#header.retry-after">Retry-After</a></li> 709 <li>10.9 <a href="#header.server">Server</a></li> 710 <li>10.10 <a href="#header.user-agent">User-Agent</a></li> 697 <li>8. <a href="#common.protocol.parameters">Common Protocol Parameters</a><ul> 698 <li>8.1 <a href="#http.date">Date/Time Formats</a></li> 699 <li>8.2 <a href="#product.tokens">Product Tokens</a></li> 711 700 </ul> 712 701 </li> 713 <li>11. <a href="#IANA.considerations">IANA Considerations</a><ul> 714 <li>11.1 <a href="#method.registration">Method Registry</a></li> 715 <li>11.2 <a href="#status.code.registration">Status Code Registry</a></li> 716 <li>11.3 <a href="#header.field.registration">Header Field Registration</a></li> 702 <li>9. <a href="#header.field.definitions">Header Field Definitions</a><ul> 703 <li>9.1 <a href="#header.allow">Allow</a></li> 704 <li>9.2 <a href="#header.date">Date</a></li> 705 <li>9.3 <a href="#header.expect">Expect</a></li> 706 <li>9.4 <a href="#header.from">From</a></li> 707 <li>9.5 <a href="#header.location">Location</a></li> 708 <li>9.6 <a href="#header.max-forwards">Max-Forwards</a></li> 709 <li>9.7 <a href="#header.referer">Referer</a></li> 710 <li>9.8 <a href="#header.retry-after">Retry-After</a></li> 711 <li>9.9 <a href="#header.server">Server</a></li> 712 <li>9.10 <a href="#header.user-agent">User-Agent</a></li> 717 713 </ul> 718 714 </li> 719 <li>12. <a href="#security.considerations">Security Considerations</a><ul> 720 <li>12.1 <a href="#security.sensitive">Transfer of Sensitive Information</a></li> 721 <li>12.2 <a href="#encoding.sensitive.information.in.uris">Encoding Sensitive Information in URIs</a></li> 722 <li>12.3 <a href="#location.spoofing-leakage">Location Header Fields: Spoofing and Information Leakage</a></li> 723 <li>12.4 <a href="#rfc.section.12.4">Security Considerations for CONNECT</a></li> 715 <li>10. <a href="#IANA.considerations">IANA Considerations</a><ul> 716 <li>10.1 <a href="#method.registration">Method Registry</a></li> 717 <li>10.2 <a href="#status.code.registration">Status Code Registry</a></li> 718 <li>10.3 <a href="#header.field.registration">Header Field Registration</a></li> 724 719 </ul> 725 720 </li> 726 <li>13. <a href="#acks">Acknowledgments</a></li> 727 <li>14. <a href="#rfc.references">References</a><ul> 728 <li>14.1 <a href="#rfc.references.1">Normative References</a></li> 729 <li>14.2 <a href="#rfc.references.2">Informative References</a></li> 721 <li>11. <a href="#security.considerations">Security Considerations</a><ul> 722 <li>11.1 <a href="#security.sensitive">Transfer of Sensitive Information</a></li> 723 <li>11.2 <a href="#encoding.sensitive.information.in.uris">Encoding Sensitive Information in URIs</a></li> 724 <li>11.3 <a href="#location.spoofing-leakage">Location Header Fields: Spoofing and Information Leakage</a></li> 725 <li>11.4 <a href="#rfc.section.11.4">Security Considerations for CONNECT</a></li> 726 </ul> 727 </li> 728 <li>12. <a href="#acks">Acknowledgments</a></li> 729 <li>13. <a href="#rfc.references">References</a><ul> 730 <li>13.1 <a href="#rfc.references.1">Normative References</a></li> 731 <li>13.2 <a href="#rfc.references.2">Informative References</a></li> 730 732 </ul> 731 733 </li> … … 815 817 </p> 816 818 <div id="rfc.figure.u.3"></div><pre class="inline"><span id="rfc.iref.g.1"></span> <a href="#method" class="smpl">method</a> = <a href="#core.rules" class="smpl">token</a> 817 </pre><p id="rfc.section.2.p.3">The list of methods allowed by a resource can be specified in an Allow header field (<a href="#header.allow" id="rfc.xref.header.allow.1" title="Allow">Section 10.1</a>). The status code of the response always notifies the client whether a method is currently allowed on a resource, since the819 </pre><p id="rfc.section.2.p.3">The list of methods allowed by a resource can be specified in an Allow header field (<a href="#header.allow" id="rfc.xref.header.allow.1" title="Allow">Section 9.1</a>). The status code of the response always notifies the client whether a method is currently allowed on a resource, since the 818 820 set of allowed methods can change dynamically. An origin server <em class="bcp14">SHOULD</em> respond with the status code 405 (Method Not Allowed) if the method is known by the origin server but not allowed for the 819 821 resource, and 501 (Not Implemented) if the method is unrecognized or not implemented by the origin server. The methods GET … … 1001 1003 <tr> 1002 1004 <td class="left">Expect</td> 1003 <td class="left"><a href="#header.expect" id="rfc.xref.header.expect.1" title="Expect">Section 10.3</a></td>1005 <td class="left"><a href="#header.expect" id="rfc.xref.header.expect.1" title="Expect">Section 9.3</a></td> 1004 1006 </tr> 1005 1007 <tr> 1006 1008 <td class="left">From</td> 1007 <td class="left"><a href="#header.from" id="rfc.xref.header.from.1" title="From">Section 10.4</a></td>1009 <td class="left"><a href="#header.from" id="rfc.xref.header.from.1" title="From">Section 9.4</a></td> 1008 1010 </tr> 1009 1011 <tr> … … 1033 1035 <tr> 1034 1036 <td class="left">Max-Forwards</td> 1035 <td class="left"><a href="#header.max-forwards" id="rfc.xref.header.max-forwards.1" title="Max-Forwards">Section 10.6</a></td>1037 <td class="left"><a href="#header.max-forwards" id="rfc.xref.header.max-forwards.1" title="Max-Forwards">Section 9.6</a></td> 1036 1038 </tr> 1037 1039 <tr> … … 1045 1047 <tr> 1046 1048 <td class="left">Referer</td> 1047 <td class="left"><a href="#header.referer" id="rfc.xref.header.referer.1" title="Referer">Section 10.7</a></td>1049 <td class="left"><a href="#header.referer" id="rfc.xref.header.referer.1" title="Referer">Section 9.7</a></td> 1048 1050 </tr> 1049 1051 <tr> … … 1053 1055 <tr> 1054 1056 <td class="left">User-Agent</td> 1055 <td class="left"><a href="#header.user-agent" id="rfc.xref.header.user-agent.1" title="User-Agent">Section 10.10</a></td>1057 <td class="left"><a href="#header.user-agent" id="rfc.xref.header.user-agent.1" title="User-Agent">Section 9.10</a></td> 1056 1058 </tr> 1057 1059 </tbody> … … 1081 1083 <tr> 1082 1084 <td class="left">Allow</td> 1083 <td class="left"><a href="#header.allow" id="rfc.xref.header.allow.2" title="Allow">Section 10.1</a></td>1085 <td class="left"><a href="#header.allow" id="rfc.xref.header.allow.2" title="Allow">Section 9.1</a></td> 1084 1086 </tr> 1085 1087 <tr> 1086 1088 <td class="left">Date</td> 1087 <td class="left"><a href="#header.date" id="rfc.xref.header.date.1" title="Date">Section 10.2</a></td>1089 <td class="left"><a href="#header.date" id="rfc.xref.header.date.1" title="Date">Section 9.2</a></td> 1088 1090 </tr> 1089 1091 <tr> … … 1093 1095 <tr> 1094 1096 <td class="left">Location</td> 1095 <td class="left"><a href="#header.location" id="rfc.xref.header.location.1" title="Location">Section 10.5</a></td>1097 <td class="left"><a href="#header.location" id="rfc.xref.header.location.1" title="Location">Section 9.5</a></td> 1096 1098 </tr> 1097 1099 <tr> … … 1101 1103 <tr> 1102 1104 <td class="left">Retry-After</td> 1103 <td class="left"><a href="#header.retry-after" id="rfc.xref.header.retry-after.1" title="Retry-After">Section 10.8</a></td>1105 <td class="left"><a href="#header.retry-after" id="rfc.xref.header.retry-after.1" title="Retry-After">Section 9.8</a></td> 1104 1106 </tr> 1105 1107 <tr> 1106 1108 <td class="left">Server</td> 1107 <td class="left"><a href="#header.server" id="rfc.xref.header.server.1" title="Server">Section 10.9</a></td>1109 <td class="left"><a href="#header.server" id="rfc.xref.header.server.1" title="Server">Section 9.9</a></td> 1108 1110 </tr> 1109 1111 <tr> … … 1458 1460 but might be defined by future extensions to HTTP. Content negotiation <em class="bcp14">MAY</em> be used to select the appropriate response format. If no response body is included, the response <em class="bcp14">MUST</em> include a Content-Length field with a field-value of "0". 1459 1461 </p> 1460 <p id="rfc.section.6.2.p.7">The Max-Forwards header field <em class="bcp14">MAY</em> be used to target a specific proxy in the request chain (see <a href="#header.max-forwards" id="rfc.xref.header.max-forwards.2" title="Max-Forwards">Section 10.6</a>). If no Max-Forwards field is present in the request, then the forwarded request <em class="bcp14">MUST NOT</em> include a Max-Forwards field.1462 <p id="rfc.section.6.2.p.7">The Max-Forwards header field <em class="bcp14">MAY</em> be used to target a specific proxy in the request chain (see <a href="#header.max-forwards" id="rfc.xref.header.max-forwards.2" title="Max-Forwards">Section 9.6</a>). If no Max-Forwards field is present in the request, then the forwarded request <em class="bcp14">MUST NOT</em> include a Max-Forwards field. 1461 1463 </p> 1462 1464 <h2 id="rfc.section.6.3"><a href="#rfc.section.6.3">6.3</a> <a id="GET" href="#GET">GET</a></h2> … … 1482 1484 <p id="rfc.section.6.3.p.6">The response to a GET request is cacheable and <em class="bcp14">MAY</em> be used to satisfy subsequent GET and HEAD requests (see <a href="#Part6" id="rfc.xref.Part6.6"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>). 1483 1485 </p> 1484 <p id="rfc.section.6.3.p.7">See <a href="#encoding.sensitive.information.in.uris" title="Encoding Sensitive Information in URIs">Section 1 2.2</a> for security considerations when used for forms.1486 <p id="rfc.section.6.3.p.7">See <a href="#encoding.sensitive.information.in.uris" title="Encoding Sensitive Information in URIs">Section 11.2</a> for security considerations when used for forms. 1485 1487 </p> 1486 1488 <h2 id="rfc.section.6.4"><a href="#rfc.section.6.4">6.4</a> <a id="HEAD" href="#HEAD">HEAD</a></h2> … … 1516 1518 </p> 1517 1519 <p id="rfc.section.6.5.p.4">If a resource has been created on the origin server, the response <em class="bcp14">SHOULD</em> be 201 (Created) and contain a representation which describes the status of the request and refers to the new resource, and 1518 a Location header field (see <a href="#header.location" id="rfc.xref.header.location.2" title="Location">Section 10.5</a>).1520 a Location header field (see <a href="#header.location" id="rfc.xref.header.location.2" title="Location">Section 9.5</a>). 1519 1521 </p> 1520 1522 <p id="rfc.section.6.5.p.5">Responses to POST requests are only cacheable when they include explicit freshness information (see <a href="p6-cache.html#calculating.freshness.lifetime" title="Calculating Freshness Lifetime">Section 2.3.1</a> of <a href="#Part6" id="rfc.xref.Part6.8"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>). A cached POST response with a Content-Location header field (see <a href="p3-payload.html#header.content-location" title="Content-Location">Section 6.7</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>) whose value is the effective Request URI <em class="bcp14">MAY</em> be used to satisfy subsequent GET and HEAD requests. … … 1606 1608 <div id="rfc.iref.m.7"></div> 1607 1609 <p id="rfc.section.6.8.p.1">The TRACE method requests a remote, application-layer loop-back of the request message. The final recipient of the request <em class="bcp14">SHOULD</em> reflect the message received back to the client as the message body of a 200 (OK) response. The final recipient is either 1608 the origin server or the first proxy to receive a Max-Forwards value of zero (0) in the request (see <a href="#header.max-forwards" id="rfc.xref.header.max-forwards.3" title="Max-Forwards">Section 10.6</a>). A TRACE request <em class="bcp14">MUST NOT</em> include a message body.1610 the origin server or the first proxy to receive a Max-Forwards value of zero (0) in the request (see <a href="#header.max-forwards" id="rfc.xref.header.max-forwards.3" title="Max-Forwards">Section 9.6</a>). A TRACE request <em class="bcp14">MUST NOT</em> include a message body. 1609 1611 </p> 1610 1612 <p id="rfc.section.6.8.p.2">TRACE allows the client to see what is being received at the other end of the request chain and use that data for testing … … 1818 1820 </p> 1819 1821 </div> 1820 <p id="rfc.section.7.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 10.5</a>.1822 <p id="rfc.section.7.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 9.5</a>. 1821 1823 </p> 1822 1824 <p id="rfc.section.7.3.p.5">Note that for methods not known to be "safe", as defined in <a href="#safe.methods" title="Safe Methods">Section 6.1.1</a>, automatic redirection needs to done with care, since the redirect might change the conditions under which the request was … … 2034 2036 <div id="rfc.iref.s.30"></div> 2035 2037 <h3 id="rfc.section.7.4.14"><a href="#rfc.section.7.4.14">7.4.14</a> <a id="status.417" href="#status.417">417 Expectation Failed</a></h3> 2036 <p id="rfc.section.7.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 10.3</a>) could not be met by this server, or, if the server is a proxy, the server has unambiguous evidence that the request could2038 <p id="rfc.section.7.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 9.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 2037 2039 not be met by the next-hop server. 2038 2040 </p> … … 2079 2081 <p id="rfc.section.7.5.4.p.1">The server is currently unable to handle the request due to a temporary overloading or maintenance of the server.</p> 2080 2082 <p id="rfc.section.7.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 the 2081 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 10.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.2083 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 9.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. 2082 2084 </p> 2083 2085 <div class="note" id="rfc.section.7.5.4.p.3"> … … 2103 2105 in <a href="p1-messaging.html#http.version" title="Protocol Versioning">Section 2.6</a> of <a href="#Part1" id="rfc.xref.Part1.37"><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. 2104 2106 </p> 2105 <h1 id="rfc.section.8"><a href="#rfc.section.8">8.</a> <a id="http.date" href="#http.date">Date/Time Formats</a></h1> 2106 <p id="rfc.section.8.p.1">HTTP applications have historically allowed three different formats for date/time stamps. However, the preferred format is 2107 <h1 id="rfc.section.8"><a href="#rfc.section.8">8.</a> <a id="common.protocol.parameters" href="#common.protocol.parameters">Common Protocol Parameters</a></h1> 2108 <h2 id="rfc.section.8.1"><a href="#rfc.section.8.1">8.1</a> <a id="http.date" href="#http.date">Date/Time Formats</a></h2> 2109 <p id="rfc.section.8.1.p.1">HTTP applications have historically allowed three different formats for date/time stamps. However, the preferred format is 2107 2110 a fixed-length subset of that defined by <a href="#RFC1123" id="rfc.xref.RFC1123.1"><cite title="Requirements for Internet Hosts - Application and Support">[RFC1123]</cite></a>: 2108 2111 </p> 2109 2112 <div id="rfc.figure.u.9"></div><pre class="text">Sun, 06 Nov 1994 08:49:37 GMT ; RFC 1123 2110 </pre><p id="rfc.section.8. p.3">The other formats are described here only for compatibility with obsolete implementations.</p>2113 </pre><p id="rfc.section.8.1.p.3">The other formats are described here only for compatibility with obsolete implementations.</p> 2111 2114 <div id="rfc.figure.u.10"></div><pre class="text">Sunday, 06-Nov-94 08:49:37 GMT ; obsolete RFC 850 format 2112 2115 Sun Nov 6 08:49:37 1994 ; ANSI C's asctime() format 2113 </pre><p id="rfc.section.8. p.5">HTTP/1.1 clients and servers that parse a date value <em class="bcp14">MUST</em> accept all three formats (for compatibility with HTTP/1.0), though they <em class="bcp14">MUST</em> only generate the RFC 1123 format for representing HTTP-date values in header fields.2114 </p> 2115 <p id="rfc.section.8. p.6">All HTTP date/time stamps <em class="bcp14">MUST</em> be represented in Greenwich Mean Time (GMT), without exception. For the purposes of HTTP, GMT is exactly equal to UTC (Coordinated2116 </pre><p id="rfc.section.8.1.p.5">HTTP/1.1 clients and servers that parse a date value <em class="bcp14">MUST</em> accept all three formats (for compatibility with HTTP/1.0), though they <em class="bcp14">MUST</em> only generate the RFC 1123 format for representing HTTP-date values in header fields. 2117 </p> 2118 <p id="rfc.section.8.1.p.6">All HTTP date/time stamps <em class="bcp14">MUST</em> be represented in Greenwich Mean Time (GMT), without exception. For the purposes of HTTP, GMT is exactly equal to UTC (Coordinated 2116 2119 Universal Time). This is indicated in the first two formats by the inclusion of "GMT" as the three-letter abbreviation for 2117 2120 time zone, and <em class="bcp14">MUST</em> be assumed when reading the asctime format. HTTP-date is case sensitive and <em class="bcp14">MUST NOT</em> include additional whitespace beyond that specifically included as SP in the grammar. … … 2119 2122 <div id="rfc.figure.u.11"></div><pre class="inline"><span id="rfc.iref.g.6"></span> <a href="#http.date" class="smpl">HTTP-date</a> = <a href="#preferred.date.format" class="smpl">rfc1123-date</a> / <a href="#obsolete.date.formats" class="smpl">obs-date</a> 2120 2123 </pre><div id="preferred.date.format"> 2121 <p id="rfc.section.8. p.8"> Preferred format:</p>2124 <p id="rfc.section.8.1.p.8"> Preferred format:</p> 2122 2125 </div> 2123 2126 <div id="rfc.figure.u.12"></div><pre class="inline"><span id="rfc.iref.g.7"></span><span id="rfc.iref.g.8"></span><span id="rfc.iref.g.9"></span><span id="rfc.iref.g.10"></span><span id="rfc.iref.g.11"></span><span id="rfc.iref.g.12"></span><span id="rfc.iref.g.13"></span><span id="rfc.iref.g.14"></span><span id="rfc.iref.g.15"></span><span id="rfc.iref.g.16"></span><span id="rfc.iref.g.17"></span><span id="rfc.iref.g.18"></span> <a href="#preferred.date.format" class="smpl">rfc1123-date</a> = <a href="#preferred.date.format" class="smpl">day-name</a> "," <a href="#notation" class="smpl">SP</a> date1 <a href="#notation" class="smpl">SP</a> <a href="#preferred.date.format" class="smpl">time-of-day</a> <a href="#notation" class="smpl">SP</a> <a href="#preferred.date.format" class="smpl">GMT</a> … … 2159 2162 <a href="#preferred.date.format" class="smpl">minute</a> = 2<a href="#notation" class="smpl">DIGIT</a> 2160 2163 <a href="#preferred.date.format" class="smpl">second</a> = 2<a href="#notation" class="smpl">DIGIT</a> 2161 </pre><p id="rfc.section.8. p.10">The semantics of <a href="#preferred.date.format" class="smpl">day-name</a>, <a href="#preferred.date.format" class="smpl">day</a>, <a href="#preferred.date.format" class="smpl">month</a>, <a href="#preferred.date.format" class="smpl">year</a>, and <a href="#preferred.date.format" class="smpl">time-of-day</a> are the same as those defined for the RFC 5322 constructs with the corresponding name (<a href="#RFC5322" id="rfc.xref.RFC5322.1"><cite title="Internet Message Format">[RFC5322]</cite></a>, <a href="http://tools.ietf.org/html/rfc5322#section-3.3">Section 3.3</a>).2164 </pre><p id="rfc.section.8.1.p.10">The semantics of <a href="#preferred.date.format" class="smpl">day-name</a>, <a href="#preferred.date.format" class="smpl">day</a>, <a href="#preferred.date.format" class="smpl">month</a>, <a href="#preferred.date.format" class="smpl">year</a>, and <a href="#preferred.date.format" class="smpl">time-of-day</a> are the same as those defined for the RFC 5322 constructs with the corresponding name (<a href="#RFC5322" id="rfc.xref.RFC5322.1"><cite title="Internet Message Format">[RFC5322]</cite></a>, <a href="http://tools.ietf.org/html/rfc5322#section-3.3">Section 3.3</a>). 2162 2165 </p> 2163 2166 <div id="obsolete.date.formats"> 2164 <p id="rfc.section.8. p.11"> Obsolete formats:</p>2167 <p id="rfc.section.8.1.p.11"> Obsolete formats:</p> 2165 2168 </div> 2166 2169 <div id="rfc.figure.u.13"></div><pre class="inline"><span id="rfc.iref.g.19"></span> <a href="#obsolete.date.formats" class="smpl">obs-date</a> = <a href="#obsolete.date.formats" class="smpl">rfc850-date</a> / <a href="#obsolete.date.formats" class="smpl">asctime-date</a> … … 2179 2182 <a href="#obsolete.date.formats" class="smpl">date3</a> = <a href="#preferred.date.format" class="smpl">month</a> <a href="#notation" class="smpl">SP</a> ( 2<a href="#notation" class="smpl">DIGIT</a> / ( <a href="#notation" class="smpl">SP</a> 1<a href="#notation" class="smpl">DIGIT</a> )) 2180 2183 ; month day (e.g., Jun 2) 2181 </pre><div class="note" id="rfc.section.8. p.15">2184 </pre><div class="note" id="rfc.section.8.1.p.15"> 2182 2185 <p> <b>Note:</b> Recipients of date values are encouraged to be robust in accepting date values that might have been sent by non-HTTP applications, 2183 2186 as is sometimes the case when retrieving or posting messages via proxies/gateways to SMTP or NNTP. 2184 2187 </p> 2185 2188 </div> 2186 <div class="note" id="rfc.section.8. p.16">2189 <div class="note" id="rfc.section.8.1.p.16"> 2187 2190 <p> <b>Note:</b> HTTP requirements for the date/time stamp format apply only to their usage within the protocol stream. Clients and servers 2188 2191 are not required to use these formats for user presentation, request logging, etc. 2189 2192 </p> 2190 2193 </div> 2191 <h 1 id="rfc.section.9"><a href="#rfc.section.9">9.</a> <a id="product.tokens" href="#product.tokens">Product Tokens</a></h1>2192 <p id="rfc.section. 9.p.1">Product tokens are used to allow communicating applications to identify themselves by software name and version. Most fields2194 <h2 id="rfc.section.8.2"><a href="#rfc.section.8.2">8.2</a> <a id="product.tokens" href="#product.tokens">Product Tokens</a></h2> 2195 <p id="rfc.section.8.2.p.1">Product tokens are used to allow communicating applications to identify themselves by software name and version. Most fields 2193 2196 using product tokens also allow sub-products which form a significant part of the application to be listed, separated by whitespace. 2194 2197 By convention, the products are listed in order of their significance for identifying the application. … … 2196 2199 <div id="rfc.figure.u.16"></div><pre class="inline"><span id="rfc.iref.g.22"></span><span id="rfc.iref.g.23"></span> <a href="#product.tokens" class="smpl">product</a> = <a href="#core.rules" class="smpl">token</a> ["/" <a href="#product.tokens" class="smpl">product-version</a>] 2197 2200 <a href="#product.tokens" class="smpl">product-version</a> = <a href="#core.rules" class="smpl">token</a> 2198 </pre><p id="rfc.section. 9.p.3">Examples:</p>2201 </pre><p id="rfc.section.8.2.p.3">Examples:</p> 2199 2202 <div id="rfc.figure.u.17"></div><pre class="text"> User-Agent: CERN-LineMode/2.15 libwww/2.17b3 2200 2203 Server: Apache/0.8.4 2201 </pre><p id="rfc.section. 9.p.5">Product tokens <em class="bcp14">SHOULD</em> be short and to the point. They <em class="bcp14">MUST NOT</em> be used for advertising or other non-essential information. Although any token octet <em class="bcp14">MAY</em> appear in a product-version, this token <em class="bcp14">SHOULD</em> only be used for a version identifier (i.e., successive versions of the same product <em class="bcp14">SHOULD</em> only differ in the product-version portion of the product value).2202 </p> 2203 <h1 id="rfc.section. 10"><a href="#rfc.section.10">10.</a> <a id="header.field.definitions" href="#header.field.definitions">Header Field Definitions</a></h1>2204 <p id="rfc.section. 10.p.1">This section defines the syntax and semantics of HTTP/1.1 header fields related to request and response semantics.</p>2204 </pre><p id="rfc.section.8.2.p.5">Product tokens <em class="bcp14">SHOULD</em> be short and to the point. They <em class="bcp14">MUST NOT</em> be used for advertising or other non-essential information. Although any token octet <em class="bcp14">MAY</em> appear in a product-version, this token <em class="bcp14">SHOULD</em> only be used for a version identifier (i.e., successive versions of the same product <em class="bcp14">SHOULD</em> only differ in the product-version portion of the product value). 2205 </p> 2206 <h1 id="rfc.section.9"><a href="#rfc.section.9">9.</a> <a id="header.field.definitions" href="#header.field.definitions">Header Field Definitions</a></h1> 2207 <p id="rfc.section.9.p.1">This section defines the syntax and semantics of HTTP/1.1 header fields related to request and response semantics.</p> 2205 2208 <div id="rfc.iref.a.1"></div> 2206 2209 <div id="rfc.iref.h.2"></div> 2207 <h2 id="rfc.section. 10.1"><a href="#rfc.section.10.1">10.1</a> <a id="header.allow" href="#header.allow">Allow</a></h2>2208 <p id="rfc.section. 10.1.p.1">The "Allow" header field lists the set of methods advertised as supported by the target resource. The purpose of this field2210 <h2 id="rfc.section.9.1"><a href="#rfc.section.9.1">9.1</a> <a id="header.allow" href="#header.allow">Allow</a></h2> 2211 <p id="rfc.section.9.1.p.1">The "Allow" header field lists the set of methods advertised as supported by the target resource. The purpose of this field 2209 2212 is strictly to inform the recipient of valid request methods associated with the resource. 2210 2213 </p> 2211 2214 <div id="rfc.figure.u.18"></div><pre class="inline"><span id="rfc.iref.g.24"></span> <a href="#header.allow" class="smpl">Allow</a> = #<a href="#method" class="smpl">method</a> 2212 </pre><p id="rfc.section. 10.1.p.3">Example of use:</p>2215 </pre><p id="rfc.section.9.1.p.3">Example of use:</p> 2213 2216 <div id="rfc.figure.u.19"></div><pre class="text"> Allow: GET, HEAD, PUT 2214 </pre><p id="rfc.section. 10.1.p.5">The actual set of allowed methods is defined by the origin server at the time of each request.</p>2215 <p id="rfc.section. 10.1.p.6">A proxy <em class="bcp14">MUST NOT</em> modify the Allow header field — it does not need to understand all the methods specified in order to handle them according2217 </pre><p id="rfc.section.9.1.p.5">The actual set of allowed methods is defined by the origin server at the time of each request.</p> 2218 <p id="rfc.section.9.1.p.6">A proxy <em class="bcp14">MUST NOT</em> modify the Allow header field — it does not need to understand all the methods specified in order to handle them according 2216 2219 to the generic message handling rules. 2217 2220 </p> 2218 2221 <div id="rfc.iref.d.2"></div> 2219 2222 <div id="rfc.iref.h.3"></div> 2220 <h2 id="rfc.section. 10.2"><a href="#rfc.section.10.2">10.2</a> <a id="header.date" href="#header.date">Date</a></h2>2221 <p id="rfc.section. 10.2.p.1">The "Date" header field represents the date and time at which the message was originated, having the same semantics as the2222 Origination Date Field (orig-date) defined in <a href="http://tools.ietf.org/html/rfc5322#section-3.6.1">Section 3.6.1</a> of <a href="#RFC5322" id="rfc.xref.RFC5322.2"><cite title="Internet Message Format">[RFC5322]</cite></a>. The field value is an HTTP-date, as defined in <a href="#http.date" title="Date/Time Formats">Section 8 </a>; it <em class="bcp14">MUST</em> be sent in rfc1123-date format.2223 <h2 id="rfc.section.9.2"><a href="#rfc.section.9.2">9.2</a> <a id="header.date" href="#header.date">Date</a></h2> 2224 <p id="rfc.section.9.2.p.1">The "Date" header field represents the date and time at which the message was originated, having the same semantics as the 2225 Origination Date Field (orig-date) defined in <a href="http://tools.ietf.org/html/rfc5322#section-3.6.1">Section 3.6.1</a> of <a href="#RFC5322" id="rfc.xref.RFC5322.2"><cite title="Internet Message Format">[RFC5322]</cite></a>. The field value is an HTTP-date, as defined in <a href="#http.date" title="Date/Time Formats">Section 8.1</a>; it <em class="bcp14">MUST</em> be sent in rfc1123-date format. 2223 2226 </p> 2224 2227 <div id="rfc.figure.u.20"></div><pre class="inline"><span id="rfc.iref.g.25"></span> <a href="#header.date" class="smpl">Date</a> = <a href="#http.date" class="smpl">HTTP-date</a> 2225 </pre><p id="rfc.section. 10.2.p.3">An example is</p>2228 </pre><p id="rfc.section.9.2.p.3">An example is</p> 2226 2229 <div id="rfc.figure.u.21"></div><pre class="text"> Date: Tue, 15 Nov 1994 08:12:31 GMT 2227 </pre><p id="rfc.section. 10.2.p.5">Origin servers <em class="bcp14">MUST</em> include a Date header field in all responses, except in these cases:2230 </pre><p id="rfc.section.9.2.p.5">Origin servers <em class="bcp14">MUST</em> include a Date header field in all responses, except in these cases: 2228 2231 </p> 2229 2232 <ol> … … 2236 2239 </li> 2237 2240 </ol> 2238 <p id="rfc.section. 10.2.p.6">A received message that does not have a Date header field <em class="bcp14">MUST</em> be assigned one by the recipient if the message will be cached by that recipient.2239 </p> 2240 <p id="rfc.section. 10.2.p.7">Clients can use the Date header field as well; in order to keep request messages small, they are advised not to include it2241 <p id="rfc.section.9.2.p.6">A received message that does not have a Date header field <em class="bcp14">MUST</em> be assigned one by the recipient if the message will be cached by that recipient. 2242 </p> 2243 <p id="rfc.section.9.2.p.7">Clients can use the Date header field as well; in order to keep request messages small, they are advised not to include it 2241 2244 when it doesn't convey any useful information (as is usually the case for requests that do not contain a payload). 2242 2245 </p> 2243 <p id="rfc.section. 10.2.p.8">The HTTP-date sent in a Date header field <em class="bcp14">SHOULD NOT</em> represent a date and time subsequent to the generation of the message. It <em class="bcp14">SHOULD</em> represent the best available approximation of the date and time of message generation, unless the implementation has no means2246 <p id="rfc.section.9.2.p.8">The HTTP-date sent in a Date header field <em class="bcp14">SHOULD NOT</em> represent a date and time subsequent to the generation of the message. It <em class="bcp14">SHOULD</em> represent the best available approximation of the date and time of message generation, unless the implementation has no means 2244 2247 of generating a reasonably accurate date and time. In theory, the date ought to represent the moment just before the payload 2245 2248 is generated. In practice, the date can be generated at any time during the message origination without affecting its semantic … … 2248 2251 <div id="rfc.iref.e.1"></div> 2249 2252 <div id="rfc.iref.h.4"></div> 2250 <h2 id="rfc.section. 10.3"><a href="#rfc.section.10.3">10.3</a> <a id="header.expect" href="#header.expect">Expect</a></h2>2251 <p id="rfc.section. 10.3.p.1">The "Expect" header field is used to indicate that particular server behaviors are required by the client.</p>2253 <h2 id="rfc.section.9.3"><a href="#rfc.section.9.3">9.3</a> <a id="header.expect" href="#header.expect">Expect</a></h2> 2254 <p id="rfc.section.9.3.p.1">The "Expect" header field is used to indicate that particular server behaviors are required by the client.</p> 2252 2255 <div id="rfc.figure.u.22"></div><pre class="inline"><span id="rfc.iref.g.26"></span><span id="rfc.iref.g.27"></span><span id="rfc.iref.g.28"></span><span id="rfc.iref.g.29"></span><span id="rfc.iref.g.30"></span> <a href="#header.expect" class="smpl">Expect</a> = 1#<a href="#header.expect" class="smpl">expectation</a> 2253 2256 … … 2258 2261 <a href="#header.expect" class="smpl">expect-name</a> = <a href="#core.rules" class="smpl">token</a> 2259 2262 <a href="#header.expect" class="smpl">expect-value</a> = <a href="#core.rules" class="smpl">token</a> / <a href="#core.rules" class="smpl">quoted-string</a> 2260 </pre><p id="rfc.section. 10.3.p.3">If all received Expect header field(s) are syntactically valid but contain an expectation that the recipient does not understand2263 </pre><p id="rfc.section.9.3.p.3">If all received Expect header field(s) are syntactically valid but contain an expectation that the recipient does not understand 2261 2264 or cannot comply with, the recipient <em class="bcp14">MUST</em> respond with a 417 (Expectation Failed) status code. A recipient of a syntactically invalid Expectation header field <em class="bcp14">MUST</em> respond with a 4xx status code other than 417. 2262 2265 </p> 2263 <p id="rfc.section. 10.3.p.4">The only expectation defined by this specification is:</p>2264 <p id="rfc.section. 10.3.p.5"><span id="rfc.iref.89"></span><span id="rfc.iref.e.2"></span> 100-continue2266 <p id="rfc.section.9.3.p.4">The only expectation defined by this specification is:</p> 2267 <p id="rfc.section.9.3.p.5"><span id="rfc.iref.89"></span><span id="rfc.iref.e.2"></span> 100-continue 2265 2268 </p> 2266 2269 <ul class="empty"> … … 2268 2271 </li> 2269 2272 </ul> 2270 <p id="rfc.section. 10.3.p.6">Comparison is case-insensitive for names (expect-name), and case-sensitive for values (expect-value).</p>2271 <p id="rfc.section. 10.3.p.7">The Expect mechanism is hop-by-hop: the above requirements apply to any server, including proxies. However, the Expect header2273 <p id="rfc.section.9.3.p.6">Comparison is case-insensitive for names (expect-name), and case-sensitive for values (expect-value).</p> 2274 <p id="rfc.section.9.3.p.7">The Expect mechanism is hop-by-hop: the above requirements apply to any server, including proxies. However, the Expect header 2272 2275 field itself is end-to-end; it <em class="bcp14">MUST</em> be forwarded if the request is forwarded. 2273 2276 </p> 2274 <p id="rfc.section. 10.3.p.8">Many older HTTP/1.0 and HTTP/1.1 applications do not understand the Expect header field.</p>2277 <p id="rfc.section.9.3.p.8">Many older HTTP/1.0 and HTTP/1.1 applications do not understand the Expect header field.</p> 2275 2278 <div id="rfc.iref.f.1"></div> 2276 2279 <div id="rfc.iref.h.5"></div> 2277 <h2 id="rfc.section. 10.4"><a href="#rfc.section.10.4">10.4</a> <a id="header.from" href="#header.from">From</a></h2>2278 <p id="rfc.section. 10.4.p.1">The "From" header field, if given, <em class="bcp14">SHOULD</em> contain an Internet e-mail address for the human user who controls the requesting user agent. The address <em class="bcp14">SHOULD</em> be machine-usable, as defined by "mailbox" in <a href="http://tools.ietf.org/html/rfc5322#section-3.4">Section 3.4</a> of <a href="#RFC5322" id="rfc.xref.RFC5322.3"><cite title="Internet Message Format">[RFC5322]</cite></a>:2280 <h2 id="rfc.section.9.4"><a href="#rfc.section.9.4">9.4</a> <a id="header.from" href="#header.from">From</a></h2> 2281 <p id="rfc.section.9.4.p.1">The "From" header field, if given, <em class="bcp14">SHOULD</em> contain an Internet e-mail address for the human user who controls the requesting user agent. The address <em class="bcp14">SHOULD</em> be machine-usable, as defined by "mailbox" in <a href="http://tools.ietf.org/html/rfc5322#section-3.4">Section 3.4</a> of <a href="#RFC5322" id="rfc.xref.RFC5322.3"><cite title="Internet Message Format">[RFC5322]</cite></a>: 2279 2282 </p> 2280 2283 <div id="rfc.figure.u.23"></div><pre class="inline"><span id="rfc.iref.g.31"></span> <a href="#header.from" class="smpl">From</a> = <a href="#header.from" class="smpl">mailbox</a> 2281 2284 2282 2285 <a href="#header.from" class="smpl">mailbox</a> = <mailbox, defined in <a href="#RFC5322" id="rfc.xref.RFC5322.4"><cite title="Internet Message Format">[RFC5322]</cite></a>, <a href="http://tools.ietf.org/html/rfc5322#section-3.4">Section 3.4</a>> 2283 </pre><p id="rfc.section. 10.4.p.3">An example is:</p>2286 </pre><p id="rfc.section.9.4.p.3">An example is:</p> 2284 2287 <div id="rfc.figure.u.24"></div><pre class="text"> From: webmaster@example.org 2285 </pre><p id="rfc.section. 10.4.p.5">This header field <em class="bcp14">MAY</em> be used for logging purposes and as a means for identifying the source of invalid or unwanted requests. It <em class="bcp14">SHOULD NOT</em> be used as an insecure form of access protection. The interpretation of this field is that the request is being performed2288 </pre><p id="rfc.section.9.4.p.5">This header field <em class="bcp14">MAY</em> be used for logging purposes and as a means for identifying the source of invalid or unwanted requests. It <em class="bcp14">SHOULD NOT</em> be used as an insecure form of access protection. The interpretation of this field is that the request is being performed 2286 2289 on behalf of the person given, who accepts responsibility for the method performed. In particular, robot agents <em class="bcp14">SHOULD</em> include this header field so that the person responsible for running the robot can be contacted if problems occur on the receiving 2287 2290 end. 2288 2291 </p> 2289 <p id="rfc.section. 10.4.p.6">The Internet e-mail address in this field <em class="bcp14">MAY</em> be separate from the Internet host which issued the request. For example, when a request is passed through a proxy the original2292 <p id="rfc.section.9.4.p.6">The Internet e-mail address in this field <em class="bcp14">MAY</em> be separate from the Internet host which issued the request. For example, when a request is passed through a proxy the original 2290 2293 issuer's address <em class="bcp14">SHOULD</em> be used. 2291 2294 </p> 2292 <p id="rfc.section. 10.4.p.7">The client <em class="bcp14">SHOULD NOT</em> send the From header field without the user's approval, as it might conflict with the user's privacy interests or their site's2295 <p id="rfc.section.9.4.p.7">The client <em class="bcp14">SHOULD NOT</em> send the From header field without the user's approval, as it might conflict with the user's privacy interests or their site's 2293 2296 security policy. It is strongly recommended that the user be able to disable, enable, and modify the value of this field at 2294 2297 any time prior to a request. … … 2296 2299 <div id="rfc.iref.l.1"></div> 2297 2300 <div id="rfc.iref.h.6"></div> 2298 <h2 id="rfc.section. 10.5"><a href="#rfc.section.10.5">10.5</a> <a id="header.location" href="#header.location">Location</a></h2>2299 <p id="rfc.section. 10.5.p.1">The "Location" header field <em class="bcp14">MAY</em> be sent in responses to refer to a specific resource in accordance with the semantics of the status code.2301 <h2 id="rfc.section.9.5"><a href="#rfc.section.9.5">9.5</a> <a id="header.location" href="#header.location">Location</a></h2> 2302 <p id="rfc.section.9.5.p.1">The "Location" header field <em class="bcp14">MAY</em> be sent in responses to refer to a specific resource in accordance with the semantics of the status code. 2300 2303 </p> 2301 2304 <div id="rfc.figure.u.25"></div><pre class="inline"><span id="rfc.iref.g.32"></span> <a href="#header.location" class="smpl">Location</a> = <a href="#abnf.dependencies" class="smpl">URI-reference</a> 2302 </pre><p id="rfc.section. 10.5.p.3">For 201 (Created) responses, the Location is the URI of the new resource which was created by the request. For 3xx responses,2305 </pre><p id="rfc.section.9.5.p.3">For 201 (Created) responses, the Location is the URI of the new resource which was created by the request. For 3xx responses, 2303 2306 the location <em class="bcp14">SHOULD</em> indicate the server's preferred URI for automatic redirection to the resource. 2304 2307 </p> 2305 <p id="rfc.section. 10.5.p.4">The field value consists of a single URI-reference. When it has the form of a relative reference (<a href="#RFC3986" id="rfc.xref.RFC3986.1"><cite title="Uniform Resource Identifier (URI): Generic Syntax">[RFC3986]</cite></a>, <a href="http://tools.ietf.org/html/rfc3986#section-4.2">Section 4.2</a>), the final value is computed by resolving it against the effective request URI (<a href="#RFC3986" id="rfc.xref.RFC3986.2"><cite title="Uniform Resource Identifier (URI): Generic Syntax">[RFC3986]</cite></a>, <a href="http://tools.ietf.org/html/rfc3986#section-5">Section 5</a>). If the original URI, as navigated to by the user agent, did contain a fragment identifier, and the final value does not,2308 <p id="rfc.section.9.5.p.4">The field value consists of a single URI-reference. When it has the form of a relative reference (<a href="#RFC3986" id="rfc.xref.RFC3986.1"><cite title="Uniform Resource Identifier (URI): Generic Syntax">[RFC3986]</cite></a>, <a href="http://tools.ietf.org/html/rfc3986#section-4.2">Section 4.2</a>), the final value is computed by resolving it against the effective request URI (<a href="#RFC3986" id="rfc.xref.RFC3986.2"><cite title="Uniform Resource Identifier (URI): Generic Syntax">[RFC3986]</cite></a>, <a href="http://tools.ietf.org/html/rfc3986#section-5">Section 5</a>). If the original URI, as navigated to by the user agent, did contain a fragment identifier, and the final value does not, 2306 2309 then the original URI's fragment identifier is added to the final value. 2307 2310 </p> … … 2312 2315 <p>An original URI "http://www.example.org/index.html#larry", combined with a field value given as:</p> <pre class="text"> Location: http://www.example.net/index.html 2313 2316 </pre> <p>would result in a final value of "http://www.example.net/index.html#larry", preserving the original fragment identifier.</p> 2314 <div class="note" id="rfc.section. 10.5.p.7">2317 <div class="note" id="rfc.section.9.5.p.7"> 2315 2318 <p> <b>Note:</b> Some recipients attempt to recover from Location fields that are not valid URI references. This specification does not mandate 2316 2319 or define such processing, but does allow it (see <a href="#intro.conformance.and.error.handling" title="Conformance and Error Handling">Section 1.1</a>). 2317 2320 </p> 2318 2321 </div> 2319 <p id="rfc.section. 10.5.p.8">There are circumstances in which a fragment identifier in a Location URI would not be appropriate. For instance, when it appears2322 <p id="rfc.section.9.5.p.8">There are circumstances in which a fragment identifier in a Location URI would not be appropriate. For instance, when it appears 2320 2323 in a 201 Created response, where the Location header field specifies the URI for the entire created resource. 2321 2324 </p> 2322 <div class="note" id="rfc.section. 10.5.p.9">2325 <div class="note" id="rfc.section.9.5.p.9"> 2323 2326 <p> <b>Note:</b> The Content-Location header field (<a href="p3-payload.html#header.content-location" title="Content-Location">Section 6.7</a> of <a href="#Part3" id="rfc.xref.Part3.13"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>) differs from Location in that the Content-Location identifies the most specific resource corresponding to the enclosed representation. 2324 2327 It is therefore possible for a response to contain header fields for both Location and Content-Location. … … 2327 2330 <div id="rfc.iref.m.9"></div> 2328 2331 <div id="rfc.iref.h.7"></div> 2329 <h2 id="rfc.section. 10.6"><a href="#rfc.section.10.6">10.6</a> <a id="header.max-forwards" href="#header.max-forwards">Max-Forwards</a></h2>2330 <p id="rfc.section. 10.6.p.1">The "Max-Forwards" header field provides a mechanism with the TRACE (<a href="#TRACE" id="rfc.xref.TRACE.2" title="TRACE">Section 6.8</a>) and OPTIONS (<a href="#OPTIONS" id="rfc.xref.OPTIONS.2" title="OPTIONS">Section 6.2</a>) methods to limit the number of times that the request is forwarded by proxies. This can be useful when the client is attempting2332 <h2 id="rfc.section.9.6"><a href="#rfc.section.9.6">9.6</a> <a id="header.max-forwards" href="#header.max-forwards">Max-Forwards</a></h2> 2333 <p id="rfc.section.9.6.p.1">The "Max-Forwards" header field provides a mechanism with the TRACE (<a href="#TRACE" id="rfc.xref.TRACE.2" title="TRACE">Section 6.8</a>) and OPTIONS (<a href="#OPTIONS" id="rfc.xref.OPTIONS.2" title="OPTIONS">Section 6.2</a>) methods to limit the number of times that the request is forwarded by proxies. This can be useful when the client is attempting 2331 2334 to trace a request which appears to be failing or looping mid-chain. 2332 2335 </p> 2333 2336 <div id="rfc.figure.u.28"></div><pre class="inline"><span id="rfc.iref.g.33"></span> <a href="#header.max-forwards" class="smpl">Max-Forwards</a> = 1*<a href="#notation" class="smpl">DIGIT</a> 2334 </pre><p id="rfc.section. 10.6.p.3">The Max-Forwards value is a decimal integer indicating the remaining number of times this request message can be forwarded.</p>2335 <p id="rfc.section. 10.6.p.4">Each recipient of a TRACE or OPTIONS request containing a Max-Forwards header field <em class="bcp14">MUST</em> check and update its value prior to forwarding the request. If the received value is zero (0), the recipient <em class="bcp14">MUST NOT</em> forward the request; instead, it <em class="bcp14">MUST</em> respond as the final recipient. If the received Max-Forwards value is greater than zero, then the forwarded message <em class="bcp14">MUST</em> contain an updated Max-Forwards field with a value decremented by one (1).2336 </p> 2337 <p id="rfc.section. 10.6.p.5">The Max-Forwards header field <em class="bcp14">MAY</em> be ignored for all other request methods.2337 </pre><p id="rfc.section.9.6.p.3">The Max-Forwards value is a decimal integer indicating the remaining number of times this request message can be forwarded.</p> 2338 <p id="rfc.section.9.6.p.4">Each recipient of a TRACE or OPTIONS request containing a Max-Forwards header field <em class="bcp14">MUST</em> check and update its value prior to forwarding the request. If the received value is zero (0), the recipient <em class="bcp14">MUST NOT</em> forward the request; instead, it <em class="bcp14">MUST</em> respond as the final recipient. If the received Max-Forwards value is greater than zero, then the forwarded message <em class="bcp14">MUST</em> contain an updated Max-Forwards field with a value decremented by one (1). 2339 </p> 2340 <p id="rfc.section.9.6.p.5">The Max-Forwards header field <em class="bcp14">MAY</em> be ignored for all other request methods. 2338 2341 </p> 2339 2342 <div id="rfc.iref.r.1"></div> 2340 2343 <div id="rfc.iref.h.8"></div> 2341 <h2 id="rfc.section. 10.7"><a href="#rfc.section.10.7">10.7</a> <a id="header.referer" href="#header.referer">Referer</a></h2>2342 <p id="rfc.section. 10.7.p.1">The "Referer" [sic] header field allows the client to specify the URI of the resource from which the target URI was obtained2344 <h2 id="rfc.section.9.7"><a href="#rfc.section.9.7">9.7</a> <a id="header.referer" href="#header.referer">Referer</a></h2> 2345 <p id="rfc.section.9.7.p.1">The "Referer" [sic] header field allows the client to specify the URI of the resource from which the target URI was obtained 2343 2346 (the "referrer", although the header field is misspelled.). 2344 2347 </p> 2345 <p id="rfc.section. 10.7.p.2">The Referer header field allows servers to generate lists of back-links to resources for interest, logging, optimized caching,2348 <p id="rfc.section.9.7.p.2">The Referer header field allows servers to generate lists of back-links to resources for interest, logging, optimized caching, 2346 2349 etc. It also allows obsolete or mistyped links to be traced for maintenance. Some servers use Referer as a means of controlling 2347 2350 where they allow links from (so-called "deep linking"), but legitimate requests do not always contain a Referer header field. 2348 2351 </p> 2349 <p id="rfc.section. 10.7.p.3">If the target URI was obtained from a source that does not have its own URI (e.g., input from the user keyboard), the Referer2352 <p id="rfc.section.9.7.p.3">If the target URI was obtained from a source that does not have its own URI (e.g., input from the user keyboard), the Referer 2350 2353 field <em class="bcp14">MUST</em> either be sent with the value "about:blank", or not be sent at all. Note that this requirement does not apply to sources with 2351 2354 non-HTTP URIs (e.g., FTP). 2352 2355 </p> 2353 2356 <div id="rfc.figure.u.29"></div><pre class="inline"><span id="rfc.iref.g.34"></span> <a href="#header.referer" class="smpl">Referer</a> = <a href="#abnf.dependencies" class="smpl">absolute-URI</a> / <a href="#abnf.dependencies" class="smpl">partial-URI</a> 2354 </pre><p id="rfc.section. 10.7.p.5">Example:</p>2357 </pre><p id="rfc.section.9.7.p.5">Example:</p> 2355 2358 <div id="rfc.figure.u.30"></div><pre class="text"> Referer: http://www.example.org/hypertext/Overview.html 2356 </pre><p id="rfc.section. 10.7.p.7">If the field value is a relative URI, it <em class="bcp14">SHOULD</em> be interpreted relative to the effective request URI. The URI <em class="bcp14">MUST NOT</em> include a fragment. See <a href="#encoding.sensitive.information.in.uris" title="Encoding Sensitive Information in URIs">Section 12.2</a> for security considerations.2359 </pre><p id="rfc.section.9.7.p.7">If the field value is a relative URI, it <em class="bcp14">SHOULD</em> be interpreted relative to the effective request URI. The URI <em class="bcp14">MUST NOT</em> include a fragment. See <a href="#encoding.sensitive.information.in.uris" title="Encoding Sensitive Information in URIs">Section 11.2</a> for security considerations. 2357 2360 </p> 2358 2361 <div id="rfc.iref.r.2"></div> 2359 2362 <div id="rfc.iref.h.9"></div> 2360 <h2 id="rfc.section. 10.8"><a href="#rfc.section.10.8">10.8</a> <a id="header.retry-after" href="#header.retry-after">Retry-After</a></h2>2361 <p id="rfc.section. 10.8.p.1">The header "Retry-After" field can be used with a 503 (Service Unavailable) response to indicate how long the service is expected2363 <h2 id="rfc.section.9.8"><a href="#rfc.section.9.8">9.8</a> <a id="header.retry-after" href="#header.retry-after">Retry-After</a></h2> 2364 <p id="rfc.section.9.8.p.1">The header "Retry-After" field can be used with a 503 (Service Unavailable) response to indicate how long the service is expected 2362 2365 to be unavailable to the requesting client. This field <em class="bcp14">MAY</em> also be used with any 3xx (Redirection) response to indicate the minimum time the user-agent is asked to wait before issuing 2363 2366 the redirected request. 2364 2367 </p> 2365 <p id="rfc.section. 10.8.p.2">The value of this field can be either an HTTP-date or an integer number of seconds (in decimal) after the time of the response.</p>2368 <p id="rfc.section.9.8.p.2">The value of this field can be either an HTTP-date or an integer number of seconds (in decimal) after the time of the response.</p> 2366 2369 <div id="rfc.figure.u.31"></div><pre class="inline"><span id="rfc.iref.g.35"></span> <a href="#header.retry-after" class="smpl">Retry-After</a> = <a href="#http.date" class="smpl">HTTP-date</a> / <a href="#rule.delta-seconds" class="smpl">delta-seconds</a> 2367 2370 </pre><div id="rule.delta-seconds"> 2368 <p id="rfc.section. 10.8.p.4"> Time spans are non-negative decimal integers, representing time in seconds.</p>2371 <p id="rfc.section.9.8.p.4"> Time spans are non-negative decimal integers, representing time in seconds.</p> 2369 2372 </div> 2370 2373 <div id="rfc.figure.u.32"></div><pre class="inline"><span id="rfc.iref.g.36"></span> <a href="#rule.delta-seconds" class="smpl">delta-seconds</a> = 1*<a href="#notation" class="smpl">DIGIT</a> 2371 </pre><p id="rfc.section. 10.8.p.6">Two examples of its use are</p>2374 </pre><p id="rfc.section.9.8.p.6">Two examples of its use are</p> 2372 2375 <div id="rfc.figure.u.33"></div><pre class="text"> Retry-After: Fri, 31 Dec 1999 23:59:59 GMT 2373 2376 Retry-After: 120 2374 </pre><p id="rfc.section. 10.8.p.8">In the latter example, the delay is 2 minutes.</p>2377 </pre><p id="rfc.section.9.8.p.8">In the latter example, the delay is 2 minutes.</p> 2375 2378 <div id="rfc.iref.s.38"></div> 2376 2379 <div id="rfc.iref.h.10"></div> 2377 <h2 id="rfc.section. 10.9"><a href="#rfc.section.10.9">10.9</a> <a id="header.server" href="#header.server">Server</a></h2>2378 <p id="rfc.section. 10.9.p.1">The "Server" header field contains information about the software used by the origin server to handle the request.</p>2379 <p id="rfc.section. 10.9.p.2">The field can contain multiple product tokens (<a href="#product.tokens" title="Product Tokens">Section 9</a>) and comments (<a href="p1-messaging.html#header.fields" title="Header Fields">Section 3.2</a> of <a href="#Part1" id="rfc.xref.Part1.39"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) identifying the server and any significant subproducts. The product tokens are listed in order of their significance for2380 <h2 id="rfc.section.9.9"><a href="#rfc.section.9.9">9.9</a> <a id="header.server" href="#header.server">Server</a></h2> 2381 <p id="rfc.section.9.9.p.1">The "Server" header field contains information about the software used by the origin server to handle the request.</p> 2382 <p id="rfc.section.9.9.p.2">The field can contain multiple product tokens (<a href="#product.tokens" title="Product Tokens">Section 8.2</a>) and comments (<a href="p1-messaging.html#header.fields" title="Header Fields">Section 3.2</a> of <a href="#Part1" id="rfc.xref.Part1.39"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) identifying the server and any significant subproducts. The product tokens are listed in order of their significance for 2380 2383 identifying the application. 2381 2384 </p> 2382 2385 <div id="rfc.figure.u.34"></div><pre class="inline"><span id="rfc.iref.g.37"></span> <a href="#header.server" class="smpl">Server</a> = <a href="#product.tokens" class="smpl">product</a> *( <a href="#core.rules" class="smpl">RWS</a> ( <a href="#product.tokens" class="smpl">product</a> / <a href="#abnf.dependencies" class="smpl">comment</a> ) ) 2383 </pre><p id="rfc.section. 10.9.p.4">Example:</p>2386 </pre><p id="rfc.section.9.9.p.4">Example:</p> 2384 2387 <div id="rfc.figure.u.35"></div><pre class="text"> Server: CERN/3.0 libwww/2.17 2385 </pre><p id="rfc.section. 10.9.p.6">If the response is being forwarded through a proxy, the proxy application <em class="bcp14">MUST NOT</em> modify the Server header field. Instead, it <em class="bcp14">MUST</em> include a Via field (as described in <a href="p1-messaging.html#header.via" title="Via">Section 6.2</a> of <a href="#Part1" id="rfc.xref.Part1.40"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>).2386 </p> 2387 <div class="note" id="rfc.section. 10.9.p.7">2388 </pre><p id="rfc.section.9.9.p.6">If the response is being forwarded through a proxy, the proxy application <em class="bcp14">MUST NOT</em> modify the Server header field. Instead, it <em class="bcp14">MUST</em> include a Via field (as described in <a href="p1-messaging.html#header.via" title="Via">Section 6.2</a> of <a href="#Part1" id="rfc.xref.Part1.40"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>). 2389 </p> 2390 <div class="note" id="rfc.section.9.9.p.7"> 2388 2391 <p> <b>Note:</b> Revealing the specific software version of the server might allow the server machine to become more vulnerable to attacks 2389 2392 against software that is known to contain security holes. Server implementors are encouraged to make this field a configurable … … 2393 2396 <div id="rfc.iref.u.1"></div> 2394 2397 <div id="rfc.iref.h.11"></div> 2395 <h2 id="rfc.section. 10.10"><a href="#rfc.section.10.10">10.10</a> <a id="header.user-agent" href="#header.user-agent">User-Agent</a></h2>2396 <p id="rfc.section. 10.10.p.1">The "User-Agent" header field contains information about the user agent originating the request. User agents <em class="bcp14">SHOULD</em> include this field with requests.2397 </p> 2398 <p id="rfc.section. 10.10.p.2">Typically, it is used for statistical purposes, the tracing of protocol violations, and tailoring responses to avoid particular2398 <h2 id="rfc.section.9.10"><a href="#rfc.section.9.10">9.10</a> <a id="header.user-agent" href="#header.user-agent">User-Agent</a></h2> 2399 <p id="rfc.section.9.10.p.1">The "User-Agent" header field contains information about the user agent originating the request. User agents <em class="bcp14">SHOULD</em> include this field with requests. 2400 </p> 2401 <p id="rfc.section.9.10.p.2">Typically, it is used for statistical purposes, the tracing of protocol violations, and tailoring responses to avoid particular 2399 2402 user agent limitations. 2400 2403 </p> 2401 <p id="rfc.section. 10.10.p.3">The field can contain multiple product tokens (<a href="#product.tokens" title="Product Tokens">Section 9</a>) and comments (<a href="p1-messaging.html#header.fields" title="Header Fields">Section 3.2</a> of <a href="#Part1" id="rfc.xref.Part1.41"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) identifying the agent and its significant subproducts. By convention, the product tokens are listed in order of their significance2404 <p id="rfc.section.9.10.p.3">The field can contain multiple product tokens (<a href="#product.tokens" title="Product Tokens">Section 8.2</a>) and comments (<a href="p1-messaging.html#header.fields" title="Header Fields">Section 3.2</a> of <a href="#Part1" id="rfc.xref.Part1.41"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) identifying the agent and its significant subproducts. By convention, the product tokens are listed in order of their significance 2402 2405 for identifying the application. 2403 2406 </p> 2404 <p id="rfc.section. 10.10.p.4">Because this field is usually sent on every request a user agent makes, implementations are encouraged not to include needlessly2407 <p id="rfc.section.9.10.p.4">Because this field is usually sent on every request a user agent makes, implementations are encouraged not to include needlessly 2405 2408 fine-grained detail, and to limit (or even prohibit) the addition of subproducts by third parties. Overly long and detailed 2406 2409 User-Agent field values make requests larger and can also be used to identify ("fingerprint") the user against their wishes. 2407 2410 </p> 2408 <p id="rfc.section. 10.10.p.5">Likewise, implementations are encouraged not to use the product tokens of other implementations in order to declare compatibility2411 <p id="rfc.section.9.10.p.5">Likewise, implementations are encouraged not to use the product tokens of other implementations in order to declare compatibility 2409 2412 with them, as this circumvents the purpose of the field. Finally, they are encouraged not to use comments to identify products; 2410 2413 doing so makes the field value more difficult to parse. 2411 2414 </p> 2412 2415 <div id="rfc.figure.u.36"></div><pre class="inline"><span id="rfc.iref.g.38"></span> <a href="#header.user-agent" class="smpl">User-Agent</a> = <a href="#product.tokens" class="smpl">product</a> *( <a href="#core.rules" class="smpl">RWS</a> ( <a href="#product.tokens" class="smpl">product</a> / <a href="#abnf.dependencies" class="smpl">comment</a> ) ) 2413 </pre><p id="rfc.section. 10.10.p.7">Example:</p>2416 </pre><p id="rfc.section.9.10.p.7">Example:</p> 2414 2417 <div id="rfc.figure.u.37"></div><pre class="text"> User-Agent: CERN-LineMode/2.15 libwww/2.17b3 2415 </pre><h1 id="rfc.section.1 1"><a href="#rfc.section.11">11.</a> <a id="IANA.considerations" href="#IANA.considerations">IANA Considerations</a></h1>2416 <h2 id="rfc.section.1 1.1"><a href="#rfc.section.11.1">11.1</a> <a id="method.registration" href="#method.registration">Method Registry</a></h2>2417 <p id="rfc.section.1 1.1.p.1">The registration procedure for HTTP request methods is defined by <a href="#method.registry" title="Method Registry">Section 2.2</a> of this document.2418 </p> 2419 <p id="rfc.section.1 1.1.p.2">The HTTP Method Registry shall be created at <<a href="http://www.iana.org/assignments/http-methods">http://www.iana.org/assignments/http-methods</a>> and be populated with the registrations below:2418 </pre><h1 id="rfc.section.10"><a href="#rfc.section.10">10.</a> <a id="IANA.considerations" href="#IANA.considerations">IANA Considerations</a></h1> 2419 <h2 id="rfc.section.10.1"><a href="#rfc.section.10.1">10.1</a> <a id="method.registration" href="#method.registration">Method Registry</a></h2> 2420 <p id="rfc.section.10.1.p.1">The registration procedure for HTTP request methods is defined by <a href="#method.registry" title="Method Registry">Section 2.2</a> of this document. 2421 </p> 2422 <p id="rfc.section.10.1.p.2">The HTTP Method Registry shall be created at <<a href="http://www.iana.org/assignments/http-methods">http://www.iana.org/assignments/http-methods</a>> and be populated with the registrations below: 2420 2423 </p> 2421 2424 <div id="rfc.table.1"> … … 2481 2484 </table> 2482 2485 </div> 2483 <h2 id="rfc.section.1 1.2"><a href="#rfc.section.11.2">11.2</a> <a id="status.code.registration" href="#status.code.registration">Status Code Registry</a></h2>2484 <p id="rfc.section.1 1.2.p.1">The registration procedure for HTTP Status Codes — previously defined in <a href="http://tools.ietf.org/html/rfc2817#section-7.1">Section 7.1</a> of <a href="#RFC2817" id="rfc.xref.RFC2817.1"><cite title="Upgrading to TLS Within HTTP/1.1">[RFC2817]</cite></a> — is now defined by <a href="#status.code.registry" title="Status Code Registry">Section 4.2</a> of this document.2485 </p> 2486 <p id="rfc.section.1 1.2.p.2">The HTTP Status Code Registry located at <<a href="http://www.iana.org/assignments/http-status-codes">http://www.iana.org/assignments/http-status-codes</a>> shall be updated with the registrations below:2486 <h2 id="rfc.section.10.2"><a href="#rfc.section.10.2">10.2</a> <a id="status.code.registration" href="#status.code.registration">Status Code Registry</a></h2> 2487 <p id="rfc.section.10.2.p.1">The registration procedure for HTTP Status Codes — previously defined in <a href="http://tools.ietf.org/html/rfc2817#section-7.1">Section 7.1</a> of <a href="#RFC2817" id="rfc.xref.RFC2817.1"><cite title="Upgrading to TLS Within HTTP/1.1">[RFC2817]</cite></a> — is now defined by <a href="#status.code.registry" title="Status Code Registry">Section 4.2</a> of this document. 2488 </p> 2489 <p id="rfc.section.10.2.p.2">The HTTP Status Code Registry located at <<a href="http://www.iana.org/assignments/http-status-codes">http://www.iana.org/assignments/http-status-codes</a>> shall be updated with the registrations below: 2487 2490 </p> 2488 2491 <div id="rfc.table.2"> … … 2716 2719 </table> 2717 2720 </div> 2718 <h2 id="rfc.section.1 1.3"><a href="#rfc.section.11.3">11.3</a> <a id="header.field.registration" href="#header.field.registration">Header Field Registration</a></h2>2719 <p id="rfc.section.1 1.3.p.1">The Message Header Field Registry located at <<a href="http://www.iana.org/assignments/message-headers/message-header-index.html">http://www.iana.org/assignments/message-headers/message-header-index.html</a>> shall be updated with the permanent registrations below (see <a href="#RFC3864" id="rfc.xref.RFC3864.3"><cite title="Registration Procedures for Message Header Fields">[RFC3864]</cite></a>):2721 <h2 id="rfc.section.10.3"><a href="#rfc.section.10.3">10.3</a> <a id="header.field.registration" href="#header.field.registration">Header Field Registration</a></h2> 2722 <p id="rfc.section.10.3.p.1">The Message Header Field Registry located at <<a href="http://www.iana.org/assignments/message-headers/message-header-index.html">http://www.iana.org/assignments/message-headers/message-header-index.html</a>> shall be updated with the permanent registrations below (see <a href="#RFC3864" id="rfc.xref.RFC3864.3"><cite title="Registration Procedures for Message Header Fields">[RFC3864]</cite></a>): 2720 2723 </p> 2721 2724 <div id="rfc.table.3"> … … 2735 2738 <td class="left">http</td> 2736 2739 <td class="left">standard</td> 2737 <td class="left"> <a href="#header.allow" id="rfc.xref.header.allow.3" title="Allow">Section 10.1</a>2740 <td class="left"> <a href="#header.allow" id="rfc.xref.header.allow.3" title="Allow">Section 9.1</a> 2738 2741 </td> 2739 2742 </tr> … … 2742 2745 <td class="left">http</td> 2743 2746 <td class="left">standard</td> 2744 <td class="left"> <a href="#header.date" id="rfc.xref.header.date.2" title="Date">Section 10.2</a>2747 <td class="left"> <a href="#header.date" id="rfc.xref.header.date.2" title="Date">Section 9.2</a> 2745 2748 </td> 2746 2749 </tr> … … 2749 2752 <td class="left">http</td> 2750 2753 <td class="left">standard</td> 2751 <td class="left"> <a href="#header.expect" id="rfc.xref.header.expect.3" title="Expect">Section 10.3</a>2754 <td class="left"> <a href="#header.expect" id="rfc.xref.header.expect.3" title="Expect">Section 9.3</a> 2752 2755 </td> 2753 2756 </tr> … … 2756 2759 <td class="left">http</td> 2757 2760 <td class="left">standard</td> 2758 <td class="left"> <a href="#header.from" id="rfc.xref.header.from.2" title="From">Section 10.4</a>2761 <td class="left"> <a href="#header.from" id="rfc.xref.header.from.2" title="From">Section 9.4</a> 2759 2762 </td> 2760 2763 </tr> … … 2763 2766 <td class="left">http</td> 2764 2767 <td class="left">standard</td> 2765 <td class="left"> <a href="#header.location" id="rfc.xref.header.location.4" title="Location">Section 10.5</a>2768 <td class="left"> <a href="#header.location" id="rfc.xref.header.location.4" title="Location">Section 9.5</a> 2766 2769 </td> 2767 2770 </tr> … … 2770 2773 <td class="left">http</td> 2771 2774 <td class="left">standard</td> 2772 <td class="left"> <a href="#header.max-forwards" id="rfc.xref.header.max-forwards.4" title="Max-Forwards">Section 10.6</a>2775 <td class="left"> <a href="#header.max-forwards" id="rfc.xref.header.max-forwards.4" title="Max-Forwards">Section 9.6</a> 2773 2776 </td> 2774 2777 </tr> … … 2777 2780 <td class="left">http</td> 2778 2781 <td class="left">standard</td> 2779 <td class="left"> <a href="#header.referer" id="rfc.xref.header.referer.2" title="Referer">Section 10.7</a>2782 <td class="left"> <a href="#header.referer" id="rfc.xref.header.referer.2" title="Referer">Section 9.7</a> 2780 2783 </td> 2781 2784 </tr> … … 2784 2787 <td class="left">http</td> 2785 2788 <td class="left">standard</td> 2786 <td class="left"> <a href="#header.retry-after" id="rfc.xref.header.retry-after.3" title="Retry-After">Section 10.8</a>2789 <td class="left"> <a href="#header.retry-after" id="rfc.xref.header.retry-after.3" title="Retry-After">Section 9.8</a> 2787 2790 </td> 2788 2791 </tr> … … 2791 2794 <td class="left">http</td> 2792 2795 <td class="left">standard</td> 2793 <td class="left"> <a href="#header.server" id="rfc.xref.header.server.2" title="Server">Section 10.9</a>2796 <td class="left"> <a href="#header.server" id="rfc.xref.header.server.2" title="Server">Section 9.9</a> 2794 2797 </td> 2795 2798 </tr> … … 2798 2801 <td class="left">http</td> 2799 2802 <td class="left">standard</td> 2800 <td class="left"> <a href="#header.user-agent" id="rfc.xref.header.user-agent.2" title="User-Agent">Section 10.10</a>2803 <td class="left"> <a href="#header.user-agent" id="rfc.xref.header.user-agent.2" title="User-Agent">Section 9.10</a> 2801 2804 </td> 2802 2805 </tr> … … 2804 2807 </table> 2805 2808 </div> 2806 <p id="rfc.section.1 1.3.p.2">The change controller is: "IETF (iesg@ietf.org) - Internet Engineering Task Force".</p>2807 <h1 id="rfc.section.1 2"><a href="#rfc.section.12">12.</a> <a id="security.considerations" href="#security.considerations">Security Considerations</a></h1>2808 <p id="rfc.section.1 2.p.1">This section is meant to inform application developers, information providers, and users of the security limitations in HTTP/1.12809 <p id="rfc.section.10.3.p.2">The change controller is: "IETF (iesg@ietf.org) - Internet Engineering Task Force".</p> 2810 <h1 id="rfc.section.11"><a href="#rfc.section.11">11.</a> <a id="security.considerations" href="#security.considerations">Security Considerations</a></h1> 2811 <p id="rfc.section.11.p.1">This section is meant to inform application developers, information providers, and users of the security limitations in HTTP/1.1 2809 2812 as described by this document. The discussion does not include definitive solutions to the problems revealed, though it does 2810 2813 make some suggestions for reducing security risks. 2811 2814 </p> 2812 <h2 id="rfc.section.1 2.1"><a href="#rfc.section.12.1">12.1</a> <a id="security.sensitive" href="#security.sensitive">Transfer of Sensitive Information</a></h2>2813 <p id="rfc.section.1 2.1.p.1">Like any generic data transfer protocol, HTTP cannot regulate the content of the data that is transferred, nor is there any2815 <h2 id="rfc.section.11.1"><a href="#rfc.section.11.1">11.1</a> <a id="security.sensitive" href="#security.sensitive">Transfer of Sensitive Information</a></h2> 2816 <p id="rfc.section.11.1.p.1">Like any generic data transfer protocol, HTTP cannot regulate the content of the data that is transferred, nor is there any 2814 2817 a priori method of determining the sensitivity of any particular piece of information within the context of any given request. 2815 2818 Therefore, applications <em class="bcp14">SHOULD</em> supply as much control over this information as possible to the provider of that information. Four header fields are worth 2816 2819 special mention in this context: Server, Via, Referer and From. 2817 2820 </p> 2818 <p id="rfc.section.1 2.1.p.2">Revealing the specific software version of the server might allow the server machine to become more vulnerable to attacks2821 <p id="rfc.section.11.1.p.2">Revealing the specific software version of the server might allow the server machine to become more vulnerable to attacks 2819 2822 against software that is known to contain security holes. Implementors <em class="bcp14">SHOULD</em> make the Server header field a configurable option. 2820 2823 </p> 2821 <p id="rfc.section.1 2.1.p.3">Proxies which serve as a portal through a network firewall <em class="bcp14">SHOULD</em> take special precautions regarding the transfer of header information that identifies the hosts behind the firewall. In particular,2824 <p id="rfc.section.11.1.p.3">Proxies which serve as a portal through a network firewall <em class="bcp14">SHOULD</em> take special precautions regarding the transfer of header information that identifies the hosts behind the firewall. In particular, 2822 2825 they <em class="bcp14">SHOULD</em> remove, or replace with sanitized versions, any Via fields generated behind the firewall. 2823 2826 </p> 2824 <p id="rfc.section.1 2.1.p.4">The Referer header field allows reading patterns to be studied and reverse links drawn. Although it can be very useful, its2827 <p id="rfc.section.11.1.p.4">The Referer header field allows reading patterns to be studied and reverse links drawn. Although it can be very useful, its 2825 2828 power can be abused if user details are not separated from the information contained in the Referer. Even when the personal 2826 2829 information has been removed, the Referer header field might indicate a private document's URI whose publication would be 2827 2830 inappropriate. 2828 2831 </p> 2829 <p id="rfc.section.1 2.1.p.5">The information sent in the From field might conflict with the user's privacy interests or their site's security policy, and2832 <p id="rfc.section.11.1.p.5">The information sent in the From field might conflict with the user's privacy interests or their site's security policy, and 2830 2833 hence it <em class="bcp14">SHOULD NOT</em> be transmitted without the user being able to disable, enable, and modify the contents of the field. The user <em class="bcp14">MUST</em> be able to set the contents of this field within a user preference or application defaults configuration. 2831 2834 </p> 2832 <p id="rfc.section.1 2.1.p.6">We suggest, though do not require, that a convenient toggle interface be provided for the user to enable or disable the sending2835 <p id="rfc.section.11.1.p.6">We suggest, though do not require, that a convenient toggle interface be provided for the user to enable or disable the sending 2833 2836 of From and Referer information. 2834 2837 </p> 2835 <p id="rfc.section.1 2.1.p.7">The User-Agent (<a href="#header.user-agent" id="rfc.xref.header.user-agent.3" title="User-Agent">Section 10.10</a>) or Server (<a href="#header.server" id="rfc.xref.header.server.3" title="Server">Section 10.9</a>) header fields can sometimes be used to determine that a specific client or server has a particular security hole which might2838 <p id="rfc.section.11.1.p.7">The User-Agent (<a href="#header.user-agent" id="rfc.xref.header.user-agent.3" title="User-Agent">Section 9.10</a>) or Server (<a href="#header.server" id="rfc.xref.header.server.3" title="Server">Section 9.9</a>) header fields can sometimes be used to determine that a specific client or server has a particular security hole which might 2836 2839 be exploited. Unfortunately, this same information is often used for other valuable purposes for which HTTP currently has 2837 2840 no better mechanism. 2838 2841 </p> 2839 <p id="rfc.section.1 2.1.p.8">Furthermore, the User-Agent header field may contain enough entropy to be used, possibly in conjunction with other material,2842 <p id="rfc.section.11.1.p.8">Furthermore, the User-Agent header field may contain enough entropy to be used, possibly in conjunction with other material, 2840 2843 to uniquely identify the user. 2841 2844 </p> 2842 <p id="rfc.section.1 2.1.p.9">Some request methods, like TRACE (<a href="#TRACE" id="rfc.xref.TRACE.4" title="TRACE">Section 6.8</a>), expose information that was sent in request header fields within the body of their response. Clients <em class="bcp14">SHOULD</em> be careful with sensitive information, like Cookies, Authorization credentials, and other header fields that might be used2845 <p id="rfc.section.11.1.p.9">Some request methods, like TRACE (<a href="#TRACE" id="rfc.xref.TRACE.4" title="TRACE">Section 6.8</a>), expose information that was sent in request header fields within the body of their response. Clients <em class="bcp14">SHOULD</em> be careful with sensitive information, like Cookies, Authorization credentials, and other header fields that might be used 2843 2846 to collect data from the client. 2844 2847 </p> 2845 <h2 id="rfc.section.1 2.2"><a href="#rfc.section.12.2">12.2</a> <a id="encoding.sensitive.information.in.uris" href="#encoding.sensitive.information.in.uris">Encoding Sensitive Information in URIs</a></h2>2846 <p id="rfc.section.1 2.2.p.1">Because the source of a link might be private information or might reveal an otherwise private information source, it is strongly2848 <h2 id="rfc.section.11.2"><a href="#rfc.section.11.2">11.2</a> <a id="encoding.sensitive.information.in.uris" href="#encoding.sensitive.information.in.uris">Encoding Sensitive Information in URIs</a></h2> 2849 <p id="rfc.section.11.2.p.1">Because the source of a link might be private information or might reveal an otherwise private information source, it is strongly 2847 2850 recommended that the user be able to select whether or not the Referer field is sent. For example, a browser client could 2848 2851 have a toggle switch for browsing openly/anonymously, which would respectively enable/disable the sending of Referer and From 2849 2852 information. 2850 2853 </p> 2851 <p id="rfc.section.1 2.2.p.2">Clients <em class="bcp14">SHOULD NOT</em> include a Referer header field in a (non-secure) HTTP request if the referring page was transferred with a secure protocol.2852 </p> 2853 <p id="rfc.section.1 2.2.p.3">Authors of services <em class="bcp14">SHOULD NOT</em> use GET-based forms for the submission of sensitive data because that data will be placed in the request-target. Many existing2854 <p id="rfc.section.11.2.p.2">Clients <em class="bcp14">SHOULD NOT</em> include a Referer header field in a (non-secure) HTTP request if the referring page was transferred with a secure protocol. 2855 </p> 2856 <p id="rfc.section.11.2.p.3">Authors of services <em class="bcp14">SHOULD NOT</em> use GET-based forms for the submission of sensitive data because that data will be placed in the request-target. Many existing 2854 2857 servers, proxies, and user agents log or display the request-target in places where it might be visible to third parties. 2855 2858 Such services can use POST-based form submission instead. 2856 2859 </p> 2857 <h2 id="rfc.section.1 2.3"><a href="#rfc.section.12.3">12.3</a> <a id="location.spoofing-leakage" href="#location.spoofing-leakage">Location Header Fields: Spoofing and Information Leakage</a></h2>2858 <p id="rfc.section.1 2.3.p.1">If a single server supports multiple organizations that do not trust one another, then it <em class="bcp14">MUST</em> check the values of Location and Content-Location header fields in responses that are generated under control of said organizations2860 <h2 id="rfc.section.11.3"><a href="#rfc.section.11.3">11.3</a> <a id="location.spoofing-leakage" href="#location.spoofing-leakage">Location Header Fields: Spoofing and Information Leakage</a></h2> 2861 <p id="rfc.section.11.3.p.1">If a single server supports multiple organizations that do not trust one another, then it <em class="bcp14">MUST</em> check the values of Location and Content-Location header fields in responses that are generated under control of said organizations 2859 2862 to make sure that they do not attempt to invalidate resources over which they have no authority. 2860 2863 </p> 2861 <p id="rfc.section.1 2.3.p.2">Furthermore, appending the fragment identifier from one URI to another one obtained from a Location header field might leak2864 <p id="rfc.section.11.3.p.2">Furthermore, appending the fragment identifier from one URI to another one obtained from a Location header field might leak 2862 2865 confidential information to the target server — although the fragment identifier is not transmitted in the final request, 2863 2866 it might be visible to the user agent through other means, such as scripting. 2864 2867 </p> 2865 <h2 id="rfc.section.1 2.4"><a href="#rfc.section.12.4">12.4</a> Security Considerations for CONNECT2868 <h2 id="rfc.section.11.4"><a href="#rfc.section.11.4">11.4</a> Security Considerations for CONNECT 2866 2869 </h2> 2867 <p id="rfc.section.1 2.4.p.1">Since tunneled data is opaque to the proxy, there are additional risks to tunneling to other well-known or reserved ports.2870 <p id="rfc.section.11.4.p.1">Since tunneled data is opaque to the proxy, there are additional risks to tunneling to other well-known or reserved ports. 2868 2871 A HTTP client CONNECTing to port 25 could relay spam via SMTP, for example. As such, proxies <em class="bcp14">SHOULD</em> restrict CONNECT access to a small number of known ports. 2869 2872 </p> 2870 <h1 id="rfc.section.1 3"><a href="#rfc.section.13">13.</a> <a id="acks" href="#acks">Acknowledgments</a></h1>2871 <p id="rfc.section.1 3.p.1">See <a href="p1-messaging.html#acks" title="Acknowledgments">Section 9</a> of <a href="#Part1" id="rfc.xref.Part1.42"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>.2872 </p> 2873 <h1 id="rfc.references"><a id="rfc.section.1 4" href="#rfc.section.14">14.</a> References2873 <h1 id="rfc.section.12"><a href="#rfc.section.12">12.</a> <a id="acks" href="#acks">Acknowledgments</a></h1> 2874 <p id="rfc.section.12.p.1">See <a href="p1-messaging.html#acks" title="Acknowledgments">Section 9</a> of <a href="#Part1" id="rfc.xref.Part1.42"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>. 2875 </p> 2876 <h1 id="rfc.references"><a id="rfc.section.13" href="#rfc.section.13">13.</a> References 2874 2877 </h1> 2875 <h2 id="rfc.references.1"><a href="#rfc.section.1 4.1" id="rfc.section.14.1">14.1</a> Normative References2878 <h2 id="rfc.references.1"><a href="#rfc.section.13.1" id="rfc.section.13.1">13.1</a> Normative References 2876 2879 </h2> 2877 2880 <table> … … 2922 2925 </tr> 2923 2926 </table> 2924 <h2 id="rfc.references.2"><a href="#rfc.section.1 4.2" id="rfc.section.14.2">14.2</a> Informative References2927 <h2 id="rfc.references.2"><a href="#rfc.section.13.2" id="rfc.section.13.2">13.2</a> Informative References 2925 2928 </h2> 2926 2929 <table> … … 3016 3019 <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 7.4.15</a>) 3017 3020 </p> 3018 <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 10</a>)3021 <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 9</a>) 3019 3022 </p> 3020 3023 <p id="rfc.section.A.p.11">Reclassify "Allow" as response header field, removing the option to specify it in a PUT request. Relax the server requirement 3021 on the contents of the Allow header field and remove requirement on clients to always trust the header field value. (<a href="#header.allow" id="rfc.xref.header.allow.4" title="Allow">Section 10.1</a>)3024 on the contents of the Allow header field and remove requirement on clients to always trust the header field value. (<a href="#header.allow" id="rfc.xref.header.allow.4" title="Allow">Section 9.1</a>) 3022 3025 </p> 3023 3026 <p id="rfc.section.A.p.12">The ABNF for the Expect header field has been both fixed (allowing parameters for value-less expectations as well) and simplified 3024 (allowing trailing semicolons after "100-continue" when they were invalid before). (<a href="#header.expect" id="rfc.xref.header.expect.4" title="Expect">Section 10.3</a>)3027 (allowing trailing semicolons after "100-continue" when they were invalid before). (<a href="#header.expect" id="rfc.xref.header.expect.4" title="Expect">Section 9.3</a>) 3025 3028 </p> 3026 3029 <p id="rfc.section.A.p.13">Correct syntax of Location header field to allow URI references (including relative references and fragments), as referred 3027 3030 symbol "absoluteURI" wasn't what was expected, and add some clarifications as to when use of fragments would not be appropriate. 3028 (<a href="#header.location" id="rfc.xref.header.location.5" title="Location">Section 10.5</a>)3029 </p> 3030 <p id="rfc.section.A.p.14">Restrict Max-Forwards header field to OPTIONS and TRACE (previously, extension methods could have used it as well). (<a href="#header.max-forwards" id="rfc.xref.header.max-forwards.5" title="Max-Forwards">Section 10.6</a>)3031 </p> 3032 <p id="rfc.section.A.p.15">Allow Referer field value of "about:blank" as alternative to not specifying it. (<a href="#header.referer" id="rfc.xref.header.referer.3" title="Referer">Section 10.7</a>)3031 (<a href="#header.location" id="rfc.xref.header.location.5" title="Location">Section 9.5</a>) 3032 </p> 3033 <p id="rfc.section.A.p.14">Restrict Max-Forwards header field to OPTIONS and TRACE (previously, extension methods could have used it as well). (<a href="#header.max-forwards" id="rfc.xref.header.max-forwards.5" title="Max-Forwards">Section 9.6</a>) 3034 </p> 3035 <p id="rfc.section.A.p.15">Allow Referer field value of "about:blank" as alternative to not specifying it. (<a href="#header.referer" id="rfc.xref.header.referer.3" title="Referer">Section 9.7</a>) 3033 3036 </p> 3034 3037 <p id="rfc.section.A.p.16">In the description of the Server header field, the Via field was described as a SHOULD. The requirement was and is stated 3035 correctly in the description of the Via header field in <a href="p1-messaging.html#header.via" title="Via">Section 6.2</a> of <a href="#Part1" id="rfc.xref.Part1.43"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>. (<a href="#header.server" id="rfc.xref.header.server.4" title="Server">Section 10.9</a>)3038 correctly in the description of the Via header field in <a href="p1-messaging.html#header.via" title="Via">Section 6.2</a> of <a href="#Part1" id="rfc.xref.Part1.43"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>. (<a href="#header.server" id="rfc.xref.header.server.4" title="Server">Section 9.9</a>) 3036 3039 </p> 3037 3040 <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a> <a id="collected.abnf" href="#collected.abnf">Collected ABNF</a></h1> … … 3476 3479 <ul class="ind"> 3477 3480 <li><a id="rfc.index.1" href="#rfc.index.1"><b>1</b></a><ul> 3478 <li>100 Continue (status code) <a href="#rfc.xref.status.100.1">4.1</a>, <a href="#rfc.iref.22"><b>7.1.1</b></a>, <a href="#rfc.xref.status.100.2">1 1.2</a></li>3479 <li>100-continue (expect value) <a href="#rfc.iref.89"><b> 10.3</b></a></li>3480 <li>101 Switching Protocols (status code) <a href="#rfc.xref.status.101.1">4.1</a>, <a href="#rfc.iref.23"><b>7.1.2</b></a>, <a href="#rfc.xref.status.101.2">1 1.2</a></li>3481 <li>100 Continue (status code) <a href="#rfc.xref.status.100.1">4.1</a>, <a href="#rfc.iref.22"><b>7.1.1</b></a>, <a href="#rfc.xref.status.100.2">10.2</a></li> 3482 <li>100-continue (expect value) <a href="#rfc.iref.89"><b>9.3</b></a></li> 3483 <li>101 Switching Protocols (status code) <a href="#rfc.xref.status.101.1">4.1</a>, <a href="#rfc.iref.23"><b>7.1.2</b></a>, <a href="#rfc.xref.status.101.2">10.2</a></li> 3481 3484 </ul> 3482 3485 </li> 3483 3486 <li><a id="rfc.index.2" href="#rfc.index.2"><b>2</b></a><ul> 3484 <li>200 OK (status code) <a href="#rfc.xref.status.200.1">4.1</a>, <a href="#rfc.iref.24"><b>7.2.1</b></a>, <a href="#rfc.xref.status.200.2">1 1.2</a></li>3485 <li>201 Created (status code) <a href="#rfc.xref.status.201.1">4.1</a>, <a href="#rfc.iref.25"><b>7.2.2</b></a>, <a href="#rfc.xref.status.201.2">1 1.2</a></li>3486 <li>202 Accepted (status code) <a href="#rfc.xref.status.202.1">4.1</a>, <a href="#rfc.iref.26"><b>7.2.3</b></a>, <a href="#rfc.xref.status.202.2">1 1.2</a></li>3487 <li>203 Non-Authoritative Information (status code) <a href="#rfc.xref.status.203.1">4.1</a>, <a href="#rfc.iref.27"><b>7.2.4</b></a>, <a href="#rfc.xref.status.203.2">1 1.2</a>, <a href="#rfc.xref.status.203.3">A</a></li>3488 <li>204 No Content (status code) <a href="#rfc.xref.status.204.1">4.1</a>, <a href="#rfc.iref.28"><b>7.2.5</b></a>, <a href="#rfc.xref.status.204.2">1 1.2</a></li>3489 <li>205 Reset Content (status code) <a href="#rfc.xref.status.205.1">4.1</a>, <a href="#rfc.iref.29"><b>7.2.6</b></a>, <a href="#rfc.xref.status.205.2">1 1.2</a></li>3487 <li>200 OK (status code) <a href="#rfc.xref.status.200.1">4.1</a>, <a href="#rfc.iref.24"><b>7.2.1</b></a>, <a href="#rfc.xref.status.200.2">10.2</a></li> 3488 <li>201 Created (status code) <a href="#rfc.xref.status.201.1">4.1</a>, <a href="#rfc.iref.25"><b>7.2.2</b></a>, <a href="#rfc.xref.status.201.2">10.2</a></li> 3489 <li>202 Accepted (status code) <a href="#rfc.xref.status.202.1">4.1</a>, <a href="#rfc.iref.26"><b>7.2.3</b></a>, <a href="#rfc.xref.status.202.2">10.2</a></li> 3490 <li>203 Non-Authoritative Information (status code) <a href="#rfc.xref.status.203.1">4.1</a>, <a href="#rfc.iref.27"><b>7.2.4</b></a>, <a href="#rfc.xref.status.203.2">10.2</a>, <a href="#rfc.xref.status.203.3">A</a></li> 3491 <li>204 No Content (status code) <a href="#rfc.xref.status.204.1">4.1</a>, <a href="#rfc.iref.28"><b>7.2.5</b></a>, <a href="#rfc.xref.status.204.2">10.2</a></li> 3492 <li>205 Reset Content (status code) <a href="#rfc.xref.status.205.1">4.1</a>, <a href="#rfc.iref.29"><b>7.2.6</b></a>, <a href="#rfc.xref.status.205.2">10.2</a></li> 3490 3493 </ul> 3491 3494 </li> 3492 3495 <li><a id="rfc.index.3" href="#rfc.index.3"><b>3</b></a><ul> 3493 <li>300 Multiple Choices (status code) <a href="#rfc.xref.status.300.1">4.1</a>, <a href="#rfc.iref.30"><b>7.3.1</b></a>, <a href="#rfc.xref.status.300.2">1 1.2</a></li>3494 <li>301 Moved Permanently (status code) <a href="#rfc.xref.status.301.1">4.1</a>, <a href="#rfc.iref.31"><b>7.3.2</b></a>, <a href="#rfc.xref.status.301.2">1 1.2</a>, <a href="#rfc.xref.status.301.3">A</a></li>3495 <li>302 Found (status code) <a href="#rfc.xref.status.302.1">4.1</a>, <a href="#rfc.iref.32"><b>7.3.3</b></a>, <a href="#rfc.xref.status.302.2">1 1.2</a>, <a href="#rfc.xref.status.302.3">A</a></li>3496 <li>303 See Other (status code) <a href="#rfc.xref.status.303.1">4.1</a>, <a href="#rfc.iref.33"><b>7.3.4</b></a>, <a href="#rfc.xref.status.303.2">1 1.2</a></li>3497 <li>305 Use Proxy (status code) <a href="#rfc.xref.status.305.1">4.1</a>, <a href="#rfc.iref.34"><b>7.3.5</b></a>, <a href="#rfc.xref.status.305.2">1 1.2</a>, <a href="#rfc.xref.status.305.3">A</a></li>3498 <li>306 (Unused) (status code) <a href="#rfc.iref.35"><b>7.3.6</b></a>, <a href="#rfc.xref.status.306.1">1 1.2</a></li>3499 <li>307 Temporary Redirect (status code) <a href="#rfc.xref.status.307.1">4.1</a>, <a href="#rfc.iref.36"><b>7.3.7</b></a>, <a href="#rfc.xref.status.307.2">1 1.2</a>, <a href="#rfc.xref.status.307.3">A</a></li>3496 <li>300 Multiple Choices (status code) <a href="#rfc.xref.status.300.1">4.1</a>, <a href="#rfc.iref.30"><b>7.3.1</b></a>, <a href="#rfc.xref.status.300.2">10.2</a></li> 3497 <li>301 Moved Permanently (status code) <a href="#rfc.xref.status.301.1">4.1</a>, <a href="#rfc.iref.31"><b>7.3.2</b></a>, <a href="#rfc.xref.status.301.2">10.2</a>, <a href="#rfc.xref.status.301.3">A</a></li> 3498 <li>302 Found (status code) <a href="#rfc.xref.status.302.1">4.1</a>, <a href="#rfc.iref.32"><b>7.3.3</b></a>, <a href="#rfc.xref.status.302.2">10.2</a>, <a href="#rfc.xref.status.302.3">A</a></li> 3499 <li>303 See Other (status code) <a href="#rfc.xref.status.303.1">4.1</a>, <a href="#rfc.iref.33"><b>7.3.4</b></a>, <a href="#rfc.xref.status.303.2">10.2</a></li> 3500 <li>305 Use Proxy (status code) <a href="#rfc.xref.status.305.1">4.1</a>, <a href="#rfc.iref.34"><b>7.3.5</b></a>, <a href="#rfc.xref.status.305.2">10.2</a>, <a href="#rfc.xref.status.305.3">A</a></li> 3501 <li>306 (Unused) (status code) <a href="#rfc.iref.35"><b>7.3.6</b></a>, <a href="#rfc.xref.status.306.1">10.2</a></li> 3502 <li>307 Temporary Redirect (status code) <a href="#rfc.xref.status.307.1">4.1</a>, <a href="#rfc.iref.36"><b>7.3.7</b></a>, <a href="#rfc.xref.status.307.2">10.2</a>, <a href="#rfc.xref.status.307.3">A</a></li> 3500 3503 </ul> 3501 3504 </li> 3502 3505 <li><a id="rfc.index.4" href="#rfc.index.4"><b>4</b></a><ul> 3503 <li>400 Bad Request (status code) <a href="#rfc.xref.status.400.1">4.1</a>, <a href="#rfc.iref.37"><b>7.4.1</b></a>, <a href="#rfc.xref.status.400.2">1 1.2</a></li>3504 <li>402 Payment Required (status code) <a href="#rfc.xref.status.402.1">4.1</a>, <a href="#rfc.iref.38"><b>7.4.2</b></a>, <a href="#rfc.xref.status.402.2">1 1.2</a></li>3505 <li>403 Forbidden (status code) <a href="#rfc.xref.status.403.1">4.1</a>, <a href="#rfc.iref.39"><b>7.4.3</b></a>, <a href="#rfc.xref.status.403.2">1 1.2</a></li>3506 <li>404 Not Found (status code) <a href="#rfc.xref.status.404.1">4.1</a>, <a href="#rfc.iref.40"><b>7.4.4</b></a>, <a href="#rfc.xref.status.404.2">1 1.2</a></li>3507 <li>405 Method Not Allowed (status code) <a href="#rfc.xref.status.405.1">4.1</a>, <a href="#rfc.iref.41"><b>7.4.5</b></a>, <a href="#rfc.xref.status.405.2">1 1.2</a></li>3508 <li>406 Not Acceptable (status code) <a href="#rfc.xref.status.406.1">4.1</a>, <a href="#rfc.iref.42"><b>7.4.6</b></a>, <a href="#rfc.xref.status.406.2">1 1.2</a></li>3509 <li>408 Request Timeout (status code) <a href="#rfc.xref.status.408.1">4.1</a>, <a href="#rfc.iref.43"><b>7.4.7</b></a>, <a href="#rfc.xref.status.408.2">1 1.2</a></li>3510 <li>409 Conflict (status code) <a href="#rfc.xref.status.409.1">4.1</a>, <a href="#rfc.iref.44"><b>7.4.8</b></a>, <a href="#rfc.xref.status.409.2">1 1.2</a></li>3511 <li>410 Gone (status code) <a href="#rfc.xref.status.410.1">4.1</a>, <a href="#rfc.iref.45"><b>7.4.9</b></a>, <a href="#rfc.xref.status.410.2">1 1.2</a></li>3512 <li>411 Length Required (status code) <a href="#rfc.xref.status.411.1">4.1</a>, <a href="#rfc.iref.46"><b>7.4.10</b></a>, <a href="#rfc.xref.status.411.2">1 1.2</a></li>3513 <li>413 Request Representation Too Large (status code) <a href="#rfc.xref.status.413.1">4.1</a>, <a href="#rfc.iref.47"><b>7.4.11</b></a>, <a href="#rfc.xref.status.413.2">1 1.2</a></li>3514 <li>414 URI Too Long (status code) <a href="#rfc.xref.status.414.1">4.1</a>, <a href="#rfc.iref.48"><b>7.4.12</b></a>, <a href="#rfc.xref.status.414.2">1 1.2</a></li>3515 <li>415 Unsupported Media Type (status code) <a href="#rfc.xref.status.415.1">4.1</a>, <a href="#rfc.iref.49"><b>7.4.13</b></a>, <a href="#rfc.xref.status.415.2">1 1.2</a></li>3516 <li>417 Expectation Failed (status code) <a href="#rfc.xref.status.417.1">4.1</a>, <a href="#rfc.iref.50"><b>7.4.14</b></a>, <a href="#rfc.xref.status.417.2">1 1.2</a></li>3517 <li>426 Upgrade Required (status code) <a href="#rfc.xref.status.426.1">4.1</a>, <a href="#rfc.iref.51"><b>7.4.15</b></a>, <a href="#rfc.xref.status.426.2">1 1.2</a>, <a href="#rfc.xref.status.426.3">A</a></li>3506 <li>400 Bad Request (status code) <a href="#rfc.xref.status.400.1">4.1</a>, <a href="#rfc.iref.37"><b>7.4.1</b></a>, <a href="#rfc.xref.status.400.2">10.2</a></li> 3507 <li>402 Payment Required (status code) <a href="#rfc.xref.status.402.1">4.1</a>, <a href="#rfc.iref.38"><b>7.4.2</b></a>, <a href="#rfc.xref.status.402.2">10.2</a></li> 3508 <li>403 Forbidden (status code) <a href="#rfc.xref.status.403.1">4.1</a>, <a href="#rfc.iref.39"><b>7.4.3</b></a>, <a href="#rfc.xref.status.403.2">10.2</a></li> 3509 <li>404 Not Found (status code) <a href="#rfc.xref.status.404.1">4.1</a>, <a href="#rfc.iref.40"><b>7.4.4</b></a>, <a href="#rfc.xref.status.404.2">10.2</a></li> 3510 <li>405 Method Not Allowed (status code) <a href="#rfc.xref.status.405.1">4.1</a>, <a href="#rfc.iref.41"><b>7.4.5</b></a>, <a href="#rfc.xref.status.405.2">10.2</a></li> 3511 <li>406 Not Acceptable (status code) <a href="#rfc.xref.status.406.1">4.1</a>, <a href="#rfc.iref.42"><b>7.4.6</b></a>, <a href="#rfc.xref.status.406.2">10.2</a></li> 3512 <li>408 Request Timeout (status code) <a href="#rfc.xref.status.408.1">4.1</a>, <a href="#rfc.iref.43"><b>7.4.7</b></a>, <a href="#rfc.xref.status.408.2">10.2</a></li> 3513 <li>409 Conflict (status code) <a href="#rfc.xref.status.409.1">4.1</a>, <a href="#rfc.iref.44"><b>7.4.8</b></a>, <a href="#rfc.xref.status.409.2">10.2</a></li> 3514 <li>410 Gone (status code) <a href="#rfc.xref.status.410.1">4.1</a>, <a href="#rfc.iref.45"><b>7.4.9</b></a>, <a href="#rfc.xref.status.410.2">10.2</a></li> 3515 <li>411 Length Required (status code) <a href="#rfc.xref.status.411.1">4.1</a>, <a href="#rfc.iref.46"><b>7.4.10</b></a>, <a href="#rfc.xref.status.411.2">10.2</a></li> 3516 <li>413 Request Representation Too Large (status code) <a href="#rfc.xref.status.413.1">4.1</a>, <a href="#rfc.iref.47"><b>7.4.11</b></a>, <a href="#rfc.xref.status.413.2">10.2</a></li> 3517 <li>414 URI Too Long (status code) <a href="#rfc.xref.status.414.1">4.1</a>, <a href="#rfc.iref.48"><b>7.4.12</b></a>, <a href="#rfc.xref.status.414.2">10.2</a></li> 3518 <li>415 Unsupported Media Type (status code) <a href="#rfc.xref.status.415.1">4.1</a>, <a href="#rfc.iref.49"><b>7.4.13</b></a>, <a href="#rfc.xref.status.415.2">10.2</a></li> 3519 <li>417 Expectation Failed (status code) <a href="#rfc.xref.status.417.1">4.1</a>, <a href="#rfc.iref.50"><b>7.4.14</b></a>, <a href="#rfc.xref.status.417.2">10.2</a></li> 3520 <li>426 Upgrade Required (status code) <a href="#rfc.xref.status.426.1">4.1</a>, <a href="#rfc.iref.51"><b>7.4.15</b></a>, <a href="#rfc.xref.status.426.2">10.2</a>, <a href="#rfc.xref.status.426.3">A</a></li> 3518 3521 </ul> 3519 3522 </li> 3520 3523 <li><a id="rfc.index.5" href="#rfc.index.5"><b>5</b></a><ul> 3521 <li>500 Internal Server Error (status code) <a href="#rfc.xref.status.500.1">4.1</a>, <a href="#rfc.iref.52"><b>7.5.1</b></a>, <a href="#rfc.xref.status.500.2">1 1.2</a></li>3522 <li>501 Not Implemented (status code) <a href="#rfc.xref.status.501.1">4.1</a>, <a href="#rfc.iref.53"><b>7.5.2</b></a>, <a href="#rfc.xref.status.501.2">1 1.2</a></li>3523 <li>502 Bad Gateway (status code) <a href="#rfc.xref.status.502.1">4.1</a>, <a href="#rfc.iref.54"><b>7.5.3</b></a>, <a href="#rfc.xref.status.502.2">1 1.2</a></li>3524 <li>503 Service Unavailable (status code) <a href="#rfc.xref.status.503.1">4.1</a>, <a href="#rfc.iref.55"><b>7.5.4</b></a>, <a href="#rfc.xref.status.503.2">1 1.2</a></li>3525 <li>504 Gateway Timeout (status code) <a href="#rfc.xref.status.504.1">4.1</a>, <a href="#rfc.iref.56"><b>7.5.5</b></a>, <a href="#rfc.xref.status.504.2">1 1.2</a></li>3526 <li>505 HTTP Version Not Supported (status code) <a href="#rfc.xref.status.505.1">4.1</a>, <a href="#rfc.iref.57"><b>7.5.6</b></a>, <a href="#rfc.xref.status.505.2">1 1.2</a></li>3524 <li>500 Internal Server Error (status code) <a href="#rfc.xref.status.500.1">4.1</a>, <a href="#rfc.iref.52"><b>7.5.1</b></a>, <a href="#rfc.xref.status.500.2">10.2</a></li> 3525 <li>501 Not Implemented (status code) <a href="#rfc.xref.status.501.1">4.1</a>, <a href="#rfc.iref.53"><b>7.5.2</b></a>, <a href="#rfc.xref.status.501.2">10.2</a></li> 3526 <li>502 Bad Gateway (status code) <a href="#rfc.xref.status.502.1">4.1</a>, <a href="#rfc.iref.54"><b>7.5.3</b></a>, <a href="#rfc.xref.status.502.2">10.2</a></li> 3527 <li>503 Service Unavailable (status code) <a href="#rfc.xref.status.503.1">4.1</a>, <a href="#rfc.iref.55"><b>7.5.4</b></a>, <a href="#rfc.xref.status.503.2">10.2</a></li> 3528 <li>504 Gateway Timeout (status code) <a href="#rfc.xref.status.504.1">4.1</a>, <a href="#rfc.iref.56"><b>7.5.5</b></a>, <a href="#rfc.xref.status.504.2">10.2</a></li> 3529 <li>505 HTTP Version Not Supported (status code) <a href="#rfc.xref.status.505.1">4.1</a>, <a href="#rfc.iref.57"><b>7.5.6</b></a>, <a href="#rfc.xref.status.505.2">10.2</a></li> 3527 3530 </ul> 3528 3531 </li> 3529 3532 <li><a id="rfc.index.A" href="#rfc.index.A"><b>A</b></a><ul> 3530 <li>Allow header field <a href="#rfc.xref.header.allow.1">2</a>, <a href="#rfc.xref.header.allow.2">3.3</a>, <a href="#rfc.iref.a.1"><b> 10.1</b></a>, <a href="#rfc.xref.header.allow.3">11.3</a>, <a href="#rfc.xref.header.allow.4">A</a></li>3533 <li>Allow header field <a href="#rfc.xref.header.allow.1">2</a>, <a href="#rfc.xref.header.allow.2">3.3</a>, <a href="#rfc.iref.a.1"><b>9.1</b></a>, <a href="#rfc.xref.header.allow.3">10.3</a>, <a href="#rfc.xref.header.allow.4">A</a></li> 3531 3534 </ul> 3532 3535 </li> 3533 3536 <li><a id="rfc.index.C" href="#rfc.index.C"><b>C</b></a><ul> 3534 <li>CONNECT method <a href="#rfc.xref.CONNECT.1">2.1</a>, <a href="#rfc.iref.c.1"><b>6.9</b></a>, <a href="#rfc.xref.CONNECT.2">1 1.1</a>, <a href="#rfc.xref.CONNECT.3">A</a></li>3537 <li>CONNECT method <a href="#rfc.xref.CONNECT.1">2.1</a>, <a href="#rfc.iref.c.1"><b>6.9</b></a>, <a href="#rfc.xref.CONNECT.2">10.1</a>, <a href="#rfc.xref.CONNECT.3">A</a></li> 3535 3538 </ul> 3536 3539 </li> 3537 3540 <li><a id="rfc.index.D" href="#rfc.index.D"><b>D</b></a><ul> 3538 <li>Date header field <a href="#rfc.xref.header.date.1">3.3</a>, <a href="#rfc.iref.d.2"><b> 10.2</b></a>, <a href="#rfc.xref.header.date.2">11.3</a></li>3539 <li>DELETE method <a href="#rfc.xref.DELETE.1">2.1</a>, <a href="#rfc.iref.d.1"><b>6.7</b></a>, <a href="#rfc.xref.DELETE.2">1 1.1</a></li>3540 <li><em>draft-reschke-http-status-308</em> <a href="#rfc.xref.draft-reschke-http-status-308.1">7.3.7</a>, <a href="#draft-reschke-http-status-308"><b>1 4.2</b></a></li>3541 <li>Date header field <a href="#rfc.xref.header.date.1">3.3</a>, <a href="#rfc.iref.d.2"><b>9.2</b></a>, <a href="#rfc.xref.header.date.2">10.3</a></li> 3542 <li>DELETE method <a href="#rfc.xref.DELETE.1">2.1</a>, <a href="#rfc.iref.d.1"><b>6.7</b></a>, <a href="#rfc.xref.DELETE.2">10.1</a></li> 3543 <li><em>draft-reschke-http-status-308</em> <a href="#rfc.xref.draft-reschke-http-status-308.1">7.3.7</a>, <a href="#draft-reschke-http-status-308"><b>13.2</b></a></li> 3541 3544 </ul> 3542 3545 </li> 3543 3546 <li><a id="rfc.index.E" href="#rfc.index.E"><b>E</b></a><ul> 3544 <li>Expect header field <a href="#rfc.xref.header.expect.1">3.2</a>, <a href="#rfc.xref.header.expect.2">7.4.14</a>, <a href="#rfc.iref.e.1"><b> 10.3</b></a>, <a href="#rfc.xref.header.expect.3">11.3</a>, <a href="#rfc.xref.header.expect.4">A</a></li>3547 <li>Expect header field <a href="#rfc.xref.header.expect.1">3.2</a>, <a href="#rfc.xref.header.expect.2">7.4.14</a>, <a href="#rfc.iref.e.1"><b>9.3</b></a>, <a href="#rfc.xref.header.expect.3">10.3</a>, <a href="#rfc.xref.header.expect.4">A</a></li> 3545 3548 <li>Expect Values 3546 3549 <ul> 3547 <li>100-continue <a href="#rfc.iref.e.2"><b> 10.3</b></a></li>3550 <li>100-continue <a href="#rfc.iref.e.2"><b>9.3</b></a></li> 3548 3551 </ul> 3549 3552 </li> … … 3551 3554 </li> 3552 3555 <li><a id="rfc.index.F" href="#rfc.index.F"><b>F</b></a><ul> 3553 <li>From header field <a href="#rfc.xref.header.from.1">3.2</a>, <a href="#rfc.iref.f.1"><b> 10.4</b></a>, <a href="#rfc.xref.header.from.2">11.3</a></li>3556 <li>From header field <a href="#rfc.xref.header.from.1">3.2</a>, <a href="#rfc.iref.f.1"><b>9.4</b></a>, <a href="#rfc.xref.header.from.2">10.3</a></li> 3554 3557 </ul> 3555 3558 </li> 3556 3559 <li><a id="rfc.index.G" href="#rfc.index.G"><b>G</b></a><ul> 3557 <li>GET method <a href="#rfc.xref.GET.1">2.1</a>, <a href="#rfc.iref.g.5"><b>6.3</b></a>, <a href="#rfc.xref.GET.2">1 1.1</a></li>3560 <li>GET method <a href="#rfc.xref.GET.1">2.1</a>, <a href="#rfc.iref.g.5"><b>6.3</b></a>, <a href="#rfc.xref.GET.2">10.1</a></li> 3558 3561 <li><tt>Grammar</tt> 3559 3562 <ul> 3560 <li><tt>Allow</tt> <a href="#rfc.iref.g.24"><b> 10.1</b></a></li>3561 <li><tt>asctime-date</tt> <a href="#rfc.iref.g.21"><b>8 </b></a></li>3562 <li><tt>Date</tt> <a href="#rfc.iref.g.25"><b> 10.2</b></a></li>3563 <li><tt>date1</tt> <a href="#rfc.iref.g.8"><b>8 </b></a></li>3564 <li><tt>day</tt> <a href="#rfc.iref.g.15"><b>8 </b></a></li>3565 <li><tt>day-name</tt> <a href="#rfc.iref.g.13"><b>8 </b></a></li>3566 <li><tt>day-name-l</tt> <a href="#rfc.iref.g.14"><b>8 </b></a></li>3567 <li><tt>delta-seconds</tt> <a href="#rfc.iref.g.36"><b> 10.8</b></a></li>3568 <li><tt>Expect</tt> <a href="#rfc.iref.g.26"><b> 10.3</b></a></li>3569 <li><tt>expect-name</tt> <a href="#rfc.iref.g.30"><b> 10.3</b></a></li>3570 <li><tt>expect-param</tt> <a href="#rfc.iref.g.28"><b> 10.3</b></a></li>3571 <li><tt>expect-value</tt> <a href="#rfc.iref.g.29"><b> 10.3</b></a></li>3572 <li><tt>expectation</tt> <a href="#rfc.iref.g.27"><b> 10.3</b></a></li>3563 <li><tt>Allow</tt> <a href="#rfc.iref.g.24"><b>9.1</b></a></li> 3564 <li><tt>asctime-date</tt> <a href="#rfc.iref.g.21"><b>8.1</b></a></li> 3565 <li><tt>Date</tt> <a href="#rfc.iref.g.25"><b>9.2</b></a></li> 3566 <li><tt>date1</tt> <a href="#rfc.iref.g.8"><b>8.1</b></a></li> 3567 <li><tt>day</tt> <a href="#rfc.iref.g.15"><b>8.1</b></a></li> 3568 <li><tt>day-name</tt> <a href="#rfc.iref.g.13"><b>8.1</b></a></li> 3569 <li><tt>day-name-l</tt> <a href="#rfc.iref.g.14"><b>8.1</b></a></li> 3570 <li><tt>delta-seconds</tt> <a href="#rfc.iref.g.36"><b>9.8</b></a></li> 3571 <li><tt>Expect</tt> <a href="#rfc.iref.g.26"><b>9.3</b></a></li> 3572 <li><tt>expect-name</tt> <a href="#rfc.iref.g.30"><b>9.3</b></a></li> 3573 <li><tt>expect-param</tt> <a href="#rfc.iref.g.28"><b>9.3</b></a></li> 3574 <li><tt>expect-value</tt> <a href="#rfc.iref.g.29"><b>9.3</b></a></li> 3575 <li><tt>expectation</tt> <a href="#rfc.iref.g.27"><b>9.3</b></a></li> 3573 3576 <li><tt>extension-code</tt> <a href="#rfc.iref.g.3"><b>4</b></a></li> 3574 <li><tt>From</tt> <a href="#rfc.iref.g.31"><b> 10.4</b></a></li>3575 <li><tt>GMT</tt> <a href="#rfc.iref.g.18"><b>8 </b></a></li>3576 <li><tt>hour</tt> <a href="#rfc.iref.g.10"><b>8 </b></a></li>3577 <li><tt>HTTP-date</tt> <a href="#rfc.iref.g.6"><b>8 </b></a></li>3578 <li><tt>Location</tt> <a href="#rfc.iref.g.32"><b> 10.5</b></a></li>3579 <li><tt>Max-Forwards</tt> <a href="#rfc.iref.g.33"><b> 10.6</b></a></li>3577 <li><tt>From</tt> <a href="#rfc.iref.g.31"><b>9.4</b></a></li> 3578 <li><tt>GMT</tt> <a href="#rfc.iref.g.18"><b>8.1</b></a></li> 3579 <li><tt>hour</tt> <a href="#rfc.iref.g.10"><b>8.1</b></a></li> 3580 <li><tt>HTTP-date</tt> <a href="#rfc.iref.g.6"><b>8.1</b></a></li> 3581 <li><tt>Location</tt> <a href="#rfc.iref.g.32"><b>9.5</b></a></li> 3582 <li><tt>Max-Forwards</tt> <a href="#rfc.iref.g.33"><b>9.6</b></a></li> 3580 3583 <li><tt>method</tt> <a href="#rfc.iref.g.1"><b>2</b></a></li> 3581 <li><tt>minute</tt> <a href="#rfc.iref.g.11"><b>8 </b></a></li>3582 <li><tt>month</tt> <a href="#rfc.iref.g.16"><b>8 </b></a></li>3583 <li><tt>obs-date</tt> <a href="#rfc.iref.g.19"><b>8 </b></a></li>3584 <li><tt>product</tt> <a href="#rfc.iref.g.22"><b> 9</b></a></li>3585 <li><tt>product-version</tt> <a href="#rfc.iref.g.23"><b> 9</b></a></li>3584 <li><tt>minute</tt> <a href="#rfc.iref.g.11"><b>8.1</b></a></li> 3585 <li><tt>month</tt> <a href="#rfc.iref.g.16"><b>8.1</b></a></li> 3586 <li><tt>obs-date</tt> <a href="#rfc.iref.g.19"><b>8.1</b></a></li> 3587 <li><tt>product</tt> <a href="#rfc.iref.g.22"><b>8.2</b></a></li> 3588 <li><tt>product-version</tt> <a href="#rfc.iref.g.23"><b>8.2</b></a></li> 3586 3589 <li><tt>reason-phrase</tt> <a href="#rfc.iref.g.4"><b>4</b></a></li> 3587 <li><tt>Referer</tt> <a href="#rfc.iref.g.34"><b> 10.7</b></a></li>3588 <li><tt>Retry-After</tt> <a href="#rfc.iref.g.35"><b> 10.8</b></a></li>3589 <li><tt>rfc1123-date</tt> <a href="#rfc.iref.g.7"><b>8 </b></a></li>3590 <li><tt>rfc850-date</tt> <a href="#rfc.iref.g.20"><b>8 </b></a></li>3591 <li><tt>second</tt> <a href="#rfc.iref.g.12"><b>8 </b></a></li>3592 <li><tt>Server</tt> <a href="#rfc.iref.g.37"><b> 10.9</b></a></li>3590 <li><tt>Referer</tt> <a href="#rfc.iref.g.34"><b>9.7</b></a></li> 3591 <li><tt>Retry-After</tt> <a href="#rfc.iref.g.35"><b>9.8</b></a></li> 3592 <li><tt>rfc1123-date</tt> <a href="#rfc.iref.g.7"><b>8.1</b></a></li> 3593 <li><tt>rfc850-date</tt> <a href="#rfc.iref.g.20"><b>8.1</b></a></li> 3594 <li><tt>second</tt> <a href="#rfc.iref.g.12"><b>8.1</b></a></li> 3595 <li><tt>Server</tt> <a href="#rfc.iref.g.37"><b>9.9</b></a></li> 3593 3596 <li><tt>status-code</tt> <a href="#rfc.iref.g.2"><b>4</b></a></li> 3594 <li><tt>time-of-day</tt> <a href="#rfc.iref.g.9"><b>8 </b></a></li>3595 <li><tt>User-Agent</tt> <a href="#rfc.iref.g.38"><b> 10.10</b></a></li>3596 <li><tt>year</tt> <a href="#rfc.iref.g.17"><b>8 </b></a></li>3597 <li><tt>time-of-day</tt> <a href="#rfc.iref.g.9"><b>8.1</b></a></li> 3598 <li><tt>User-Agent</tt> <a href="#rfc.iref.g.38"><b>9.10</b></a></li> 3599 <li><tt>year</tt> <a href="#rfc.iref.g.17"><b>8.1</b></a></li> 3597 3600 </ul> 3598 3601 </li> … … 3600 3603 </li> 3601 3604 <li><a id="rfc.index.H" href="#rfc.index.H"><b>H</b></a><ul> 3602 <li>HEAD method <a href="#rfc.xref.HEAD.1">2.1</a>, <a href="#rfc.iref.h.1"><b>6.4</b></a>, <a href="#rfc.xref.HEAD.2">1 1.1</a></li>3605 <li>HEAD method <a href="#rfc.xref.HEAD.1">2.1</a>, <a href="#rfc.iref.h.1"><b>6.4</b></a>, <a href="#rfc.xref.HEAD.2">10.1</a></li> 3603 3606 <li>Header Fields 3604 3607 <ul> 3605 <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> 10.1</b></a>, <a href="#rfc.xref.header.allow.3">11.3</a>, <a href="#rfc.xref.header.allow.4">A</a></li>3606 <li>Date <a href="#rfc.xref.header.date.1">3.3</a>, <a href="#rfc.iref.h.3"><b> 10.2</b></a>, <a href="#rfc.xref.header.date.2">11.3</a></li>3607 <li>Expect <a href="#rfc.xref.header.expect.1">3.2</a>, <a href="#rfc.xref.header.expect.2">7.4.14</a>, <a href="#rfc.iref.h.4"><b> 10.3</b></a>, <a href="#rfc.xref.header.expect.3">11.3</a>, <a href="#rfc.xref.header.expect.4">A</a></li>3608 <li>From <a href="#rfc.xref.header.from.1">3.2</a>, <a href="#rfc.iref.h.5"><b> 10.4</b></a>, <a href="#rfc.xref.header.from.2">11.3</a></li>3609 <li>Location <a href="#rfc.xref.header.location.1">3.3</a>, <a href="#rfc.xref.header.location.2">6.5</a>, <a href="#rfc.xref.header.location.3">7.3</a>, <a href="#rfc.iref.h.6"><b> 10.5</b></a>, <a href="#rfc.xref.header.location.4">11.3</a>, <a href="#rfc.xref.header.location.5">A</a></li>3610 <li>Max-Forwards <a href="#rfc.xref.header.max-forwards.1">3.2</a>, <a href="#rfc.xref.header.max-forwards.2">6.2</a>, <a href="#rfc.xref.header.max-forwards.3">6.8</a>, <a href="#rfc.iref.h.7"><b> 10.6</b></a>, <a href="#rfc.xref.header.max-forwards.4">11.3</a>, <a href="#rfc.xref.header.max-forwards.5">A</a></li>3611 <li>Referer <a href="#rfc.xref.header.referer.1">3.2</a>, <a href="#rfc.iref.h.8"><b> 10.7</b></a>, <a href="#rfc.xref.header.referer.2">11.3</a>, <a href="#rfc.xref.header.referer.3">A</a></li>3612 <li>Retry-After <a href="#rfc.xref.header.retry-after.1">3.3</a>, <a href="#rfc.xref.header.retry-after.2">7.5.4</a>, <a href="#rfc.iref.h.9"><b> 10.8</b></a>, <a href="#rfc.xref.header.retry-after.3">11.3</a></li>3613 <li>Server <a href="#rfc.xref.header.server.1">3.3</a>, <a href="#rfc.iref.h.10"><b> 10.9</b></a>, <a href="#rfc.xref.header.server.2">11.3</a>, <a href="#rfc.xref.header.server.3">12.1</a>, <a href="#rfc.xref.header.server.4">A</a></li>3614 <li>User-Agent <a href="#rfc.xref.header.user-agent.1">3.2</a>, <a href="#rfc.iref.h.11"><b> 10.10</b></a>, <a href="#rfc.xref.header.user-agent.2">11.3</a>, <a href="#rfc.xref.header.user-agent.3">12.1</a></li>3608 <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>9.1</b></a>, <a href="#rfc.xref.header.allow.3">10.3</a>, <a href="#rfc.xref.header.allow.4">A</a></li> 3609 <li>Date <a href="#rfc.xref.header.date.1">3.3</a>, <a href="#rfc.iref.h.3"><b>9.2</b></a>, <a href="#rfc.xref.header.date.2">10.3</a></li> 3610 <li>Expect <a href="#rfc.xref.header.expect.1">3.2</a>, <a href="#rfc.xref.header.expect.2">7.4.14</a>, <a href="#rfc.iref.h.4"><b>9.3</b></a>, <a href="#rfc.xref.header.expect.3">10.3</a>, <a href="#rfc.xref.header.expect.4">A</a></li> 3611 <li>From <a href="#rfc.xref.header.from.1">3.2</a>, <a href="#rfc.iref.h.5"><b>9.4</b></a>, <a href="#rfc.xref.header.from.2">10.3</a></li> 3612 <li>Location <a href="#rfc.xref.header.location.1">3.3</a>, <a href="#rfc.xref.header.location.2">6.5</a>, <a href="#rfc.xref.header.location.3">7.3</a>, <a href="#rfc.iref.h.6"><b>9.5</b></a>, <a href="#rfc.xref.header.location.4">10.3</a>, <a href="#rfc.xref.header.location.5">A</a></li> 3613 <li>Max-Forwards <a href="#rfc.xref.header.max-forwards.1">3.2</a>, <a href="#rfc.xref.header.max-forwards.2">6.2</a>, <a href="#rfc.xref.header.max-forwards.3">6.8</a>, <a href="#rfc.iref.h.7"><b>9.6</b></a>, <a href="#rfc.xref.header.max-forwards.4">10.3</a>, <a href="#rfc.xref.header.max-forwards.5">A</a></li> 3614 <li>Referer <a href="#rfc.xref.header.referer.1">3.2</a>, <a href="#rfc.iref.h.8"><b>9.7</b></a>, <a href="#rfc.xref.header.referer.2">10.3</a>, <a href="#rfc.xref.header.referer.3">A</a></li> 3615 <li>Retry-After <a href="#rfc.xref.header.retry-after.1">3.3</a>, <a href="#rfc.xref.header.retry-after.2">7.5.4</a>, <a href="#rfc.iref.h.9"><b>9.8</b></a>, <a href="#rfc.xref.header.retry-after.3">10.3</a></li> 3616 <li>Server <a href="#rfc.xref.header.server.1">3.3</a>, <a href="#rfc.iref.h.10"><b>9.9</b></a>, <a href="#rfc.xref.header.server.2">10.3</a>, <a href="#rfc.xref.header.server.3">11.1</a>, <a href="#rfc.xref.header.server.4">A</a></li> 3617 <li>User-Agent <a href="#rfc.xref.header.user-agent.1">3.2</a>, <a href="#rfc.iref.h.11"><b>9.10</b></a>, <a href="#rfc.xref.header.user-agent.2">10.3</a>, <a href="#rfc.xref.header.user-agent.3">11.1</a></li> 3615 3618 </ul> 3616 3619 </li> … … 3622 3625 </li> 3623 3626 <li><a id="rfc.index.L" href="#rfc.index.L"><b>L</b></a><ul> 3624 <li>Location header field <a href="#rfc.xref.header.location.1">3.3</a>, <a href="#rfc.xref.header.location.2">6.5</a>, <a href="#rfc.xref.header.location.3">7.3</a>, <a href="#rfc.iref.l.1"><b> 10.5</b></a>, <a href="#rfc.xref.header.location.4">11.3</a>, <a href="#rfc.xref.header.location.5">A</a></li>3627 <li>Location header field <a href="#rfc.xref.header.location.1">3.3</a>, <a href="#rfc.xref.header.location.2">6.5</a>, <a href="#rfc.xref.header.location.3">7.3</a>, <a href="#rfc.iref.l.1"><b>9.5</b></a>, <a href="#rfc.xref.header.location.4">10.3</a>, <a href="#rfc.xref.header.location.5">A</a></li> 3625 3628 </ul> 3626 3629 </li> 3627 3630 <li><a id="rfc.index.M" href="#rfc.index.M"><b>M</b></a><ul> 3628 <li>Max-Forwards header field <a href="#rfc.xref.header.max-forwards.1">3.2</a>, <a href="#rfc.xref.header.max-forwards.2">6.2</a>, <a href="#rfc.xref.header.max-forwards.3">6.8</a>, <a href="#rfc.iref.m.9"><b> 10.6</b></a>, <a href="#rfc.xref.header.max-forwards.4">11.3</a>, <a href="#rfc.xref.header.max-forwards.5">A</a></li>3631 <li>Max-Forwards header field <a href="#rfc.xref.header.max-forwards.1">3.2</a>, <a href="#rfc.xref.header.max-forwards.2">6.2</a>, <a href="#rfc.xref.header.max-forwards.3">6.8</a>, <a href="#rfc.iref.m.9"><b>9.6</b></a>, <a href="#rfc.xref.header.max-forwards.4">10.3</a>, <a href="#rfc.xref.header.max-forwards.5">A</a></li> 3629 3632 <li>Methods 3630 3633 <ul> 3631 <li>CONNECT <a href="#rfc.xref.CONNECT.1">2.1</a>, <a href="#rfc.iref.m.8"><b>6.9</b></a>, <a href="#rfc.xref.CONNECT.2">1 1.1</a>, <a href="#rfc.xref.CONNECT.3">A</a></li>3632 <li>DELETE <a href="#rfc.xref.DELETE.1">2.1</a>, <a href="#rfc.iref.m.6"><b>6.7</b></a>, <a href="#rfc.xref.DELETE.2">1 1.1</a></li>3633 <li>GET <a href="#rfc.xref.GET.1">2.1</a>, <a href="#rfc.iref.m.2"><b>6.3</b></a>, <a href="#rfc.xref.GET.2">1 1.1</a></li>3634 <li>HEAD <a href="#rfc.xref.HEAD.1">2.1</a>, <a href="#rfc.iref.m.3"><b>6.4</b></a>, <a href="#rfc.xref.HEAD.2">1 1.1</a></li>3635 <li>OPTIONS <a href="#rfc.xref.OPTIONS.1">2.1</a>, <a href="#rfc.iref.m.1"><b>6.2</b></a>, <a href="#rfc.xref.OPTIONS.2"> 10.6</a>, <a href="#rfc.xref.OPTIONS.3">11.1</a></li>3636 <li>POST <a href="#rfc.xref.POST.1">2.1</a>, <a href="#rfc.iref.m.4"><b>6.5</b></a>, <a href="#rfc.xref.POST.2">1 1.1</a>, <a href="#rfc.xref.POST.3">A</a></li>3637 <li>PUT <a href="#rfc.xref.PUT.1">2.1</a>, <a href="#rfc.iref.m.5"><b>6.6</b></a>, <a href="#rfc.xref.PUT.2">1 1.1</a>, <a href="#rfc.xref.PUT.3">A</a></li>3638 <li>TRACE <a href="#rfc.xref.TRACE.1">2.1</a>, <a href="#rfc.iref.m.7"><b>6.8</b></a>, <a href="#rfc.xref.TRACE.2"> 10.6</a>, <a href="#rfc.xref.TRACE.3">11.1</a>, <a href="#rfc.xref.TRACE.4">12.1</a></li>3634 <li>CONNECT <a href="#rfc.xref.CONNECT.1">2.1</a>, <a href="#rfc.iref.m.8"><b>6.9</b></a>, <a href="#rfc.xref.CONNECT.2">10.1</a>, <a href="#rfc.xref.CONNECT.3">A</a></li> 3635 <li>DELETE <a href="#rfc.xref.DELETE.1">2.1</a>, <a href="#rfc.iref.m.6"><b>6.7</b></a>, <a href="#rfc.xref.DELETE.2">10.1</a></li> 3636 <li>GET <a href="#rfc.xref.GET.1">2.1</a>, <a href="#rfc.iref.m.2"><b>6.3</b></a>, <a href="#rfc.xref.GET.2">10.1</a></li> 3637 <li>HEAD <a href="#rfc.xref.HEAD.1">2.1</a>, <a href="#rfc.iref.m.3"><b>6.4</b></a>, <a href="#rfc.xref.HEAD.2">10.1</a></li> 3638 <li>OPTIONS <a href="#rfc.xref.OPTIONS.1">2.1</a>, <a href="#rfc.iref.m.1"><b>6.2</b></a>, <a href="#rfc.xref.OPTIONS.2">9.6</a>, <a href="#rfc.xref.OPTIONS.3">10.1</a></li> 3639 <li>POST <a href="#rfc.xref.POST.1">2.1</a>, <a href="#rfc.iref.m.4"><b>6.5</b></a>, <a href="#rfc.xref.POST.2">10.1</a>, <a href="#rfc.xref.POST.3">A</a></li> 3640 <li>PUT <a href="#rfc.xref.PUT.1">2.1</a>, <a href="#rfc.iref.m.5"><b>6.6</b></a>, <a href="#rfc.xref.PUT.2">10.1</a>, <a href="#rfc.xref.PUT.3">A</a></li> 3641 <li>TRACE <a href="#rfc.xref.TRACE.1">2.1</a>, <a href="#rfc.iref.m.7"><b>6.8</b></a>, <a href="#rfc.xref.TRACE.2">9.6</a>, <a href="#rfc.xref.TRACE.3">10.1</a>, <a href="#rfc.xref.TRACE.4">11.1</a></li> 3639 3642 </ul> 3640 3643 </li> … … 3642 3645 </li> 3643 3646 <li><a id="rfc.index.O" href="#rfc.index.O"><b>O</b></a><ul> 3644 <li>OPTIONS method <a href="#rfc.xref.OPTIONS.1">2.1</a>, <a href="#rfc.iref.o.1"><b>6.2</b></a>, <a href="#rfc.xref.OPTIONS.2"> 10.6</a>, <a href="#rfc.xref.OPTIONS.3">11.1</a></li>3647 <li>OPTIONS method <a href="#rfc.xref.OPTIONS.1">2.1</a>, <a href="#rfc.iref.o.1"><b>6.2</b></a>, <a href="#rfc.xref.OPTIONS.2">9.6</a>, <a href="#rfc.xref.OPTIONS.3">10.1</a></li> 3645 3648 </ul> 3646 3649 </li> 3647 3650 <li><a id="rfc.index.P" href="#rfc.index.P"><b>P</b></a><ul> 3648 <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">3</a>, <a href="#rfc.xref.Part1.18">3.1</a>, <a href="#rfc.xref.Part1.19">3.1</a>, <a href="#rfc.xref.Part1.20">3.1</a>, <a href="#rfc.xref.Part1.21">3.1</a>, <a href="#rfc.xref.Part1.22">3.1</a>, <a href="#rfc.xref.Part1.23">3.2</a>, <a href="#rfc.xref.Part1.24">3.2</a>, <a href="#rfc.xref.Part1.25">3.3</a>, <a href="#rfc.xref.Part1.26">5</a>, <a href="#rfc.xref.Part1.27">5.1</a>, <a href="#rfc.xref.Part1.28">6.2</a>, <a href="#rfc.xref.Part1.29">6.8</a>, <a href="#rfc.xref.Part1.30">6.8</a>, <a href="#rfc.xref.Part1.31">6.9</a>, <a href="#rfc.xref.Part1.32">7.1.1</a>, <a href="#rfc.xref.Part1.33">7.1.2</a>, <a href="#rfc.xref.Part1.34">7.2.4</a>, <a href="#rfc.xref.Part1.35">7.2.6</a>, <a href="#rfc.xref.Part1.36">7.4.15</a>, <a href="#rfc.xref.Part1.37">7.5.6</a>, <a href="#rfc.xref.Part1.38"> 10.3</a>, <a href="#rfc.xref.Part1.39">10.9</a>, <a href="#rfc.xref.Part1.40">10.9</a>, <a href="#rfc.xref.Part1.41">10.10</a>, <a href="#rfc.xref.Part1.42">13</a>, <a href="#Part1"><b>14.1</b></a>, <a href="#rfc.xref.Part1.43">A</a><ul>3651 <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">3</a>, <a href="#rfc.xref.Part1.18">3.1</a>, <a href="#rfc.xref.Part1.19">3.1</a>, <a href="#rfc.xref.Part1.20">3.1</a>, <a href="#rfc.xref.Part1.21">3.1</a>, <a href="#rfc.xref.Part1.22">3.1</a>, <a href="#rfc.xref.Part1.23">3.2</a>, <a href="#rfc.xref.Part1.24">3.2</a>, <a href="#rfc.xref.Part1.25">3.3</a>, <a href="#rfc.xref.Part1.26">5</a>, <a href="#rfc.xref.Part1.27">5.1</a>, <a href="#rfc.xref.Part1.28">6.2</a>, <a href="#rfc.xref.Part1.29">6.8</a>, <a href="#rfc.xref.Part1.30">6.8</a>, <a href="#rfc.xref.Part1.31">6.9</a>, <a href="#rfc.xref.Part1.32">7.1.1</a>, <a href="#rfc.xref.Part1.33">7.1.2</a>, <a href="#rfc.xref.Part1.34">7.2.4</a>, <a href="#rfc.xref.Part1.35">7.2.6</a>, <a href="#rfc.xref.Part1.36">7.4.15</a>, <a href="#rfc.xref.Part1.37">7.5.6</a>, <a href="#rfc.xref.Part1.38">9.3</a>, <a href="#rfc.xref.Part1.39">9.9</a>, <a href="#rfc.xref.Part1.40">9.9</a>, <a href="#rfc.xref.Part1.41">9.10</a>, <a href="#rfc.xref.Part1.42">12</a>, <a href="#Part1"><b>13.1</b></a>, <a href="#rfc.xref.Part1.43">A</a><ul> 3649 3652 <li><em>Section 1.2</em> <a href="#rfc.xref.Part1.3">1.2</a></li> 3650 3653 <li><em>Section 2</em> <a href="#rfc.xref.Part1.2">1.1</a></li> … … 3653 3656 <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> 3654 3657 <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> 3655 <li><em>Section 3.2</em> <a href="#rfc.xref.Part1.17">3</a>, <a href="#rfc.xref.Part1.20">3.1</a>, <a href="#rfc.xref.Part1.39"> 10.9</a>, <a href="#rfc.xref.Part1.41">10.10</a></li>3658 <li><em>Section 3.2</em> <a href="#rfc.xref.Part1.17">3</a>, <a href="#rfc.xref.Part1.20">3.1</a>, <a href="#rfc.xref.Part1.39">9.9</a>, <a href="#rfc.xref.Part1.41">9.10</a></li> 3656 3659 <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.19">3.1</a></li> 3657 3660 <li><em>Section 3.2.5</em> <a href="#rfc.xref.Part1.18">3.1</a></li> … … 3663 3666 <li><em>Section 5.5</em> <a href="#rfc.xref.Part1.15">2</a>, <a href="#rfc.xref.Part1.25">3.3</a>, <a href="#rfc.xref.Part1.27">5.1</a></li> 3664 3667 <li><em>Section 6.1</em> <a href="#rfc.xref.Part1.21">3.1</a></li> 3665 <li><em>Section 6.2</em> <a href="#rfc.xref.Part1.29">6.8</a>, <a href="#rfc.xref.Part1.40"> 10.9</a>, <a href="#rfc.xref.Part1.43">A</a></li>3666 <li><em>Section 6.4.3</em> <a href="#rfc.xref.Part1.32">7.1.1</a>, <a href="#rfc.xref.Part1.38"> 10.3</a></li>3668 <li><em>Section 6.2</em> <a href="#rfc.xref.Part1.29">6.8</a>, <a href="#rfc.xref.Part1.40">9.9</a>, <a href="#rfc.xref.Part1.43">A</a></li> 3669 <li><em>Section 6.4.3</em> <a href="#rfc.xref.Part1.32">7.1.1</a>, <a href="#rfc.xref.Part1.38">9.3</a></li> 3667 3670 <li><em>Section 6.5</em> <a href="#rfc.xref.Part1.33">7.1.2</a>, <a href="#rfc.xref.Part1.36">7.4.15</a></li> 3668 3671 <li><em>Section 7.3.1</em> <a href="#rfc.xref.Part1.30">6.8</a></li> 3669 <li><em>Section 9</em> <a href="#rfc.xref.Part1.42">1 3</a></li>3672 <li><em>Section 9</em> <a href="#rfc.xref.Part1.42">12</a></li> 3670 3673 </ul> 3671 3674 </li> 3672 <li><em>Part3</em> <a href="#rfc.xref.Part3.1">3.1</a>, <a href="#rfc.xref.Part3.2">3.1</a>, <a href="#rfc.xref.Part3.3">3.2</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">5</a>, <a href="#rfc.xref.Part3.8">6.5</a>, <a href="#rfc.xref.Part3.9">7</a>, <a href="#rfc.xref.Part3.10">7.3</a>, <a href="#rfc.xref.Part3.11">7.3.1</a>, <a href="#rfc.xref.Part3.12">7.4.6</a>, <a href="#rfc.xref.Part3.13"> 10.5</a>, <a href="#Part3"><b>14.1</b></a><ul>3675 <li><em>Part3</em> <a href="#rfc.xref.Part3.1">3.1</a>, <a href="#rfc.xref.Part3.2">3.1</a>, <a href="#rfc.xref.Part3.3">3.2</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">5</a>, <a href="#rfc.xref.Part3.8">6.5</a>, <a href="#rfc.xref.Part3.9">7</a>, <a href="#rfc.xref.Part3.10">7.3</a>, <a href="#rfc.xref.Part3.11">7.3.1</a>, <a href="#rfc.xref.Part3.12">7.4.6</a>, <a href="#rfc.xref.Part3.13">9.5</a>, <a href="#Part3"><b>13.1</b></a><ul> 3673 3676 <li><em>Section 2.3</em> <a href="#rfc.xref.Part3.2">3.1</a></li> 3674 3677 <li><em>Section 5</em> <a href="#rfc.xref.Part3.11">7.3.1</a></li> … … 3679 3682 <li><em>Section 6.3</em> <a href="#rfc.xref.Part3.5">3.2</a></li> 3680 3683 <li><em>Section 6.4</em> <a href="#rfc.xref.Part3.6">3.2</a></li> 3681 <li><em>Section 6.7</em> <a href="#rfc.xref.Part3.8">6.5</a>, <a href="#rfc.xref.Part3.13"> 10.5</a></li>3684 <li><em>Section 6.7</em> <a href="#rfc.xref.Part3.8">6.5</a>, <a href="#rfc.xref.Part3.13">9.5</a></li> 3682 3685 <li><em>Section 6.8</em> <a href="#rfc.xref.Part3.1">3.1</a>, <a href="#rfc.xref.Part3.9">7</a></li> 3683 3686 </ul> 3684 3687 </li> 3685 <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">7.2.2</a>, <a href="#rfc.xref.Part4.10">7.3</a>, <a href="#Part4"><b>1 4.1</b></a>, <a href="#rfc.xref.Part4.11">C.2</a><ul>3688 <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">7.2.2</a>, <a href="#rfc.xref.Part4.10">7.3</a>, <a href="#Part4"><b>13.1</b></a>, <a href="#rfc.xref.Part4.11">C.2</a><ul> 3686 3689 <li><em>Section 2.3</em> <a href="#rfc.xref.Part4.5">3.3</a>, <a href="#rfc.xref.Part4.9">7.2.2</a></li> 3687 3690 <li><em>Section 3.1</em> <a href="#rfc.xref.Part4.1">3.2</a></li> … … 3694 3697 </ul> 3695 3698 </li> 3696 <li><em>Part5</em> <a href="#rfc.xref.Part5.1">3.2</a>, <a href="#rfc.xref.Part5.2">3.2</a>, <a href="#rfc.xref.Part5.3">3.3</a>, <a href="#rfc.xref.Part5.4">4.1</a>, <a href="#rfc.xref.Part5.5">4.1</a>, <a href="#rfc.xref.Part5.6">4.1</a>, <a href="#rfc.xref.Part5.7">6.3</a>, <a href="#Part5"><b>1 4.1</b></a><ul>3699 <li><em>Part5</em> <a href="#rfc.xref.Part5.1">3.2</a>, <a href="#rfc.xref.Part5.2">3.2</a>, <a href="#rfc.xref.Part5.3">3.3</a>, <a href="#rfc.xref.Part5.4">4.1</a>, <a href="#rfc.xref.Part5.5">4.1</a>, <a href="#rfc.xref.Part5.6">4.1</a>, <a href="#rfc.xref.Part5.7">6.3</a>, <a href="#Part5"><b>13.1</b></a><ul> 3697 3700 <li><em>Section 3</em> <a href="#rfc.xref.Part5.4">4.1</a></li> 3698 3701 <li><em>Section 3.1</em> <a href="#rfc.xref.Part5.5">4.1</a></li> … … 3703 3706 </ul> 3704 3707 </li> 3705 <li><em>Part6</em> <a href="#rfc.xref.Part6.1">2.2.1</a>, <a href="#rfc.xref.Part6.2">3.1</a>, <a href="#rfc.xref.Part6.3">3.3</a>, <a href="#rfc.xref.Part6.4">3.3</a>, <a href="#rfc.xref.Part6.5">4.2.1</a>, <a href="#rfc.xref.Part6.6">6.3</a>, <a href="#rfc.xref.Part6.7">6.4</a>, <a href="#rfc.xref.Part6.8">6.5</a>, <a href="#rfc.xref.Part6.9">6.6</a>, <a href="#rfc.xref.Part6.10">6.7</a>, <a href="#rfc.xref.Part6.11">7.2.1</a>, <a href="#rfc.xref.Part6.12">7.2.4</a>, <a href="#rfc.xref.Part6.13">7.2.4</a>, <a href="#rfc.xref.Part6.14">7.2.4</a>, <a href="#rfc.xref.Part6.15">7.3.1</a>, <a href="#rfc.xref.Part6.16">7.3.2</a>, <a href="#rfc.xref.Part6.17">7.4.9</a>, <a href="#Part6"><b>1 4.1</b></a><ul>3708 <li><em>Part6</em> <a href="#rfc.xref.Part6.1">2.2.1</a>, <a href="#rfc.xref.Part6.2">3.1</a>, <a href="#rfc.xref.Part6.3">3.3</a>, <a href="#rfc.xref.Part6.4">3.3</a>, <a href="#rfc.xref.Part6.5">4.2.1</a>, <a href="#rfc.xref.Part6.6">6.3</a>, <a href="#rfc.xref.Part6.7">6.4</a>, <a href="#rfc.xref.Part6.8">6.5</a>, <a href="#rfc.xref.Part6.9">6.6</a>, <a href="#rfc.xref.Part6.10">6.7</a>, <a href="#rfc.xref.Part6.11">7.2.1</a>, <a href="#rfc.xref.Part6.12">7.2.4</a>, <a href="#rfc.xref.Part6.13">7.2.4</a>, <a href="#rfc.xref.Part6.14">7.2.4</a>, <a href="#rfc.xref.Part6.15">7.3.1</a>, <a href="#rfc.xref.Part6.16">7.3.2</a>, <a href="#rfc.xref.Part6.17">7.4.9</a>, <a href="#Part6"><b>13.1</b></a><ul> 3706 3709 <li><em>Section 2.3.1</em> <a href="#rfc.xref.Part6.8">6.5</a></li> 3707 3710 <li><em>Section 2.3.1.1</em> <a href="#rfc.xref.Part6.11">7.2.1</a>, <a href="#rfc.xref.Part6.14">7.2.4</a>, <a href="#rfc.xref.Part6.15">7.3.1</a>, <a href="#rfc.xref.Part6.16">7.3.2</a>, <a href="#rfc.xref.Part6.17">7.4.9</a></li> … … 3714 3717 </ul> 3715 3718 </li> 3716 <li><em>Part7</em> <a href="#rfc.xref.Part7.1">3.2</a>, <a href="#rfc.xref.Part7.2">3.2</a>, <a href="#rfc.xref.Part7.3">3.3</a>, <a href="#rfc.xref.Part7.4">3.3</a>, <a href="#rfc.xref.Part7.5">4.1</a>, <a href="#rfc.xref.Part7.6">4.1</a>, <a href="#rfc.xref.Part7.7">4.1</a>, <a href="#Part7"><b>1 4.1</b></a><ul>3719 <li><em>Part7</em> <a href="#rfc.xref.Part7.1">3.2</a>, <a href="#rfc.xref.Part7.2">3.2</a>, <a href="#rfc.xref.Part7.3">3.3</a>, <a href="#rfc.xref.Part7.4">3.3</a>, <a href="#rfc.xref.Part7.5">4.1</a>, <a href="#rfc.xref.Part7.6">4.1</a>, <a href="#rfc.xref.Part7.7">4.1</a>, <a href="#Part7"><b>13.1</b></a><ul> 3717 3720 <li><em>Section 3</em> <a href="#rfc.xref.Part7.5">4.1</a></li> 3718 3721 <li><em>Section 3.1</em> <a href="#rfc.xref.Part7.6">4.1</a></li> … … 3724 3727 </ul> 3725 3728 </li> 3726 <li>POST method <a href="#rfc.xref.POST.1">2.1</a>, <a href="#rfc.iref.p.1"><b>6.5</b></a>, <a href="#rfc.xref.POST.2">1 1.1</a>, <a href="#rfc.xref.POST.3">A</a></li>3727 <li>PUT method <a href="#rfc.xref.PUT.1">2.1</a>, <a href="#rfc.iref.p.2"><b>6.6</b></a>, <a href="#rfc.xref.PUT.2">1 1.1</a>, <a href="#rfc.xref.PUT.3">A</a></li>3729 <li>POST method <a href="#rfc.xref.POST.1">2.1</a>, <a href="#rfc.iref.p.1"><b>6.5</b></a>, <a href="#rfc.xref.POST.2">10.1</a>, <a href="#rfc.xref.POST.3">A</a></li> 3730 <li>PUT method <a href="#rfc.xref.PUT.1">2.1</a>, <a href="#rfc.iref.p.2"><b>6.6</b></a>, <a href="#rfc.xref.PUT.2">10.1</a>, <a href="#rfc.xref.PUT.3">A</a></li> 3728 3731 </ul> 3729 3732 </li> 3730 3733 <li><a id="rfc.index.R" href="#rfc.index.R"><b>R</b></a><ul> 3731 <li>Referer header field <a href="#rfc.xref.header.referer.1">3.2</a>, <a href="#rfc.iref.r.1"><b> 10.7</b></a>, <a href="#rfc.xref.header.referer.2">11.3</a>, <a href="#rfc.xref.header.referer.3">A</a></li>3732 <li>Retry-After header field <a href="#rfc.xref.header.retry-after.1">3.3</a>, <a href="#rfc.xref.header.retry-after.2">7.5.4</a>, <a href="#rfc.iref.r.2"><b> 10.8</b></a>, <a href="#rfc.xref.header.retry-after.3">11.3</a></li>3733 <li><em>RFC1123</em> <a href="#rfc.xref.RFC1123.1">8 </a>, <a href="#rfc.xref.RFC1123.2">8</a>, <a href="#RFC1123"><b>14.2</b></a><ul>3734 <li><em>Section 5.2.14</em> <a href="#rfc.xref.RFC1123.2">8 </a></li>3734 <li>Referer header field <a href="#rfc.xref.header.referer.1">3.2</a>, <a href="#rfc.iref.r.1"><b>9.7</b></a>, <a href="#rfc.xref.header.referer.2">10.3</a>, <a href="#rfc.xref.header.referer.3">A</a></li> 3735 <li>Retry-After header field <a href="#rfc.xref.header.retry-after.1">3.3</a>, <a href="#rfc.xref.header.retry-after.2">7.5.4</a>, <a href="#rfc.iref.r.2"><b>9.8</b></a>, <a href="#rfc.xref.header.retry-after.3">10.3</a></li> 3736 <li><em>RFC1123</em> <a href="#rfc.xref.RFC1123.1">8.1</a>, <a href="#rfc.xref.RFC1123.2">8.1</a>, <a href="#RFC1123"><b>13.2</b></a><ul> 3737 <li><em>Section 5.2.14</em> <a href="#rfc.xref.RFC1123.2">8.1</a></li> 3735 3738 </ul> 3736 3739 </li> 3737 <li><em>RFC1945</em> <a href="#rfc.xref.RFC1945.1">7.3</a>, <a href="#RFC1945"><b>1 4.2</b></a><ul>3740 <li><em>RFC1945</em> <a href="#rfc.xref.RFC1945.1">7.3</a>, <a href="#RFC1945"><b>13.2</b></a><ul> 3738 3741 <li><em>Section 9.3</em> <a href="#rfc.xref.RFC1945.1">7.3</a></li> 3739 3742 </ul> 3740 3743 </li> 3741 <li><em>RFC2068</em> <a href="#rfc.xref.RFC2068.1">7.3</a>, <a href="#rfc.xref.RFC2068.2">7.3</a>, <a href="#RFC2068"><b>1 4.2</b></a><ul>3744 <li><em>RFC2068</em> <a href="#rfc.xref.RFC2068.1">7.3</a>, <a href="#rfc.xref.RFC2068.2">7.3</a>, <a href="#RFC2068"><b>13.2</b></a><ul> 3742 3745 <li><em>Section 10.3</em> <a href="#rfc.xref.RFC2068.2">7.3</a></li> 3743 3746 <li><em>Section 10.3.4</em> <a href="#rfc.xref.RFC2068.1">7.3</a></li> 3744 3747 </ul> 3745 3748 </li> 3746 <li><em>RFC2119</em> <a href="#rfc.xref.RFC2119.1">1.1</a>, <a href="#RFC2119"><b>1 4.1</b></a></li>3747 <li><em>RFC2616</em> <a href="#rfc.xref.RFC2616.1">1</a>, <a href="#rfc.xref.RFC2616.2">7.3</a>, <a href="#RFC2616"><b>1 4.2</b></a>, <a href="#rfc.xref.RFC2616.3">C.1</a><ul>3749 <li><em>RFC2119</em> <a href="#rfc.xref.RFC2119.1">1.1</a>, <a href="#RFC2119"><b>13.1</b></a></li> 3750 <li><em>RFC2616</em> <a href="#rfc.xref.RFC2616.1">1</a>, <a href="#rfc.xref.RFC2616.2">7.3</a>, <a href="#RFC2616"><b>13.2</b></a>, <a href="#rfc.xref.RFC2616.3">C.1</a><ul> 3748 3751 <li><em>Section 10.3.8</em> <a href="#rfc.xref.RFC2616.2">7.3</a></li> 3749 3752 </ul> 3750 3753 </li> 3751 <li><em>RFC2817</em> <a href="#rfc.xref.RFC2817.1">1 1.2</a>, <a href="#RFC2817"><b>14.2</b></a>, <a href="#rfc.xref.RFC2817.2">A</a>, <a href="#rfc.xref.RFC2817.3">A</a>, <a href="#rfc.xref.RFC2817.4">A</a><ul>3752 <li><em>Section 7.1</em> <a href="#rfc.xref.RFC2817.1">1 1.2</a>, <a href="#rfc.xref.RFC2817.2">A</a></li>3754 <li><em>RFC2817</em> <a href="#rfc.xref.RFC2817.1">10.2</a>, <a href="#RFC2817"><b>13.2</b></a>, <a href="#rfc.xref.RFC2817.2">A</a>, <a href="#rfc.xref.RFC2817.3">A</a>, <a href="#rfc.xref.RFC2817.4">A</a><ul> 3755 <li><em>Section 7.1</em> <a href="#rfc.xref.RFC2817.1">10.2</a>, <a href="#rfc.xref.RFC2817.2">A</a></li> 3753 3756 </ul> 3754 3757 </li> 3755 <li><em>RFC3864</em> <a href="#rfc.xref.RFC3864.1">3.1</a>, <a href="#rfc.xref.RFC3864.2">3.1</a>, <a href="#rfc.xref.RFC3864.3">1 1.3</a>, <a href="#RFC3864"><b>14.2</b></a><ul>3758 <li><em>RFC3864</em> <a href="#rfc.xref.RFC3864.1">3.1</a>, <a href="#rfc.xref.RFC3864.2">3.1</a>, <a href="#rfc.xref.RFC3864.3">10.3</a>, <a href="#RFC3864"><b>13.2</b></a><ul> 3756 3759 <li><em>Section 4.1</em> <a href="#rfc.xref.RFC3864.2">3.1</a></li> 3757 3760 </ul> 3758 3761 </li> 3759 <li><em>RFC3986</em> <a href="#rfc.xref.RFC3986.1"> 10.5</a>, <a href="#rfc.xref.RFC3986.2">10.5</a>, <a href="#RFC3986"><b>14.1</b></a><ul>3760 <li><em>Section 4.2</em> <a href="#rfc.xref.RFC3986.1"> 10.5</a></li>3761 <li><em>Section 5</em> <a href="#rfc.xref.RFC3986.2"> 10.5</a></li>3762 <li><em>RFC3986</em> <a href="#rfc.xref.RFC3986.1">9.5</a>, <a href="#rfc.xref.RFC3986.2">9.5</a>, <a href="#RFC3986"><b>13.1</b></a><ul> 3763 <li><em>Section 4.2</em> <a href="#rfc.xref.RFC3986.1">9.5</a></li> 3764 <li><em>Section 5</em> <a href="#rfc.xref.RFC3986.2">9.5</a></li> 3762 3765 </ul> 3763 3766 </li> 3764 <li><em>RFC5226</em> <a href="#rfc.xref.RFC5226.1">2.2</a>, <a href="#rfc.xref.RFC5226.2">4.2</a>, <a href="#RFC5226"><b>1 4.2</b></a><ul>3767 <li><em>RFC5226</em> <a href="#rfc.xref.RFC5226.1">2.2</a>, <a href="#rfc.xref.RFC5226.2">4.2</a>, <a href="#RFC5226"><b>13.2</b></a><ul> 3765 3768 <li><em>Section 4.1</em> <a href="#rfc.xref.RFC5226.1">2.2</a>, <a href="#rfc.xref.RFC5226.2">4.2</a></li> 3766 3769 </ul> 3767 3770 </li> 3768 <li><em>RFC5234</em> <a href="#rfc.xref.RFC5234.1">1.2</a>, <a href="#rfc.xref.RFC5234.2">1.2</a>, <a href="#rfc.xref.RFC5234.3">3.1</a>, <a href="#RFC5234"><b>1 4.1</b></a><ul>3771 <li><em>RFC5234</em> <a href="#rfc.xref.RFC5234.1">1.2</a>, <a href="#rfc.xref.RFC5234.2">1.2</a>, <a href="#rfc.xref.RFC5234.3">3.1</a>, <a href="#RFC5234"><b>13.1</b></a><ul> 3769 3772 <li><em>Appendix B.1</em> <a href="#rfc.xref.RFC5234.2">1.2</a></li> 3770 3773 </ul> 3771 3774 </li> 3772 <li><em>RFC5322</em> <a href="#rfc.xref.RFC5322.1">8 </a>, <a href="#rfc.xref.RFC5322.2">10.2</a>, <a href="#rfc.xref.RFC5322.3">10.4</a>, <a href="#rfc.xref.RFC5322.4">10.4</a>, <a href="#RFC5322"><b>14.2</b></a><ul>3773 <li><em>Section 3.3</em> <a href="#rfc.xref.RFC5322.1">8 </a></li>3774 <li><em>Section 3.4</em> <a href="#rfc.xref.RFC5322.3"> 10.4</a>, <a href="#rfc.xref.RFC5322.4">10.4</a></li>3775 <li><em>Section 3.6.1</em> <a href="#rfc.xref.RFC5322.2"> 10.2</a></li>3775 <li><em>RFC5322</em> <a href="#rfc.xref.RFC5322.1">8.1</a>, <a href="#rfc.xref.RFC5322.2">9.2</a>, <a href="#rfc.xref.RFC5322.3">9.4</a>, <a href="#rfc.xref.RFC5322.4">9.4</a>, <a href="#RFC5322"><b>13.2</b></a><ul> 3776 <li><em>Section 3.3</em> <a href="#rfc.xref.RFC5322.1">8.1</a></li> 3777 <li><em>Section 3.4</em> <a href="#rfc.xref.RFC5322.3">9.4</a>, <a href="#rfc.xref.RFC5322.4">9.4</a></li> 3778 <li><em>Section 3.6.1</em> <a href="#rfc.xref.RFC5322.2">9.2</a></li> 3776 3779 </ul> 3777 3780 </li> 3778 <li><em>RFC5789</em> <a href="#rfc.xref.RFC5789.1">6.6</a>, <a href="#RFC5789"><b>1 4.2</b></a></li>3779 <li><em>RFC5987</em> <a href="#rfc.xref.RFC5987.1">3.1</a>, <a href="#RFC5987"><b>1 4.2</b></a></li>3781 <li><em>RFC5789</em> <a href="#rfc.xref.RFC5789.1">6.6</a>, <a href="#RFC5789"><b>13.2</b></a></li> 3782 <li><em>RFC5987</em> <a href="#rfc.xref.RFC5987.1">3.1</a>, <a href="#RFC5987"><b>13.2</b></a></li> 3780 3783 </ul> 3781 3784 </li> 3782 3785 <li><a id="rfc.index.S" href="#rfc.index.S"><b>S</b></a><ul> 3783 3786 <li>Safe Methods <a href="#rfc.iref.s.1"><b>6.1.1</b></a></li> 3784 <li>Server header field <a href="#rfc.xref.header.server.1">3.3</a>, <a href="#rfc.iref.s.38"><b> 10.9</b></a>, <a href="#rfc.xref.header.server.2">11.3</a>, <a href="#rfc.xref.header.server.3">12.1</a>, <a href="#rfc.xref.header.server.4">A</a></li>3787 <li>Server header field <a href="#rfc.xref.header.server.1">3.3</a>, <a href="#rfc.iref.s.38"><b>9.9</b></a>, <a href="#rfc.xref.header.server.2">10.3</a>, <a href="#rfc.xref.header.server.3">11.1</a>, <a href="#rfc.xref.header.server.4">A</a></li> 3785 3788 <li>Status Codes 3786 3789 <ul> 3787 <li>100 Continue <a href="#rfc.xref.status.100.1">4.1</a>, <a href="#rfc.iref.s.2"><b>7.1.1</b></a>, <a href="#rfc.xref.status.100.2">1 1.2</a></li>3788 <li>101 Switching Protocols <a href="#rfc.xref.status.101.1">4.1</a>, <a href="#rfc.iref.s.3"><b>7.1.2</b></a>, <a href="#rfc.xref.status.101.2">1 1.2</a></li>3789 <li>200 OK <a href="#rfc.xref.status.200.1">4.1</a>, <a href="#rfc.iref.s.4"><b>7.2.1</b></a>, <a href="#rfc.xref.status.200.2">1 1.2</a></li>3790 <li>201 Created <a href="#rfc.xref.status.201.1">4.1</a>, <a href="#rfc.iref.s.5"><b>7.2.2</b></a>, <a href="#rfc.xref.status.201.2">1 1.2</a></li>3791 <li>202 Accepted <a href="#rfc.xref.status.202.1">4.1</a>, <a href="#rfc.iref.s.6"><b>7.2.3</b></a>, <a href="#rfc.xref.status.202.2">1 1.2</a></li>3792 <li>203 Non-Authoritative Information <a href="#rfc.xref.status.203.1">4.1</a>, <a href="#rfc.iref.s.7"><b>7.2.4</b></a>, <a href="#rfc.xref.status.203.2">1 1.2</a>, <a href="#rfc.xref.status.203.3">A</a></li>3793 <li>204 No Content <a href="#rfc.xref.status.204.1">4.1</a>, <a href="#rfc.iref.s.8"><b>7.2.5</b></a>, <a href="#rfc.xref.status.204.2">1 1.2</a></li>3794 <li>205 Reset Content <a href="#rfc.xref.status.205.1">4.1</a>, <a href="#rfc.iref.s.9"><b>7.2.6</b></a>, <a href="#rfc.xref.status.205.2">1 1.2</a></li>3795 <li>300 Multiple Choices <a href="#rfc.xref.status.300.1">4.1</a>, <a href="#rfc.iref.s.10"><b>7.3.1</b></a>, <a href="#rfc.xref.status.300.2">1 1.2</a></li>3796 <li>301 Moved Permanently <a href="#rfc.xref.status.301.1">4.1</a>, <a href="#rfc.iref.s.11"><b>7.3.2</b></a>, <a href="#rfc.xref.status.301.2">1 1.2</a>, <a href="#rfc.xref.status.301.3">A</a></li>3797 <li>302 Found <a href="#rfc.xref.status.302.1">4.1</a>, <a href="#rfc.iref.s.12"><b>7.3.3</b></a>, <a href="#rfc.xref.status.302.2">1 1.2</a>, <a href="#rfc.xref.status.302.3">A</a></li>3798 <li>303 See Other <a href="#rfc.xref.status.303.1">4.1</a>, <a href="#rfc.iref.s.13"><b>7.3.4</b></a>, <a href="#rfc.xref.status.303.2">1 1.2</a></li>3799 <li>305 Use Proxy <a href="#rfc.xref.status.305.1">4.1</a>, <a href="#rfc.iref.s.14"><b>7.3.5</b></a>, <a href="#rfc.xref.status.305.2">1 1.2</a>, <a href="#rfc.xref.status.305.3">A</a></li>3800 <li>306 (Unused) <a href="#rfc.iref.s.15"><b>7.3.6</b></a>, <a href="#rfc.xref.status.306.1">1 1.2</a></li>3801 <li>307 Temporary Redirect <a href="#rfc.xref.status.307.1">4.1</a>, <a href="#rfc.iref.s.16"><b>7.3.7</b></a>, <a href="#rfc.xref.status.307.2">1 1.2</a>, <a href="#rfc.xref.status.307.3">A</a></li>3802 <li>400 Bad Request <a href="#rfc.xref.status.400.1">4.1</a>, <a href="#rfc.iref.s.17"><b>7.4.1</b></a>, <a href="#rfc.xref.status.400.2">1 1.2</a></li>3803 <li>402 Payment Required <a href="#rfc.xref.status.402.1">4.1</a>, <a href="#rfc.iref.s.18"><b>7.4.2</b></a>, <a href="#rfc.xref.status.402.2">1 1.2</a></li>3804 <li>403 Forbidden <a href="#rfc.xref.status.403.1">4.1</a>, <a href="#rfc.iref.s.19"><b>7.4.3</b></a>, <a href="#rfc.xref.status.403.2">1 1.2</a></li>3805 <li>404 Not Found <a href="#rfc.xref.status.404.1">4.1</a>, <a href="#rfc.iref.s.20"><b>7.4.4</b></a>, <a href="#rfc.xref.status.404.2">1 1.2</a></li>3806 <li>405 Method Not Allowed <a href="#rfc.xref.status.405.1">4.1</a>, <a href="#rfc.iref.s.21"><b>7.4.5</b></a>, <a href="#rfc.xref.status.405.2">1 1.2</a></li>3807 <li>406 Not Acceptable <a href="#rfc.xref.status.406.1">4.1</a>, <a href="#rfc.iref.s.22"><b>7.4.6</b></a>, <a href="#rfc.xref.status.406.2">1 1.2</a></li>3808 <li>408 Request Timeout <a href="#rfc.xref.status.408.1">4.1</a>, <a href="#rfc.iref.s.23"><b>7.4.7</b></a>, <a href="#rfc.xref.status.408.2">1 1.2</a></li>3809 <li>409 Conflict <a href="#rfc.xref.status.409.1">4.1</a>, <a href="#rfc.iref.s.24"><b>7.4.8</b></a>, <a href="#rfc.xref.status.409.2">1 1.2</a></li>3810 <li>410 Gone <a href="#rfc.xref.status.410.1">4.1</a>, <a href="#rfc.iref.s.25"><b>7.4.9</b></a>, <a href="#rfc.xref.status.410.2">1 1.2</a></li>3811 <li>411 Length Required <a href="#rfc.xref.status.411.1">4.1</a>, <a href="#rfc.iref.s.26"><b>7.4.10</b></a>, <a href="#rfc.xref.status.411.2">1 1.2</a></li>3812 <li>413 Request Representation Too Large <a href="#rfc.xref.status.413.1">4.1</a>, <a href="#rfc.iref.s.27"><b>7.4.11</b></a>, <a href="#rfc.xref.status.413.2">1 1.2</a></li>3813 <li>414 URI Too Long <a href="#rfc.xref.status.414.1">4.1</a>, <a href="#rfc.iref.s.28"><b>7.4.12</b></a>, <a href="#rfc.xref.status.414.2">1 1.2</a></li>3814 <li>415 Unsupported Media Type <a href="#rfc.xref.status.415.1">4.1</a>, <a href="#rfc.iref.s.29"><b>7.4.13</b></a>, <a href="#rfc.xref.status.415.2">1 1.2</a></li>3815 <li>417 Expectation Failed <a href="#rfc.xref.status.417.1">4.1</a>, <a href="#rfc.iref.s.30"><b>7.4.14</b></a>, <a href="#rfc.xref.status.417.2">1 1.2</a></li>3816 <li>426 Upgrade Required <a href="#rfc.xref.status.426.1">4.1</a>, <a href="#rfc.iref.s.31"><b>7.4.15</b></a>, <a href="#rfc.xref.status.426.2">1 1.2</a>, <a href="#rfc.xref.status.426.3">A</a></li>3817 <li>500 Internal Server Error <a href="#rfc.xref.status.500.1">4.1</a>, <a href="#rfc.iref.s.32"><b>7.5.1</b></a>, <a href="#rfc.xref.status.500.2">1 1.2</a></li>3818 <li>501 Not Implemented <a href="#rfc.xref.status.501.1">4.1</a>, <a href="#rfc.iref.s.33"><b>7.5.2</b></a>, <a href="#rfc.xref.status.501.2">1 1.2</a></li>3819 <li>502 Bad Gateway <a href="#rfc.xref.status.502.1">4.1</a>, <a href="#rfc.iref.s.34"><b>7.5.3</b></a>, <a href="#rfc.xref.status.502.2">1 1.2</a></li>3820 <li>503 Service Unavailable <a href="#rfc.xref.status.503.1">4.1</a>, <a href="#rfc.iref.s.35"><b>7.5.4</b></a>, <a href="#rfc.xref.status.503.2">1 1.2</a></li>3821 <li>504 Gateway Timeout <a href="#rfc.xref.status.504.1">4.1</a>, <a href="#rfc.iref.s.36"><b>7.5.5</b></a>, <a href="#rfc.xref.status.504.2">1 1.2</a></li>3822 <li>505 HTTP Version Not Supported <a href="#rfc.xref.status.505.1">4.1</a>, <a href="#rfc.iref.s.37"><b>7.5.6</b></a>, <a href="#rfc.xref.status.505.2">1 1.2</a></li>3790 <li>100 Continue <a href="#rfc.xref.status.100.1">4.1</a>, <a href="#rfc.iref.s.2"><b>7.1.1</b></a>, <a href="#rfc.xref.status.100.2">10.2</a></li> 3791 <li>101 Switching Protocols <a href="#rfc.xref.status.101.1">4.1</a>, <a href="#rfc.iref.s.3"><b>7.1.2</b></a>, <a href="#rfc.xref.status.101.2">10.2</a></li> 3792 <li>200 OK <a href="#rfc.xref.status.200.1">4.1</a>, <a href="#rfc.iref.s.4"><b>7.2.1</b></a>, <a href="#rfc.xref.status.200.2">10.2</a></li> 3793 <li>201 Created <a href="#rfc.xref.status.201.1">4.1</a>, <a href="#rfc.iref.s.5"><b>7.2.2</b></a>, <a href="#rfc.xref.status.201.2">10.2</a></li> 3794 <li>202 Accepted <a href="#rfc.xref.status.202.1">4.1</a>, <a href="#rfc.iref.s.6"><b>7.2.3</b></a>, <a href="#rfc.xref.status.202.2">10.2</a></li> 3795 <li>203 Non-Authoritative Information <a href="#rfc.xref.status.203.1">4.1</a>, <a href="#rfc.iref.s.7"><b>7.2.4</b></a>, <a href="#rfc.xref.status.203.2">10.2</a>, <a href="#rfc.xref.status.203.3">A</a></li> 3796 <li>204 No Content <a href="#rfc.xref.status.204.1">4.1</a>, <a href="#rfc.iref.s.8"><b>7.2.5</b></a>, <a href="#rfc.xref.status.204.2">10.2</a></li> 3797 <li>205 Reset Content <a href="#rfc.xref.status.205.1">4.1</a>, <a href="#rfc.iref.s.9"><b>7.2.6</b></a>, <a href="#rfc.xref.status.205.2">10.2</a></li> 3798 <li>300 Multiple Choices <a href="#rfc.xref.status.300.1">4.1</a>, <a href="#rfc.iref.s.10"><b>7.3.1</b></a>, <a href="#rfc.xref.status.300.2">10.2</a></li> 3799 <li>301 Moved Permanently <a href="#rfc.xref.status.301.1">4.1</a>, <a href="#rfc.iref.s.11"><b>7.3.2</b></a>, <a href="#rfc.xref.status.301.2">10.2</a>, <a href="#rfc.xref.status.301.3">A</a></li> 3800 <li>302 Found <a href="#rfc.xref.status.302.1">4.1</a>, <a href="#rfc.iref.s.12"><b>7.3.3</b></a>, <a href="#rfc.xref.status.302.2">10.2</a>, <a href="#rfc.xref.status.302.3">A</a></li> 3801 <li>303 See Other <a href="#rfc.xref.status.303.1">4.1</a>, <a href="#rfc.iref.s.13"><b>7.3.4</b></a>, <a href="#rfc.xref.status.303.2">10.2</a></li> 3802 <li>305 Use Proxy <a href="#rfc.xref.status.305.1">4.1</a>, <a href="#rfc.iref.s.14"><b>7.3.5</b></a>, <a href="#rfc.xref.status.305.2">10.2</a>, <a href="#rfc.xref.status.305.3">A</a></li> 3803 <li>306 (Unused) <a href="#rfc.iref.s.15"><b>7.3.6</b></a>, <a href="#rfc.xref.status.306.1">10.2</a></li> 3804 <li>307 Temporary Redirect <a href="#rfc.xref.status.307.1">4.1</a>, <a href="#rfc.iref.s.16"><b>7.3.7</b></a>, <a href="#rfc.xref.status.307.2">10.2</a>, <a href="#rfc.xref.status.307.3">A</a></li> 3805 <li>400 Bad Request <a href="#rfc.xref.status.400.1">4.1</a>, <a href="#rfc.iref.s.17"><b>7.4.1</b></a>, <a href="#rfc.xref.status.400.2">10.2</a></li> 3806 <li>402 Payment Required <a href="#rfc.xref.status.402.1">4.1</a>, <a href="#rfc.iref.s.18"><b>7.4.2</b></a>, <a href="#rfc.xref.status.402.2">10.2</a></li> 3807 <li>403 Forbidden <a href="#rfc.xref.status.403.1">4.1</a>, <a href="#rfc.iref.s.19"><b>7.4.3</b></a>, <a href="#rfc.xref.status.403.2">10.2</a></li> 3808 <li>404 Not Found <a href="#rfc.xref.status.404.1">4.1</a>, <a href="#rfc.iref.s.20"><b>7.4.4</b></a>, <a href="#rfc.xref.status.404.2">10.2</a></li> 3809 <li>405 Method Not Allowed <a href="#rfc.xref.status.405.1">4.1</a>, <a href="#rfc.iref.s.21"><b>7.4.5</b></a>, <a href="#rfc.xref.status.405.2">10.2</a></li> 3810 <li>406 Not Acceptable <a href="#rfc.xref.status.406.1">4.1</a>, <a href="#rfc.iref.s.22"><b>7.4.6</b></a>, <a href="#rfc.xref.status.406.2">10.2</a></li> 3811 <li>408 Request Timeout <a href="#rfc.xref.status.408.1">4.1</a>, <a href="#rfc.iref.s.23"><b>7.4.7</b></a>, <a href="#rfc.xref.status.408.2">10.2</a></li> 3812 <li>409 Conflict <a href="#rfc.xref.status.409.1">4.1</a>, <a href="#rfc.iref.s.24"><b>7.4.8</b></a>, <a href="#rfc.xref.status.409.2">10.2</a></li> 3813 <li>410 Gone <a href="#rfc.xref.status.410.1">4.1</a>, <a href="#rfc.iref.s.25"><b>7.4.9</b></a>, <a href="#rfc.xref.status.410.2">10.2</a></li> 3814 <li>411 Length Required <a href="#rfc.xref.status.411.1">4.1</a>, <a href="#rfc.iref.s.26"><b>7.4.10</b></a>, <a href="#rfc.xref.status.411.2">10.2</a></li> 3815 <li>413 Request Representation Too Large <a href="#rfc.xref.status.413.1">4.1</a>, <a href="#rfc.iref.s.27"><b>7.4.11</b></a>, <a href="#rfc.xref.status.413.2">10.2</a></li> 3816 <li>414 URI Too Long <a href="#rfc.xref.status.414.1">4.1</a>, <a href="#rfc.iref.s.28"><b>7.4.12</b></a>, <a href="#rfc.xref.status.414.2">10.2</a></li> 3817 <li>415 Unsupported Media Type <a href="#rfc.xref.status.415.1">4.1</a>, <a href="#rfc.iref.s.29"><b>7.4.13</b></a>, <a href="#rfc.xref.status.415.2">10.2</a></li> 3818 <li>417 Expectation Failed <a href="#rfc.xref.status.417.1">4.1</a>, <a href="#rfc.iref.s.30"><b>7.4.14</b></a>, <a href="#rfc.xref.status.417.2">10.2</a></li> 3819 <li>426 Upgrade Required <a href="#rfc.xref.status.426.1">4.1</a>, <a href="#rfc.iref.s.31"><b>7.4.15</b></a>, <a href="#rfc.xref.status.426.2">10.2</a>, <a href="#rfc.xref.status.426.3">A</a></li> 3820 <li>500 Internal Server Error <a href="#rfc.xref.status.500.1">4.1</a>, <a href="#rfc.iref.s.32"><b>7.5.1</b></a>, <a href="#rfc.xref.status.500.2">10.2</a></li> 3821 <li>501 Not Implemented <a href="#rfc.xref.status.501.1">4.1</a>, <a href="#rfc.iref.s.33"><b>7.5.2</b></a>, <a href="#rfc.xref.status.501.2">10.2</a></li> 3822 <li>502 Bad Gateway <a href="#rfc.xref.status.502.1">4.1</a>, <a href="#rfc.iref.s.34"><b>7.5.3</b></a>, <a href="#rfc.xref.status.502.2">10.2</a></li> 3823 <li>503 Service Unavailable <a href="#rfc.xref.status.503.1">4.1</a>, <a href="#rfc.iref.s.35"><b>7.5.4</b></a>, <a href="#rfc.xref.status.503.2">10.2</a></li> 3824 <li>504 Gateway Timeout <a href="#rfc.xref.status.504.1">4.1</a>, <a href="#rfc.iref.s.36"><b>7.5.5</b></a>, <a href="#rfc.xref.status.504.2">10.2</a></li> 3825 <li>505 HTTP Version Not Supported <a href="#rfc.xref.status.505.1">4.1</a>, <a href="#rfc.iref.s.37"><b>7.5.6</b></a>, <a href="#rfc.xref.status.505.2">10.2</a></li> 3823 3826 </ul> 3824 3827 </li> … … 3826 3829 </li> 3827 3830 <li><a id="rfc.index.T" href="#rfc.index.T"><b>T</b></a><ul> 3828 <li>TRACE method <a href="#rfc.xref.TRACE.1">2.1</a>, <a href="#rfc.iref.t.1"><b>6.8</b></a>, <a href="#rfc.xref.TRACE.2"> 10.6</a>, <a href="#rfc.xref.TRACE.3">11.1</a>, <a href="#rfc.xref.TRACE.4">12.1</a></li>3831 <li>TRACE method <a href="#rfc.xref.TRACE.1">2.1</a>, <a href="#rfc.iref.t.1"><b>6.8</b></a>, <a href="#rfc.xref.TRACE.2">9.6</a>, <a href="#rfc.xref.TRACE.3">10.1</a>, <a href="#rfc.xref.TRACE.4">11.1</a></li> 3829 3832 </ul> 3830 3833 </li> 3831 3834 <li><a id="rfc.index.U" href="#rfc.index.U"><b>U</b></a><ul> 3832 <li>User-Agent header field <a href="#rfc.xref.header.user-agent.1">3.2</a>, <a href="#rfc.iref.u.1"><b> 10.10</b></a>, <a href="#rfc.xref.header.user-agent.2">11.3</a>, <a href="#rfc.xref.header.user-agent.3">12.1</a></li>3835 <li>User-Agent header field <a href="#rfc.xref.header.user-agent.1">3.2</a>, <a href="#rfc.iref.u.1"><b>9.10</b></a>, <a href="#rfc.xref.header.user-agent.2">10.3</a>, <a href="#rfc.xref.header.user-agent.3">11.1</a></li> 3833 3836 </ul> 3834 3837 </li>
Note: See TracChangeset
for help on using the changeset viewer.