TC and apache don't need to know about each other unless you want tomcat and apache to run on the same port. (This includes SSL on 443...) - TC would have to use a different port than the standard https 443 for secure transmission - if you require such a thing.
Other than that - they can both run on different ports no problem. Randy ----- Original Message ----- From: "Wendy Smoak" <[EMAIL PROTECTED]> To: "'Tomcat Users List'" <[EMAIL PROTECTED]> Sent: Wednesday, October 30, 2002 3:13 PM Subject: Tomcat & Apache, not connected? > > We've currently got Apache running on HP-UX 11. Now I'm developing a Struts > webapp that will need to go on the same box. HP hasn't released Tomcat 4 > yet, so we'll have to get it to work ourselves. > > Since the Struts app has no static content, is there any reason to put > ourselves through the pain of convincing Apache and Tomcat to play nicely > together? Or can the two run on the same machine with no knowledge of one > another? > > The only disadvantage I see is that my Tomcat URL's will have to include a > port number, since Apache is already listening on port 80. > > Anything else I should know? > > -- > Wendy Smoak > http://sourceforge.net/projects/unidbtags > -- To unsubscribe, e-mail: <mailto:tomcat-user-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:tomcat-user-help@;jakarta.apache.org>
