Ignore:
Timestamp:
Feb 9, 2011, 6:24:03 PM (9 years ago)
Author:
mnot@…
Message:

Clarify side effects of PUT and DELETE #225

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p2-semantics.xml

    r1106 r1111  
    7777  <!ENTITY p7-status-codes            "<xref target='Part7' x:rel='#status.code.definitions' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    7878  <!ENTITY p6-heuristic               "<xref target='Part6' x:rel='#heuristic.freshness' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    79   <!ENTITY p6-explicit               "<xref target='Part6' x:rel='#calculating.freshness.lifetime' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     79  <!ENTITY p6-explicit                "<xref target='Part6' x:rel='#calculating.freshness.lifetime' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     80  <!ENTITY p6-invalid                 "<xref target='Part6' x:rel='#invalidation.after.updates.or.deletions' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    8081]>
    8182<?rfc toc="yes" ?>
     
    10421043</t>
    10431044<t>
    1044    If the request passes through a cache that has one or more stored
    1045    responses for the effective request URI, those stored responses
    1046    &SHOULD; be marked as stale if the response to the PUT request
    1047    has a success status code. Responses to the PUT method are
    1048    not cacheable.
     1045   Responses to the PUT method are not cacheable. If a PUT request passes
     1046   through a cache that has one or more stored responses for the effective
     1047   request URI, those stored responses will be invalidated (see
     1048   &p6-invalid;).
    10491049</t>
    10501050<t>
     
    11021102</t>
    11031103<t>
    1104    If the request passes through a cache and the effective request URI
    1105    identifies one or more currently cached representations, those entries &SHOULD; be
    1106    treated as stale. Responses to the DELETE method are not cacheable.
     1104   Responses to the DELETE method are not cacheable. If a DELETE request
     1105   passes through a cache that has one or more stored responses for the
     1106   effective request URI, those stored responses will be invalidated (see
     1107   &p6-invalid;).
    11071108</t>
    11081109</section>
     
    40504051      "Migrate Upgrade details from RFC2817"
    40514052    </t>
     4053    <t>
     4054      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/225"/>:
     4055      "PUT side effect: invalidation or just stale?"
     4056    </t>
     4057     
    40524058  </list>
    40534059</t>
Note: See TracChangeset for help on using the changeset viewer.