...">

Html5 cache & # 8594; "network: *" does not work

I am trying to do a simple test with html 5 cache.

Here is a simple web page:

<!DOCTYPE html> <html manifest="test.manifest"> <head> </head> <body> <img src="http://www.somewebsite.com/picture.jpg"/> </body> </html> 

With the following manifest:

 CACHE MANIFEST #v0.1 NETWORK: http://www.somewebsite.com/ 

This work is beautiful, the image is displayed.

My problem is that I can’t find out where the picture comes from. Here's an online whitelist lookup flag that should solve my problem.

But with the manifest:

 CACHE MANIFEST #v0.1 NETWORK: * 

The image does not appear (checked on safari / safari mobile / firefox).

What does not work?

Is there any other way to enable the whitelist wildcard flag?

+4
source share
3 answers

Tested in Firefox 3.6.4:

 NETWORK: http://* 
+4
source

Per docs when the “open whitelist wildcard flag is open” (i.e. NETWORK: format NETWORK: * )

Subresources, such as style sheets, images, etc., will be cached using normal HTTP semantics caching, however.

which seems to be "something that doesn't work." In order to cache subresources in the HTML5 method, the manifest must either list them in the CACHE: section, or use specific "whitelist namespaces", as it was in your first version.

+1
source

I want to use the svg font in webapp intended for mobile safari (mobile safari only reads the svg font format for @ font-face). Mobile Safari also requires a font identifier that is included at the end of the file name but included after the number sign (#):

font-name.svg # 123456789

This does not work in the manifest cache for the site, and with the limited feedback received from the mobile safari, I only assume that # causes the font to be identified as a comment, and not part of the actual file name.

Is there a way to “trick” the cache manifest when reading this differently? Perhaps with a pattern after SVG? Or ICQ-trick?

-1
source

Source: https://habr.com/ru/post/1307874/


All Articles