Changeset 1167
- Timestamp:
- 11/03/11 13:43:45 (11 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 4 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p2-semantics.html
r1165 r1167 741 741 <div id="rfc.figure.u.2"></div><pre class="inline"> <a href="#abnf.dependencies" class="smpl">absolute-URI</a> = <absolute-URI, defined in <a href="#Part1" id="rfc.xref.Part1.9"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#uri" title="Uniform Resource Identifiers">Section 2.6</a>> 742 742 <a href="#abnf.dependencies" class="smpl">comment</a> = <comment, defined in <a href="#Part1" id="rfc.xref.Part1.10"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#header.fields" title="Header Fields">Section 3.2</a>> 743 <a href="#abnf.dependencies" class="smpl">Host</a> = <Host, defined in <a href="#Part1" id="rfc.xref.Part1.11"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#uri" title="Uniform Resource Identifiers">Section 2.6</a>> 744 <a href="#abnf.dependencies" class="smpl">HTTP-date</a> = <HTTP-date, defined in <a href="#Part1" id="rfc.xref.Part1.12"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#date.time.formats.full.date" title="Date/Time Formats: Full Date">Section 6.1</a>> 745 <a href="#abnf.dependencies" class="smpl">partial-URI</a> = <partial-URI, defined in <a href="#Part1" id="rfc.xref.Part1.13"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#uri" title="Uniform Resource Identifiers">Section 2.6</a>> 746 <a href="#abnf.dependencies" class="smpl">product</a> = <product, defined in <a href="#Part1" id="rfc.xref.Part1.14"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#product.tokens" title="Product Tokens">Section 6.3</a>> 747 <a href="#abnf.dependencies" class="smpl">TE</a> = <TE, defined in <a href="#Part1" id="rfc.xref.Part1.15"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#header.te" title="TE">Section 9.5</a>> 748 <a href="#abnf.dependencies" class="smpl">URI-reference</a> = <URI-reference, defined in <a href="#Part1" id="rfc.xref.Part1.16"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#uri" title="Uniform Resource Identifiers">Section 2.6</a>> 749 </pre><div id="rfc.figure.u.3"></div><pre class="inline"> <a href="#abnf.dependencies" class="smpl">Accept</a> = <Accept, defined in <a href="#Part3" id="rfc.xref.Part3.1"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="p3-payload.html#header.accept" title="Accept">Section 6.1</a>> 750 <a href="#abnf.dependencies" class="smpl">Accept-Charset</a> = 751 <Accept-Charset, defined in <a href="#Part3" id="rfc.xref.Part3.2"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="p3-payload.html#header.accept-charset" title="Accept-Charset">Section 6.2</a>> 752 <a href="#abnf.dependencies" class="smpl">Accept-Encoding</a> = 753 <Accept-Encoding, defined in <a href="#Part3" id="rfc.xref.Part3.3"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="p3-payload.html#header.accept-encoding" title="Accept-Encoding">Section 6.3</a>> 754 <a href="#abnf.dependencies" class="smpl">Accept-Language</a> = 755 <Accept-Language, defined in <a href="#Part3" id="rfc.xref.Part3.4"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="p3-payload.html#header.accept-language" title="Accept-Language">Section 6.4</a>> 756 </pre><div id="rfc.figure.u.4"></div><pre class="inline"> <a href="#abnf.dependencies" class="smpl">ETag</a> = <ETag, defined in <a href="#Part4" id="rfc.xref.Part4.1"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>, <a href="p4-conditional.html#header.etag" title="ETag">Section 6.1</a>> 757 <a href="#abnf.dependencies" class="smpl">If-Match</a> = <If-Match, defined in <a href="#Part4" id="rfc.xref.Part4.2"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>, <a href="p4-conditional.html#header.if-match" title="If-Match">Section 6.2</a>> 758 <a href="#abnf.dependencies" class="smpl">If-Modified-Since</a> = 759 <If-Modified-Since, defined in <a href="#Part4" id="rfc.xref.Part4.3"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>, <a href="p4-conditional.html#header.if-modified-since" title="If-Modified-Since">Section 6.3</a>> 760 <a href="#abnf.dependencies" class="smpl">If-None-Match</a> = <If-None-Match, defined in <a href="#Part4" id="rfc.xref.Part4.4"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>, <a href="p4-conditional.html#header.if-none-match" title="If-None-Match">Section 6.4</a>> 761 <a href="#abnf.dependencies" class="smpl">If-Unmodified-Since</a> = 762 <If-Unmodified-Since, defined in <a href="#Part4" id="rfc.xref.Part4.5"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>, <a href="p4-conditional.html#header.if-unmodified-since" title="If-Unmodified-Since">Section 6.5</a>> 763 </pre><div id="rfc.figure.u.5"></div><pre class="inline"> <a href="#abnf.dependencies" class="smpl">Accept-Ranges</a> = <Accept-Ranges, defined in <a href="#Part5" id="rfc.xref.Part5.1"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>, <a href="p5-range.html#header.accept-ranges" title="Accept-Ranges">Section 5.1</a>> 764 <a href="#abnf.dependencies" class="smpl">If-Range</a> = <If-Range, defined in <a href="#Part5" id="rfc.xref.Part5.2"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>, <a href="p5-range.html#header.if-range" title="If-Range">Section 5.3</a>> 765 <a href="#abnf.dependencies" class="smpl">Range</a> = <Range, defined in <a href="#Part5" id="rfc.xref.Part5.3"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>, <a href="p5-range.html#header.range" title="Range">Section 5.4</a>> 766 </pre><div id="rfc.figure.u.6"></div><pre class="inline"> <a href="#abnf.dependencies" class="smpl">Age</a> = <Age, defined in <a href="#Part6" id="rfc.xref.Part6.1"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>, <a href="p6-cache.html#header.age" title="Age">Section 3.1</a>> 767 <a href="#abnf.dependencies" class="smpl">Vary</a> = <Vary, defined in <a href="#Part6" id="rfc.xref.Part6.2"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>, <a href="p6-cache.html#header.vary" title="Vary">Section 3.5</a>> 768 </pre><div id="rfc.figure.u.7"></div><pre class="inline"> <a href="#abnf.dependencies" class="smpl">Authorization</a> = <Authorization, defined in <a href="#Part7" id="rfc.xref.Part7.1"><cite title="HTTP/1.1, part 7: Authentication">[Part7]</cite></a>, <a href="p7-auth.html#header.authorization" title="Authorization">Section 4.1</a>> 769 <a href="#abnf.dependencies" class="smpl">Proxy-Authenticate</a> = 770 <Proxy-Authenticate, defined in <a href="#Part7" id="rfc.xref.Part7.2"><cite title="HTTP/1.1, part 7: Authentication">[Part7]</cite></a>, <a href="p7-auth.html#header.proxy-authenticate" title="Proxy-Authenticate">Section 4.2</a>> 771 <a href="#abnf.dependencies" class="smpl">Proxy-Authorization</a> = 772 <Proxy-Authorization, defined in <a href="#Part7" id="rfc.xref.Part7.3"><cite title="HTTP/1.1, part 7: Authentication">[Part7]</cite></a>, <a href="p7-auth.html#header.proxy-authorization" title="Proxy-Authorization">Section 4.3</a>> 773 <a href="#abnf.dependencies" class="smpl">WWW-Authenticate</a> = 774 <WWW-Authenticate, defined in <a href="#Part7" id="rfc.xref.Part7.4"><cite title="HTTP/1.1, part 7: Authentication">[Part7]</cite></a>, <a href="p7-auth.html#header.www-authenticate" title="WWW-Authenticate">Section 4.4</a>> 743 <a href="#abnf.dependencies" class="smpl">HTTP-date</a> = <HTTP-date, defined in <a href="#Part1" id="rfc.xref.Part1.11"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#date.time.formats.full.date" title="Date/Time Formats: Full Date">Section 6.1</a>> 744 <a href="#abnf.dependencies" class="smpl">partial-URI</a> = <partial-URI, defined in <a href="#Part1" id="rfc.xref.Part1.12"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#uri" title="Uniform Resource Identifiers">Section 2.6</a>> 745 <a href="#abnf.dependencies" class="smpl">product</a> = <product, defined in <a href="#Part1" id="rfc.xref.Part1.13"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#product.tokens" title="Product Tokens">Section 6.3</a>> 746 <a href="#abnf.dependencies" class="smpl">URI-reference</a> = <URI-reference, defined in <a href="#Part1" id="rfc.xref.Part1.14"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#uri" title="Uniform Resource Identifiers">Section 2.6</a>> 775 747 </pre><h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a> <a id="method" href="#method">Method</a></h1> 776 <p id="rfc.section.2.p.1">The Method token indicates the request method to be performed on the target resource (<a href="p1-messaging.html#effective.request.uri" title="Effective Request URI">Section 4.3</a> of <a href="#Part1" id="rfc.xref.Part1.1 7"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>). The method is case-sensitive.777 </p> 778 <div id="rfc.figure.u. 8"></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>748 <p id="rfc.section.2.p.1">The Method token indicates the request method to be performed on the target resource (<a href="p1-messaging.html#effective.request.uri" title="Effective Request URI">Section 4.3</a> of <a href="#Part1" id="rfc.xref.Part1.15"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>). The method is case-sensitive. 749 </p> 750 <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> 779 751 </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 780 752 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 … … 853 825 to a single application, so that this is clear. 854 826 </p> 855 <p id="rfc.section.2.2.1.p.3">Due to the parsing rules defined in <a href="p1-messaging.html#message.body" title="Message Body">Section 3.3</a> of <a href="#Part1" id="rfc.xref.Part1.1 8"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, definitions of HTTP methods cannot prohibit the presence of a message-body on either the request or the response message827 <p id="rfc.section.2.2.1.p.3">Due to the parsing rules defined in <a href="p1-messaging.html#message.body" title="Message Body">Section 3.3</a> of <a href="#Part1" id="rfc.xref.Part1.16"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, definitions of HTTP methods cannot prohibit the presence of a message-body on either the request or the response message 856 828 (with responses to HEAD requests being the single exception). Definitions of new methods cannot change this rule, but they 857 829 can specify that only zero-length bodies (as opposed to absent bodies) are allowed. 858 830 </p> 859 <p id="rfc.section.2.2.1.p.4">New method definitions need to indicate whether they are safe (<a href="#safe.methods" title="Safe Methods">Section 7.1.1</a>) and whether they are idempotent (<a href="#idempotent.methods" title="Idempotent Methods">Section 7.1.2</a>). They also need to state whether they can be cached (<a href="#Part6" id="rfc.xref.Part6. 3"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>); in particular what conditions a cache may store the response, and under what conditions such a stored response may be used831 <p id="rfc.section.2.2.1.p.4">New method definitions need to indicate whether they are safe (<a href="#safe.methods" title="Safe Methods">Section 7.1.1</a>) and whether they are idempotent (<a href="#idempotent.methods" title="Idempotent Methods">Section 7.1.2</a>). They also need to state whether they can be cached (<a href="#Part6" id="rfc.xref.Part6.1"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>); in particular what conditions a cache may store the response, and under what conditions such a stored response may be used 860 832 to satisfy a subsequent request. 861 833 </p> … … 876 848 <tr> 877 849 <td class="left">Accept</td> 878 <td class="left"><a href="p3-payload.html#header.accept" title="Accept">Section 6.1</a> of <a href="#Part3" id="rfc.xref.Part3. 5"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a></td>850 <td class="left"><a href="p3-payload.html#header.accept" title="Accept">Section 6.1</a> of <a href="#Part3" id="rfc.xref.Part3.1"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a></td> 879 851 </tr> 880 852 <tr> 881 853 <td class="left">Accept-Charset</td> 882 <td class="left"><a href="p3-payload.html#header.accept-charset" title="Accept-Charset">Section 6.2</a> of <a href="#Part3" id="rfc.xref.Part3. 6"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a></td>854 <td class="left"><a href="p3-payload.html#header.accept-charset" title="Accept-Charset">Section 6.2</a> of <a href="#Part3" id="rfc.xref.Part3.2"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a></td> 883 855 </tr> 884 856 <tr> 885 857 <td class="left">Accept-Encoding</td> 886 <td class="left"><a href="p3-payload.html#header.accept-encoding" title="Accept-Encoding">Section 6.3</a> of <a href="#Part3" id="rfc.xref.Part3. 7"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a></td>858 <td class="left"><a href="p3-payload.html#header.accept-encoding" title="Accept-Encoding">Section 6.3</a> of <a href="#Part3" id="rfc.xref.Part3.3"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a></td> 887 859 </tr> 888 860 <tr> 889 861 <td class="left">Accept-Language</td> 890 <td class="left"><a href="p3-payload.html#header.accept-language" title="Accept-Language">Section 6.4</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></td>862 <td class="left"><a href="p3-payload.html#header.accept-language" title="Accept-Language">Section 6.4</a> of <a href="#Part3" id="rfc.xref.Part3.4"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a></td> 891 863 </tr> 892 864 <tr> 893 865 <td class="left">Authorization</td> 894 <td class="left"><a href="p7-auth.html#header.authorization" title="Authorization">Section 4.1</a> of <a href="#Part7" id="rfc.xref.Part7. 5"><cite title="HTTP/1.1, part 7: Authentication">[Part7]</cite></a></td>866 <td class="left"><a href="p7-auth.html#header.authorization" title="Authorization">Section 4.1</a> of <a href="#Part7" id="rfc.xref.Part7.1"><cite title="HTTP/1.1, part 7: Authentication">[Part7]</cite></a></td> 895 867 </tr> 896 868 <tr> … … 904 876 <tr> 905 877 <td class="left">Host</td> 906 <td class="left"><a href="p1-messaging.html#header.host" title="Host">Section 9.4</a> of <a href="#Part1" id="rfc.xref.Part1.1 9"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a></td>878 <td class="left"><a href="p1-messaging.html#header.host" title="Host">Section 9.4</a> of <a href="#Part1" id="rfc.xref.Part1.17"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a></td> 907 879 </tr> 908 880 <tr> 909 881 <td class="left">If-Match</td> 910 <td class="left"><a href="p4-conditional.html#header.if-match" title="If-Match">Section 6.2</a> of <a href="#Part4" id="rfc.xref.Part4. 6"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a></td>882 <td class="left"><a href="p4-conditional.html#header.if-match" title="If-Match">Section 6.2</a> of <a href="#Part4" id="rfc.xref.Part4.1"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a></td> 911 883 </tr> 912 884 <tr> 913 885 <td class="left">If-Modified-Since</td> 914 <td class="left"><a href="p4-conditional.html#header.if-modified-since" title="If-Modified-Since">Section 6.3</a> of <a href="#Part4" id="rfc.xref.Part4. 7"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a></td>886 <td class="left"><a href="p4-conditional.html#header.if-modified-since" title="If-Modified-Since">Section 6.3</a> of <a href="#Part4" id="rfc.xref.Part4.2"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a></td> 915 887 </tr> 916 888 <tr> 917 889 <td class="left">If-None-Match</td> 918 <td class="left"><a href="p4-conditional.html#header.if-none-match" title="If-None-Match">Section 6.4</a> of <a href="#Part4" id="rfc.xref.Part4. 8"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a></td>890 <td class="left"><a href="p4-conditional.html#header.if-none-match" title="If-None-Match">Section 6.4</a> of <a href="#Part4" id="rfc.xref.Part4.3"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a></td> 919 891 </tr> 920 892 <tr> 921 893 <td class="left">If-Range</td> 922 <td class="left"><a href="p5-range.html#header.if-range" title="If-Range">Section 5.3</a> of <a href="#Part5" id="rfc.xref.Part5. 4"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a></td>894 <td class="left"><a href="p5-range.html#header.if-range" title="If-Range">Section 5.3</a> of <a href="#Part5" id="rfc.xref.Part5.1"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a></td> 923 895 </tr> 924 896 <tr> 925 897 <td class="left">If-Unmodified-Since</td> 926 <td class="left"><a href="p4-conditional.html#header.if-unmodified-since" title="If-Unmodified-Since">Section 6.5</a> of <a href="#Part4" id="rfc.xref.Part4. 9"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a></td>898 <td class="left"><a href="p4-conditional.html#header.if-unmodified-since" title="If-Unmodified-Since">Section 6.5</a> of <a href="#Part4" id="rfc.xref.Part4.4"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a></td> 927 899 </tr> 928 900 <tr> … … 932 904 <tr> 933 905 <td class="left">Proxy-Authorization</td> 934 <td class="left"><a href="p7-auth.html#header.proxy-authorization" title="Proxy-Authorization">Section 4.3</a> of <a href="#Part7" id="rfc.xref.Part7. 6"><cite title="HTTP/1.1, part 7: Authentication">[Part7]</cite></a></td>906 <td class="left"><a href="p7-auth.html#header.proxy-authorization" title="Proxy-Authorization">Section 4.3</a> of <a href="#Part7" id="rfc.xref.Part7.2"><cite title="HTTP/1.1, part 7: Authentication">[Part7]</cite></a></td> 935 907 </tr> 936 908 <tr> 937 909 <td class="left">Range</td> 938 <td class="left"><a href="p5-range.html#header.range" title="Range">Section 5.4</a> of <a href="#Part5" id="rfc.xref.Part5. 5"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a></td>910 <td class="left"><a href="p5-range.html#header.range" title="Range">Section 5.4</a> of <a href="#Part5" id="rfc.xref.Part5.2"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a></td> 939 911 </tr> 940 912 <tr> … … 944 916 <tr> 945 917 <td class="left">TE</td> 946 <td class="left"><a href="p1-messaging.html#header.te" title="TE">Section 9.5</a> of <a href="#Part1" id="rfc.xref.Part1. 20"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a></td>918 <td class="left"><a href="p1-messaging.html#header.te" title="TE">Section 9.5</a> of <a href="#Part1" id="rfc.xref.Part1.18"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a></td> 947 919 </tr> 948 920 <tr> … … 958 930 client does not need to examine or display the Reason-Phrase. 959 931 </p> 960 <div id="rfc.figure.u. 9"></div><pre class="inline"><span id="rfc.iref.g.2"></span><span id="rfc.iref.g.3"></span><span id="rfc.iref.g.4"></span> <a href="#status.code.and.reason.phrase" class="smpl">Status-Code</a> = 3<a href="#notation" class="smpl">DIGIT</a>932 <div id="rfc.figure.u.4"></div><pre class="inline"><span id="rfc.iref.g.2"></span><span id="rfc.iref.g.3"></span><span id="rfc.iref.g.4"></span> <a href="#status.code.and.reason.phrase" class="smpl">Status-Code</a> = 3<a href="#notation" class="smpl">DIGIT</a> 961 933 <a href="#status.code.and.reason.phrase" class="smpl">Reason-Phrase</a> = *( <a href="#notation" class="smpl">WSP</a> / <a href="#notation" class="smpl">VCHAR</a> / <a href="#core.rules" class="smpl">obs-text</a> ) 962 934 </pre><p id="rfc.section.4.p.4">HTTP status codes are extensible. HTTP applications are not required to understand the meaning of all registered status codes, … … 967 939 </p> 968 940 <h2 id="rfc.section.4.1"><a href="#rfc.section.4.1">4.1</a> <a id="overview.of.status.codes" href="#overview.of.status.codes">Overview of Status Codes</a></h2> 969 <p id="rfc.section.4.1.p.1">The status codes listed below are defined in <a href="#status.codes" title="Status Code Definitions">Section 8</a> of this specification, <a href="p4-conditional.html#status.code.definitions" title="Status Code Definitions">Section 3</a> of <a href="#Part4" id="rfc.xref.Part4. 10"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>, <a href="p5-range.html#status.code.definitions" title="Status Code Definitions">Section 3</a> of <a href="#Part5" id="rfc.xref.Part5.6"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>, and <a href="p7-auth.html#status.code.definitions" title="Status Code Definitions">Section 3</a> of <a href="#Part7" id="rfc.xref.Part7.7"><cite title="HTTP/1.1, part 7: Authentication">[Part7]</cite></a>. The reason phrases listed here are only recommendations — they can be replaced by local equivalents without affecting the941 <p id="rfc.section.4.1.p.1">The status codes listed below are defined in <a href="#status.codes" title="Status Code Definitions">Section 8</a> of this specification, <a href="p4-conditional.html#status.code.definitions" title="Status Code Definitions">Section 3</a> of <a href="#Part4" id="rfc.xref.Part4.5"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>, <a href="p5-range.html#status.code.definitions" title="Status Code Definitions">Section 3</a> of <a href="#Part5" id="rfc.xref.Part5.3"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>, and <a href="p7-auth.html#status.code.definitions" title="Status Code Definitions">Section 3</a> of <a href="#Part7" id="rfc.xref.Part7.3"><cite title="HTTP/1.1, part 7: Authentication">[Part7]</cite></a>. The reason phrases listed here are only recommendations — they can be replaced by local equivalents without affecting the 970 942 protocol. 971 943 </p> … … 1023 995 <td class="left">206</td> 1024 996 <td class="left">Partial Content</td> 1025 <td class="left"><a href="p5-range.html#status.206" title="206 Partial Content">Section 3.1</a> of <a href="#Part5" id="rfc.xref.Part5. 7"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a></td>997 <td class="left"><a href="p5-range.html#status.206" title="206 Partial Content">Section 3.1</a> of <a href="#Part5" id="rfc.xref.Part5.4"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a></td> 1026 998 </tr> 1027 999 <tr> … … 1048 1020 <td class="left">304</td> 1049 1021 <td class="left">Not Modified</td> 1050 <td class="left"><a href="p4-conditional.html#status.304" title="304 Not Modified">Section 3.1</a> of <a href="#Part4" id="rfc.xref.Part4. 11"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a></td>1022 <td class="left"><a href="p4-conditional.html#status.304" title="304 Not Modified">Section 3.1</a> of <a href="#Part4" id="rfc.xref.Part4.6"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a></td> 1051 1023 </tr> 1052 1024 <tr> … … 1068 1040 <td class="left">401</td> 1069 1041 <td class="left">Unauthorized</td> 1070 <td class="left"><a href="p7-auth.html#status.401" title="401 Unauthorized">Section 3.1</a> of <a href="#Part7" id="rfc.xref.Part7. 8"><cite title="HTTP/1.1, part 7: Authentication">[Part7]</cite></a></td>1042 <td class="left"><a href="p7-auth.html#status.401" title="401 Unauthorized">Section 3.1</a> of <a href="#Part7" id="rfc.xref.Part7.4"><cite title="HTTP/1.1, part 7: Authentication">[Part7]</cite></a></td> 1071 1043 </tr> 1072 1044 <tr> … … 1098 1070 <td class="left">407</td> 1099 1071 <td class="left">Proxy Authentication Required</td> 1100 <td class="left"><a href="p7-auth.html#status.407" title="407 Proxy Authentication Required">Section 3.2</a> of <a href="#Part7" id="rfc.xref.Part7. 9"><cite title="HTTP/1.1, part 7: Authentication">[Part7]</cite></a></td>1072 <td class="left"><a href="p7-auth.html#status.407" title="407 Proxy Authentication Required">Section 3.2</a> of <a href="#Part7" id="rfc.xref.Part7.5"><cite title="HTTP/1.1, part 7: Authentication">[Part7]</cite></a></td> 1101 1073 </tr> 1102 1074 <tr> … … 1123 1095 <td class="left">412</td> 1124 1096 <td class="left">Precondition Failed</td> 1125 <td class="left"><a href="p4-conditional.html#status.412" title="412 Precondition Failed">Section 3.2</a> of <a href="#Part4" id="rfc.xref.Part4. 12"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a></td>1097 <td class="left"><a href="p4-conditional.html#status.412" title="412 Precondition Failed">Section 3.2</a> of <a href="#Part4" id="rfc.xref.Part4.7"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a></td> 1126 1098 </tr> 1127 1099 <tr> … … 1143 1115 <td class="left">416</td> 1144 1116 <td class="left">Requested range not satisfiable</td> 1145 <td class="left"><a href="p5-range.html#status.416" title="416 Requested Range Not Satisfiable">Section 3.2</a> of <a href="#Part5" id="rfc.xref.Part5. 8"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a></td>1117 <td class="left"><a href="p5-range.html#status.416" title="416 Requested Range Not Satisfiable">Section 3.2</a> of <a href="#Part5" id="rfc.xref.Part5.5"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a></td> 1146 1118 </tr> 1147 1119 <tr> … … 1210 1182 a zero-length response body. They can require the presence of one or more particular HTTP response header(s). 1211 1183 </p> 1212 <p id="rfc.section.4.2.1.p.5">Likewise, their definitions can specify that caches are allowed to use heuristics to determine their freshness (see <a href="#Part6" id="rfc.xref.Part6. 4"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>; by default, it is not allowed), and can define how to determine the resource which they carry a representation for (see <a href="#identifying.response.associated.with.representation" title="Identifying the Resource Associated with a Representation">Section 6.1</a>; by default, it is anonymous).1184 <p id="rfc.section.4.2.1.p.5">Likewise, their definitions can specify that caches are allowed to use heuristics to determine their freshness (see <a href="#Part6" id="rfc.xref.Part6.2"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>; by default, it is not allowed), and can define how to determine the resource which they carry a representation for (see <a href="#identifying.response.associated.with.representation" title="Identifying the Resource Associated with a Representation">Section 6.1</a>; by default, it is anonymous). 1213 1185 </p> 1214 1186 <h1 id="rfc.section.5"><a href="#rfc.section.5">5.</a> <a id="response.header.fields" href="#response.header.fields">Response Header Fields</a></h1> 1215 1187 <p id="rfc.section.5.p.1">The response header fields allow the server to pass additional information about the response which cannot be placed in the 1216 Status-Line. These header fields give information about the server and about further access to the target resource (<a href="p1-messaging.html#effective.request.uri" title="Effective Request URI">Section 4.3</a> of <a href="#Part1" id="rfc.xref.Part1. 21"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>).1188 Status-Line. These header fields give information about the server and about further access to the target resource (<a href="p1-messaging.html#effective.request.uri" title="Effective Request URI">Section 4.3</a> of <a href="#Part1" id="rfc.xref.Part1.19"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>). 1217 1189 </p> 1218 1190 <div id="rfc.table.u.4"> … … 1227 1199 <tr> 1228 1200 <td class="left">Accept-Ranges</td> 1229 <td class="left"><a href="p5-range.html#header.accept-ranges" title="Accept-Ranges">Section 5.1</a> of <a href="#Part5" id="rfc.xref.Part5. 9"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a></td>1201 <td class="left"><a href="p5-range.html#header.accept-ranges" title="Accept-Ranges">Section 5.1</a> of <a href="#Part5" id="rfc.xref.Part5.6"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a></td> 1230 1202 </tr> 1231 1203 <tr> 1232 1204 <td class="left">Age</td> 1233 <td class="left"><a href="p6-cache.html#header.age" title="Age">Section 3.1</a> of <a href="#Part6" id="rfc.xref.Part6. 5"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a></td>1205 <td class="left"><a href="p6-cache.html#header.age" title="Age">Section 3.1</a> of <a href="#Part6" id="rfc.xref.Part6.3"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a></td> 1234 1206 </tr> 1235 1207 <tr> … … 1239 1211 <tr> 1240 1212 <td class="left">ETag</td> 1241 <td class="left"><a href="p4-conditional.html#header.etag" title="ETag">Section 6.1</a> of <a href="#Part4" id="rfc.xref.Part4. 13"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a></td>1213 <td class="left"><a href="p4-conditional.html#header.etag" title="ETag">Section 6.1</a> of <a href="#Part4" id="rfc.xref.Part4.8"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a></td> 1242 1214 </tr> 1243 1215 <tr> … … 1247 1219 <tr> 1248 1220 <td class="left">Proxy-Authenticate</td> 1249 <td class="left"><a href="p7-auth.html#header.proxy-authenticate" title="Proxy-Authenticate">Section 4.2</a> of <a href="#Part7" id="rfc.xref.Part7. 10"><cite title="HTTP/1.1, part 7: Authentication">[Part7]</cite></a></td>1221 <td class="left"><a href="p7-auth.html#header.proxy-authenticate" title="Proxy-Authenticate">Section 4.2</a> of <a href="#Part7" id="rfc.xref.Part7.6"><cite title="HTTP/1.1, part 7: Authentication">[Part7]</cite></a></td> 1250 1222 </tr> 1251 1223 <tr> … … 1259 1231 <tr> 1260 1232 <td class="left">Vary</td> 1261 <td class="left"><a href="p6-cache.html#header.vary" title="Vary">Section 3.5</a> of <a href="#Part6" id="rfc.xref.Part6. 6"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a></td>1233 <td class="left"><a href="p6-cache.html#header.vary" title="Vary">Section 3.5</a> of <a href="#Part6" id="rfc.xref.Part6.4"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a></td> 1262 1234 </tr> 1263 1235 <tr> 1264 1236 <td class="left">WWW-Authenticate</td> 1265 <td class="left"><a href="p7-auth.html#header.www-authenticate" title="WWW-Authenticate">Section 4.4</a> of <a href="#Part7" id="rfc.xref.Part7. 11"><cite title="HTTP/1.1, part 7: Authentication">[Part7]</cite></a></td>1237 <td class="left"><a href="p7-auth.html#header.www-authenticate" title="WWW-Authenticate">Section 4.4</a> of <a href="#Part7" id="rfc.xref.Part7.7"><cite title="HTTP/1.1, part 7: Authentication">[Part7]</cite></a></td> 1266 1238 </tr> 1267 1239 </tbody> … … 1271 1243 <p id="rfc.section.6.p.1">Request and Response messages <em class="bcp14">MAY</em> transfer a representation if not otherwise restricted by the request method or response status code. A representation consists 1272 1244 of metadata (representation header fields) and data (representation body). When a complete or partial representation is enclosed 1273 in an HTTP message, it is referred to as the payload of the message. HTTP representations are defined in <a href="#Part3" id="rfc.xref.Part3. 9"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>.1274 </p> 1275 <p id="rfc.section.6.p.2">A representation body is only present in a message when a message-body is present, as described in <a href="p1-messaging.html#message.body" title="Message Body">Section 3.3</a> of <a href="#Part1" id="rfc.xref.Part1.2 2"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>. The representation body is obtained from the message-body by decoding any Transfer-Encoding that might have been applied1245 in an HTTP message, it is referred to as the payload of the message. HTTP representations are defined in <a href="#Part3" id="rfc.xref.Part3.5"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>. 1246 </p> 1247 <p id="rfc.section.6.p.2">A representation body is only present in a message when a message-body is present, as described in <a href="p1-messaging.html#message.body" title="Message Body">Section 3.3</a> of <a href="#Part1" id="rfc.xref.Part1.20"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>. The representation body is obtained from the message-body by decoding any Transfer-Encoding that might have been applied 1276 1248 to ensure safe and proper transfer of the message. 1277 1249 </p> … … 1279 1251 <p id="rfc.section.6.1.p.1">It is sometimes necessary to determine an identifier for the resource associated with a representation.</p> 1280 1252 <p id="rfc.section.6.1.p.2">An HTTP request representation, when present, is always associated with an anonymous (i.e., unidentified) resource.</p> 1281 <p id="rfc.section.6.1.p.3">In the common case, an HTTP response is a representation of the target resource (see <a href="p1-messaging.html#effective.request.uri" title="Effective Request URI">Section 4.3</a> of <a href="#Part1" id="rfc.xref.Part1.2 3"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>). However, this is not always the case. To determine the URI of the resource a response is associated with, the following1253 <p id="rfc.section.6.1.p.3">In the common case, an HTTP response is a representation of the target resource (see <a href="p1-messaging.html#effective.request.uri" title="Effective Request URI">Section 4.3</a> of <a href="#Part1" id="rfc.xref.Part1.21"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>). However, this is not always the case. To determine the URI of the resource a response is associated with, the following 1282 1254 rules are used (with the first applicable one being selected): 1283 1255 </p> … … 1287 1259 </li> 1288 1260 <li>If the response status code is 204, 206, or 304 and the request method was GET or HEAD, the response payload is a partial 1289 representation of the target resource (see <a href="p6-cache.html#combining.responses" title="Combining Responses">Section 2.8</a> of <a href="#Part6" id="rfc.xref.Part6. 7"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>).1261 representation of the target resource (see <a href="p6-cache.html#combining.responses" title="Combining Responses">Section 2.8</a> of <a href="#Part6" id="rfc.xref.Part6.5"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>). 1290 1262 </li> 1291 1263 <li>If the response has a Content-Location header field, and that URI is the same as the effective request URI, the response payload … … 1365 1337 </p> 1366 1338 <p id="rfc.section.7.3.p.4">The semantics of the GET method change to a "partial GET" if the request message includes a Range header field. A partial 1367 GET requests that only part of the representation be transferred, as described in <a href="p5-range.html#header.range" title="Range">Section 5.4</a> of <a href="#Part5" id="rfc.xref.Part5. 10"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>. The partial GET request is intended to reduce unnecessary network usage by allowing partially-retrieved representations1339 GET requests that only part of the representation be transferred, as described in <a href="p5-range.html#header.range" title="Range">Section 5.4</a> of <a href="#Part5" id="rfc.xref.Part5.7"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>. The partial GET request is intended to reduce unnecessary network usage by allowing partially-retrieved representations 1368 1340 to be completed without transferring data already held by the client. 1369 1341 </p> 1370 <p id="rfc.section.7.3.p.5">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. 8"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>).1342 <p id="rfc.section.7.3.p.5">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>). 1371 1343 </p> 1372 1344 <p id="rfc.section.7.3.p.6">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. … … 1379 1351 hypertext links for validity, accessibility, and recent modification. 1380 1352 </p> 1381 <p id="rfc.section.7.4.p.2">The response to a HEAD request is cacheable and <em class="bcp14">MAY</em> be used to satisfy a subsequent HEAD request; see <a href="#Part6" id="rfc.xref.Part6. 9"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>. It also <em class="bcp14">MAY</em> be used to update a previously cached representation from that resource; if the new field values indicate that the cached1353 <p id="rfc.section.7.4.p.2">The response to a HEAD request is cacheable and <em class="bcp14">MAY</em> be used to satisfy a subsequent HEAD request; see <a href="#Part6" id="rfc.xref.Part6.7"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>. It also <em class="bcp14">MAY</em> be used to update a previously cached representation from that resource; if the new field values indicate that the cached 1382 1354 representation differs from the current representation (as would be indicated by a change in Content-Length, Content-MD5, 1383 1355 ETag or Last-Modified), then the cache <em class="bcp14">MUST</em> treat the cache entry as stale. … … 1405 1377 a Location header field (see <a href="#header.location" id="rfc.xref.header.location.2" title="Location">Section 9.4</a>). 1406 1378 </p> 1407 <p id="rfc.section.7.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. 10"><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.10"><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.1379 <p id="rfc.section.7.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.6"><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. 1408 1380 </p> 1409 1381 <p id="rfc.section.7.5.p.6">Note that POST caching is not widely implemented. However, the 303 (See Other) response can be used to direct the user agent … … 1468 1440 </p> 1469 1441 <p id="rfc.section.7.6.p.11">Responses to the PUT method are not cacheable. If a PUT request passes through a cache that has one or more stored responses 1470 for the effective request URI, those stored responses will be invalidated (see <a href="p6-cache.html#invalidation.after.updates.or.deletions" title="Request Methods that Invalidate">Section 2.5</a> of <a href="#Part6" id="rfc.xref.Part6. 11"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>).1442 for the effective request URI, those stored responses will be invalidated (see <a href="p6-cache.html#invalidation.after.updates.or.deletions" title="Request Methods that Invalidate">Section 2.5</a> of <a href="#Part6" id="rfc.xref.Part6.9"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>). 1471 1443 </p> 1472 1444 <div id="rfc.iref.d.1"></div> … … 1482 1454 </p> 1483 1455 <p id="rfc.section.7.7.p.3">Responses to the DELETE method are not cacheable. If a DELETE request passes through a cache that has one or more stored responses 1484 for the effective request URI, those stored responses will be invalidated (see <a href="p6-cache.html#invalidation.after.updates.or.deletions" title="Request Methods that Invalidate">Section 2.5</a> of <a href="#Part6" id="rfc.xref.Part6.1 2"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>).1456 for the effective request URI, those stored responses will be invalidated (see <a href="p6-cache.html#invalidation.after.updates.or.deletions" title="Request Methods that Invalidate">Section 2.5</a> of <a href="#Part6" id="rfc.xref.Part6.10"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>). 1485 1457 </p> 1486 1458 <h2 id="rfc.section.7.8"><a href="#rfc.section.7.8">7.8</a> <a id="TRACE" href="#TRACE">TRACE</a></h2> … … 1491 1463 </p> 1492 1464 <p id="rfc.section.7.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 1493 or diagnostic information. The value of the Via header field (<a href="p1-messaging.html#header.via" title="Via">Section 9.9</a> of <a href="#Part1" id="rfc.xref.Part1.2 4"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) is of particular interest, since it acts as a trace of the request chain. Use of the Max-Forwards header field allows the1465 or diagnostic information. The value of the Via header field (<a href="p1-messaging.html#header.via" title="Via">Section 9.9</a> of <a href="#Part1" id="rfc.xref.Part1.22"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) is of particular interest, since it acts as a trace of the request chain. Use of the Max-Forwards header field allows the 1494 1466 client to limit the length of the request chain, which is useful for testing a chain of proxies forwarding messages in an 1495 1467 infinite loop. 1496 1468 </p> 1497 <p id="rfc.section.7.8.p.3">If the request is valid, the response <em class="bcp14">SHOULD</em> have a Content-Type of "message/http" (see <a href="p1-messaging.html#internet.media.type.message.http" title="Internet Media Type message/http">Section 10.3.1</a> of <a href="#Part1" id="rfc.xref.Part1.2 5"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) and contain a message-body that encloses a copy of the entire request message. Responses to the TRACE method are not cacheable.1469 <p id="rfc.section.7.8.p.3">If the request is valid, the response <em class="bcp14">SHOULD</em> have a Content-Type of "message/http" (see <a href="p1-messaging.html#internet.media.type.message.http" title="Internet Media Type message/http">Section 10.3.1</a> of <a href="#Part1" id="rfc.xref.Part1.23"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) and contain a message-body that encloses a copy of the entire request message. Responses to the TRACE method are not cacheable. 1498 1470 </p> 1499 1471 <div id="rfc.iref.c.1"></div> … … 1503 1475 forwarding of packets until the connection is closed. 1504 1476 </p> 1505 <p id="rfc.section.7.9.p.2">When using CONNECT, the request-target <em class="bcp14">MUST</em> use the authority form (<a href="p1-messaging.html#request-target" title="request-target">Section 4.1.2</a> of <a href="#Part1" id="rfc.xref.Part1.2 6"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>); i.e., the request-target consists of only the host name and port number of the tunnel destination, separated by a colon.1477 <p id="rfc.section.7.9.p.2">When using CONNECT, the request-target <em class="bcp14">MUST</em> use the authority form (<a href="p1-messaging.html#request-target" title="request-target">Section 4.1.2</a> of <a href="#Part1" id="rfc.xref.Part1.24"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>); i.e., the request-target consists of only the host name and port number of the tunnel destination, separated by a colon. 1506 1478 For example, 1507 1479 </p> 1508 <div id="rfc.figure.u. 10"></div><pre class="text2">CONNECT server.example.com:80 HTTP/1.11480 <div id="rfc.figure.u.5"></div><pre class="text2">CONNECT server.example.com:80 HTTP/1.1 1509 1481 Host: server.example.com:80 1510 1482 … … 1513 1485 </p> 1514 1486 <p id="rfc.section.7.9.p.5">For example, proxy authentication might be used to establish the authority to create a tunnel:</p> 1515 <div id="rfc.figure.u. 11"></div><pre class="text2">CONNECT server.example.com:80 HTTP/1.11487 <div id="rfc.figure.u.6"></div><pre class="text2">CONNECT server.example.com:80 HTTP/1.1 1516 1488 Host: server.example.com:80 1517 1489 Proxy-Authorization: basic aGVsbG86d29ybGQ= … … 1554 1526 <p id="rfc.section.8.1.1.p.1">The client <em class="bcp14">SHOULD</em> continue with its request. This interim response is used to inform the client that the initial part of the request has been 1555 1527 received and has not yet been rejected by the server. The client <em class="bcp14">SHOULD</em> continue by sending the remainder of the request or, if the request has already been completed, ignore this response. The 1556 server <em class="bcp14">MUST</em> send a final response after the request has been completed. See <a href="p1-messaging.html#use.of.the.100.status" title="Use of the 100 (Continue) Status">Section 7.2.3</a> of <a href="#Part1" id="rfc.xref.Part1.2 7"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a> for detailed discussion of the use and handling of this status code.1528 server <em class="bcp14">MUST</em> send a final response after the request has been completed. See <a href="p1-messaging.html#use.of.the.100.status" title="Use of the 100 (Continue) Status">Section 7.2.3</a> of <a href="#Part1" id="rfc.xref.Part1.25"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a> for detailed discussion of the use and handling of this status code. 1557 1529 </p> 1558 1530 <div id="rfc.iref.23"></div> 1559 1531 <div id="rfc.iref.s.3"></div> 1560 1532 <h3 id="rfc.section.8.1.2"><a href="#rfc.section.8.1.2">8.1.2</a> <a id="status.101" href="#status.101">101 Switching Protocols</a></h3> 1561 <p id="rfc.section.8.1.2.p.1">The server understands and is willing to comply with the client's request, via the Upgrade message header field (<a href="p1-messaging.html#header.upgrade" title="Upgrade">Section 9.8</a> of <a href="#Part1" id="rfc.xref.Part1.2 8"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>), for a change in the application protocol being used on this connection. The server will switch protocols to those defined1533 <p id="rfc.section.8.1.2.p.1">The server understands and is willing to comply with the client's request, via the Upgrade message header field (<a href="p1-messaging.html#header.upgrade" title="Upgrade">Section 9.8</a> of <a href="#Part1" id="rfc.xref.Part1.26"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>), for a change in the application protocol being used on this connection. The server will switch protocols to those defined 1562 1534 by the response's Upgrade header field immediately after the empty line which terminates the 101 response. 1563 1535 </p> … … 1582 1554 <dd>a representation containing the request message as received by the end server.</dd> 1583 1555 </dl> 1584 <p id="rfc.section.8.2.1.p.2">Caches <em class="bcp14">MAY</em> use a heuristic (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 2.3.1.1</a> of <a href="#Part6" id="rfc.xref.Part6.1 3"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>) to determine freshness for 200 responses.1556 <p id="rfc.section.8.2.1.p.2">Caches <em class="bcp14">MAY</em> use a heuristic (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 2.3.1.1</a> of <a href="#Part6" id="rfc.xref.Part6.11"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>) to determine freshness for 200 responses. 1585 1557 </p> 1586 1558 <div id="rfc.iref.25"></div> … … 1594 1566 </p> 1595 1567 <p id="rfc.section.8.2.2.p.2">A 201 response <em class="bcp14">MAY</em> contain an ETag response header field indicating the current value of the entity-tag for the representation of the resource 1596 just created (see <a href="p4-conditional.html#header.etag" title="ETag">Section 6.1</a> of <a href="#Part4" id="rfc.xref.Part4. 14"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>).1568 just created (see <a href="p4-conditional.html#header.etag" title="ETag">Section 6.1</a> of <a href="#Part4" id="rfc.xref.Part4.9"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>). 1597 1569 </p> 1598 1570 <div id="rfc.iref.26"></div> … … 1616 1588 when the response would otherwise be 200 (OK). 1617 1589 </p> 1618 <p id="rfc.section.8.2.4.p.2">Caches <em class="bcp14">MAY</em> use a heuristic (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 2.3.1.1</a> of <a href="#Part6" id="rfc.xref.Part6.1 4"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>) to determine freshness for 203 responses.1590 <p id="rfc.section.8.2.4.p.2">Caches <em class="bcp14">MAY</em> use a heuristic (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 2.3.1.1</a> of <a href="#Part6" id="rfc.xref.Part6.12"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>) to determine freshness for 203 responses. 1619 1591 </p> 1620 1592 <div id="rfc.iref.28"></div> … … 1639 1611 another input action. 1640 1612 </p> 1641 <p id="rfc.section.8.2.6.p.2">The message-body included with the response <em class="bcp14">MUST</em> be empty. Note that receivers still need to parse the response according to the algorithm defined in <a href="p1-messaging.html#message.body" title="Message Body">Section 3.3</a> of <a href="#Part1" id="rfc.xref.Part1.2 9"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>.1613 <p id="rfc.section.8.2.6.p.2">The message-body included with the response <em class="bcp14">MUST</em> be empty. Note that receivers still need to parse the response according to the algorithm defined in <a href="p1-messaging.html#message.body" title="Message Body">Section 3.3</a> of <a href="#Part1" id="rfc.xref.Part1.27"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>. 1642 1614 </p> 1643 1615 <div id="rfc.iref.30"></div> … … 1645 1617 <h3 id="rfc.section.8.2.7"><a href="#rfc.section.8.2.7">8.2.7</a> <a id="status.206" href="#status.206">206 Partial Content</a></h3> 1646 1618 <p id="rfc.section.8.2.7.p.1">The server has fulfilled the partial GET request for the resource and the enclosed payload is a partial representation as 1647 defined in <a href="p5-range.html#status.206" title="206 Partial Content">Section 3.1</a> of <a href="#Part5" id="rfc.xref.Part5. 11"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>.1648 </p> 1649 <p id="rfc.section.8.2.7.p.2">Caches <em class="bcp14">MAY</em> use a heuristic (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 2.3.1.1</a> of <a href="#Part6" id="rfc.xref.Part6.1 5"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>) to determine freshness for 206 responses.1619 defined in <a href="p5-range.html#status.206" title="206 Partial Content">Section 3.1</a> of <a href="#Part5" id="rfc.xref.Part5.8"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>. 1620 </p> 1621 <p id="rfc.section.8.2.7.p.2">Caches <em class="bcp14">MAY</em> use a heuristic (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 2.3.1.1</a> of <a href="#Part6" id="rfc.xref.Part6.13"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>) to determine freshness for 206 responses. 1650 1622 </p> 1651 1623 <h2 id="rfc.section.8.3"><a href="#rfc.section.8.3">8.3</a> <a id="status.3xx" href="#status.3xx">Redirection 3xx</a></h2> … … 1662 1634 <h3 id="rfc.section.8.3.1"><a href="#rfc.section.8.3.1">8.3.1</a> <a id="status.300" href="#status.300">300 Multiple Choices</a></h3> 1663 1635 <p id="rfc.section.8.3.1.p.1">The target resource has more than one representation, each with its own specific location, and agent-driven negotiation information 1664 (<a href="p3-payload.html#content.negotiation" title="Content Negotiation">Section 5</a> of <a href="#Part3" id="rfc.xref.Part3. 11"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>) is being provided so that the user (or user agent) can select a preferred representation by redirecting its request to that1636 (<a href="p3-payload.html#content.negotiation" title="Content Negotiation">Section 5</a> of <a href="#Part3" id="rfc.xref.Part3.7"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>) is being provided so that the user (or user agent) can select a preferred representation by redirecting its request to that 1665 1637 location. 1666 1638 </p> … … 1671 1643 <p id="rfc.section.8.3.1.p.3">If the server has a preferred choice of representation, it <em class="bcp14">SHOULD</em> include the specific URI for that representation in the Location field; user agents <em class="bcp14">MAY</em> use the Location field value for automatic redirection. 1672 1644 </p> 1673 <p id="rfc.section.8.3.1.p.4">Caches <em class="bcp14">MAY</em> use a heuristic (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 2.3.1.1</a> of <a href="#Part6" id="rfc.xref.Part6.1 6"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>) to determine freshness for 300 responses.1645 <p id="rfc.section.8.3.1.p.4">Caches <em class="bcp14">MAY</em> use a heuristic (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 2.3.1.1</a> of <a href="#Part6" id="rfc.xref.Part6.14"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>) to determine freshness for 300 responses. 1674 1646 </p> 1675 1647 <div id="rfc.iref.32"></div> … … 1679 1651 request URI to one or more of the new references returned by the server, where possible. 1680 1652 </p> 1681 <p id="rfc.section.8.3.2.p.2">Caches <em class="bcp14">MAY</em> use a heuristic (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 2.3.1.1</a> of <a href="#Part6" id="rfc.xref.Part6.1 7"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>) to determine freshness for 301 responses.1653 <p id="rfc.section.8.3.2.p.2">Caches <em class="bcp14">MAY</em> use a heuristic (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 2.3.1.1</a> of <a href="#Part6" id="rfc.xref.Part6.15"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>) to determine freshness for 301 responses. 1682 1654 </p> 1683 1655 <p id="rfc.section.8.3.2.p.3">The new permanent URI <em class="bcp14">SHOULD</em> be given by the Location field in the response. Unless the request method was HEAD, the representation of the response <em class="bcp14">SHOULD</em> contain a short hypertext note with a hyperlink to the new URI(s). … … 1731 1703 <h3 id="rfc.section.8.3.5"><a href="#rfc.section.8.3.5">8.3.5</a> <a id="status.304" href="#status.304">304 Not Modified</a></h3> 1732 1704 <p id="rfc.section.8.3.5.p.1">The response to the request has not been modified since the conditions indicated by the client's conditional GET request, 1733 as defined in <a href="p4-conditional.html#status.304" title="304 Not Modified">Section 3.1</a> of <a href="#Part4" id="rfc.xref.Part4.1 5"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>.1705 as defined in <a href="p4-conditional.html#status.304" title="304 Not Modified">Section 3.1</a> of <a href="#Part4" id="rfc.xref.Part4.10"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>. 1734 1706 </p> 1735 1707 <div id="rfc.iref.36"></div> … … 1771 1743 <div id="rfc.iref.s.20"></div> 1772 1744 <h3 id="rfc.section.8.4.2"><a href="#rfc.section.8.4.2">8.4.2</a> <a id="status.401" href="#status.401">401 Unauthorized</a></h3> 1773 <p id="rfc.section.8.4.2.p.1">The request requires user authentication (see <a href="p7-auth.html#status.401" title="401 Unauthorized">Section 3.1</a> of <a href="#Part7" id="rfc.xref.Part7. 12"><cite title="HTTP/1.1, part 7: Authentication">[Part7]</cite></a>).1745 <p id="rfc.section.8.4.2.p.1">The request requires user authentication (see <a href="p7-auth.html#status.401" title="401 Unauthorized">Section 3.1</a> of <a href="#Part7" id="rfc.xref.Part7.8"><cite title="HTTP/1.1, part 7: Authentication">[Part7]</cite></a>). 1774 1746 </p> 1775 1747 <div id="rfc.iref.41"></div> … … 1818 1790 <div id="rfc.iref.s.26"></div> 1819 1791 <h3 id="rfc.section.8.4.8"><a href="#rfc.section.8.4.8">8.4.8</a> <a id="status.407" href="#status.407">407 Proxy Authentication Required</a></h3> 1820 <p id="rfc.section.8.4.8.p.1">This code is similar to 401 (Unauthorized), but indicates that the client must first authenticate itself with the proxy (see <a href="p7-auth.html#status.407" title="407 Proxy Authentication Required">Section 3.2</a> of <a href="#Part7" id="rfc.xref.Part7. 13"><cite title="HTTP/1.1, part 7: Authentication">[Part7]</cite></a>).1792 <p id="rfc.section.8.4.8.p.1">This code is similar to 401 (Unauthorized), but indicates that the client must first authenticate itself with the proxy (see <a href="p7-auth.html#status.407" title="407 Proxy Authentication Required">Section 3.2</a> of <a href="#Part7" id="rfc.xref.Part7.9"><cite title="HTTP/1.1, part 7: Authentication">[Part7]</cite></a>). 1821 1793 </p> 1822 1794 <div id="rfc.iref.47"></div> … … 1851 1823 — that is left to the discretion of the server owner. 1852 1824 </p> 1853 <p id="rfc.section.8.4.11.p.3">Caches <em class="bcp14">MAY</em> use a heuristic (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 2.3.1.1</a> of <a href="#Part6" id="rfc.xref.Part6.1 8"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>) to determine freshness for 410 responses.1825 <p id="rfc.section.8.4.11.p.3">Caches <em class="bcp14">MAY</em> use a heuristic (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 2.3.1.1</a> of <a href="#Part6" id="rfc.xref.Part6.16"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>) to determine freshness for 410 responses. 1854 1826 </p> 1855 1827 <div id="rfc.iref.50"></div> … … 1863 1835 <h3 id="rfc.section.8.4.13"><a href="#rfc.section.8.4.13">8.4.13</a> <a id="status.412" href="#status.412">412 Precondition Failed</a></h3> 1864 1836 <p id="rfc.section.8.4.13.p.1">The precondition given in one or more of the header fields evaluated to false when it was tested on the server, as defined 1865 in <a href="p4-conditional.html#status.412" title="412 Precondition Failed">Section 3.2</a> of <a href="#Part4" id="rfc.xref.Part4.1 6"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>.1837 in <a href="p4-conditional.html#status.412" title="412 Precondition Failed">Section 3.2</a> of <a href="#Part4" id="rfc.xref.Part4.11"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>. 1866 1838 </p> 1867 1839 <div id="rfc.iref.52"></div> … … 1891 1863 <div id="rfc.iref.s.35"></div> 1892 1864 <h3 id="rfc.section.8.4.17"><a href="#rfc.section.8.4.17">8.4.17</a> <a id="status.416" href="#status.416">416 Requested Range Not Satisfiable</a></h3> 1893 <p id="rfc.section.8.4.17.p.1">The request included a Range header field (<a href="p5-range.html#header.range" title="Range">Section 5.4</a> of <a href="#Part5" id="rfc.xref.Part5. 12"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>) and none of the range-specifier values in this field overlap the current extent of the selected resource. See <a href="p5-range.html#status.416" title="416 Requested Range Not Satisfiable">Section 3.2</a> of <a href="#Part5" id="rfc.xref.Part5.13"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>.1865 <p id="rfc.section.8.4.17.p.1">The request included a Range header field (<a href="p5-range.html#header.range" title="Range">Section 5.4</a> of <a href="#Part5" id="rfc.xref.Part5.9"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>) and none of the range-specifier values in this field overlap the current extent of the selected resource. See <a href="p5-range.html#status.416" title="416 Requested Range Not Satisfiable">Section 3.2</a> of <a href="#Part5" id="rfc.xref.Part5.10"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>. 1894 1866 </p> 1895 1867 <div id="rfc.iref.56"></div> … … 1902 1874 <div id="rfc.iref.s.37"></div> 1903 1875 <h3 id="rfc.section.8.4.19"><a href="#rfc.section.8.4.19">8.4.19</a> <a id="status.426" href="#status.426">426 Upgrade Required</a></h3> 1904 <p id="rfc.section.8.4.19.p.1">The request can not be completed without a prior protocol upgrade. This response <em class="bcp14">MUST</em> include an Upgrade header field (<a href="p1-messaging.html#header.upgrade" title="Upgrade">Section 9.8</a> of <a href="#Part1" id="rfc.xref.Part1. 30"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) specifying the required protocols.1905 </p> 1906 <div id="rfc.figure.u. 12"></div>1876 <p id="rfc.section.8.4.19.p.1">The request can not be completed without a prior protocol upgrade. This response <em class="bcp14">MUST</em> include an Upgrade header field (<a href="p1-messaging.html#header.upgrade" title="Upgrade">Section 9.8</a> of <a href="#Part1" id="rfc.xref.Part1.28"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) specifying the required protocols. 1877 </p> 1878 <div id="rfc.figure.u.7"></div> 1907 1879 <p>Example:</p> <pre class="text2">HTTP/1.1 426 Upgrade Required 1908 1880 Upgrade: HTTP/2.0 … … 1959 1931 <p id="rfc.section.8.5.6.p.1">The server does not support, or refuses to support, the protocol version that was used in the request message. The server 1960 1932 is indicating that it is unable or unwilling to complete the request using the same major version as the client, as described 1961 in <a href="p1-messaging.html#http.version" title="Protocol Versioning">Section 2.5</a> of <a href="#Part1" id="rfc.xref.Part1. 31"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, 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.1933 in <a href="p1-messaging.html#http.version" title="Protocol Versioning">Section 2.5</a> of <a href="#Part1" id="rfc.xref.Part1.29"><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. 1962 1934 </p> 1963 1935 <h1 id="rfc.section.9"><a href="#rfc.section.9">9.</a> <a id="header.fields" href="#header.fields">Header Field Definitions</a></h1> … … 1969 1941 is strictly to inform the recipient of valid request methods associated with the resource. 1970 1942 </p> 1971 <div id="rfc.figure.u. 13"></div><pre class="inline"><span id="rfc.iref.g.6"></span><span id="rfc.iref.g.7"></span> <a href="#header.allow" class="smpl">Allow</a> = "Allow" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.allow" class="smpl">Allow-v</a>1943 <div id="rfc.figure.u.8"></div><pre class="inline"><span id="rfc.iref.g.6"></span><span id="rfc.iref.g.7"></span> <a href="#header.allow" class="smpl">Allow</a> = "Allow" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.allow" class="smpl">Allow-v</a> 1972 1944 <a href="#header.allow" class="smpl">Allow-v</a> = #<a href="#method" class="smpl">Method</a> 1973 1945 </pre><p id="rfc.section.9.1.p.3">Example of use:</p> 1974 <div id="rfc.figure.u. 14"></div><pre class="text"> Allow: GET, HEAD, PUT1946 <div id="rfc.figure.u.9"></div><pre class="text"> Allow: GET, HEAD, PUT 1975 1947 </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> 1976 1948 <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 … … 1981 1953 <h2 id="rfc.section.9.2"><a href="#rfc.section.9.2">9.2</a> <a id="header.expect" href="#header.expect">Expect</a></h2> 1982 1954 <p id="rfc.section.9.2.p.1">The "Expect" header field is used to indicate that particular server behaviors are required by the client.</p> 1983 <div id="rfc.figure.u.1 5"></div><pre class="inline"><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> <a href="#header.expect" class="smpl">Expect</a> = "Expect" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.expect" class="smpl">Expect-v</a>1955 <div id="rfc.figure.u.10"></div><pre class="inline"><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> <a href="#header.expect" class="smpl">Expect</a> = "Expect" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.expect" class="smpl">Expect-v</a> 1984 1956 <a href="#header.expect" class="smpl">Expect-v</a> = 1#<a href="#header.expect" class="smpl">expectation</a> 1985 1957 … … 2001 1973 </p> 2002 1974 <p id="rfc.section.9.2.p.7">Many older HTTP/1.0 and HTTP/1.1 applications do not understand the Expect header field.</p> 2003 <p id="rfc.section.9.2.p.8">See <a href="p1-messaging.html#use.of.the.100.status" title="Use of the 100 (Continue) Status">Section 7.2.3</a> of <a href="#Part1" id="rfc.xref.Part1.3 2"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a> for the use of the 100 (Continue) status code.1975 <p id="rfc.section.9.2.p.8">See <a href="p1-messaging.html#use.of.the.100.status" title="Use of the 100 (Continue) Status">Section 7.2.3</a> of <a href="#Part1" id="rfc.xref.Part1.30"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a> for the use of the 100 (Continue) status code. 2004 1976 </p> 2005 1977 <div id="rfc.iref.f.1"></div> … … 2008 1980 <p id="rfc.section.9.3.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.1"><cite title="Internet Message Format">[RFC5322]</cite></a>: 2009 1981 </p> 2010 <div id="rfc.figure.u.1 6"></div><pre class="inline"><span id="rfc.iref.g.13"></span><span id="rfc.iref.g.14"></span> <a href="#header.from" class="smpl">From</a> = "From" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.from" class="smpl">From-v</a>1982 <div id="rfc.figure.u.11"></div><pre class="inline"><span id="rfc.iref.g.13"></span><span id="rfc.iref.g.14"></span> <a href="#header.from" class="smpl">From</a> = "From" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.from" class="smpl">From-v</a> 2011 1983 <a href="#header.from" class="smpl">From-v</a> = <a href="#header.from" class="smpl">mailbox</a> 2012 1984 2013 1985 <a href="#header.from" class="smpl">mailbox</a> = <mailbox, defined in <a href="#RFC5322" id="rfc.xref.RFC5322.2"><cite title="Internet Message Format">[RFC5322]</cite></a>, <a href="http://tools.ietf.org/html/rfc5322#section-3.4">Section 3.4</a>> 2014 1986 </pre><p id="rfc.section.9.3.p.3">An example is:</p> 2015 <div id="rfc.figure.u.1 7"></div><pre class="text"> From: webmaster@example.org1987 <div id="rfc.figure.u.12"></div><pre class="text"> From: webmaster@example.org 2016 1988 </pre><p id="rfc.section.9.3.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 2017 1989 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 … … 2036 2008 <p id="rfc.section.9.4.p.3">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>). 2037 2009 </p> 2038 <div id="rfc.figure.u.1 8"></div><pre class="inline"><span id="rfc.iref.g.15"></span><span id="rfc.iref.g.16"></span> <a href="#header.location" class="smpl">Location</a> = "Location" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.location" class="smpl">Location-v</a>2010 <div id="rfc.figure.u.13"></div><pre class="inline"><span id="rfc.iref.g.15"></span><span id="rfc.iref.g.16"></span> <a href="#header.location" class="smpl">Location</a> = "Location" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.location" class="smpl">Location-v</a> 2039 2011 <a href="#header.location" class="smpl">Location-v</a> = <a href="#abnf.dependencies" class="smpl">URI-reference</a> 2040 </pre><div id="rfc.figure.u.1 9"></div>2012 </pre><div id="rfc.figure.u.14"></div> 2041 2013 <p>Examples are:</p> <pre class="text"> Location: http://www.example.org/pub/WWW/People.html#tim 2042 </pre><div id="rfc.figure.u. 20"></div><pre class="text"> Location: /index.html2014 </pre><div id="rfc.figure.u.15"></div><pre class="text"> Location: /index.html 2043 2015 </pre><p id="rfc.section.9.4.p.7">There are circumstances in which a fragment identifier in a Location URI would not be appropriate: </p> 2044 2016 <ul> … … 2053 2025 </div> 2054 2026 <div class="note" id="rfc.section.9.4.p.9"> 2055 <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. 12"><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.2027 <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.8"><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. 2056 2028 It is therefore possible for a response to contain header fields for both Location and Content-Location. 2057 2029 </p> … … 2063 2035 is attempting to trace a request which appears to be failing or looping in mid-chain. 2064 2036 </p> 2065 <div id="rfc.figure.u. 21"></div><pre class="inline"><span id="rfc.iref.g.17"></span><span id="rfc.iref.g.18"></span> <a href="#header.max-forwards" class="smpl">Max-Forwards</a> = "Max-Forwards" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.max-forwards" class="smpl">Max-Forwards-v</a>2037 <div id="rfc.figure.u.16"></div><pre class="inline"><span id="rfc.iref.g.17"></span><span id="rfc.iref.g.18"></span> <a href="#header.max-forwards" class="smpl">Max-Forwards</a> = "Max-Forwards" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.max-forwards" class="smpl">Max-Forwards-v</a> 2066 2038 <a href="#header.max-forwards" class="smpl">Max-Forwards-v</a> = 1*<a href="#notation" class="smpl">DIGIT</a> 2067 2039 </pre><p id="rfc.section.9.5.p.3">The Max-Forwards value is a decimal integer indicating the remaining number of times this request message can be forwarded.</p> … … 2084 2056 non-HTTP URIs (e.g., FTP). 2085 2057 </p> 2086 <div id="rfc.figure.u. 22"></div><pre class="inline"><span id="rfc.iref.g.19"></span><span id="rfc.iref.g.20"></span> <a href="#header.referer" class="smpl">Referer</a> = "Referer" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.referer" class="smpl">Referer-v</a>2058 <div id="rfc.figure.u.17"></div><pre class="inline"><span id="rfc.iref.g.19"></span><span id="rfc.iref.g.20"></span> <a href="#header.referer" class="smpl">Referer</a> = "Referer" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.referer" class="smpl">Referer-v</a> 2087 2059 <a href="#header.referer" class="smpl">Referer-v</a> = <a href="#abnf.dependencies" class="smpl">absolute-URI</a> / <a href="#abnf.dependencies" class="smpl">partial-URI</a> 2088 2060 </pre><p id="rfc.section.9.6.p.5">Example:</p> 2089 <div id="rfc.figure.u. 23"></div><pre class="text"> Referer: http://www.example.org/hypertext/Overview.html2061 <div id="rfc.figure.u.18"></div><pre class="text"> Referer: http://www.example.org/hypertext/Overview.html 2090 2062 </pre><p id="rfc.section.9.6.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. 2091 2063 </p> … … 2098 2070 </p> 2099 2071 <p id="rfc.section.9.7.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> 2100 <div id="rfc.figure.u. 24"></div><pre class="inline"><span id="rfc.iref.g.21"></span><span id="rfc.iref.g.22"></span> <a href="#header.retry-after" class="smpl">Retry-After</a> = "Retry-After" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.retry-after" class="smpl">Retry-After-v</a>2072 <div id="rfc.figure.u.19"></div><pre class="inline"><span id="rfc.iref.g.21"></span><span id="rfc.iref.g.22"></span> <a href="#header.retry-after" class="smpl">Retry-After</a> = "Retry-After" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.retry-after" class="smpl">Retry-After-v</a> 2101 2073 <a href="#header.retry-after" class="smpl">Retry-After-v</a> = <a href="#abnf.dependencies" class="smpl">HTTP-date</a> / <a href="#rule.delta-seconds" class="smpl">delta-seconds</a> 2102 2074 </pre><div id="rule.delta-seconds"> 2103 2075 <p id="rfc.section.9.7.p.4"> Time spans are non-negative decimal integers, representing time in seconds.</p> 2104 2076 </div> 2105 <div id="rfc.figure.u.2 5"></div><pre class="inline"><span id="rfc.iref.g.23"></span> <a href="#rule.delta-seconds" class="smpl">delta-seconds</a> = 1*<a href="#notation" class="smpl">DIGIT</a>2077 <div id="rfc.figure.u.20"></div><pre class="inline"><span id="rfc.iref.g.23"></span> <a href="#rule.delta-seconds" class="smpl">delta-seconds</a> = 1*<a href="#notation" class="smpl">DIGIT</a> 2106 2078 </pre><p id="rfc.section.9.7.p.6">Two examples of its use are</p> 2107 <div id="rfc.figure.u.2 6"></div><pre class="text"> Retry-After: Fri, 31 Dec 1999 23:59:59 GMT2079 <div id="rfc.figure.u.21"></div><pre class="text"> Retry-After: Fri, 31 Dec 1999 23:59:59 GMT 2108 2080 Retry-After: 120 2109 2081 </pre><p id="rfc.section.9.7.p.8">In the latter example, the delay is 2 minutes.</p> … … 2112 2084 <h2 id="rfc.section.9.8"><a href="#rfc.section.9.8">9.8</a> <a id="header.server" href="#header.server">Server</a></h2> 2113 2085 <p id="rfc.section.9.8.p.1">The "Server" header field contains information about the software used by the origin server to handle the request.</p> 2114 <p id="rfc.section.9.8.p.2">The field can contain multiple product tokens (<a href="p1-messaging.html#product.tokens" title="Product Tokens">Section 6.3</a> of <a href="#Part1" id="rfc.xref.Part1.3 3"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></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.34"><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 for2086 <p id="rfc.section.9.8.p.2">The field can contain multiple product tokens (<a href="p1-messaging.html#product.tokens" title="Product Tokens">Section 6.3</a> of <a href="#Part1" id="rfc.xref.Part1.31"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) and comments (<a href="p1-messaging.html#header.fields" title="Header Fields">Section 3.2</a> of <a href="#Part1" id="rfc.xref.Part1.32"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) identifying the server and any significant subproducts. The product tokens are listed in order of their significance for 2115 2087 identifying the application. 2116 2088 </p> 2117 <div id="rfc.figure.u.2 7"></div><pre class="inline"><span id="rfc.iref.g.24"></span><span id="rfc.iref.g.25"></span> <a href="#header.server" class="smpl">Server</a> = "Server" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.server" class="smpl">Server-v</a>2089 <div id="rfc.figure.u.22"></div><pre class="inline"><span id="rfc.iref.g.24"></span><span id="rfc.iref.g.25"></span> <a href="#header.server" class="smpl">Server</a> = "Server" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.server" class="smpl">Server-v</a> 2118 2090 <a href="#header.server" class="smpl">Server-v</a> = <a href="#abnf.dependencies" class="smpl">product</a> 2119 2091 *( <a href="#core.rules" class="smpl">RWS</a> ( <a href="#abnf.dependencies" class="smpl">product</a> / <a href="#abnf.dependencies" class="smpl">comment</a> ) ) 2120 2092 </pre><p id="rfc.section.9.8.p.4">Example:</p> 2121 <div id="rfc.figure.u.2 8"></div><pre class="text"> Server: CERN/3.0 libwww/2.172122 </pre><p id="rfc.section.9.8.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 9.9</a> of <a href="#Part1" id="rfc.xref.Part1.3 5"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>).2093 <div id="rfc.figure.u.23"></div><pre class="text"> Server: CERN/3.0 libwww/2.17 2094 </pre><p id="rfc.section.9.8.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 9.9</a> of <a href="#Part1" id="rfc.xref.Part1.33"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>). 2123 2095 </p> 2124 2096 <div class="note" id="rfc.section.9.8.p.7"> … … 2136 2108 user agent limitations. 2137 2109 </p> 2138 <p id="rfc.section.9.9.p.3">The field can contain multiple product tokens (<a href="p1-messaging.html#product.tokens" title="Product Tokens">Section 6.3</a> of <a href="#Part1" id="rfc.xref.Part1.3 6"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) and comments (<a href="p1-messaging.html#header.fields" title="Header Fields">Section 3.2</a> of <a href="#Part1" id="rfc.xref.Part1.37"><cite title="HTTP/1.1, part 1: 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 significance2110 <p id="rfc.section.9.9.p.3">The field can contain multiple product tokens (<a href="p1-messaging.html#product.tokens" title="Product Tokens">Section 6.3</a> of <a href="#Part1" id="rfc.xref.Part1.34"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) and comments (<a href="p1-messaging.html#header.fields" title="Header Fields">Section 3.2</a> of <a href="#Part1" id="rfc.xref.Part1.35"><cite title="HTTP/1.1, part 1: 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 2139 2111 for identifying the application. 2140 2112 </p> … … 2147 2119 doing so makes the field value more difficult to parse. 2148 2120 </p> 2149 <div id="rfc.figure.u.2 9"></div><pre class="inline"><span id="rfc.iref.g.26"></span><span id="rfc.iref.g.27"></span> <a href="#header.user-agent" class="smpl">User-Agent</a> = "User-Agent" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.user-agent" class="smpl">User-Agent-v</a>2121 <div id="rfc.figure.u.24"></div><pre class="inline"><span id="rfc.iref.g.26"></span><span id="rfc.iref.g.27"></span> <a href="#header.user-agent" class="smpl">User-Agent</a> = "User-Agent" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.user-agent" class="smpl">User-Agent-v</a> 2150 2122 <a href="#header.user-agent" class="smpl">User-Agent-v</a> = <a href="#abnf.dependencies" class="smpl">product</a> *( <a href="#core.rules" class="smpl">RWS</a> ( <a href="#abnf.dependencies" class="smpl">product</a> / <a href="#abnf.dependencies" class="smpl">comment</a> ) ) 2151 2123 </pre><p id="rfc.section.9.9.p.7">Example:</p> 2152 <div id="rfc.figure.u. 30"></div><pre class="text"> User-Agent: CERN-LineMode/2.15 libwww/2.17b32124 <div id="rfc.figure.u.25"></div><pre class="text"> User-Agent: CERN-LineMode/2.15 libwww/2.17b3 2153 2125 </pre><h1 id="rfc.section.10"><a href="#rfc.section.10">10.</a> <a id="IANA.considerations" href="#IANA.considerations">IANA Considerations</a></h1> 2154 2126 <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> … … 2745 2717 </p> 2746 2718 <p id="rfc.section.A.p.12">In the description of the Server header field, the Via field was described as a SHOULD. The requirement was and is stated 2747 correctly in the description of the Via header field in <a href="p1-messaging.html#header.via" title="Via">Section 9.9</a> of <a href="#Part1" id="rfc.xref.Part1.3 8"><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.8</a>)2719 correctly in the description of the Via header field in <a href="p1-messaging.html#header.via" title="Via">Section 9.9</a> of <a href="#Part1" id="rfc.xref.Part1.36"><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.8</a>) 2748 2720 </p> 2749 2721 <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a> <a id="collected.abnf" href="#collected.abnf">Collected ABNF</a></h1> 2750 <div id="rfc.figure.u.31"></div> <pre class="inline"><a href="#abnf.dependencies" class="smpl">Accept</a> = <Accept, defined in [Part3], Section 6.1> 2751 <a href="#abnf.dependencies" class="smpl">Accept-Charset</a> = <Accept-Charset, defined in [Part3], Section 6.2> 2752 <a href="#abnf.dependencies" class="smpl">Accept-Encoding</a> = <Accept-Encoding, defined in [Part3], Section 6.3> 2753 <a href="#abnf.dependencies" class="smpl">Accept-Language</a> = <Accept-Language, defined in [Part3], Section 6.4> 2754 <a href="#abnf.dependencies" class="smpl">Accept-Ranges</a> = <Accept-Ranges, defined in [Part5], Section 5.1> 2755 <a href="#abnf.dependencies" class="smpl">Age</a> = <Age, defined in [Part6], Section 3.1> 2756 <a href="#header.allow" class="smpl">Allow</a> = "Allow:" OWS Allow-v 2722 <div id="rfc.figure.u.26"></div> <pre class="inline"><a href="#header.allow" class="smpl">Allow</a> = "Allow:" OWS Allow-v 2757 2723 <a href="#header.allow" class="smpl">Allow-v</a> = [ ( "," / Method ) *( OWS "," [ OWS Method ] ) ] 2758 <a href="#abnf.dependencies" class="smpl">Authorization</a> = <Authorization, defined in [Part7], Section 4.1>2759 2724 2760 <a href="#abnf.dependencies" class="smpl">ETag</a> = <ETag, defined in [Part4], Section 6.1>2761 2725 <a href="#header.expect" class="smpl">Expect</a> = "Expect:" OWS Expect-v 2762 2726 <a href="#header.expect" class="smpl">Expect-v</a> = *( "," OWS ) expectation *( OWS "," [ OWS expectation ] ) … … 2766 2730 2767 2731 <a href="#abnf.dependencies" class="smpl">HTTP-date</a> = <HTTP-date, defined in [Part1], Section 6.1> 2768 <a href="#abnf.dependencies" class="smpl">Host</a> = <Host, defined in [Part1], Section 2.6>2769 2770 <a href="#abnf.dependencies" class="smpl">If-Match</a> = <If-Match, defined in [Part4], Section 6.2>2771 If-Modified-Since =2772 <If-Modified-Since, defined in [Part4], Section 6.3>2773 <a href="#abnf.dependencies" class="smpl">If-None-Match</a> = <If-None-Match, defined in [Part4], Section 6.4>2774 <a href="#abnf.dependencies" class="smpl">If-Range</a> = <If-Range, defined in [Part5], Section 5.3>2775 If-Unmodified-Since =2776 <If-Unmodified-Since, defined in [Part4], Section 6.5>2777 2732 2778 2733 <a href="#header.location" class="smpl">Location</a> = "Location:" OWS Location-v … … 2785 2740 <a href="#core.rules" class="smpl">OWS</a> = <OWS, defined in [Part1], Section 1.2.2> 2786 2741 2787 Proxy-Authenticate =2788 <Proxy-Authenticate, defined in [Part7], Section 4.2>2789 Proxy-Authorization =2790 <Proxy-Authorization, defined in [Part7], Section 4.3>2791 2792 2742 <a href="#core.rules" class="smpl">RWS</a> = <RWS, defined in [Part1], Section 1.2.2> 2793 <a href="#abnf.dependencies" class="smpl">Range</a> = <Range, defined in [Part5], Section 5.4>2794 2743 <a href="#status.code.and.reason.phrase" class="smpl">Reason-Phrase</a> = *( WSP / VCHAR / obs-text ) 2795 2744 <a href="#header.referer" class="smpl">Referer</a> = "Referer:" OWS Referer-v … … 2802 2751 <a href="#status.code.and.reason.phrase" class="smpl">Status-Code</a> = 3DIGIT 2803 2752 2804 <a href="#abnf.dependencies" class="smpl">TE</a> = <TE, defined in [Part1], Section 9.5>2805 2806 2753 <a href="#abnf.dependencies" class="smpl">URI-reference</a> = <URI-reference, defined in [Part1], Section 2.6> 2807 2754 <a href="#header.user-agent" class="smpl">User-Agent</a> = "User-Agent:" OWS User-Agent-v 2808 2755 <a href="#header.user-agent" class="smpl">User-Agent-v</a> = product *( RWS ( product / comment ) ) 2809 2810 <a href="#abnf.dependencies" class="smpl">Vary</a> = <Vary, defined in [Part6], Section 3.5>2811 2812 WWW-Authenticate =2813 <WWW-Authenticate, defined in [Part7], Section 4.4>2814 2756 2815 2757 <a href="#abnf.dependencies" class="smpl">absolute-URI</a> = <absolute-URI, defined in [Part1], Section 2.6> … … 2834 2776 2835 2777 <a href="#core.rules" class="smpl">token</a> = <token, defined in [Part1], Section 1.2.2> 2836 </pre> <div id="rfc.figure.u.32"></div> 2837 <p>ABNF diagnostics:</p><pre class="inline">; Accept defined but not used 2838 ; Accept-Charset defined but not used 2839 ; Accept-Encoding defined but not used 2840 ; Accept-Language defined but not used 2841 ; Accept-Ranges defined but not used 2842 ; Age defined but not used 2843 ; Allow defined but not used 2844 ; Authorization defined but not used 2845 ; ETag defined but not used 2778 </pre> <div id="rfc.figure.u.27"></div> 2779 <p>ABNF diagnostics:</p><pre class="inline">; Allow defined but not used 2846 2780 ; Expect defined but not used 2847 2781 ; From defined but not used 2848 ; Host defined but not used2849 ; If-Match defined but not used2850 ; If-Modified-Since defined but not used2851 ; If-None-Match defined but not used2852 ; If-Range defined but not used2853 ; If-Unmodified-Since defined but not used2854 2782 ; Location defined but not used 2855 2783 ; Max-Forwards defined but not used 2856 ; Proxy-Authenticate defined but not used2857 ; Proxy-Authorization defined but not used2858 ; Range defined but not used2859 2784 ; Reason-Phrase defined but not used 2860 2785 ; Referer defined but not used … … 2862 2787 ; Server defined but not used 2863 2788 ; Status-Code defined but not used 2864 ; TE defined but not used2865 2789 ; User-Agent defined but not used 2866 ; Vary defined but not used2867 ; WWW-Authenticate defined but not used2868 2790 </pre><h1 id="rfc.section.C"><a href="#rfc.section.C">C.</a> <a id="change.log" href="#change.log">Change Log (to be removed by RFC Editor before publication)</a></h1> 2869 2791 <h2 id="rfc.section.C.1"><a href="#rfc.section.C.1">C.1</a> Since RFC 2616 … … 2894 2816 <p id="rfc.section.C.2.p.2">Other changes: </p> 2895 2817 <ul> 2896 <li>Move definitions of 304 and 412 condition codes to <a href="#Part4" id="rfc.xref.Part4.1 7"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>2818 <li>Move definitions of 304 and 412 condition codes to <a href="#Part4" id="rfc.xref.Part4.12"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a> 2897 2819 </li> 2898 2820 </ul> … … 3267 3189 </li> 3268 3190 <li><a id="rfc.index.P" href="#rfc.index.P"><b>P</b></a><ul> 3269 <li><em>Part1</em> <a href="#rfc.xref.Part1.1">1</a>, <a href="#rfc.xref.Part1.2">1.2</a>, <a href="#rfc.xref.Part1.3">1.2.1</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.2</a>, <a href="#rfc.xref.Part1.10">1.2.2</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"> 1.2.2</a>, <a href="#rfc.xref.Part1.16">1.2.2</a>, <a href="#rfc.xref.Part1.17">2</a>, <a href="#rfc.xref.Part1.18">2.2.1</a>, <a href="#rfc.xref.Part1.19">3</a>, <a href="#rfc.xref.Part1.20">3</a>, <a href="#rfc.xref.Part1.21">5</a>, <a href="#rfc.xref.Part1.22">6</a>, <a href="#rfc.xref.Part1.23">6.1</a>, <a href="#rfc.xref.Part1.24">7.8</a>, <a href="#rfc.xref.Part1.25">7.8</a>, <a href="#rfc.xref.Part1.26">7.9</a>, <a href="#rfc.xref.Part1.27">8.1.1</a>, <a href="#rfc.xref.Part1.28">8.1.2</a>, <a href="#rfc.xref.Part1.29">8.2.6</a>, <a href="#rfc.xref.Part1.30">8.4.19</a>, <a href="#rfc.xref.Part1.31">8.5.6</a>, <a href="#rfc.xref.Part1.32">9.2</a>, <a href="#rfc.xref.Part1.33">9.8</a>, <a href="#rfc.xref.Part1.34">9.8</a>, <a href="#rfc.xref.Part1.35">9.8</a>, <a href="#rfc.xref.Part1.36">9.9</a>, <a href="#rfc.xref.Part1.37">9.9</a>, <a href="#Part1"><b>13.1</b></a>, <a href="#rfc.xref.Part1.38">A</a><ul>3191 <li><em>Part1</em> <a href="#rfc.xref.Part1.1">1</a>, <a href="#rfc.xref.Part1.2">1.2</a>, <a href="#rfc.xref.Part1.3">1.2.1</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.2</a>, <a href="#rfc.xref.Part1.10">1.2.2</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</a>, <a href="#rfc.xref.Part1.19">5</a>, <a href="#rfc.xref.Part1.20">6</a>, <a href="#rfc.xref.Part1.21">6.1</a>, <a href="#rfc.xref.Part1.22">7.8</a>, <a href="#rfc.xref.Part1.23">7.8</a>, <a href="#rfc.xref.Part1.24">7.9</a>, <a href="#rfc.xref.Part1.25">8.1.1</a>, <a href="#rfc.xref.Part1.26">8.1.2</a>, <a href="#rfc.xref.Part1.27">8.2.6</a>, <a href="#rfc.xref.Part1.28">8.4.19</a>, <a href="#rfc.xref.Part1.29">8.5.6</a>, <a href="#rfc.xref.Part1.30">9.2</a>, <a href="#rfc.xref.Part1.31">9.8</a>, <a href="#rfc.xref.Part1.32">9.8</a>, <a href="#rfc.xref.Part1.33">9.8</a>, <a href="#rfc.xref.Part1.34">9.9</a>, <a href="#rfc.xref.Part1.35">9.9</a>, <a href="#Part1"><b>13.1</b></a>, <a href="#rfc.xref.Part1.36">A</a><ul> 3270 3192 <li><em>Section 1.2</em> <a href="#rfc.xref.Part1.2">1.2</a></li> 3271 3193 <li><em>Section 1.2.2</em> <a href="#rfc.xref.Part1.3">1.2.1</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></li> 3272 <li><em>Section 2.5</em> <a href="#rfc.xref.Part1. 31">8.5.6</a></li>3273 <li><em>Section 2.6</em> <a href="#rfc.xref.Part1.9">1.2.2</a>, <a href="#rfc.xref.Part1.1 1">1.2.2</a>, <a href="#rfc.xref.Part1.13">1.2.2</a>, <a href="#rfc.xref.Part1.16">1.2.2</a></li>3274 <li><em>Section 3.2</em> <a href="#rfc.xref.Part1.10">1.2.2</a>, <a href="#rfc.xref.Part1.3 4">9.8</a>, <a href="#rfc.xref.Part1.37">9.9</a></li>3275 <li><em>Section 3.3</em> <a href="#rfc.xref.Part1.1 8">2.2.1</a>, <a href="#rfc.xref.Part1.22">6</a>, <a href="#rfc.xref.Part1.29">8.2.6</a></li>3276 <li><em>Section 4.1.2</em> <a href="#rfc.xref.Part1.2 6">7.9</a></li>3277 <li><em>Section 4.3</em> <a href="#rfc.xref.Part1.1 7">2</a>, <a href="#rfc.xref.Part1.21">5</a>, <a href="#rfc.xref.Part1.23">6.1</a></li>3278 <li><em>Section 6.1</em> <a href="#rfc.xref.Part1.1 2">1.2.2</a></li>3279 <li><em>Section 6.3</em> <a href="#rfc.xref.Part1.1 4">1.2.2</a>, <a href="#rfc.xref.Part1.33">9.8</a>, <a href="#rfc.xref.Part1.36">9.9</a></li>3280 <li><em>Section 7.2.3</em> <a href="#rfc.xref.Part1.2 7">8.1.1</a>, <a href="#rfc.xref.Part1.32">9.2</a></li>3281 <li><em>Section 9.4</em> <a href="#rfc.xref.Part1.1 9">3</a></li>3282 <li><em>Section 9.5</em> <a href="#rfc.xref.Part1.1 5">1.2.2</a>, <a href="#rfc.xref.Part1.20">3</a></li>3283 <li><em>Section 9.8</em> <a href="#rfc.xref.Part1.2 8">8.1.2</a>, <a href="#rfc.xref.Part1.30">8.4.19</a></li>3284 <li><em>Section 9.9</em> <a href="#rfc.xref.Part1.2 4">7.8</a>, <a href="#rfc.xref.Part1.35">9.8</a>, <a href="#rfc.xref.Part1.38">A</a></li>3285 <li><em>Section 10.3.1</em> <a href="#rfc.xref.Part1.2 5">7.8</a></li>3194 <li><em>Section 2.5</em> <a href="#rfc.xref.Part1.29">8.5.6</a></li> 3195 <li><em>Section 2.6</em> <a href="#rfc.xref.Part1.9">1.2.2</a>, <a href="#rfc.xref.Part1.12">1.2.2</a>, <a href="#rfc.xref.Part1.14">1.2.2</a></li> 3196 <li><em>Section 3.2</em> <a href="#rfc.xref.Part1.10">1.2.2</a>, <a href="#rfc.xref.Part1.32">9.8</a>, <a href="#rfc.xref.Part1.35">9.9</a></li> 3197 <li><em>Section 3.3</em> <a href="#rfc.xref.Part1.16">2.2.1</a>, <a href="#rfc.xref.Part1.20">6</a>, <a href="#rfc.xref.Part1.27">8.2.6</a></li> 3198 <li><em>Section 4.1.2</em> <a href="#rfc.xref.Part1.24">7.9</a></li> 3199 <li><em>Section 4.3</em> <a href="#rfc.xref.Part1.15">2</a>, <a href="#rfc.xref.Part1.19">5</a>, <a href="#rfc.xref.Part1.21">6.1</a></li> 3200 <li><em>Section 6.1</em> <a href="#rfc.xref.Part1.11">1.2.2</a></li> 3201 <li><em>Section 6.3</em> <a href="#rfc.xref.Part1.13">1.2.2</a>, <a href="#rfc.xref.Part1.31">9.8</a>, <a href="#rfc.xref.Part1.34">9.9</a></li> 3202 <li><em>Section 7.2.3</em> <a href="#rfc.xref.Part1.25">8.1.1</a>, <a href="#rfc.xref.Part1.30">9.2</a></li> 3203 <li><em>Section 9.4</em> <a href="#rfc.xref.Part1.17">3</a></li> 3204 <li><em>Section 9.5</em> <a href="#rfc.xref.Part1.18">3</a></li> 3205 <li><em>Section 9.8</em> <a href="#rfc.xref.Part1.26">8.1.2</a>, <a href="#rfc.xref.Part1.28">8.4.19</a></li> 3206 <li><em>Section 9.9</em> <a href="#rfc.xref.Part1.22">7.8</a>, <a href="#rfc.xref.Part1.33">9.8</a>, <a href="#rfc.xref.Part1.36">A</a></li> 3207 <li><em>Section 10.3.1</em> <a href="#rfc.xref.Part1.23">7.8</a></li> 3286 3208 </ul> 3287 3209 </li> 3288 <li><em>Part3</em> <a href="#rfc.xref.Part3.1"> 1.2.2</a>, <a href="#rfc.xref.Part3.2">1.2.2</a>, <a href="#rfc.xref.Part3.3">1.2.2</a>, <a href="#rfc.xref.Part3.4">1.2.2</a>, <a href="#rfc.xref.Part3.5">3</a>, <a href="#rfc.xref.Part3.6">3</a>, <a href="#rfc.xref.Part3.7">3</a>, <a href="#rfc.xref.Part3.8">3</a>, <a href="#rfc.xref.Part3.9">6</a>, <a href="#rfc.xref.Part3.10">7.5</a>, <a href="#rfc.xref.Part3.11">8.3.1</a>, <a href="#rfc.xref.Part3.12">9.4</a>, <a href="#Part3"><b>13.1</b></a><ul>3289 <li><em>Section 5</em> <a href="#rfc.xref.Part3. 11">8.3.1</a></li>3290 <li><em>Section 6.1</em> <a href="#rfc.xref.Part3.1"> 1.2.2</a>, <a href="#rfc.xref.Part3.5">3</a></li>3291 <li><em>Section 6.2</em> <a href="#rfc.xref.Part3.2"> 1.2.2</a>, <a href="#rfc.xref.Part3.6">3</a></li>3292 <li><em>Section 6.3</em> <a href="#rfc.xref.Part3.3"> 1.2.2</a>, <a href="#rfc.xref.Part3.7">3</a></li>3293 <li><em>Section 6.4</em> <a href="#rfc.xref.Part3.4"> 1.2.2</a>, <a href="#rfc.xref.Part3.8">3</a></li>3294 <li><em>Section 6.7</em> <a href="#rfc.xref.Part3. 10">7.5</a>, <a href="#rfc.xref.Part3.12">9.4</a></li>3210 <li><em>Part3</em> <a href="#rfc.xref.Part3.1">3</a>, <a href="#rfc.xref.Part3.2">3</a>, <a href="#rfc.xref.Part3.3">3</a>, <a href="#rfc.xref.Part3.4">3</a>, <a href="#rfc.xref.Part3.5">6</a>, <a href="#rfc.xref.Part3.6">7.5</a>, <a href="#rfc.xref.Part3.7">8.3.1</a>, <a href="#rfc.xref.Part3.8">9.4</a>, <a href="#Part3"><b>13.1</b></a><ul> 3211 <li><em>Section 5</em> <a href="#rfc.xref.Part3.7">8.3.1</a></li> 3212 <li><em>Section 6.1</em> <a href="#rfc.xref.Part3.1">3</a></li> 3213 <li><em>Section 6.2</em> <a href="#rfc.xref.Part3.2">3</a></li> 3214 <li><em>Section 6.3</em> <a href="#rfc.xref.Part3.3">3</a></li> 3215 <li><em>Section 6.4</em> <a href="#rfc.xref.Part3.4">3</a></li> 3216 <li><em>Section 6.7</em> <a href="#rfc.xref.Part3.6">7.5</a>, <a href="#rfc.xref.Part3.8">9.4</a></li> 3295 3217 </ul> 3296 3218 </li> 3297 <li><em>Part4</em> <a href="#rfc.xref.Part4.1"> 1.2.2</a>, <a href="#rfc.xref.Part4.2">1.2.2</a>, <a href="#rfc.xref.Part4.3">1.2.2</a>, <a href="#rfc.xref.Part4.4">1.2.2</a>, <a href="#rfc.xref.Part4.5">1.2.2</a>, <a href="#rfc.xref.Part4.6">3</a>, <a href="#rfc.xref.Part4.7">3</a>, <a href="#rfc.xref.Part4.8">3</a>, <a href="#rfc.xref.Part4.9">3</a>, <a href="#rfc.xref.Part4.10">4.1</a>, <a href="#rfc.xref.Part4.11">4.1</a>, <a href="#rfc.xref.Part4.12">4.1</a>, <a href="#rfc.xref.Part4.13">5</a>, <a href="#rfc.xref.Part4.14">8.2.2</a>, <a href="#rfc.xref.Part4.15">8.3.5</a>, <a href="#rfc.xref.Part4.16">8.4.13</a>, <a href="#Part4"><b>13.1</b></a>, <a href="#rfc.xref.Part4.17">C.2</a><ul>3298 <li><em>Section 3</em> <a href="#rfc.xref.Part4. 10">4.1</a></li>3299 <li><em>Section 3.1</em> <a href="#rfc.xref.Part4. 11">4.1</a>, <a href="#rfc.xref.Part4.15">8.3.5</a></li>3300 <li><em>Section 3.2</em> <a href="#rfc.xref.Part4. 12">4.1</a>, <a href="#rfc.xref.Part4.16">8.4.13</a></li>3301 <li><em>Section 6.1</em> <a href="#rfc.xref.Part4. 1">1.2.2</a>, <a href="#rfc.xref.Part4.13">5</a>, <a href="#rfc.xref.Part4.14">8.2.2</a></li>3302 <li><em>Section 6.2</em> <a href="#rfc.xref.Part4. 2">1.2.2</a>, <a href="#rfc.xref.Part4.6">3</a></li>3303 <li><em>Section 6.3</em> <a href="#rfc.xref.Part4. 3">1.2.2</a>, <a href="#rfc.xref.Part4.7">3</a></li>3304 <li><em>Section 6.4</em> <a href="#rfc.xref.Part4. 4">1.2.2</a>, <a href="#rfc.xref.Part4.8">3</a></li>3305 <li><em>Section 6.5</em> <a href="#rfc.xref.Part4. 5">1.2.2</a>, <a href="#rfc.xref.Part4.9">3</a></li>3219 <li><em>Part4</em> <a href="#rfc.xref.Part4.1">3</a>, <a href="#rfc.xref.Part4.2">3</a>, <a href="#rfc.xref.Part4.3">3</a>, <a href="#rfc.xref.Part4.4">3</a>, <a href="#rfc.xref.Part4.5">4.1</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">5</a>, <a href="#rfc.xref.Part4.9">8.2.2</a>, <a href="#rfc.xref.Part4.10">8.3.5</a>, <a href="#rfc.xref.Part4.11">8.4.13</a>, <a href="#Part4"><b>13.1</b></a>, <a href="#rfc.xref.Part4.12">C.2</a><ul> 3220 <li><em>Section 3</em> <a href="#rfc.xref.Part4.5">4.1</a></li> 3221 <li><em>Section 3.1</em> <a href="#rfc.xref.Part4.6">4.1</a>, <a href="#rfc.xref.Part4.10">8.3.5</a></li> 3222 <li><em>Section 3.2</em> <a href="#rfc.xref.Part4.7">4.1</a>, <a href="#rfc.xref.Part4.11">8.4.13</a></li> 3223 <li><em>Section 6.1</em> <a href="#rfc.xref.Part4.8">5</a>, <a href="#rfc.xref.Part4.9">8.2.2</a></li> 3224 <li><em>Section 6.2</em> <a href="#rfc.xref.Part4.1">3</a></li> 3225 <li><em>Section 6.3</em> <a href="#rfc.xref.Part4.2">3</a></li> 3226 <li><em>Section 6.4</em> <a href="#rfc.xref.Part4.3">3</a></li> 3227 <li><em>Section 6.5</em> <a href="#rfc.xref.Part4.4">3</a></li> 3306 3228 </ul> 3307 3229 </li> 3308 <li><em>Part5</em> <a href="#rfc.xref.Part5.1"> 1.2.2</a>, <a href="#rfc.xref.Part5.2">1.2.2</a>, <a href="#rfc.xref.Part5.3">1.2.2</a>, <a href="#rfc.xref.Part5.4">3</a>, <a href="#rfc.xref.Part5.5">3</a>, <a href="#rfc.xref.Part5.6">4.1</a>, <a href="#rfc.xref.Part5.7">4.1</a>, <a href="#rfc.xref.Part5.8">4.1</a>, <a href="#rfc.xref.Part5.9">5</a>, <a href="#rfc.xref.Part5.10">7.3</a>, <a href="#rfc.xref.Part5.11">8.2.7</a>, <a href="#rfc.xref.Part5.12">8.4.17</a>, <a href="#rfc.xref.Part5.13">8.4.17</a>, <a href="#Part5"><b>13.1</b></a><ul>3309 <li><em>Section 3</em> <a href="#rfc.xref.Part5. 6">4.1</a></li>3310 <li><em>Section 3.1</em> <a href="#rfc.xref.Part5. 7">4.1</a>, <a href="#rfc.xref.Part5.11">8.2.7</a></li>3311 <li><em>Section 3.2</em> <a href="#rfc.xref.Part5. 8">4.1</a>, <a href="#rfc.xref.Part5.13">8.4.17</a></li>3312 <li><em>Section 5.1</em> <a href="#rfc.xref.Part5. 1">1.2.2</a>, <a href="#rfc.xref.Part5.9">5</a></li>3313 <li><em>Section 5.3</em> <a href="#rfc.xref.Part5. 2">1.2.2</a>, <a href="#rfc.xref.Part5.4">3</a></li>3314 <li><em>Section 5.4</em> <a href="#rfc.xref.Part5. 3">1.2.2</a>, <a href="#rfc.xref.Part5.5">3</a>, <a href="#rfc.xref.Part5.10">7.3</a>, <a href="#rfc.xref.Part5.12">8.4.17</a></li>3230 <li><em>Part5</em> <a href="#rfc.xref.Part5.1">3</a>, <a href="#rfc.xref.Part5.2">3</a>, <a href="#rfc.xref.Part5.3">4.1</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">5</a>, <a href="#rfc.xref.Part5.7">7.3</a>, <a href="#rfc.xref.Part5.8">8.2.7</a>, <a href="#rfc.xref.Part5.9">8.4.17</a>, <a href="#rfc.xref.Part5.10">8.4.17</a>, <a href="#Part5"><b>13.1</b></a><ul> 3231 <li><em>Section 3</em> <a href="#rfc.xref.Part5.3">4.1</a></li> 3232 <li><em>Section 3.1</em> <a href="#rfc.xref.Part5.4">4.1</a>, <a href="#rfc.xref.Part5.8">8.2.7</a></li> 3233 <li><em>Section 3.2</em> <a href="#rfc.xref.Part5.5">4.1</a>, <a href="#rfc.xref.Part5.10">8.4.17</a></li> 3234 <li><em>Section 5.1</em> <a href="#rfc.xref.Part5.6">5</a></li> 3235 <li><em>Section 5.3</em> <a href="#rfc.xref.Part5.1">3</a></li> 3236 <li><em>Section 5.4</em> <a href="#rfc.xref.Part5.2">3</a>, <a href="#rfc.xref.Part5.7">7.3</a>, <a href="#rfc.xref.Part5.9">8.4.17</a></li> 3315 3237 </ul> 3316 3238 </li> 3317 <li><em>Part6</em> <a href="#rfc.xref.Part6.1"> 1.2.2</a>, <a href="#rfc.xref.Part6.2">1.2.2</a>, <a href="#rfc.xref.Part6.3">2.2.1</a>, <a href="#rfc.xref.Part6.4">4.2.1</a>, <a href="#rfc.xref.Part6.5">5</a>, <a href="#rfc.xref.Part6.6">5</a>, <a href="#rfc.xref.Part6.7">6.1</a>, <a href="#rfc.xref.Part6.8">7.3</a>, <a href="#rfc.xref.Part6.9">7.4</a>, <a href="#rfc.xref.Part6.10">7.5</a>, <a href="#rfc.xref.Part6.11">7.6</a>, <a href="#rfc.xref.Part6.12">7.7</a>, <a href="#rfc.xref.Part6.13">8.2.1</a>, <a href="#rfc.xref.Part6.14">8.2.4</a>, <a href="#rfc.xref.Part6.15">8.2.7</a>, <a href="#rfc.xref.Part6.16">8.3.1</a>, <a href="#rfc.xref.Part6.17">8.3.2</a>, <a href="#rfc.xref.Part6.18">8.4.11</a>, <a href="#Part6"><b>13.1</b></a><ul>3318 <li><em>Section 2.3.1</em> <a href="#rfc.xref.Part6. 10">7.5</a></li>3319 <li><em>Section 2.3.1.1</em> <a href="#rfc.xref.Part6.1 3">8.2.1</a>, <a href="#rfc.xref.Part6.14">8.2.4</a>, <a href="#rfc.xref.Part6.15">8.2.7</a>, <a href="#rfc.xref.Part6.16">8.3.1</a>, <a href="#rfc.xref.Part6.17">8.3.2</a>, <a href="#rfc.xref.Part6.18">8.4.11</a></li>3320 <li><em>Section 2.5</em> <a href="#rfc.xref.Part6. 11">7.6</a>, <a href="#rfc.xref.Part6.12">7.7</a></li>3321 <li><em>Section 2.8</em> <a href="#rfc.xref.Part6. 7">6.1</a></li>3322 <li><em>Section 3.1</em> <a href="#rfc.xref.Part6. 1">1.2.2</a>, <a href="#rfc.xref.Part6.5">5</a></li>3323 <li><em>Section 3.5</em> <a href="#rfc.xref.Part6. 2">1.2.2</a>, <a href="#rfc.xref.Part6.6">5</a></li>3239 <li><em>Part6</em> <a href="#rfc.xref.Part6.1">2.2.1</a>, <a href="#rfc.xref.Part6.2">4.2.1</a>, <a href="#rfc.xref.Part6.3">5</a>, <a href="#rfc.xref.Part6.4">5</a>, <a href="#rfc.xref.Part6.5">6.1</a>, <a href="#rfc.xref.Part6.6">7.3</a>, <a href="#rfc.xref.Part6.7">7.4</a>, <a href="#rfc.xref.Part6.8">7.5</a>, <a href="#rfc.xref.Part6.9">7.6</a>, <a href="#rfc.xref.Part6.10">7.7</a>, <a href="#rfc.xref.Part6.11">8.2.1</a>, <a href="#rfc.xref.Part6.12">8.2.4</a>, <a href="#rfc.xref.Part6.13">8.2.7</a>, <a href="#rfc.xref.Part6.14">8.3.1</a>, <a href="#rfc.xref.Part6.15">8.3.2</a>, <a href="#rfc.xref.Part6.16">8.4.11</a>, <a href="#Part6"><b>13.1</b></a><ul> 3240 <li><em>Section 2.3.1</em> <a href="#rfc.xref.Part6.8">7.5</a></li> 3241 <li><em>Section 2.3.1.1</em> <a href="#rfc.xref.Part6.11">8.2.1</a>, <a href="#rfc.xref.Part6.12">8.2.4</a>, <a href="#rfc.xref.Part6.13">8.2.7</a>, <a href="#rfc.xref.Part6.14">8.3.1</a>, <a href="#rfc.xref.Part6.15">8.3.2</a>, <a href="#rfc.xref.Part6.16">8.4.11</a></li> 3242 <li><em>Section 2.5</em> <a href="#rfc.xref.Part6.9">7.6</a>, <a href="#rfc.xref.Part6.10">7.7</a></li> 3243 <li><em>Section 2.8</em> <a href="#rfc.xref.Part6.5">6.1</a></li> 3244 <li><em>Section 3.1</em> <a href="#rfc.xref.Part6.3">5</a></li> 3245 <li><em>Section 3.5</em> <a href="#rfc.xref.Part6.4">5</a></li> 3324 3246 </ul> 3325 3247 </li> 3326 <li><em>Part7</em> <a href="#rfc.xref.Part7.1"> 1.2.2</a>, <a href="#rfc.xref.Part7.2">1.2.2</a>, <a href="#rfc.xref.Part7.3">1.2.2</a>, <a href="#rfc.xref.Part7.4">1.2.2</a>, <a href="#rfc.xref.Part7.5">3</a>, <a href="#rfc.xref.Part7.6">3</a>, <a href="#rfc.xref.Part7.7">4.1</a>, <a href="#rfc.xref.Part7.8">4.1</a>, <a href="#rfc.xref.Part7.9">4.1</a>, <a href="#rfc.xref.Part7.10">5</a>, <a href="#rfc.xref.Part7.11">5</a>, <a href="#rfc.xref.Part7.12">8.4.2</a>, <a href="#rfc.xref.Part7.13">8.4.8</a>, <a href="#Part7"><b>13.1</b></a><ul>3327 <li><em>Section 3</em> <a href="#rfc.xref.Part7. 7">4.1</a></li>3328 <li><em>Section 3.1</em> <a href="#rfc.xref.Part7. 8">4.1</a>, <a href="#rfc.xref.Part7.12">8.4.2</a></li>3329 <li><em>Section 3.2</em> <a href="#rfc.xref.Part7. 9">4.1</a>, <a href="#rfc.xref.Part7.13">8.4.8</a></li>3330 <li><em>Section 4.1</em> <a href="#rfc.xref.Part7.1"> 1.2.2</a>, <a href="#rfc.xref.Part7.5">3</a></li>3331 <li><em>Section 4.2</em> <a href="#rfc.xref.Part7. 2">1.2.2</a>, <a href="#rfc.xref.Part7.10">5</a></li>3332 <li><em>Section 4.3</em> <a href="#rfc.xref.Part7. 3">1.2.2</a>, <a href="#rfc.xref.Part7.6">3</a></li>3333 <li><em>Section 4.4</em> <a href="#rfc.xref.Part7. 4">1.2.2</a>, <a href="#rfc.xref.Part7.11">5</a></li>3248 <li><em>Part7</em> <a href="#rfc.xref.Part7.1">3</a>, <a href="#rfc.xref.Part7.2">3</a>, <a href="#rfc.xref.Part7.3">4.1</a>, <a href="#rfc.xref.Part7.4">4.1</a>, <a href="#rfc.xref.Part7.5">4.1</a>, <a href="#rfc.xref.Part7.6">5</a>, <a href="#rfc.xref.Part7.7">5</a>, <a href="#rfc.xref.Part7.8">8.4.2</a>, <a href="#rfc.xref.Part7.9">8.4.8</a>, <a href="#Part7"><b>13.1</b></a><ul> 3249 <li><em>Section 3</em> <a href="#rfc.xref.Part7.3">4.1</a></li> 3250 <li><em>Section 3.1</em> <a href="#rfc.xref.Part7.4">4.1</a>, <a href="#rfc.xref.Part7.8">8.4.2</a></li> 3251 <li><em>Section 3.2</em> <a href="#rfc.xref.Part7.5">4.1</a>, <a href="#rfc.xref.Part7.9">8.4.8</a></li> 3252 <li><em>Section 4.1</em> <a href="#rfc.xref.Part7.1">3</a></li> 3253 <li><em>Section 4.2</em> <a href="#rfc.xref.Part7.6">5</a></li> 3254 <li><em>Section 4.3</em> <a href="#rfc.xref.Part7.2">3</a></li> 3255 <li><em>Section 4.4</em> <a href="#rfc.xref.Part7.7">5</a></li> 3334 3256 </ul> 3335 3257 </li> -
draft-ietf-httpbis/latest/p2-semantics.xml
r1165 r1167 348 348 <section title="ABNF Rules defined in other Parts of the Specification" anchor="abnf.dependencies"> 349 349 <x:anchor-alias value="absolute-URI"/> 350 <x:anchor-alias value="Accept"/>351 <x:anchor-alias value="Accept-Charset"/>352 <x:anchor-alias value="Accept-Encoding"/>353 <x:anchor-alias value="Accept-Language"/>354 <x:anchor-alias value="Accept-Ranges"/>355 <x:anchor-alias value="Age"/>356 <x:anchor-alias value="Authorization"/>357 350 <x:anchor-alias value="comment"/> 358 <x:anchor-alias value="ETag"/>359 <x:anchor-alias value="Host"/>360 351 <x:anchor-alias value="HTTP-date"/> 361 <x:anchor-alias value="If-Match"/>362 <x:anchor-alias value="If-Modified-Since"/>363 <x:anchor-alias value="If-None-Match"/>364 <x:anchor-alias value="If-Range"/>365 <x:anchor-alias value="If-Unmodified-Since"/>366 352 <x:anchor-alias value="partial-URI"/> 367 353 <x:anchor-alias value="product"/> 368 <x:anchor-alias value="Proxy-Authenticate"/>369 <x:anchor-alias value="Proxy-Authorization"/>370 <x:anchor-alias value="Range"/>371 <x:anchor-alias value="TE"/>372 354 <x:anchor-alias value="URI-reference"/> 373 <x:anchor-alias value="Vary"/>374 <x:anchor-alias value="WWW-Authenticate"/>375 355 <t> 376 356 The ABNF rules below are defined in other parts: … … 379 359 <x:ref>absolute-URI</x:ref> = <absolute-URI, defined in &uri;> 380 360 <x:ref>comment</x:ref> = <comment, defined in &header-fields;> 381 <x:ref>Host</x:ref> = <Host, defined in &uri;>382 361 <x:ref>HTTP-date</x:ref> = <HTTP-date, defined in &full-date;> 383 362 <x:ref>partial-URI</x:ref> = <partial-URI, defined in &uri;> 384 363 <x:ref>product</x:ref> = <product, defined in &product-tokens;> 385 <x:ref>TE</x:ref> = <TE, defined in &header-te;>386 364 <x:ref>URI-reference</x:ref> = <URI-reference, defined in &uri;> 387 </artwork></figure>388 <figure><!--Part3--><artwork type="abnf2616">389 <x:ref>Accept</x:ref> = <Accept, defined in &header-accept;>390 <x:ref>Accept-Charset</x:ref> =391 <Accept-Charset, defined in &header-accept-charset;>392 <x:ref>Accept-Encoding</x:ref> =393 <Accept-Encoding, defined in &header-accept-encoding;>394 <x:ref>Accept-Language</x:ref> =395 <Accept-Language, defined in &header-accept-language;>396 </artwork></figure>397 <figure><!--Part4--><artwork type="abnf2616">398 <x:ref>ETag</x:ref> = <ETag, defined in &header-etag;>399 <x:ref>If-Match</x:ref> = <If-Match, defined in &header-if-match;>400 <x:ref>If-Modified-Since</x:ref> =401 <If-Modified-Since, defined in &header-if-modified-since;>402 <x:ref>If-None-Match</x:ref> = <If-None-Match, defined in &header-if-none-match;>403 <x:ref>If-Unmodified-Since</x:ref> =404 <If-Unmodified-Since, defined in &header-if-unmodified-since;>405 </artwork></figure>406 <figure><!--Part5--><artwork type="abnf2616">407 <x:ref>Accept-Ranges</x:ref> = <Accept-Ranges, defined in &header-accept-ranges;>408 <x:ref>If-Range</x:ref> = <If-Range, defined in &header-if-range;>409 <x:ref>Range</x:ref> = <Range, defined in &header-range;>410 </artwork></figure>411 <figure><!--Part6--><artwork type="abnf2616">412 <x:ref>Age</x:ref> = <Age, defined in &header-age;>413 <x:ref>Vary</x:ref> = <Vary, defined in &header-vary;>414 </artwork><!--Part7--></figure>415 <figure><artwork type="abnf2616">416 <x:ref>Authorization</x:ref> = <Authorization, defined in &header-authorization;>417 <x:ref>Proxy-Authenticate</x:ref> =418 <Proxy-Authenticate, defined in &header-proxy-authenticate;>419 <x:ref>Proxy-Authorization</x:ref> =420 <Proxy-Authorization, defined in &header-proxy-authorization;>421 <x:ref>WWW-Authenticate</x:ref> =422 <WWW-Authenticate, defined in &header-www-authenticate;>423 365 </artwork></figure> 424 366 </section> … … 3606 3548 <figure> 3607 3549 <artwork type="abnf" name="p2-semantics.parsed-abnf"> 3608 <x:ref>Accept</x:ref> = <Accept, defined in [Part3], Section 6.1>3609 <x:ref>Accept-Charset</x:ref> = <Accept-Charset, defined in [Part3], Section 6.2>3610 <x:ref>Accept-Encoding</x:ref> = <Accept-Encoding, defined in [Part3], Section 6.3>3611 <x:ref>Accept-Language</x:ref> = <Accept-Language, defined in [Part3], Section 6.4>3612 <x:ref>Accept-Ranges</x:ref> = <Accept-Ranges, defined in [Part5], Section 5.1>3613 <x:ref>Age</x:ref> = <Age, defined in [Part6], Section 3.1>3614 3550 <x:ref>Allow</x:ref> = "Allow:" OWS Allow-v 3615 3551 <x:ref>Allow-v</x:ref> = [ ( "," / Method ) *( OWS "," [ OWS Method ] ) ] 3616 <x:ref>Authorization</x:ref> = <Authorization, defined in [Part7], Section 4.1> 3617 3618 <x:ref>ETag</x:ref> = <ETag, defined in [Part4], Section 6.1> 3552 3619 3553 <x:ref>Expect</x:ref> = "Expect:" OWS Expect-v 3620 3554 <x:ref>Expect-v</x:ref> = *( "," OWS ) expectation *( OWS "," [ OWS expectation ] ) … … 3624 3558 3625 3559 <x:ref>HTTP-date</x:ref> = <HTTP-date, defined in [Part1], Section 6.1> 3626 <x:ref>Host</x:ref> = <Host, defined in [Part1], Section 2.6>3627 3628 <x:ref>If-Match</x:ref> = <If-Match, defined in [Part4], Section 6.2>3629 If-Modified-Since =3630 <If-Modified-Since, defined in [Part4], Section 6.3>3631 <x:ref>If-None-Match</x:ref> = <If-None-Match, defined in [Part4], Section 6.4>3632 <x:ref>If-Range</x:ref> = <If-Range, defined in [Part5], Section 5.3>3633 If-Unmodified-Since =3634 <If-Unmodified-Since, defined in [Part4], Section 6.5>3635 3560 3636 3561 <x:ref>Location</x:ref> = "Location:" OWS Location-v … … 3643 3568 <x:ref>OWS</x:ref> = <OWS, defined in [Part1], Section 1.2.2> 3644 3569 3645 Proxy-Authenticate =3646 <Proxy-Authenticate, defined in [Part7], Section 4.2>3647 Proxy-Authorization =3648 <Proxy-Authorization, defined in [Part7], Section 4.3>3649 3650 3570 <x:ref>RWS</x:ref> = <RWS, defined in [Part1], Section 1.2.2> 3651 <x:ref>Range</x:ref> = <Range, defined in [Part5], Section 5.4>3652 3571 <x:ref>Reason-Phrase</x:ref> = *( WSP / VCHAR / obs-text ) 3653 3572 <x:ref>Referer</x:ref> = "Referer:" OWS Referer-v … … 3660 3579 <x:ref>Status-Code</x:ref> = 3DIGIT 3661 3580 3662 <x:ref>TE</x:ref> = <TE, defined in [Part1], Section 9.5>3663 3664 3581 <x:ref>URI-reference</x:ref> = <URI-reference, defined in [Part1], Section 2.6> 3665 3582 <x:ref>User-Agent</x:ref> = "User-Agent:" OWS User-Agent-v 3666 3583 <x:ref>User-Agent-v</x:ref> = product *( RWS ( product / comment ) ) 3667 3668 <x:ref>Vary</x:ref> = <Vary, defined in [Part6], Section 3.5>3669 3670 WWW-Authenticate =3671 <WWW-Authenticate, defined in [Part7], Section 4.4>3672 3584 3673 3585 <x:ref>absolute-URI</x:ref> = <absolute-URI, defined in [Part1], Section 2.6> … … 3695 3607 </figure> 3696 3608 <figure><preamble>ABNF diagnostics:</preamble><artwork type="inline"> 3697 ; Accept defined but not used3698 ; Accept-Charset defined but not used3699 ; Accept-Encoding defined but not used3700 ; Accept-Language defined but not used3701 ; Accept-Ranges defined but not used3702 ; Age defined but not used3703 3609 ; Allow defined but not used 3704 ; Authorization defined but not used3705 ; ETag defined but not used3706 3610 ; Expect defined but not used 3707 3611 ; From defined but not used 3708 ; Host defined but not used3709 ; If-Match defined but not used3710 ; If-Modified-Since defined but not used3711 ; If-None-Match defined but not used3712 ; If-Range defined but not used3713 ; If-Unmodified-Since defined but not used3714 3612 ; Location defined but not used 3715 3613 ; Max-Forwards defined but not used 3716 ; Proxy-Authenticate defined but not used3717 ; Proxy-Authorization defined but not used3718 ; Range defined but not used3719 3614 ; Reason-Phrase defined but not used 3720 3615 ; Referer defined but not used … … 3722 3617 ; Server defined but not used 3723 3618 ; Status-Code defined but not used 3724 ; TE defined but not used3725 3619 ; User-Agent defined but not used 3726 ; Vary defined but not used3727 ; WWW-Authenticate defined but not used3728 3620 </artwork></figure></section> 3729 3621 <?ENDINC p2-semantics.abnf-appendix ?> -
draft-ietf-httpbis/latest/p3-payload.html
r1165 r1167 682 682 <p id="rfc.section.1.3.2.p.1">The ABNF rules below are defined in other parts:</p> 683 683 <div id="rfc.figure.u.2"></div><pre class="inline"> <a href="#abnf.dependencies" class="smpl">absolute-URI</a> = <absolute-URI, defined in <a href="#Part1" id="rfc.xref.Part1.6"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#uri" title="Uniform Resource Identifiers">Section 2.6</a>> 684 <a href="#abnf.dependencies" class="smpl">Content-Length</a> = <Content-Length, defined in <a href="#Part1" id="rfc.xref.Part1.7"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#header.content-length" title="Content-Length">Section 9.2</a>> 685 <a href="#abnf.dependencies" class="smpl">partial-URI</a> = <partial-URI, defined in <a href="#Part1" id="rfc.xref.Part1.8"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#uri" title="Uniform Resource Identifiers">Section 2.6</a>> 686 <a href="#abnf.dependencies" class="smpl">qvalue</a> = <qvalue, defined in <a href="#Part1" id="rfc.xref.Part1.9"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#quality.values" title="Quality Values">Section 6.4</a>> 687 </pre><div id="rfc.figure.u.3"></div><pre class="inline"> <a href="#abnf.dependencies" class="smpl">Last-Modified</a> = <Last-Modified, defined in <a href="#Part4" id="rfc.xref.Part4.1"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>, <a href="p4-conditional.html#header.last-modified" title="Last-Modified">Section 6.6</a>> 688 </pre><div id="rfc.figure.u.4"></div><pre class="inline"> <a href="#abnf.dependencies" class="smpl">Content-Range</a> = <Content-Range, defined in <a href="#Part5" id="rfc.xref.Part5.1"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>, <a href="p5-range.html#header.content-range" title="Content-Range">Section 5.2</a>> 689 </pre><div id="rfc.figure.u.5"></div><pre class="inline"> <a href="#abnf.dependencies" class="smpl">Expires</a> = <Expires, defined in <a href="#Part6" id="rfc.xref.Part6.1"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>, <a href="p6-cache.html#header.expires" title="Expires">Section 3.3</a>> 684 <a href="#abnf.dependencies" class="smpl">partial-URI</a> = <partial-URI, defined in <a href="#Part1" id="rfc.xref.Part1.7"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#uri" title="Uniform Resource Identifiers">Section 2.6</a>> 685 <a href="#abnf.dependencies" class="smpl">qvalue</a> = <qvalue, defined in <a href="#Part1" id="rfc.xref.Part1.8"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#quality.values" title="Quality Values">Section 6.4</a>> 690 686 </pre><h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a> <a id="protocol.parameters" href="#protocol.parameters">Protocol Parameters</a></h1> 691 687 <h2 id="rfc.section.2.1"><a href="#rfc.section.2.1">2.1</a> <a id="character.sets" href="#character.sets">Character Sets</a></h2> … … 709 705 </p> 710 706 </div> 711 <div id="rfc.figure.u. 6"></div><pre class="inline"><span id="rfc.iref.g.1"></span> <a href="#rule.charset" class="smpl">charset</a> = <a href="#core.rules" class="smpl">token</a>707 <div id="rfc.figure.u.3"></div><pre class="inline"><span id="rfc.iref.g.1"></span> <a href="#rule.charset" class="smpl">charset</a> = <a href="#core.rules" class="smpl">token</a> 712 708 </pre><p id="rfc.section.2.1.p.6">Although HTTP allows an arbitrary token to be used as a charset value, any token that has a predefined value within the IANA 713 709 Character Set registry <em class="bcp14">MUST</em> represent the character set defined by that registry. Applications <em class="bcp14">SHOULD</em> limit their use of character sets to those defined by the IANA registry. … … 732 728 directly, and only decoded by the recipient. 733 729 </p> 734 <div id="rfc.figure.u. 7"></div><pre class="inline"><span id="rfc.iref.g.2"></span> <a href="#content.codings" class="smpl">content-coding</a> = <a href="#core.rules" class="smpl">token</a>730 <div id="rfc.figure.u.4"></div><pre class="inline"><span id="rfc.iref.g.2"></span> <a href="#content.codings" class="smpl">content-coding</a> = <a href="#core.rules" class="smpl">token</a> 735 731 </pre><p id="rfc.section.2.2.p.3">All content-coding values are case-insensitive. HTTP/1.1 uses content-coding values in the Accept-Encoding (<a href="#header.accept-encoding" id="rfc.xref.header.accept-encoding.1" title="Accept-Encoding">Section 6.3</a>) and Content-Encoding (<a href="#header.content-encoding" id="rfc.xref.header.content-encoding.1" title="Content-Encoding">Section 6.5</a>) header fields. Although the value describes the content-coding, what is more important is that it indicates what decoding 736 732 mechanism will be required to remove the encoding. … … 739 735 </p> 740 736 <ul class="empty"> 741 <li>See <a href="p1-messaging.html#compress.coding" title="Compress Coding">Section 6.2.2.1</a> of <a href="#Part1" id="rfc.xref.Part1. 10"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>.737 <li>See <a href="p1-messaging.html#compress.coding" title="Compress Coding">Section 6.2.2.1</a> of <a href="#Part1" id="rfc.xref.Part1.9"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>. 742 738 </li> 743 739 </ul> … … 745 741 </p> 746 742 <ul class="empty"> 747 <li>See <a href="p1-messaging.html#deflate.coding" title="Deflate Coding">Section 6.2.2.2</a> of <a href="#Part1" id="rfc.xref.Part1.1 1"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>.743 <li>See <a href="p1-messaging.html#deflate.coding" title="Deflate Coding">Section 6.2.2.2</a> of <a href="#Part1" id="rfc.xref.Part1.10"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>. 748 744 </li> 749 745 </ul> … … 751 747 </p> 752 748 <ul class="empty"> 753 <li>See <a href="p1-messaging.html#gzip.coding" title="Gzip Coding">Section 6.2.2.3</a> of <a href="#Part1" id="rfc.xref.Part1.1 2"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>.749 <li>See <a href="p1-messaging.html#gzip.coding" title="Gzip Coding">Section 6.2.2.3</a> of <a href="#Part1" id="rfc.xref.Part1.11"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>. 754 750 </li> 755 751 </ul> … … 770 766 <li>Pointer to specification text</li> 771 767 </ul> 772 <p id="rfc.section.2.2.1.p.3">Names of content codings <em class="bcp14">MUST NOT</em> overlap with names of transfer codings (<a href="p1-messaging.html#transfer.codings" title="Transfer Codings">Section 6.2</a> of <a href="#Part1" id="rfc.xref.Part1.1 3"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>), unless the encoding transformation is identical (as it is the case for the compression codings defined in <a href="p1-messaging.html#compression.codings" title="Compression Codings">Section 6.2.2</a> of <a href="#Part1" id="rfc.xref.Part1.14"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>).768 <p id="rfc.section.2.2.1.p.3">Names of content codings <em class="bcp14">MUST NOT</em> overlap with names of transfer codings (<a href="p1-messaging.html#transfer.codings" title="Transfer Codings">Section 6.2</a> of <a href="#Part1" id="rfc.xref.Part1.12"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>), unless the encoding transformation is identical (as it is the case for the compression codings defined in <a href="p1-messaging.html#compression.codings" title="Compression Codings">Section 6.2.2</a> of <a href="#Part1" id="rfc.xref.Part1.13"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>). 773 769 </p> 774 770 <p id="rfc.section.2.2.1.p.4">Values to be added to this name space require a specification (see "Specification Required" in <a href="http://tools.ietf.org/html/rfc5226#section-4.1">Section 4.1</a> of <a href="#RFC5226" id="rfc.xref.RFC5226.1"><cite title="Guidelines for Writing an IANA Considerations Section in RFCs">[RFC5226]</cite></a>), and <em class="bcp14">MUST</em> conform to the purpose of content coding defined in this section. … … 779 775 <p id="rfc.section.2.3.p.1">HTTP uses Internet Media Types <a href="#RFC2046" id="rfc.xref.RFC2046.1"><cite title="Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types">[RFC2046]</cite></a> in the Content-Type (<a href="#header.content-type" id="rfc.xref.header.content-type.1" title="Content-Type">Section 6.9</a>) and Accept (<a href="#header.accept" id="rfc.xref.header.accept.1" title="Accept">Section 6.1</a>) header fields in order to provide open and extensible data typing and type negotiation. 780 776 </p> 781 <div id="rfc.figure.u. 8"></div><pre class="inline"><span id="rfc.iref.g.4"></span><span id="rfc.iref.g.5"></span><span id="rfc.iref.g.6"></span> <a href="#media.types" class="smpl">media-type</a> = <a href="#media.types" class="smpl">type</a> "/" <a href="#media.types" class="smpl">subtype</a> *( <a href="#core.rules" class="smpl">OWS</a> ";" <a href="#core.rules" class="smpl">OWS</a> <a href="#rule.parameter" class="smpl">parameter</a> )777 <div id="rfc.figure.u.5"></div><pre class="inline"><span id="rfc.iref.g.4"></span><span id="rfc.iref.g.5"></span><span id="rfc.iref.g.6"></span> <a href="#media.types" class="smpl">media-type</a> = <a href="#media.types" class="smpl">type</a> "/" <a href="#media.types" class="smpl">subtype</a> *( <a href="#core.rules" class="smpl">OWS</a> ";" <a href="#core.rules" class="smpl">OWS</a> <a href="#rule.parameter" class="smpl">parameter</a> ) 782 778 <a href="#media.types" class="smpl">type</a> = <a href="#core.rules" class="smpl">token</a> 783 779 <a href="#media.types" class="smpl">subtype</a> = <a href="#core.rules" class="smpl">token</a> … … 786 782 </p> 787 783 </div> 788 <div id="rfc.figure.u. 9"></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> <a href="#rule.parameter" class="smpl">parameter</a> = <a href="#rule.parameter" class="smpl">attribute</a> "=" <a href="#rule.parameter" class="smpl">value</a>784 <div id="rfc.figure.u.6"></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> <a href="#rule.parameter" class="smpl">parameter</a> = <a href="#rule.parameter" class="smpl">attribute</a> "=" <a href="#rule.parameter" class="smpl">value</a> 789 785 <a href="#rule.parameter" class="smpl">attribute</a> = <a href="#core.rules" class="smpl">token</a> 790 786 <a href="#rule.parameter" class="smpl">value</a> = <a href="#core.rules" class="smpl">word</a> … … 841 837 of subtags: 842 838 </p> 843 <div id="rfc.figure.u. 10"></div><pre class="inline"><span id="rfc.iref.g.10"></span> <a href="#language.tags" class="smpl">language-tag</a> = <Language-Tag, defined in <a href="#RFC5646" id="rfc.xref.RFC5646.2"><cite title="Tags for Identifying Languages">[RFC5646]</cite></a>, <a href="http://tools.ietf.org/html/rfc5646#section-2.1">Section 2.1</a>>839 <div id="rfc.figure.u.7"></div><pre class="inline"><span id="rfc.iref.g.10"></span> <a href="#language.tags" class="smpl">language-tag</a> = <Language-Tag, defined in <a href="#RFC5646" id="rfc.xref.RFC5646.2"><cite title="Tags for Identifying Languages">[RFC5646]</cite></a>, <a href="http://tools.ietf.org/html/rfc5646#section-2.1">Section 2.1</a>> 844 840 </pre><p id="rfc.section.2.4.p.4">White space is not allowed within the tag and all tags are case-insensitive. The name space of language subtags is administered 845 841 by the IANA (see <<a href="http://www.iana.org/assignments/language-subtag-registry">http://www.iana.org/assignments/language-subtag-registry</a>>). 846 842 </p> 847 <div id="rfc.figure.u. 11"></div>843 <div id="rfc.figure.u.8"></div> 848 844 <p>Example tags include:</p> <pre class="text"> en, en-US, es-419, az-Arab, x-pig-latin, man-Nkoo-GN 849 845 </pre> <p id="rfc.section.2.4.p.6">See <a href="#RFC5646" id="rfc.xref.RFC5646.3"><cite title="Tags for Identifying Languages">[RFC5646]</cite></a> for further information. … … 874 870 <tr> 875 871 <td class="left">Content-Length</td> 876 <td class="left"><a href="p1-messaging.html#header.content-length" title="Content-Length">Section 9.2</a> of <a href="#Part1" id="rfc.xref.Part1.1 5"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a></td>872 <td class="left"><a href="p1-messaging.html#header.content-length" title="Content-Length">Section 9.2</a> of <a href="#Part1" id="rfc.xref.Part1.14"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a></td> 877 873 </tr> 878 874 <tr> … … 882 878 <tr> 883 879 <td class="left">Content-Range</td> 884 <td class="left"><a href="p5-range.html#header.content-range" title="Content-Range">Section 5.2</a> of <a href="#Part5" id="rfc.xref.Part5. 2"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a></td>880 <td class="left"><a href="p5-range.html#header.content-range" title="Content-Range">Section 5.2</a> of <a href="#Part5" id="rfc.xref.Part5.1"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a></td> 885 881 </tr> 886 882 </tbody> … … 888 884 </div> 889 885 <h2 id="rfc.section.3.2"><a href="#rfc.section.3.2">3.2</a> <a id="payload.body" href="#payload.body">Payload Body</a></h2> 890 <p id="rfc.section.3.2.p.1">A payload body is only present in a message when a message-body is present, as described in <a href="p1-messaging.html#message.body" title="Message Body">Section 3.3</a> of <a href="#Part1" id="rfc.xref.Part1.1 6"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>. The payload body is obtained from the message-body by decoding any Transfer-Encoding that might have been applied to ensure886 <p id="rfc.section.3.2.p.1">A payload body is only present in a message when a message-body is present, as described in <a href="p1-messaging.html#message.body" title="Message Body">Section 3.3</a> of <a href="#Part1" id="rfc.xref.Part1.15"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>. The payload body is obtained from the message-body by decoding any Transfer-Encoding that might have been applied to ensure 891 887 safe and proper transfer of the message. 892 888 </p> … … 939 935 <tr> 940 936 <td class="left">Expires</td> 941 <td class="left"><a href="p6-cache.html#header.expires" title="Expires">Section 3.3</a> of <a href="#Part6" id="rfc.xref.Part6. 2"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a></td>937 <td class="left"><a href="p6-cache.html#header.expires" title="Expires">Section 3.3</a> of <a href="#Part6" id="rfc.xref.Part6.1"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a></td> 942 938 </tr> 943 939 <tr> 944 940 <td class="left">Last-Modified</td> 945 <td class="left"><a href="p4-conditional.html#header.last-modified" title="Last-Modified">Section 6.6</a> of <a href="#Part4" id="rfc.xref.Part4. 2"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a></td>941 <td class="left"><a href="p4-conditional.html#header.last-modified" title="Last-Modified">Section 6.6</a> of <a href="#Part4" id="rfc.xref.Part4.1"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a></td> 946 942 </tr> 947 943 </tbody> … … 956 952 a two-layer, ordered encoding model: 957 953 </p> 958 <div id="rfc.figure.u. 12"></div><pre class="text"> representation-data := Content-Encoding( Content-Type( bits ) )954 <div id="rfc.figure.u.9"></div><pre class="text"> representation-data := Content-Encoding( Content-Type( bits ) ) 959 955 </pre><p id="rfc.section.4.2.p.4">Content-Type specifies the media type of the underlying data, which defines both the data format and how that data <em class="bcp14">SHOULD</em> be processed by the recipient (within the scope of the request method semantics). Any HTTP/1.1 message containing a payload 960 956 body <em class="bcp14">SHOULD</em> include a Content-Type header field defining the media type of the associated representation unless that metadata is unknown … … 1028 1024 </p> 1029 1025 </div> 1030 <p id="rfc.section.5.1.p.6">The Vary header field (<a href="p6-cache.html#header.vary" title="Vary">Section 3.5</a> of <a href="#Part6" id="rfc.xref.Part6. 3"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>) can be used to express the parameters the server uses to select a representation that is subject to server-driven negotiation.1026 <p id="rfc.section.5.1.p.6">The Vary header field (<a href="p6-cache.html#header.vary" title="Vary">Section 3.5</a> of <a href="#Part6" id="rfc.xref.Part6.2"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>) can be used to express the parameters the server uses to select a representation that is subject to server-driven negotiation. 1031 1027 </p> 1032 1028 <h2 id="rfc.section.5.2"><a href="#rfc.section.5.2">5.2</a> <a id="agent-driven.negotiation" href="#agent-driven.negotiation">Agent-driven Negotiation</a></h2> … … 1058 1054 for an in-line image. 1059 1055 </p> 1060 <div id="rfc.figure.u.1 3"></div><pre class="inline"><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> <a href="#header.accept" class="smpl">Accept</a> = "Accept" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.accept" class="smpl">Accept-v</a>1056 <div id="rfc.figure.u.10"></div><pre class="inline"><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> <a href="#header.accept" class="smpl">Accept</a> = "Accept" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.accept" class="smpl">Accept-v</a> 1061 1057 <a href="#header.accept" class="smpl">Accept-v</a> = #( <a href="#header.accept" class="smpl">media-range</a> [ <a href="#header.accept" class="smpl">accept-params</a> ] ) 1062 1058 … … 1072 1068 <p id="rfc.section.6.1.p.4">Each media-range <em class="bcp14">MAY</em> be followed by one or more accept-params, beginning with the "q" parameter for indicating a relative quality factor. The first 1073 1069 "q" parameter (if any) separates the media-range parameter(s) from the accept-params. Quality factors allow the user or user 1074 agent to indicate the relative degree of preference for that media-range, using the qvalue scale from 0 to 1 (<a href="p1-messaging.html#quality.values" title="Quality Values">Section 6.4</a> of <a href="#Part1" id="rfc.xref.Part1.1 7"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>). The default value is q=1.1070 agent to indicate the relative degree of preference for that media-range, using the qvalue scale from 0 to 1 (<a href="p1-messaging.html#quality.values" title="Quality Values">Section 6.4</a> of <a href="#Part1" id="rfc.xref.Part1.16"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>). The default value is q=1. 1075 1071 </p> 1076 1072 <div class="note" id="rfc.section.6.1.p.5"> … … 1082 1078 </div> 1083 1079 <p id="rfc.section.6.1.p.6">The example</p> 1084 <div id="rfc.figure.u.1 4"></div><pre class="text"> Accept: audio/*; q=0.2, audio/basic1080 <div id="rfc.figure.u.11"></div><pre class="text"> Accept: audio/*; q=0.2, audio/basic 1085 1081 </pre><p id="rfc.section.6.1.p.8"> <em class="bcp14">SHOULD</em> be interpreted as "I prefer audio/basic, but send me any audio type if it is the best available after an 80% mark-down in 1086 1082 quality". … … 1091 1087 </p> 1092 1088 <p id="rfc.section.6.1.p.10">A more elaborate example is</p> 1093 <div id="rfc.figure.u.1 5"></div><pre class="text"> Accept: text/plain; q=0.5, text/html,1089 <div id="rfc.figure.u.12"></div><pre class="text"> Accept: text/plain; q=0.5, text/html, 1094 1090 text/x-dvi; q=0.8, text/x-c 1095 1091 </pre><p id="rfc.section.6.1.p.12">Verbally, this would be interpreted as "text/html and text/x-c are the preferred media types, but if they do not exist, then … … 1099 1095 to a given type, the most specific reference has precedence. For example, 1100 1096 </p> 1101 <div id="rfc.figure.u.1 6"></div><pre class="text"> Accept: text/*, text/html, text/html;level=1, */*1097 <div id="rfc.figure.u.13"></div><pre class="text"> Accept: text/*, text/html, text/html;level=1, */* 1102 1098 </pre><p id="rfc.section.6.1.p.15">have the following precedence: </p> 1103 1099 <ol> … … 1110 1106 which matches that type. For example, 1111 1107 </p> 1112 <div id="rfc.figure.u.1 7"></div><pre class="text"> Accept: text/*;q=0.3, text/html;q=0.7, text/html;level=1,1108 <div id="rfc.figure.u.14"></div><pre class="text"> Accept: text/*;q=0.3, text/html;q=0.7, text/html;level=1, 1113 1109 text/html;level=2;q=0.4, */*;q=0.5 1114 1110 </pre><p id="rfc.section.6.1.p.18">would cause the following values to be associated:</p> … … 1159 1155 to a server which is capable of representing documents in those character sets. 1160 1156 </p> 1161 <div id="rfc.figure.u.1 8"></div><pre class="inline"><span id="rfc.iref.g.16"></span><span id="rfc.iref.g.17"></span> <a href="#header.accept-charset" class="smpl">Accept-Charset</a> = "Accept-Charset" ":" <a href="#core.rules" class="smpl">OWS</a>1157 <div id="rfc.figure.u.15"></div><pre class="inline"><span id="rfc.iref.g.16"></span><span id="rfc.iref.g.17"></span> <a href="#header.accept-charset" class="smpl">Accept-Charset</a> = "Accept-Charset" ":" <a href="#core.rules" class="smpl">OWS</a> 1162 1158 <a href="#header.accept-charset" class="smpl">Accept-Charset-v</a> 1163 1159 <a href="#header.accept-charset" class="smpl">Accept-Charset-v</a> = 1#( ( <a href="#rule.charset" class="smpl">charset</a> / "*" ) … … 1166 1162 example is 1167 1163 </p> 1168 <div id="rfc.figure.u.1 9"></div><pre class="text"> Accept-Charset: iso-8859-5, unicode-1-1;q=0.81164 <div id="rfc.figure.u.16"></div><pre class="text"> Accept-Charset: iso-8859-5, unicode-1-1;q=0.8 1169 1165 </pre><p id="rfc.section.6.2.p.5">The special value "*", if present in the Accept-Charset field, matches every character set (including ISO-8859-1) which is 1170 1166 not mentioned elsewhere in the Accept-Charset field. If no "*" is present in an Accept-Charset field, then all character sets … … 1181 1177 <p id="rfc.section.6.3.p.1">The "Accept-Encoding" header field can be used by user agents to indicate what response content-codings (<a href="#content.codings" title="Content Codings">Section 2.2</a>) are acceptable in the response. 1182 1178 </p> 1183 <div id="rfc.figure.u. 20"></div><pre class="inline"><span id="rfc.iref.g.18"></span><span id="rfc.iref.g.19"></span><span id="rfc.iref.g.20"></span> <a href="#header.accept-encoding" class="smpl">Accept-Encoding</a> = "Accept-Encoding" ":" <a href="#core.rules" class="smpl">OWS</a>1179 <div id="rfc.figure.u.17"></div><pre class="inline"><span id="rfc.iref.g.18"></span><span id="rfc.iref.g.19"></span><span id="rfc.iref.g.20"></span> <a href="#header.accept-encoding" class="smpl">Accept-Encoding</a> = "Accept-Encoding" ":" <a href="#core.rules" class="smpl">OWS</a> 1184 1180 <a href="#header.accept-encoding" class="smpl">Accept-Encoding-v</a> 1185 1181 <a href="#header.accept-encoding" class="smpl">Accept-Encoding-v</a> = … … 1189 1185 </p> 1190 1186 <p id="rfc.section.6.3.p.4">Examples of its use are:</p> 1191 <div id="rfc.figure.u. 21"></div><pre class="text"> Accept-Encoding: compress, gzip1187 <div id="rfc.figure.u.18"></div><pre class="text"> Accept-Encoding: compress, gzip 1192 1188 Accept-Encoding: 1193 1189 Accept-Encoding: * … … 1197 1193 <ol> 1198 1194 <li>If the content-coding is one of the content-codings listed in the Accept-Encoding field, then it is acceptable, unless it 1199 is accompanied by a qvalue of 0. (As defined in <a href="p1-messaging.html#quality.values" title="Quality Values">Section 6.4</a> of <a href="#Part1" id="rfc.xref.Part1.1 8"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, a qvalue of 0 means "not acceptable".)1195 is accompanied by a qvalue of 0. (As defined in <a href="p1-messaging.html#quality.values" title="Quality Values">Section 6.4</a> of <a href="#Part1" id="rfc.xref.Part1.17"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, a qvalue of 0 means "not acceptable".) 1200 1196 </li> 1201 1197 <li>The special "*" symbol in an Accept-Encoding field matches any available content-coding not explicitly listed in the header … … 1233 1229 in the response. Language tags are defined in <a href="#language.tags" title="Language Tags">Section 2.4</a>. 1234 1230 </p> 1235 <div id="rfc.figure.u. 22"></div><pre class="inline"><span id="rfc.iref.g.21"></span><span id="rfc.iref.g.22"></span><span id="rfc.iref.g.23"></span> <a href="#header.accept-language" class="smpl">Accept-Language</a> = "Accept-Language" ":" <a href="#core.rules" class="smpl">OWS</a>1231 <div id="rfc.figure.u.19"></div><pre class="inline"><span id="rfc.iref.g.21"></span><span id="rfc.iref.g.22"></span><span id="rfc.iref.g.23"></span> <a href="#header.accept-language" class="smpl">Accept-Language</a> = "Accept-Language" ":" <a href="#core.rules" class="smpl">OWS</a> 1236 1232 <a href="#header.accept-language" class="smpl">Accept-Language-v</a> 1237 1233 <a href="#header.accept-language" class="smpl">Accept-Language-v</a> = … … 1242 1238 languages specified by that range. The quality value defaults to "q=1". For example, 1243 1239 </p> 1244 <div id="rfc.figure.u.2 3"></div><pre class="text"> Accept-Language: da, en-gb;q=0.8, en;q=0.71240 <div id="rfc.figure.u.20"></div><pre class="text"> Accept-Language: da, en-gb;q=0.8, en;q=0.7 1245 1241 </pre><p id="rfc.section.6.4.p.5">would mean: "I prefer Danish, but will accept British English and other types of English". (see also <a href="http://tools.ietf.org/html/rfc4647#section-2.3">Section 2.3</a> of <a href="#RFC4647" id="rfc.xref.RFC4647.2"><cite title="Matching of Language Tags">[RFC4647]</cite></a>) 1246 1242 </p> … … 1271 1267 is primarily used to allow a representation to be compressed without losing the identity of its underlying media type. 1272 1268 </p> 1273 <div id="rfc.figure.u.2 4"></div><pre class="inline"><span id="rfc.iref.g.24"></span><span id="rfc.iref.g.25"></span> <a href="#header.content-encoding" class="smpl">Content-Encoding</a> = "Content-Encoding" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.content-encoding" class="smpl">Content-Encoding-v</a>1269 <div id="rfc.figure.u.21"></div><pre class="inline"><span id="rfc.iref.g.24"></span><span id="rfc.iref.g.25"></span> <a href="#header.content-encoding" class="smpl">Content-Encoding</a> = "Content-Encoding" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.content-encoding" class="smpl">Content-Encoding-v</a> 1274 1270 <a href="#header.content-encoding" class="smpl">Content-Encoding-v</a> = 1#<a href="#content.codings" class="smpl">content-coding</a> 1275 1271 </pre><p id="rfc.section.6.5.p.3">Content codings are defined in <a href="#content.codings" title="Content Codings">Section 2.2</a>. An example of its use is 1276 1272 </p> 1277 <div id="rfc.figure.u.2 5"></div><pre class="text"> Content-Encoding: gzip1273 <div id="rfc.figure.u.22"></div><pre class="text"> Content-Encoding: gzip 1278 1274 </pre><p id="rfc.section.6.5.p.5">The content-coding is a characteristic of the representation. Typically, the representation body is stored with this encoding 1279 1275 and is only decoded before rendering or analogous usage. However, a transforming proxy <em class="bcp14">MAY</em> modify the content-coding if the new coding is known to be acceptable to the recipient, unless the "no-transform" cache-control … … 1292 1288 that this might not be equivalent to all the languages used within the representation. 1293 1289 </p> 1294 <div id="rfc.figure.u.2 6"></div><pre class="inline"><span id="rfc.iref.g.26"></span><span id="rfc.iref.g.27"></span> <a href="#header.content-language" class="smpl">Content-Language</a> = "Content-Language" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.content-language" class="smpl">Content-Language-v</a>1290 <div id="rfc.figure.u.23"></div><pre class="inline"><span id="rfc.iref.g.26"></span><span id="rfc.iref.g.27"></span> <a href="#header.content-language" class="smpl">Content-Language</a> = "Content-Language" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.content-language" class="smpl">Content-Language-v</a> 1295 1291 <a href="#header.content-language" class="smpl">Content-Language-v</a> = 1#<a href="#language.tags" class="smpl">language-tag</a> 1296 1292 </pre><p id="rfc.section.6.6.p.3">Language tags are defined in <a href="#language.tags" title="Language Tags">Section 2.4</a>. The primary purpose of Content-Language is to allow a user to identify and differentiate representations according to the … … 1298 1294 field is 1299 1295 </p> 1300 <div id="rfc.figure.u.2 7"></div><pre class="text"> Content-Language: da1296 <div id="rfc.figure.u.24"></div><pre class="text"> Content-Language: da 1301 1297 </pre><p id="rfc.section.6.6.p.5">If no Content-Language is specified, the default is that the content is intended for all language audiences. This might mean 1302 1298 that the sender does not consider it to be specific to any natural language, or that the sender does not know for which language … … 1306 1302 simultaneously in the original Maori and English versions, would call for 1307 1303 </p> 1308 <div id="rfc.figure.u.2 8"></div><pre class="text"> Content-Language: mi, en1304 <div id="rfc.figure.u.25"></div><pre class="text"> Content-Language: mi, en 1309 1305 </pre><p id="rfc.section.6.6.p.8">However, just because multiple languages are present within a representation does not mean that it is intended for multiple 1310 1306 linguistic audiences. An example would be a beginner's language primer, such as "A First Lesson in Latin", which is clearly … … 1320 1316 would contain the same representation that is enclosed as payload in this message. 1321 1317 </p> 1322 <div id="rfc.figure.u.2 9"></div><pre class="inline"><span id="rfc.iref.g.28"></span><span id="rfc.iref.g.29"></span> <a href="#header.content-location" class="smpl">Content-Location</a> = "Content-Location" ":" <a href="#core.rules" class="smpl">OWS</a>1318 <div id="rfc.figure.u.26"></div><pre class="inline"><span id="rfc.iref.g.28"></span><span id="rfc.iref.g.29"></span> <a href="#header.content-location" class="smpl">Content-Location</a> = "Content-Location" ":" <a href="#core.rules" class="smpl">OWS</a> 1323 1319 <a href="#header.content-location" class="smpl">Content-Location-v</a> 1324 1320 <a href="#header.content-location" class="smpl">Content-Location-v</a> = 1325 1321 <a href="#abnf.dependencies" class="smpl">absolute-URI</a> / <a href="#abnf.dependencies" class="smpl">partial-URI</a> 1326 </pre><p id="rfc.section.6.7.p.3">The Content-Location value is not a replacement for the effective Request URI (<a href="p1-messaging.html#effective.request.uri" title="Effective Request URI">Section 4.3</a> of <a href="#Part1" id="rfc.xref.Part1.1 9"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>). It is representation metadata. It has the same syntax and semantics as the header field of the same name defined for MIME1322 </pre><p id="rfc.section.6.7.p.3">The Content-Location value is not a replacement for the effective Request URI (<a href="p1-messaging.html#effective.request.uri" title="Effective Request URI">Section 4.3</a> of <a href="#Part1" id="rfc.xref.Part1.18"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>). It is representation metadata. It has the same syntax and semantics as the header field of the same name defined for MIME 1327 1323 body parts in <a href="http://tools.ietf.org/html/rfc2557#section-4">Section 4</a> of <a href="#RFC2557" id="rfc.xref.RFC2557.1"><cite title="MIME Encapsulation of Aggregate Documents, such as HTML (MHTML)">[RFC2557]</cite></a>. However, its appearance in an HTTP message has some special implications for HTTP recipients. 1328 1324 </p> … … 1365 1361 body in transit, but is not proof against malicious attacks. 1366 1362 </p> 1367 <div id="rfc.figure.u. 30"></div><pre class="inline"><span id="rfc.iref.g.30"></span><span id="rfc.iref.g.31"></span> <a href="#header.content-md5" class="smpl">Content-MD5</a> = "Content-MD5" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.content-md5" class="smpl">Content-MD5-v</a>1363 <div id="rfc.figure.u.27"></div><pre class="inline"><span id="rfc.iref.g.30"></span><span id="rfc.iref.g.31"></span> <a href="#header.content-md5" class="smpl">Content-MD5</a> = "Content-MD5" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.content-md5" class="smpl">Content-MD5-v</a> 1368 1364 <a href="#header.content-md5" class="smpl">Content-MD5-v</a> = <base64 of 128 bit MD5 digest as per <a href="#RFC1864" id="rfc.xref.RFC1864.2"><cite title="The Content-MD5 Header Field">[RFC1864]</cite></a>> 1369 1365 </pre><p id="rfc.section.6.8.p.3">The Content-MD5 header field <em class="bcp14">MAY</em> be generated by an origin server or client to function as an integrity check of the payload body. Only origin servers or user … … 1399 1395 the media type is that which would have been sent had the request been a GET. 1400 1396 </p> 1401 <div id="rfc.figure.u. 31"></div><pre class="inline"><span id="rfc.iref.g.32"></span><span id="rfc.iref.g.33"></span> <a href="#header.content-type" class="smpl">Content-Type</a> = "Content-Type" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.content-type" class="smpl">Content-Type-v</a>1397 <div id="rfc.figure.u.28"></div><pre class="inline"><span id="rfc.iref.g.32"></span><span id="rfc.iref.g.33"></span> <a href="#header.content-type" class="smpl">Content-Type</a> = "Content-Type" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.content-type" class="smpl">Content-Type-v</a> 1402 1398 <a href="#header.content-type" class="smpl">Content-Type-v</a> = <a href="#media.types" class="smpl">media-type</a> 1403 1399 </pre><p id="rfc.section.6.9.p.3">Media types are defined in <a href="#media.types" title="Media Types">Section 2.3</a>. An example of the field is 1404 1400 </p> 1405 <div id="rfc.figure.u. 32"></div><pre class="text"> Content-Type: text/html; charset=ISO-8859-41401 <div id="rfc.figure.u.29"></div><pre class="text"> Content-Type: text/html; charset=ISO-8859-4 1406 1402 </pre><p id="rfc.section.6.9.p.5">Further discussion of Content-Type is provided in <a href="#representation.data" title="Representation Data">Section 4.2</a>. 1407 1403 </p> … … 1515 1511 <td class="left">compress</td> 1516 1512 <td class="left">UNIX "compress" program method</td> 1517 <td class="left"> <a href="p1-messaging.html#compress.coding" title="Compress Coding">Section 6.2.2.1</a> of <a href="#Part1" id="rfc.xref.Part1. 20"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>1513 <td class="left"> <a href="p1-messaging.html#compress.coding" title="Compress Coding">Section 6.2.2.1</a> of <a href="#Part1" id="rfc.xref.Part1.19"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a> 1518 1514 </td> 1519 1515 </tr> … … 1522 1518 <td class="left">"deflate" compression mechanism (<a href="#RFC1951" id="rfc.xref.RFC1951.1"><cite title="DEFLATE Compressed Data Format Specification version 1.3">[RFC1951]</cite></a>) used inside the "zlib" data format (<a href="#RFC1950" id="rfc.xref.RFC1950.1"><cite title="ZLIB Compressed Data Format Specification version 3.3">[RFC1950]</cite></a>) 1523 1519 </td> 1524 <td class="left"> <a href="p1-messaging.html#deflate.coding" title="Deflate Coding">Section 6.2.2.2</a> of <a href="#Part1" id="rfc.xref.Part1.2 1"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>1520 <td class="left"> <a href="p1-messaging.html#deflate.coding" title="Deflate Coding">Section 6.2.2.2</a> of <a href="#Part1" id="rfc.xref.Part1.20"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a> 1525 1521 </td> 1526 1522 </tr> … … 1528 1524 <td class="left">gzip</td> 1529 1525 <td class="left">Same as GNU zip <a href="#RFC1952" id="rfc.xref.RFC1952.1"><cite title="GZIP file format specification version 4.3">[RFC1952]</cite></a></td> 1530 <td class="left"> <a href="p1-messaging.html#gzip.coding" title="Gzip Coding">Section 6.2.2.3</a> of <a href="#Part1" id="rfc.xref.Part1.2 2"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>1526 <td class="left"> <a href="p1-messaging.html#gzip.coding" title="Gzip Coding">Section 6.2.2.3</a> of <a href="#Part1" id="rfc.xref.Part1.21"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a> 1531 1527 </td> 1532 1528 </tr> … … 1766 1762 environments. 1767 1763 </p> 1768 <div id="rfc.figure.u.3 3"></div><pre class="inline"><span id="rfc.iref.g.34"></span><span id="rfc.iref.g.35"></span> <a href="#mime-version" class="smpl">MIME-Version</a> = "MIME-Version" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#mime-version" class="smpl">MIME-Version-v</a>1764 <div id="rfc.figure.u.30"></div><pre class="inline"><span id="rfc.iref.g.34"></span><span id="rfc.iref.g.35"></span> <a href="#mime-version" class="smpl">MIME-Version</a> = "MIME-Version" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#mime-version" class="smpl">MIME-Version-v</a> 1769 1765 <a href="#mime-version" class="smpl">MIME-Version-v</a> = 1*<a href="#notation" class="smpl">DIGIT</a> "." 1*<a href="#notation" class="smpl">DIGIT</a> 1770 1766 </pre><p id="rfc.section.A.1.p.3">MIME version "1.0" is the default for use in HTTP/1.1. However, HTTP/1.1 message parsing and semantics are defined by this … … 1784 1780 </p> 1785 1781 <h2 id="rfc.section.A.3"><a href="#rfc.section.A.3">A.3</a> <a id="conversion.of.date.formats" href="#conversion.of.date.formats">Conversion of Date Formats</a></h2> 1786 <p id="rfc.section.A.3.p.1">HTTP/1.1 uses a restricted set of date formats (<a href="p1-messaging.html#date.time.formats.full.date" title="Date/Time Formats: Full Date">Section 6.1</a> of <a href="#Part1" id="rfc.xref.Part1.2 3"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) to simplify the process of date comparison. Proxies and gateways from other protocols <em class="bcp14">SHOULD</em> ensure that any Date header field present in a message conforms to one of the HTTP/1.1 formats and rewrite the date if necessary.1782 <p id="rfc.section.A.3.p.1">HTTP/1.1 uses a restricted set of date formats (<a href="p1-messaging.html#date.time.formats.full.date" title="Date/Time Formats: Full Date">Section 6.1</a> of <a href="#Part1" id="rfc.xref.Part1.22"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) to simplify the process of date comparison. Proxies and gateways from other protocols <em class="bcp14">SHOULD</em> ensure that any Date header field present in a message conforms to one of the HTTP/1.1 formats and rewrite the date if necessary. 1787 1783 </p> 1788 1784 <h2 id="rfc.section.A.4"><a href="#rfc.section.A.4">A.4</a> <a id="introduction.of.content-encoding" href="#introduction.of.content-encoding">Introduction of Content-Encoding</a></h2> … … 1801 1797 </p> 1802 1798 <h2 id="rfc.section.A.6"><a href="#rfc.section.A.6">A.6</a> <a id="introduction.of.transfer-encoding" href="#introduction.of.transfer-encoding">Introduction of Transfer-Encoding</a></h2> 1803 <p id="rfc.section.A.6.p.1">HTTP/1.1 introduces the Transfer-Encoding header field (<a href="p1-messaging.html#header.transfer-encoding" title="Transfer-Encoding">Section 9.7</a> of <a href="#Part1" id="rfc.xref.Part1.2 4"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>). Proxies/gateways <em class="bcp14">MUST</em> remove any transfer-coding prior to forwarding a message via a MIME-compliant protocol.1799 <p id="rfc.section.A.6.p.1">HTTP/1.1 introduces the Transfer-Encoding header field (<a href="p1-messaging.html#header.transfer-encoding" title="Transfer-Encoding">Section 9.7</a> of <a href="#Part1" id="rfc.xref.Part1.23"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>). Proxies/gateways <em class="bcp14">MUST</em> remove any transfer-coding prior to forwarding a message via a MIME-compliant protocol. 1804 1800 </p> 1805 1801 <h2 id="rfc.section.A.7"><a href="#rfc.section.A.7">A.7</a> <a id="mhtml.line.length" href="#mhtml.line.length">MHTML and Line Length Limitations</a></h2> … … 1826 1822 </p> 1827 1823 <h1 id="rfc.section.D"><a href="#rfc.section.D">D.</a> <a id="collected.abnf" href="#collected.abnf">Collected ABNF</a></h1> 1828 <div id="rfc.figure.u.3 4"></div> <pre class="inline"><a href="#header.accept" class="smpl">Accept</a> = "Accept:" OWS Accept-v1824 <div id="rfc.figure.u.31"></div> <pre class="inline"><a href="#header.accept" class="smpl">Accept</a> = "Accept:" OWS Accept-v 1829 1825 <a href="#header.accept-charset" class="smpl">Accept-Charset</a> = "Accept-Charset:" OWS Accept-Charset-v 1830 1826 <a href="#header.accept-charset" class="smpl">Accept-Charset-v</a> = *( "," OWS ) ( charset / "*" ) [ OWS ";" OWS "q=" … … 1847 1843 <a href="#header.content-language" class="smpl">Content-Language-v</a> = *( "," OWS ) language-tag *( OWS "," [ OWS 1848 1844 language-tag ] ) 1849 <a href="#abnf.dependencies" class="smpl">Content-Length</a> = <Content-Length, defined in [Part1], Section 9.2>1850 1845 <a href="#header.content-location" class="smpl">Content-Location</a> = "Content-Location:" OWS Content-Location-v 1851 1846 <a href="#header.content-location" class="smpl">Content-Location-v</a> = absolute-URI / partial-URI 1852 1847 <a href="#header.content-md5" class="smpl">Content-MD5</a> = "Content-MD5:" OWS Content-MD5-v 1853 1848 <a href="#header.content-md5" class="smpl">Content-MD5-v</a> = <base64 of 128 bit MD5 digest as per [RFC1864]> 1854 <a href="#abnf.dependencies" class="smpl">Content-Range</a> = <Content-Range, defined in [Part5], Section 5.2>1855 1849 <a href="#header.content-type" class="smpl">Content-Type</a> = "Content-Type:" OWS Content-Type-v 1856 1850 <a href="#header.content-type" class="smpl">Content-Type-v</a> = media-type 1857 1858 <a href="#abnf.dependencies" class="smpl">Expires</a> = <Expires, defined in [Part6], Section 3.3>1859 1860 <a href="#abnf.dependencies" class="smpl">Last-Modified</a> = <Last-Modified, defined in [Part4], Section 6.6>1861 1851 1862 1852 <a href="#mime-version" class="smpl">MIME-Version</a> = "MIME-Version:" OWS MIME-Version-v … … 1894 1884 1895 1885 <a href="#core.rules" class="smpl">word</a> = <word, defined in [Part1], Section 1.2.2> 1896 </pre> <div id="rfc.figure.u.3 5"></div>1886 </pre> <div id="rfc.figure.u.32"></div> 1897 1887 <p>ABNF diagnostics:</p><pre class="inline">; Accept defined but not used 1898 1888 ; Accept-Charset defined but not used … … 1901 1891 ; Content-Encoding defined but not used 1902 1892 ; Content-Language defined but not used 1903 ; Content-Length defined but not used1904 1893 ; Content-Location defined but not used 1905 1894 ; Content-MD5 defined but not used 1906 ; Content-Range defined but not used1907 1895 ; Content-Type defined but not used 1908 ; Expires defined but not used1909 ; Last-Modified defined but not used1910 1896 ; MIME-Version defined but not used 1911 1897 </pre><h1 id="rfc.section.E"><a href="#rfc.section.E">E.</a> <a id="change.log" href="#change.log">Change Log (to be removed by RFC Editor before publication)</a></h1> … … 2097 2083 <ul> 2098 2084 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/224">http://tools.ietf.org/wg/httpbis/trac/ticket/224</a>>: "Header Classification" 2085 </li> 2086 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/276">http://tools.ietf.org/wg/httpbis/trac/ticket/276</a>>: "untangle ABNFs for header fields" 2099 2087 </li> 2100 2088 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/277">http://tools.ietf.org/wg/httpbis/trac/ticket/277</a>>: "potentially misleading MAY in media-type def" … … 2208 2196 </li> 2209 2197 <li><a id="rfc.index.P" href="#rfc.index.P"><b>P</b></a><ul> 2210 <li><em>Part1</em> <a href="#rfc.xref.Part1.1">1.3</a>, <a href="#rfc.xref.Part1.2">1.3.1</a>, <a href="#rfc.xref.Part1.3">1.3.1</a>, <a href="#rfc.xref.Part1.4">1.3.1</a>, <a href="#rfc.xref.Part1.5">1.3.1</a>, <a href="#rfc.xref.Part1.6">1.3.2</a>, <a href="#rfc.xref.Part1.7">1.3.2</a>, <a href="#rfc.xref.Part1.8">1.3.2</a>, <a href="#rfc.xref.Part1.9"> 1.3.2</a>, <a href="#rfc.xref.Part1.10">2.2</a>, <a href="#rfc.xref.Part1.11">2.2</a>, <a href="#rfc.xref.Part1.12">2.2</a>, <a href="#rfc.xref.Part1.13">2.2.1</a>, <a href="#rfc.xref.Part1.14">2.2.1</a>, <a href="#rfc.xref.Part1.15">3.1</a>, <a href="#rfc.xref.Part1.16">3.2</a>, <a href="#rfc.xref.Part1.17">6.1</a>, <a href="#rfc.xref.Part1.18">6.3</a>, <a href="#rfc.xref.Part1.19">6.7</a>, <a href="#rfc.xref.Part1.20">7.2</a>, <a href="#rfc.xref.Part1.21">7.2</a>, <a href="#rfc.xref.Part1.22">7.2</a>, <a href="#Part1"><b>10.1</b></a>, <a href="#rfc.xref.Part1.23">A.3</a>, <a href="#rfc.xref.Part1.24">A.6</a><ul>2198 <li><em>Part1</em> <a href="#rfc.xref.Part1.1">1.3</a>, <a href="#rfc.xref.Part1.2">1.3.1</a>, <a href="#rfc.xref.Part1.3">1.3.1</a>, <a href="#rfc.xref.Part1.4">1.3.1</a>, <a href="#rfc.xref.Part1.5">1.3.1</a>, <a href="#rfc.xref.Part1.6">1.3.2</a>, <a href="#rfc.xref.Part1.7">1.3.2</a>, <a href="#rfc.xref.Part1.8">1.3.2</a>, <a href="#rfc.xref.Part1.9">2.2</a>, <a href="#rfc.xref.Part1.10">2.2</a>, <a href="#rfc.xref.Part1.11">2.2</a>, <a href="#rfc.xref.Part1.12">2.2.1</a>, <a href="#rfc.xref.Part1.13">2.2.1</a>, <a href="#rfc.xref.Part1.14">3.1</a>, <a href="#rfc.xref.Part1.15">3.2</a>, <a href="#rfc.xref.Part1.16">6.1</a>, <a href="#rfc.xref.Part1.17">6.3</a>, <a href="#rfc.xref.Part1.18">6.7</a>, <a href="#rfc.xref.Part1.19">7.2</a>, <a href="#rfc.xref.Part1.20">7.2</a>, <a href="#rfc.xref.Part1.21">7.2</a>, <a href="#Part1"><b>10.1</b></a>, <a href="#rfc.xref.Part1.22">A.3</a>, <a href="#rfc.xref.Part1.23">A.6</a><ul> 2211 2199 <li><em>Section 1.2</em> <a href="#rfc.xref.Part1.1">1.3</a></li> 2212 2200 <li><em>Section 1.2.2</em> <a href="#rfc.xref.Part1.2">1.3.1</a>, <a href="#rfc.xref.Part1.3">1.3.1</a>, <a href="#rfc.xref.Part1.4">1.3.1</a>, <a href="#rfc.xref.Part1.5">1.3.1</a></li> 2213 <li><em>Section 2.6</em> <a href="#rfc.xref.Part1.6">1.3.2</a>, <a href="#rfc.xref.Part1. 8">1.3.2</a></li>2214 <li><em>Section 3.3</em> <a href="#rfc.xref.Part1.1 6">3.2</a></li>2215 <li><em>Section 4.3</em> <a href="#rfc.xref.Part1.1 9">6.7</a></li>2216 <li><em>Section 6.1</em> <a href="#rfc.xref.Part1.2 3">A.3</a></li>2217 <li><em>Section 6.2</em> <a href="#rfc.xref.Part1.1 3">2.2.1</a></li>2218 <li><em>Section 6.2.2.1</em> <a href="#rfc.xref.Part1. 10">2.2</a>, <a href="#rfc.xref.Part1.20">7.2</a></li>2219 <li><em>Section 6.2.2</em> <a href="#rfc.xref.Part1.1 4">2.2.1</a></li>2220 <li><em>Section 6.2.2.2</em> <a href="#rfc.xref.Part1.1 1">2.2</a>, <a href="#rfc.xref.Part1.21">7.2</a></li>2221 <li><em>Section 6.2.2.3</em> <a href="#rfc.xref.Part1.1 2">2.2</a>, <a href="#rfc.xref.Part1.22">7.2</a></li>2222 <li><em>Section 6.4</em> <a href="#rfc.xref.Part1. 9">1.3.2</a>, <a href="#rfc.xref.Part1.17">6.1</a>, <a href="#rfc.xref.Part1.18">6.3</a></li>2223 <li><em>Section 9.2</em> <a href="#rfc.xref.Part1. 7">1.3.2</a>, <a href="#rfc.xref.Part1.15">3.1</a></li>2224 <li><em>Section 9.7</em> <a href="#rfc.xref.Part1.2 4">A.6</a></li>2201 <li><em>Section 2.6</em> <a href="#rfc.xref.Part1.6">1.3.2</a>, <a href="#rfc.xref.Part1.7">1.3.2</a></li> 2202 <li><em>Section 3.3</em> <a href="#rfc.xref.Part1.15">3.2</a></li> 2203 <li><em>Section 4.3</em> <a href="#rfc.xref.Part1.18">6.7</a></li> 2204 <li><em>Section 6.1</em> <a href="#rfc.xref.Part1.22">A.3</a></li> 2205 <li><em>Section 6.2</em> <a href="#rfc.xref.Part1.12">2.2.1</a></li> 2206 <li><em>Section 6.2.2.1</em> <a href="#rfc.xref.Part1.9">2.2</a>, <a href="#rfc.xref.Part1.19">7.2</a></li> 2207 <li><em>Section 6.2.2</em> <a href="#rfc.xref.Part1.13">2.2.1</a></li> 2208 <li><em>Section 6.2.2.2</em> <a href="#rfc.xref.Part1.10">2.2</a>, <a href="#rfc.xref.Part1.20">7.2</a></li> 2209 <li><em>Section 6.2.2.3</em> <a href="#rfc.xref.Part1.11">2.2</a>, <a href="#rfc.xref.Part1.21">7.2</a></li> 2210 <li><em>Section 6.4</em> <a href="#rfc.xref.Part1.8">1.3.2</a>, <a href="#rfc.xref.Part1.16">6.1</a>, <a href="#rfc.xref.Part1.17">6.3</a></li> 2211 <li><em>Section 9.2</em> <a href="#rfc.xref.Part1.14">3.1</a></li> 2212 <li><em>Section 9.7</em> <a href="#rfc.xref.Part1.23">A.6</a></li> 2225 2213 </ul> 2226 2214 </li> … … 2229 2217 </ul> 2230 2218 </li> 2231 <li><em>Part4</em> <a href="#rfc.xref.Part4.1"> 1.3.2</a>, <a href="#rfc.xref.Part4.2">4.1</a>, <a href="#Part4"><b>10.1</b></a><ul>2232 <li><em>Section 6.6</em> <a href="#rfc.xref.Part4.1"> 1.3.2</a>, <a href="#rfc.xref.Part4.2">4.1</a></li>2219 <li><em>Part4</em> <a href="#rfc.xref.Part4.1">4.1</a>, <a href="#Part4"><b>10.1</b></a><ul> 2220 <li><em>Section 6.6</em> <a href="#rfc.xref.Part4.1">4.1</a></li> 2233 2221 </ul> 2234 2222 </li> 2235 <li><em>Part5</em> <a href="#rfc.xref.Part5.1"> 1.3.2</a>, <a href="#rfc.xref.Part5.2">3.1</a>, <a href="#Part5"><b>10.1</b></a><ul>2236 <li><em>Section 5.2</em> <a href="#rfc.xref.Part5.1"> 1.3.2</a>, <a href="#rfc.xref.Part5.2">3.1</a></li>2223 <li><em>Part5</em> <a href="#rfc.xref.Part5.1">3.1</a>, <a href="#Part5"><b>10.1</b></a><ul> 2224 <li><em>Section 5.2</em> <a href="#rfc.xref.Part5.1">3.1</a></li> 2237 2225 </ul> 2238 2226 </li> 2239 <li><em>Part6</em> <a href="#rfc.xref.Part6.1"> 1.3.2</a>, <a href="#rfc.xref.Part6.2">4.1</a>, <a href="#rfc.xref.Part6.3">5.1</a>, <a href="#Part6"><b>10.1</b></a><ul>2240 <li><em>Section 3.3</em> <a href="#rfc.xref.Part6.1"> 1.3.2</a>, <a href="#rfc.xref.Part6.2">4.1</a></li>2241 <li><em>Section 3.5</em> <a href="#rfc.xref.Part6. 3">5.1</a></li>2227 <li><em>Part6</em> <a href="#rfc.xref.Part6.1">4.1</a>, <a href="#rfc.xref.Part6.2">5.1</a>, <a href="#Part6"><b>10.1</b></a><ul> 2228 <li><em>Section 3.3</em> <a href="#rfc.xref.Part6.1">4.1</a></li> 2229 <li><em>Section 3.5</em> <a href="#rfc.xref.Part6.2">5.1</a></li> 2242 2230 </ul> 2243 2231 </li> -
draft-ietf-httpbis/latest/p3-payload.xml
r1165 r1167 318 318 <section title="ABNF Rules defined in other Parts of the Specification" anchor="abnf.dependencies"> 319 319 <x:anchor-alias value="absolute-URI"/> 320 <x:anchor-alias value="Allow"/>321 <x:anchor-alias value="Content-Length"/>322 <x:anchor-alias value="Content-Range"/>323 <x:anchor-alias value="Expires"/>324 <x:anchor-alias value="Last-Modified"/>325 320 <x:anchor-alias value="partial-URI"/> 326 321 <x:anchor-alias value="qvalue"/> … … 330 325 <figure><!--Part1--><artwork type="abnf2616"> 331 326 <x:ref>absolute-URI</x:ref> = <absolute-URI, defined in &uri;> 332 <x:ref>Content-Length</x:ref> = <Content-Length, defined in &header-content-length;>333 327 <x:ref>partial-URI</x:ref> = <partial-URI, defined in &uri;> 334 328 <x:ref>qvalue</x:ref> = <qvalue, defined in &qvalue;> 335 </artwork></figure>336 <figure><!--Part4--><artwork type="abnf2616">337 <x:ref>Last-Modified</x:ref> = <Last-Modified, defined in &header-last-modified;>338 </artwork></figure>339 <figure><!--Part5--><artwork type="abnf2616">340 <x:ref>Content-Range</x:ref> = <Content-Range, defined in &header-content-range;>341 </artwork></figure>342 <figure><!--Part6--><artwork type="abnf2616">343 <x:ref>Expires</x:ref> = <Expires, defined in &header-expires;>344 329 </artwork></figure> 345 330 </section> … … 2699 2684 <x:ref>Content-Language-v</x:ref> = *( "," OWS ) language-tag *( OWS "," [ OWS 2700 2685 language-tag ] ) 2701 <x:ref>Content-Length</x:ref> = <Content-Length, defined in [Part1], Section 9.2>2702 2686 <x:ref>Content-Location</x:ref> = "Content-Location:" OWS Content-Location-v 2703 2687 <x:ref>Content-Location-v</x:ref> = absolute-URI / partial-URI 2704 2688 <x:ref>Content-MD5</x:ref> = "Content-MD5:" OWS Content-MD5-v 2705 2689 <x:ref>Content-MD5-v</x:ref> = <base64 of 128 bit MD5 digest as per [RFC1864]> 2706 <x:ref>Content-Range</x:ref> = <Content-Range, defined in [Part5], Section 5.2>2707 2690 <x:ref>Content-Type</x:ref> = "Content-Type:" OWS Content-Type-v 2708 2691 <x:ref>Content-Type-v</x:ref> = media-type 2709 2710 <x:ref>Expires</x:ref> = <Expires, defined in [Part6], Section 3.3>2711 2712 <x:ref>Last-Modified</x:ref> = <Last-Modified, defined in [Part4], Section 6.6>2713 2692 2714 2693 <x:ref>MIME-Version</x:ref> = "MIME-Version:" OWS MIME-Version-v … … 2755 2734 ; Content-Encoding defined but not used 2756 2735 ; Content-Language defined but not used 2757 ; Content-Length defined but not used2758 2736 ; Content-Location defined but not used 2759 2737 ; Content-MD5 defined but not used 2760 ; Content-Range defined but not used2761 2738 ; Content-Type defined but not used 2762 ; Expires defined but not used2763 ; Last-Modified defined but not used2764 2739 ; MIME-Version defined but not used 2765 2740 </artwork></figure></section> … … 3137 3112 </t> 3138 3113 <t> 3114 <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/276"/>: 3115 "untangle ABNFs for header fields" 3116 </t> 3117 <t> 3139 3118 <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/277"/>: 3140 3119 "potentially misleading MAY in media-type def"
Note: See TracChangeset
for help on using the changeset viewer.