Ignore:
Timestamp:
Jul 23, 2010, 7:45:21 AM (9 years ago)
Author:
mnot@…
Message:

Define caching requirements for methods (see #139).

File:
1 edited

Legend:

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

    r886 r888  
    7676  <!ENTITY p6-heuristic               "<xref target='Part6' x:rel='#heuristic.freshness'
    7777xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     78  <!ENTITY p6-explicit               "<xref target='Part6' x:rel='#calculating.freshness.lifetime'
     79xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     80  <!ENTITY p6-combine               "<xref target='Part6' x:rel='#combining.headers'
     81xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    7882]>
    7983<?rfc toc="yes" ?>
     
    864868</t>
    865869<t>
    866    The response to a GET request is cacheable if and only if it meets
    867    the requirements for HTTP caching described in &caching;.
     870   The response to a GET request is cacheable and &MAY; be used to satisfy
     871   subsequent GET and HEAD requests (see &caching;).
    868872</t>
    869873<t>
     
    889893</t>
    890894<t>
    891    The response to a HEAD request &MAY; be cacheable in the sense that the
    892    information contained in the response &MAY; be used to update a
    893    previously cached representation from that resource. If the new field values
     895   The response to a HEAD request is cacheable and &MAY; be used to satisfy
     896   a subsequent HEAD request; see &caching;. It also &MAY; be used to update a previously cached
     897   representation from that resource; if the new field values
    894898   indicate that the cached representation differs from the current representation (as
    895899   would be indicated by a change in Content-Length, Content-MD5, ETag
     
    942946</t>
    943947<t>
    944    Responses to this method are not cacheable, unless the response
    945    includes appropriate Cache-Control or Expires header fields. However,
    946    the 303 (See Other) response can be used to direct the user agent to
    947    retrieve a cacheable resource.
     948   Responses to POST requests are cacheable only when they
     949   include explicit freshness information (see &p6-explicit;). Such
     950   cached POST responses &MAY; be used to satisfy subsequent GET and
     951   HEAD requests. Note that POST caching is not widely implemented.
     952   However, the 303 (See Other) response can be used to direct the
     953   user agent to retrieve a cacheable resource.
    948954</t>
    949955</section>
     
    10391045   If the request passes through a cache and the Effective Request URI
    10401046   identifies one or more currently cached representations, those entries &SHOULD; be
    1041    treated as stale. Responses to the DELETE method &MUST-NOT; be cached.
     1047   treated as stale. Responses to the DELETE method are not cacheable.
    10421048</t>
    10431049</section>
     
    10711077   "message/http" (see &media-type-message-http;) and contain a message-body
    10721078   that encloses a copy of the entire request message.
    1073    Responses to the TRACE method &MUST-NOT; be cached.
     1079   Responses to the TRACE method are not cacheable.
    10741080</t>
    10751081</section>
Note: See TracChangeset for help on using the changeset viewer.