NCSA HTTPd Installation Page 1
Installation Instructions
Installing NCSA HTTPd can be broken down into these basic steps:
1
Downloading the NCSA HTTPd Server 2
Finding HTTPd a Good Home 3
Configuring HTTPd 4
Selecting Scripts 5
Starting NCSA HTTPd
Downloading the NCSA HTTPd Server
If you already have a copy of the current release of NCSA HTTPd 1.5, you may
6
skip to the next step.
7 8
NCSA HTTPd is available as precompiled distributions and binaries for systems we
have access to.
9
There is also a new SingleClick Download and Configure for easy access to NCSA
HTTPd.
If you already have NCSA HTTPd 1.4 running, you may update the HTTPd binary
without the new support files.
Note: There are several new support files for the new authorization types, as
well as examples of many of the other new features in the configuration files,
10
so you might want to retrieve the support files anyways. A step−by−step guide on
how to update the old server is available.
If your system is not on this list, or if you feel more comfortable doing so, you must
11
compile a binary.
Finding HTTPd a Good Home
At this stage, you should move HTTPd’s control files from the directory you have
12
been working in to the directory you intend to use as ServerRoot in the server
configuration file.
Unless you have redefined their locations in the server configuration file, you will
13
have to move the following files and directories into ServerRoot:
1 #Download
2 #Move
3 #Configure
4 #Select
5 #Start
6 #Configure
7 PreCompiled.html
8 PreExec.html
9 SingleClick.html
10 Update.html
11 Compilation.html
12 httpd/ServerRoot.html
13 httpd/ServerRoot.html
http://hoohoo.ncsa.uiuc.edu/docs/setup/Install.html Printed Tue Dec 5 22:02:41 1995
NCSA HTTPd Installation Page 2
httpd : The server itself
conf : Configuration files
logs : Access log and error log
support : Support programs
cgi−bin : Server scripts
14
The logs directory should not be writable by the User your server is
running as.
Configuring HTTPd
The NCSA HTTPd Server is a versatile piece of software, the result of hours and
hours of blood, sweat, and tears by the NCSA HTTPd Development team and Beta
testers the world over. Its versatility does come at a price, however, as you the
webmaster must configure the server to fit your needs. There are 3 types of
configuration that can be done.
Compile Time
The NCSA HTTPd server has several compile time flags. These are contained in the
files src/Makefile and src/config.h of the distribution. These files are
fairly well documented. 15
See also: Compiling NCSA HTTPd
Startup Configuration Files
There are 3 files the server parses at start up (or after receiving a SIGHUP signal).
16
There is some General information available on the configuration file format.
17
There are three configuration files which control Server Configuration, Resource
18 19
Configuration, and Access Control. You should look at and modify the files
conf/httpd.conf−dist, conf/srm.conf−dist and
conf/access.conf−dist which come with the distribution so that they are
correct for your server.
Run Time Configuration
The server also supports per directory configuration files, mostly for access control.
The files in each directory of an accessed The name of this file is set with the
20 21
AccessFileName directive in the Resource Configuration file. See the Access
22
Configuration documents for more information.
Selecting Scripts
14 httpd/User.html
15 Compilation.html
16 ConfigureInfo.html
17 httpd/Overview.html
18 srm/Overview.html
19 access/Overview.html
20 srm/AccessFileName.html
21 srm/Overview.html
22 access/Overview.html
http://hoohoo.ncsa.uiuc.edu/docs/setup/Install.html Printed Tue Dec 5 22:02:41 1995
NCSA HTTPd Installation Page 3
NCSA HTTPd 1.5 comes with many CGI scripts, both useful and informative.
NCSA HTTPd 1.5 does not support the former NCSA htbin scripts, and these
scripts should be removed from the document tree. It is not necessary to install all of
23
the scripts at your site (and we don’t recommend it). Peruse the list of CGI scripts,
and move those you want into the cgi−bin/ directory you defined in your Server
24
Resource Configuration File.
Starting NCSA HTTPd
25
Once you have completed the above steps, and you are using standalone you can start
the server by typing httpd at the command line. Note: You must be root in order
to use a port less than 1024. You may need to use one of the command line options
to override the compile time paths to the configuration files. The flags are:
Usage: httpd [−d directory] [−f file] [−v]
−d directory : specify an alternate initial ServerRoot
−f file : specify an alternate ServerConfigFile
−v : version information (this screen)
If you are installing the server as root, you will probably want to automatically start
HTTPd when the machine boots. This can be done through modifications to various
/etc/rc* or /etc/init.d/* files, depending on your system.
26
If you are running the server from inetd, you need to edit the OS system files.
27
If you have problems starting your server, check out the FAQ
If you have completed these steps, Congratulations! Your server is ready to go.
Before you run off to play with your new toy, please read this guide to referencing
28
files on your server. Particularly, if you are wondering how to set up your server’s
"home page", instructions are in there.
29
Return to the Overview
30
NCSA HTTPd Development Team / httpd@ncsa.uiuc.edu / 10−30−95
23 ScriptList.html
24 srm/Overview.html
25 httpd/ServerType.html
26 StartInetd.html
27 ../FAQ.html#Starting
28 admin/AccessingFiles.html
29 ../Overview.html
30 ../FeedBack.html
http://hoohoo.ncsa.uiuc.edu/docs/setup/Install.html Printed Tue Dec 5 22:02:41 1995
