Ignore:
Timestamp:
26/09/12 16:14:22 (9 years ago)
Author:
mnot@…
Message:

Make it crystal clear that cached POST responses can't be used to satisfy future POST requests

File:
1 edited

Legend:

Unmodified
Added
Removed

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

    r1912 r1913  
    11961196</t>
    11971197<t>
    1198    Responses to POST requests are only cacheable when they
    1199    include explicit freshness information (see &p6-explicit;). A
    1200    cached POST response with a <x:ref>Content-Location</x:ref> header field
    1201    (see &header-content-location;) whose value is the effective
    1202    Request URI &MAY; be used to satisfy subsequent GET and HEAD requests.
     1198   Responses to POST requests are only cacheable when they include explicit
     1199   freshness information (see &p6-explicit;). A cached POST response with a
     1200   <x:ref>Content-Location</x:ref> header field (see
     1201   &header-content-location;) whose value is the effective Request URI &MAY;
     1202   be used to satisfy subsequent GET and HEAD (not POST) requests.
    12031203</t>
    12041204<t>
Note: See TracChangeset for help on using the changeset viewer.