You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Wade Billings <wb...@lowermybills.com> on 2004/09/12 20:54:43 UTC
Tomcat-Apache and SSL- Re-Post
Here is a fun one for ya all... We recently decided to migrate from a
Jrun/Apahe platform to an Apache2.0/Tomcat5.0 platform. Everything went
great until we placed it into production and found that our SSL sites
were broken.
Here are the details, and forgive me, as I am not a developer so I may
misquote some Java terminology.... Be patient...
WE determine whether or not a page is secured via which port it is
sourced from. We have a pair of load balancers, which handle all of the
SSL, and pass only HTTP/1.1 back to the actual web servers where the JVM
sits. IN order for the app to determine whether or not it is secure, we
source all SSL'ized traffic from port 8000. This setup works very well
on Jrun, but not so well on Tomcat. It appears that for some reason, the
source port of 8000 is either lost or ignored during the
Apache/AJP13/Tomcat conversation.
What I need to be able to do is to get Tomcat to recognize that the
source port from the load balancer has changed from port 80 to port 8000
so our app will behave correctly and will present our pages as secure.
Any help is greatly appreciated.....
Cheers,
Q. Wade Billings
Re: Tomcat-Apache and SSL- Re-Post
Posted by Bill Barker <wb...@wilshire.com>.
If 8000 is the Apache port, then use request.getLocalPort(). If 8000 is the
AJP port, it can't be done.
"Wade Billings" <wb...@lowermybills.com> wrote in message
news:9216686F09CDEC4BBCC9B08203C21348040F5B@lmbpexc01.lmbcorp.com...
Here is a fun one for ya all... We recently decided to migrate from a
Jrun/Apahe platform to an Apache2.0/Tomcat5.0 platform. Everything went
great until we placed it into production and found that our SSL sites
were broken.
Here are the details, and forgive me, as I am not a developer so I may
misquote some Java terminology.... Be patient...
WE determine whether or not a page is secured via which port it is
sourced from. We have a pair of load balancers, which handle all of the
SSL, and pass only HTTP/1.1 back to the actual web servers where the JVM
sits. IN order for the app to determine whether or not it is secure, we
source all SSL'ized traffic from port 8000. This setup works very well
on Jrun, but not so well on Tomcat. It appears that for some reason, the
source port of 8000 is either lost or ignored during the
Apache/AJP13/Tomcat conversation.
What I need to be able to do is to get Tomcat to recognize that the
source port from the load balancer has changed from port 80 to port 8000
so our app will behave correctly and will present our pages as secure.
Any help is greatly appreciated.....
Cheers,
Q. Wade Billings
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
AW: Tomcat-Apache and SSL- Re-Post
Posted by SH Solutions <sh...@gmx.net>.
Hi
> ... that the source port from the load balancer has changed from port 80
to port 8000 so our app will behave correctly and will present our pages as
secure.
Are you sure, you are talking about source ports?
Since you need to contact tomcat on the same port every time and your target
and source ips are always the same too, there would be no way for the tcp/ip
stack to associate packets with connection...
Regards,
Steffen
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org