Skip Menu |

This queue is for tickets about the perl-ldap CPAN distribution.

Report information
The Basics
Id: 2018
Status: resolved
Priority: 0/
Queue: perl-ldap

People
Owner: Nobody in particular
Requestors: mah [...] everybody.org
Cc:
AdminCc:

Bug Information
Severity: Normal
Broken in: 0.26
Fixed in: (no value)



Subject: Loading Net::LDAPS munges https retrieval
Attached file shows a simple demonstration that https urls fail after "Net::LDAPS" is loaded.
#!/usr/bin/perl #tmp.pl: use LWP::Debug; use LWP::Simple; use Net::LDAP; LWP::Debug::level("+"); get("https://login.yahoo.com/config/login?.src=ym"); __END__ $ perl tmp.pl LWP::UserAgent::new: () LWP::UserAgent::request: () LWP::UserAgent::send_request: GET https://login.yahoo.com/config/login?.src=ym LWP::UserAgent::_need_proxy: Not proxied LWP::Protocol::http::request: () LWP::Protocol::collect: read 631 bytes LWP::Protocol::collect: read 4096 bytes LWP::Protocol::collect: read 4096 bytes LWP::Protocol::collect: read 4096 bytes LWP::Protocol::collect: read 1784 bytes LWP::UserAgent::request: Simple response: OK # Change "Net::LDAP" to "Net::LDAPS"; ~/work/nichework.com/bin $ perl tmp.pl LWP::UserAgent::new: () LWP::UserAgent::request: () LWP::UserAgent::send_request: GET https://login.yahoo.com/config/login?.src=ym LWP::UserAgent::_need_proxy: Not proxied LWP::Protocol::http::request: () LWP::UserAgent::request: Simple response: Internal Server Error $ uname -a Linux superman 2.4.18-686xfs-smp #1 SMP Thu Sep 19 21:10:19 CDT 2002 i686 Pentium III (Coppermine) GenuineIntel GNU/Linux $ perl -MNet::LDAP -e "print $Net::LDAP::VERSION"; 0.26 $ perl -MNet::LDAPS -e "print $Net::LDAPS::VERSION"; 0.04
[MAHEX - Sat Feb 1 15:24:15 2003]: Show quoted text
> Attached file shows a simple demonstration that https urls fail after > "Net::LDAPS" is loaded.
I cannot see that this is a bug with Net::LDAPS. LWP must be sensetive to the order of modules loaded or something. The only difference between loading Net::LDAP and Net::LDAPS is that Net::LDAPS does a use IO::Socket::SSL. Do you have the same problem if you change Net::LDAPS to IO::Socket::SSL ?