Closed Bug 649803 Opened 14 years ago Closed 14 years ago

Cannot clear appcache

Categories

(Firefox :: General, defect)

4.0 Branch
x86_64
Windows 7
defect
Not set
normal

Tracking

()

RESOLVED INVALID

People

(Reporter: ilkkah, Unassigned)

Details

User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0) Gecko/20100101 Firefox/4.0 Build Identifier: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0) Gecko/20100101 Firefox/4.0 I played with the application cache (appcache, cache manifets) and I managed to put my Firefox 4 in a state, where it always loads the site from the cache. Nothing I have tried has remedies this: - I removed the manifest="" from the html file, but Firebug shows it being there - I put the manifest back, it didn't affect anything - I have cleared my cache (Clear Recent History/Cookies+cache+active logins/time range:everything) many times during this, it hasn't affected anything. - I have refreshed the page a lot, restarted the browser a lot, no help. I think I may have to do uninstall/install until the situation is fixed. The site that I did this is on my local computer. Reproducible: Always Steps to Reproduce: 1. Define cache manifest 2. Play with it until it breaks :)
Version: unspecified → 4.0 Branch
I believe this is working as designed. The html page is implicitly in the appcache IIUC, so changes will not be reflected in the client, at least not without an update (that's where it gets a little more vague) Changes to the manifest file *should* trigger an update, apparently subject to normal caching heuristics and HTTP rules. There's a separate way to clear the offline cache. Clearing the regular cache doesn't clear the appcache.
It may be that I just didn't find the way to empty the offline cache. I ended up deleting the folder for that in the filesystem, which helped. Probably works as intended then.
Considering comment2, setting resolution to Resolved Invalid.
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.