On 26 Jan 2011, at 23:23, Christopher Schultz
ch...@christopherschultz.net wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Konstantin,
On 1/26/2011 10:55 AM, Konstantin Kolinko wrote:
2011/1/25 Christopher Schultz ch...@christopherschultz.net:
Should I expect that a request that
From: Pid [mailto:p...@pidster.com]
Subject: Re: 400 error when a request does not map to a context
There was a list discussion about this recently, which I thought
led to a BZ, but I can't see it now.
You might be thinking of this one:
2011/1/25 Christopher Schultz ch...@christopherschultz.net:
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.
Tomcat 6.0.29 and Tomcat 7.0.6 both behave this way.
With no ROOT context deployed, make a
Konstantin Kolinko wrote:
2011/1/25 Christopher Schultz ch...@christopherschultz.net:
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.
Tomcat 6.0.29 and Tomcat 7.0.6 both behave this way.
With no ROOT
2011/1/26 André Warnier a...@ice-sa.com:
By the way, having had my curiosity triggered by what Chris was reporting, I
scanned the Servlet Spec 3.0 for mentions of the ROOT (default) context,
and could not really find much of relevance.
Namely, it does not mention that one is required. Is it ?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Konstantin,
On 1/26/2011 10:55 AM, Konstantin Kolinko wrote:
2011/1/25 Christopher Schultz ch...@christopherschultz.net:
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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
All,
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.
Tomcat 6.0.29 and Tomcat 7.0.6 both behave this way.
With no ROOT context deployed, make a request to
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
On 1/25/11 5:37 PM, Michael Ludwig wrote:
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.
