Mailing List Archive

Using the Location field of the HTTP header makes sense since a 301 or 302 response must provide it.

One suggestion is that Nessus should also recognize 301 in no4040.nasl. My patch suggestion on March 4, 2003 would be an example.

-Art

--
Art Green V: +1-608-937-5226
Sr. Security Analyst
Lands' End, Inc.
1 Lands' End Lane
Dodgeville, WI 53595
Visit us on the web: http://www.landsend.com
--
-----Original Message-----
From: Michel Arboi [mailto:mikhail@nessus.org]
Sent: Wednesday, March 19, 2003 5:39 AM
To: nessus-devel@list.nessus.org
Subject: no404 and 302 (redirect)
What about this patch?

"Green, Art" <Art.Green@landsend.com> writes:

> One suggestion is that Nessus should also recognize 301 in
> no4040.nasl. My patch suggestion on March 4, 2003 would be an
> example.

I found your patch back (I usually lose data in my mailboxes :)

I think it is better to check the "Location" field rather than just the
30x code. With this, I hope we can make the difference between a
"real" redirect and a redirect to the standard "not found" error page.

Good point, I stand corrected! :) Thanks for pointing this out.

-Art
-----Original Message-----
From: Michel Arboi [mailto:mikhail@nessus.org]
Sent: Wednesday, March 19, 2003 12:32 PM
To: Green, Art
Cc: nessus-devel@list.nessus.org
Subject: Re: no404 and 302 (redirect)


"Green, Art" <Art.Green@landsend.com> writes:

> One suggestion is that Nessus should also recognize 301 in
> no4040.nasl. My patch suggestion on March 4, 2003 would be an
> example.

I found your patch back (I usually lose data in my mailboxes :)

I think it is better to check the "Location" field rather than just the
30x code. With this, I hope we can make the difference between a
"real" redirect and a redirect to the standard "not found" error page.