Changeset 492 for draft-ietf-httpbis
- Timestamp:
- 04/03/09 06:20:00 (13 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest-roy/p6-cache.xml
r491 r492 473 473 <t>When a response is "fresh" in the cache, it can be used to satisfy subsequent 474 474 requests without contacting the origin server, thereby improving efficiency.</t> 475 <t>This mechanism applies only to responses taken from a cache and not to first-hand responses.476 It cannot be used to force a user agent to refresh its display or reload a resource; its477 semantics apply only to caches. See <xref target="history.lists" /> for an explanation of478 the difference between caches and history mechanisms.</t>479 475 <t>The primary mechanism for avoiding requests is for an origin server to provide an 480 476 explicit expiration time in the future, using either the Expires header (<xref … … 503 499 several request cache directives, with the effect of either increasing or loosening 504 500 constraints on freshness. See <xref target="cache-request-directive" />.</t> 501 <t>Note that reshness applies only to cache operation; it cannot be used to force a user agent 502 to refresh its display or reload a resource. See <xref target="history.lists" /> for an explanation of 503 the difference between caches and history mechanisms.</t> 505 504 <t> 506 505 <cref>ISSUE: there are not requirements directly applying to cache-request-directives and
Note: See TracChangeset
for help on using the changeset viewer.