Tried this one and it's not verbose enough to verify that the certificate is loaded/sent. This was at the debug set to 4. 

DEBUG: .../IO/Socket/SSL.pm:2649: new ctx 47286544
DEBUG: .../IO/Socket/SSL.pm:562: socket not yet connected
DEBUG: .../IO/Socket/SSL.pm:564: socket connected
DEBUG: .../IO/Socket/SSL.pm:586: ssl handshake not started
DEBUG: .../IO/Socket/SSL.pm:619: using SNI with hostname OMIT
DEBUG: .../IO/Socket/SSL.pm:654: request OCSP stapling
DEBUG: .../IO/Socket/SSL.pm:673: set socket to non-blocking to enforce
+ timeout=180
DEBUG: .../IO/Socket/SSL.pm:686: call Net::SSLeay::connect
DEBUG: .../IO/Socket/SSL.pm:689: done Net::SSLeay::connect -> -1
DEBUG: .../IO/Socket/SSL.pm:699: ssl handshake in progress
DEBUG: .../IO/Socket/SSL.pm:709: waiting for fd to become ready: SSL w
+ants a read first
DEBUG: .../IO/Socket/SSL.pm:729: socket ready, retrying connect
DEBUG: .../IO/Socket/SSL.pm:686: call Net::SSLeay::connect
DEBUG: .../IO/Socket/SSL.pm:2552: did not get stapled OCSP response
DEBUG: .../IO/Socket/SSL.pm:2505: ok=1 cert=52520624
DEBUG: .../IO/Socket/SSL.pm:2505: ok=1 cert=52517456
DEBUG: .../IO/Socket/SSL.pm:2505: ok=1 cert=53422432
DEBUG: .../IO/Socket/SSL.pm:1594: scheme=www cert=53422432
DEBUG: .../IO/Socket/SSL.pm:1604: identity=OMIT cn=OMIT alt=2 OMIT
DEBUG: .../IO/Socket/SSL.pm:689: done Net::SSLeay::connect -> -1
DEBUG: .../IO/Socket/SSL.pm:699: ssl handshake in progress
DEBUG: .../IO/Socket/SSL.pm:709: waiting for fd to become ready: SSL w
+ants a read first
DEBUG: .../IO/Socket/SSL.pm:729: socket ready, retrying connect
DEBUG: .../IO/Socket/SSL.pm:686: call Net::SSLeay::connect
DEBUG: .../IO/Socket/SSL.pm:689: done Net::SSLeay::connect -> 1
DEBUG: .../IO/Socket/SSL.pm:744: ssl handshake done
DEBUG: .../IO/Socket/SSL.pm:2552: did not get stapled OCSP response
DEBUG: .../IO/Socket/SSL.pm:2505: ok=1 cert=52520624
DEBUG: .../IO/Socket/SSL.pm:2505: ok=1 cert=52517456
DEBUG: .../IO/Socket/SSL.pm:2505: ok=1 cert=53426480
DEBUG: .../IO/Socket/SSL.pm:1594: scheme=www cert=53426480
DEBUG: .../IO/Socket/SSL.pm:1604: identity=OMIT cn=OMIT alt=2 OMIT
DEBUG: .../IO/Socket/SSL.pm:2682: free ctx 47286544 open=47286544
DEBUG: .../IO/Socket/SSL.pm:2687: free ctx 47286544 callback
DEBUG: .../IO/Socket/SSL.pm:2694: OK free ctx 47286544
Error: 403 Forbidden

[download]

In reply to Re^2: Issue with LWP loading client certificate by ffrost
in thread Issue with LWP loading client certificate by ffrost

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.