Always make a drawing.
client -> https -> tcp-loadbalancer -> still same https connection-> multiple
tomcats
client -> https -> http-loadbalancer (Apache, proxy) -> new ajp/http(s)
connection-> multiple tomcats
Normally the loadbalancer and tomcats are in the same private network. It is
your choice if that is secure enough. In the end the data is unencrypted in the
database I guess, so normally you trust your own network.
Ronald.
Op woensdag, 25 november 2009 10:18 schreef jkv <j.kumara...@gmail.com>:
Hello,
We are using Tomcat 6.0 and running HTTPS (enabled SSL). The number of
requests has grown up and we have decided to do go for clustering and
loadbalancing. We have decided to go for Apache and mod_proxy/mod_jk
loadbalacing. My certificate resides in Tomcat.
In order to loadbalance HTTPS request using Apache and mod_proxy/mod_jk,
should I configure Apache to handle HTTPS and tell it about my certificate
details?
While loadbalancing I understand that http/https request to Apache is
converted to ajp and tunneled to Tomcat, so is ajp protocol secure? should I
enable SSL in tomcat to handle this request?
Should I have two copies of my certificate files if Apache and Tomcat reside
on two different physical machines(Horizontal Clustering)?
I searched the forums and they are too advanced for my question. I am really
new to clustering and load balancing and any help is deeply appreciated.
Thanks in advance.
Regards
jkv
--
View this message in context:
http://old.nabble.com/Tomcat-Https-loadbalancing---tp26509573p26509573.html
Sent from the Tomcat - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
