Mozilla 도움말 검색

고객 지원 사기를 피하세요. 저희는 여러분께 절대로 전화를 걸거나 문자를 보내거나 개인 정보를 공유하도록 요청하지 않습니다. "악용 사례 신고"옵션을 사용하여 의심스러운 활동을 신고해 주세요.

자세히 살펴보기

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

  • 3 답장
  • 3 이 문제를 만남
  • 1 보기
  • 최종 답변자: 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.