Re: CGI/1.1 draft

• Mail folder: WWW Talk Jan 94-present
• Next message: Dave_Raggett: "Re: Insecure WWW Access Authorization Protocol?"
• Previous message: Roy T. Fielding: "Re: Questions about HTML conventions "

Errors-To: listmaster@www0.cern.ch
Date: Mon, 7 Mar 1994 10:21:51 --100
Message-id: <9403070117.aa21425@paris.ics.uci.edu>
Errors-To: listmaster@www0.cern.ch
Reply-To: fielding@simplon.ICS.UCI.EDU
Originator: www-talk@info.cern.ch
Sender: www-talk@www0.cern.ch
Precedence: bulk
From: "Roy T. Fielding" <fielding@simplon.ICS.UCI.EDU>
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
Content-Length: 1244

Rob writes:

> One idea I have found interesting is the idea of making some kind of
> configuration directory available. Something like CGI_CONFIG which would be
> set to a central location of CGI configuration files may be nice, but then
> people will all have to have write access to this directory. So I'm not sure
> if this would help much either. This could be set to SERVER_ROOT/conf for
> NCSA httpd, or just allow users to configure it. The point would be to
> create a central repository for CGI config. files which would be available
> on any server.

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


...Roy Fielding   ICS Grad Student, University of California, Irvine  USA
                   (fielding@ics.uci.edu)
    <A HREF="http://www.ics.uci.edu/dir/grad/Software/fielding">About Roy</A>