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

Question

I have a security certificate provided by the CDN provider. Website: https: www.connect4fitness.com

Going 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 in firefox or chrome, everything works fine. But I see a warning about “Mixed Content” and “Partially Encrypted Content” when I look at the certificate data.

All outgoing links on the site are https. This is probably some content that introduces the CDN causing the message. But how to determine the exact part of a webpage that is not encrypted? I need this information to work with CDN's technical support, as they claim that everything is in order.

Are there any tools or methods that I can use to find out which part of the displayed page received by the browser is NOT encrypted?

Additional Information:

Clearing the CDN cache resolves error messages for Firefox and Chrome. IE is still complaining about mixed content, although I don't see any “http” requests coming out of the “Network” tab. Any ideas?

Answer 1

I finally found the problem.

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

In the end, I just got rid of the plugin because on their website they took care of the problem when they last had it ( See here ). I think this probably repeated, and I'm not going to experiment with it, since it was a plugin with a nice connection.

Answer 2

The actual problem that caused the mixed content error in IE was a broken link to the included javascript file. The call was https, but this did not lead to 200 responses and something made IE stop issuing further calls when it tried to load the page. I deleted this call and then IE loaded the full page without any warnings or errors.

Answer 3

Never use http:// links on a page served by https:// . The fact that it does not affect the user experience in Firefox is more likely a Firefox bug than anything else; perfectly. (Another issue with Firefox, unless it has changed recently, is that it will only display a warning after sending a request anyway.)

Use the Chrome or Firebug developer tools (Network tab) to find out which resources are loaded with simple HTTP and use the https:// URI instead. (You may need to use a CDN that supports HTTPS.)