ssl. padlock with yellow triangle. Problem? If so, how to fix?

[zenartman]

Recently we changed our ssl, as old one expired. Then SSL started giving warning signs. In chrome browser, the front https://www.mongolianshop.com looks ok (green padlock). Login page looks ok (greenpadlock).

Once I enter username and password, I see padlock with yellow triangle. Is that a problem?
Then when i further checkout, the padlock becomes normal green back again. Do I need to fix it? If so how?

Strangely, when I logged into this forum I see the same. See the image:


Thank you all.

[jonnyboy22]

This usually indicates some files on the page are not going through the SSL (any files via http not https). e.g. <img src="http://yourdomain.com/pic.jpg"> instead of <img src="https://yourdomain.com/pic.jpg">

If you use Google Chrome, you can use the following guide http://stackoverflow.com/questions/1...-an-https-page to see what items are non-SSL on the page.

Hope this helps.

[colosports]

i took a quick look at your home page and on line 228, have
<img alt="" src="http://mongolianshop.com/images/2cocc02.gif" />

You need to make sure it is
<img alt="" src="https://mongolianshop.com/images/2cocc02.gif" />
or
<img alt="" src="/images/2cocc02.gif" />

[RodG]

You need to make sure it is
<img alt="" src="https://mongolianshop.com/images/2cocc02.gif" />
or
<img alt="" src="/images/2cocc02.gif" />

Unless the image/file is hosted on a different site the second method is the one to use because
1) It avoids the need for a DNS lookup.
2) It will work with both SSL and Non-SSL pages.
3) It makes the site/pages more portable (IOW if the host name or domain name ever gets changed there will be no need to edit the code. Eg. If the site gets moved to/from a subdomain.
4) It will work both with and without the "www"

Many people already know all this, but I thought it worth mentioning for those that think both methods are identical.
Cheers
RodG

[DrByte]

Related FAQ article: http://www.zen-cart.com/content.php?...lly-encrypted)

[zenartman]

Yes, I knew those images that caused the problem. So i deleted them from the server. Then the problem still lingered. Thus i wondered and asked here. Thank you for your feedback.

[zenartman]

Colosport, Dr Byte your recommendations solved the issue.

I deleted the culprit images already before posting this question here. Yet as it appears still there was a code calling for the src=http://.....images.... And got it from the mainpage editor.

Thank you very much.

[RodG]

Yes, I knew those images that caused the problem. So i deleted them from the server. Then the problem still lingered. Thus i wondered and asked here. Thank you for your feedback.

It is hard to tell from your comment whether you've resolved the problem or not.

Deleting the images themselves will not solve the problem (and in some instances can actually make things worse). What you need to do is delete the LINKS to the images, or better yet, FIX the links as has been described throughout this thread.

Cheers
RodG

[zenartman]

Thanks RodG. I solved the problem. Fixed the link and also bought a cup of coffee for ZC.