Re: web server identification

2001-12-03 Thread Greg McCarroll
* [EMAIL PROTECTED] ([EMAIL PROTECTED]) wrote: > On Mon, Dec 03, 2001 at 06:15:54PM -, Andrew Bowman wrote: > > From: <[EMAIL PROTECTED]> > > > I reckon it ought to be fairly easy to identify a web server based > > > on error messages and details of responses. > > > Is there any software out t

Re: web server identification

2001-12-03 Thread Chris Devers
On 3 Dec 2001, Steve Mynott wrote: > Obvious things are is the response 200 or 404 for requests for > default.htm or index.html? We're going in circles here, but if it's up to me, I like to tell Apache to map all .htm files to .html, and in the case of home pages I redirect requests for default.

Re: web server identification

2001-12-03 Thread Steve Mynott
[EMAIL PROTECTED] writes: > I'm thinking of more or less the same functionality as (iirc) queso, > which will guess a machine's OS from looking at responses to various > interesting network packets. There are only a few web servers in common use (Apache, IIS and iPlanet (formerly Netscape) and Z

Re: web server identification

2001-12-03 Thread the hatter
On Mon, 3 Dec 2001 [EMAIL PROTECTED] wrote: > I'm thinking of more or less the same functionality as (iirc) queso, > which will guess a machine's OS from looking at responses to various > interesting network packets. I'd think that, even if they change/remove the Server: header that the other in

Re: web server identification

2001-12-03 Thread Andrew Bowman
From: <[EMAIL PROTECTED]> > I reckon it ought to be fairly easy to identify a web server based > on error messages and details of responses. > > Is there any software out there that already does this, or evidence > as to why it would be impractical? Depends what you're trying to achieve - is ther

Re: web server identification

2001-12-03 Thread Chris Devers
On Mon, 3 Dec 2001, David Cantrell wrote: > On Mon, Dec 03, 2001 at 04:38:04PM +, [EMAIL PROTECTED] wrote: > > I reckon it ought to be fairly easy to identify a web server based > > on error messages and details of responses. > > > > Is there any software out there that already does this, or

Re: web server identification

2001-12-03 Thread Leon Brocard
[EMAIL PROTECTED] sent the following bits through the ether: > That doesn't actually *say*, but it sounds like it just uses the > Server: header to work out what web server you're running. It does. I never got around to releasing the module when I was working there. Anyway, I was *convinced* th

Re: web server identification

2001-12-03 Thread David Cantrell
On Mon, Dec 03, 2001 at 04:38:04PM +, [EMAIL PROTECTED] wrote: > I reckon it ought to be fairly easy to identify a web server based > on error messages and details of responses. > > Is there any software out there that already does this, or evidence > as to why it would be impractical? It's

Re: web server identification

2001-12-03 Thread Chris Devers
On Mon, 3 Dec 2001 [EMAIL PROTECTED] wrote: > I reckon it ought to be fairly easy to identify a web server based > on error messages and details of responses. But that sort of thing can be munged. Can you query $ENV{server_software}? Even if you could, that can me munged too. > Is there any s

Re: web server identification

2001-12-03 Thread Chris Ball
On Mon, Dec 03, 2001 at 04:38:04PM +, [EMAIL PROTECTED] wrote: > I reckon it ought to be fairly easy to identify a web server based > on error messages and details of responses. It is. That, and it usually tells you. > Is there any software out there that already does this, or evidence > as