tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Randy Layman <>
Subject RE: Tomcat/Apache/Firewalls
Date Tue, 30 Jan 2001 16:45:03 GMT

	This is right.   The process is firewal -> Apache -> mod_jk ->
Tomcat, and then the reverse.  The client receives the request on port 80
and never even knows that Tomcat was involved.  The downside to this is that
you can't shutdown Tomcat from outside the network (probably no a problem,


-----Original Message-----
From: Gearoid Griffin []
Sent: Tuesday, January 30, 2001 11:59 AM
Subject: Tomcat/Apache/Firewalls

I'm trying to get my head around trying to make tomcat as secure as
Basically I'm unable to get any other ports open in our firewall bar 80. 
What I'm trying to do is when a user sends a request to our site (first hes 
reversed proxied just to knock out any bizarre strings) then the query gets 
sent to apache,( with mod_jk, and tomcat hanging off it.) runs various 
servlets (cocoon, xerces,xalan, etc) but sends the response back via port 
80? Is this possible? Or do I just have to live with the fact of having 
other ports (for tomcat and the ajpmountpoint) open on the router?
GearĂ³id Griffin

To unsubscribe, e-mail:
For additional commands, email:

View raw message