Re^2: LWP 500 Internal response read timeout

I modified LWP code to print out "timeoutt" just ensure it's coming from LWP. And yes the "transfer-encoding" is "chunked". Again, the timeout message is not from target server.

Comment on Re^2: LWP 500 Internal response read timeout

Replies are listed 'Best First'.
Re^3: LWP 500 Internal response read timeout by derby (Abbot) on Jun 13, 2013 at 09:57 UTC
There were some issues with certain version of Net::HTTP and chunked responses. -derby	[reply]
Re^4: LWP 500 Internal response read timeout by vhn2000 (Initiate) on Jun 13, 2013 at 18:03 UTC
OK, so do you have any workaround or link or something to resolve this?	[reply]
Re^4: LWP 500 Internal response read timeout by vhn2000 (Initiate) on Jun 13, 2013 at 18:48 UTC
I updated LWP::UserAgent, Net::HTTP to the latest: perl -MNet::HTTP -e 'print "$Net::HTTP::VERSION\n"' 6.06 The timeout issue is still there.	[reply]