Markus,
Thanks for replying. I saw that line as well:
"The value of this field must not be set except when statically defining
a Context in server.xml, as it will be infered from the filenames used
for either the .xml context file or the docBase."
As the current 5.5 documentation states that it is not recommended to
embed Contexts in server.xml but rather place them in /META-INF/ of the
web app, I was unclear as to the validity of the above statement for my
particular case. That is, I don't staically define my Context in
server.xml, but rather in the recommended location (META-INF).
Thanks for the clarification.
/robert
Markus Schönhaber wrote:
Robert Taylor wrote:
Greetings,
I'm using Tomcat 5.5.15 on Win2k in development.
I start Tomcat through a target in my Ant build and pass it a server.xml
file.
My web app is deployed to a directory named "webapp" (the docbase) and
contains a /META-INF/context.xml file which has a context path, "/test".
When I start tomcat and attempt to access my web app using the context
path of /test, I get a strange 400 error.
HTTP/1.x 400 No Host matches server name localhost
When I access the webapp using /webapp as the context path, tomcat
serves up the content.
Therefore, it appears that Tomcat is ignoring the context path I have
defined and using the docbase directory in name by default.
And that's exactly the way it's documented. Read about <Context>'s
"path"-attribute here:
http://tomcat.apache.org/tomcat-5.5-doc/config/context.html
In essence: in most situations the "path"-attribute is ignored (even
documented as "must not be set") and the Context path is derived from the
corresponding filename.
Regards
mks
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
