Unsecured Content

[masterrusty]

My site(s) Fantasycostume.com & Fantasycostume.net are serving the "Advanced Search" link as unsecured (even on secured pages). How do I change that?

Here is some more info...
(example of issue)
https://fantasycostume.com/index.php...eywords%20here

(error from console)
Mixed Content: The page at 'https://fantasycostume.com/index.php?main_page=advanced_search&search_in_description=1&keyword=Enter%20sear ch%20keywords%20here' was loaded over a secure connection, but contains a form that targets an insecure endpoint 'http://www.fantasycostume.com/index.php?main_page=advanced_search_result'. This endpoint should be made available over a secure connection.

[carlwhat]

change the HTTP_SERVER in your configure.php file to the same as HTTPS_SERVER, ie:

define('HTTP_SERVER', 'https://yoursite.com');
define('HTTPS_SERVER', 'https://yoursite.com');

notice https in both entries.

[mc12345678]

ZC guidance for implementing SSL is at: https://www.zen-cart.com/content.php...alled-zen-cart

Would suggest verifying the actions described be confirmed complete.

[masterrusty]

ZC guidance for implementing SSL is at: https://www.zen-cart.com/content.php...alled-zen-cart

Would suggest verifying the actions described be confirmed complete.

This site has had SSL for over 20 years. Are you telling me that I need to "re-implement" now?


The other comment basically said that I should make the whole site secure (change my standard HTTP server to an HTTPS address). Aren't there potential issues with doing that?

[carlwhat]

This site has had SSL for over 20 years. Are you telling me that I need to "re-implement" now?


The other comment basically said that I should make the whole site secure (change my standard HTTP server to an HTTPS address). Aren't there potential issues with doing that?

rusty,
perhaps you should be clearer in your description of your problem.

in re-looking at what you are now saying, i have no idea what your issue is.

recent changes in google's search algorithm have any number of people asking about how to make their site https for the WHOLE site. the only issue with that is speed and resources. which in today's internet is not much of an issue. which is what i assumed you are talking about. forgive me for my assumption.

you have a search page that one can get to using either http or https. there is no redirection whatsoever.

the search page is NOT considered to be a secure form, so if one gets there via https, you WILL have the 'error' that i think you are talking about. which is not really an error, it is a warning. because you arrived at a page via https, ZC does not automatically put every form on that page to https. only what ZC deems to be sensitive information. product search does not fall in that realm.

the accepted way in ZC to address this 'issue' is to make your whole site https. else i would not worry about this warning.

[answer=42]

Carlwhat explained it better.

[masterrusty]

Thanks. I think I got it.

[delia]

When you make the site secure by forcing it thru htaccess, it is easy to forget to make sure the configure file matches. The site works fine (unless you have one of the payment methods that requires secure) and it's easy to never realize the configure file wasn't changed. The symptoms are two that I've run into recently - the search form is one and a disappearing payment method is the other. Can't believe i missed it but did it twice recently.