httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jeff Trawick <traw...@gmail.com>
Subject mod_cgid, unix socket, ScriptSock directive
Date Sat, 20 Nov 2004 17:11:34 GMT
The ScriptSock directive must be used when there are two instances of
the server with same ServerRoot.  If it is omitted, symptoms may
include

. wrong credentials for CGIs
. CGIs stop working for one server when other server is terminated

It should be easy to avoid this configuration requirement by appending
parent pid to the name of the unix socket which is used *when user
didn't specify ScriptSock*, though there is slight migration concern
in case administrator relies on name of unix socket for other reason
(e.g., to use its existence as knowledge that mod_cgid is ready for
business).

It should be easy to catch such a misconfiguration by adding the
parent pid to the CGI request sent over the Unix socket, and fail the
request (and log appropriate message) if parent pid is wrong.

Any concerns with adding parent pid to name of the unix socket used by
mod_cgid?  If the default unix socket name is changed, then chance of
misconfiguration goes way down, so there is not much benefit to adding
the server-instance check as part of every CGI request.

Mime
View raw message