:-) That seems to be the crux of it...
It is being loaded before DBI, however the escalating
number of DB connections we're observing tends to
disagree. I think someone has added a LoadModule
directive somewhere in the wrong place and that module
has a call to DBI.. I've managed to confirm
Apache::
Geoffrey Young wrote:
>>**
>>mod_perl-1.99_16-3
>>**
>>DirectoryIndex index.pl
>
>
> please see this thread
>
> http://marc.theaimsgroup.com/?t=11133509941&r=1&w=2
>
> specifically the solution found here
>
> http://marc.theaimsgroup.com/?l=apache-modperl&m=1114451502
Geoffrey Young wrote:
if you read through the above thread completely you'll see an analysis of
what happens when using SetHandler + DirectoryIndex - basically, mod_dir is
never able to apply the DirectoryIndex directive because it never enters the
request. however, it is possible to get Directo
Philip M. Gollucci wrote:
> Geoffrey Young wrote:
>
>> if you read through the above thread completely you'll see an analysis of
>> what happens when using SetHandler + DirectoryIndex - basically,
>> mod_dir is
>> never able to apply the DirectoryIndex directive because it never
>> enters the
>>
I think it's worth noting (again) that as Perrin said, if you use a instead of a for your registry scripts, then
mod_dir will still handle the directory indexes correctly. If you want a quick
fix, it's probably not going to get any quicker than that.
Adam
-Original Message-
From: Ge
Hi,
I am trying to redirect a request to another location and the following code
works, but the new location is not printed in the address bar.
$r->status_line('302 Moved');
$r->headers_out->add('Location' => 'http://localhost/');
return Apache2::Const::OK;
return Apache2::Const::REDIRECT; #give
Philip M. Gollucci wrote:
[error] slurp_filename('/opt/apache2/perl/script.pl?a=a&b=b&c=c')
/ opening: (2) No such file or directory at
/opt/perl/lib/site_perl/5.8.7/i686-linux/ModPerl/RegistryCooker.pm
line 540
This works for me if I am understanding you correctly.
Okay, so
