Changeset 2052 for draft-ietf-httpbis/latest/p6-cache.xml
- Timestamp:
- 16/12/12 03:46:23 (8 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p6-cache.xml
r2046 r2052 211 211 <list> 212 212 <t>The time at which the origin server intends that a representation 213 no longer be returnedby a cache without further validation.</t>213 no longer be sent by a cache without further validation.</t> 214 214 </list> 215 215 </t> … … 471 471 title="Constructing Responses from Caches"> 472 472 <t> 473 For a presented request, a cache &MUST-NOT; returna stored response,473 For a presented request, a cache &MUST-NOT; send a stored response, 474 474 unless: 475 475 <list style="symbols"> … … 796 796 </t> 797 797 <t> 798 A cache &MUST-NOT; returna stale response if it is prohibited by an798 A cache &MUST-NOT; send a stale response if it is prohibited by an 799 799 explicit in-protocol directive (e.g., by a "no-store" or "no-cache" cache 800 800 directive, a "must-revalidate" cache-response-directive, or an applicable … … 803 803 </t> 804 804 <t> 805 A cache &MUST-NOT; returnstale responses unless it is disconnected805 A cache &MUST-NOT; send stale responses unless it is disconnected 806 806 (i.e., it cannot contact the origin server or otherwise find a forward 807 807 path) or doing so is explicitly allowed (e.g., by the max-stale request … … 872 872 response while attempting to validate a response, it can either 873 873 forward this response to the requesting client, or act as if the 874 server failed to respond. In the latter case, it can returna874 server failed to respond. In the latter case, it can send a 875 875 previously stored response (see <xref 876 876 target="serving.stale.responses" />). … … 1073 1073 the cache will either remove all stored responses related to the effective 1074 1074 request URI, or will mark these as "invalid" and in need of a mandatory 1075 validation before they can be returnedin response to a subsequent request.1075 validation before they can be sent in response to a subsequent request. 1076 1076 </t> 1077 1077 <t> … … 1362 1362 the origin server. This allows an origin server to prevent a cache from 1363 1363 using it to satisfy a request without contacting it, even by caches that 1364 have been configured to returnstale responses.1364 have been configured to send stale responses. 1365 1365 </t> 1366 1366 <t> … … 1757 1757 rectified by a validation (for example, a lossy compression of the 1758 1758 representation) and &MUST-NOT; be deleted by a cache after validation, 1759 unless a full response is returned, in which case they &MUST; be.</t>1759 unless a full response is sent, in which case they &MUST; be.</t> 1760 1760 </list> 1761 1761 </t> … … 1783 1783 <iref primary="true" item="110 Response is Stale (warn code)" x:for-anchor=""/> 1784 1784 <t> 1785 A cache &SHOULD; include this whenever the returnedresponse is stale.1785 A cache &SHOULD; include this whenever the sent response is stale. 1786 1786 </t> 1787 1787 </section> … … 1790 1790 <iref primary="true" item="111 Revalidation Failed (warn code)" x:for-anchor=""/> 1791 1791 <t> 1792 A cache &SHOULD; include this when returning a stale response because an1792 A cache &SHOULD; include this when sending a stale response because an 1793 1793 attempt to validate the response failed, due to an inability to reach 1794 1794 the server. … … 2559 2559 <x:ref>Expires</x:ref> = HTTP-date 2560 2560 2561 <x:ref>HTTP-date</x:ref> = <HTTP-date, defined in [Part2], Section 8.1.1.1>2561 <x:ref>HTTP-date</x:ref> = <HTTP-date, defined in [Part2], Section 7.1.1.1> 2562 2562 2563 2563 <x:ref>OWS</x:ref> = <OWS, defined in [Part1], Section 3.2.3>
Note: See TracChangeset
for help on using the changeset viewer.