Ignore:
Timestamp:
10/02/11 05:55:58 (10 years ago)
Author:
mnot@…
Message:

Setting Expires in the past doesn't guarantee that caches will always validate.

File:
1 edited

Legend:

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

    r1112 r1113  
    588588   If an origin server wishes to force a cache to validate every request, it
    589589   can assign an explicit expiration time in the past to indicate that the
    590    response is already stale.  Compliant caches will validate the cached response
    591    before reusing it for subsequent requests.
     590   response is already stale. Compliant caches will normally validate the
     591   cached response before reusing it for subsequent requests (see <xref
     592   target="serving.stale.responses" />).
    592593</t>
    593594<t>
Note: See TracChangeset for help on using the changeset viewer.