Closed
Bug 738715
Opened 13 years ago
Closed 13 years ago
SSL cannot continue
Categories
(Firefox :: Untriaged, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 659736
People
(Reporter: knoxth, Unassigned)
References
()
Details
Attachments
(1 file)
|
192.06 KB,
image/png
|
Details |
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:11.0) Gecko/20100101 Firefox/11.0
Build ID: 20120312181643
Steps to reproduce:
Tried to go to a site with a self-signed SSL certificate
Actual results:
I was told that the site wasn't trusted and chose I UNderstand The Risks. Then, in the following screen, I was told that the certificate is valid. This leaves me no way of continuing and actually going to the site
Expected results:
It should eaither have trusted the connection from the get go or allowed me to confirm.
Comment 1•13 years ago
|
||
adding an exception works for me with Mozilla/5.0 (Windows NT 6.1; rv:14.0) Gecko/20120322 Firefox/14.0a1 SeaMonkey/2.11a1 and Firefox 11.0
Does it work with a new profile ?
http://support.mozilla.org/kb/Managing%20profiles
Comment 2•13 years ago
|
||
WFM - Mozilla/5.0 (Windows NT 5.1; rv:14.0) Gecko/20120323 Firefox/14.0a1 ID:20120323031214
Did you install the certificate into Firefox? What happens if you reload the page?
| Reporter | ||
Comment 3•13 years ago
|
||
Yes, the first time I went to the site I installed the certificate and everything worked completely correctly. When I went back, this is what happened. I have reloaded the page multiple times. I can't get past this screen now.
| Reporter | ||
Comment 4•13 years ago
|
||
It works with a different profile.
Comment 5•13 years ago
|
||
Does clearing the cache (see bug 659736 comment 64) help?
Whiteboard: [closeme 2012-05-10]
| Reporter | ||
Comment 6•13 years ago
|
||
Yes, clearning the cache solved the issue.
Comment 7•13 years ago
|
||
Thanks for the update. It means that your issue was the same as 659736.
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → DUPLICATE
Whiteboard: [closeme 2012-05-10]
You need to log in
before you can comment on or make changes to this bug.
Description
•