搜索 | 用户支持

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

详细了解

Firefox not parsing SSL (encrypting page) but other browsers are

  • 5 个回答
  • 23 人有此问题
  • 1 次查看
  • 最后回复者为 markhtpa

more options

I have a secure page that IE, Safari, Chrome all encrypt correctly but FF will not. If you go directly to the page from an external link FF does encrypt the page. BUT if you go to the page from another page within the site, while using the site navigation menu system the page does not encrypt. If you refresh the page while you're on it, it goes ahead and encrypts.

So, what's not working is (for example) if you're on the home page at http://kmisinc.com and you go to the Registration form using the site navigation, i.e. Classes & Events -> Register Online FF will not encrypt the page. But then if you refresh the page it encrypts.

When it doesn't encrypt the page there is an exclamation mark (!) on top of the lock icon. If you click on that the dialog states that some of the content on the page is not encrypted and some is. But this is not true.

Thank you for any assistance -Mark

I have a secure page that IE, Safari, Chrome all encrypt correctly but FF will not. If you go directly to the page from an external link FF does encrypt the page. BUT if you go to the page from another page within the site, while using the site navigation menu system the page does not encrypt. If you refresh the page while you're on it, it goes ahead and encrypts. So, what's not working is (for example) if you're on the home page at http://kmisinc.com and you go to the Registration form using the site navigation, i.e. Classes & Events -> Register Online FF will not encrypt the page. But then if you refresh the page it encrypts. When it doesn't encrypt the page there is an exclamation mark (!) on top of the lock icon. If you click on that the dialog states that some of the content on the page is not encrypted and some is. But this is not true. Thank you for any assistance -Mark

所有回复 (5)

more options

I've found a temporary solution to this problem by adding this code inside the head tags:

<script> var reloaded = false; var loc=""+document.location; loc = loc.indexOf("?reloaded=")!=-1?loc.substring(loc.indexOf("?reloaded=")+10,loc.length):""; loc = loc.indexOf("&")!=-1?loc.substring(0,loc.indexOf("&")):loc; reloaded = loc!=""?(loc=="true"):reloaded;

function reloadOnceOnly() { if (!reloaded) window.location.replace(window.location+"?reloaded=true"); } reloadOnceOnly(); </script>

However it still states the page is not encrypted, but reloads the page encrypting it automatically.

How can I fix this to where I am not getting this error?

You have requested an encrypted page that contains some unencrypted information. Information that you see or enter on this page could easily be read by a third party.

The page is encrypted but I am still getting this error: https://americantesol.com/advanced-courses-catalog.html

more options

tesol, thanks for this work around. I have learned a bit more about this issue since I made this original post. Earlier versions of FF do not exhibit this same behavior. I can't say at what version it started but for example v3.0 doesn't do it. That version encrypts normally. So it appears it may be a bug that was introduced in later version releases.

I can also share that I have another site that uses a Comodo Certificate and it works fine using FF. the site where the problem exists uses Trust Wave so I initially thought it was a certificate issue. But I see your page uses Geo Trust so this does confuse the situation again.

more options

Thanks for the update. Maybe it is the CSS file that is creating the error. I am going to update the CSS in the head from:

<link href="stylenew2.css" rel="stylesheet" type="text/css" /> to: <link href="https://americantesol.com/stylenew2.css" rel="stylesheet" type="text/css" />

more options

no did not work

more options

That was the first thing I tried, making absolute paths for every single thing on the page, all supporting files. I even went so far as to put absolute paths inside the style sheet where images were being used. Made no difference for me.