Damyan, Could it be that App1::Setup is taking over the App1001::Setup namespace. My guess is that the problem is in the code for App1::Setup.
simran. On Wed, 2002-12-04 at 20:37, Damyan Ivanov wrote: > [apache-1.3.26/mod_perl-1.27 from Debian/unstable] > > Hello, > > I am having trouble setting different Perl*Handler's for two different > VirtualHosts. The virtual hosts use one IP and are name-based. > > configuration is as follows: > > Port 80 > Bind 10.0.0.1 > NameVirtualHost 10.0.0.1 > PerlRequire /etc/apache-perl/startup.pl > > <VirtualHost 10.0.0.1> > ServerName test1.domain > > ... > PerlFixupHandler App1::Setup > ... > </VirtualHost> > > <VirtualHost 10.0.1.1 > ServerName test1001.domain > ... > PerlFixupHandler App1001::Setup > ... > </VirtualHost> > > According to Apache Name Virtual Host docs, this is the right way to > setup name-based virtual hosts (imho). > > When I try to access test1.domain everithing works fine. If I try to > access test1001.domain after that - I get App1::Setup invoked, > instead of App1001::Setup > > after a restart I am able to work with test1001.domain correctly, but > after that test1.domain invoces App1001::Setup again. > > Is this as designed? Is it possible to run multiple applications with > different Perl*Handlers using virtual hosts? Any readings I've missed? > > > Thanks in advance. > dam
