I just wanted to confirm (due to paranoia) that this problem is still outstanding as identified in https://rt.cpan.org/Public/Bug/Display.html?id=67001
I modified that test apache.t in LWP::Protocol::https as follows:
diff t/apache.t t/apache-jim.t 13c13 < my $res = $ua->simple_request(HTTP::Request->new(GET => "https://www +.apache.org")); --- > my $res = $ua->simple_request(HTTP::Request->new(GET => "https://www +.bankofamerica.com")); 18c18 < like($res->content, qr/Apache Software Foundation/); --- > like($res->content, qr/Bank of America/);
And I got success:
$ prove --blib t/apache-jim.t t/apache-jim.t .. ok All tests successful. Files=1, Tests=5, 3 wallclock secs ( 0.04 usr 0.01 sys + 0.25 cusr + 0.04 csys = 0.34 CPU) Result: PASS
I see that the bug is still outstanding, but I am nervous that the Apache Foundation cert query is still not fixed and/or the test has not been updated to something more reasonable.
So - again feel pretty good. Just wanted another opinion from the Monks.
JIM
In reply to Re^5: Can't install LWP::Protocol::https::Socket
by jimhallsun
in thread Can't install LWP::Protocol::https::Socket
by Dillman
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |