Michael Thompson <[EMAIL PROTECTED]> writes:
> Yes, I encountered that error, too. I traced the problem
> to _new_socket() in LWP::Protocol::http11 which was putting
> the socket in non-blocking mode. This would sometimes cause
> reads to return EAGAIN, which not everything is prepared for.
> Below is my patch.
> Michael Thompson
> [EMAIL PROTECTED]
> ---- c u t -- h e r e ----
> --- http11.pm.orig Mon Oct 22 14:14:56 2001
> +++ http11.pm Mon Oct 22 14:15:13 2001
> @@ -79,7 +79,6 @@
> $@ =~ s/^.*?: //;
> die "Can't connect to $host:$port ($@)";
> - $sock->blocking(0);
The HTTP code itself should be prepared. I patch I checked in made
this effective only for HTTPS by overriding
&LWP::Protocol::MyHTTPS::blocking to be a noop.