: What does the Chrome error code (6) in "appcache fetch failed" indicate? I am developing a website that uses the html cache manifest (AppCache). I often see the following line in Chrome's console:
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) 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
More posts by @Rambettina238
3 Comments
Sorted by latest first Latest Oldest Best
Looking into Chrome source code, those numbers 6, 9 or similar are order numbers of enum. In case of 6, this is NETWORK_ERROR, in case of 9 it is SECURITY_ERROR.
Here is source showing that if given error is SERVER_ERROR it will put response code, but if it isn't SERVER_ERROR it will map its error to enum value, and this enum is defined here and the codes are:
UPDATE_OK (0)
DB_ERROR (1)
DISKCACHE_ERROR (2)
QUOTA_ERROR (3)
REDIRECT_ERROR (4)
MANIFEST_ERROR (5)
NETWORK_ERROR (6)
SERVER_ERROR (7)
CANCELLED_ERROR (8)
SECURITY_ERROR (9)
NUM_UPDATE_JOB_RESULT_TYPES (10)
To be honest I saw only 4 when server was sending 302, 9 when certificate is wrong, and 6 but here I still don't understand whole problem.
If you still get this problem, make sure...
You don't have switched on "Google Chrome can run in background" option
Go to $sysdrive$Users$youraccount$AppDataLocalGoogleChromeUser DataDefaultApplication Cache -> delete files and folders
I had exactly the same issue when using Application Cache on Chrome v38.0.2125.111 m.
Tried several different manifest configs but in the end I simply closed Chrome and reopened it again. Hey presto, issue was gone and cache was working fine!
Hope this helps someone!
Terms of Use Create Support ticket Your support tickets Stock Market News! © vmapp.org2025 All Rights reserved.