Washington Post site comes up as untrusted in Firefox, but not in IE 9.0
I just updated Firefox to 3.6.15. Since then I have had to change my homepage in Firefox from Washington Post to the New York Times because I keep getting this message:
You have asked Firefox to connect securely to www.washingtonpost.com, but we can't confirm that your connection is secure.
Normally, when you try to connect securely, sites will present trusted identification to prove that you are going to the right place. However, this site's identity can't be verified.
I have also changed my default browser to IE 9.0 to get to the Post site without the annoying message
Todas as respostas (8)
Any particular reason you are using HTTPS for that website and not HTTP?
edit: I see you are using HTTPS-Everywhere - that is causing this problem. You need to figure out how that extension works and not use a secure, HTTPS connection for that domain.
I get this - There is a problem with this website's security certificate. - with IE8. Which is the same as an Untrusted Connection in Firefox. Try it yourself.
Modificado por the-edmeister a
I am using one of Mozilla's recommended script blockers. But I can't get to the screen that gives me a choice to allow the site. . I get this message when I click on any link in my newsletter. I have also emailed Washington Post . Should I disable the script blocker entirely?
Just go into HTTPS-Everywhere's option page and uncheck Washington Post.
Thank you. Thank you. It took me a few minutes to figure out how to access the add on . Went to Tools-Add ONS- HTTPS EVERYWHERE- clicked options. Then I went to the list of sites and unchecked Washington Post and New York Times. Interestingly, although the NYT box was checked, I did not have the same problem with the NYT site.
Problem remains. Opened email today, clicked on a link for Washington Post and got the "not trusted" reply AGAIN . Message: www.washingtonpost.com uses an invalid security certificate.
The certificate is only valid for the following names:
a248.e.akamai.net , *.akamaihd.net
(Error code: ssl_error_bad_cert_domain)
I went back to HTTPS Everywhere , clicked on options. Wash Post was unchecked, but the site is still identified as untrusted! Sigh I had also disabled the NO Script AddOn to see if it was causing the problem.
Modificado por SALLYOHIO a
It was happening to me too, despite having only Facebook checked in the settings. I ended up having to disable HTTPS Everywhere altogether. More and more sites are automatically enabling HTTPS, so I think its usefulness is diminishing anyway.
Similar behavior was occurring when I had HTTPFox installed -- a popup alert with only an OK button, instead of the normal "I Understand The Risks" page -- so I suspect there's a Firefox bug somewhere in the interaction between SSL and extensions.
I solved the problem by going to my homepage address under internet options. Rechecked the address and noticed that the Washington Post address was https. I deleted the s , closed and reopened Firefox and now the links work just fine.
How do I find HTTPSEverywhere? Even when I try to go to "add-ons" I get this message. I NEVER selected this option - how did it make it on to my PC?