On Fri, Sep 27, 2002 at 04:18:38PM -0500, Gilles Detillieux 
([EMAIL PROTECTED]) wrote:
> According to Amy Tanner:
> > I'm having difficult getting htdig-3.2.0-2.011302 to dig SSL sites.  I'm
> > running this version because it's the most recent RedHat RPM.  Here's
> 
> There have been fixes to SSL support in 3.2.0b4 since the Jan 13/02 snapshot.
> You may want to try the latest RPMs in http://www.htdig.org/files/binaries/

Thanks.  I tried htdig-3.2.0-3.20020922.  It appears to be failing
similarly:

# rundig -vvvv
ht://dig Start Time: Mon Sep 30 09:51:43 2002
        1:1:https://lists.ahpcrc.org/
New server: lists.ahpcrc.org, 443
 - Persistent connections: enabled
 - HEAD before GET: disabled
 - Timeout: 30
 - Connection space: 0
 - Max Documents: -1
 - TCP retries: 1
 - TCP wait time: 5
 - Accept-Language: 

Trying to retrieve robots.txt file
Making HTTP request on https://lists.ahpcrc.org/robots.txt
Header line: HTTP/1.1 400 Bad Request
Header line: Date: Mon, 30 Sep 2002 14:51:43 GMT
Header line: Server: Apache/1.3.22 (Unix)  (Red-Hat/Linux) mod_ssl/2.8.5
OpenSSL/0.9.6 mod_throttle/3.1.2
Header line: Connection: close
Header line: Content-Type: text/html; charset=iso-8859-1
No modification time returned: assuming now
Retrieving document /robots.txt on host: lists.ahpcrc.org:443
Http version      : HTTP/1.1
Server            : HTTP/1.1
Status Code       : 400
Reason            : Bad Request
Access Time       : Mon, 30 Sep 2002 14:51:43 GMT
Modification Time : Mon, 30 Sep 2002 14:51:43 GMT
Content-type      : text/html; charset=iso-8859-1
Connection        : close
Request time: 0 secs
 pushed
pick: lists.ahpcrc.org, # servers = 1
> lists.ahpcrc.org with a traditional HTTP connection
0:2:0:https://lists.ahpcrc.org/: Making HTTP request on
https://lists.ahpcrc.org/
Header line: HTTP/1.1 400 Bad Request
Header line: Date: Mon, 30 Sep 2002 14:51:43 GMT
Header line: Server: Apache/1.3.22 (Unix)  (Red-Hat/Linux) mod_ssl/2.8.5
OpenSSL/0.9.6 mod_throttle/3.1.2
Header line: Connection: close
Header line: Content-Type: text/html; charset=iso-8859-1
No modification time returned: assuming now
Retrieving document / on host: lists.ahpcrc.org:443
Http version      : HTTP/1.1
Server            : HTTP/1.1
Status Code       : 400
Reason            : Bad Request
Access Time       : Mon, 30 Sep 2002 14:51:43 GMT
Modification Time : Mon, 30 Sep 2002 14:51:43 GMT
Content-type      : text/html; charset=iso-8859-1
Connection        : close
Request time: 0 secs
 not found
pick: lists.ahpcrc.org, # servers = 1
> lists.ahpcrc.org with a traditional HTTP connection
ht://dig End Time: Mon Sep 30 09:51:43 2002
Deleted, not found: ID: 2 URL: https://lists.ahpcrc.org/


Preamble text:


Postamble text:
Note: This message will be sent again if you do not change or
take away the notification of the above mentioned HTML page.

Find out more about the notification service at

    http://www.htdig.org/meta.html

Cheers!

ht://Dig Notification Service


/usr/bin/rundig: line 81: 11071 Segmentation fault      /usr/bin/htfuzzy
$verbose metaphone
/usr/bin/rundig: line 82: 11072 Segmentation fault      /usr/bin/htfuzzy
$verbose soundex


I also still see this in the apache error logs:

[Mon Sep 30 09:51:43 2002] [error] mod_ssl: SSL handshake failed: HTTP spoken on HTTPS 
port; trying to send HTML error page (OpenSSL library error follows)
[Mon Sep 30 09:51:43 2002] [error] OpenSSL: error:1407609C:SSL 
routines:SSL23_GET_CLIENT_HELLO:http request [Hint: speaking HTTP to HTTPS port!?]
[Mon Sep 30 09:51:43 2002] [error] mod_ssl: SSL handshake failed: HTTP spoken on HTTPS 
port; trying to send HTML error page (OpenSSL library error follows)
[Mon Sep 30 09:51:43 2002] [error] OpenSSL: error:1407609C:SSL 
routines:SSL23_GET_CLIENT_HELLO:http request [Hint: speaking HTTP to HTTPS port!?]

I tried htdig-3.1.6-0.rh72:

# rundig -vvvv
        1:1:https://lists.ahpcrc.org/
New server: lists.ahpcrc.org, 80
Unable to build connection with lists.ahpcrc.org:80
 pushed
pick: lists.ahpcrc.org, # servers = 1
htmerge: Unable to open word list file '/var/lib/htdig/db.wordlist'.
  Did you index anything?
  Check your config file and try running htdig again.

Preamble text:


Postamble text:
Note: This message will be sent again if you do not change or
take away the notification of the above mentioned HTML page.

Find out more about the notification service at

    http://www.htdig.org/meta.html

Cheers!

ht://Dig Notification Service



And nothing shows up in the apache access or error logs.

Has anyone been able to get htdig's SSL support to work reliably?
Thanks.
-- 
Amy Tanner
[EMAIL PROTECTED]

Attachment: msg05912/pgp00000.pgp
Description: PGP signature

Reply via email to