Steps to reproduce: 1. Set a header for the manifest file: "Cache-Control: no-store, no-cache, must-revalidate" 2. Go to a page using that manifest, listening to the appcache events Actual results: * The 'error' event handler is run * The page isn't cached Expected results: * Either the 'cached', 'noupdate' or 'updateready' event handler should run * The page should be cached There might be other headers causing the same errors. The manifest file should only be discarded upon user request, and when it becomes obsolete or replaced by a newer version.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.