Insecure URL

[diaza]

Hi,

 

I'm getting several insecure url's but I don't know where I can fix this or what I'm supposed to do...that way my padlock could finally appear. Really appreciate in advance any light, advice or directions! :)

 

Insecure URL: http://fonts.googleapis.com/css?family=Open+Sans:400,300,600,700,800

Found in: https://www.mywebstore.com/

 

Insecure URL: http://themes.googleusercontent.com/static/fonts/opensans/v6/DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf

Found in: http://fonts.googleapis.com/css?family=Open+Sans:400,300,600,700,800

 

Insecure URL: http://themes.googleusercontent.com/static/fonts/opensans/v6/cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf

Found in: http://fonts.googleapis.com/css?family=Open+Sans:400,300,600,700,800

 

Insecure URL: http://themes.googleusercontent.com/static/fonts/opensans/v6/MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf

Found in: http://fonts.googleapis.com/css?family=Open+Sans:400,300,600,700,800

 

Insecure URL: http://themes.googleusercontent.com/static/fonts/opensans/v6/k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf

Found in: http://fonts.googleapis.com/css?family=Open+Sans:400,300,600,700,800

 

Insecure URL: http://themes.googleusercontent.com/static/fonts/opensans/v6/EInbV5DfGHOiMmvb1Xr-honF5uFdDttMLvmWuJdhhgs.ttf

Found in: http://fonts.googleapis.com/css?family=Open+Sans:400,300,600,700,800

[Guest]

@@diaza

 

 

Sorry, those error messages don't give us the information needed to help you.

 

 

 

Chris

[Bob Terveuren]

Hi

 

Somewhere in your template or header file there's a call to download fonts from the Google APi - that's coded in to link through on http://

 

Find where the call is and then try one of the fixes:

 

http://www.amixa.com/blog/2012/06/06/how-to-use-google-fonts-under-both-ssl-and-non-ssl-without-ssl-insecure-messages/

 

or

 

http://www.misterhowto.com/index.php?category=Computers&subcategory=Programming&article=google_web_fonts_ssl

 

The first is easier to code

[MrPhil]

The first thing is that you've misconfigured your store such that the entire thing is under SSL. Unless you have a very good reason to do that, you should let osC put only selected pages under SSL, and leave the rest under non-SSL (http:). If you insist on putting the whole site under SSL (https:), you'll have to do some custom coding updates to remove non-SSL stuff from your pages (or put it under SSL).

[diaza]

thank you all :)