Changeset 563 for draft-ietf-httpbis/latest/p4-conditional.html
- Timestamp:
- 24/03/09 20:48:26 (13 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p4-conditional.html
r560 r563 29 29 cite { 30 30 font-style: normal; 31 } 32 div.note { 33 margin-left: 2em; 31 34 } 32 35 dd { … … 464 467 <tr> 465 468 <td class="header left"></td> 466 <td class="header right">March 12, 2009</td>469 <td class="header right">March 24, 2009</td> 467 470 </tr> 468 471 </table> … … 792 795 value. 793 796 </p> 794 <p id="rfc.section.5.p.4">In order to be legal, a strong entity tag <em class="bcp14">MUST</em> change whenever the associated entity changes in any way. A weak entity tag <em class="bcp14">SHOULD</em> change whenever the associated entity changes in a semantically significant way. 795 </p> 796 <d l class="empty">797 < dd> <b>Note:</b> in order to provide semantically transparent caching, an origin server must avoid reusing a specific strong entity tag value797 <p id="rfc.section.5.p.4">In order to be legal, a strong entity tag <em class="bcp14">MUST</em> change whenever the associated entity changes in any way. A weak entity tag <em class="bcp14">SHOULD</em> change whenever the associated entity changes in a semantically significant way. 798 </p> 799 <div class="note"> 800 <p> <b>Note:</b> in order to provide semantically transparent caching, an origin server must avoid reusing a specific strong entity tag value 798 801 for two different entities, or reusing a specific weak entity tag value for two semantically different entities. Cache entries 799 802 might persist for arbitrarily long periods, regardless of expiration times, so it might be inappropriate to expect that a 800 803 cache will never again attempt to validate an entry using a validator that it obtained at some point in the past. 801 </ dd>802 </d l>803 <p id="rfc.section.5.p. 5">HTTP/1.1 clients: </p>804 </p> 805 </div> 806 <p id="rfc.section.5.p.6">HTTP/1.1 clients: </p> 804 807 <ul> 805 808 <li>If an entity tag has been provided by the origin server, <em class="bcp14">MUST</em> use that entity tag in any cache-conditional request (using If-Match or If-None-Match). … … 812 815 </li> 813 816 </ul> 814 <p id="rfc.section.5.p. 6">An HTTP/1.1 origin server, upon receiving a conditional request that includes both a Last-Modified date (e.g., in an If-Modified-Since817 <p id="rfc.section.5.p.7">An HTTP/1.1 origin server, upon receiving a conditional request that includes both a Last-Modified date (e.g., in an If-Modified-Since 815 818 or If-Unmodified-Since header field) and one or more entity tags (e.g., in an If-Match, If-None-Match, or If-Range header 816 819 field) as cache validators, <em class="bcp14">MUST NOT</em> return a response status of 304 (Not Modified) unless doing so is consistent with all of the conditional header fields in 817 820 the request. 818 821 </p> 819 <p id="rfc.section.5.p. 7">An HTTP/1.1 caching proxy, upon receiving a conditional request that includes both a Last-Modified date and one or more entity822 <p id="rfc.section.5.p.8">An HTTP/1.1 caching proxy, upon receiving a conditional request that includes both a Last-Modified date and one or more entity 820 823 tags as cache validators, <em class="bcp14">MUST NOT</em> return a locally cached response to the client unless that cached response is consistent with all of the conditional header 821 824 fields in the request.
Note: See TracChangeset
for help on using the changeset viewer.