You can analyze and analyze and guess, and add print statements and tweak and repeat this over and over and over again.

But at a certain point, we really really need to break out the debugger.

Get into the debugger, and trace it ALL the way down. Down into LWP, into the HTTPS networking code. You really need to just burrow down into the guts, looking at the contents of the variables as you go.

And go as deep as it takes to find the _exact_ place at which it fails.

Speculation and guessing can only go so far, before you need to break out the debugger. And it sounds like you are there.

In reply to Re: www::mechanize submit _form silent fail by adamk
in thread www::mechanize submit _form silent fail by mujiburger

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.