Take the 2-minute tour ×
Webmasters Stack Exchange is a question and answer site for pro webmasters. It's 100% free, no registration required.

I am developing a website that uses the html cache manifest (AppCache). I often see the following line in Chrome's console:

Application Cache Error event: Manifest fetch failed (6) https://192.168.0.102/static/index.appcache

Apparently the error code in parentheses is meant to be the HTTP status code, or -1 if the browser is offline. But my server is not returning 6 as status code. So what does this code indicate?

Chrome's behavior regarding this error is very odd. If I force it to re-download the website by removing the appcache client-side (via chrome://appcache-internals), this error often still occurs, but this time not preventing but interrupting an already running download; the second refresh then works fine.

The problem occurs regardless of whether there is a new version of the cache manifest or not, and this makes it hard to update Chrome's appcache. The problem does not occur in IE 11.

I'm using TLS with a self-signed certificate for this development stage. The HTTP response headers for the appcache manifest are HTTP/1.1 200 OK Accept-Ranges: bytes Cache-Control: no-cache, must-revalidate Content-Encoding: gzip Content-Type: text/cache-manifest; charset=utf-8 Expires: -1 Last-Modified: Fri, 11 Apr 2014 07:49:30 GMT Pragma: no-cache Vary: Accept-Encoding Date: Fri, 11 Apr 2014 07:51:38 GMT Content-Length: 480

share|improve this question
    
Tag wishlist: "appcache" "error-code" –  pyramids Apr 11 at 8:08
    
I have exactly the same issue but nowhere can explain the (6) bit. I don't know if it helps, but I get this from a browser running in a terminal server session and it's trying to access the site on the same network; an intranet basically. Accessing the same site externally works fine. Exactly the same code. Both IIS setups are exactly the same too. So frustrating as FF and IE work fine. Somebody out there must have had this and managed to fix it? –  Michael Wilkinson May 19 at 16:11
    
From the looks of code.google.com/p/chromium/issues/detail?id=315167 and the less-relevant readynas.com/forum/viewtopic.php?t=75968&p=423394 , it appears that this is a Chrome issue which is not fully resolved. –  Jeremy Miller May 20 at 5:38
    
I am currently seeing this error when the browser is not offline but my development server is. I doubt that was the case when I originally ran into this issue, but I've changed my setup so much, I can't exactly verify that there wasn't some unrecognized problem preventing the browser from actually getting server responses for the manifest. –  pyramids May 20 at 19:37

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.