883N/A# This is the main Apache HTTP server configuration file. It contains the
883N/A# configuration directives that give the server its instructions.
883N/A# for a discussion of each configuration directive.
883N/A# Do NOT simply read the instructions in here without understanding
883N/A# what they do. They're here only as hints or reminders. If you are unsure
883N/A# consult the online docs. You have been warned.
883N/A# Configuration and logfile names: If the filenames you specify for many
883N/A# of the server's control files begin with "/" (or "drive:/" for Win32), the
883N/A# server will use that explicit path. If the filenames do *not* begin
883N/A# ServerRoot: The top of the directory tree under which the server's
883N/A# configuration, error, and log files are kept.
883N/A# Do not add a slash at the end of the directory path. If you point
883N/A# ServerRoot at a non-local disk, be sure to point the LockFile directive
883N/A# at a local disk. If you wish to share the same ServerRoot for multiple
883N/A# httpd daemons, you will need to change at least LockFile and PidFile.
883N/A# Dynamic Shared Object (DSO) Support
883N/A# To be able to use the functionality of a module which was built as a DSO you
883N/A# have to place corresponding `LoadModule' lines at this location so the
883N/A# directives contained in it are actually available _before_ they are used.
883N/A# Statically compiled modules (those listed by `httpd -l') do not need
883N/A<IfModule !mpm_netware_module>
883N/A# If you wish httpd to run as a different user or group, you must run
883N/A# httpd as root initially and it will switch.
883N/A# It is usually good practice to create a dedicated user and group for
883N/A# running httpd, as with most system services.
883N/A# 'Main' server configuration
883N/A# The directives in this section set up the values used by the 'main'
883N/A# server, which responds to any requests that aren't handled by a
883N/A# <VirtualHost> definition. These values also provide defaults for
883N/A# any <VirtualHost> containers you may define later in the file.
883N/A# All of these directives may appear inside <VirtualHost> containers,
883N/A# in which case these default settings will be overridden for the
883N/A# virtual host being defined.
883N/A# ServerAdmin: Your address, where problems with the server should be
883N/A# e-mailed. This address appears on some server-generated pages, such
883N/A# as error documents.
e.g. admin@your-domain.com
883N/AServerAdmin root@localhost
883N/A# ServerName gives the name and port that the server uses to identify itself.
883N/A# This can often be determined automatically, but we recommend you specify
883N/A# it explicitly to prevent problems during startup.
883N/A# If your host doesn't have a registered DNS name, enter its IP address here.
883N/A# Each directory to which Apache has access can be configured with respect
883N/A# to which services and features are allowed
and/or disabled in that
883N/A# directory (and its subdirectories).
883N/A# First, we configure the "default" to be a very restrictive set of
883N/A# Note that from this point forward you must specifically allow
883N/A# particular features to be enabled - so if something's not working as
883N/A# you might expect, make sure that you have specifically enabled it
883N/A# DirectoryIndex: sets the file that Apache will serve if a directory
883N/A# The following lines prevent .htaccess and .htpasswd files from being
883N/A# viewed by Web clients.
883N/A# ErrorLog: The location of the error log file.
883N/A# If you do not specify an ErrorLog directive within a <VirtualHost>
883N/A# container, error messages relating to that virtual host will be
883N/A# logged here. If you *do* define an error logfile for a <VirtualHost>
883N/A# container, that host's errors will be logged there and not here.
883N/A# LogLevel: Control the number of messages logged to the error_log.
883N/A# Possible values include: debug, info, notice, warn, error, crit,
883N/A<IfModule log_config_module>
883N/A # The following directives define some format nicknames for use with
883N/A # a CustomLog directive (see below).
883N/A LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\"" combined
883N/A LogFormat "%h %l %u %t \"%r\" %>s %b" common
883N/A <IfModule logio_module>
883N/A LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\" %I %O" combinedio
883N/A # The location and format of the access logfile (Common Logfile Format).
883N/A # If you do not define any access logfiles within a <VirtualHost>
883N/A # container, they will be logged here. Contrariwise, if you *do*
883N/A # define per-<VirtualHost> access logfiles, transactions will be
883N/A # logged therein and *not* in this file.
883N/A # If you prefer a logfile with access, agent, and referer information
883N/A # (Combined Logfile Format) you can use the following directive.
883N/A # Redirect: Allows you to tell clients about documents that used to
883N/A # exist in your server's namespace, but do not anymore. The client
883N/A # will make a new request for the document at its new location.
883N/A # Alias: Maps web paths into filesystem paths and is used to
883N/A # access content that does not live under the DocumentRoot.
883N/A # If you include a trailing / on /webpath then the server will
883N/A # require it to be present in the URL. You will also likely
883N/A # need to provide a <Directory> section to allow access to
883N/A # ScriptAlias: This controls which directories contain server scripts.
883N/A # ScriptAliases are essentially the same as Aliases, except that
883N/A # documents in the target directory are treated as applications and
883N/A # run by the server when requested rather than as documents sent to the
883N/A # client. The same rules about trailing "/" apply to ScriptAlias
883N/A # directives as to Alias.
883N/A # ScriptSock: On threaded servers, designate the path to the UNIX
883N/A # socket used to communicate with the CGI daemon of mod_cgid.
883N/A# CGI directory exists, if you have that configured.
883N/A# DefaultType: the default MIME type the server will use for a document
883N/A# if it cannot otherwise determine one, such as from filename extensions.
883N/A# a good value. If most of your content is binary, such as applications
883N/A# keep browsers from trying to display binary files as though they are
883N/A # TypesConfig points to the file containing the list of mappings from
883N/A # filename extension to MIME-type.
883N/A # AddType allows you to add to or override the MIME configuration
883N/A # file specified in TypesConfig for specific file types.
883N/A # AddEncoding allows you to have certain browsers uncompress
883N/A # information on the fly. Note: Not all browsers support this.
883N/A #AddEncoding x-compress .Z
883N/A #AddEncoding x-gzip .gz .tgz
883N/A # If the AddEncoding directives above are commented-out, then you
883N/A # probably should define those extensions to indicate media types:
883N/A # AddHandler allows you to map certain file extensions to "handlers":
883N/A # actions unrelated to filetype. These can be either built into the server
883N/A # or added with the Action directive (see below)
883N/A # To use CGI scripts outside of ScriptAliased directories:
883N/A # (You will also need to add "ExecCGI" to the "Options" directive.)
883N/A AddHandler cgi-script .cgi
883N/A AddHandler perl-script .pl
883N/A PerlResponseHandler ModPerl::Registry
883N/A PerlOptions +ParseHeaders
883N/A # For type maps (negotiated resources):
883N/A #AddHandler type-map var
883N/A # Filters allow you to process content before it is sent to the client.
883N/A # To parse .shtml files for server-side includes (SSI):
883N/A # (You will also need to add "Includes" to the "Options" directive.)
883N/A #AddOutputFilter INCLUDES .shtml
883N/A# The mod_mime_magic module allows the server to use various hints from the
883N/A# contents of the file itself to determine its type. The MIMEMagicFile
883N/A# directive tells the module where the hint definitions are located.
883N/A# Customizable error responses come in three flavors:
883N/A# 1) plain text 2) local redirects 3) external redirects
883N/A#ErrorDocument 500 "The server made a boo boo."
883N/A# EnableMMAP and EnableSendfile: On systems that support it,
883N/A# memory-mapping or the sendfile syscall is used to deliver
883N/A# files. This usually improves server performance, but must
883N/A# be turned off when serving from networked-mounted
883N/A# filesystems or if support for these functions is otherwise
883N/A# broken on your system.
883N/A# Supplemental configuration
1040N/A# Include all the .conf configuration files in the
1040N/A# You can place additional configuration files in the
1040N/A# or to modify the default configuration of the server,
1040N/A# or you may simply copy their contents here and change as
1040N/A# Sample configuration files are in the
1040N/A# directory and modify as required.
883N/A# Visual Panels will supply SSL configuration(s)
883N/A# Note: The following must must be present to support
883N/A# but a statically compiled-in mod_ssl.
883N/ASSLRandomSeed startup builtin
883N/ASSLRandomSeed connect builtin
883N/A# machine you can setup VirtualHost containers for them. Most configurations
883N/A# use only name-based virtual hosts so the server doesn't need to worry about
883N/A# IP addresses. This is indicated by the asterisks in the directives below.
883N/A# Please see the documentation at
883N/A# for further details before you try to setup virtual hosts.
883N/A# You may use the command line option '-S' to verify your virtual host