On Tue, Jan 22, 2002 at 08:53:39AM -0500, Geoffrey Young wrote:
>
> > >
> > > <Directory "/data/apache">
> > > AddHandler .pl perl-script
> > > PerlHandler Apache::Registry
> > > Options +ExecCGI
> > > </Directory>
> > >
> >
> > thnx, but: This part doesnt make the problem. mod_perl works like a
> > charm. Problem is how to deactivate it for a certain location ?
>
> well, only .pl files will be handled by Apache::Registry under this
> config - /data/apache/foo.html ought to be handled by core.
>
> unless you have a global SetHandler perl-script somewhere, mod_perl
> should not handle the content-generation phase without being further
> specified.
>
but this is what my config does:
<Directory "/data/apache">
<Files ~ "\.pl$">
SetHandler perl-script
PerlHandler Apache::Registry
Options +ExecCGI
</Files>
</Directory>
only pl-files are affected. Unfortunately I have some pl-files that
must not run under mod_perl (even not under PerlRun cause they are
really dirty) and I wonder if there is no way to set the orginal
cgi-handler (that does not use mod_perl) for a certain
location/virtual host.
I thought this default-handler is cgi-script, but
SetHandler cgi-script
in a virtual host does not do the trick.
The only way I've found by now is not to enable mod_perl globally, but
put the above config in each virtual-host section but the one that
contains the mad pl-files.
While this is what I do now, I really wonder I one cant disable
mod_perl ..
thnx,
peter
