Created attachment 697914 [details] kt,pl Recent perl changes caused https stopped working on some sites. example export PERL_LWP_SSL_VERIFY_HOSTNAME=0 perl -w kt.pl https://github.com/ works , but the perl -w kt.pl 'https://www134.safesecureweb.com/jrproperties/default.htm' Before req U=https://www134.safesecureweb.com/jrproperties/default.htm U=https://www134.safesecureweb.com/jrproperties/default.htm REQUEST ISSUED SSL_connect:before/connect initialization SSL_connect:SSLv2/v3 write client hello A SSL_connect:SSLv3 read server hello A SSL_connect:SSLv3 read server certificate A SSL_connect:SSLv3 read server done A SSL_connect:SSLv3 write client key exchange A SSL_connect:SSLv3 write change cipher spec A SSL_connect:SSLv3 write finished A SSL_connect:SSLv3 flush data SSL_connect:SSLv3 read finished A ..... and waits forever Previously F17 did work OK, F18 did not work. Recent update to F17 made https also non-working for some sites. Now both F17 & F18 fail to https for some sites
Note that downgrade to perl-Net-HTTP-6.02-2.fc17.noarch.rpm seems fixed the issue rpm -Uvh --force http://mirrors.kernel.org/fedora//releases/17/Fedora/x86_64/os/Packages/p/perl-Net-HTTP-6.02-2.fc17.noarch.rpm Retrieving http://mirrors.kernel.org/fedora//releases/17/Fedora/x86_64/os/Packages/p/perl-Net-HTTP-6.02-2.fc17.noarch.rpm Preparing... ########################################### [100%] 1:perl-Net-HTTP ########################################### [100%]
Confirmed that the downgrade to http://mirrors.kernel.org/fedora//releases/17/Fedora/source/SRPMS/p/perl-Net-HTTP-6.02-2.fc17.src.rpm fixed the issue both on F17 & F18
Also confirmed, that perl-Net-HTTP-6.05 may lock forever even on http sites
Confirmed that perl-Net-HTTP.noarch 6.05-1.fc17 updates is a problematic is a sense, it may hang forever and the request never returned, hanging in sleep or wait. (It consumes co CPU in this state). The perl-Net-HTTP.noarch 6.02-2.fc17 installed cures the problem both in F17 & F18 For some season the problem is most easily observed when using https. Test code is attached in first post. But the problem was observed also without https, via plain http. In this case it is more difficult to reproduce it.
I was expected these problems. See bug #768394 for more details, especially comment #16 and #18. And also watch or linked CPAN reports. This is open issue with no good solution yet. *** This bug has been marked as a duplicate of bug 768394 ***