搜尋 Mozilla 技術支援網站

防止技術支援詐騙。我們絕對不會要求您撥打電話或發送簡訊,或是提供個人資訊。請用「回報濫用」功能回報可疑的行為。

了解更多

Why doesn't Mozilla have a valid certificate for its support survey page?

  • 3 回覆
  • 3 有這個問題
  • 4 次檢視
  • 最近回覆由 jmaloney

more options

I received the following email asking me to complete a survey:

"Hi We are working to improve the Mozilla Firefox Support Site and we need your help. If you don't mind, please fill out this survey -- it should only take a few minutes.

http://qsurvey.mozilla.com/s3/cfdb14/i-100600100-662734/

Thank You!"

When I try to go to the survey page I get a message telling me the security certificate is invalid. Mozilla needs to fix this.

I received the following email asking me to complete a survey: "Hi We are working to improve the Mozilla Firefox Support Site and we need your help. If you don't mind, please fill out this survey -- it should only take a few minutes. http://qsurvey.mozilla.com/s3/cfdb14/i-100600100-662734/ Thank You!" When I try to go to the survey page I get a message telling me the security certificate is invalid. Mozilla needs to fix this.

被選擇的解決方法

The link show an open HTTP link and that wouldn't cause this problem.

Is there an HTTP link in the mail or an HTTPS link?

從原來的回覆中察看解決方案 👍 2

所有回覆 (3)

more options

For some reason my screen shot of the error message does not appear in the post above. I'll try to include it here.

more options

選擇的解決方法

The link show an open HTTP link and that wouldn't cause this problem.

Is there an HTTP link in the mail or an HTTPS link?

more options

I use the Firefox add-on HTTPS Everywhere 5.0.5 from EFF, which apparently resulted in this problem on the survey site. When I disable HTTPS Everywhere and go to the link in the email the survey site comes up fine.

The EFF FAQ says in part, "If sites you use don't support HTTPS, ask the site operators to add it; only the site operator is able to enable HTTPS. There is more information and instruction on how server operators can do that in the EFF article How to Deploy HTTPS Correctly." https://www.eff.org/https-everywhere/deploying-https

Thanks for your comment identifying the problem.