> -----Original Message-----
> From: Fred Toth [mailto:[EMAIL PROTECTED]]
> Sent: Friday, March 09, 2001 1:03 PM
> To: [EMAIL PROTECTED]
> Subject: Installing global handler breaks CGI
>
>
> Hi,
>
> I'm lost on this one. I'm trying to install a simple handler that
> will get called on every request.
you can place any Perl*Handler at a server level (well, except PerlHandler I
guess)
and it will apply to all requests received by the server.
PerlAccessHandler My::Access
<Location ...
> My first try at this is:
>
> <Location />
> SetHandler perl-script
> PerlAccessHandler My::Access
> </Location>
well, <Directory> controls things of a filesystem basis and <Location>
controls on a URL basis.
for both <Directory> and <Location> / is kinda special - I think I remember
reading a thread on new-httpd that talked about why / was not merged the
same way as other places, but I'm not sure. At any rate, you typically
don't see Perl*Handlers installed for /
see the apache docs on both directives for more general info...
HTH
--Geoff
>
> Right now the handler does nothing except write to the log
> and return DECLINED. It works fine.
>
> However, what does NOT work any longer is standard CGI
> (/cgi-bin/whatever). Instead of executing, my CGI script is
> returned to the browser.
>
> I'm guessing that somehow the location of "/" is overriding
> the ExecCGI-ness of /cgi-bin, but I don't know why, nor can
> I find any way of putting it back.
>
> If I remove the above Location block, CGI returns to normal.
>
> Can anyone explain this to me?
>
> Thanks,
>
> Fred Toth
> [EMAIL PROTECTED]
>
