"Configuring Apache"

[Joshua Slive]

In the spirit of procrastination, which has once again overwhelmed me this
weekend, here is a first draft of what I talked about this morning: A
document that gives the very basics of how the apache configuration
process works.  It is meant to be very short and simple without many
technical details, but with links to other places in the docs where the
details can be obtained.

Comments/suggestions/criticisms strongly encouraged.

-- 
Joshua Slive
[EMAIL PROTECTED]
http://finance.commerce.ubc.ca/~slive/
Phone: (604) 822-1871

Title: Configuring Apache

Configuring Apache Main Configuration Files Apache is configured by placing directives in plain text configuration files. The main configuration file is usually called httpd.conf. The location of this file is set at compile-time, but may be overridden with the -f command line flag. Some sites also have srm.conf and access.conf files for historical reasons. In addition, other configuration files may be added using the Include directive. Any directive may be placed in any of these configuration files. Changes to the main configuration files are only recognized by Apache when it is started or restarted. The server also reads a file containing mime document types; the filename is set by the TypesConfig directive, and is mime.types by default. Syntax of the Configuration Files Directives in the configuration files are case-insensitive, but arguments to directives are often case sensitive. Lines which begin with the hash character "#" are considered comments, and are ignored. Comments may not be included on a line after a configuration directive. White space occurring before a directive is ignored, so you may indent directives for clarity. You can check your configuration files for syntax errors without starting the server by using apachectl configtest or the -t command line option. Scope of Directives Directives placed in the main configuration files apply to the entire server. If you wish to change the configuration for only a part of the server, you can scope your directives by placing them in <Directory>, <DirectoryMatch>, <Files>, <FilesMatch>, <Location>, and <LocationMatch> sections. These sections limit the application of the directives which they enclose to particular filesystem locations, or URLs. These directives can also be nested, allowing for very fine grained configuration. .htaccess Files Apache allows for decentralized management of configuration via special files placed inside the web tree. The special files are usually called .htaccess, but any name can be specified in the AccessFileName directive. Directives placed in .htaccess files apply to the directory where you place the file, and all sub-directories. The .htaccess files follow the same syntax as the main configuration files. Since .htaccess files are read on every request, rather than only at server startup, changes made in these files take immediate effect. To find which directives can be placed in .htaccess files, check the Context of the directive. The server administrator further controls what directives may be placed in .htaccess files by configuring the AllowOverride directive in the main configuration files.