According to Patrick:
> I don't think that htdig is following the Location of the 30x redirect
> headers properly. The IIS server I'm trying to spider sends headers like
> this (in htdig output format)
>
> Header line: HTTP/1.1 302 Object moved
> Header line: Server: Microsoft-IIS/4.0
> Header line: Date: Thu, 20 Jul 2000 15:56:45 GMT
> Header line: Location: testdir.ASP?page=15
> Header line: Connection: Keep-Alive
> Header line: Content-Length: 140
> Header line: Content-Type: text/html
> Header line: Cache-control: private
> Header line:
> returnStatus = 3
> redirect
> redirect:
>
> Rejected: Not an http or relative link!pick: , # servers = 2
>
> The Location does not contain "http://www.foo.om/" -- but, it should
> still be treated as a relative link by htdig, shouldn't it?
The Location header above is technically invalid, as it contains a
relative URI. The specification calls for an absolute URI. See Andrew's
message about a similar problem a few months ago:
http://www.htdig.org/mail/2000/04/0023.html
If the redirect is generated by a CGI script, you should fix that script
to conform to the spec. If your IIS server is generating the redirect
itself, then it is buggy. (A buggy MS product? Gasp! Say it ain't so! :-)
The latest beta release, 3.2.0b2, allows redirects to relative URIs,
just because this appears to be an increasingly common problem, but if
you can fix the problem at the source that would be preferable.
--
Gilles R. Detillieux E-mail: <[EMAIL PROTECTED]>
Spinal Cord Research Centre WWW: http://www.scrc.umanitoba.ca/~grdetil
Dept. Physiology, U. of Manitoba Phone: (204)789-3766
Winnipeg, MB R3E 3J7 (Canada) Fax: (204)789-3930
------------------------------------
To unsubscribe from the htdig3-dev mailing list, send a message to
[EMAIL PROTECTED]
You will receive a message to confirm this.
