Broken url in application cache manifest is not triggering error in IE10 / IE11

Vote count:

0

I am developing an app using application cache and I seem to have come across an issue with IE10 / IE11 whereby it does not seem to trigger an error when the url for an item is broken in the cache manifest. In all other browsers this will trigger an error and the cache will fail to create, but in IE 10 / 11 it simply proceeds to create the cache.

Here is a sample page which contains 3 images and a JS file with some code to log status messages to the console, it references a manifest file with a deliberately incorrect img url in order to make the cache creation fail:

If you look at the console output you should see that IE happily reports the download process and ultimately claims that "This Cache is now stored on the device", but in all other browsers you'll see an error.

I have tested the manifest file (http://ift.tt/QgmoF0) using http://ift.tt/KGdcWK and it definitely contains a broken url.

The strange thing is that I've tried Googling regarding issues with IE and appcache and can't seem to find this being an issue for people, seems unlikely that I'm the first to notice this issue but I can't see what I might be doing wrong. Has anyone encountered this issue before and do you also see it with these test files?

asked 55 secs ago

Rick Curran

121