10.1.1. Features of Apache HTTP Server 2.0

Apache HTTP Server 2.0 includes the following features:

• Apache API — Modules utilize a more powerful set of Application Programming Interfaces (APIs).

  	Important
  	Modules 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.

A more complete list of changes can be found online at https://httpd.apache.org/docs-2.0/.

10.1.2. Packaging Changes in Apache HTTP Server 2.0

Starting with Red Hat Enterprise Linux 3, the Apache HTTP Server packages were renamed. Also, some related packages were renamed, deprecated, or incorporated into other packages.

Below is a list of packaging changes:

• The apache, apache-devel and apache-manual packages were renamed to httpd, httpd-devel and httpd-manual respectively.

• The mod_dav package was incorporated into the httpd package.

• The mod_put and mod_roaming packages were removed, since their functionality is a subset of that provided by mod_dav (which is now incorporated into the httpd package).

• The mod_auth_any and mod_bandwidth packages were removed.

• The version number for the mod_ssl package is now synchronized with the httpd package. This means that the mod_ssl package for Apache HTTP Server 2.0 has a lower version number than mod_ssl package for Apache HTTP Server 1.3.

10.1.3. File System Changes in Apache HTTP Server 2.0

The following changes to the file system layout occur when upgrading to 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 mod_ssl, mod_perl, and php. The server is instructed to load configuration files from this location by the directive Include conf.d/*.conf within the Apache HTTP Server configuration file, /etc/httpd/conf/httpd.conf.

  	Important
  	It is vital that the line specifying the new configuration directory be inserted when migrating an existing configuration.

• The ab and logresolve programs 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.

• The dbmmanage command has been replaced. — The dbmmanage command has been replaced by htdbm. Refer to Section 10.2.4.5 The mod_auth_dbm and mod_auth_db Modules for more information.

• The logrotate configuration file has been renamed. — The logrotate configuration file has been renamed from /etc/logrotate.d/apache to /etc/logrotate.d/httpd.

The next section outlines how to migrate an Apache HTTP Server 1.3 configuration to the 2.0 format.