image\overbutt.gifConfiguring the httpd.conf file

The httpd.conf file is the first of three files that you must configure to set up the HTTP server. You can configure the httpd.conf file by typing the values in a text editor. In the httpd.conf file listed below, all configured values appear in bold type.

To configure the httpd.conf file

1. Click Application Starter, Corel File Manager.

2. Type /etc/apache/ in the Address box.

3. Double-click httpd.conf.

4. Configure the httpd.conf file.

You can refer to the following httpd.conf file for a reference.

5. Save the httpd.conf file.

image\nicon.gif Notes

 

# This is the main server configuration file. See URL http://www.apache.org/

# for instructions.

# Originally by Rob McCool

# Shared Object Module Loading:

# To be able to use the functionality of a module that was built

# as a shared object you have to place corresponding `LoadModule'

# lines at this location so the directives contained in it are

# actually available _before_ they are used.

# Example:

 

# ServerType is either inetd, or standalone.

ServerType standalone

 

# If you are running from inetd, go to "ServerAdmin".

 

# Port: The port the standalone listens to. For ports < 1023, you will need httpd

# to be run as root initially.

Port 80

 

# HostnameLookups: Log the names of clients or just their IP numbers e.g.

# www.apache.org (on) or 204.62.129.132 (off) The default is off because it is better

# for the Internet if # people had to knowingly turn this feature on.

HostnameLookups off

 

# If you wish httpd to run as a different user or group, you must run

# httpd as root initially and it will switch.

 

# User/Group: The name (or #number) of the user/group to run httpd as.

# On SCO (ODT 3) use User nouser and Group nogroup

# On HPUX you may not be able to use shared memory as nobody, and the

# suggested workaround is to create a user www and use that user.

User nobody

Group nobody

 

# ServerAdmin: Your address, where problems with the server should be

# e-mailed.

ServerAdmin FrankJ@myDomain.com

 

# ServerRoot: The directory the server's config, error, and log files

# are kept in.

# NOTE! If you intend to place this on a NFS (or otherwise network)

# mounted filesystem then please read the LockFile documentation,

# you will save yourself a lot of trouble.

ServerRoot /etc/apache

 

# BindAddress: You can support virtual hosts with this option. This

# option is used to tell the server which IP address to listen to. It

# can either contain "*", an IP address, or a fully qualified.

# Internet domain name. See also the VirtualHost directive.

BindAddress *

 

# ErrorLog: The location of the error log file. If this does not

# start with /, ServerRoot is prepended to it.

ErrorLog /var/log/apache/error.log

 

# LogLevel: Control the number of messages logged to the error_log.

# Possible values include: debug, info, notice, warn, error, crit,

# alert, emerg.

LogLevel warn

 

# The following directives define some format nicknames for use with

# a CustomLog directive (see below).

LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\" %T %v" full

LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\"" combined

LogFormat "%h %l %u %t \"%r\" %>s %b" common

LogFormat "%{Referer}i -> %U" referer

LogFormat "%{User-agent}i" agent

 

# The location of the access logfile (Common Logfile Format).

# If this does not start with /, ServerRoot is prepended to it.

CustomLog /var/log/apache/access.log common

 

# If you would like to have an agent and referer logfile uncomment

# the following directives.

#CustomLog logs/referer_log referer

#CustomLog logs/agent_log agent

 

# If you prefer a single logfile with access, agent and referer

# information(Combined Logfile Format) you can use the following #directive.

CustomLog /var/log/apache/access_log combined

 

# PidFile: The file the server should log its pid to

PidFile /var/run/apache.pid

 

# ScoreBoardFile: File used to store internal server process

# information. Not all architectures require this. But if yours does

# (you'll know because this file is created when you run Apache) then

# you *must* ensure that no two invocations of Apache share the same

# scoreboard file. ScoreBoardFile logs/apache_runtime_status

 

# The LockFile directive sets the path to the lockfile used when

# Apache is compiled with either USE_FCNTL_SERIALIZED_ACCEPT or

# USE_FLOCK_SERIALIZED_ACCEPT. This directive should normally be left

# at its default value. The main reason for changing it is if the

# logs directory is NFS mounted, since the lockfile MUST BE STORED ON

# D A LOCAL ISK. The PID of the main server process is automatically

# appended to the filename.

LockFile /var/run/apache.lock

 

# ServerName allows you to set a host name which is sent back to

# clients for your server if it's different than the one the program

# would get (i.e. use "www" instead of the host's real name).

# Note: You cannot just invent host names and hope they work. The

# name you define here must be a valid DNS name for your host. If you

# don't understand this, ask your network administrator.

ServerName myHost_doc1

 

# UseCanonicalName: (new for 1.3) With this setting turned on,

# whenever Apache needs to construct a self-referencing URL (a url

# that refers back to the server the response is coming from) it will

# use ServerName and Port to form a "canonical" name. With this

# setting off, Apache will use the hostname:port that the client

# supplied, when possible. This also affects SERVER_NAME and #SERVER_PORT in CGIs.

UseCanonicalName on

 

# CacheNegotiatedDocs: By default, Apache sends Pragma: no-cache with

# each document that was negotiated on the basis of content. This

# asks proxy servers not to cache the document. Uncommenting the

# following line disables this behavior, and proxies will be allowed #to cache the documents.

#CacheNegotiatedDocs

 

# Timeout: The number of seconds before receives and sends time out

Timeout 300

 

# KeepAlive: Whether or not to allow persistent connections (more

# than one request per connection). Set to "Off" to deactivate.

KeepAlive On

 

# MaxKeepAliveRequests: The maximum number of requests to allow

# during a persistent connection. Set to 0 to allow an unlimited

# amount. We recommend you leave this number high, for maximum #performance.

MaxKeepAliveRequests 100

 

# KeepAliveTimeout: Number of seconds to wait for the next request

KeepAliveTimeout 15

 

# Server-pool size regulation. Rather than making you guess how many

# server processes you need, Apache dynamically adapts to the load it

# sees --- that is, it tries to maintain enough server processes to

# handle the current load, plus a few spare servers to handle

# transient load spikes (e.g., multiple simultaneous requests from a

# single Netscape browser).

 

# It does this by periodically checking how many servers are waiting

# for a request. If there are fewer than MinSpareServers, it creates

# a new spare. If there are more than MaxSpareServers, some of the

# spares die off. These values are probably OK for most sites ---

MinSpareServers 5

MaxSpareServers 10

 

# Number of servers to start --- should be a reasonable ballpark #figure.

StartServers 5

 

# Limit on total number of servers running, i.e., limit on the number

# of clients who can simultaneously connect --- if this limit is ever

# reached, clients will be LOCKED OUT, so it should NOT BE SET TOO

# LOW. It is intended mainly as a brake to keep a runaway server from

# taking Unix with it as it spirals down...

MaxClients 150

 

# MaxRequestsPerChild: the number of requests each child process is

# allowed to process before the child dies.

# The child will exit so as to avoid problems after prolonged use

# when Apache (and maybe the libraries it uses) leak. On most

# systems, this isn't really needed, but a few (such as Solaris) do

# have notable leaks in the libraries.

MaxRequestsPerChild 30