Entwickeler reichtet Augenmerk auf:
QuotePlease be aware that with the IPv6 capable super classes, it will look first for the IPv6 address of a given hostname. If the resolver provides an IPv6 address, but the host cannot be reached by IPv6, there will be no automatic fallback to IPv4. To avoid these problems you can enforce IPv4 for a specific socket by using the Domain or Family option with the value AF_INET as described in IO::Socket::IP. Alternatively you can enforce IPv4 globally by loading IO::Socket::SSL with the option 'inet4', in which case it will use the IPv4 only class IO::Socket::INET as the super class
—
https://metacpan.org/pod/IO::Socket::SSL#Descripti...
Wenn also Host IPv6 und IPv6 auflöst, aber IPv6 nicht erreichbar ist, stirbt das Programm.
Und stat dessen IPv4 erzwingen ist auch nur ein Würgaround.
Ziemlich unresilient, das.
Bei eignen Programmen kann eine ja rummurksen, aber leider hilft das nicht bei LWP-Request.