Internet Explorer blocked this website from displaying content with security certificate errors

Question

I have a security certificate hosted by a CDN provider. The website is https:www.connect4fitness.com

Navigating to the site in IE gives the following error:

"Internet Explorer blocked this website from displaying content with security certificate errors."

When I pull the site up in firefox or chrome, everything works fine. But I do see a warning about "Mixed content" and "Partially encrypted content" when I probe the certificate details.

All the outbound links on the site are https. It's probably some content injected by the CDN that is triggering the message. But how do I pinpoint the exact part of the webpage that is not being encrypted? I need that information to work with the Tech Support of the CDN company as they are claiming everything is fine.

Are there any tools or techniques that I can use to find out which part of the rendered page received by the browser was NOT encrypted?

Additional information:

Purging the CDN cache resolved the error messages for Firefox and Chrome. IE still complains about mixed content though I do not see any "http" requests going out on the Network tab. Any ideas?

Answer 1

I finally found the issue.

I had javascript plugin for client-side exception logging (exceptionhub). This plugin inserted runtime JS to make an https call to it's servers for logging and got a certificate error. Apparently only IE found this objectionable as the other browsers did not complain.

In the end I just got rid of the plugin because per their website they took care of the issue when they last had it (See here). I think it probably recurred and I am not about to experiment with it as it was a nice-to-have plugin.

Answer 2

The actual issue that was triggering the mixed content error on IE was a broken link to an included hosted javascript file. The call was https but it did not result in 200 response and that somehow made IE stop issuing further calls as it tried to load the page. I removed this call and then IE loaded the full page without any warnings or errors.

Answer 3

Never use http:// links in a page served over https://. The fact that it doesn't impact the user experience in Firefox is more of a Firefox bug than anything else; ideally, it should. (One other problem with Firefox, unless it has changed recently, is that it will only show the warning after having sent the request anyway.)

Use Chrome's Developer Tools or Firebug (Network tab) to find out which resources are loaded with plain HTTP and use https:// URIs instead. (You may need to use a CDN that supports HTTPS.)