AppCache NETWORK: tests

  • Supported in Firefox
  • Supported in Chrome
  • Supported in Safari
  • Supported in IE
  • Supported in Opera

Yesterday I blogged about a number of issues I was having with AppCache NETWORK: section and SSL. After a couple of tweet exchanges with Jake Archibald it would appear that I did not understand the way the NETWORK: part of the specification worked. There also seemed to be a few implementation differences with the browsers. So I built 7 small sub sites all of which used AppCache NETWORK: section in a different way to test the current implementations.

AppCache NETWORK: tests - xhr calls to same domain as manifest

  1. Uses * wildcard
  2. Uses relative URLs
  3. Uses absolute URLs
  4. Uses relative "Prefix match"

AppCache NETWORK: tests - cross domain xhr calls by URL

  1. Uses absolute cross domain URLs
  2. Uses cross domain "Prefix match"

None specification? (see notes)

  1. Uses http://* wildcard (mentioned on appcachefacts.info)

Compatibility

  Firefox 19.0.2 Chrome 25.0 Safari 6.0.2 IE 10.0 Opera 12.14
* wildcard No Yes Yes Yes Yes
Same domain relative URLs Yes Yes Yes Yes Yes
Same domain absolute URLs Yes Yes Yes Yes Yes
Same domain "Prefix match" Yes Yes Yes Yes Yes
  Firefox 19.0.2 Chrome 25.0 Safari 6.0.2 IE 10.0 Opera 12.14
Cross domain absolute URLs No Yes Yes Yes Yes
Cross domain "Prefix match" No Yes Yes Yes Yes
  Firefox 19.0.2 Chrome 25.0 Safari 6.0.2 IE 10.0 Opera 12.14
http://* wildcard No Yes No No Yes

Notes

Although appcachefacts.info site says there is support for http://* and https://* wildcard patterns, I could not find these mentioned in the current specification documents. Only tested IE10, I am unsure of AppCache support in earlier versions of IE.

I believe that making cross-domain URLs entries in the NETWORK: section of AppCache is outside the current specification. If this is the case Firefox is following the specification strictly and the other browsers have ignored this element of the specification.

Useful Links