HTML5 appcache is not working in chrome as expected?
For example
http://html5demos.com/offlineapp
when you load the above URL is will save locally,but when you refresh the page again it will not render properly.
MANIFEST file:
http://html5demos.com/html5demo.appcache
will cache the following files :-
images/shade.jpg
images/bin.jpg
/js/h5utils-offline.js
/css/html5demos.css
expect these files every other resources are not rendering when we refresh the page.
expected behavior:
All other resources(which are not in MANIFEST file) should load properly when user comes online.
but in Firefox this is working almost fine.
Why chrome is not working as expected ?
It will be great if there is some perfectly working demo.
html5 appcache is at risk and may be removed:
http://www.w3.org/TR/html5/
http://w3-video.com/Web_Technologies/HTML5/html5_attributes/html/html5_html_manifest_attribute.php
Non-cached resources will not load on a cached page. See Gotcha #5 from this article:
http://alistapart.com/article/application-cache-is-a-douchebag
Using the network wildcard:
NETWORK:
*
...would fix this.
Related
I use cache.manifest (with correct content-type and expire=-1 http-header) to cache a very very simple page for offline use. (this page)
The page works correctly with chrome browser, but FF 29 doesn't display it when I am offline.
I also use this code but I couldn't find the problem.
I have a problem with HTML5 appCache on Firefox and IE10.
I have build a minimal test case available on: https://docs.google.com/file/d/0B7CVmRJOMgTNZUxkLWRDNmhtVU0/edit?usp=sharing
Accessing the page at "applicationCache/test.html" the browser will look for the correct manifest and will start to download all the content from the files in its list.
The problem occurs when I put in the list a .php file handling COOKIES; for example I have added a .php file which will call the php function "session_start()".
Chrome and Safari can handle correctly such file during the application cache download.
Firefox and IE10 share the behaviour: they halt and signal a generic error.
During a long search I found out this ticket on bugzilla: https://bugzilla.mozilla.org/show_bug.cgi?id=722683
Is there anyone who can give me a hint to handle correctly the COOKIES during applicationCache download event, without getting an error ?
Am I doing something wrong or against the standard ?
Thank you for your assistance!
I am not sure but can you make use of the localStorage instead of cookies?
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 have run into an issue with one of my webpages that was changed to use the HTML5 appcache feature. Chrome 19 (ad I assume earlier versions) is blocking my cross site css files when the appcache is enabled on a page. The page, http://www.ericperrets.info/index.html, loads a number of image/css files from my server and a number of css files from a google url/servers. Below is the epi.appcache file content
CACHE MANIFEST
#
CACHE:
/default.css
/800px.css
/images/bg.jpg
/images/spwright.png
/images/spwright2.png
/images/meme.jpg
/favicon.ico
/Resume%20-%20Eric%20Perret.pdf
NETWORK:
/index.html
*
http://*
https://*
This works find when the page is loaded in the latest safari or firefox, but when I try to load it in Chrome, it blocks the calls to http://fonts.googleapis.com/css?family=Reenie+Beanie|Candal&v1&text=ERIC%20PT%E2%80%99SINFOAesumWorkaplntcfLidh%2C
Update: I fixed the issue by disabling one of my plug-ins that I had for Chrome: HTTPS Everywhere. This is a really useful plugin. Is there a way around this issue other than changing the URL to https?
For an html5 game I'm making at a company we've hit a snag. In safari it doesn't even seem to be trying to load our manifest file while in chrome it is. And it runs offline too. Is there any huge differences between how the two handle it that trip it up?
I'll check how firefox handles it and update in a bit. This is literally how the cache looks. Already had it validated and everything.
CACHE MANIFEST
#v 1.01
CACHE:
/graphics/Apalia_Map 02.jpg
/graphics/comic/PAGE4.jpg
/graphics/comic/PAGE2.jpg
/graphics/comic/PAGE8.jpg
/graphics/comic/PAGE7.jpg
/graphics/comic/PAGE3.jpg
/graphics/comic/PAGE6.jpg
/graphics/comic/PAGE5.jpg
/graphics/comic/PAGE1.jpg
/graphics/gameComplete.jpg
/graphics/ui/main_menu_bg.jpg
/graphics/ui/apaliaCredits.jpg
/graphics/levels/elpala3-lvl1.jpg
/graphics/levels/elpala1-lvl1.jpg
/graphics/levels/elpala2-lvl1.jpg
/graphics/effects/fswipe_northwest_1_4.png
/graphics/effects/spinfx08.png
/graphics/effects/shieldfx_7.png
/graphics/effects/spinfx01.png
etc...
I have found the answer about this question.....
Safari is more funny than chrome, I can easily make chrome cache my page, but safari does not.
I list these key to make the instruction clearly for the dump like me:
The HTML tag contain Manifest file name like this:
< !DOCTYPE html>
< html manifest="safari.manifest" >
addType, I use apache server, my http.conf contain this in IfModule which contain those addtype:
< IfModule >
....(other content...)
AddType text/cache-manifest .manifest
< /IfModule >
The manifest file name is "safari.manifest". Its content is the most funny part, I have a html that only contain the javascript. I have no image so I don't have anything in NETWORK and FALLBACK. So I don't even fill them in the safari.manifest.
My failed safari.manifest content is:
CACHE MANIFEST
So it does not work.
My success safari.manifest content is:
CACHE MANIFEST
NETWORK:
FALLBACK:
SO FUNNY that I STILL need that "NETWORK FALLBACK" empty blocks in the file to make safari cache the page. If I don't add that two words, Safari will not cache anything.
That's all I found.
not sure as I can't see what is happening, but the problem could be related either to the way you link to the manifest file or (and I'll place my bets now) to the mime-type the file gets sent with (has to be "text/cache-manifest").