Changeset 362 for draft-ietf-httpbis/latest/p4-conditional.html
- Timestamp:
- 13/11/08 15:47:23 (14 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p4-conditional.html
r345 r362 473 473 <tr> 474 474 <td class="header left"></td> 475 <td class="header right">November 1 1, 2008</td>475 <td class="header right">November 13, 2008</td> 476 476 </tr> 477 477 </table> … … 580 580 </p> 581 581 <h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a> <a id="notation" href="#notation">Notational Conventions and Generic Grammar</a></h1> 582 <p id="rfc.section.2.p.1">This specification uses the ABNF syntax defined in <a href="p1-messaging.html#notation.abnf" title="A ugmented BNF">Section 2.1</a> of <a href="#Part1" id="rfc.xref.Part1.1"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a> and the core rules defined in <a href="p1-messaging.html#basic.rules" title="Basic Rules">Section 2.2</a> of <a href="#Part1" id="rfc.xref.Part1.2"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>: <span class="comment">[abnf.dep: ABNF syntax and basic rules will be adopted from RFC 5234, see <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>>.]</span>582 <p id="rfc.section.2.p.1">This specification uses the ABNF syntax defined in <a href="p1-messaging.html#notation.abnf" title="ABNF Extensions">Section 2.1</a> of <a href="#Part1" id="rfc.xref.Part1.1"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a> and the core rules defined in <a href="p1-messaging.html#basic.rules" title="Basic Rules">Section 2.2</a> of <a href="#Part1" id="rfc.xref.Part1.2"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>: <span class="comment">[abnf.dep: ABNF syntax and basic rules will be adopted from RFC 5234, see <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>>.]</span> 583 583 </p> 584 584 <div id="rfc.figure.u.1"></div><pre class="inline"> <a href="#notation" class="smpl">quoted-string</a> = <quoted-string, defined in <a href="#Part1" id="rfc.xref.Part1.3"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#basic.rules" title="Basic Rules">Section 2.2</a>> 585 <a href="#notation" class="smpl">BWS</a> = <BWS, defined in <a href="#Part1" id="rfc.xref.Part1.4"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#basic.rules" title="Basic Rules">Section 2.2</a>> 586 <a href="#notation" class="smpl">OWS</a> = <OWS, defined in <a href="#Part1" id="rfc.xref.Part1.5"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#basic.rules" title="Basic Rules">Section 2.2</a>> 587 <a href="#notation" class="smpl">RWS</a> = <RWS, 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#basic.rules" title="Basic Rules">Section 2.2</a>> 585 588 </pre><div id="abnf.dependencies"> 586 589 <p id="rfc.section.2.p.3"> The ABNF rules below are defined in other parts:</p> 587 590 </div> 588 <div id="rfc.figure.u.2"></div><pre class="inline"> <a href="#abnf.dependencies" class="smpl">HTTP-date</a> = <HTTP-date, defined in <a href="#Part1" id="rfc.xref.Part1. 4"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#full.date" title="Full Date">Section 3.3.1</a>>591 <div id="rfc.figure.u.2"></div><pre class="inline"> <a href="#abnf.dependencies" class="smpl">HTTP-date</a> = <HTTP-date, 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#full.date" title="Full Date">Section 3.3.1</a>> 589 592 </pre><h1 id="rfc.section.3"><a href="#rfc.section.3">3.</a> <a id="entity.tags" href="#entity.tags">Entity Tags</a></h1> 590 593 <p id="rfc.section.3.p.1">Entity tags are used for comparing two or more entities from the same requested resource. HTTP/1.1 uses entity tags in the … … 613 616 <ul> 614 617 <li> 615 <p>Date, unless its omission is required by <a href="p1-messaging.html#clockless.origin.server.operation" title="Clockless Origin Server Operation">Section 8.3.1</a> of <a href="#Part1" id="rfc.xref.Part1. 5"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>.618 <p>Date, unless its omission is required by <a href="p1-messaging.html#clockless.origin.server.operation" title="Clockless Origin Server Operation">Section 8.3.1</a> of <a href="#Part1" id="rfc.xref.Part1.8"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>. 616 619 </p> 617 620 <p>If a clockless origin server obeys these rules, and proxies and clients add their own Date to any response received without 618 one (as already specified by <a href="p1-messaging.html#header.date" title="Date">Section 8.3</a> of <a href="#Part1" id="rfc.xref.Part1. 6"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, caches will operate correctly.621 one (as already specified by <a href="p1-messaging.html#header.date" title="Date">Section 8.3</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>, caches will operate correctly. 619 622 </p> 620 623 </li> … … 827 830 <div id="rfc.iref.h.1"></div> 828 831 <h2 id="rfc.section.7.1"><a href="#rfc.section.7.1">7.1</a> <a id="header.etag" href="#header.etag">ETag</a></h2> 829 <p id="rfc.section.7.1.p.1">The ETag response-header field provides the current value of the entity tag (see <a href="#entity.tags" title="Entity Tags">Section 3</a>) for the requested variant. The headers used with entity tags are described in Sections <a href="#header.if-match" id="rfc.xref.header.if-match.2" title="If-Match">7.2</a> and <a href="#header.if-none-match" id="rfc.xref.header.if-none-match.2" title="If-None-Match">7.4</a> of this document, and in <a href="p5-range.html#header.if-range" title="If-Range">Section 6.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>. The entity tag <em class="bcp14">MAY</em> be used for comparison with other entities from the same resource (see <a href="#weak.and.strong.validators" title="Weak and Strong Validators">Section 5</a>). 830 </p> 831 <div id="rfc.figure.u.4"></div><pre class="inline"><span id="rfc.iref.g.4"></span> <a href="#header.etag" class="smpl">ETag</a> = "ETag" ":" <a href="#entity.tags" class="smpl">entity-tag</a> 832 <p id="rfc.section.7.1.p.1">The response-header field "ETag" provides the current value of the entity tag (see <a href="#entity.tags" title="Entity Tags">Section 3</a>) for the requested variant. The headers used with entity tags are described in Sections <a href="#header.if-match" id="rfc.xref.header.if-match.2" title="If-Match">7.2</a> and <a href="#header.if-none-match" id="rfc.xref.header.if-none-match.2" title="If-None-Match">7.4</a> of this document, and in <a href="p5-range.html#header.if-range" title="If-Range">Section 6.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>. The entity tag <em class="bcp14">MAY</em> be used for comparison with other entities from the same resource (see <a href="#weak.and.strong.validators" title="Weak and Strong Validators">Section 5</a>). 833 </p> 834 <div id="rfc.figure.u.4"></div><pre class="inline"><span id="rfc.iref.g.4"></span><span id="rfc.iref.g.5"></span> <a href="#header.etag" class="smpl">ETag</a> = "ETag" <a href="#notation" class="smpl">BWS</a> ":" <a href="#notation" class="smpl">OWS</a> <a href="#header.etag" class="smpl">ETag-v</a> 835 <a href="#header.etag" class="smpl">ETag-v</a> = <a href="#entity.tags" class="smpl">entity-tag</a> 832 836 </pre><div id="rfc.figure.u.5"></div> 833 <p>Examples:</p> <pre class="text"> 834 835 837 <p>Examples:</p> <pre class="text"> ETag: "xyzzy" 838 ETag: W/"xyzzy" 839 ETag: "" 836 840 </pre><p id="rfc.section.7.1.p.4">The ETag response-header field value, an entity tag, provides for an "opaque" cache validator. This might allow more reliable 837 841 validation in situations where it is inconvenient to store modification dates, where the one-second resolution of HTTP date … … 847 851 <div id="rfc.iref.h.2"></div> 848 852 <h2 id="rfc.section.7.2"><a href="#rfc.section.7.2">7.2</a> <a id="header.if-match" href="#header.if-match">If-Match</a></h2> 849 <p id="rfc.section.7.2.p.1">The If-Match request-header fieldis used with a method to make it conditional. A client that has one or more entities previously853 <p id="rfc.section.7.2.p.1">The request-header field "If-Match" is used with a method to make it conditional. A client that has one or more entities previously 850 854 obtained from the resource can verify that one of those entities is current by including a list of their associated entity 851 855 tags in the If-Match header field. Entity tags are defined in <a href="#entity.tags" title="Entity Tags">Section 3</a>. The purpose of this feature is to allow efficient updates of cached information with a minimum amount of transaction overhead. … … 853 857 case, the value "*" matches any current entity of the resource. 854 858 </p> 855 <div id="rfc.figure.u.6"></div><pre class="inline"><span id="rfc.iref.g.5"></span> <a href="#header.if-match" class="smpl">If-Match</a> = "If-Match" ":" ( "*" / 1#<a href="#entity.tags" class="smpl">entity-tag</a> ) 859 <div id="rfc.figure.u.6"></div><pre class="inline"><span id="rfc.iref.g.6"></span><span id="rfc.iref.g.7"></span> <a href="#header.if-match" class="smpl">If-Match</a> = "If-Match" <a href="#notation" class="smpl">BWS</a> ":" <a href="#notation" class="smpl">OWS</a> <a href="#header.if-match" class="smpl">If-Match-v</a> 860 <a href="#header.if-match" class="smpl">If-Match-v</a> = "*" / 1#<a href="#entity.tags" class="smpl">entity-tag</a> 856 861 </pre><p id="rfc.section.7.2.p.3">If any of the entity tags match the entity tag of the entity that would have been returned in the response to a similar GET 857 862 request (without the If-Match header) on that resource, or if "*" is given and any current entity exists for that resource, … … 872 877 their knowledge. Examples: 873 878 </p> 874 <div id="rfc.figure.u.7"></div><pre class="text"> 875 876 879 <div id="rfc.figure.u.7"></div><pre class="text"> If-Match: "xyzzy" 880 If-Match: "xyzzy", "r2d2xxxx", "c3piozzzz" 881 If-Match: * 877 882 </pre><p id="rfc.section.7.2.p.10">The result of a request having both an If-Match header field and either an If-None-Match or an If-Modified-Since header fields 878 883 is undefined by this specification. … … 881 886 <div id="rfc.iref.h.3"></div> 882 887 <h2 id="rfc.section.7.3"><a href="#rfc.section.7.3">7.3</a> <a id="header.if-modified-since" href="#header.if-modified-since">If-Modified-Since</a></h2> 883 <p id="rfc.section.7.3.p.1">The If-Modified-Since request-header fieldis used with a method to make it conditional: if the requested variant has not888 <p id="rfc.section.7.3.p.1">The request-header field "If-Modified-Since" is used with a method to make it conditional: if the requested variant has not 884 889 been modified since the time specified in this field, an entity will not be returned from the server; instead, a 304 (Not 885 890 Modified) response will be returned without any message-body. 886 891 </p> 887 <div id="rfc.figure.u.8"></div><pre class="inline"><span id="rfc.iref.g.6"></span> <a href="#header.if-modified-since" class="smpl">If-Modified-Since</a> = "If-Modified-Since" ":" <a href="#abnf.dependencies" class="smpl">HTTP-date</a> 892 <div id="rfc.figure.u.8"></div><pre class="inline"><span id="rfc.iref.g.8"></span><span id="rfc.iref.g.9"></span> <a href="#header.if-modified-since" class="smpl">If-Modified-Since</a> = "If-Modified-Since" <a href="#notation" class="smpl">BWS</a> ":" <a href="#notation" class="smpl">OWS</a> <a href="#header.if-modified-since" class="smpl">If-Modified-Since-v</a> 893 <a href="#header.if-modified-since" class="smpl">If-Modified-Since-v</a> = <a href="#abnf.dependencies" class="smpl">HTTP-date</a> 888 894 </pre><p id="rfc.section.7.3.p.3">An example of the field is:</p> 889 <div id="rfc.figure.u.9"></div><pre class="text"> 895 <div id="rfc.figure.u.9"></div><pre class="text"> If-Modified-Since: Sat, 29 Oct 1994 19:43:31 GMT 890 896 </pre><p id="rfc.section.7.3.p.5">A GET method with an If-Modified-Since header and no Range header requests that the identified entity be transferred only 891 897 if it has been modified since the date given by the If-Modified-Since header. The algorithm for determining this includes … … 926 932 <div id="rfc.iref.h.4"></div> 927 933 <h2 id="rfc.section.7.4"><a href="#rfc.section.7.4">7.4</a> <a id="header.if-none-match" href="#header.if-none-match">If-None-Match</a></h2> 928 <p id="rfc.section.7.4.p.1">The If-None-Match request-header fieldis used with a method to make it conditional. A client that has one or more entities934 <p id="rfc.section.7.4.p.1">The request-header field "If-None-Match" is used with a method to make it conditional. A client that has one or more entities 929 935 previously obtained from the resource can verify that none of those entities is current by including a list of their associated 930 936 entity tags in the If-None-Match header field. The purpose of this feature is to allow efficient updates of cached information … … 933 939 </p> 934 940 <p id="rfc.section.7.4.p.2">As a special case, the value "*" matches any current entity of the resource.</p> 935 <div id="rfc.figure.u.10"></div><pre class="inline"><span id="rfc.iref.g.7"></span> <a href="#header.if-none-match" class="smpl">If-None-Match</a> = "If-None-Match" ":" ( "*" / 1#<a href="#entity.tags" class="smpl">entity-tag</a> ) 941 <div id="rfc.figure.u.10"></div><pre class="inline"><span id="rfc.iref.g.10"></span><span id="rfc.iref.g.11"></span> <a href="#header.if-none-match" class="smpl">If-None-Match</a> = "If-None-Match" <a href="#notation" class="smpl">BWS</a> ":" <a href="#notation" class="smpl">OWS</a> <a href="#header.if-none-match" class="smpl">If-None-Match-v</a> 942 <a href="#header.if-none-match" class="smpl">If-None-Match-v</a> = "*" / 1#<a href="#entity.tags" class="smpl">entity-tag</a> 936 943 </pre><p id="rfc.section.7.4.p.4">If any of the entity tags match the entity tag of the entity that would have been returned in the response to a similar GET 937 944 request (without the If-None-Match header) on that resource, or if "*" is given and any current entity exists for that resource, … … 950 957 </p> 951 958 <p id="rfc.section.7.4.p.9">Examples:</p> 952 <div id="rfc.figure.u.11"></div><pre class="text"> 953 954 955 956 959 <div id="rfc.figure.u.11"></div><pre class="text"> If-None-Match: "xyzzy" 960 If-None-Match: W/"xyzzy" 961 If-None-Match: "xyzzy", "r2d2xxxx", "c3piozzzz" 962 If-None-Match: W/"xyzzy", W/"r2d2xxxx", W/"c3piozzzz" 963 If-None-Match: * 957 964 </pre><p id="rfc.section.7.4.p.11">The result of a request having both an If-None-Match header field and either an If-Match or an If-Unmodified-Since header 958 965 fields is undefined by this specification. … … 961 968 <div id="rfc.iref.h.5"></div> 962 969 <h2 id="rfc.section.7.5"><a href="#rfc.section.7.5">7.5</a> <a id="header.if-unmodified-since" href="#header.if-unmodified-since">If-Unmodified-Since</a></h2> 963 <p id="rfc.section.7.5.p.1">The If-Unmodified-Since request-header field is used with a method to make it conditional. If the requested resource has not964 been modified since the time specified in this field, the server <em class="bcp14">SHOULD</em> perform the requested operation as if the If-Unmodified-Since header were not present.970 <p id="rfc.section.7.5.p.1">The request-header field "If-Unmodified-Since" is used with a method to make it conditional. If the requested resource has 971 not been modified since the time specified in this field, the server <em class="bcp14">SHOULD</em> perform the requested operation as if the If-Unmodified-Since header were not present. 965 972 </p> 966 973 <p id="rfc.section.7.5.p.2">If the requested variant has been modified since the specified time, the server <em class="bcp14">MUST NOT</em> perform the requested operation, and <em class="bcp14">MUST</em> return a 412 (Precondition Failed). 967 974 </p> 968 <div id="rfc.figure.u.12"></div><pre class="inline"><span id="rfc.iref.g.8"></span> <a href="#header.if-unmodified-since" class="smpl">If-Unmodified-Since</a> = "If-Unmodified-Since" ":" <a href="#abnf.dependencies" class="smpl">HTTP-date</a> 975 <div id="rfc.figure.u.12"></div><pre class="inline"><span id="rfc.iref.g.12"></span><span id="rfc.iref.g.13"></span> <a href="#header.if-unmodified-since" class="smpl">If-Unmodified-Since</a> = "If-Unmodified-Since" <a href="#notation" class="smpl">BWS</a> ":" <a href="#notation" class="smpl">OWS</a> <a href="#header.if-unmodified-since" class="smpl">If-Unmodified-Since-v</a> 976 <a href="#header.if-unmodified-since" class="smpl">If-Unmodified-Since-v</a> = <a href="#abnf.dependencies" class="smpl">HTTP-date</a> 969 977 </pre><p id="rfc.section.7.5.p.4">An example of the field is:</p> 970 <div id="rfc.figure.u.13"></div><pre class="text"> 978 <div id="rfc.figure.u.13"></div><pre class="text"> If-Unmodified-Since: Sat, 29 Oct 1994 19:43:31 GMT 971 979 </pre><p id="rfc.section.7.5.p.6">If the request normally (i.e., without the If-Unmodified-Since header) would result in anything other than a 2xx or 412 status, 972 980 the If-Unmodified-Since header <em class="bcp14">SHOULD</em> be ignored. … … 979 987 <div id="rfc.iref.h.6"></div> 980 988 <h2 id="rfc.section.7.6"><a href="#rfc.section.7.6">7.6</a> <a id="header.last-modified" href="#header.last-modified">Last-Modified</a></h2> 981 <p id="rfc.section.7.6.p.1">The Last-Modified entity-header fieldindicates the date and time at which the origin server believes the variant was last989 <p id="rfc.section.7.6.p.1">The entity-header field "Last-Modified" indicates the date and time at which the origin server believes the variant was last 982 990 modified. 983 991 </p> 984 <div id="rfc.figure.u.14"></div><pre class="inline"><span id="rfc.iref.g.9"></span> <a href="#header.last-modified" class="smpl">Last-Modified</a> = "Last-Modified" ":" <a href="#abnf.dependencies" class="smpl">HTTP-date</a> 992 <div id="rfc.figure.u.14"></div><pre class="inline"><span id="rfc.iref.g.14"></span><span id="rfc.iref.g.15"></span> <a href="#header.last-modified" class="smpl">Last-Modified</a> = "Last-Modified" <a href="#notation" class="smpl">BWS</a> ":" <a href="#notation" class="smpl">OWS</a> <a href="#header.last-modified" class="smpl">Last-Modified-v</a> 993 <a href="#header.last-modified" class="smpl">Last-Modified-v</a> = <a href="#abnf.dependencies" class="smpl">HTTP-date</a> 985 994 </pre><p id="rfc.section.7.6.p.3">An example of its use is</p> 986 <div id="rfc.figure.u.15"></div><pre class="text"> 995 <div id="rfc.figure.u.15"></div><pre class="text"> Last-Modified: Tue, 15 Nov 1994 12:45:26 GMT 987 996 </pre><p id="rfc.section.7.6.p.5">The exact meaning of this header field depends on the implementation of the origin server and the nature of the original resource. 988 997 For files, it may be just the file system last-modified time. For entities with dynamically included parts, it may be the … … 1065 1074 <p id="rfc.section.8.1.p.2">The change controller is: "IETF (iesg@ietf.org) - Internet Engineering Task Force".</p> 1066 1075 <h1 id="rfc.section.9"><a href="#rfc.section.9">9.</a> <a id="security.considerations" href="#security.considerations">Security Considerations</a></h1> 1067 <p id="rfc.section.9.p.1">No additional security considerations have been identified beyond those applicable to HTTP in general <a href="#Part1" id="rfc.xref.Part1. 7"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>.1076 <p id="rfc.section.9.p.1">No additional security considerations have been identified beyond those applicable to HTTP in general <a href="#Part1" id="rfc.xref.Part1.10"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>. 1068 1077 </p> 1069 1078 <h1 id="rfc.section.10"><a href="#rfc.section.10">10.</a> <a id="ack" href="#ack">Acknowledgments</a></h1> … … 1177 1186 <ul> 1178 1187 <li>Use "/" instead of "|" for alternatives.</li> 1188 <li>Introduce new ABNF rules for "bad" whitespace ("BWS"), optional whitespace ("OWS") and required whitespace ("RWS").</li> 1189 <li>Rewrite ABNFs to spell out whitespace rules, factor out header value format definitions.</li> 1179 1190 </ul> 1180 1191 <h1><a id="rfc.copyright" href="#rfc.copyright">Full Copyright Statement</a></h1> … … 1224 1235 <li class="indline1"><tt>entity-tag</tt> <a class="iref" href="#rfc.iref.g.1"><b>3</b></a></li> 1225 1236 <li class="indline1"><tt>ETag</tt> <a class="iref" href="#rfc.iref.g.4"><b>7.1</b></a></li> 1226 <li class="indline1"><tt>If-Match</tt> <a class="iref" href="#rfc.iref.g.5"><b>7.2</b></a></li> 1227 <li class="indline1"><tt>If-Modified-Since</tt> <a class="iref" href="#rfc.iref.g.6"><b>7.3</b></a></li> 1228 <li class="indline1"><tt>If-None-Match</tt> <a class="iref" href="#rfc.iref.g.7"><b>7.4</b></a></li> 1229 <li class="indline1"><tt>If-Unmodified-Since</tt> <a class="iref" href="#rfc.iref.g.8"><b>7.5</b></a></li> 1230 <li class="indline1"><tt>Last-Modified</tt> <a class="iref" href="#rfc.iref.g.9"><b>7.6</b></a></li> 1237 <li class="indline1"><tt>ETag-v</tt> <a class="iref" href="#rfc.iref.g.5"><b>7.1</b></a></li> 1238 <li class="indline1"><tt>If-Match</tt> <a class="iref" href="#rfc.iref.g.6"><b>7.2</b></a></li> 1239 <li class="indline1"><tt>If-Match-v</tt> <a class="iref" href="#rfc.iref.g.7"><b>7.2</b></a></li> 1240 <li class="indline1"><tt>If-Modified-Since</tt> <a class="iref" href="#rfc.iref.g.8"><b>7.3</b></a></li> 1241 <li class="indline1"><tt>If-Modified-Since-v</tt> <a class="iref" href="#rfc.iref.g.9"><b>7.3</b></a></li> 1242 <li class="indline1"><tt>If-None-Match</tt> <a class="iref" href="#rfc.iref.g.10"><b>7.4</b></a></li> 1243 <li class="indline1"><tt>If-None-Match-v</tt> <a class="iref" href="#rfc.iref.g.11"><b>7.4</b></a></li> 1244 <li class="indline1"><tt>If-Unmodified-Since</tt> <a class="iref" href="#rfc.iref.g.12"><b>7.5</b></a></li> 1245 <li class="indline1"><tt>If-Unmodified-Since-v</tt> <a class="iref" href="#rfc.iref.g.13"><b>7.5</b></a></li> 1246 <li class="indline1"><tt>Last-Modified</tt> <a class="iref" href="#rfc.iref.g.14"><b>7.6</b></a></li> 1247 <li class="indline1"><tt>Last-Modified-v</tt> <a class="iref" href="#rfc.iref.g.15"><b>7.6</b></a></li> 1231 1248 <li class="indline1"><tt>opaque-tag</tt> <a class="iref" href="#rfc.iref.g.3"><b>3</b></a></li> 1232 1249 <li class="indline1"><tt>weak</tt> <a class="iref" href="#rfc.iref.g.2"><b>3</b></a></li> … … 1260 1277 </li> 1261 1278 <li class="indline0"><a id="rfc.index.P" href="#rfc.index.P"><b>P</b></a><ul class="ind"> 1262 <li class="indline1"><em>Part1</em> <a class="iref" href="#rfc.xref.Part1.1">2</a>, <a class="iref" href="#rfc.xref.Part1.2">2</a>, <a class="iref" href="#rfc.xref.Part1.3">2</a>, <a class="iref" href="#rfc.xref.Part1.4">2</a>, <a class="iref" href="#rfc.xref.Part1.5"> 4.1</a>, <a class="iref" href="#rfc.xref.Part1.6">4.1</a>, <a class="iref" href="#rfc.xref.Part1.7">9</a>, <a class="iref" href="#Part1"><b>11.1</b></a><ul class="ind">1279 <li class="indline1"><em>Part1</em> <a class="iref" href="#rfc.xref.Part1.1">2</a>, <a class="iref" href="#rfc.xref.Part1.2">2</a>, <a class="iref" href="#rfc.xref.Part1.3">2</a>, <a class="iref" href="#rfc.xref.Part1.4">2</a>, <a class="iref" href="#rfc.xref.Part1.5">2</a>, <a class="iref" href="#rfc.xref.Part1.6">2</a>, <a class="iref" href="#rfc.xref.Part1.7">2</a>, <a class="iref" href="#rfc.xref.Part1.8">4.1</a>, <a class="iref" href="#rfc.xref.Part1.9">4.1</a>, <a class="iref" href="#rfc.xref.Part1.10">9</a>, <a class="iref" href="#Part1"><b>11.1</b></a><ul class="ind"> 1263 1280 <li class="indline1"><em>Section 2.1</em> <a class="iref" href="#rfc.xref.Part1.1">2</a></li> 1264 <li class="indline1"><em>Section 2.2</em> <a class="iref" href="#rfc.xref.Part1.2">2</a>, <a class="iref" href="#rfc.xref.Part1.3">2</a> </li>1265 <li class="indline1"><em>Section 3.3.1</em> <a class="iref" href="#rfc.xref.Part1. 4">2</a></li>1266 <li class="indline1"><em>Section 8.3.1</em> <a class="iref" href="#rfc.xref.Part1. 5">4.1</a></li>1267 <li class="indline1"><em>Section 8.3</em> <a class="iref" href="#rfc.xref.Part1. 6">4.1</a></li>1281 <li class="indline1"><em>Section 2.2</em> <a class="iref" href="#rfc.xref.Part1.2">2</a>, <a class="iref" href="#rfc.xref.Part1.3">2</a>, <a class="iref" href="#rfc.xref.Part1.4">2</a>, <a class="iref" href="#rfc.xref.Part1.5">2</a>, <a class="iref" href="#rfc.xref.Part1.6">2</a></li> 1282 <li class="indline1"><em>Section 3.3.1</em> <a class="iref" href="#rfc.xref.Part1.7">2</a></li> 1283 <li class="indline1"><em>Section 8.3.1</em> <a class="iref" href="#rfc.xref.Part1.8">4.1</a></li> 1284 <li class="indline1"><em>Section 8.3</em> <a class="iref" href="#rfc.xref.Part1.9">4.1</a></li> 1268 1285 </ul> 1269 1286 </li>
Note: See TracChangeset
for help on using the changeset viewer.