Ignore:
Timestamp:
Mar 3, 2009, 10:46:55 PM (11 years ago)
Author:
mnot@…
Message:

rearrange serving stale responses

File:
1 edited

Legend:

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

    r494 r495  
    619619            have heuristic expiry calculated, but is not fresh according to the calculations in
    620620              <xref target="expiration.model" />.</t>
     621          <t>Caches &MAY; return a stale response if disconnected or explicitly allowed (e.g.,
     622            the max-stale request directive; see <xref target="cache-request-directive" />).</t>
     623          <t>Otherwise, caches &SHOULD-NOT; return stale responses.</t>
    621624          <t>Caches &MUST-NOT; return a stale response if it is prohibited by an explicit
    622625            in-protocol directive (e.g., by a "no-store" or "no-cache" cache directive, a
     
    624627            "proxy-revalidate" cache-response-directive; see <xref target="cache-response-directive"
    625628             />). </t>
    626           <t>Caches &MAY; return a stale response if disconnected or explicitly allowed (e.g.,
    627             the max-stale request directive; see <xref target="cache-request-directive" />).</t>
    628           <t>Otherwise, caches &SHOULD-NOT; return stale responses.</t>
    629629          <t>Stale responses &SHOULD; have a Warning header with the 110 warn-code (see <xref
    630630              target="header.warning" />).</t>
Note: See TracChangeset for help on using the changeset viewer.