This page contains both secure and nonsecure items

[Mantorok]

Hi all

This has been driving me nuts for months now, if I access my site from IE
https://db.cornwall.gov.uk/PlanningApplications and then hover over one of
the 2-level menus it comes up with the message:

"This page contains both secure and nonsecure items. Do you want to display
the nonsecure items?"

I've confirmed that there are "no" nonsecure items on this site, it works ok
from Firefox but not IE.

Can someone have a look at the site and see if they get the same problem -
it's been driving me crazy - and why does it only come up when hovering over
the menu item?

Thanks all
Kev

 

[Marc Gravell]

My money is on the following line:

childFrame.src = (data.iframeUrl ? data.iframeUrl :
"about:blank");

I'm guessing it doesn't like the transition between the "https" and "about"
protocols; this is also supported by the error-message in IE7

Might be wrong, though, but worth a try... could easily test by using a
blank page on your site (not a good option long term - just to check if this
is the cause). If this /is/ the case, try and get rid of the need for the
child frame...

Marc

 

[Mantorok]

Hi

I can't see the line you are mentioning, where are you getting that from?

Thanks
Kev

 

[Marc Gravell]

First - I did a quick test after my last post, and yes: "about:blank"
content does trigger this warning when adjacent to "https" content.

In the HTML is a script include:

<script
src="/PlanningApplications/WebResource.axd?d=_M0QBBJNc5T5u0BVY01Xsw2&amp;t=632706918817031250"
type="text/javascript"></script>

(the filename etc probably looks very different in the original [aspx?]
source; but it's a script include somewhere)

So: get
https://db.cornwall.gov.uk/Planning...QBBJNc5T5u0BVY01Xsw2&amp;t=632706918817031250

Look in this, and there is a PopOut_Show method, which is the one in
question (again, in the source code this is likely to be in a resource file
of some kind - sorry, I'm not an aspx expert so can't say exactly where).

Finally, note that the reason it only breaks in IE might be because Firefox
has a different IFrame implementation, or it could be because of the "isIE"
variable, which means this block only runs on browsers claiming to be IE.

Hope this helps,

Marc