Closed
Bug 430077
Opened 16 years ago
Closed 16 years ago
pages are cached even when no-cache is set
Categories
(Core :: Networking: Cache, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 202896
People
(Reporter: adam_mcneely, Unassigned)
References
()
Details
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; TRPIT; .NET CLR 1.1.4322; .NET CLR 2.0.50727; InfoPath.1) Build Identifier: 2.0.0.14 If you log into yahoo mail, then click logout, then click back it will display the main yahoo mail page. It should not be caching and should display the login page. It seems that Cache-Control, pragma, or expires are broken in firefox 2.0.0.14. Reproducible: Always Steps to Reproduce: 1. log into yahoo mail (mail.yahoo.com) 2. log out 3. click back button. Actual Results: browser displays the main mail page, not the login screen. Expected Results: In previous versions of firefox and IE it will display the login screen and not cache the non-cacheable content.
Reporter | ||
Comment 1•16 years ago
|
||
You must disable firebug and any other add-ons for this to occur.
Reporter | ||
Updated•16 years ago
|
Version: unspecified → 2.0 Branch
Comment 2•16 years ago
|
||
I think you have to use no-store rather than no-cache to kill the back button. In what version of Firefox did you see it "work"?
Reporter | ||
Comment 3•16 years ago
|
||
I thought I could get this to work in 2.0.0.12 but it turned out I had firebug turned on, which "fixes" the problem.
Component: History → Networking: Cache
Product: Firefox → Core
QA Contact: history → networking.cache
Version: 2.0 Branch → 1.8 Branch
Comment 5•16 years ago
|
||
> I have tried changing the code to use > <meta http-equiv="Pragma" content="no-cache"> > <meta http-equiv="Expires" content="0"> > <meta http-equiv="Cache-Control" content="no-cache"> > <meta http-equiv="Cache-Control" content="no-store"> > <meta http-equiv="Cache-Control" content="post-check=0"> > <meta http-equiv="Cache-Control" content="pre-check=0"> > however the issue persists. no-store doesn't work as a meta tag. It only works as an http header. See bug 202896.
Group: core-security
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•