Very Computer

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.  :-)

Quote:

> 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.

YM you have something like:

$LUSER/cgi-bin
$LUSER/cgi-bin/someprog.cgi
$LUSER/cgi-bin/docs
$LUSER/cgi-bin/docs/some-doc.txt

Did you try rearranging it:

mv $LUSER/cgi-bin/docs $LUSER/cgi-bin-docs

with an AliasMatch in httpd.conf?

--
Nick Kew

We're so advanced here ... our nearest main road is called the A 386

Quote:> But you know better.

Quote:> YM you have something like:

> $LUSER/cgi-bin
> $LUSER/cgi-bin/someprog.cgi
> $LUSER/cgi-bin/docs
> $LUSER/cgi-bin/docs/some-doc.txt

Quote:> Did you try rearranging it:

> mv $LUSER/cgi-bin/docs $LUSER/cgi-bin-docs

I'm thinking I ought to persuade them to change this anyhow.
The design was theirs (he mumbles in sort-of self defence).

Alias /cgi-bin/ /path/to/cgi-bin/

<Directory /path/to/cgi-bin/>
Options ExecCGI
</Directory>

<LocationMatch /cgi-bin/[^/]*>
SetHandler cgi-script
</Location>

--
Joshua Slive

http://finance.commerce.ubc.ca/~slive/

Quote:> One suggestion which, as usual, I have not tested, is to get rid
> of the ScriptAlias and [...]
> Alias /cgi-bin/ /path/to/cgi-bin/
> <Directory /path/to/cgi-bin/>
> Options ExecCGI
> </Directory>
> <LocationMatch /cgi-bin/[^/]*>
> SetHandler cgi-script
> </Location>

Yes, I've now set something like that up in a test directory, and it
seems to work, thanks!  I can see now what I need to do for the user.

Quote:> Practical suggestions would be welcomed.  :-)

ScriptAlias /cgi-bin/ /opt/apache/cgi-bin/

<Directory "/opt/apache/cgi-bin">
    AllowOverride None
    Options None
    Order allow,deny
    Allow from all
</Directory>

<Directory "/opt/apache/cgi-bin/*">
    SetHandler default-handler
</Directory>

This allows me to access http://localhost/cgi-bin/printenv as a CGI, but
http://localhost/cgi-bin/html/index.html (and the contents of any other
subdirectory of cgi-bin) is served as a normal HTML document.

Ciao

Thomas

--

[normal-ish CGI configuration ... then:]

Quote:> <Directory "/opt/apache/cgi-bin/*">
>     SetHandler default-handler
> </Directory>

Quote:> This allows me to access http://localhost/cgi-bin/printenv as a CGI, but
> http://localhost/cgi-bin/html/index.html (and the contents of any other
> subdirectory of cgi-bin) is served as a normal HTML document.