Hi! Apache and Tomcat ARE working at the moment (with mod_jk). That is not the problem. The problem is that Jetspeed writes the port Tomcat is running on into the URLs. -----Ursprüngliche Nachricht----- Von: Jim O'Connor [mailto:[EMAIL PROTECTED]] Gesendet: Freitag, 31. August 2001 13:28 An: [EMAIL PROTECTED] Betreff: Re: Apache 1.3.x / Tomcat / Firewall = no go ? Norman, You need to have Apache hand-off to Tomcat, using mod_jk. Take a look at this http://jakarta.apache.org/tomcat/tomcat-3.3-doc/mod_jk-howto.html ----- Original Message ----- From: Norman Schoneich <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, August 30, 2001 11:34 AM Subject: Apache 1.3.x / Tomcat / Firewall = no go ? > Hi! > > I've set up Apache as a proxy(+ reverse proxy) for Tomcat 3.2.3 and I'm > using the current (cvs) Jetspeed version. My problem with this setup is that > Jetspeed adds the tomcat port (8080) to the urls. But there's no access > through the firewall to the 8080 urls. How can I tell Jetspeed to add port > 80 instead of port 8080 to the urls or simply add nothing ? > > TIA. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]