in reply to What part of the software stack might cause the timeout on LWP::UserAgent via HTTPS to fail with some perls on Linux and Windows?

http://search.cpan.org/dist/IO-Socket-SSL/README.Win32

The underlying IO::Socket::INET does not support non-blocking sockets on Win32, thus non-blocking IO::Socket::SSL is not supported on Win32, which means also, that timeouts don't work (because they are based on non-blocking). See also IO::Socket::INET -- jettero verses non-blocking in windows

See also Non-blocking socket win32 not work with IO::Socket::SSL, how to set socket recv timeout in architecture independent manner?, what does timeout mean in IO::Socket::INET ?

This information may or may not be outdated.

Suggestions, upgrade all of LWP, IO::Socket, IO::Socket::SSL, Net::SSLeay and it will probably just work

Turn on all possible debugging options, one

use IO::Socket::SSL qw/ debug3 /;

  • Comment on Re: What part of the software stack might cause the timeout on LWP::UserAgent via HTTPS to fail with some perls on Linux and Windows?

Replies are listed 'Best First'.
Re^2: What part of the software stack might cause the timeout on LWP::UserAgent via HTTPS to fail with some perls on Linux and Windows?
by milu (Initiate) on Mar 26, 2012 at 08:46 UTC
    Thank you, anonymous poster, this is precisely what I wanted to know.
      Ah, sorry, I posted too quickly. Timeout does work on Windows, just not via SSL. So I'm not sure the info back from 2004 about non-blocking not supported on Windows still applies. I have seen it to work on Windows, just not via SSL.