in reply to Re^2: Perl issue with Windows 7 vs XP
in thread Perl issue with Windows 7 vs XP

The issue is that LWP::UserAgent fails quietly on https requests when you don't have the necessary modules installed. I got bit by it a few years ago. LWP::Protocol::https is not actually a module, but rather an installation construct for the modules required for https access. Also make sure you explicitly include the https protocol in your URL.

If you are using ActiveState Perl, PPM should give you an easy method to quickly check if you've installed the LWP::Protocol::https package.

#11929 First ask yourself `How would I do this without a computer?' Then have the computer do it the same way.

Replies are listed 'Best First'.
Re^4: Perl issue with Windows 7 vs XP
by Anonymous Monk on Jul 25, 2013 at 14:37 UTC

    Hello Kenneth, thank you very much for all your help. I will have to wait for my App Support team to install it for me as I have restricted access to these things. I was really hoping that there would be a small difference that I overlooked between xp and 7 that could be fixed easily.

[reply]
      You can quickly check if Crypt::SSLeay is installed by running 
      perl -MCrypt::SSLeay -e1

      [download]

      on the command line. If it does not error, then you have the module installed.

      #11929 First ask yourself `How would I do this without a computer?' Then have the computer do it the same way.

[reply]
[d/l]

        Hey Kenneth, I figured out the problem I had. It was an access issue. The version of perl I was using was on the network servers and I only had permission to access a sub folder which perl was located in. As such, windows explorer would work fine in locating it, but the path would not be found when perl was executed through cmd.

[reply]

In Section Seekers of Perl Wisdom