- From: Nathan <nathan@webr3.org>
- Date: Mon, 03 Dec 2012 11:01:18 +0000
- To: Henry Story <henry.story@bblfish.net>
- CC: Kingsley Idehen <kidehen@openlinksw.com>, public-webid@w3.org
all applications that use HTTP and need to cache, including intermediaries, not just javascript applications. Henry Story wrote: > We still have to see what the issues are here. It seems that the cacheability problem pointed out by Nathan > would affect all JavaScript applications, not just tabulator > > [[ > > 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. > ]]
Received on Monday, 3 December 2012 11:02:23 UTC