Re: draft-snell-http-prefer

On 12 October 2012 10:11, Ken Murchison <> wrote:
> In other words, is there a way to make the response suitable for a cache to
> use it to satisfy subsequent GET/HEAD requests, in the same way that POST
> responses can be?

p2 is quite clear on PUT and caches: PUT invalidates caches and nothing more.

My hope was that the rules for indicating that a response is cacheable
would be more generally applicable than for just POST.  I can see how
"return-representation" on PUT would be a useful optimization for
cache population.

Received on Friday, 12 October 2012 18:50:20 UTC