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 /;
In reply to 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?
by Anonymous Monk
in thread 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
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |