Tad Woods wrote: > However, looking at the Tomcat Manager, my web app now appears twice, once > under "/root" and again under "/". That makes sense if the directories under > the appBase are now automatically added as Contexts.
Try using ROOT. Case is important. > So, why not just do the following instead, where emptyAppBase is an empty > directory? > > <Host name="katchconstructionsupply.com" appBase="/home/katch/emptyAppBase"> > <Context path="" docBase="/home/katch/public_html" /> That would work but means having to add a Context element for every context. Which, as an aside, is best not being place in server.xml. See http://tomcat.apache.org/tomcat-6.0-doc/config/context.html > I guess I don't understand the purpose or benefit of automatically adding > directories under appBase as Contexts. What am I missing? I have too many > URL patterns established as bookmarks on clients to change the Context's > path from "". Ease of management. > On a related issue, although url-patterns taking precedence over directories > now works for me again, password protecting directories that are part of the > <url-pattern> no longer works. For example, password-protecting the > directory "/office" and then having "/office" as a <url-pattern> for a > servlet, previously caused the client to be required to provide the password > and then the servlet would proceed to handle the request. Now, however > Tomcat is handling the request completely bypasses any password on a > directory of the same name. Does this sound like correct behavior? No that is not correct. It sounds like your configuration is still messed up. Mark --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
