> In httpd.conf I have
>
>
> ServerName myhost1.domain.com
> DocumentRoot /httpd/docs
> ErrorLog logs/httpd-errors
> CustomLog logs/httpd-log common
> AccessConfig conf/access.conf
> ResourceConfig conf/srm.conf
Try doing the following instead:
ResourceConfig conf/srm1.conf
It could be that
It's Apache 1.3.9, mod_perl 1.21 on Linux.
The only change I have is patch for correcting PATH enviroment
corruption provided by Doug.
Andrei
On Tue, Nov 16, 1999 at 05:29:46PM +0100, Eric Cholet wrote:
> Which version of mod_perl are you using, 1.21 or the CVS version perhaps?
>
> > Hi!
> >
Which version of mod_perl are you using, 1.21 or the CVS version perhaps?
> Hi!
>
> I've encountered very interesting problem. When I set some variable
> using PerlSetVar in configuration files for different virtual servers
> they seem to be available to ALL of those virtual servers.
>
> Here's
Well, sorry. I've forgotten to put 'my' in front of those varibles in
the example. In the actual code it is there (I use strict :)
The problem is not there.
Andrei
On Tue, Nov 16, 1999 at 05:02:49PM +0100, Gerald Richter wrote:
> > In Myhandler::handler I do
> > $myvar1 = $r->dir_config('MyVa
> In Myhandler::handler I do
> $myvar1 = $r->dir_config('MyVariable');
> $myvar2 = $r->dir_config('MyVariable2);
>
> if($myvar1){
> ## do stuff for first virtual server
> }else{
> ## do stuff for the second one
> }
>
If $myvar1 is a global it will hold it's content forever...
so try
my $myva
Hi!
I've encountered very interesting problem. When I set some variable
using PerlSetVar in configuration files for different virtual servers
they seem to be available to ALL of those virtual servers.
Here's details to clarify.
In httpd.conf I have
ServerName myhost1.domain.com
DocumentRoot
Ok. I think I've figured that out
Reading documentation on Apache ResourceConfig directive. It states
--
Syntax: ResourceConfig filename
Default: ResourceConfig conf/srm.conf
Context: server config, virtual host
Status: core
The server will read this file for more directives after r
Andrei,
I do not see this behavior if I use PerlSetVar directly inside a
section instead of via a ResourceConfig. I do see it if I move the directive
to the main server, so I suppose it's a scope issue with ResourceConfig.
> It's Apache 1.3.9, mod_perl 1.21 on Linux.
>
> The only change I hav