Why Mozilla tries to kill Firefox because it cannot connect to https websites? Stupid idea!
When we go to most of https websites, it prompts user to take risk to view the website. It doesn't even allow to connect to some websites such as gmail.com. Do we have to use different browser to view different website? Stupid idea! Why Internet Explorer and Chrome don't have this kind of prompt or problem? If you are trying to kill Firefox, just remove the download software from the internet and shutdown Mozilla and Firefox websites.
すべての返信 (4)
Please explain your exact problem. Are you getting a security error when you try to go to gmail? Can you please give us the error?
Date, time, and time zone correct in Vista? Double-click the time display in the lower-right corner of the system tray to open Date and Time Properties and verify that is correct.
Some some antivirus apps have https scanning features that can interfere and can problems like this in Firefox.
Check the date and time and time zone in the clock on your computer: (double) click the clock icon on the Windows Taskbar.
Check out why the site is untrusted and click "Technical Details" to expand this section. If the certificate is not trusted because no issuer chain was provided (sec_error_unknown_issuer) then see if you can install this intermediate certificate from another source.
You can retrieve the certificate and check details like who issued certificates and expiration dates of certificates.
- Click the link at the bottom of the error page: "I Understand the Risks"
Let Firefox retrieve the certificate: "Add Exception" -> "Get Certificate".
- Click the "View..." button and inspect the certificate and check who is the issuer of the certificate.
You can see more Details like intermediate certificates that are used in the Details pane.
If "I Understand the Risks" is missing then this page may be opened in an (i)frame and in that case try the right-click context menu and use "This Frame: Open Frame in New Tab".
- Note that some firewalls monitor (secure) connections and that programs like Sendori or FiddlerRoot can intercept connections and send their own certificate instead of the website's certificate.
- Note that it is not recommended to add a permanent exception in cases like this, so only use it to inspect the certificate.
If you can't check it with the above posted steps then try this:
Open this chrome URI by pasting or typing this URI in the location/address bar to open the "Add Security Exception" window and check the certificate:
- chrome://pippki/content/exceptionDialog.xul
In the location field type/paste the URL of the website
- retrieve the certificate via the "Get certificate" button
- inspect the certificate via the "View..." button