Changeset 910

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:

• draft-ietf-httpbis/latest/p2-semantics.xml (modified) (1 diff)

draft-ietf-httpbis/latest/p2-semantics.xml

@@ -940 +940 @@
 </t>
 <t>
-   Responses to POST requests are cacheable only when they
-   include explicit freshness information (see &p6-explicit;). Such 
-   cached POST responses &MAY; be used to satisfy subsequent GET and 
-   HEAD requests. Note that POST caching is not widely implemented. 
+   Responses to POST requests are only cacheable when they
+   include explicit freshness information (see &p6-explicit;). A
+   cached POST response with a Content-Location header 
+   (see &header-content-location;) whose value is the Effective 
+   Request URI &MAY; be used to satisfy subsequent GET and HEAD requests.
+</t>
+<t>
+   Note that POST caching is not widely implemented. 
    However, the 303 (See Other) response can be used to direct the 
    user agent to retrieve a cacheable resource.