W3C home > Mailing lists > Public > public-html-comments@w3.org > August 2011

appcache & cache-control

From: Yves Lafon <ylafon@w3.org>
Date: Wed, 3 Aug 2011 16:11:13 -0400 (EDT)
To: public-html-comments@w3.org
Message-ID: <alpine.DEB.1.10.1108031603080.2827@wnl.j3.bet>
7.3, there is this note:
HTTP caching rules, such as Cache-Control: no-store, are ignored for the 
purposes of the application cache download process.

Either it needs to be called out as a willful violation of RFC2616, or 
step 6 should be amended to add the presence of a Cache-Control: no-store
to the list of failures like this:
Otherwise, if fetching the manifest fails in some other way (e.g. the 
server returns another 4xx or 5xx response or equivalent, or the server 
indicates that the representation cannot be stored, or there is a 
DNS error, or the connection times out, or the user cancels the download, 
or the parser for manifests fails when checking the magic signature)
The second option would also help apps developers catching wrong 
configuration server-side and allow better caching of those resources 
(like for users behind regional caches).

Baroula que barouleras, au tiéu toujou t'entourneras.

Received on Wednesday, 3 August 2011 20:11:18 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:26:27 UTC