Home/ Questions/Q 6723037
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-26T09:31:14+00:00

I am a little slow to the HTML5 caching, I have just some simple

  • 0

I am a little slow to the HTML5 caching, I have just some simple questions though.

1) How long is data in a caching manifest cached?

2) If I update the data, how can I make sure the client checks for a newer version when it is available, or is this already done?

3) Also, is this completely useless for a non-0mobile environment or can it speed up load times on a desktop?

<html lang="en" manifest="offline.manifest">

offline.manifest

CACHE MANIFEST
index.html
style.css
image.jpg
image-med.jpg
image-small.jpg
notre-dame.jpg
Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    1) As long as the user cares to cache it. The only way to completely get rid of the cache is to go into the browser settings and explicitly remove it.

    2) If you update the manifest file, the client will download new versions of all the files. This download is still governed by ‘old’ HTTP caching rules, so set headers appropriately, also make sure you send a ‘no-cache’ header on the manifest file itself. The rules from HTML5 Boilerplate are probably a good place to start.

    3) Remember desktops can lose connectivity too. Also, having files in application cache means they are always served locally so, providing you’re sensible about what you put in it, the application cache can reduce bandwidth and latency. What I mean by sensible is: if most visitors only see a couple of pages of your site and you update the manifest of your entire site every week, then they could end up using more bandwidth if you’re forcing them to cache a load of static files for pages they never look at.

    To really cut down on bandwidth and latency in your HTML5 website of the future: use the application cache for all your assets and a static framework; use something like mustache to render all your content from JSON; send that JSON over Web Sockets instead of HTTP, saving you ~800 bytes and a two way network handshake per request; cache data with Local Storage to save you fetching it again, and manage navigation with the History API.

    • 0