HTML5 应用程序缓存清单文件在硬盘上的位置
我有一个使用 HTML5 应用程序缓存的网站,但我无法确定缓存更新开始的原因。我没有进行更改或添加/删除文件。
清单文件是动态生成的,包含应用程序文件夹中的所有文件(少数不应缓存的文件除外)。我想检查缓存的清单文件,看看它与当前版本有什么区别。
浏览器如何存储清单文件,以便能够确定它何时发生更改以及何时应启动缓存更新?
可以在浏览器缓存文件夹中的硬盘驱动器上的某个位置找到此文件吗?
I have a site which uses HTML5 App Cache and I'm having trouble determining why the cache update started. I haven't made changes or added/removed files.
The manifest file is generated dynamically and includes all files from the app's folder, except a few which should not be cached. I would like to check the cached manifest file to see what is the difference between it and the current version.
How do the browsers store the manifest file so they are able determine when it has changed and when should the cache update kick in ?
Can this file be found somewhere on the hard drive in the browser's cache folder ?
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(1)
是的,他们必须这样做。否则它应该如何工作?存储在 RAM 中,重启后会丢失,并且仅存储在 Web 中,无法导致离线应用程序。
但它们存储在哪里以及是否加密是另一个问题。在 Firefox 中:
C:\Users\brach\AppData\Local\Mozilla\Firefox\Profiles\xxxxx.default\OfflineCache\0\9\77546B5B27E111-0
该文件的内容是
所以这是一个清单我们是如何知道的。但对于其他浏览器,您必须自己探索...;)
about:cache
作为 URL,然后在离线缓存设备
中查找部分。chrome://appcache-internals
作为 URL,让您直接在浏览器中显示任何缓存文件的内容,包括清单。Yes they have to. How it should work otherwise? Stored in RAM it would be lost after reboot and stored only in web could not lead to an offline app.
But where they store them and if they are encrypted is another question. In Firefox:
C:\Users\brach\AppData\Local\Mozilla\Firefox\Profiles\xxxxx.default\OfflineCache\0\9\77546B5B27E111-0
The content of that file is
So that's a manifest how we know it. But for other browsers you have to explore it by yourself... ;)
about:cache
as URL and look inOffline cache device
section.chrome://appcache-internals
as URL and let you show the content of any cached file including the manifest directly in the browser.