Ignore:
Timestamp:
Sep 11, 2009, 2:58:13 AM (10 years ago)
Author:
julian.reschke@…
Message:

remove requirement to consider Content-Location in successful responses in order to determine the appropriate response to use (see #167)

File:
1 edited

Legend:

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

    r689 r691  
    756756  target="serving.stale.responses" />).
    757757</t>
    758 <t>
    759   If a cache receives a successful response whose Content-Location field 
    760   matches that of an existing stored response for the same Request-URI, 
    761   whose entity-tag differs from that of the existing stored response, 
    762   and whose Date is more recent than that of the existing response, the 
    763   existing response &SHOULD-NOT; be returned in response to future 
    764   requests and &SHOULD; be deleted from the cache. <cref>DISCUSS: Not 
    765   sure if this is necessary.</cref>
    766 </t>
    767758</section>
    768759
     
    20702061<section anchor="changes.from.rfc.2616" title="Changes from RFC 2616">
    20712062<t>
     2063  Remove requirement to consider Content-Location in successful responses
     2064  in order to determine the appropriate response to use.
     2065  (<xref target="validation.model" />)
     2066</t>
     2067<t>
    20722068  Clarify denial of service attack avoidance requirement.
    20732069  (<xref target="invalidation.after.updates.or.deletions" />)
     
    23092305  <list style="symbols">
    23102306    <t>
     2307      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/167"/>:
     2308      "Content-Location on 304 responses"
     2309    </t>
     2310    <t>
    23112311      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/187"/>:
    23122312      "RFC2047 and warn-text"
Note: See TracChangeset for help on using the changeset viewer.