Are there any tools or techniques to help determine the exact cause of a nonsecure page element error?

Question

I run into this quite often where a new page is supposedly "tested" and ready to go. But as soon as I change the page from http to https (secure) mode I get the "This page contains both secure and nonsecure items." error.

Usually I can find the problem and fix it pretty quick. Today is different. I've checked every image reference and every javascript reference and their source and haven't found anything that should be causing this error.

Are there any developer tools or techniques that can point out specifically what is causing this error?

Answer 1

If you're in Firefox you can use Tools -> Page Info -> Media, then just scan down the list to find the non-https link. There might also be JavaScript building dynamic <script> tags, or CSS including non-secure elements.

Answer 2

Firebug's Net panel. Again, only in Firefox, although Firebug Lite might include this, I'm not sure. If it does, that'd cover this too.

Answer 3

I don't think these answer the question - I have the same issue - I've found many times tracking scripts even when loading via https the JS will have a http link somewhere in it that will cause this. A utility that identifies exactly WHAT is loading insecurely would be invaluable. Anybody?

Answer 4

Just to add a couple of other tools should someone have this problem in the future:

• If you're using IE, there is Fiddler.
• Wireshark is another tool that may be useful.