Changeset 2240 for draft-ietf-httpbis/latest
- Timestamp:
- 07/05/13 10:16:35 (10 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p6-cache.html
r2239 r2240 698 698 request. A stored response is considered "fresh", as defined in <a href="#expiration.model" title="Freshness">Section 4.1</a>, if the response can be reused without "validation" (checking with the origin server to see if the cached response remains 699 699 valid for this request). A fresh response can therefore reduce both latency and network overhead each time it is reused. When 700 a cached response is not fresh, it might still be reusable if it can be freshened by validation (<a href="#validation.model" title="Validation">Section 4.2</a>) or if the origin is unavailable ( xref target="serving.stale.responses" />).700 a cached response is not fresh, it might still be reusable if it can be freshened by validation (<a href="#validation.model" title="Validation">Section 4.2</a>) or if the origin is unavailable (<a href="#serving.stale.responses" title="Serving Stale Responses">Section 4.1.4</a>). 701 701 </p> 702 702 <h2 id="rfc.section.1.1"><a href="#rfc.section.1.1">1.1</a> <a id="conformance" href="#conformance">Conformance and Error Handling</a></h2> -
draft-ietf-httpbis/latest/p6-cache.xml
r2239 r2240 171 171 When a cached response is not fresh, it might still be reusable if it can 172 172 be freshened by validation (<xref target="validation.model" />) or if the 173 origin is unavailable ( xref target="serving.stale.responses" />).173 origin is unavailable (<xref target="serving.stale.responses" />). 174 174 </t> 175 175
Note: See TracChangeset
for help on using the changeset viewer.