I've inherited a situation from an NCSA server in which the user
has a subdirectory of ordinary files underneath their cgi-bin
subdirectory. Their cgi-bin is using ScriptAlias.
Apparently under NCSA this worked OK, it seems that the scriptalias
property was apparently not inherited into the subdirectory.
But when I try to service the same file structure from Apache, it
refuses to access the files in the subdirectory, reporting "file
permissions deny server execution" i.e thinking that it is supposed to
execute them (and their execute permissions are off, but of course
this isn't the real problem).
Although this seems to be poor practice and I wouldn't recommend it
for a new application, it looks as if I should find some way to
support it for this case. Is there some way I can leave scriptalias
in effect for the cgi-bin directory itself, but turn it off so that
the subdirectory is treated as a normal one?
(Of course I could change the configuration of the cgi-bin directory
itself, so that only *.cgi (or whatever) files are executed. But this
would be moving quite a long way away from the original.)
Practical suggestions would be welcomed. :-)