Changeset 493

Timestamp:

04/03/09 06:21:25 (13 years ago)

Author:

mnot@…

Message:

tweak freshness intro

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>The primary mechanism for avoiding requests is for an origin server to provide an
+        <t>The primary mechanism for determining freshness is for an origin server to provide an
           explicit expiration time in the future, using either the Expires header (<xref
             target="header.expires" />) or the max-age response cache directive (<xref
@@ -483 +483 @@
           stale, so that caches should validate it before using it for subsequent requests. <cref>This wording may cause confusion, because the response may still be served stale.</cref></t>
         <t>Since origin servers do not always provide explicit expiration times, HTTP caches may
-          assign heuristic expiration times when they are not specified, employing algorithms that
+          also assign heuristic expiration times when they are not specified, employing algorithms that
           use other header values (such as the Last-Modified time) to estimate a plausible
           expiration time. The HTTP/1.1 specification does not provide specific algorithms, but does
           impose worst-case constraints on their results.</t>
-        <t>The calculation to determine if a response has expired is:</t>
+        <t>The calculation to determine if a response is fresh is:</t>
         <figure>
           <artwork type="code">