SSL Not working on Safari?

  • Posts: 21
  • Thank you received: 2
10 years 10 months ago #163195

-- HikaShop version -- : Latest
-- Joomla version -- : Latest

I'm struggling to get my SSL to work with Hikashop on Safari (Mac OSX). The administration side of Joomla is clearly using SSL (https) and works fine by showing the padlock icon but when I go to checkout in Hikashop the SSL padlock is not shown. If I try the same in Google Chrome, the SSL works fine (it shows the padlock).

If I try to force SSL on the entire site (in the Joomla system configuration, all the pages fail to load due to "too many redirects". If I retype the carts URL adding https:// to the front on Safari, the page refreshes and just returns to www

Any Suggestions? :-)

Last edit: 10 years 10 months ago by Scott. Reason: More information

Please Log in or Create an account to join the conversation.

  • Posts: 83831
  • Thank you received: 13572
  • MODERATOR
10 years 10 months ago #163199

Hi,

Turning on the Force SSL on checkout option should be enough to activate the SSL on the checkout.
HikaShop has a failsafe in order to avoid loops like you have with Joomla's SSL.
So apparently the issue would be a SEF extension or a modification of your htaccess which redirects HTTPS requests to HTTP. I would recommend to first check on that because there is no point in trying to activate SSL on your website if you have something else which forces the website to not display with SSL.

Please Log in or Create an account to join the conversation.

  • Posts: 21
  • Thank you received: 2
10 years 10 months ago #163259

Thanks for the reply Nicolas, I think the SSL is working - its just not displaying the padlock on Safari.

When using Google chrome it displays the padlock on checkout, as does IE but Safari does not. However, when using the admin side of Joomla, it does display the padlock icon and https:.

I believe this may be an issue or coding bug with Hikashop on a Safari browser?

Last edit: 10 years 10 months ago by Scott.

Please Log in or Create an account to join the conversation.

  • Posts: 21
  • Thank you received: 2
10 years 10 months ago #163310

I've found the problem.

For possible future reference, Safari places more variables that must be satisfied for it to consider the site safe, my problem was due to my template calling http://google for its fonts. I had to change all the font calls to https:// and it works fine now.

The following user(s) said Thank You: Jerome

Please Log in or Create an account to join the conversation.

Time to create page: 0.056 seconds
Powered by Kunena Forum