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.xml

    r780 r781  
    588588    <t>If the Expires response header (<xref target="header.expires" />) is present, use
    589589      its value minus the value of the Date response header, or</t>
    590     <t>Otherwise, no explicit expiration time is present in the response, but a heuristic
    591       may be used; see <xref target="heuristic.freshness" />.</t>
     590    <t>Otherwise, no explicit expiration time is present in the response. A heuristic
     591      freshness lifetime might be applicable; see <xref target="heuristic.freshness" />.</t>
    592592  </list>
    593593</t>
Note: See TracChangeset for help on using the changeset viewer.