Printable View
Using ver. 1.5.7 ppatch 1
I noticed that I get the following screen on Firefox: Attachment 20140
Connection Not Secure
Parts of this page are not secure (such as images)
In both configure files my page is directed to the https://www.pazdarwinery.com
In the admin configure file I have the following:
define('HTTP_CATALOG_SERVER', 'https://www.pazdarwinery.com');
define('HTTPS_CATALOG_SERVER', 'https://www.pazdarwinery.com');
The enable SSL are set to 'true'
What else do I need to change?
If you view the source code of the home page (View Source) and search its contents for http: you will see all of the links that are insecure i.e. non-https.
It looks to me that all of them have been added by you rather than generated by ZC. You should change them to https:
BTW, it's possible that the links to categories in the center column blurb have been added as Absolute instead of Relative links.
Good info at https://www.w3schools.com/html/html_filepaths.asp
Once you get that straightened out, you need to take a look at matching your SSL to your site.
Your SSL certificate specifies it is for www.pazdarwineryDOTcom.
That's not common in SSLs today as www is SO last millenium. It's hardly even put on correspondence or business cards anymore.
However, you and your customers can have access problems because of this. And, Google may knock your ranking down for duplicate content.
Both of those could happen because your SSL specifies www and you can also reach your site without the www. Store owners have reported problems accessiing their admin if they get the URL wrong.
If you can't easily change your SSL to non-www, then I would add a redirect either in your cPanel or similar controller. You can also add a redirect in your .htaccess file located in the root of your site.
Either way, you want to force the site to go to www.pazddarwineryDOT.com no matter what is entered in the browser. This stops the look of duplication and makes sure everyone arrrives at www.pazdarwineryDOTcom versus pazdarwineryDOT.com
:thumbsup:
Thank you, that cleared it. I never thought to make sure those were all "https" instead of "http"
I do have the redirect set up so that non "www" goes to the store, thank you
It might make sense to check that the altered external links still work as https - I would have thought they would but you never know.Quote:
Originally Posted by pazdar
If you are not sure of the externals setting, you can use simply // versus https://
With the // the browser will adjust accordingly