LWP - timeout

[agoth]

Am I misunderstanding the $ua->timeout() method of LWP UserAgent? the www.richard.com in the list doesnt return but doesnt timeout either even if set to 10 seconds.
Is there a way to stop this, short of terminating the request myself??

use LWP::UserAgent;
my $ua = LWP::UserAgent->new;

print "Timeout : ", $ua->timeout, "\n";
$ua->timeout(10);
print "Timeout : ", $ua->timeout, "\n";

my %urls = ('http://www.hotmail.com', '',
            'http://www.richard.com', '',
            'http://www.slashdot.org', '',
            'http://doesnt.exist.com/', '',
            'http://www-uk.cricket.org/', '');

are_live(keys %urls);

sub are_live {
    for (@_) {
        $ua->timeout('5');
        my $res = $ua->request(HTTP::Request->new(GET => $_));
        $urls{$_} = ($res->is_success) ? "OK" : "NOT OK";
    }
}

for (keys %urls) {
    print "URL : $_ : $urls{$_} \n";
}

[arhuman]

It seems I had a similar problem...
The fact is that if the host is unreachable, the timeout doesn't seems to work...
Or maybe the time out is only used once the TCP connections is done...
You could try to test if host is reachable before connecting or set your sig handler to control the time out 'by-hand' (something like (courtesy of axion on QuestionExchange) :


#!/usr/local/bin/perl -w

use strict;
use IO::Socket;

{
  my $timeout = 0;
  my $sock = undef;

  $SIG{ALRM} = sub {$timeout = 1; die};

  eval {
      alarm (2);
       $sock = new IO::Socket::INET (PeerAddr => '10.1.1.18',
                                                             PeerPort 
+=> 29,
);
      alarm (0);
                  };

 die "Can't open socket: timeout=$timeout\n" if ($timeout or !$sock);

 print "I would print to the socket now, if I knew what I was connecte
+d
to\n";

 close ($sock);
          }

) Or even modify the LWP Timeout method...

[Rune]

It seems that www.richard.com is not properly configured and doesn't resolve. The $ua->timeout() probably doesn't take account for DNS timeouts and AFAIR, doesn't have any options specifically for this.

It seems to me that you'll have to live with the long timeout or perform a lookup seperately before the actual HTTP request. I'm pretty sure that there's a DNS module on CPAN that provides more control over the DNS query than LWP does.

[dws]

You don't mention what platform you're running on. If you're on Win32, you may be SOL. Under the covers, LWP uses SIGALRM (in IO::Socket) for timeouts. Unfortunately, signals aren't supported on Win32.

See the "Quicks" page in the ActiveState FAQ for details.

(If someone knows otherwise, please set me straight. I've never been able to get timeouts working with LPW on Win32, but perhaps there's some trick.)

[MeowChow]

The IO::Socket modules use the timeout feature built into the select() system call to do timeouts when recving or sending data; however, in order to do a connect, they attempt to set the socket to non-blocking mode (which does not work properly without some cajoling on Win32 systems).

For this reason, if you cannot actually connect to your peer's http port, a Win32 timeout on an LWP call will not work. If, however, you can connect to the peer's listening socket, then the timeout should work.

[agoth]

Mercifully I'm on Solaris and occasionally FreeBSD,
I know IO::Socket is installed, but i suspect the reason is as above.