Windows 10 已于2025年10月14日停止支持。如果您正在使用 Windows 10,参见 这篇文章

Windows 10 reached EOS (end of support) on October 14, 2025. If you are on Windows 10, see this article.

搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信,及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

详细了解
已存档

in-secure site warning inaccurate

Wesley Branton 已回复
platzermedia

When clients log out from platzermedia.com they get an insecure site warning, even though the URL says https://platzermedia.com if I add a forward slash at the end of the URL or www. in front of the domain there's no insecure site warning. Seems odd that a site would become insecure if a forward slash "/" is removed?!

In other words…

https://platzermedia.com is NOT secure according to Firefox???!!! https://platzermedia.com/ is secure https://www.platzermedia.com is secure

When clients log out from platzermedia.com they get an insecure site warning, even though the URL says https://platzermedia.com if I add a forward slash at the end of the URL or www. in front of the domain there's no insecure site warning. Seems odd that a site would become insecure if a forward slash "/" is removed?! In other words… https://platzermedia.com is NOT secure according to Firefox???!!! https://platzermedia.com/ is secure https://www.platzermedia.com is secure

所有回复 (1)

Your certificate is not correct. It's been issued to www.www.platzermedia.com and www.platzermedia.com. Therefore, when you try to connect without the www, it's not covered by the certificate.

The most likely cause is that when you ordered your SSL certificate, you added the WWW part to the domain that you registered. Most SSL authorities want just the domain because they automatically include the www part.

In this situation, you will need to contact the company that issued the SSL certificate so that they can correct the certificate and issue a new one.

Hope this helps.

NOTE: In my response, I'm assuming that you are the web administrator of this website. If not, contact the website administrator. There's no workaround for this issue because it's not a Firefox problem. It's an issue on the website's end.

由Wesley Branton于修改