Skip Menu |

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

Report information
The Basics
Id: 37637
Status: resolved
Priority: 0/
Queue: libwww-perl

People
Owner: Nobody in particular
Requestors: davecortesi [...] gmail.com
Cc:
AdminCc:

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



Subject: https.t always fails, requires force install LWP
Date: Sat, 12 Jul 2008 09:20:47 -0700
To: bug-libwww-perl [...] rt.cpan.org
From: "David Cortesi" <davecortesi [...] gmail.com>
Trying to install Bundle::LWP the test case https.t fails, making it necessary to use force install. The test case accesses https://www.sun.com and looks for "Sun Microsystems" in the returned data. Access by browser to that URL succeeds, as does the command curl 'https://www.sun.com' | grep Microsystems We do note that sun appears to redirect to 'https://www.sun.com/' (adding a terminal slash), could this be the cause of the failure?
On Sat Jul 12 12:21:08 2008, davecortesi@gmail.com wrote: Show quoted text
> Trying to install Bundle::LWP the test case https.t fails, making it > necessary to use force install. > > The test case accesses https://www.sun.com and looks for "Sun
Microsystems" Show quoted text
> in the returned data. > > Access by browser to that URL succeeds, as does the command > > curl 'https://www.sun.com' | grep Microsystems > > We do note that sun appears to redirect to 'https://www.sun.com/'
(adding a Show quoted text
> terminal slash), > could this be the cause of the failure?
With 5.816 I see the error, too. The error goes away if I install Crypt::SSLeay before. So probably the detection if SSL is available is broken. Regards, Slaven
I see the problem here too with recent versions of ActivePerl if I hide the Crypt::SSLeay module. To me it looks like a perl problem where exceptions are not propagated as they should. What version of perl you using?
On Wed Oct 01 07:37:28 2008, GAAS wrote: Show quoted text
> To me it looks like a perl problem where exceptions are not propagated > as they should. > > What version of perl you using?
Forget about that. I was only confusing myself. The problem was a stray "my" in LWP::UserAgent.
Fixed by http://gitorious.org/projects/libwww- perl/repos/mainline/commits/fc6b60aa1f4355fe144b20d8b7179e3ac7fe3287 Detection of unsupported schemes was broken [RT#37637] We used to return the response from this block; but with the reorg in 5.815 we no longer do and the "my" prevents us from updating the outer $response. diff --git a/lib/LWP/UserAgent.pm b/lib/LWP/UserAgent.pm index 8678954..9c0e487 100644 --- a/lib/LWP/UserAgent.pm +++ b/lib/LWP/UserAgent.pm @@ -165,7 +165,7 @@ sub send_request $protocol = eval { LWP::Protocol::create($scheme, $self) }; if ($@) { $@ =~ s/ at .* line \d+.*//s; # remove file/line number - my $response = _new_response($request, &HTTP::Status::RC_NOT_IMPLEMENTED, $@); + $response = _new_response($request, &HTTP::Status::RC_NOT_IMPLEMENTED, $@); if ($scheme eq "https") { $response->message($response->message . " (Crypt::SSLeay not installed)"); $response->content_type("text/plain");