I only use Google Chrome these day for browsing. But when I am creating a design I also test in Internet Explorer and Firefox.
I had an issue the other day when I set up a design I made on localhost to the live server. All went well, until I had to set up the osCommerce site to use SSL – we all know how easy this is…a change in the configure file and all is done.
Then I tested it in Chrome. The browser was telling me there was unsecured content within the page! Well, after a good 30 minutes of checking through my code, I can’t find anything that is insecure!
I then checked the site in both Internet Explorer and Firefox – guess what – padlock SSL is working just fine with no insecure warnings! Try Google Chrome again, and it is still giving me warnings.
I then Googled and found some bug reports for Chrome, one of which is the SSL problem. It seems as though Chrome issues an insecure report when ANY link within a https page is linked to a http page! So this in a https page;
will make Chrome choke and give an insecure warning – simply because the link is to a http page rather than a https page. This is a bug that needs sorting out, please Google.
Anyway, just wanted to post this to save anyone else from wasting time hunting for a fix when they see Chrome is giving a warning when other browsers are not.