This module doesn't work at all in google chrome. For one as soon as you log in to drupal, it loads the page in https:// even though I told it nowhere to do this. Second, it will not give the green lock. It says that the page includes resources that are not secure??? How is this possible. I even tried to test it by deleting every region and only loading the cart. This is completely bugged in Chrome but works in every other browser. Not good, Chrome is increasing in popularity all the time.
| Comment | File | Size | Author |
|---|---|---|---|
| #5 | mixed_content.png | 218.3 KB | grendzy |
Comments
Comment #1
grendzy commentedI haven't been able to reproduce this - Chrome works fine for me.
You can get a list of insecure resources by checking Chrome's error log under View -> Developer -> Developer Tools.
Comment #2
eeyorrI'm seeing the "includes resources that are not secure" issue in Chrome, as well. This appears to be more of a Chrome issue. Apparently, Chrome throws that warning whenever a secure page serves a resource from a non-secure address. So an image served by an http address could cause this. In my case, my non-secure domain is the same as my secure domain. So http://example.com/catalog gets redirected to https://example.com/catalog. In looking at Chrome's resource list, I see that both url's are listed. The http address is listed as a 302 redirect, so I guess Chrome considers that a security breach.
Edit: Updating to Chrome 13 fixed my problem.
Comment #3
grendzy commentedGlad to hear that Chrome 13 improves the situation. Anyway, mixed content problems can be caused by many things and is beyond the scope of securepages.
Comment #4
thedavidmeister commentedI'm having the same problems with no "mixed content". Just getting a lock with a cross in it that I don't see in other browsers.
Comment #5
grendzy commentedClicking the lock icon in chrome will give a more detailed explanation of the icon. Opening the error console will show even more details. Here's an example of what this looks like when I intentionally added an insecure image to a page body: