[cgiwrap-users] RE: Adding fastcgi support to cgiwrap...

[Rob S. <ro...@ch...>]

> > > As long as it is passed a reasonable set of environment
> > > variables, it should
> > > work ok. The problem is that people do not access cgiwrap
> > scripts through
> > > the document root. They access them via PATH_INFO added to
> > cgiwrap call.
> >
> > How exactly is this a problem?  I don't understand.
>
> Doesn't su-exec require some access path to the executable? i.e. it has to
> know where it is. In the case of cgiwrap, apache doesn't know where the
> executable is.

The invocation of suexec by apache (or mod_fastcgi) includes an argument
which is the CGI application's pathname.  This is the URI "resolve" to the
filesystem.  The file technically doesn't have to exist as long as the
handler knows what to do (currently mod_cgi and mod_fastcgi will
complain/abort if doesn't exist).  I will change that in mod_fastcgi (when
suexec is enabled).  The CGI application's pathname will be ignored by
cgiwrap (I assume - user and group are also passed as args and will have to
be ignored too), the environment will look the same as if invoked as a CGI.

--robs