Ignore:
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.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p6-cache.html

    r780 r781  
    829829         <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
    830830         </li>
    831          <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>.
     831         <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>.
    832832         </li>
    833833      </ul>
Note: See TracChangeset for help on using the changeset viewer.