Originally Posted by
machinerye
I used bislewl's instructions, and they worked perfectly, except as I mentioned, when SSL mode, and clicking on the two links in the header, you get the "some items unsecure" notice. However when in regular mode, no problems.
Thank you for the reply, but bislewl provided instructions to accomplish both aspects. That said:
Code:
I didn't (or don't) want to make the whole catalog https for the potential to fall in search engine rankings. That is big for the customers to be able to find me.
indicates that the includes/configure.php file was not modified to have both HTTP_SERVER and HTTPS_SERVER set to https...
As for loss in rankings, I am not associated with any group that has knowledge of how the rankings are currently determined; however, there is one search engine that is pushing for all websites to use https for all web-pages... As part of that, it would seem that the search engine actually favors https web pages over those that are not...
The general/predominant philosophy of those in this forum has been that there should be a need to encrypt the contents of the pages, the most basic need is programmed into ZC at pages such as contact_us, the various checkout pages, login, etc... where effort should be made to encrypt/obscure personal information. Part of the reason not to encrypt every page is that the process uses more computer time and resources, and in the case of presenting say "HI, Welcome to our store." where there is nothing of significance to compromise, then why slow down/burden everything to display that information?
Anyways, this post is likely to bring up more discussion regarding this aspect of the thread, but I thought that I would at least point out that there is/soon to be a change/shift in philosophy about using https to serve pages. There are definite business/legal needs for various pages to be secured, but beyond that is well... subjective.
Bookmarks