Need to switch to HTTPS:// from HTTP:

Hey Tuan,

I have a very lively site now with 10 to 20 bookings per day. Problem is that I need to switch to HTTPS://. How will it affect the EB component and what do I need to do?

Thanks

Bye

Tim

Everything on my site works fine with either http or https. Make sure that any images that you've included in the event descriptions either reference the relative path (eg: /images/yourimag.jpg) or do not specify the protocol (eg: //yoursite.com/images/youimage.jpg) so that images are being pulled through the current protocol and not creating a "mixed" protocol warning.
If you want to force everyone to your ssl secured https part of the site, you can create a .htaccess rewrite to handle that (do a google search for something like "htaccess redirect select folder to https") or use a [strike]rewrite[/strike] [edit] redirect [end edit] component within Joomla (I've been using ReDJ - extensions.joomla.org/extension/redj with great success as it works with any matching url and not just 404'd urls like the built-in Joomla redirect does).

Regardless of whether you decide to implement HTTPS throughout the entire site. I would strongly recommend that you implement it on your booking pages, or any pages that accept Credit Card.

As it stands, someone can go to a booking link directly and not have HTTPS activated, even when the administrator has enabled it on the back-end. From my point of view this is a security hole in the code.

You can have a look here: joomdonation.com/forum/events-booking-fe...48052-force-ssl.html

In the scope of Events Booking, all you need to do is going to Events Booking -> Configuration, find the config option Activate Https, set it to Yes and the registration page will be https automatically

I also think that this config option is not necessary and I will remove it in the next release 2.3.1. Basically, the extension will check to see whether your server has SSL certificate or not, if it is available, then the registration page will become https automatically

Regards,

Tuan

Hi Tuan,

My personal experience was that this was not always the case. We regularly send the exact registration links to individuals, the .../register.html URL. I found that even with HTTPS activated in the settings. The webpage would still allow people register and enter their credit card details via HTTP. This only became a problem for us when people started entering their details on the site directly for Stripe. It wasn't a problem with PayPal etc.

Hope this helps.

Dave.