Thanks Julian. Brian's reference to 2616bis tripped me to think that it is something new in the bis draft. It can't be.
Regards, Subbu On Apr 25, 2008, at 3:08 AM, Julian Reschke wrote:
Subbu Allamaraju wrote:On Apr 24, 2008, at 9:24 AM, Brian Smith wrote:Any reason why? With 2616, if a response has Content-Location and Cache-Control, caches are free to replace currently cached copies with the representation in the response. The response to the PUT itself will be fresh, but a subsequent GET to the Content-Location URI may be from a cache.Thomas Broyer wrote:On Wed, Apr 23, 2008 at 8:28 PM, Nikunj Mehta wrote:The HTTP spec states that Responses to this [PUT] method are not cacheable....except if you include a proper Cache-Control header.The latest HTTPbis draft just says "Responses to this method are not cacheable." for PUT.For the record: RCF2616 and httpbis say exactly the same thing. BR, Julian