Changeset 910


Ignore:
Timestamp:
Jul 24, 2010, 1:54:02 AM (9 years ago)
Author:
mnot@…
Message:

Require Content-Location on POST responses in order to use them to satisfy a GET/HEAD (see #139).

File:
1 edited

Legend:

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

    r901 r910  
    940940</t>
    941941<t>
    942    Responses to POST requests are cacheable only when they
    943    include explicit freshness information (see &p6-explicit;). Such
    944    cached POST responses &MAY; be used to satisfy subsequent GET and
    945    HEAD requests. Note that POST caching is not widely implemented.
     942   Responses to POST requests are only cacheable when they
     943   include explicit freshness information (see &p6-explicit;). A
     944   cached POST response with a Content-Location header
     945   (see &header-content-location;) whose value is the Effective
     946   Request URI &MAY; be used to satisfy subsequent GET and HEAD requests.
     947</t>
     948<t>
     949   Note that POST caching is not widely implemented.
    946950   However, the 303 (See Other) response can be used to direct the
    947951   user agent to retrieve a cacheable resource.
Note: See TracChangeset for help on using the changeset viewer.