Re: LWP 500 read timeout

"Client-Warning: Internal response" indicates that LWP generated the error, rather than the server, and "500 read timeout" indicates that the HTTP request timed out on the client side. Try increasing the timeout, eg with $ua->timeout($seconds). The default appears to be 180.

Comment on Re: LWP 500 read timeout Download Code

Replies are listed 'Best First'.
Re^2: LWP 500 read timeout by Anonymous Monk on Jun 16, 2010 at 09:09 UTC
Increased the timeout to 1000s and tried. It still didn't work. Since curl and wget work, maybe it isn't a server side problem. Can it be a problem related to headers not being allowed,etc? Can I remove such default headers? Thanks, Bharat.	[reply]
Re^3: LWP 500 read timeout by Anonymous Monk on Jun 16, 2010 at 09:42 UTC
Can it be a problem related to headers not being allowed,etc? Can I remove such default headers? It could be firewall, proxy, or anything. Check. Get WireShark/Ethereal and compare	[reply]