As far as it's concerned, HTTPS is just data. It won't have any problem at all forwarding HTTPS data to backend servers but it will not be able to inspect the payload data and then do load balancing based on URL. This means that the HASH & STATIC balancing algorithms will not be useful when forwarding this traffic.
Still, you will get all the features like server node health detection and overload protection if you've got SNMP setup on the server so it's not going to be useless for your needs :)
Also, the way a lot of big sites do SSL is that right up front a SSL accelerator strips off the SSL from the HTTPS and then just forwards the data as normal HTTP to the back-end application servers which typically have to do all the heavy lifting.
Please let me know if you have any more questions.
Cheers
Al
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
hi,
nice project.. can this support HTTPS?. i was going to test for an eCommerce site with maybe 2 or 3 back-end servers for redundancy.
Thanks,
Peter
Hi Peter,
OctopusLB is oblivious to the HTTPS protocol.
As far as it's concerned, HTTPS is just data. It won't have any problem at all forwarding HTTPS data to backend servers but it will not be able to inspect the payload data and then do load balancing based on URL. This means that the HASH & STATIC balancing algorithms will not be useful when forwarding this traffic.
Still, you will get all the features like server node health detection and overload protection if you've got SNMP setup on the server so it's not going to be useless for your needs :)
Also, the way a lot of big sites do SSL is that right up front a SSL accelerator strips off the SSL from the HTTPS and then just forwards the data as normal HTTP to the back-end application servers which typically have to do all the heavy lifting.
Please let me know if you have any more questions.
Cheers
Al