SEC7111: HTTPS security is compromised by https://www.example.com.
This is not the typical mixed content browser warning when you have an HTTPS page loading an HTTP resource. This is the opposite (HTTPS resource on an HTTP page). Neither Chrome or Firefox give any warning on this page. Just IE11 gives the error. My IE11 setting is to Prompt for mixed content, however it doesn't actually prompt and is actually loading the HTTPS iframe. The only indication of mixed content in IE11 is the error in the developer console.
Question 1: Will having an HTTPS resource on an HTTP page cause problems? Are there other browsers that may either refuse to load the iframe or display a message/dialog prompting whether to load mixed content? Ideally I'd like the iframe to load and for there not to be any browser warnings. My instincts are that loading HTTPS content on an HTTP page should be alright, which I'm sure is why Firefox and Chrome are not displaying any messages.
Interestingly, I have run across some HTTP webpages that have an HTTPS script tag on them. For example a script tag to https://apis.google.com/js/plusone.js on an HTTP page. IE11 does not give any errors in the developer console on this page. Because both the
script tag and
iframe tag are considered mixed "active" content tags, I would expect that IE11 would also raise an error for this HTTPS script tag, but it doesn't. Question 2, what is the reason IE11 doesn't report a mixed content error in this scenario?