Changeset 2512
- Timestamp:
- 19/12/13 03:07:42 (9 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p6-cache.xml
r2511 r2512 290 290 target="header.cache-control" />) does not appear in request or response 291 291 header fields, and</t> 292 <t>the "private" cacheresponse directive (see <xref292 <t>the "private" response directive (see <xref 293 293 target="cache-response-directive.private" />) does not appear in the 294 294 response, if the cache is shared, and</t> … … 301 301 <t>contains an <x:ref>Expires</x:ref> header field (see 302 302 <xref target="header.expires"/>), or</t> 303 <t>contains a max-age response cachedirective (see <xref303 <t>contains a max-age response directive (see <xref 304 304 target="cache-response-directive.max-age" />), or</t> 305 <t>contains a s-maxage response cachedirective (see <xref305 <t>contains a s-maxage response directive (see <xref 306 306 target="cache-response-directive.s-maxage" />) and the cache is 307 307 shared, or</t> … … 311 311 <t>has a status code that is defined as cacheable by default 312 312 (see <xref target="heuristic.freshness" />), or</t> 313 <t>contains a public response cachedirective (see <xref313 <t>contains a public response directive (see <xref 314 314 target="cache-response-directive.public"/>).</t> 315 315 </list> … … 567 567 provide an explicit expiration time in the future, using either the 568 568 <x:ref>Expires</x:ref> header field (<xref target="header.expires" />) or 569 the max-age response cachedirective (<xref569 the max-age response directive (<xref 570 570 target="cache-response-directive.max-age" />). Generally, origin servers 571 571 will assign future explicit expiration times to responses in the belief … … 637 637 freshness_lifetime) of a response by using the first match of: 638 638 <list style="symbols"> 639 <t>If the cache is shared and the s-maxage response cachedirective639 <t>If the cache is shared and the s-maxage response directive 640 640 (<xref target="cache-response-directive.s-maxage" />) is present, use its value, 641 641 or</t> 642 <t>If the max-age response cachedirective (<xref642 <t>If the max-age response directive (<xref 643 643 target="cache-response-directive.max-age" />) is present, use its value, or</t> 644 644 <t>If the <x:ref>Expires</x:ref> response header field … … 679 679 freshness whose status codes are defined as cacheable by default (see 680 680 &status-overview;), and those responses without explicit freshness that have 681 been marked as explicitly cacheable (e.g., with a "public" response cache681 been marked as explicitly cacheable (e.g., with a "public" response 682 682 directive). 683 683 </t> … … 1218 1218 </t> 1219 1219 <t> 1220 The "max-age" request directive indicates that the client is unwilling to1221 accept a response whose age is greater than the specified number of1222 seconds. Unless the max-stale request directive is also present, the 1223 clientis not willing to accept a stale response.1220 The "max-age" request directive indicates that the client is unwilling 1221 to accept a response whose age is greater than the specified number of 1222 seconds. Unless the max-stale request directive is also present, the client 1223 is not willing to accept a stale response. 1224 1224 </t> 1225 1225 <t> … … 2525 2525 </t> 2526 2526 <t> 2527 The "no-store" cacherequest directive doesn't apply to responses; i.e.,2527 The "no-store" request directive doesn't apply to responses; i.e., 2528 2528 a cache can satisfy a request with no-store on it, and does not invalidate 2529 2529 it. … … 2538 2538 </t> 2539 2539 <t> 2540 The "no-cache" response cachedirective's meaning has been clarified.2540 The "no-cache" response directive's meaning has been clarified. 2541 2541 (<xref target="cache-response-directive.no-cache" />) 2542 2542 </t>
Note: See TracChangeset
for help on using the changeset viewer.