Thanks for the advice. Since HTTPS is encrypted and the LWP's source is at hand, I just let LWP print out (uncomment one line, really) the HTTP header it's sending, and the culprit turns out to be the Transfer-Encoding (TE) header. I'll be bugging Gisle Aas again to give LWP the option of not sending TE header.
In reply to Re^4: Investigating connection reset with LWP to an https site (packets)
by sedusedan
in thread Investigating connection reset with LWP to an https site
by sedusedan
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |