Resource Center : Tech Speak : <IE6/7 mixed content/ unsecure content warning in https / SSL pages>

IE6/7 mixed content/ unsecure content warning in https / SSL pages

When you develop applications for https protocol, you come across the mixed content warning in browsers, because of some content in the page being loaded from something other than https protocol.

And obviously you would remove or redirect all your non-https URL's to https based URLs. and if the error still happens, you might go through view source or the actual html output received by the browser from the server, to detect which content exactly causes the warning.

The most common items that are hard to detect here are:

1. If you have flash animation or video on the webpage, you must check whether the codebase url and object src or embed src URLs are https protocol. If not, you should make them. For codebase URLs which are usually some adobe.com or macromedia.com URL for flash content, you can just convert the http to https in the URL and try.

2. If you have iframe with a 'about:blank' or some window object which you initialize to or load with a blank page using 'about:blank', then this will cause problems in older IE versions.. IE 7 understands that about:blank is not unsecure content but just a blank page. To make it compatible with older browsers, like IE6, you might have to create a blank page like https://mysite.com/blank.html and use it.

Advertisement