My appcache is given below and it works perfectly. It works great when i am offline and visit nocache.html page where it shows me offline.html page. Below is the working example -
CACHE MANIFEST
cache.html
NETWORK:
nocache.html
FALLBACK:
/ offline.html
Now i want to ask that when i change the fallback to -
FALLBACK:
nocache.html offline.html
then it does not work. Can somebody tell me what is the problem here?
If you change your network section entry to the more typical *, it works the way you expect.
CACHE MANIFEST
cache.html
NETWORK:
*
FALLBACK:
nocache.html offline.html
It's possible that by explicitly identifying nocache.html in the NETWORK section, the browser will not permit a FALLBACK for it.
I do not know if that is spec-compliant or not and I'm merely guessing, so comments or edits from more knowledgable people are welcome.
Related
Is it possible to tell your HTML5 Webapp to not load the site from the appcache, if the client has network connection?
This isn't exactly what you're asking, but a way to achieve this is to set up a FALLBACK from / to for example /offline/index.html and then check in the offline index.html if you're online and if you are redirect back to /. That way your normal site is loaded over the internet and your offline version is loaded only when offline.
FALLBACK:
/ /offline/index.html
NETWORK:
*
PS. I have never tried this exact setup, and never even used FALLBACK urls, however I worked a lot with appcaches, so I am pretty sure this should work.
I am trying to get the Cache Manifest to fallback to an offline.aspx page when offline.
So when the current page that contains the following cache manifest is loaded online it displays as normal, but when there is no internet connection offline.aspx is shown instead of the current page.
CACHE MANIFEST
# v1.39
NETWORK:
*
FALLBACK:
/ /offline.aspx
Is this possible? Am I understanding that you can replace the current page offline with a fallback page? Is my manifest file correct?
I replaced the /s with /*s and it still didn't work. Chrome Developer Tools shows the offline.aspx as in the cache as type 'Fallback' and the default.aspx as 'Master'. When offline the offline.aspx never gets shown - it still shows default.aspx. I'm going offline by disabling the Local Area Connection in the Network Adapters in Windows 7.
Check these examples:
static.html will be served if main.html is inaccessible
offline.jpg will be served in place of all images in images/large/
offline.html will be served in place of all other .html files (for your case try /* or *)
FALLBACK:
/main.html /static.html
images/large/ images/offline.jpg
*.html /offline.html
p.s.:
Your
NETWORK:
*
should be like:
NETWORK:
/ or /*
these question can help too: HTML5 Cache Manifest: Fallback section & Network *
I'm a asp.net developer and I'm using the HTML5 offline features but the FALLBACK isn't working as I expected: when the server is down, instead the page listed of opening the page in FALLBACK is presented the browser standard page of no connection.
In the manifest file I tried:
FALLBACK:
* /Default.htm
and I tried:
FALLBACK:
/ /Default.htm
and the "default.html" page is never opened when the server is down.
I tried in Google Chrome and in Firefox and result is the same.
What I'm doing wrong? Someone can help me?
Regards,
Carlos Pinheiro
I had a similar issue. Followed every resource online and the only detail that made my manifest work was removing the prefixed '/' before the fallback url.
In your example, change /Default.htm to Default.htm.
FALLBACK:
/ Default.htm
I am playing with HTML5 app cache and right from the beginning I ran into issues:/
I am trying to have simple offline fallback for my page so that there would be nice styled page instead of classic offline error. According to few resources I have red I created this manifest file.
CACHE MANIFEST
# 0.01
CACHE:
NETWORK:
*
FALLBACK:
/ /offline.html
The problem is, that the browser loads into the cache not only the offline.html file, but also the root page, which leads into that page is displayed with lot of errors (no js loaded, no imaged loaded, no CSS, ...) while offline and offline.html is completely bypassed by the browser.
The screenshot below shows logged information about caching progress. You can see there, that the browser downloads both files, instead of only the offline.html as I am trying to do.
All this has been done in latest dev Chrome (23.0.1262.0 dev)
The page which references the manifest file is always included in the offline cache. If you don't want the root page to be cached then you need to create a separate static page to reference the manifest and load it in an iframe.
Hey guys my Manifest is as follows:
CACHE MANIFEST
CACHE:
images/trunk/text/text-images.png
css/site.css
FALLBACK:
/ offline.html
NETWORK:
*
I've since fixed a random random problem whereby safari couldn't load google maps without NETWORK *. What I now want to do is ensure that if someone is offline they only ever hit that offline.html page, I've noticed its possible to sometimes hit a regular page, which looks relaly broken and then you only get transferred to the fallback page after requesting another page. Is tehre anything I need to add here?