Bug 23476 – HTTP redirect should make application cache updating fail

• Status: RESOLVED
• Resolution: FIXED
• Component: WebCore Misc.

[Alexey Proskuryakov]

4. <404/410 handing for manifests>
5. Otherwise, if fetching the manifest fails in some other way (e.g. the server returns another 4xx or 5xx response or equivalent, or there is a DNS error, or the connection times out, or the user cancels the download, or the parser for manifests fails when checking the magic signature), or if the server returned a redirect, or if the resource is labeled with a MIME type other than text/cache-manifest, then run the cache failure steps.
...
16.4 If the previous step fails (e.g. the server returns a 4xx or 5xx response or equivalent, or there is a DNS error, or the connection times out, or the user cancels the download), or if the server returned a redirect, then run the first appropriate step from the following list:

  * If the URL being processed was flagged as an "explicit entry" or a "fallback entry"
       Run the cache failure steps.

[Alexey Proskuryakov]

I have a patch ready, but cannot upload it due to a Bugzilla internal error yet.

[Alexey Proskuryakov]

Created attachment 26934 [details]
proposed patch

[Anders Carlsson]

Comment on attachment 26934 [details]
proposed patch

r=me

[Alexey Proskuryakov]

Committed revision 40356.