Re: hash in WebID - cachability problem

Henry Story wrote:
> Hi Tim,
> 
> A couple of weeks ago you mentioned a number of problems that you
> had with Tabulator and 303s. Do you have a description to those problems?
> Are they specific to Firefox and Tabulator, or would those be problems
> any JavaScript application would have?

Every client.

RFC 2616 says:
"The 303 response MUST NOT be cached, but the response to the second 
(redirected) request might be cacheable."

HTTPBis says:
"A 303 response SHOULD NOT be cached unless it is indicated as cacheable 
by Cache-Control or Expires header fields."

Of course most tooling will not cache 303s as it's been a MUST NOT for 
13+ years.

Best,

Nathan

Received on Sunday, 2 December 2012 19:04:03 UTC