Beefy Boxes and Bandwidth Generously Provided by pair Networks
Do you know where your variables are?

Re^2: IO::Socket::SSL incompatibility with WWW::Mechanize

by Madhuk (Initiate)
on Jul 09, 2013 at 01:45 UTC ( #1043222=note: print w/replies, xml ) Need Help??

in reply to Re: IO::Socket::SSL incompatibility with WWW::Mechanize
in thread IO::Socket::SSL incompatibility with WWW::Mechanize

Here is the error.

Error GETing https:weblink : Can't connect to (connect: Unknown error) at line xxx.

Just to give more information. I don't see this problem if I run on a computer that doesn't require to go through the proxy.



  • Comment on Re^2: IO::Socket::SSL incompatibility with WWW::Mechanize

Replies are listed 'Best First'.
Re^3: IO::Socket::SSL incompatibility with WWW::Mechanize
by syphilis (Chancellor) on Jul 09, 2013 at 03:09 UTC
    I don't use WWW::Mechanize, but have a look at its noproxy documentation. It says:

    This needs to be explicitly turned off if you're using Crypt::SSLeay to access a https site via a proxy server. Note: you still need to set your HTTPS_PROXY environment variable as appropriate.

    Even if you're not using Crypt::SSLeay, there might be something (not sure exactly what) of relevance there.


      Hi Rob,

      Sorry for the delayed response.

      I have tried turning off and on the noproxy, but there was no change.

      Since the WWW::Mechanize works fine without installing either Net::SSLeay or IO::SOCKET::SSL, is there any debug methodology where I can get the call stack trace? I can use that to run with and without installing the packages and see the difference.



Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://1043222]
and all is quiet...

How do I use this? | Other CB clients
Other Users?
Others about the Monastery: (7)
As of 2017-09-21 09:23 GMT
Find Nodes?
    Voting Booth?
    During the recent solar eclipse, I:

    Results (244 votes). Check out past polls.