Changeset 875 for draft-ietf-httpbis/latest/p6-cache.html
- Timestamp:
- 23/07/10 05:43:59 (12 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p6-cache.html
r868 r875 645 645 </p> 646 646 <ul class="empty"> 647 <li>The time at which the origin server intends that an entity should no longer be returned by a cache without further validation.</li> 647 <li>The time at which the origin server intends that a representation should no longer be returned by a cache without further 648 validation. 649 </li> 648 650 </ul> 649 651 <p id="rfc.section.1.2.p.4"> <span id="rfc.iref.h.1"></span> <dfn>heuristic expiration time</dfn> … … 680 682 </p> 681 683 <ul class="empty"> 682 <li>A protocol element (e.g., an entity 684 <li>A protocol element (e.g., an entity-tag or a Last-Modified time) that is used to find out whether a stored response has an 683 685 equivalent copy of a representation. 684 686 </li> … … 1018 1020 <p id="rfc.section.2.8.p.5">If a header field-name in the new response matches more than one header in the stored response, all such stored headers <em class="bcp14">MUST</em> be replaced. 1019 1021 </p> 1020 <p id="rfc.section.2.8.p.6">The updated response can <span class="comment" id="TODO-is-req">[<a href="#TODO-is-req" class="smpl">TODO-is-req</a>: requirement?]</span> be used to replace the stored response in cache. In the case of a 206 response, the combined entity-body<em class="bcp14">MAY</em> be stored.1022 <p id="rfc.section.2.8.p.6">The updated response can <span class="comment" id="TODO-is-req">[<a href="#TODO-is-req" class="smpl">TODO-is-req</a>: requirement?]</span> be used to replace the stored response in cache. In the case of a 206 response, the combined representation <em class="bcp14">MAY</em> be stored. 1021 1023 </p> 1022 1024 <p id="rfc.section.2.8.p.7"> <span class="comment" id="ISSUE-how-head">[<a href="#ISSUE-how-head" class="smpl">ISSUE-how-head</a>: discuss how to handle HEAD updates]</span> … … 1121 1123 </p> 1122 1124 <ul class="empty"> 1123 <li>The no-transform request directive indicates that an intermediate cache or proxy <em class="bcp14">MUST NOT</em> change the Content-Encoding, Content-Range or Content-Type request headers, nor the request entity-body.1125 <li>The no-transform request directive indicates that an intermediate cache or proxy <em class="bcp14">MUST NOT</em> change the Content-Encoding, Content-Range or Content-Type request headers, nor the request representation. 1124 1126 </li> 1125 1127 </ul> … … 1225 1227 </p> 1226 1228 <ul class="empty"> 1227 <li>The no-transform response directive indicates that an intermediate cache or proxy <em class="bcp14">MUST NOT</em> change the Content-Encoding, Content-Range or Content-Type response headers, nor the response entity-body.1229 <li>The no-transform response directive indicates that an intermediate cache or proxy <em class="bcp14">MUST NOT</em> change the Content-Encoding, Content-Range or Content-Type response headers, nor the response representation. 1228 1230 </li> 1229 1231 </ul> … … 1412 1414 <p id="rfc.section.3.6.p.17"> 214 Transformation applied </p> 1413 1415 <ul class="empty"> 1414 <li><em class="bcp14">MUST</em> be added by an intermediate cache or proxy if it applies any transformation changing the content-coding (as specified in the 1415 Content-Encoding header) or media-type (as specified in the Content-Type header) of the response, or the entity-body of the 1416 response, unless this Warning code already appears in the response. 1416 <li><em class="bcp14">MUST</em> be added by an intermediate proxy if it applies any transformation to the representation, such as changing the content-coding, 1417 media-type, or modifying the representation data, unless this Warning code already appears in the response. 1417 1418 </li> 1418 1419 </ul> … … 1423 1424 </ul> 1424 1425 <h1 id="rfc.section.4"><a href="#rfc.section.4">4.</a> <a id="history.lists" href="#history.lists">History Lists</a></h1> 1425 <p id="rfc.section.4.p.1">User agents often have history mechanisms, such as "Back" buttons and history lists, that can be used to redisplay a n entity1426 <p id="rfc.section.4.p.1">User agents often have history mechanisms, such as "Back" buttons and history lists, that can be used to redisplay a representation 1426 1427 retrieved earlier in a session. 1427 1428 </p>
Note: See TracChangeset
for help on using the changeset viewer.