HTML5 offline cache is deployed under tomcat to enable offline browsing of pictures, flash, etc._html5 tutorial skills

Open a web page, and after loading, if the Internet is suddenly disconnected, the page will be gone after you refresh it.
Have you ever thought that after refreshing, the page is still the same as before? If you open another page in a new window and enter the same URL, it will still be the same page when you are disconnected from the Internet. . HTML5 offline applications provide such a function.
When the data in the page is loaded, you can set some images, flash, css, js, html and other files to be cached. You can use those cached files next time when the Internet is not available. This is the offline application of HTML5.
In fact, it is very simple to implement.

Requires server. Here we use tomcat server to explain.
First, configure the mine type of the file with the .manifest suffix to text/cache-manifest.
When it comes to tomcat configuration, familiar friends will naturally think of the web.xml file. Yes, just add the following configuration to the file:

Copy the code

The code is as follows:

manifest

Then write a xxx.manifest file, xxx is a name you choose yourself. The format of this file is like this:

Copy the code

The code is as follows:

CACHE MANIFEST
#version 1.5
CACHE:
MyTest.html
CSS/main.css
Javascript/bwH5LS.js
exp-calif-logo.gif

The first line is required, it identifies that this is the manifest configuration file.
#version 1.5
This sentence is a comment and has no actual effect. I just want the browser to update the cache file. Because when the manifest file is the same as the original, the browser will not reload the cache file, so we can use this comment to modify the version number on the one hand and let the browser update the cache on the other.
CACHE:
This line indicates that the following file is to be cached. In the example, the current page: MyTest.html, as well as some css and js files and images are cached.
There are a few keyword examples not mentioned, namely
NETWORK:
FALLBACK:
NETWORK refers to pages that do not want to be cached; FALLBACK refers to the requested file not being found or the server for the file not being available. Alternatives in response, for example, if we want to request a nested page, but the server of this page cannot be connected, then I can move to another specified page.
This is the second and third step. Just add the location of the manifest in the tag:

Here you go. You can implement simple offline applications.

Where are those cached files?
Tested it on chrome and found that it saves these files in chunks according to its own mechanism, so I couldn't find the complete file. The saved data is in:
C:UsersjasonlingAppDataLocalGoogleChromeUser DataDefault. I don’t know how to save it specifically.
Files on Firefox are also stored according to its own mechanism. However, after opening it with SQLite, the author found the specific information of the cached file:
Readers who are interested can try it themselves and see if it works. New discoveries.