Take the 2-minute tour ×  When I have mixed content (SSL and
non-SSL on a https:// page), I would rather have a broken page
than an insecure page.  Is there any way to disable the loading
of non-SSL elements while on an https page?  share|improve this
question this isn't really an issue the "non-secure" parts of a
page are the static images ( logos etc. ) and have no reason to
be encrypted. –  Lamar B Dec 13 '11 at 7:53 @LamarB: It can be
an issue if one of the insecure elements is a <script>, a good
target for MITM attacks. –  grawity Dec 13 '11 at 12:51 @grawity
agreed, but if security is that big of an issue you should
already have javascript disabled and selectively run the ones
you need. –  Lamar B Dec 13 '11 at 19:11 @LamarB: Well, first,
many stores and banking sites require JavaScript. But the point
I was trying to make is that without SSL, an attacker could
replace a modify a script which you do need, and you wouldn't
know it. You'd be thinking, "all scripts except this one are
blocked, I'm safe". – 