mod_proxy is only for proxy forward. mod_jk is using to be load balancer.
[client] <--https--> [Apache] <--ajp13--> [JBoss 3.2.5 (A)]
^--------ajp13--> [JBoss 3.2.5 (B)]
When i setup all the ssl in Apache and JBoss, and using Ethereal to capture the data from Apache, i found that the data haven't encrypt in ajp13.
So that i can't use mod_proxy to do load balancer.^^
Hi there! I am dealing with a similar problem. The SSL part works (clients can access my JBoss content via Apache using HTTPS), but the authentication doesn't.
Before, when I was using Tomcat 5.5 stand-alone, clients had to authenticate with a name/password before viewing pages. Now, using JBoss 4.0.3 SP1, they can just get right in.
My mod_jk configuration is almost exactly the same.
Any thoughts, anyone? All help is appreciated.