generates the same error. Anyone know what's going on? I googled it and super searched it and the only other reports I saw with this error seem to involve LPW::UserAgent::Parallel, which I'm not using.use LWP::UserAgent; my $request_url = 'http://perlmonks.com'; my $user_agent = LWP::UserAgent->new; $user_agent->timeout(30); my $request = HTTP::Request->new('GET', $request_url); my $response = $user_agent->request($request);
TIA...
Steve
UPDATE
Eureka! All along I had been running the code in ActiveState Komodo IDE 4.0. I finally took to stepping though the code with its debugger. I narrowed the problem down to line 313 of http.pm, which leads to a socket read on line 232 of Methods.pm, which calls sub sysread in line 382 of http.pm. If I stepped through the code slowly it would return a valid read on perlmonks.com, but if I set breakpoints on line 313 and on sub sysread and hit continue to go between them, I would get the error. Since there seemed to be an interaction between debugger actions and the error, I tried it from the command line and it worked. I guess there was some kind of bad interaction between Komodo and the perl interpreter.
Why this error occurs for perlmonks but not google is a mystery to me, but there you have it. I am going to put in a bug report on Komod and go my merry way.
Thanks for all your suggestions.
Steve
In reply to LWP error 500 read timeout "internal response" by cormanaz
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |