Serious problems with html5 application cache

Comments: Html5 application cache is used in our 3G website project to put most of the image resources, js, css and other static Resources in the manifest file, for details, refer to the html5 application cache used in the project of our 3G website and put most of the static resources such as image resources, js resources, and css in the manifest file.

I did not expect a serious problem on the first day of the launch: application cache caches the current page by default !!! Even if we have the following settings:

The Code is as follows:
NETWORK :*

That is to say, for all dynamic pages, the application cache will be cached, and how users refresh is old!

Moreover, mobile browsers are hard to be cleared, and js cleanup is not supported!

It took me one morning to try a lot of methods, check a lot of information, and fail to clear the client cache. One morning, the user complained badly.

Finally, the omnipotent stackoverflow saved me:

Do not use appcache unless it is REALLY 100% EXACTLY WHAT YOU WANT TO DO
Even if it IS 100% exactly what you want to do, * do not ** use appcache until you are 100% CERTAIN that you are not going to make a single change to that page (or any file that it links to) for a LONG time.
Delete the manifest file from the server -- if the browser can't find the manifest file, then it will clear its cache ...... this will also turn caching off for everyone.
Don't turn it on again until it's 100% CORRECT
Dealing with appcache is miserable, often.
The solution is simple. Delete the manifest file on the server and use application cache with caution.

Of course, there are also ways to use application cache while bypassing the automatic cache of the current page. That is, iframe