Chapter 10. Apache HTTP Server
/etc/httpd/conf/httpd.conf) to aid those who require a custom configuration or need to convert a configuration file from the older Apache HTTP Server 1.3 format.
system-config-httpd), do not hand edit the Apache HTTP Server's configuration file as the HTTP Configuration Tool regenerates this file whenever it is used.
10.1. Apache HTTP Server 2.0
10.1.1. Features of Apache HTTP Server 2.0
- Apache API — Modules utilize a more powerful set of Application Programming Interfaces (APIs).
ImportantModules built for Apache HTTP Server 1.3 do not work without being ported to the new API. If unsure whether or not a particular module has been ported, consult the developer before upgrading.
- Filtering — Modules can act as content filters. Refer to Section 10.2.4, “Modules and Apache HTTP Server 2.0” for more on how filtering works.
- IPv6 Support — The next generation IP addressing format is supported.
- Simplified Directives — A number of confusing directives have been removed while others have been simplified. Refer to Section 10.5, “Configuration Directives in
httpd.conf” for more information about specific directives.
- Multilingual Error Responses — When using Server Side Include (SSI) documents, customizable error response pages can be delivered in multiple languages.
10.1.2. Packaging Changes in Apache HTTP Server 2.0
apache-manualpackages were renamed to
mod_davpackage was incorporated into the
mod_roamingpackages were removed, since their functionality is a subset of that provided by
mod_dav(which is now incorporated into the
mod_bandwidthpackages were removed.
- The version number for the
mod_sslpackage is now synchronized with the
httpdpackage. This means that the
mod_sslpackage for Apache HTTP Server 2.0 has a lower version number than
mod_sslpackage for Apache HTTP Server 1.3.
10.1.3. File System Changes in Apache HTTP Server 2.0
- The configuration directory,
/etc/httpd/conf.d/, has been added. — This directory is used to store configuration files for individually packaged modules, such as
php. The server is instructed to load configuration files from this location by the directive
Include conf.d/*.confwithin the Apache HTTP Server configuration file,
ImportantIt is vital that the line specifying the new configuration directory be inserted when migrating an existing configuration.
logresolveprograms have been moved. — These utility programs have been moved from the
/usr/sbin/directory and into the
/usr/bin/directory. This causes scripts with absolute paths for these binaries to fail.
dbmmanagecommand has been replaced. — The
dbmmanagecommand has been replaced by
htdbm. Refer to Section 10.2.4.5, “The
mod_auth_dbModules” for more information.
logrotateconfiguration file has been renamed. — The
logrotateconfiguration file has been renamed from