Changeset 495
- Timestamp:
- 04/03/09 06:46:55 (13 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest-roy/p6-cache.xml
r494 r495 619 619 have heuristic expiry calculated, but is not fresh according to the calculations in 620 620 <xref target="expiration.model" />.</t> 621 <t>Caches &MAY; return a stale response if disconnected or explicitly allowed (e.g., 622 the max-stale request directive; see <xref target="cache-request-directive" />).</t> 623 <t>Otherwise, caches &SHOULD-NOT; return stale responses.</t> 621 624 <t>Caches &MUST-NOT; return a stale response if it is prohibited by an explicit 622 625 in-protocol directive (e.g., by a "no-store" or "no-cache" cache directive, a … … 624 627 "proxy-revalidate" cache-response-directive; see <xref target="cache-response-directive" 625 628 />). </t> 626 <t>Caches &MAY; return a stale response if disconnected or explicitly allowed (e.g.,627 the max-stale request directive; see <xref target="cache-request-directive" />).</t>628 <t>Otherwise, caches &SHOULD-NOT; return stale responses.</t>629 629 <t>Stale responses &SHOULD; have a Warning header with the 110 warn-code (see <xref 630 630 target="header.warning" />).</t>
Note: See TracChangeset
for help on using the changeset viewer.