Changeset 1290 for draft-ietf-httpbis/latest
- Timestamp:
- 27/05/11 04:06:18 (11 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p6-cache.html
r1289 r1290 961 961 </p> 962 962 <h2 id="rfc.section.2.5"><a href="#rfc.section.2.5">2.5</a> <a id="invalidation.after.updates.or.deletions" href="#invalidation.after.updates.or.deletions">Request Methods that Invalidate</a></h2> 963 <p id="rfc.section.2.5.p.1">Because unsafe request methods (<a href="p2-semantics.html#safe.methods" title="Safe Methods">Section 7.1.1</a> of <a href="#Part2" id="rfc.xref.Part2.3"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>) have the potential for changing state on the origin server, intervening caches can use them to keep their contents up-to-date. 964 </p> 965 <p id="rfc.section.2.5.p.2">A cache <em class="bcp14">MUST</em> invalidate the effective Request URI (<a href="p1-messaging.html#effective.request.uri" title="Effective Request URI">Section 4.3</a> of <a href="#Part1" id="rfc.xref.Part1.13"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) as well as the URI(s) in the Location and Content-Location header fields (if present) when the following request methods 966 are received: 967 </p> 968 <ul> 969 <li>PUT</li> 970 <li>DELETE</li> 971 <li>POST</li> 972 </ul> 963 <p id="rfc.section.2.5.p.1">Because unsafe request methods (<a href="p2-semantics.html#safe.methods" title="Safe Methods">Section 7.1.1</a> of <a href="#Part2" id="rfc.xref.Part2.3"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>) such as PUT, POST or DELETE have the potential for changing state on the origin server, intervening caches can use them 964 to keep their contents up-to-date. 965 </p> 966 <p id="rfc.section.2.5.p.2">A cache <em class="bcp14">MUST</em> invalidate the effective Request URI (<a href="p1-messaging.html#effective.request.uri" title="Effective Request URI">Section 4.3</a> of <a href="#Part1" id="rfc.xref.Part1.13"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) as well as the URI(s) in the Location and Content-Location header fields (if present) when requests with unsafe methods 967 are received. 968 </p> 973 969 <p id="rfc.section.2.5.p.3">However, a cache <em class="bcp14">MUST NOT</em> invalidate a URI from a Location or Content-Location header field if the host part of that URI differs from the host part 974 970 in the effective request URI (<a href="p1-messaging.html#effective.request.uri" title="Effective Request URI">Section 4.3</a> of <a href="#Part1" id="rfc.xref.Part1.14"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>). This helps prevent denial of service attacks. 975 971 </p> 976 <p id="rfc.section.2.5.p.4">A cache that passes through requests with methods it does not understand <em class="bcp14">SHOULD</em> invalidate the effective request URI (<a href="p1-messaging.html#effective.request.uri" title="Effective Request URI">Section 4.3</a> of <a href="#Part1" id="rfc.xref.Part1.15"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>).972 <p id="rfc.section.2.5.p.4">A cache <em class="bcp14">SHOULD</em> invalidate the effective request URI (<a href="p1-messaging.html#effective.request.uri" title="Effective Request URI">Section 4.3</a> of <a href="#Part1" id="rfc.xref.Part1.15"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) when passing through requests with methods whose safety is unknown. 977 973 </p> 978 974 <p id="rfc.section.2.5.p.5">Here, "invalidate" means that the cache will either remove all stored responses related to the effective request URI, or will … … 1967 1963 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/38">http://tools.ietf.org/wg/httpbis/trac/ticket/38</a>>: "Mismatch Vary" 1968 1964 </li> 1965 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/289">http://tools.ietf.org/wg/httpbis/trac/ticket/289</a>>: "Proxies don't 'understand' methods" 1966 </li> 1969 1967 </ul> 1970 1968 <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1> -
draft-ietf-httpbis/latest/p6-cache.xml
r1289 r1290 870 870 title="Request Methods that Invalidate"> 871 871 <t> 872 Because unsafe request methods (&safe-methods;) have the potential for changing873 state on the origin server, intervening caches can use them to keep their874 c ontents up-to-date.872 Because unsafe request methods (&safe-methods;) such as PUT, POST or DELETE 873 have the potential for changing state on the origin server, intervening 874 caches can use them to keep their contents up-to-date. 875 875 </t> 876 876 <t> 877 877 A cache &MUST; invalidate the effective Request URI 878 878 (&effective-request-uri;) as well as the URI(s) in the Location 879 and Content-Location header fields (if present) when the following 880 request methods are received: 881 <list style="symbols"> 882 <t>PUT</t> 883 <t>DELETE</t> 884 <t>POST</t> 885 </list> 879 and Content-Location header fields (if present) when requests with 880 unsafe methods are received. 886 881 </t> 887 882 <t> … … 892 887 </t> 893 888 <t> 894 A cache that passes through requests with methods it does not understand 895 &SHOULD; invalidate the effective request URI (&effective-request-uri;). 889 A cache &SHOULD; invalidate the effective request URI 890 (&effective-request-uri;) when passing through requests with methods 891 whose safety is unknown. 896 892 </t> 897 893 <t> … … 2711 2707 "Mismatch Vary" 2712 2708 </t> 2709 <t> 2710 <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/289"/>: 2711 "Proxies don't 'understand' methods" 2712 </t> 2713 2713 </list> 2714 2714 </t>
Note: See TracChangeset
for help on using the changeset viewer.