in reply to Re: LWP, Crypt-SSLeay, and CLI vs. WWW
in thread LWP, Crypt-SSLeay, and CLI vs. WWW

well....one of the things I tried before I posted was to see if the machine the .pl lived on could see both web addr (http, https) in a web browser - could both times

is there something i can check after that?

specifically, the address i'm trying to go to is
http(s)://ias4/error_403.html

with http, works through browser and CLI
with https, works only through CLI
the machine where the .pl lives can open up both http://... and https://... in a browser

maybe I'm just being obtuse (entirely possible) but I can't get past thinking that it's something in how I'm making the call in the .pl
  • Comment on Re: Re: LWP, Crypt-SSLeay, and CLI vs. WWW

Replies are listed 'Best First'.
Re: Re: Re: LWP, Crypt-SSLeay, and CLI vs. WWW
by dorko (Prior) on Feb 24, 2004 at 19:36 UTC
    Whenever someone says "it works fine from the command line but it doesn't work as CGI..." it makes me think of users' permissions. The user executing CGI scripts is oftentimes "apache" or "nobody". When you run the same script from the command line, you're logged in as a user with rights and permissions that are usually quite different from apache/nobody.

    Also, I'm guessing you're running the CLI script with the same account you ran the PPM to install Crypt::SSLeay which is different than the account your web browser uses to exectute the script as a CGI.

    It may or may not help, but it's something to think about.

    Cheers,

    Brent
    -- Yeah, I'm a Delt.

      FWIW

      the example that LWPCOOK provides here uses "'https://www.helsinki.fi/'"

      can't use that either, even as a test target...which is why i keep going back to the code....but i dunno