RE: install script and CGIs

["Turner, Ian (iant)" <ia...@sequent.com>]

Place the CGI examples in the documentation section and remove the provided
ones from the distribution directory,
its simple enough for the end user to cut and paste the example to create the
shell scripts.

> -----Original Message-----
> From:	William A. Rowe, Jr. [SMTP:wrowe@lnd.com]
> Sent:	Monday, January 31, 2000 3:00 PM
> To:	new-httpd@apache.org
> Subject:	RE: install script and CGIs
> 
> > > | Suggestions on the best way to have them not installed so 
> > > | they can be run by default?  Confusing users by setting the 
> > > | permissions to non-executible isn't a good idea, especially 
> > > | since it isn't cross-platform.
> > > 
> > > It seems like they belong in some sort of "examples" directory,  
> > > but we don't have one of those.  We could have cgi-bin/examples 
> > > with a README.  Can we drop a .htaccess file there that 
> > > disables CGI?
> > 
> > No, because .htaccess files are disabled.  <g>  
> > 
> > There is a cgi-src directory (well, only in CVS since it is 
> > empty) that used to contain other random exploitable programs.
> > Guess we could move them there...
>  
> Seems a majority of Q's are about cgi-bin access.  I agree it must
> be executable from installation.  But won't there be as many Q's
> of 'why won't my script/app execute from cgi-src'?  Seems another
> fitting name, such as cgi-hazmat, should be provided for poor CGI
> examples.  On the other hand, why provide hazardous samples in
> the first place?