Using PerlSetVar in virtual environments

[Will Fould]

Hello -- I'm have a 'contamination' issue using PerlSetVar in a virtual environment.
I'm wondering if my trouble is from my use of 'require' or from using
non-unique PerlSetVar variable names (although, under separate virtual
containers). While we can continue to run separate Apache instances for each
site, I want to bundle multiple smaller sites under at least one of
the instances.

Can someone spot the weakness here?

In testing, I've got Example1 and Example2 virtual directives:

       <VirtualHost NNN.NN.NN.NNN:80>
               ServerName example1.com
       ...
                   <Location /var/example1/>
                   PerlSetVar foo /var/example1/site.conf
                   </Location>
       </VirtualHost>
      
       <VirtualHost NNN.NN.NN.NNN:80>
               ServerName example2.com
       ...
                   <Location /var/example2/>
                   PerlSetVar foo /var/example2/site.conf
                   </Location>
       </VirtualHost>

In the scripts under each site, I use:

       my $r=Apache2::RequestUtil->request;
       $site_conf=$r->dir_config('foo ');
       require "$site_conf";


Eventually, Example2 site uses details specified in example1/site.conf

Must 'foo' be unique under each virtual environment? (i.e. foo1, foo2)


Thank you for helping!
Will