Thanks for your quick reply Derby. The script does use LWP::UserAgent. Here is my stripped down test script:
use CGI qw/:standard/;
use CGI::Carp (fatalsToBrowser);
require LWP::UserAgent;
print header;
my $ua = LWP::UserAgent->new;
my $url = 'http://google.com';
my $response = $ua->get($url);
if ($response->is_success) {
print $response->decoded_content; # or whatever
}
else {
die "failed: $url : ", $response->status_line;
}
So, it's dying w/ Status code 500. The server logs don't say much: "GET /scripts/prince/lwp_test.plx - 200 Mozilla/5.0+(compatible;+MSIE+10.0;+Windows+NT+6.1;+WOW64;+Trident/6.0;+EIE10;ENUSWOL)"
I have run this script on two different servers, after the Perl upgrade on both, and I get the same error message.
| [reply] [Watch: Dir/Any] [d/l] |
Is it really throwing the error with the google url or was that just a change for posting? What happens if you run the
above script from the command line? Do you still get the 500? The 500 error *should* be from the server the
url points to and I have a hard time believing google is throwing a 500.
The only *recent* LWP upgrade issue that I can think of is the SSL validity check on https -- but that would throw an entirely different error I believe.
| [reply] [Watch: Dir/Any] |
The only *recent* LWP upgrade issue that I can think of is the SSL validity check on https
After this (after 6.x) there were updates related to socket stuff.
| [reply] [Watch: Dir/Any] |
print $response->dump;
(in case of failure) and paste output here? | [reply] [Watch: Dir/Any] [d/l] |
LWP can return fake HTTP 500 responses together with header Client-Warning => Internal Response. This means some internal error.
| [reply] [Watch: Dir/Any] |
| [reply] [Watch: Dir/Any] |