>> Our tomcat apps are self-contained (non-exploded) wars, and >> mapping each individual extension beomces a challenge (ie: >> .jsp, .jspa, jsps, .jpg, .js, .....), so we found it easier >> just to map the entire context.
>In that case, why are you using httpd at all? Is it needed for some >other reason? If all your requests are going to Tomcat anyway, adding >httpd to the mix just slows things down. Well, individual applications run using mapped contexts, but there are still other static pages being mapped as well. Not to mention other virtual hosts that I do not want to host using Tomcat. For example: www.mydomain.com/* is static content www.mydomain.com/app1 is context for tomcat application 1 www.mydomain.com/app2 is context for tomcat application 2 www.myotherdomain.com/* is static content for a virtual server ... etc. Plus, like this I get to harness all the advantages of httpd (including .htaccess, php, perl, etc) without having to worry about the java server. Also it lets me separate my web server from my application server, and gives me a little more firewall control over my java application server (only JK ports are open, for example, and machine is only accessible internally, etc.). Thanks again. Eric --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
