Hi, This is a single case, I saw others that weren't, i.e. they were misconfigured host that would return 500 for EVERY record requested. This should be handled quite easily in my opinion. Thanks Noam Rathaus http://www.BeyondSecurity.com http://www.SecuriTeam.com ----- Original Message ----- From: "Michael Scheidell" <scheidell@secnap.net> To: "Noam Rathaus" <noamr@beyondsecurity.com> Cc: "Nessus Mailing List" <nessus@list.nessus.org>; "Nessus Plugins Writers" <plugins-writers@list.nessus.org>; "Renaud Deraison" <deraison@cvs.nessus.org> Sent: Sunday, May 05, 2002 21:50 Subject: Re: no404 > > access to file parser cause it, file parser that capture all incoming > > request and handle them, i.e. even accessing /foobar will cause this error), > > 401 Unauthorized (Username required), 403 Forbidden (IP limited hosts), 500 > > Internal Server Error (Very similar to the one for bad request, usually due > > 500 errors are a TRUE positive for some of the IIS crap. > > -- > Michael Scheidell > SECNAP Network Security, LLC > (561) 368-9561 scheidell@secnap.net > http://www.secnap.net/ > >
This archive was generated by hypermail 2b30 : Sun May 05 2002 - 12:54:19 PDT