Frank Maas wrote:
> You state that this is an Apache thing, but I tend to disagree slightly.
> All handlers are defined using a Perl* prefix and this triggers mod_perl,
> not Apache. AFAIK the Apache configuration does not let you tamper with
> the request-phases directly.
You are correct, and
> Just for sake of an example:
>
>
> PerlFixupHandler My::Fixup
>
>
>
> # disable PerlFixupHandler
PerlFixupHandler 'sub {0}'
>
seriously, people almost universally find that is a bigger
hassle than it's worth...
--Geoff
On Wed, Oct 19, 2005 at 11:15:18AM -0400, Garrison Hoffman wrote:
>
> This really has more to do with Apache than mod_perl. Look at the
> Apache docs for mod_access & RemoveHandler.
>
> http://httpd.apache.org/docs/2.0/
>
> Anything you can override, you can also restore. In the case of
> auth
Frank Maas wrote:
>>
>> SetHandler none
>>
>
> This seems to disable the PerlHandler, but the Perl*Handlers remain
> intact. I have defined a PerlAuthenHandler, PerlAuthzHandler and a
> PerlFixupHandler for / and would like to disable all for /images. Is
> that at all possible (with MP2)? And
Garrison Hoffman wrote:
> Here is another way, add your images and static files to locations
> with default handlers:
>
>
> SetHandler none
>
This seems to disable the PerlHandler, but the Perl*Handlers remain
intact. I have defined a PerlAuthenHandler, PerlAuthzHandler and a
PerlFixupHa
