Hello,
Parsons Technical Services wrote:
Now as for the issue, I am not sure that it is a bug but just a feature.
Unless you can show where it does not meet the servlet specs then it
will not be considered a bug.
Ok, and since the issue is actually documented, it cannot be called a
bug. Und
somewhere there
is someone who doesn't like it.
Doug
- Original Message -
From: "Thomas Corte" <[EMAIL PROTECTED]>
To: "Tomcat Users List"
Sent: Tuesday, August 30, 2005 4:28 PM
Subject: Re: "No Host matches server name localhost" error
Hi,
P
Hi,
Parsons Technical Services wrote:
Per the 5.5 doc you can't do it that way. You can only specify the path
as a blank string when the context element is in the server.xml.
To reiterate: so the only 2 ways to define the *default web app* for the
host are either
- to define the context in
Brian Moseley wrote:
i don't recall seeing any references to a ROOT.xml. i tried renaming my
context xml file to ROOT.xml (within conf/Catalina/localhost of course)
but it did not seem to have been processed (requests to / gave that same
400 error).
and gosh, what a misleading error message
Paul Austin wrote:
It seems that Tomcat 5.5 discourages you from putting contexts in the
server.xml, and that is something that is a good idea as it's easier to
manage them when they are outside. But the context path is only
supported when you put it in the server.xml so you can't deploy the war
> From: Paul Austin [mailto:[EMAIL PROTECTED]
> Subject: RE: "No Host matches server name localhost" error
>
> But the context path is only supported when you put it
> in the server.xml so you can't deploy the wars to any
> other path other than the name of th
On Tue, 2005-08-30 at 13:25 -0500, Caldarale, Charles R wrote:
> > From: Brian Moseley [mailto:[EMAIL PROTECTED]
> > Subject: Re: "No Host matches server name localhost" error
> >
> > thanks for the pointer. after moving my context definition into
>
> From: Brian Moseley [mailto:[EMAIL PROTECTED]
> Subject: Re: "No Host matches server name localhost" error
>
> thanks for the pointer. after moving my context definition into
> server.xml
Bad move. This is specifically discouraged in 5.5.
> i wonder what the
Parsons Technical Services wrote:
Per the 5.5 doc you can't do it that way. You can only specify the path
as a blank string when the context element is in the server.xml.
http://jakarta.apache.org/tomcat/tomcat-5.5-doc/config/context.html
Look at the path attribute.
aha! man, if only somebod
Per the 5.5 doc you can't do it that way. You can only specify the path as a
blank string when the context element is in the server.xml.
http://jakarta.apache.org/tomcat/tomcat-5.5-doc/config/context.html
Look at the path attribute.
Doug
- Original Message -
From: "Brian Moseley" <[
The error your getting is more likely saying that you computer can not
resolve localhost as domain name. If so it would have nothing to do
with your server config. Try using the loop back IP(127.0.0.1). If
this is happening on a windows box you may want to run a check for
viruses or spywa
Try renaming the context.xml to ROOT.xml, I normally get the 400 error
if it can't find the context for a particular path. For some reason
Tomcat tends to ignore the path on the context.
Paul
On Tue, 2005-08-30 at 09:50 -0700, Brian Moseley wrote:
> i'm using tomcat 5.5.9 with a single webapp de
12 matches
Mail list logo