On Apr 3, 2007, at 12:46 PM, Joe Auty wrote: > Could this problem be with my using a self-signed certificate?
To the best of my knowledge a self-signed certificate shouldn't be a problem. I don't recall anyone ever reporting that as an issue, and I do seem to recall at least one person stating that they tested with a self-signed certificate (don't remember what version of ht://Dig). Sorry that I can't provide a more certain answer. If you have access to the server logs you might want to check those. In short what appears to be happening is that htdig makes a request for robots.txt, goes to the connection to look for a response, and times out before it sees one. It tries waiting on the response three times and then bails. The most obvious causes are that the connection is going away from some reason, the server is not sending a response, or htdig is for some reason unable to see the response. The patch corrected one case where the latter could occur. Is there any possibility that a firewall might be blocking the response? Have you tried accessing the site with a regular browser from the machine running htdig? Jim ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ ht://Dig general mailing list: <[email protected]> ht://Dig FAQ: http://htdig.sourceforge.net/FAQ.html List information (subscribe/unsubscribe, etc.) https://lists.sourceforge.net/lists/listinfo/htdig-general
