![(please configure the [header_logo] section in trac.ini)](https://www.ietf.org/images/ietflogotrans.gif)
Changeset 698 for draft-ietf-httpbis/latest/p4-conditional.html
- Timestamp:
- Sep 26, 2009, 3:09:09 AM (10 years ago)
- File:
-
- 1 edited
-
draft-ietf-httpbis/latest/p4-conditional.html (modified) (19 diffs)
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p4-conditional.html
r697 r698 396 396 <meta name="DC.Creator" content="Reschke, J. F."> 397 397 <meta name="DC.Identifier" content="urn:ietf:id:draft-ietf-httpbis-p4-conditional-latest"> 398 <meta name="DC.Date.Issued" scheme="ISO8601" content="2009-09-2 5">398 <meta name="DC.Date.Issued" scheme="ISO8601" content="2009-09-26"> 399 399 <meta name="DC.Relation.Replaces" content="urn:ietf:rfc:2616"> 400 400 <meta name="DC.Description.Abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 4 of the seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 4 defines request header fields for indicating conditional requests and the rules for constructing responses to those requests."> … … 428 428 </tr> 429 429 <tr> 430 <td class="header left">Expires: March 29, 2010</td>430 <td class="header left">Expires: March 30, 2010</td> 431 431 <td class="header right">HP</td> 432 432 </tr> … … 481 481 <tr> 482 482 <td class="header left"></td> 483 <td class="header right">September 2 5, 2009</td>483 <td class="header right">September 26, 2009</td> 484 484 </tr> 485 485 </table> … … 505 505 <p>The list of Internet-Draft Shadow Directories can be accessed at <<a href="http://www.ietf.org/shadow.html">http://www.ietf.org/shadow.html</a>>. 506 506 </p> 507 <p>This Internet-Draft will expire in March 29, 2010.</p>507 <p>This Internet-Draft will expire in March 30, 2010.</p> 508 508 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 509 509 <p>Copyright © 2009 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 858 858 <div id="rfc.iref.h.1"></div> 859 859 <h2 id="rfc.section.6.1"><a href="#rfc.section.6.1">6.1</a> <a id="header.etag" href="#header.etag">ETag</a></h2> 860 <p id="rfc.section.6.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 2</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">6.2</a> and <a href="#header.if-none-match" id="rfc.xref.header.if-none-match.2" title="If-None-Match">6.4</a> of this document, and in <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>. 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 4</a>).860 <p id="rfc.section.6.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 2</a>) for the requested variant, which may be used for comparison with other entities from the same resource (see <a href="#weak.and.strong.validators" title="Weak and Strong Validators">Section 4</a>). 861 861 </p> 862 862 <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="#core.rules" class="smpl">OWS</a> <a href="#header.etag" class="smpl">ETag-v</a> … … 879 879 <div id="rfc.iref.h.2"></div> 880 880 <h2 id="rfc.section.6.2"><a href="#rfc.section.6.2">6.2</a> <a id="header.if-match" href="#header.if-match">If-Match</a></h2> 881 <p id="rfc.section.6.2.p.1">The "If-Match" request-header field is used with a method to make itconditional. A client that has one or more entities previously881 <p id="rfc.section.6.2.p.1">The "If-Match" request-header field is used to make a request method conditional. A client that has one or more entities previously 882 882 obtained from the resource can verify that one of those entities is current by including a list of their associated entity 883 tags in the If-Match header field. Entity tags are defined in <a href="#entity.tags" title="Entity Tags">Section 2</a>. The purpose of this feature is to allow efficient updates of cached information with a minimum amount of transaction overhead. 884 It is also used, on updating requests, to prevent inadvertent modification of the wrong version of a resource. As a special 885 case, the value "*" matches any current entity of the resource. 883 tags in the If-Match header field. 884 </p> 885 <p id="rfc.section.6.2.p.2">This allows efficient updates of cached information with a minimum amount of transaction overhead. It is also used when updating 886 resources, to prevent inadvertent modification of the wrong version of a resource. As a special case, the value "*" matches 887 any current entity of the resource. 886 888 </p> 887 889 <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="#core.rules" class="smpl">OWS</a> <a href="#header.if-match" class="smpl">If-Match-v</a> 888 890 <a href="#header.if-match" class="smpl">If-Match-v</a> = "*" / 1#<a href="#entity.tags" class="smpl">entity-tag</a> 889 </pre><p id="rfc.section.6.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 GET891 </pre><p id="rfc.section.6.2.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 890 892 request (without the If-Match header) on that resource, or if "*" is given and any current entity exists for that resource, 891 893 then the server <em class="bcp14">MAY</em> perform the requested method as if the If-Match header field did not exist. 892 894 </p> 893 <p id="rfc.section.6.2.p. 4">If none of the entity tags match, or if "*" is given and no current entity exists, the server <em class="bcp14">MUST NOT</em> perform the requested method, and <em class="bcp14">MUST</em> return a 412 (Precondition Failed) response. This behavior is most useful when the client wants to prevent an updating method,895 <p id="rfc.section.6.2.p.5">If none of the entity tags match, or if "*" is given and no current entity exists, the server <em class="bcp14">MUST NOT</em> perform the requested method, and <em class="bcp14">MUST</em> return a 412 (Precondition Failed) response. This behavior is most useful when the client wants to prevent an updating method, 894 896 such as PUT, from modifying a resource that has changed since the client last retrieved it. 895 897 </p> 896 <p id="rfc.section.6.2.p. 5">If the request would, without the If-Match header field, result in anything other than a 2xx or 412 status, then the If-Match898 <p id="rfc.section.6.2.p.6">If the request would, without the If-Match header field, result in anything other than a 2xx or 412 status, then the If-Match 897 899 header <em class="bcp14">MUST</em> be ignored. 898 900 </p> 899 <p id="rfc.section.6.2.p. 6">The meaning of "If-Match: *" is that the method <em class="bcp14">SHOULD</em> be performed if the representation selected by the origin server (or by a cache, possibly using the Vary mechanism, see <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>) exists, and <em class="bcp14">MUST NOT</em> be performed if the representation does not exist.900 </p> 901 <p id="rfc.section.6.2.p. 7">A request intended to update a resource (e.g., a PUT) <em class="bcp14">MAY</em> include an If-Match header field to signal that the request method <em class="bcp14">MUST NOT</em> be applied if the entity corresponding to the If-Match value (a single entity tag) is no longer a representation of that resource.901 <p id="rfc.section.6.2.p.7">The meaning of "If-Match: *" is that the method <em class="bcp14">SHOULD</em> be performed if the representation selected by the origin server (or by a cache, possibly using the Vary mechanism, see <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>) exists, and <em class="bcp14">MUST NOT</em> be performed if the representation does not exist. 902 </p> 903 <p id="rfc.section.6.2.p.8">A request intended to update a resource (e.g., a PUT) <em class="bcp14">MAY</em> include an If-Match header field to signal that the request method <em class="bcp14">MUST NOT</em> be applied if the entity corresponding to the If-Match value (a single entity tag) is no longer a representation of that resource. 902 904 This allows the user to indicate that they do not wish the request to be successful if the resource has been changed without 903 905 their knowledge. Examples: … … 906 908 If-Match: "xyzzy", "r2d2xxxx", "c3piozzzz" 907 909 If-Match: * 908 </pre><p id="rfc.section.6.2.p. 9">The result of a request having both an If-Match header field and either an If-None-Match or an If-Modified-Since header fields910 </pre><p id="rfc.section.6.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 909 911 is undefined by this specification. 910 912 </p> … … 912 914 <div id="rfc.iref.h.3"></div> 913 915 <h2 id="rfc.section.6.3"><a href="#rfc.section.6.3">6.3</a> <a id="header.if-modified-since" href="#header.if-modified-since">If-Modified-Since</a></h2> 914 <p id="rfc.section.6.3.p.1">The "If-Modified-Since" request-header field is used with a method to make itconditional: if the requested variant has not915 been modified since the time specified in this field, an entity will not be returned from the server; instead, a 304 (Not916 Modified) response will be returned without any message-body.916 <p id="rfc.section.6.3.p.1">The "If-Modified-Since" request-header field is used to make a request method conditional: if the requested variant has not 917 been modified since the time specified in this field, the server will not return an entity; instead, a 304 (Not Modified) 918 response will be returned. 917 919 </p> 918 920 <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="#core.rules" class="smpl">OWS</a> … … 935 937 <p id="rfc.section.6.3.p.6">The purpose of this feature is to allow efficient updates of cached information with a minimum amount of transaction overhead. </p> 936 938 <dl class="empty"> 937 <dd> <b>Note:</b> The Range request-header field modifies the meaning of If-Modified-Since; see <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> for full details.939 <dd> <b>Note:</b> The Range request-header field modifies the meaning of If-Modified-Since; see <a href="p5-range.html#header.range" title="Range">Section 5.4</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> for full details. 938 940 </dd> 939 941 <dd> <b>Note:</b> If-Modified-Since times are interpreted by the server, whose clock might not be synchronized with the client. … … 959 961 <div id="rfc.iref.h.4"></div> 960 962 <h2 id="rfc.section.6.4"><a href="#rfc.section.6.4">6.4</a> <a id="header.if-none-match" href="#header.if-none-match">If-None-Match</a></h2> 961 <p id="rfc.section.6.4.p.1">The "If-None-Match" request-header field is used with a method to make itconditional. A client that has one or more entities963 <p id="rfc.section.6.4.p.1">The "If-None-Match" request-header field is used to make a request method conditional. A client that has one or more entities 962 964 previously obtained from the resource can verify that none of those entities is current by including a list of their associated 963 entity tags in the If-None-Match header field. The purpose of this feature is to allow efficient updates of cached information 964 with a minimum amount of transaction overhead. It is also used to prevent a method (e.g. PUT) from inadvertently modifying 965 an existing resource when the client believes that the resource does not exist. 966 </p> 967 <p id="rfc.section.6.4.p.2">As a special case, the value "*" matches any current entity of the resource.</p> 965 entity tags in the If-None-Match header field. 966 </p> 967 <p id="rfc.section.6.4.p.2">This allows efficient updates of cached information with a minimum amount of transaction overhead. It is also used to prevent 968 a method (e.g. PUT) from inadvertently modifying an existing resource when the client believes that the resource does not 969 exist. 970 </p> 971 <p id="rfc.section.6.4.p.3">As a special case, the value "*" matches any current entity of the resource.</p> 968 972 <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="#core.rules" class="smpl">OWS</a> <a href="#header.if-none-match" class="smpl">If-None-Match-v</a> 969 973 <a href="#header.if-none-match" class="smpl">If-None-Match-v</a> = "*" / 1#<a href="#entity.tags" class="smpl">entity-tag</a> 970 </pre><p id="rfc.section.6.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 GET974 </pre><p id="rfc.section.6.4.p.5">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 971 975 request (without the If-None-Match header) on that resource, or if "*" is given and any current entity exists for that resource, 972 976 then the server <em class="bcp14">MUST NOT</em> perform the requested method, unless required to do so because the resource's modification date fails to match that supplied … … 974 978 that matched. For all other request methods, the server <em class="bcp14">MUST</em> respond with a status of 412 (Precondition Failed). 975 979 </p> 976 <p id="rfc.section.6.4.p. 5">If none of the entity tags match, then the server <em class="bcp14">MAY</em> perform the requested method as if the If-None-Match header field did not exist, but <em class="bcp14">MUST</em> also ignore any If-Modified-Since header field(s) in the request. That is, if no entity tags match, then the server <em class="bcp14">MUST NOT</em> return a 304 (Not Modified) response.977 </p> 978 <p id="rfc.section.6.4.p. 6">If the request would, without the If-None-Match header field, result in anything other than a 2xx or 304 status, then the980 <p id="rfc.section.6.4.p.6">If none of the entity tags match, then the server <em class="bcp14">MAY</em> perform the requested method as if the If-None-Match header field did not exist, but <em class="bcp14">MUST</em> also ignore any If-Modified-Since header field(s) in the request. That is, if no entity tags match, then the server <em class="bcp14">MUST NOT</em> return a 304 (Not Modified) response. 981 </p> 982 <p id="rfc.section.6.4.p.7">If the request would, without the If-None-Match header field, result in anything other than a 2xx or 304 status, then the 979 983 If-None-Match header <em class="bcp14">MUST</em> be ignored. (See <a href="#rules.for.when.to.use.entity.tags.and.last-modified.dates" title="Rules for When to Use Entity Tags and Last-Modified Dates">Section 5</a> for a discussion of server behavior when both If-Modified-Since and If-None-Match appear in the same request.) 980 984 </p> 981 <p id="rfc.section.6.4.p. 7">The meaning of "If-None-Match: *" is that the method <em class="bcp14">MUST NOT</em> be performed if the representation selected by the origin server (or by a cache, possibly using the Vary mechanism, see <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>) exists, and <em class="bcp14">SHOULD</em> be performed if the representation does not exist. This feature is intended to be useful in preventing races between PUT operations.982 </p> 983 <p id="rfc.section.6.4.p. 8">Examples:</p>985 <p id="rfc.section.6.4.p.8">The meaning of "If-None-Match: *" is that the method <em class="bcp14">MUST NOT</em> be performed if the representation selected by the origin server (or by a cache, possibly using the Vary mechanism, see <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>) exists, and <em class="bcp14">SHOULD</em> be performed if the representation does not exist. This feature is intended to be useful in preventing races between PUT operations. 986 </p> 987 <p id="rfc.section.6.4.p.9">Examples:</p> 984 988 <div id="rfc.figure.u.11"></div><pre class="text"> If-None-Match: "xyzzy" 985 989 If-None-Match: W/"xyzzy" … … 987 991 If-None-Match: W/"xyzzy", W/"r2d2xxxx", W/"c3piozzzz" 988 992 If-None-Match: * 989 </pre><p id="rfc.section.6.4.p.1 0">The result of a request having both an If-None-Match header field and either an If-Match or an If-Unmodified-Since header993 </pre><p id="rfc.section.6.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 990 994 fields is undefined by this specification. 991 995 </p> … … 993 997 <div id="rfc.iref.h.5"></div> 994 998 <h2 id="rfc.section.6.5"><a href="#rfc.section.6.5">6.5</a> <a id="header.if-unmodified-since" href="#header.if-unmodified-since">If-Unmodified-Since</a></h2> 995 <p id="rfc.section.6.5.p.1">The "If-Unmodified-Since" request-header field is used with a method to make itconditional. If the requested resource has999 <p id="rfc.section.6.5.p.1">The "If-Unmodified-Since" request-header field is used to make a request method conditional. If the requested resource has 996 1000 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. 997 1001 </p> … … 1064 1068 <td>http</td> 1065 1069 <td>standard</td> 1066 <td> <a href="#header.if-match" id="rfc.xref.header.if-match. 3" title="If-Match">Section 6.2</a>1070 <td> <a href="#header.if-match" id="rfc.xref.header.if-match.2" title="If-Match">Section 6.2</a> 1067 1071 </td> 1068 1072 </tr> … … 1078 1082 <td>http</td> 1079 1083 <td>standard</td> 1080 <td> <a href="#header.if-none-match" id="rfc.xref.header.if-none-match. 3" title="If-None-Match">Section 6.4</a>1084 <td> <a href="#header.if-none-match" id="rfc.xref.header.if-none-match.2" title="If-None-Match">Section 6.4</a> 1081 1085 </td> 1082 1086 </tr> … … 1168 1172 <h1 id="rfc.section.A" class="np"><a href="#rfc.section.A">A.</a> <a id="compatibility" href="#compatibility">Compatibility with Previous Versions</a></h1> 1169 1173 <h2 id="rfc.section.A.1"><a href="#rfc.section.A.1">A.1</a> <a id="changes.from.rfc.2616" href="#changes.from.rfc.2616">Changes from RFC 2616</a></h2> 1170 <p id="rfc.section.A.1.p.1">Allow weak entity tags in all requests except range requests (Sections <a href="#weak.and.strong.validators" title="Weak and Strong Validators">4</a> and <a href="#header.if-none-match" id="rfc.xref.header.if-none-match. 4" title="If-None-Match">6.4</a>).1174 <p id="rfc.section.A.1.p.1">Allow weak entity tags in all requests except range requests (Sections <a href="#weak.and.strong.validators" title="Weak and Strong Validators">4</a> and <a href="#header.if-none-match" id="rfc.xref.header.if-none-match.3" title="If-None-Match">6.4</a>). 1171 1175 </p> 1172 1176 <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a> <a id="collected.abnf" href="#collected.abnf">Collected ABNF</a></h1> … … 1320 1324 <ul class="ind"> 1321 1325 <li class="indline1">ETag <a class="iref" href="#rfc.xref.header.etag.1">2</a>, <a class="iref" href="#rfc.iref.h.1"><b>6.1</b></a>, <a class="iref" href="#rfc.xref.header.etag.2">7.1</a></li> 1322 <li class="indline1">If-Match <a class="iref" href="#rfc.xref.header.if-match.1">2</a>, <a class="iref" href="#rfc. xref.header.if-match.2">6.1</a>, <a class="iref" href="#rfc.iref.h.2"><b>6.2</b></a>, <a class="iref" href="#rfc.xref.header.if-match.3">7.1</a></li>1326 <li class="indline1">If-Match <a class="iref" href="#rfc.xref.header.if-match.1">2</a>, <a class="iref" href="#rfc.iref.h.2"><b>6.2</b></a>, <a class="iref" href="#rfc.xref.header.if-match.2">7.1</a></li> 1323 1327 <li class="indline1">If-Modified-Since <a class="iref" href="#rfc.iref.h.3"><b>6.3</b></a>, <a class="iref" href="#rfc.xref.header.if-modified-since.1">7.1</a></li> 1324 <li class="indline1">If-None-Match <a class="iref" href="#rfc.xref.header.if-none-match.1">2</a>, <a class="iref" href="#rfc. xref.header.if-none-match.2">6.1</a>, <a class="iref" href="#rfc.iref.h.4"><b>6.4</b></a>, <a class="iref" href="#rfc.xref.header.if-none-match.3">7.1</a>, <a class="iref" href="#rfc.xref.header.if-none-match.4">A.1</a></li>1328 <li class="indline1">If-None-Match <a class="iref" href="#rfc.xref.header.if-none-match.1">2</a>, <a class="iref" href="#rfc.iref.h.4"><b>6.4</b></a>, <a class="iref" href="#rfc.xref.header.if-none-match.2">7.1</a>, <a class="iref" href="#rfc.xref.header.if-none-match.3">A.1</a></li> 1325 1329 <li class="indline1">If-Unmodified-Since <a class="iref" href="#rfc.iref.h.5"><b>6.5</b></a>, <a class="iref" href="#rfc.xref.header.if-unmodified-since.1">7.1</a></li> 1326 1330 <li class="indline1">Last-Modified <a class="iref" href="#rfc.iref.h.6"><b>6.6</b></a>, <a class="iref" href="#rfc.xref.header.last-modified.1">7.1</a></li> … … 1330 1334 </li> 1331 1335 <li class="indline0"><a id="rfc.index.I" href="#rfc.index.I"><b>I</b></a><ul class="ind"> 1332 <li class="indline1">If-Match header <a class="iref" href="#rfc.xref.header.if-match.1">2</a>, <a class="iref" href="#rfc. xref.header.if-match.2">6.1</a>, <a class="iref" href="#rfc.iref.i.1"><b>6.2</b></a>, <a class="iref" href="#rfc.xref.header.if-match.3">7.1</a></li>1336 <li class="indline1">If-Match header <a class="iref" href="#rfc.xref.header.if-match.1">2</a>, <a class="iref" href="#rfc.iref.i.1"><b>6.2</b></a>, <a class="iref" href="#rfc.xref.header.if-match.2">7.1</a></li> 1333 1337 <li class="indline1">If-Modified-Since header <a class="iref" href="#rfc.iref.i.2"><b>6.3</b></a>, <a class="iref" href="#rfc.xref.header.if-modified-since.1">7.1</a></li> 1334 <li class="indline1">If-None-Match header <a class="iref" href="#rfc.xref.header.if-none-match.1">2</a>, <a class="iref" href="#rfc. xref.header.if-none-match.2">6.1</a>, <a class="iref" href="#rfc.iref.i.3"><b>6.4</b></a>, <a class="iref" href="#rfc.xref.header.if-none-match.3">7.1</a>, <a class="iref" href="#rfc.xref.header.if-none-match.4">A.1</a></li>1338 <li class="indline1">If-None-Match header <a class="iref" href="#rfc.xref.header.if-none-match.1">2</a>, <a class="iref" href="#rfc.iref.i.3"><b>6.4</b></a>, <a class="iref" href="#rfc.xref.header.if-none-match.2">7.1</a>, <a class="iref" href="#rfc.xref.header.if-none-match.3">A.1</a></li> 1335 1339 <li class="indline1">If-Unmodified-Since header <a class="iref" href="#rfc.iref.i.4"><b>6.5</b></a>, <a class="iref" href="#rfc.xref.header.if-unmodified-since.1">7.1</a></li> 1336 1340 </ul> … … 1349 1353 </ul> 1350 1354 </li> 1351 <li class="indline1"><em>Part5</em> <a class="iref" href="#rfc.xref.Part5.1">2</a>, <a class="iref" href="#rfc.xref.Part5.2">4</a>, <a class="iref" href="#rfc.xref.Part5.3">4</a>, <a class="iref" href="#rfc.xref.Part5.4">6. 1</a>, <a class="iref" href="#rfc.xref.Part5.5">6.3</a>, <a class="iref" href="#Part5"><b>10.1</b></a><ul class="ind">1352 <li class="indline1"><em>Section 5.3</em> <a class="iref" href="#rfc.xref.Part5.1">2</a> , <a class="iref" href="#rfc.xref.Part5.4">6.1</a></li>1353 <li class="indline1"><em>Section 5.4</em> <a class="iref" href="#rfc.xref.Part5. 5">6.3</a></li>1355 <li class="indline1"><em>Part5</em> <a class="iref" href="#rfc.xref.Part5.1">2</a>, <a class="iref" href="#rfc.xref.Part5.2">4</a>, <a class="iref" href="#rfc.xref.Part5.3">4</a>, <a class="iref" href="#rfc.xref.Part5.4">6.3</a>, <a class="iref" href="#Part5"><b>10.1</b></a><ul class="ind"> 1356 <li class="indline1"><em>Section 5.3</em> <a class="iref" href="#rfc.xref.Part5.1">2</a></li> 1357 <li class="indline1"><em>Section 5.4</em> <a class="iref" href="#rfc.xref.Part5.4">6.3</a></li> 1354 1358 </ul> 1355 1359 </li>
Note: See TracChangeset
for help on using the changeset viewer.
