offline web application doesn't work in firefox - html

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.

Related

Loading pdf file from AWS s3 into iframe does not work in IE 11

I have ASP.NET Core web application. The view is using iframe to load PDF file from amazon s3.
<iframe style="width:100%;height:100vh" src="https://xxxx.s3-us-west-2.amazonaws.com/mybucket/a_01_03_44_35_5745663485955446.pdf"></iframe>
The above code was working fine until recently.
Now iframe does not show any pdf. When i check network using F12 it shows Protocol and Result/Description as Pending
if copy the URL and paste it into IE 11 directly then browser shows the file.
The above behavior is happening in IE 11 and IE Edge, as usual chrome works fine.
I am not sure if recent windows update has got anything to do with this.
Update 1
I take it back, I cannot open S3 url in IE 11 or IE Edge directly either.
This has nothing to do with ASP.NET Core. Why don't you load the PDF with HttpClient and serve it through a controller. Could also have the benefit that you can cache it if this is frequently requested. Or better use the AWS SDK.
I have the same problem since the begining of 2017/08. The difference is I cannot open the url directly on IE11 and Edge eigther. The F12 network tab also shows both Protocal and Result/Description as Pending. No problem on Chrome, firefox and safari.
Several PCs in our company started having this problem from the same time.
Here is a sample url
(please open this by IE11 on Windows10).

HTML5 AppCache - preview in browsers

I'm implementing an appcache in my application and I have a lot of problems with setings it correctly.
For this specific moment I have problems to determine, if files loaded are for sure from the appcache and not from the regular cache?
Can someone provide me with links/tips how can I check that? E.g. in Chrome in the dev tools in Network tab there is placed a (from cache) text for cached resources, but how can I know this is the correct cache?
In Firefox sometimes on files which should be cached in appcache I have nitification in Firebug, that they are loaded from BFCache not AppCache and something like tjat houldn't happen.
So once again, can you provie me with e.g. some plugins for popular browsers (IE, Firefox, Chrome) to check that?
You explicitly declare a page to be cached by the AppCache by referencing a manifest file so you can be sure its using AppCache. A manifest file is
simple text file that lists the resources the browser should cache for
offline access.
and,
The manifest attribute should be included on every page of your web
application that you want cached.
<html manifest="example.appcache">
....
</html>
http://www.html5rocks.com/en/tutorials/appcache/beginner/
BFCache on the other hand is specific to Firefox (other browsers have similar implementation) and serves its purpose differently from AppCache.
AppCache helps your web apps be accessible offline while BFCache speeds up your backward and forward page navigation between visited pages.
You will no longer require any plugins aside from Firebug and the browser's built-in Developer tools if AppCache is implemented correctly

html5 appcahe offline browsing not working fine in chrome?

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.

html5 application cache on ipad not working

I am designing on offline html5 application, which works fine in desktop browser(IE, Chrome, Safari etc) and supports offline capability.
The same application will not work in iPad Safari Browser, but works fine in Chrome browser.
I have set the MIME type to text/cache-manifest and also validated my manifest file online which is fine.
Are there any special settings required for the application to make it work in ipad Safari?
The problem in my cache manifest was
1. I specify the homepage as "/" that need to be cached.
The above works fine on all browsers except on iPad which throws error.
I have removed the "/" that represent home page from the cache section. It works fine now on all the browsers including iPad.
Ensure the cache.manifest file only uses relative URLs not ABSOLUTE.
Ensure the cache.manifest was saved in right charset in your IDE/Text redactor
Don't include page where cache.manifest is inited (page with <html manifest="cache.manifest">)

Offline cache size limit for Firefox Mobile

I am developing a web app that uses an appcache manifest for offline use. One of the files to be cached is relatively large (13.6 MB). The caching works as expected in Firefox desktop, both as a web app and as a normal web page. However, the offline caching of the large file doesn't seem to be working in Firefox mobile, either as a web app or in the regular browser mode. Is there a offline cache size limit in Firefox mobile? I have found this site about limits, but didn't see anything about Firefox mobile. I have also looked extensively at the Mozilla documentation. Thanks for any help.