Hi Marko,
Summary:
- IO::Socket::SSL has problems with broken connections
- Crypt::SSL (0.17, includes Net::SSL) still has a memory leak
- Net::SSLeay::get_https works fine
(with own eval()/die() timeout wrapper)
> you mentioned having both Crypt-SSLeay and IO-Socket-SSL in your
> environment. LWP uses only _one_ of these modules for SSL/TLS support if
> both are installed. Crypt-SSLeay is the default one.
>
Err - that one was on me; I checked LWP::Protocols::https.pm
and saw firt IO-Socket-SSL and then Net-SSL but didn't lock
as close to the logic :-(
Anyway, there is a problem with ***IO-Socket-SSL*** too:
When using LWP::UserAgent connecting to a non-reachable Server
I get the reply (which is correct):
500 (Internal Server Error) Can't connect to 195.126.111.144:443 (Operation now in
progress)
Client-Date: Sat, 09 Sep 2000 19:53:48 GMT
But when I then do further connects to other servers:
500 (Internal Server Error) Can't connect to service.de.uu.net:443 ()
Client-Date: Sat, 09 Sep 2000 19:53:48 GMT
Do I use ***Crype::SSL (Net::SSL)*** (which has since 0.17
a much smaller, but still a memory leak):
500 (Internal Server Error) Connect failed: Operation now in progress
Client-Date: Sat, 09 Sep 2000 19:55:14 GMT
Further connects (other SSL servers)
HTTP/1.1 200 OK
Connection: close
[...]
Meanwhile I'm using plain get_https (from Net::SSLeay) which
my own eval/die() wrapper to handle timeouts I don't have
such problems at all. But I can't use the LWP stuff here :-(
Jan
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
