Changeset 781 for draft-ietf-httpbis

Timestamp:

Mar 9, 2010, 8:26:23 PM (10 years ago)

Author:

mnot@…

Message:

refine language around heuristic freshness to clarify that it isn't always allowed.

Location:

draft-ietf-httpbis/latest

Files:

• p6-cache.html (modified) (1 diff)
• p6-cache.xml (modified) (1 diff)

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

@@ -829 +829 @@
          <li>If the Expires response header (<a href="#header.expires" id="rfc.xref.header.expires.3" title="Expires">Section&nbsp;3.3</a>) is present, use its value minus the value of the Date response header, or
          </li>
-         <li>Otherwise, no explicit expiration time is present in the response, but a heuristic may be used; see <a href="#heuristic.freshness" title="Calculating Heuristic Freshness">Section&nbsp;2.3.1.1</a>.
+         <li>Otherwise, no explicit expiration time is present in the response. A heuristic freshness lifetime might be applicable; see <a href="#heuristic.freshness" title="Calculating Heuristic Freshness">Section&nbsp;2.3.1.1</a>.
          </li>
       </ul>

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

@@ -588 +588 @@
     <t>If the Expires response header (<xref target="header.expires" />) is present, use
       its value minus the value of the Date response header, or</t>
-    <t>Otherwise, no explicit expiration time is present in the response, but a heuristic
-      may be used; see <xref target="heuristic.freshness" />.</t>
+    <t>Otherwise, no explicit expiration time is present in the response. A heuristic
+      freshness lifetime might be applicable; see <xref target="heuristic.freshness" />.</t>
   </list>
 </t>