Re: CGI/1.1 draft
robm@ncsa.uiuc.edu (Rob McCool)
Errors-To: listmaster@www0.cern.ch
Date: Wed, 16 Mar 1994 02:30:03 --100
Message-id: <9403160118.AA05467@void.ncsa.uiuc.edu>
Errors-To: listmaster@www0.cern.ch
Reply-To: robm@ncsa.uiuc.edu
Originator: www-talk@info.cern.ch
Sender: www-talk@www0.cern.ch
Precedence: bulk
From: robm@ncsa.uiuc.edu (Rob McCool)
To: Multiple recipients of list <www-talk@www0.cern.ch>
Subject: Re: CGI/1.1 draft
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
X-Mailer: Mail User's Shell (7.2.5 10/14/92)
X-Mailer: Mail User's Shell (7.2.5 10/14/92)
X-Mailer: Mail User's Shell (7.2.5 10/14/92)
X-Mailer: Mail User's Shell (7.2.5 10/14/92)
X-Mailer: Mail User's Shell (7.2.5 10/14/92)
Content-Length: 857
/*
* Re: CGI/1.1 draft by "Roy T. Fielding"
* written on Mar 7, 1:17am.
*
* Given the option, I would prefer that script config files (including
* imagemap's) have their own directory other than the SERVER_ROOT/conf dir.
* I need to make special precautions against rabid scripts and I find it
* much easier to keep organized (and avoid overlooking something) if all the
* script-specific stuff is in a separate location. Also, it makes it slightly
* easier to install new versions of the server.
*
* Thus, I like the idea but would prefer the location SERVER_ROOT/cgi-conf
*/
My point is that a given server would allow the admin to configure what
directory it was, but that all HTTP servers would set CGI_CONFDIR to
something that scripts could rely on. If someone set it to
SERVER_ROOT/cgi-conf under NCSA httpd, that's fine.
--Rob