tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael Ludwig <mil...@gmx.de>
Subject Re: 400 error when a request does not map to a context
Date Tue, 25 Jan 2011 17:37:21 GMT
Christopher Schultz schrieb am 25.01.2011 um 11:48 (-0500):
> 
> Should I expect that a request that doesn't map to a running context
> should return a 400 error? I would have expected a 404 Not Found.

Definitely 404, as long as it isn't a "bad request".

> Tomcat 6.0.29 and Tomcat 7.0.6 both behave this way.
> 
> With no ROOT context deployed, make a request to something that
> doesn't map to a deployed webapp, like "/nocontext" or even "/" and
> you'll get a 400 Bad Request.
> 
> HTTP Spec says 400 means "The request could not be understood by the
> server due to malformed syntax" but the request is perfectly valid.

-- 
Michael Ludwig

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


Mime
View raw message