Ignore:
Timestamp:
29/12/09 09:22:21 (10 years ago)
Author:
mnot@…
Message:

require understanding of response status code, as well as response cacheability, for storing a response (see #199).

File:
1 edited

Legend:

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

    r736 r737  
    423423  <list style="symbols">
    424424    <t>The request method is understood by the cache and defined as being cacheable, and</t>
    425     <t>The response status is understood by the cache and defined as being cacheable, and</t>
     425    <t>the response status code is understood by the cache, and</t>
    426426    <t>the "no-store" cache directive (see <xref target="header.cache-control" />) does not
    427427       appear in request or response headers, and</t>
    428     <t>the "private" cache response directive (see <xref target="header.cache-control" />
     428    <t>the "private" cache response directive (see <xref target="cache-response-directive" />
    429429       does not appear in the response, if the cache is shared, and</t>
    430430    <t>the "Authorization" header (see &header-authorization;) does not appear in the request, if
    431431       the cache is shared (unless the "public" directive is present; see <xref
    432        target="header.cache-control" />), and</t>           
    433     <t>the cache understands partial responses, if the response is partial or incomplete
    434        (see <xref target="errors.or.incomplete.response.cache.behavior" />).</t>
    435   </list>
     432       target="header.cache-control" />), and</t>
     433    <t>the response either:
     434      <list style="symbols">
     435        <t>contains an Expires header (see <xref target="header.expires" />), or</t>
     436        <t>contains a max-age response cache directive (see <xref target="cache-response-directive" />), or</t>
     437        <t>contains a s-maxage response cache directive and the cache is shared, or</t>
     438        <t>contains a Cache Control Extension (see <xref target="cache.control.extensions" />) that allows it to be cached, or</t>
     439        <t>has a status code that can be served with heuristic freshness (see <xref
     440           target="heuristic.freshness" />).</t>
     441      </list>
     442    </t>
     443  </list>
     444</t>
     445<t>
     446  In this context, a cache has "understood" a request method or a response status
     447  code if it recognises it and implements any cache-specific behaviour. In
     448  particular, 206 Partial Content responses cannot be cached by an
     449  implementation that does not handle partial content
     450  (see <xref target="errors.or.incomplete.response.cache.behavior" />).
    436451</t>
    437452<t>
Note: See TracChangeset for help on using the changeset viewer.