On 12/10/2011 17:51, Woonsan Ko wrote: > > ----- Original Message ----- >> From: André Warnier <a...@ice-sa.com> >> To: Tomcat Users List <users@tomcat.apache.org> >> Cc: >> Sent: Wednesday, October 12, 2011 11:52 AM >> Subject: Re: redirection error due to context path after JAAS authentication >> with mod_proxy >> >> Woonsan Ko wrote: >>> Hi, >>> >>> I have a reverse proxy configuration like this: >>> >>> <VirtualHost *:80> ServerName localhost ProxyPreserveHost On >> ProxyPass / http://localhost:8080/app1/ ProxyPassReverse / >> http://localhost:8080/app1/ ProxyPassReverseCookiePath /app1 / >> </VirtualHost> >> >> If it is really like above, then why are you using an Apache httpd front-end >> at >> all? >> Would it not be easier (+ simpler, + more efficient) to just get Tomcat to >> listen on port 80 and whatever IP address Apache httpd is listening to right >> now >> ? > > One simple strong reason is that I don't want to run tomcat by root.
JSVC, iptables, Tanuki - bunch of different way to handle that. p >> (To get exactly the same behaviour as above, you would also have to make >> "app1" be the Tomcat ROOT application.) >> >> Note: I also use a lot of setups with Apache httpd as front-end, and Tomcat >> as a >> back-end, and sometimes this is very practical. At least, when the Apache >> httpd >> front-end is actually "doing something" other than forwarding the >> requests to Tomcat. >> But here, it does not seem to be doing anything at all. >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org >> For additional commands, e-mail: users-h...@tomcat.apache.org >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org >
signature.asc
Description: OpenPGP digital signature
