Changeset 823 for draft-ietf-httpbis/latest/p6-cache.xml
- Timestamp:
- 26/05/10 17:25:13 (12 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p6-cache.xml
r817 r823 18 18 <!ENTITY basic-rules "<xref target='Part1' x:rel='#basic.rules' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> 19 19 <!ENTITY uri "<xref target='Part1' x:rel='#uri' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> 20 <!ENTITY effective-request-uri "<xref target='Part1' x:rel='#effective.request.uri' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> 20 21 <!ENTITY messaging "<xref target='Part1' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> 21 22 <!ENTITY conditional "<xref target='Part4' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> … … 478 479 For a presented request, a cache &MUST-NOT; return a stored response, unless: 479 480 <list style="symbols"> 480 <t>The presented Request-URI and that of the stored response match 481 (<cref anchor="TODO-Request-URI">Need to find a new term for this, as Part 482 1 doesn't define Request-URI anymore; the new term request-target does not 483 work for this. (see <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/196" />)</cref>), and</t> 481 <t>The presented Effective Request URI (&effective-request-uri;) and that of the stored response match, and</t> 484 482 <t>the request method associated with the stored response allows it to be 485 483 used for the presented request, and</t> … … 798 796 </t> 799 797 <t> 800 The following HTTP methods &MUST; cause a cache to invalidate the Request-URIas well798 The following HTTP methods &MUST; cause a cache to invalidate the Effective Request URI (&effective-request-uri;) as well 801 799 as the URI(s) in the Location and Content-Location headers (if present): 802 800 <list style="symbols"> … … 808 806 <t> 809 807 An invalidation based on a URI from a Location or Content-Location header &MUST-NOT; 810 be performed if the host part of that URI differs from the host part in the Request-URI.808 be performed if the host part of that URI differs from the host part in the Effective Request URI (&effective-request-uri;). 811 809 This helps prevent denial of service attacks. 812 810 </t> … … 816 814 <t> 817 815 A cache that passes through requests for methods it does not understand &SHOULD; 818 invalidate the Request-URI.816 invalidate the Effective Request URI (&effective-request-uri;). 819 817 </t> 820 818 <t> 821 819 Here, "invalidate" means that the cache will either remove all stored responses related 822 to the Request-URI, or will mark these as "invalid" and in need of a mandatory validation820 to the Effective Request URI, or will mark these as "invalid" and in need of a mandatory validation 823 821 before they can be returned in response to a subsequent request. 824 822 </t> … … 2450 2448 </list> 2451 2449 </t> 2450 <t> 2451 Partly resolved issues: 2452 <list style="symbols"> 2453 <t> 2454 <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/196"/>: 2455 "Term for the requested resource's URI" 2456 </t> 2457 </list> 2458 </t> 2452 2459 </section> 2453 2460
Note: See TracChangeset
for help on using the changeset viewer.