LWP::UserAgent->request(https) resets alarm()

[jarkun]

found a bug in LWP. When calling LWP::UserAgent->request(https)
any pre-existing alarm() gets reset. Digging around the problem
appears that the LWP uses NET::SSL.pm as part of the https connection
and this code uses an alarm() for timeouts

This doesn't happen for plain ol http-style connections, only https

I haven't puzzled out which piece needs to be changed SSL.pm or LWP

This is happening on a redhat9 box with what I believe are all the
latest packages from CPAN

Who do I contact to submit this as a bug report?


Chris Goebel

 

[Charles DeRykus]

found a bug in LWP. When calling LWP::UserAgent->request(https)
any pre-existing alarm() gets reset. Digging around the problem
appears that the LWP uses NET::SSL.pm as part of the https connection
and this code uses an alarm() for timeouts

This doesn't happen for plain ol http-style connections, only https

I haven't puzzled out which piece needs to be changed SSL.pm or LWP

This is happening on a redhat9 box with what I believe are all the
latest packages from CPAN

Who do I contact to submit this as a bug report?

Hm, I'm using alarms successfully with LWP (2.001),
Crypt-SSLeay (0.51), and openssl 0.9.6g.

[ Crypt::SSLeay includes Net::SSL ]

Are you sure you're using the latest versions?

HTH,