Changeset 1113 for draft-ietf-httpbis/latest/p6-cache.html
- Timestamp:
- 10/02/11 05:55:58 (12 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p6-cache.html
r1112 r1113 813 813 </p> 814 814 <p id="rfc.section.2.3.p.3">If an origin server wishes to force a cache to validate every request, it can assign an explicit expiration time in the past 815 to indicate that the response is already stale. Compliant caches will validate the cached response before reusing it for subsequent816 requests.815 to indicate that the response is already stale. Compliant caches will normally validate the cached response before reusing 816 it for subsequent requests (see <a href="#serving.stale.responses" title="Serving Stale Responses">Section 2.3.3</a>). 817 817 </p> 818 818 <p id="rfc.section.2.3.p.4">Since origin servers do not always provide explicit expiration times, a cache <em class="bcp14">MAY</em> assign a heuristic expiration time when an explicit time is not specified, employing algorithms that use other header field
Note: See TracChangeset
for help on using the changeset viewer.