in reply to WWW::Mechanize cannot connect to HTTPS site

Any ideas?

Oddly, I get the same "Can't connect to www.cpan.org:443" error using Strawberry Perl 5.24.1 on Windows 11, whereas Strawberry Perl 5.24.4 (on the very same machine) retrieves the page just fine.
On SP-5.24.1:
D:\>perl -le "print $];" 5.024001 D:\>\b\pmver WWW::Mechanize 1.83 D:\>\b\pmver Crypt::SSLeay 0.72 D:\>\b\pmver Net::SSLeay 1.80 D:\>\b\pmver IO::Socket::SSL 2.043 D:\>\b\pmver Net::SSL 2.86 D:\>\b\pmver LWP::Protocol::https 6.06
On SP-5.24.4:
D:\>perl -le "print $];" 5.024004 D:\>\b\pmver WWW::Mechanize 1.88 D:\>\b\pmver Crypt::SSLeay 0.72 D:\>\b\pmver Net::SSLeay 1.85 D:\>\b\pmver IO::Socket::SSL 2.056 D:\>\b\pmver Net::SSL 2.86 D:\>\b\pmver LWP::Protocol::https 6.07
("pmver" is just a local batch file that prints out the version number of its argument.)

<UPDATE>:
They both use different versions of openssl, too. SP-5.24.1 has 1.0.2j and SP-5.24.4 has 1.0.2o
</UPDATE>

Is there anything in there that helps ?

Cheers,
Rob

Replies are listed 'Best First'.
Re^2: WWW::Mechanize cannot connect to HTTPS site
by syphilis (Archbishop) on May 29, 2024 at 12:52 UTC
    I checked a little bit further and found the same brokenness in both SP-5.24.2 and SP-5.24.3.
    SP-5.24.3 (still broken) had the following versions installed:
    D:\>perl -le "print $];" 5.024003 D:\>\b\pmver WWW::Mechanize 1.86 D:\>\b\pmver Crypt::SSLeay 0.72 D:\>\b\pmver Net::SSLeay 1.81 D:\>\b\pmver IO::Socket::SSL 2.051 D:\>\b\pmver Net::SSL 2.86 D:\>\b\pmver LWP::Protocol::https 6.07
    Its openssl version was 1.0.2l

    UPDATE:
    Upgrading IO::Socket::SSL to version 2.056 (on SP-5.24.3) did not fix the problem - so it would seem that the issue lies NOT with any of those perl modules.
    And I couldn't see any flags being waved in 5.24.4 perldelta, so I guess the problem is with either the openssl version, or some other module.

    Cheers,
    Rob
      And Mozilla::CA?
        And Mozilla::CA?

        Yep -I think you nailed it.
        SP-5.24.3 ships with Mozilla-CA-20160104, whereas SP-5.24.4 ships with Mozilla-CA-20180117.
        When I update SP-5.24.3 to Mozilla-CA-20180117 the problem goes away.

        Cheers,
        Rob