There is a clear separation for the web applications themselves. There isn't when you allow the different virtual hosts to use the manager to deploy web applications.
I would configure a different appBase for each Host, that way each host has a separate directory where their webapps are located and you won't run into one host stepping on another when deploying applications. Regards, Glenn Chris Price wrote: > > Hi; > > I have a system running Apache 1.3.26, mod_jk and Tomcat 4.1.12. > > Apache has a number of name-based virtual hosts confgured, of which 2 > are setup to route jsp and servlet requests to a ajp13 connector (called > 'ajp13'). ajp13 is setup to use a single tomcat instance running on > localhost at port 8009. Tomcat itself is setup with seperate <Host ...> > </Host> for each of the two corresponding front-end apache virtual > hosts. > > My Question; > > What kind of code seperation does the Tomcat <Host..></Host> facility > provide? > > In other words; what (if any) kind of safety and security mechanisms > exist to ensure that code running under <Host name=www.a.com ...></Host> > from <Host name=www.b.com ...></Host> > > > I found the following excerpt in the Tomcat 3.2 doumentation; > > "We want different virtual hosts served by different Tomcat processes to > provide a clear separation between sites belonging to different > companies" > > Can anyone explain what this means? > > Cheers & TIA > > Chris > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
