Changeset 2002
- Timestamp:
- 28/11/12 01:10:07 (10 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p6-cache.html
r2001 r2002 916 916 </pre> <p id="rfc.section.4.1.p.6">The freshness_lifetime is defined in <a href="#calculating.freshness.lifetime" title="Calculating Freshness Lifetime">Section 4.1.1</a>; the current_age is defined in <a href="#age.calculations" title="Calculating Age">Section 4.1.3</a>. 917 917 </p> 918 <p id="rfc.section.4.1.p.7"> Additionally, clients can influence freshness calculation — either constraining or it relaxing it — by using the max-age and919 min-fresh request cache directives. See <a href="#cache-request-directive" title="Request Cache-Control Directives">Section 7.2.1</a> for details.918 <p id="rfc.section.4.1.p.7">Clients can send the max-age or min-fresh cache directives in a request to constrain or relax freshness calculations for the 919 corresponding response (<a href="#cache-request-directive" title="Request Cache-Control Directives">Section 7.2.1</a>). 920 920 </p> 921 921 <p id="rfc.section.4.1.p.8">Note that freshness applies only to cache operation; it cannot be used to force a user agent to refresh its display or reload -
draft-ietf-httpbis/latest/p6-cache.xml
r1995 r2002 578 578 </t> 579 579 <t> 580 Additionally, clients can influence freshness calculation — either 581 constraining or it relaxing it — by using the max-age and min-fresh 582 request cache directives. See <xref target="cache-request-directive" /> 583 for details. 580 Clients can send the max-age or min-fresh cache directives in a request to 581 constrain or relax freshness calculations for the corresponding response 582 (<xref target="cache-request-directive" />). 584 583 </t> 585 584 <t>
Note: See TracChangeset
for help on using the changeset viewer.