Changeset 471


Ignore:
Timestamp:
Mar 3, 2009, 7:01:40 PM (11 years ago)
Author:
mnot@…
Message:

first go at defining how methods affect caching.

File:
1 edited

Legend:

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

    r470 r471  
    390390      <section anchor="response.cacheability" title="Response Cacheability">
    391391        <t>A cache &MAY; store a response to any request, provided that: <list style="symbols">
     392                <t>The request method is defined as being cacheable, and</t>
    392393            <t>the "no-store" cache directive (see <xref target="header.cache-control" />) does not
    393394              appear in request or response headers, and</t>
     
    421422            <t>the presented target-URI and that of the stored response match (see
    422423              <cref>TBD</cref>), and</t>
     424            <t>the request method associated with the stored response allows it to be
     425              used for the presented request, and</t>
    423426            <t>selecting request-headers nominated by the stored response (if any) match (see <xref
    424427                target="caching.negotiated.responses" />), and</t>
     
    429432             />).</t>
    430433          </list>
    431         </t>
    432         <t>
    433           <cref>ISSUE: This doesn't specify whether the request method is part of the cache
    434           key.</cref>
    435434        </t>
    436435        <t>A shared cache &MAY; return a stored response, provided that: <list style="symbols">
Note: See TracChangeset for help on using the changeset viewer.