Hi Mark, Thanks for the quick response. I think for me the intention that there is always a ROOT webapp wasn't clear to me. I'll ensure we have one in future.
Simon -----Original Message----- From: Mark Thomas [mailto:ma...@apache.org] Sent: 28 October 2009 14:08 To: Tomcat Users List Subject: Re: HTTP 400 not appearing in access log Simon MaticLangford wrote: > 2 questions come from this: > > - From a user perspective, I would expect to get a 404 Not Found. Is there a reason we get the bad request instead? Yes. You removed the ROOT web application. You need a ROOT webapp to handle requests that don't map to any other app. Could Tomcat detect this and return a 404 in this case? Maybe, but I haven't looked at the code and to be perfectly honest it is far simpler to just create an empty ROOT directory in the webapps dir. The intention is that there is always a ROOT web app so if you remove it, expect odd things to happen. > - Why does the 400 not go to the access log? Because without an application to map it to, the request gets rejected before it reaches the valve pipeline where the access log sits. Mark --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org ________________________________________________________________________ In order to protect our email recipients, Betfair Group use SkyScan from MessageLabs to scan all Incoming and Outgoing mail for viruses. ________________________________________________________________________ --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
