views:

868

answers:

6

I've just got a site running nicely with the whole site running through SSL, but Google Chrome is throwing a "This page contains some insecure elements" message, which isn't good in terms of end user trust-ability. All other browsers work fine, and give the golden padlock.

The site is a Drupal 6 e-commerce site, running on apache2, and the error appears in the front end as well as the admin area.

Does anyone know of any methods to find out exactly which elements are being considered insecure?

Edit: I've used Fiddler to check the traffic, and it really is all HTTPS. It even complains on the site holding page, which is very light and has no javascript etc on it...

+1  A: 

Search the source for http:? Something like <Ctrl-U> <Ctrl-F> http: in firefox should do.

The insecure element is something loaded over insecure — non-https — connection, e.g. image, stylesheet, etc. you obviously need fully qualified URL to load insecure element/

Michael Krelin - hacker
done that, there is only the links to:<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en" dir="ltr"> Taking those out doesn't fix the problem...
jsims281
could it be that stylesheet imports another stylesheet or some script-generated content?
Michael Krelin - hacker
Hmm, there is some styling being done with jquery, but still, all the actual files are coming through https ... looking into this possibility as we speak
jsims281
+1  A: 

Use Firebug plugin of Firefox. In the NET tab all file locations are shown clearly. Try to find any files that are obtained from http protocol.

Cem Kalyoncu
Good idea, I've just checked through all the files, and every one is HTTPS.Really scratching my head about this one...
jsims281
+5  A: 

It could be a browser issue? Have you tried restarting, or clearing all of your cache?

Tisch
Wow, yes this was it. Restarted chrome and it works.<sheepish>
jsims281
;-))) Have to vote this one up.
Michael Krelin - hacker
A: 

In Chrome, this is trivial. Hit CTRL+SHIFT+J to open the developer tools, and it will plainly list the URL of the insecure content.

Try it on https://www.fiddler2.com/test/securepageinsecureimage.htm, for instance.

EricLaw -MSFT-
A: 

FYI, I'm having the same issue with Drupal 6 and Ubercart 2.0. Everything you're saying is also applicable to my situation, and I can't figure it out for the life of me. I don't think this should come into play, but any chance you use ipsCA as your certificate provider?

Did you ever find a solution?

Pat
This is not an answer. Also, the question is clearly resolved; see the green checkmark over there?
ephemient
+1  A: 

It's probably related to this bug:

http://code.google.com/p/chromium/issues/detail?id=24152

Which is why a restart fixed it.