Not naive at all; I think it's an entirely relevant and obvious question.

In my situation we have a system that's administered by a different group than mine (we're merely application programmers) and the system administrators have settled on doing things this way. They're understaffed and overworked so having a common setup for everyone on this shared system seems reasonable to me.


André Warnier wrote:
Johnny Kewl wrote:

----- Original Message ----- From: "Rusty Wright" <[EMAIL PROTECTED]> To: "Markus Lord" <[EMAIL PROTECTED]>; "Tomcat Users List" <users@tomcat.apache.org>
Sent: Tuesday, October 07, 2008 11:31 PM
Subject: Re: tomcat ROOT


Hi Markus, did you ever figure this out? I was looking in the archives of the tomcat mailing list and saw your query but it didn't seem to me that anyone answered it fully, at least not for me.

I figured out that I could remove/rename the webapps/ROOT directory and deploy my war file as ROOT.war and then it would replace tomcat's web page at http://www.myhost.edu/ but I also have apache in front of tomcat and I don't understand how to set up the jkmount in my httpd.conf file to map apache's root to tomcat's root.

Yes renaming a webapp to ROOT with a empty context path, makes it run as the root...

Then...

JkMount /  worker1

Should make apache send it to your tomcat root

My naive question then would be : why keep Apache in front of Tomcat, if you are redirecting/proxying everything anyway ?

---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to