Originally posted by nagrom I suspect it comes from calling up images or external scripts outside the SSL layer (like an external style sheet called with an absolute path)
Does anyone know?
And you are absolutely right. Having images or scripts outside the secure server will trigger this message. A quick solution: copy them into the secure directory and call them within the secure layer. Redundant, yes, but it rids you of that annoying message.. which might also drive paranoid customers away.
Actually, if you have any images on the page they should reference the HTTPS:// as well or the page will give the error. It means that all "components" on the page are not loading as secure... so somewhere there is a reference (whether it is a script or picture) with HTTP instead of HTTPS - If you have any ABSOLUTE urls that might be where your prob is...