RE: [cobalt-users] CGI above the /web directory...

["Thomas Hodkin" <tom@xxxxxxxx>]

-----Original Message-----
From: cobalt-users-admin@xxxxxxxxxxxxxxx
[mailto:cobalt-users-admin@xxxxxxxxxxxxxxx]On Behalf Of Jay Summers
Sent: 31 August 2001 17:15
To: cobalt-users@xxxxxxxxxxxxxxx
Subject: Re: [cobalt-users] CGI above the /web directory...


>> ScriptAlias /cgi-bin/ /home/sites/site#/cgi-bin/
>> AddHandler cgi-script .cgi
>> AddHandler cgi-script .pl
>>
>
> I'm trying to understand what the point of doing this is? Is it for
> security?

Yes.

> With the scriptalias can't anyone still browse to
> www.domain.com/cgi-bin/file.ext  and just get pointed to the
> /home/sites/site#/cgi-bin/ instead of /home/sites/site#/web/cgi-bin/

No, you can't browse the cgi-bin because it's above the viewable web tree.

> I could see doing this with a cgi-bin someplace on the server and a script
> alias tag in all sites pointing to that for a global cgi-bin or a shared
> cgi-bin for sites created outside of the GUI.

That's probably the best reason for doing it this way. The thing is, my
needs are a little bit different from the normal Cobalt appliance user. I
assume most ppl are using them to host customer websites. We use our Raq2's
to host *only* our private company sites. The only users on our Raq's are me
and my boss. Therefore, I didn't care about CGI-Wrap so I disabled it and
use the above method to keep my cgi-bin's non-browseable. When we left our
previous ISP in favor of colocating our own Raq, this is how they had done
it. I was familiar with it and it just kind of stuck.

regards,
j

_______________________________________________
cobalt-users mailing list
cobalt-users@xxxxxxxxxxxxxxx
To Subscribe or Unsubscribe, please go to:
http://list.cobalt.com/mailman/listinfo/cobalt-users