* WGs marked with an * asterisk has had at least one new draft made available during the last 5 days

Ticket #167: 167.diff

File 167.diff, 1.6 KB (added by julian.reschke@gmx.de, 6 years ago)

Proposed patch for part 6.

  • p6-cache.xml

    755755  respond. In the latter case, it &MAY; return a previously stored response (see <xref 
    756756  target="serving.stale.responses" />). 
    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> 
    769760<section anchor="invalidation.after.updates.or.deletions" title="Request Methods that Invalidate"> 
    20702061<section anchor="changes.from.rfc.2616" title="Changes from RFC 2616"> 
     2063  Remove requirement to consider Content-Location in successful responses 
     2064  in order to invalidate cached responses. 
     2065  (<xref target="validation.model" />) 
    20722068  Clarify denial of service attack avoidance requirement. 
    20732069  (<xref target="invalidation.after.updates.or.deletions" />) 
    23082304  Closed issues: 
    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" 
    23132313    </t>