Changeset 875 for draft-ietf-httpbis/latest/p6-cache.html

Timestamp:

Jul 22, 2010, 10:43:59 PM (9 years ago)

Author:

fielding@…

Message:

regenerate html

File:

• draft-ietf-httpbis/latest/p6-cache.html (modified) (7 diffs)

draft-ietf-httpbis/latest/p6-cache.html

@@ -645 +645 @@
       </p>
       <ul class="empty">
-         <li>The time at which the origin server intends that an entity should no longer be returned by a cache without further validation.</li>
+         <li>The time at which the origin server intends that a representation should no longer be returned by a cache without further
+            validation.
+         </li>
       </ul>
       <p id="rfc.section.1.2.p.4"> <span id="rfc.iref.h.1"></span>  <dfn>heuristic expiration time</dfn>  
@@ -680 +682 @@
       </p>
       <ul class="empty">
-         <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
+         <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
             equivalent copy of a representation.
          </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.
       </p>
-      <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.
+      <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.
       </p>
       <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>
       <ul class="empty">
-         <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.
+         <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.
          </li>
       </ul>
@@ -1225 +1227 @@
       </p>
       <ul class="empty">
-         <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.
+         <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.
          </li>
       </ul>
@@ -1412 +1414 @@
       <p id="rfc.section.3.6.p.17"> 214 Transformation applied </p>
       <ul class="empty">
-         <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
-            Content-Encoding header) or media-type (as specified in the Content-Type header) of the response, or the entity-body of the
-            response, unless this Warning code already appears in the response.
+         <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,
+            media-type, or modifying the representation data, unless this Warning code already appears in the response.
          </li>
       </ul>
@@ -1423 +1424 @@
       </ul>
       <h1 id="rfc.section.4"><a href="#rfc.section.4">4.</a>&nbsp;<a id="history.lists" href="#history.lists">History Lists</a></h1>
-      <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 an entity
+      <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
          retrieved earlier in a session.
       </p>