> -----Original Message----- > From: Stas Bekman [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, July 31, 2001 11:17 PM > To: Chris Rodgers > Cc: [EMAIL PROTECTED] > Subject: Re: Bug?? > > > On Tue, 31 Jul 2001, Chris Rodgers wrote: > > > Thanks for that. However, I've already seen this. The > problem is that I'm > > requesting pages at: > > > > http://my.server.com/perl/blah.pl > > > > and also > > > > https://my.server.com/perl/blah.pl > > > > Now these should be different scripts, and Apache is set up with a > > completely different document and perl root for the http and https > > servers. Unfortunately, these still get confused, even with the > > NameWithVirtualHost code. Hence, I thought of hacking the > .pm files to > > include the server port as well as the name in the uniquely > generated > > namespace. > > > > Any other ideas?? > > Hmm, I think you are the first one to hit this issue. Try > this (untested): > > --- ./lib/Apache/Registry.pm.orig Wed Aug 1 11:06:49 2001 > +++ ./lib/Apache/Registry.pm Wed Aug 1 11:11:04 2001 > @@ -70,7 +70,8 @@ > > if ($Apache::Registry::NameWithVirtualHost && > $r->server->is_virtual) { > my $name = $r->get_server_name; > - $script_name = join "", $name, $script_name if $name; > + $script_name = join "", (exists $ENV{HTTPS}?'https':''), > + $name, $script_name if $name; > } of course, that won't work with PerlSetupEnv Off - maybe use $r->subprocess_env('https') instead :) what about just moving to Apache::RegistryNG, since it subclasses PerlRun which uses the filename and not the URL? --Geoff
