On Fri, 9 Mar 2001, Andrew Ho wrote:
> Stas,
>
> SB>Try adding:
> SB><Location /cgi-bin/>
> SB> Options +ExecCGI
> SB></Location>
>
> This is a fine fix; I'm actually curious, now that it's been brought up,
> as to why ScriptAlias suddenly breaks. In my config if I have this outside
> of a <Directory>, <Location>, or other container:
>
> <FilesMatch "\.pl$">
> SetHandler perl-script
> PerlHandler Apache::Registry
> PerlSendHeader On
> </FilesMatch>
>
> Then anything before like this which IS inside a container:
>
> <Location ...>
> ...
> ScriptAlias /cgi-bin/ /path/to/cgi-bin/
> <Directory /path/to/cgi-bin/>
> Options FollowSymLinks
> AllowOverrideNone
> </Directory>
> </Location>
>
> Stops working. Fixing this is easy--I just SetHandler cgi-script inside
> the <Directory ...> container. So is the ScriptAlias priority lower than
> the <FilesMatch> assignment?
May be this happens, due to the fact that you define a new section
handling the same location/directory? This is sort of Apache specific one,
to figure out what are the precedence and inheritance rules. I guess
delving into the docs on this will provide the answer.
> I always thought ScriptAlias was just shorthand for Alias + <Location
> ...> + SetHandler.
This is correct. What happens if you don't use the shortcut, but define
the cgi-bin behavior explicitly, just like you do for mod_perl?
_____________________________________________________________________
Stas Bekman JAm_pH -- Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide http://perl.apache.org/guide
mailto:[EMAIL PROTECTED] http://apachetoday.com http://logilune.com/
http://singlesheaven.com http://perl.apache.org http://perlmonth.com/
