- From: Jeffrey Mogul <mogul@pa.dec.com>
- Date: Thu, 11 Jan 96 11:29:09 PST
- To: "Roy T. Fielding" <fielding@avron.ICS.UCI.EDU>
- Cc: http-caching@pa.dec.com
"public" would replace "cachable" -- it is simply a better name. I
think it would also override the non-cachable default on methods
other than GET and HEAD -- the current wording in draft 00 is too
restrictive in the method sections.
I agree that the current wording is probably too restrictive (in
light of the discussions we've had on caching POST and PUT responses).
What I'm not sure about is whether it makes sense to allow
Cache-control: public
on the response to *any* method, or whether we should be more
selective.
For example, does this make sense for DELETE? Or TRACE?
Having raised those questions, I'd appreciate it if people did NOT
immediately start a new discussion of that. I'd like to hold
off on discussions of extending caching to new methods (including
POST and PUT) until we are somewhat closer to consensus on the
caching design for GET. I will mark this as an action item, to
be taken up in the (near) future.
-Jeff
Received on Thursday, 11 January 1996 19:40:10 UTC