Closed Bug 236682 Opened 20 years ago Closed 19 years ago

Site does not load if browser.cache.memory.enable=false and site returns Cache-control: no-store

Categories

(Firefox :: General, defect)

x86
Windows XP
defect
Not set
minor

Tracking

()

RESOLVED DUPLICATE of bug 184304

People

(Reporter: richardtallent, Assigned: bugzilla)

References

()

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040206 Firefox/0.6
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040206 Firefox/0.6

If the user configures Firefox with "browser.cache.memory.enable=false" and then
visits a site that returns the "Cache-control: no-store" directive, the site
does not load.

Reproducible: Always
Steps to Reproduce:
1. Use the about:config page to set browser.cache.memory.enable equal to false.
2. Visit any site that returns "Cache-control: no-store" in the response header.

Actual Results:  
The page does not load.

Expected Results:  
Either the browser should ignore the directive and load the page, or it should
at least give the user an error dialog explaining the situation and potentially
allowing the user to change the memory cache setting and continue loading the page.
Confirmed

Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7b) Gecko/20040305 Firefox/0.8.0+
Status: UNCONFIRMED → NEW
Ever confirmed: true
Please use descriptive summaries!

Furthermore, is this even a Firefox bug (always check this before confirming,
especially for backend bugs like this)? Please test it in Mozilla and see if it
works there. If it doesn't, then please move this over to Browser. Also, check
if there is a bug on this already open. If so, please dupe it.
Summary: site does not load → Site does not load if browser.cache.memory.enable=false and site returns Cache-control: no-store
(In reply to comment #2)

I'll try to be more descriptive in the future...

> Please test it in Mozilla and see if it works there. If it
> doesn't, then please move this over to Browser. Also, check
> if there is a bug on this already open. If so, please dupe it.

There is serious confusion about what should be in "Browser" and what shouldn't.
If it is thrown to the "Browser" team, will it *also* automatically be addressed
by the alternative browser Firefox? Sorry, I'm a Firefox fan, but only a very
ocassional Bugzilla user, and I find the entire Bugzilla UI to be disorienting.

Also, I checked for dupes and found none.

On a more constructive note, there is a potential security risk if the browser
ignores the HTTP response directive and saves it to disk anyway. The correct
response, IMHO should be that it should (a) display a message explaining the
conundrum and (b) offer to enable on memory caching and continue loading (this
setting does not require a browser restart to take effect).
(In reply to comment #3)

> There is serious confusion about what should be in "Browser" and what shouldn't.
> If it is thrown to the "Browser" team, will it *also* automatically be addressed
> by the alternative browser Firefox? Sorry, I'm a Firefox fan, but only a very
> ocassional Bugzilla user, and I find the entire Bugzilla UI to be disorienting.

Firefox gets almost all of its backend code (page layout, rendering, networking,
printing, caching, etc) from Mozilla (Browser). For the most part, only the
frontend UI code is different.
*** Bug 269121 has been marked as a duplicate of this bug. ***
Does bug #247555 relate to this bug?
Looks similar to Bug 184304
*** Bug 275003 has been marked as a duplicate of this bug. ***
I agree with comment 7, this is most likely a dupe of that bug in the backend.
(Sorry, should have dupes bug 275003 there as well.)

*** This bug has been marked as a duplicate of 184304 ***
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.