Changeset 492 for draft-ietf-httpbis

Timestamp:

Mar 3, 2009, 10:20:00 PM (11 years ago)

Author:

mnot@…

Message:

tweak freshenss intro talk about history, cache specificity

File:

• draft-ietf-httpbis/latest-roy/p6-cache.xml (modified) (2 diffs)

draft-ietf-httpbis/latest-roy/p6-cache.xml

@@ -473 +473 @@
         <t>When a response is "fresh" in the cache, it can be used to satisfy subsequent
           requests without contacting the origin server, thereby improving efficiency.</t>
-        <t>This mechanism applies only to responses taken from a cache and not to first-hand responses.
-          It cannot be used to force a user agent to refresh its display or reload a resource; its
-          semantics apply only to caches. See <xref target="history.lists" /> for an explanation of
-          the difference between caches and history mechanisms.</t>
         <t>The primary mechanism for avoiding requests is for an origin server to provide an
           explicit expiration time in the future, using either the Expires header (<xref
@@ -503 +499 @@
           several request cache directives, with the effect of either increasing or loosening
           constraints on freshness. See <xref target="cache-request-directive" />.</t>
+        <t>Note that reshness applies only to cache operation; it cannot be used to force a user agent 
+        to refresh its display or reload a resource. See <xref target="history.lists" /> for an explanation of
+          the difference between caches and history mechanisms.</t>
         <t>
           <cref>ISSUE: there are not requirements directly applying to cache-request-directives and