tag:blogger.com,1999:blog-7865803374326096685.post146780915752137026..comments2023-12-14T04:12:12.533-08:00Comments on SaikoTroid: Application Cache whitelisting the master entryBody Hammerhttp://www.blogger.com/profile/11503666927809156483noreply@blogger.comBlogger7125tag:blogger.com,1999:blog-7865803374326096685.post-22373829159093455742022-09-02T01:36:48.008-07:002022-09-02T01:36:48.008-07:00The high speed laser trimming supplier can be used...The <a href="https://www.laserchina.com/resistor-trimmer/" rel="nofollow">high speed laser trimming supplier</a> can be used for precise manufacturing.Laserchinahttps://www.blogger.com/profile/12838728723410936790noreply@blogger.comtag:blogger.com,1999:blog-7865803374326096685.post-87572481912709527032013-08-16T05:50:17.708-07:002013-08-16T05:50:17.708-07:00I guess the Iframe-workaround doesn't work. If...I guess the Iframe-workaround doesn't work. If you think the files are loaeded from appcache: no. they're coming from browser cache.<br /><br />disable browsercache in devtools-settings und look at "network". you can see, that all elements will be loaded via network and don't come frome (app)cache.Murksfurtzhttps://www.blogger.com/profile/16818799156031430048noreply@blogger.comtag:blogger.com,1999:blog-7865803374326096685.post-76513700266883975722012-03-29T02:21:57.496-07:002012-03-29T02:21:57.496-07:00Hi,
I have been experiencing exactly this same pro...Hi,<br />I have been experiencing exactly this same problem with iOS. I found that adding "Cache-control: no-store" to the page that declares the manifest stops the entire manifest from working!; so nothing gets cached. I am loathe to use the iframe workaround because it really seems like a bodge-fix.Richardhttps://www.blogger.com/profile/01577850772736868028noreply@blogger.comtag:blogger.com,1999:blog-7865803374326096685.post-37627006215572320042011-11-19T16:34:44.104-08:002011-11-19T16:34:44.104-08:00Hi.
Im working with appcache, and this issue is re...Hi.<br />Im working with appcache, and this issue is really annoying.<br />I posted in my blog the researches about this.<br />Actually, Google Chrome seems to be ignoring Cache-Control:no-store.<br />http://jaydson.org/en/html5-appcache-cache-control-no-store<br />Well, this workaround using Iframes seems to be a simple solution, but sure, the spec needs to be upgraded to fix that.<br />Tks.Jaydson Gomeshttps://www.blogger.com/profile/17250666057227395514noreply@blogger.comtag:blogger.com,1999:blog-7865803374326096685.post-73938513629534895012011-09-21T13:45:03.857-07:002011-09-21T13:45:03.857-07:00This does not seem to work (tested in Chrome). The...This does not seem to work (tested in Chrome). The files used in ORIGINAL HTML that are listed in the manifest file are not loaded from the cache. Instead they are downloaded like usual.<br /><br />Does anything else need to be in the OTHER HTML besides the html tag referencing the manifest file?<br /><br />Does it matter where the iframe is added to the ORIGINAL HTML? I tried the begging and the end of the body.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-7865803374326096685.post-72156339887421494572011-07-17T22:37:47.061-07:002011-07-17T22:37:47.061-07:00thx Zaki! unfortunately HTTPS is not an option for...thx Zaki! unfortunately HTTPS is not an option for us.grasshopper rtultatjhttps://www.blogger.com/profile/03473958194082705731noreply@blogger.comtag:blogger.com,1999:blog-7865803374326096685.post-70321482167272501222011-07-14T23:35:20.573-07:002011-07-14T23:35:20.573-07:00Hey, it was nice catching up with you yesterday. H...Hey, it was nice catching up with you yesterday. Here's the note from the reference [1] related to offline manifests:<br /><br />> Authors are encouraged to include the main page in the manifest also, but in practice the page that referenced the manifest is automatically cached even if it isn't explicitly mentioned.<br /><br />> With the exception of "no-store" directive, HTTP cache headers and restrictions on caching pages served over TLS (encrypted, using https:) are overridden by manifests. Thus, pages will not expire from an application cache before the user agent has updated it, and even applications served over TLS can be made to work offline.<br /><br />Not sure if Cache-Control: no-store solves your particular problem and if UA's really honor it IRL, but might be worth a shot. :)<br /><br />Zaki<br /><br />[1] http://www.whatwg.org/specs/web-apps/current-work/#offline section 6.6.1Zakihttps://www.blogger.com/profile/05990193322217506451noreply@blogger.com