Mozilla fails to open cached web page

RESOLVED INCOMPLETE

Status

()

Core
Networking: Cache
RESOLVED INCOMPLETE
11 years ago
4 years ago

People

(Reporter: Bauke Conijn, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(URL)

(Reporter)

Description

11 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9b3) Gecko/2008020514 Firefox/3.0b3
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9b3) Gecko/2008020514 Firefox/3.0b3

When opening this page the server sends a 304-not modified response. But mozilla gives a 'cannot find file' error-page. After a full-refresh of the page, the page loaded again. 


Reproducible: Couldn't Reproduce

Steps to Reproduce:
1. Open the page once (to store it in the cache)
2. Close/Kill Mozilla and Corrupt the cache
4. Start Mozilla
5. Open the page again
Actual Results:  
Mozilla responds with a 'cannot find file' error message.

Expected Results:  
The page should just be opened normally. (Eventually by sending a new page request.)

I suppose there's something wrong in the caching mechanism that causes Mozilla to fail opening the (possibly corrupted) cached page and fail detecting that the cache is corrupted. 

The cache might have been corrupted due to the fact that I had to kill Mozilla, because it didn't stop after closing all windows. This happens when I use the java 1.7 plug in to run applets.
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9b4pre) Gecko/2008021908 Minefield/3.0b4pre

I can't reproduce this, Bauke. Did you also test this with a new profile?
(Reporter)

Comment 2

11 years ago
Have tested this with a new profile. The steps are a bit different though:

Steps to Reproduce:
1. open http://www.win.tue.nl/~hermanh/teaching/2IL15/
2. find the folder where the cache is stored: something like "C:\documents and settings\<username>\local settings\application data\mozilla\firefox\Profiles\<current profile>\Cache\"
3. rename the last accessed file and append an underscore. (maybe deleting also works, but this is what I did.)
4. refresh the page.

This should give the "File not found" error message.

5. restart firefox
6. open the page again.

Mozilla still gives the file not found error message.

I think that mozilla should detect that something went wrong with the cache and try to load the page bypassing the cache.

Note: This problem does not show up with all web pages.

Clearing Private Data including cache while browsing is supported, but after that I see no trouble when I click Reload. I think deleting some entries in the cache is not supported. It's not something that you would expect users to do. A "cure" might be to press Shift while reloading. I suggest to resolve this bug as INVALID (= not a bug in Firefox).
(Reporter)

Comment 4

11 years ago
When Firefox malfunctions, it might do the same to the cache. The resulting error message is not clear for the user. The requested file seems to be unavailable *at the server*. This means the error message is incorrect. 

So in my opinion Firefox should either:
- Show an appropriate error message telling the page could not be loaded from cache and the user could try to press shift while reloading.
- Or get the page from the server and restore the cache automatically.

Because the problem seems to reside at the server. It would take several days to detect that it actually is a problem with the cache. Those days are not always available.

Indeed, you should not expect a user to mess with the cache. But then, Firefox is not fool-proof.

Handling this error might also reduce the impact of other cache related bugs.



Component: General → Networking: Cache
Product: Firefox → Core
QA Contact: general → networking.cache

Comment 5

4 years ago
Does this fail for you in a current version of firefox, which has a newer cache implimentation?
Flags: needinfo?(bcmpinc)
Whiteboard: [closeme 2014-10-10]

Comment 6

4 years ago
Resolved per whiteboard
Status: UNCONFIRMED → RESOLVED
Last Resolved: 4 years ago
Flags: needinfo?(bcmpinc)
Resolution: --- → INCOMPLETE
Whiteboard: [closeme 2014-10-10]
You need to log in before you can comment on or make changes to this bug.