Depending on what browser and what version you use, the dialog box will appear differently. The message is still the same though: You're viewing a secure page (https://
...) and a warning pops up that there is some insecure content mixed in, asking you what to do about it. It happens on small sites, corporate sites, even banks, social networking and other very large sites that should have the technical know-how not to scare you like that. (This can be especially scary when you get security messages from your bank's website!)
So what is it?
If this error appears on your own site, which you know doesn't contain any malicious hacking code, what do you do about it?
... that will trigger the security warning. The same applies for calling images from another server, which is a common technique for distributing the server load by hosting images separate from the main content. So the way to solve this is to load everything from a secure https connection. Depending on how your code is written, this can be done either by writing all references with a complete URL such as https://myserver.com/images/foo.jpg
or if they are on the same server your page is on, by a relative URL such as /images/foo.jpg. Once there are no longer any non-secured items in your secure page, the warning should go away. (Note: This does not apply to outbound URLs - you don't have to worry about changing your <a> tags, so <a href="http://www.google.com
">Google</a> is still okay.)
A sneaky trick
> you can write it as <img src="//imgserver.myserver.
/foo.jpg> and omit the "http" or "https" altogether. This tells the user's browser to use whichever protocol the current page is using. I use this technique when I load the jQuery library on a page, so I don't have to worry about using the secure or non-secure links when referencing the externally-hosted library.
Important note about browser settings
- If you search around on your favorite search engine for getting rid of the mixed security mode error, many sites will give you directions on changing your browser settings to enable display of mixed content. Besides the fact that it only changes the behavior for YOUR browser, not everyone else's, this is the web-surfing equivalent of closing your eyes when somebody points a gun at you. The potential danger is still there, but you don't see it. The better solution is to fix the actual issue with your own site so that it doesn't exist in the first place. Change your mixed-mode settings with extreme caution.. they can hide a real problem from view if there is malicious code on somebody else's site.