- From: Bjoern Hoehrmann <derhoermi@gmx.net>
- Date: Tue, 21 Jan 2014 01:55:48 +0100
- To: aga@flyingsoft.phatcode.net
- Cc: <public-webapps@w3.org>
* aga@flyingsoft.phatcode.net wrote: >Please refer to the following bug report: >http://code.google.com/p/chromium/issues/detail?id=336292 > >In summary, all Webkit-derived browsers (excluding Safari 5.1.7 on >Windows) do not do in-process (in-instance?) caching when the header is >"expired". Firefox, IE11 (but not IE10, I think), and Safari 5.1.7 do. I take it this is about ordinary HTTP caching behavior, not about, say, "appcache", correct? Also, it seems the issue is that you tell browsers not to cache a resource, and then expect it to be cached anyway. Could you elaborate on that? In any case, a better forum for the problem might be a group specialising in HTTP caching questions, e.g. if you want to know what the HTTP specification has to say on this situation. -- Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de Am Badedeich 7 · Telefon: +49(0)160/4415681 · http://www.bjoernsworld.de 25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/
Received on Tuesday, 21 January 2014 00:56:16 UTC