Changeset 1314 for draft-ietf-httpbis/latest/p6-cache.xml
- Timestamp:
- 29/06/11 01:27:43 (10 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p6-cache.xml
r1303 r1314 882 882 caches can use them to keep their contents up-to-date. 883 883 </t> 884 885 Here, a non-error response is one with a 2xx or 3xx status code. 886 884 887 <t> 885 888 A cache &MUST; invalidate the effective Request URI 886 889 (&effective-request-uri;) as well as the URI(s) in the Location 887 and Content-Location header fields (if present) when requests with888 unsafe methods arereceived.890 and Content-Location header fields (if present) when a non-error 891 response to a request with an unsafe method is received. 889 892 </t> 890 893 <t> … … 896 899 <t> 897 900 A cache &SHOULD; invalidate the effective request URI 898 (&effective-request-uri;) when passing through requests with methods 899 whose safety is unknown. 900 </t> 901 <t> 902 Here, "invalidate" means that the cache will either remove all stored 901 (&effective-request-uri;) when it receives a non-error response 902 to a request with a method whose safety is unknown. 903 </t> 904 <t> 905 Here, a "non-error response" is one with a 2xx or 3xx status code. 906 "Invalidate" means that the cache will either remove all stored 903 907 responses related to the effective request URI, or will mark these as 904 908 "invalid" and in need of a mandatory validation before they can be returned … … 2723 2727 "Proxies don't 'understand' methods" 2724 2728 </t> 2729 <t> 2730 <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/235"/>: 2731 "Cache Invalidation only happens upon successful responses" 2732 </t> 2725 2733 </list> 2726 2734 </t>
Note: See TracChangeset
for help on using the changeset viewer.