- Original Message -
From: Erich Oliphant [EMAIL PROTECTED]
To: Stas Bekman [EMAIL PROTECTED]
Sent: Wednesday, January 15, 2003 9:21 PM
Subject: Re: Passing CGI environment to subprograms
Duh :) Sorry, I thought I included the rev in my original post, yes I am
using 2.0. Hmm
Erich Oliphant wrote:
- Original Message -
From: Erich Oliphant [EMAIL PROTECTED]
To: Stas Bekman [EMAIL PROTECTED]
Sent: Wednesday, January 15, 2003 9:21 PM
Subject: Re: Passing CGI environment to subprograms
Duh :) Sorry, I thought I included the rev in my original post, yes I am
-
From: Stas Bekman [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Thursday, January 09, 2003 10:01 PM
Subject: Re: Passing CGI environment to subprograms
I don't see any reason why your `` invoked process doesn't see the CGI
env vars. For example:
#!/usr/bin/perl
print
I don't see any reason why your `` invoked process doesn't see the CGI
env vars. For example:
#!/usr/bin/perl
print Content-type: text/plain\n\n;
$ENV{'PATH'} = '/bin:/usr/bin';
delete @ENV{'IFS', 'CDPATH', 'ENV', 'BASH_ENV'};
print qx{printenv |grep REMOTE_ADDR};
prints:
REMOTE_ADDR=127.0.0.1
Hi,
I have a mod_perl script that exec's (via backticks) another program.
This program actually needs the CGI enviroment variables to perform
correctly (it's a proprietary program, it was actually called by
shell CGI initially, this approach cuts our exec's in half until
we get an alternative
PROTECTED]
Sent: Wednesday, January 08, 2003 4:46 PM
Subject: Passing CGI environment to subprograms
Hi,
I have a mod_perl script that exec's (via backticks) another program.
This program actually needs the CGI enviroment variables to perform
correctly (it's a proprietary program, it was actually
