From owner-freebsd-questions  Sat Mar 23  9:26:27 2002
Delivered-To: freebsd-questions@freebsd.org
Received: from mts-116.wallnet.com (mts-116.wallnet.com [208.225.162.48])
	by hub.freebsd.org (Postfix) with ESMTP id BAE1B37B41A
	for <freebsd-questions@FreeBSD.ORG>; Sat, 23 Mar 2002 09:26:09 -0800 (PST)
Received: by 10.0.1.6 (8.11.6/8.11.6) id g2N36SZ00524;
	Fri, 22 Mar 2002 22:06:28 -0500 (EST)
	(envelope-from timothyk)
Message-Id: <200203230306.g2N36SZ00524@10.0.1.6>
Content-Type: text/plain;
  charset="iso-8859-1"
From: Tim Kellers <timothyk@wallnet.com>
To: Steven Lake <raiden@shell.core.com>,
	freebsd-questions@FreeBSD.ORG
Subject: Re: Apache - Refresh my mind
Date: Fri, 22 Mar 2002 22:06:24 -0500
X-Mailer: KMail [version 1.3.2]
References: <Pine.GSO.4.44L0.0203221953400.21774-100000@shell.core.com>
In-Reply-To: <Pine.GSO.4.44L0.0203221953400.21774-100000@shell.core.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Sender: owner-freebsd-questions@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-questions.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-questions>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-questions>
X-Loop: FreeBSD.ORG

It really depends on what you want to do with the server.  You can enable cgi 
by placing ExecCGI in directory containers (in the below example, replace 
IncludesNoExec with ExecCGI --and further tweak the container, the below 
example is HIGHLY restrictive)

<Directory /home/*/public_html>
    AllowOverride FileInfo AuthConfig Limit
    Options MultiViews Indexes SymLinksIfOwnerMatch IncludesNoExec 
    <Limit GET POST OPTIONS PROPFIND>
        Order allow,deny
        Allow from all
    </Limit>
    <LimitExcept GET POST OPTIONS PROPFIND>
        Order deny,allow
        Deny from all
    </LimitExcept>
</Directory>


If you just want system-wide cgi's to function, the following from the 
default httpd.conf file will probably do what you need right out of the box:

  # ScriptAlias: This controls which directories contain server scripts.
    # ScriptAliases are essentially the same as Aliases, except that
    # documents in the realname directory are treated as applications and
    # run by the server when requested rather than as documents sent to the   
    # client.
    # The same rules about trailing "/" apply to ScriptAlias directives as to
    # Alias.
    #
    ScriptAlias /cgi-bin/ "/usr/local/www/cgi-bin/"

    #
    # "/usr/local/www/cgi-bin" should be changed to whatever your 
ScriptAliased
    # CGI directory exists, if you have that configured.
    #
    <Directory "/usr/local/www/cgi-bin">
        AllowOverride None
        Options None
        Order allow,deny
        Allow from all
    </Directory>

And if you want to use .cgi files outside of script aliased directories:

 # If you want to use server side includes, or CGI outside
    # ScriptAliased directories, uncomment the following lines.
    #
    # To use CGI scripts:
    #
    AddHandler cgi-script .cgi

Lastly, if you want to allow safe handling of cgi scripts outside of the 
"usual" directories, compile suexec in the apache sources directory (there is 
a section in the FreeBSD handbook about suexec, IMHO it's well worth the 
(little) trouble it takes to make it work.

Hope this helps

Tim Kellers
CPE/NJIT

On Friday 22 March 2002 08:56 pm, Steven Lake wrote:
> Ok, I'm having to rebuild a server and I need to install Apache on
> it for HTTP access with CGI capabilities.  Now, since I'm being forgetful
> today, what all do I need to install HTTP services with CGI capabilities?
> Do I just install Apache 1.3 and call it a day or do I need more.  I'm
> thinking I need more, but I wanted to be sure.
>
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-questions" in the body of the message

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message