in reply to Re: Re: Mixing modules, LWP::UserAgent and Net::LDAPS not playing well together.
in thread Mixing modules, LWP::UserAgent and Net::LDAPS not playing well together.

It just dawned on me that all that $ENV{HTTPS_CERT_FILE} stuff is probably the root of your problems.

Check you Net::LDAPS documentation on passing this information through the constructor.

Also take a look at LWP::Protocol::https10.

# # $Id: https10.pm,v 1.1 2001/10/26 17:27:19 gisle Exp $ use strict; package LWP::Protocol::https10; # Figure out which SSL implementation to use use vars qw($SSL_CLASS); if ($IO::Socket::SSL::VERSION) { $SSL_CLASS = "IO::Socket::SSL"; # it was already loaded } else { eval { require Net::SSL; }; # from Crypt-SSLeay if ($@) { require IO::Socket::SSL; $SSL_CLASS = "IO::Socket::SSL"; } else { $SSL_CLASS = "Net::SSL"; } }
Examine $LWP::Protocol::https10::SSL_CLASS after creating a HTTPS request, before you request it or something, and make sure it points to Net::SSL

I don't know how significant, but the IO::Socket::SLL pod says

Currently, the IO::Socket::INET interface as implemented by this package is not quite complete. There can be only one SSL context at a given time.

____________________________________________________
** The Third rule of perl club is a statement of fact: pod is sexy.