> >
> > There is no "directory, .htaccess" in the context and that's like it
really
> > behaves. (unless they changed it in a very recent version and didn't
update
> > the docs, which I don't expect)
> >
> > PerlSetEnv is the only chance to have different values in different
> > directories.
>
> i
On Tue, 10 Jul 2001, Gerald Richter wrote:
> The docs says:
>
> SetEnv directive
> Syntax: SetEnv variable value
> Context: server config, virtual host
> Status: Base
> Module: mod_env
> Compatibility: SetEnv is only available in Apache 1.1 and later.
> Sets an environment variable, which is th
Doug,
Thanks for the quick turn around. The patch works
great.
-MikeB.
-Original Message-
From: Doug MacEachern [mailto:[EMAIL PROTECTED]]
this patch should fix the problem. you should also be able to
s/PerlSetEnv/SetEnv/g, unless Embperl needs these variables before the
fix
>
> > Embperl doesn't need them before the fixup phase, but sometimes you want
> > different values for the environment variables for different
directories,
> > which doesn't work with SetEnv
>
> really? glancing at mod_env.c looks like it should work.
>
The docs says:
SetEnv directive
Syntax:
On Tue, 10 Jul 2001, Gerald Richter wrote:
> Yes, this fixes the problem :-)
cool.
> Embperl doesn't need them before the fixup phase, but sometimes you want
> different values for the environment variables for different directories,
> which doesn't work with SetEnv
really? glancing at mod_
> this patch should fix the problem.
Yes, this fixes the problem :-)
> you should also be able to
> s/PerlSetEnv/SetEnv/g, unless Embperl needs these variables before the
> fixup phase.
>
Embperl doesn't need them before the fixup phase, but sometimes you want
different values for the environ
this patch should fix the problem. you should also be able to
s/PerlSetEnv/SetEnv/g, unless Embperl needs these variables before the
fixup phase.
Index: src/modules/perl/mod_perl.c
===
RCS file: /home/cvs/modperl/src/modules/perl/mo
