Can we get rid of the "This page contains both secure and nonsecure items" warning?
When I did some searching on google, I found that full paths [ http://....] especially for images referred from secure sites can cause these. We are using the relative paths only in our application. [../ or mostly /mydir...]
However, there are some links on the page which are anchors to some other site. Say this is the portal main site.. our application will be one part of it.
1. On one site I read that such anchor [<a href>] tags do not create such alerts. Is it true? 2. Also on one forum I read that it does not come because of the 'http://' occurences I have in the serverside [in web services/ namespace references etc] 3. I have AJAX for some other functionality. For IE we are initializing one activeX control for it. Can this be the cause?
Any hint will be a huge help!
Moderator: If this is not a proper forum, can you move this to the one which is right and can fetch me an answer? Thanks!
Alongwith being a good coder, try to be a good professional as well!
Joined: Mar 22, 2005
Having HTTP links to other sites in a page will not trigger this warning (but it will trigger a different warning if you click on them.)
How can I find out what is making the problem? Which element? Now we know its because of the mixing of content. But when I do a view source of the page, I do not get anything in search of the html source that is 'http:'. How do I search/debug this?
Joined: Mar 22, 2005
You can check the log files of the web server to see which resources are accessed. Or use Firefox with the excellent LiveHttpHeaders extension, which logs all HTTP(S) requests and responses.
Originally posted by Tina Desai: How can I find out what is making the problem? Which element? Now we know its because of the mixing of content. But when I do a view source of the page, I do not get anything in search of the html source that is 'http:'. How do I search/debug this?
MSIE will also throw up that warning if the "href" or "src" attribute of an element (img, iframe, etc..) is blank.