Closed
Bug 136380
Opened 23 years ago
Closed 23 years ago
My mozilla won't load any page under SSL
Categories
(Core Graveyard :: Security: UI, defect, P3)
Tracking
(Not tracked)
VERIFIED
DUPLICATE
of bug 136210
People
(Reporter: david.peterson, Assigned: ssaux)
References
()
Details
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.9) Gecko/20020311
BuildID: 2002031115
Reproducible: Always
Steps to Reproduce:
1. Visit any http (port 80) site
2. Type in the URL of a https (port 443) site
3. The status bar indicates connects, transferring data, and the padlock changes
colour to yellow (secure) but the site never renders on the browser screen.
Actual Results: The brower page remains unchanged, ie the original site remains
displayed. Interestingly, when the padlock is clicked and the security dialog is
browsed, you can view the certificate for the SSL site that you are attempting
to access (eg https://my.rackspace.com/)
Expected Results: Loaded and displayed the SSL page
I have only started experiencing this problem today, after months of running
0.9.7 without issue. Thinking it could be a 0.9.7 issue, I just upgraded to
0.9.9 (using the redhat 7.x rpms) and am experiencing the same problem.
Does this suggest to you that it might not be a moz problem at all, rather a
problem with another library or component in my system? Is this a known problem
at all - I tried searching bugzilla and groups.google.com without success.
Thanks.
Comment 1•23 years ago
|
||
WFM with my Mozilla (2002040803/Win2K)
| Reporter | ||
Comment 2•23 years ago
|
||
I know my bug report sounds absolutely crazy, but if I wasn't seeing it happen
with my own eyes I wouldn't believe it :)
A bit more info: when I click the padlock icon, all the information I see
displayed is for the *earlier* page, except for the SSL cert info, which is for
the *new* (requested) page.
But, as outlined, the page never appears.
Comment 3•23 years ago
|
||
Reporter, are you behind a proxy?
If yes, could it be a dupe of bug #127671 ?
| Reporter | ||
Comment 5•23 years ago
|
||
I have encountered the same problem from both behind a proxy and via direct
connection.
Comment 6•23 years ago
|
||
Reporter, can you try again with a new profile? ./mozilla -ProfileManager
Component: XP Apps → Client Library
Product: Browser → PSM
Version: other → 2.3
Comment 8•23 years ago
|
||
Reporter, I saw a recent report about such a behaviour, and it was caused by
cache settings. There is a separate bug.
Can you please check what your cache settings are? I think the bug happens, if
memory cache is set to zero, and disk cache is not zero.
| Reporter | ||
Comment 9•23 years ago
|
||
Kai,
YES, you are correct. Your fix has worked.
My memory cache entry was blank (presumably = 0), and my disk cache was set to
50000.
When I reset my memory cache to 10000 and then *restarted* mozilla, the
behaviour has gone away! (yay!). Note - unlike some settings which can be
changed on the fly in moz (eg proxy etc), presumably moz has to be *restarted*
after changing the memory cache setting for this to take effect. (I tried to
load the ssl page again immediately after changing the setting, but before
restarting, and the same bug behaviour occured).
I can confirm that this bug exists in 0.9.7 and 0.9.9 milestones (the two
versions I have run). I tried to search existing bug reports before filing this
one (sorry if I have filed a dupe) - I can't believe it wasn't filed under a
string like "won't load under SSL". Surely I am not the first to have
experienced this problem? I would have thought it was almost stupid enough to go
in a FAQ :)
Anyway, thanks for your fix. Everything working fine now.
As this is my first bug report, I'm not sure what to mark in terms of closing,
etc, so can I leave this action to someone else on the list. Thanks.
David
Comment 10•23 years ago
|
||
*** This bug has been marked as a duplicate of 136210 ***
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
Updated•9 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•