Changeset 782 for draft-ietf-httpbis
- Timestamp:
- 10/03/10 04:38:03 (12 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p6-cache.html
r781 r782 905 905 current_age = corrected_initial_age + resident_time; 906 906 </pre><h3 id="rfc.section.2.3.3"><a href="#rfc.section.2.3.3">2.3.3</a> <a id="serving.stale.responses" href="#serving.stale.responses">Serving Stale Responses</a></h3> 907 <p id="rfc.section.2.3.3.p.1">A "stale" response is one that either has explicit expiry information , or is allowed to have heuristic expiry calculated,908 butis not fresh according to the calculations in <a href="#expiration.model" title="Freshness Model">Section 2.3</a>.907 <p id="rfc.section.2.3.3.p.1">A "stale" response is one that either has explicit expiry information or is allowed to have heuristic expiry calculated, but 908 is not fresh according to the calculations in <a href="#expiration.model" title="Freshness Model">Section 2.3</a>. 909 909 </p> 910 910 <p id="rfc.section.2.3.3.p.2">Caches <em class="bcp14">MUST NOT</em> return a stale response if it is prohibited by an explicit in-protocol directive (e.g., by a "no-store" or "no-cache" cache -
draft-ietf-httpbis/latest/p6-cache.xml
r781 r782 727 727 <section anchor="serving.stale.responses" title="Serving Stale Responses"> 728 728 <t> 729 A "stale" response is one that either has explicit expiry information ,or is allowed to729 A "stale" response is one that either has explicit expiry information or is allowed to 730 730 have heuristic expiry calculated, but is not fresh according to the calculations in 731 731 <xref target="expiration.model" />.
Note: See TracChangeset
for help on using the changeset viewer.