It's a slightly older version (0.96) so debug4 which I use is the most verbose option. From perldoc IO::Socket::SSL on the server in question;

use IO::Socket::SSL qw(debug3); #Print out progress, ciphers, and errors. use IO::Socket::SSL qw(debug4); #Print out everything, including data.

Just to humor you, here is the output from debug3:

SSL connect attempt failederror:14094418:SSL routines:SSL3_READ_BYTES: +tlsv1 alert unknown ca at biz_test.pl line 6 IO::Socket::INET configuration failed at biz_test.pl line 6 I encountered a problem: IO::Socket::INET configuration failed at biz_ +test.pl line 20. IO::Socket::SSL: Timeout ...caught at biz_test.pl line 23.

Confucius says kill mosquito unless cannon

In reply to Re^2: OpenSSL vs IO::Socket::SSL by marcussen
in thread OpenSSL vs IO::Socket::SSL by marcussen

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.