Ignore:
Timestamp:
Jul 24, 2010, 3:44:07 AM (9 years ago)
Author:
mnot@…
Message:

Allow new status codes to define whether they allow heuristic freshness (see #223).

File:
1 edited

Legend:

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

    r911 r914  
    3232  <!ENTITY safe-methods                "<xref target='Part2' x:rel='#safe.methods' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    3333  <!ENTITY weak-and-strong             "<xref target='Part4' x:rel='#weak.and.strong.validators' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     34  <!ENTITY status-codes                "<xref target='Part2' x:rel='#status.codes' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    3435]>
    3536<?rfc toc="yes" ?>
     
    596597<t>
    597598  If no explicit expiration time is present in a stored response that has a status code
    598   of 200, 203, 206, 300, 301 or 410, a heuristic expiration time can be
    599   calculated. Heuristics &MUST-NOT; be used for other response status codes.
     599  whose definition allows heuristic freshness to be used (including the following
     600  in &status-codes;: 200, 203, 206, 300, 301 and 410), a heuristic expiration time &MAY; be
     601  calculated. Heuristics &MUST-NOT; be used for response status codes that do not explicitly
     602  allow it.
    600603</t>
    601604<t>
Note: See TracChangeset for help on using the changeset viewer.