http://qs321.pair.com?node_id=1106018


in reply to Re: 500 error with LWP:UserAgent
in thread 500 error with LWP:UserAgent

Hi there,

I tried your modification and it didnt change my case.

I use
perl v5.14.2
LWP::UserAgent v6.06
HTTP::Request v6.00
IO::Socket::SSL 1.955

Adding 
use Net::SSLeay;
$Net::SSLeay::trace = 2;

[download]

as suggested on stackoverflow : http://stackoverflow.com/questions/26732578/500-error-with-lwpuseragent produced the output
DEBUG: .../IO/Socket/SSL.pm:449: socket not yet connected
DEBUG: .../IO/Socket/SSL.pm:451: socket connected
DEBUG: .../IO/Socket/SSL.pm:469: ssl handshake not started
DEBUG: .../IO/Socket/SSL.pm:504: using SNI with hostname sis-t.redsys.
+es
DEBUG: .../IO/Socket/SSL.pm:527: set socket to non-blocking to enforce
+ timeout=10
DEBUG: .../IO/Socket/SSL.pm:550: ssl handshake in progress
DEBUG: .../IO/Socket/SSL.pm:560: waiting for fd to become ready: SSL w
+ants a read first
DEBUG: .../IO/Socket/SSL.pm:570: handshake failed because socket did n
+ot became ready
Error: 500 Can't connect to sis-t.redsys.es:25443

[download]

Replies are listed 'Best First'.
Re^3: 500 error with LWP:UserAgent
by Loops (Curate) on Nov 04, 2014 at 13:47 UTC

    Well it's a puzzle for sure. I installed Perl and those modules with the same version you have, and it just worked with the updated code. The old code gave the same Net::SSLeay debug output as yours. There is some underlying difference between our setups obviously.

    There's a chance that changing the SSL version to this would help:

    SSL_version => 'TLSv1:!TLSv11:!TLSv12:!SSLv2:!SSLv3'

    [download]

    The last two components are supposedly redundant. But in any case, that long version string wasn't needed here (with any of 3 machines).

    Update: Just as a debugging step, try adding random garbage to the string you pass into SSL_version. You should expect the following error, otherwise something is up in Denmark:

    Error: 500 invalid SSL_version specified

    [download]
[reply]
[d/l]
[select]
      May i ask for your perl -MIO::Socket::SSL -e 'print "$IO::Socket::SSL::VERSION\n"' version please ?

      I just was able to test on a machine with
      perl 5.14.2
      LWP:User::Agent 6.04
      IO::Socket::SSL 1.76
      Net::SSLeay 1.48 (while mine is 1.55)
      and it just worked fine (exact same code, I scp-ed it)
[reply]

        Well I configured one machine as yours to test:

      • LWP::UserAgent : 6.06
      • IO::Socket::SSL : 1.955
      • Net::SSLeay : 1.66

        • Just retried with SSLeay @ 1.55, still works fine.

        This is all testing with Perl 5.14.2 to stay as close to yours as possible. However, it may well be the underlying OpenSSL version. All the machines here are Fedora 20 boxen.. with:

        openssl-1.0.1e-40.fc20.x86_64

        Would be interesting to see if your two machines have separate versions. By the way, on the machine that works for you, maybe give it a go with and without the SSL_version parameter.

[reply]
      One good news, one bad.

      Good news is we dont need to disturb Denmark government, i achieved the 500 invalid SSL_version specified with SSL_version='Garbage'

      Bad news is changing the SSL_version doesnt solve my problem at all.

      Could it be due to perl version ? (I cant change mine here :/)
[reply]

In Section Seekers of Perl Wisdom