Re: [cobalt-developers] cgiwrap and Environment Variables

["Robert G. Fisher" <rfisher@xxxxxxxxxxxxxxx>]

> ...but it doesn't seem as though cgiwrap does a particularly thorough job
> of passing environment variables, particularly $ENV{'DOCUMENT_URI'}, which
> is used extensively in most CGI scripts to return a unique identifier for
> SSI transactions.

I think you are looking for REQUEST_URI instead, this works
in ScriptAliased directories, cgiwrap calls, and straight
SSI.

The whole point of cgiwrap is to allow a CGI script to run
with the permissions of a given user.  It also can be
used to ensure that no one is executing a script/program
that is setuid or setgid as well as disallow scripts to
run at a userid below a certain level (default 10 thus
disallowing a script to accidentally run as root if
the admin slips up.)

It also can check the permissions, to disallow running
group or world writeable files (After all, if they are
writeable, how can you guarantee somoene hasn't replaced
the code?)

You can also specify resource limits on how much any
given CGI can consume from the server -- very handy,
albeit, it would be nice to know what the cgiwrap
distributed by Cobalt has since these options are
via the configure script used at compile time.

This means you can specify maximum ram or file size
each cgi instance can use.

Can also setup logs to go through syslog or directly
to a file ( I believe a file is default on Cobalts)



-- 
Robert G. Fisher		     NEOCOM Microspecialists Inc. 
System Administrator/Programmer      (540) 666-9533 x 116