It’s not clear to me from the description of the cache manifest that I read (for example, http://www.w3.org/TR/offline-webapps/#offline and elsewhere) that this is a file. I will explain what I find obscure.
The title of the heading (“Offline Web Applications”) assumes that the cache manifest is relevant only for offline scripts; cache manifest is defined as
"The mechanism for ensuring Web applications are available
even when the user is not connected to their network"
But does the cache manifest have any implications for use on the Internet? It seems so. The file contains the NETWORK section, and the files listed there (sometimes I saw that it is described as the last file specified there) are not included in the cache; they are
"...should never be cached, so that any attempt to access that file will bypass the cache."
What would bypass cache mean in an autonomous context? But if the user is connected to the network, are the files listed in the NETWORK section always received from the server, even if they were previously cached?
Files added to the NETWORK section are called white. Typically, for a whitelist, something means allowing this. In fact, these files are blacklisted - that is, they are not allowed in the cache.
This page is copied verbatim or paraphrased as a lemming in many other documents, so the original imperfect clarity remains.
, : -, , , , -, , , 31 , 2010. - , , HTML5?