Re^5: HTTP error response code 500 using LWP::UserAgent on one site, but not on any other

[Anonymous Monk]

use IO::Socket::SSL qw(debug3);

Also, http://search.cpan.org/perldoc/Crypt::SSLeay#SSL_diagnostics_and_Debugging lists $ENV{HTTPS_DEBUG} = 1;

[ted.byers]

Thanks. That was helpful. But it raises a couple puzzles.

1) I get the following output:

DEBUG: .../IO/Socket/SSL.pm:1645: new ctx 45510240
DEBUG: .../IO/Socket/SSL.pm:363: socket not yet connected
DEBUG: .../IO/Socket/SSL.pm:365: socket connected
DEBUG: .../IO/Socket/SSL.pm:383: ssl handshake not started
DEBUG: .../IO/Socket/SSL.pm:446: Net::SSLeay::connect -> -1
DEBUG: .../IO/Socket/SSL.pm:1320: SSL connect attempt failed with unkn
+own error error:00000000:lib(0):func(0):reason(0)

DEBUG: .../IO/Socket/SSL.pm:452: fatal SSL error: SSL connect attempt 
+failed with unknown error error:00000000:lib(0):func(0):reason(0)
DEBUG: .../IO/Socket/SSL.pm:1320: IO::Socket::INET configuration faile
+d error:00000000:lib(0):func(0):reason(0)

DEBUG: .../IO/Socket/SSL.pm:1682: free ctx 45510240 open=45510240
DEBUG: .../IO/Socket/SSL.pm:1690: OK free ctx 45510240

How do I determine why this low level library is unable to complete the usual SSL hand-shaking only with this server (It succeeds with every other server I have tried)

2) The cdirective fails on my workstation, on which the IO::Socket::SSL package is not installed. But, while the version of Perl on the servers is 5.14 or later, that on my workstation is 5.12. What would LWP be using for SSL on my workstation? I suspect some subtle difference between what was used with Perl 5.12 and that used with 5.14 or 5.16 may be responsible for the observed difference in behaviour. How would I determine this (and get similar debug information on my workstation that I am now getting on the two servers?

Thanks

Ted

[Anonymous Monk]

Don't know, don't care, I go out of my way not to :) see Re: Long delay with Crypt::SSLeay and LWP and Debugging SSL communications