-----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 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. - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk0+/uAACgkQ9CaO5/Lv0PDTGgCdGsI9IKkZapKQarJQPlHMUp65 TlEAnRaRJwLLHnIfZwbn32W3p1/SgQAg =h+lx -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
