On Wed, Nov 28, 2001 at 04:31:07PM -0800, Kenny Smith wrote:
Hello,
I'm using mod_perl as a replacement for CGI. We are getting strange behavior
where $ENV{'REMOTE_USER'} isn't being set correctly.
The script is protected by an .htaccess type of authentication, so when I
log in as
-Original Message-
From: Terry Moran [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, June 27, 2001 3:39 PM
To: [EMAIL PROTECTED]
Subject: %ENV push_handlers
To all:
I am putting together a site utilizing stacked handlers where the
first of the modules uses the
(foo = 'bar');
$r-push_handlers(PerlCleanupHandler = sub {
warn shift-pnotes('foo');
});
works no problemo...
--Geoff
-Original Message-
From: Terry Moran
To: Geoffrey Young
Sent: 6/27/01 7:57 PM
Subject: Re: %ENV push_handlers
Geoff:
I really appreciate the help. I got a chance
-Original Message-
From: Paul Evad
To: [EMAIL PROTECTED]
Sent: 3/21/01 1:36 PM
Subject: %ENV via PerlTransHandler
question: how does one access the environment variables when using
mod_perl as a transhandler?
what kind of stuff are you expecting HTTP_REFERER and company via
Gene Dascher ([EMAIL PROTECTED]) said something to this effect on 03/15/2001:
Is the ENV hash sanitized and repopulated between the time the Perl*Auth
handlers are run and the requested cgi is executed? I am setting an ENV key
in one of my handlers that I'd like to use in a cgi that resides
Subject: Re: %ENV
Gene Dascher ([EMAIL PROTECTED]) said something to this effect on
03/15/2001:
Is the ENV hash sanitized and repopulated between the time the Perl*Auth
handlers are run and the requested cgi is executed? I am setting an ENV
key
in one of my handlers that I'd like to use in a cgi
-Original Message-
From: darren chamberlain [mailto:[EMAIL PROTECTED]]
Sent: Thursday, March 15, 2001 7:19 AM
To: modperl
Subject: Re: %ENV
[snip]
Try fiddling with $r-subprocess_env; I've had good results
that way. e.g.:
$r-subprocess_env('TEST_VAR', 1);
I
Gene Dascher ([EMAIL PROTECTED]) said something to this effect on 03/15/2001:
Well, with the subprocess_env(), I can see the key that I set in my cgi now,
but the value that I set the key to is a Hash reference that I need to use
in my cgi. Unfortunately, all I get now is ENV{'TEST_VAR'} =
-Original Message-
From: darren chamberlain [mailto:[EMAIL PROTECTED]]
Sent: Thursday, March 15, 2001 8:34 AM
To: [EMAIL PROTECTED]
Subject: Re: %ENV
Gene Dascher ([EMAIL PROTECTED]) said something to
this effect on 03/15/2001:
Well, with the subprocess_env(), I can see
Geoffrey Young ([EMAIL PROTECTED]) said something to this effect on 03/15/2001:
Gene Dascher ([EMAIL PROTECTED]) said something to
this effect on 03/15/2001:
Well, with the subprocess_env(), I can see the key that I
set in my cgi now,
but the value that I set the key to is a Hash
On Tue, 6 Jun 2000, Ben Cohen wrote:
This was certainly a weird bug ( I think it was a bug ).
Even setting PerlSetEnv in httpd.conf didn't help.
The PATH would be properly set until the first time a mod_perl
script modified its PATH at which point all other
scripts including mod_cgi
On Mon, 14 Aug 2000, Niraj Sheth wrote:
Hi,
I am having very strange problem with environment variables.
From Apache::PerlRun script(cgi) I am setting env and firing background
process ..
system("$command ") (or print `$command `;)
now looks like environment variable being
On Tue, 15 Aug 2000, Niraj Sheth wrote:
so why dump_env is getting both?
If I either uncomment "local %ENV = %ENV;" in script or put "%ENV = ();"
in PerlCleanupHandler then dump_env is working fine.
I tried both Apache::PerlRun and Apache::Registry which same result.
oh whoops, you did
2000 3:32 PM
To: Niraj Sheth
Cc: [EMAIL PROTECTED]
Subject: RE: env in background process
On Tue, 15 Aug 2000, Niraj Sheth wrote:
so why dump_env is getting both?
If I either uncomment "local %ENV = %ENV;" in script or put
"%ENV = ();"
in PerlCleanupHandler
On Wed, 23 Aug 2000, Sheth, Niraj wrote:
Didn't get any reply yet on this, so I think i am doing something very
stupid ...
i'm still catching up with plenty of unanswered mail in my modperl
mailbox, including yours, doing the best i can.
]
Subject: RE: env in background process
Follow up on this.
script1.pl(set FOO1 env)
===
#!/usr/local/bin/perl
print "Content-type: text/html\n\n";
print "PID = $$BR\n";
print "SCRIPT1 with FOO1BR\n";
#local %ENV = %ENV;
$ENV{FOO1} = "foo
Follow up on this.
script1.pl(set FOO1 env)
===
#!/usr/local/bin/perl
print "Content-type: text/html\n\n";
print "PID = $$BR\n";
print "SCRIPT1 with FOO1BR\n";
#local %ENV = %ENV;
$ENV{FOO1} = "foo1";
print map { "$_ = $ENV{$_}BR\n"; } sort keys %ENV;
$command = "dump_env";
print
Ben Cohen writes:
Go to the line that reads:
eval { {$cv}($r, @_) } if $r-seqno;
I love perl :)
Dirk
On Tue, 6 Jun 2000, Ben Cohen wrote:
Thanks to all for the helpful suggestions.
Gunther Birzniek from the list suggested a solution that I've
now tried and it works perfectly:
{begin quote}
I assume you are running with Apache:Registry?
You could also save off the $ENV{PATH}...
On Sun, 4 Jun 2000, Ben Cohen wrote:
The problem is that when a mod_perl script modifies the PATH
environment variable, this change seems to become global and
affects even plain old mod_cgi scripts.
While I also wonder (as another respondent did) why a mod_perl script would
need to alter
Thanks to all for the helpful suggestions.
Gunther Birzniek from the list suggested a solution that I've
now tried and it works perfectly:
{begin quote}
I assume you are running with Apache:Registry?
You could also save off the $ENV{PATH}...
Go to the line that reads:
eval {
[EMAIL PROTECTED] (Ben Cohen) wrote:
{begin quote}
I assume you are running with Apache:Registry?
You could also save off the $ENV{PATH}...
Go to the line that reads:
eval { {$cv}($r, @_) } if $r-seqno;
And before it have something like
$ENV{OLD_PATH} = $ENV{PATH}
and after it
| I know that the old CGI scripts probably shoudn't rely on PATH
| but they do and there are too many to fix right away.
To rely on $ENV{PATH} is one thing. But why would a mod_perl script ever
need to *change* it?
Ime
23 matches
Mail list logo
