Ignore:
Timestamp:
May 26, 2010, 10:25:13 AM (10 years ago)
Author:
julian.reschke@…
Message:

Introduce term "effective request URI" and use it throughout; may require some more fine-tuning (see #196)

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p6-cache.xml

    r817 r823  
    1818  <!ENTITY basic-rules                 "<xref target='Part1' x:rel='#basic.rules' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    1919  <!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'/>">
    2021  <!ENTITY messaging                   "<xref target='Part1' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    2122  <!ENTITY conditional                 "<xref target='Part4' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     
    478479  For a presented request, a cache &MUST-NOT; return a stored response, unless:
    479480  <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>
    484482    <t>the request method associated with the stored response allows it to be
    485483      used for the presented request, and</t>
     
    798796</t>
    799797<t>
    800   The following HTTP methods &MUST; cause a cache to invalidate the Request-URI as well
     798  The following HTTP methods &MUST; cause a cache to invalidate the Effective Request URI (&effective-request-uri;) as well
    801799  as the URI(s) in the Location and Content-Location headers (if present):
    802800  <list style="symbols">
     
    808806<t>
    809807  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;).
    811809  This helps prevent denial of service attacks.
    812810</t>
     
    816814<t>
    817815  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;).
    819817</t>
    820818<t>
    821819  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 validation
     820  to the Effective Request URI, or will mark these as "invalid" and in need of a mandatory validation
    823821  before they can be returned in response to a subsequent request.
    824822</t>
     
    24502448  </list>
    24512449</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>
    24522459</section>
    24532460
Note: See TracChangeset for help on using the changeset viewer.