At 12:47 PM +0200 8/7/01, Torsten Neuer wrote:
>I think this is related to the non-standard port of the server in
>question here (8080). AFAIK, Ht://Dig does not honour non-standard
>ports but instead will fall back to the standard HTTP port 80.
That would be a *very* old bug that came back from the grave in that
case. AFAIK, it's been dead for a very long time:
Wed Sep 1 15:39:41 1999 Gilles Detillieux <[EMAIL PROTECTED]>
...
* htlib/URL.cc(parse): Fix PR#348, to make sure a missing
or invalid port number will get set correctly.
>(correctly) detected that "http://agheli:8080/"; /= "http://agheli/";,
>so that any other (probably relative) URLs which the index page refers
>to are skipped.
Since we don't have the HTML of the pages in question, it's hard to
know whether the URLs are relative or whether they fail to include
the port number.
If someone can show me that the URL parser in 3.1.5 or 3.2.0b3 (or
newer snapshots) lop off port numbers when supplied, I'll eat my
words. But I think I'd need to see some HTML...
--
--
-Geoff Hutchison
Williams Students Online
http://wso.williams.edu/
_______________________________________________
htdig-general mailing list <[EMAIL PROTECTED]>
To unsubscribe, send a message to <[EMAIL PROTECTED]> with a
subject of unsubscribe
FAQ: http://htdig.sourceforge.net/FAQ.html
