25.2. Migrating Apache HTTP Server Configuration Files
25.2.1. Migrating Apache HTTP Server 2.0 Configuration Files
This section outlines migration from version 2.0 to 2.2. If you are migrating from version 1.3, please refer to Section 25.2.2, “Migrating Apache HTTP Server 1.3 Configuration Files to 2.0”.
- Configuration files and startup scripts from version 2.0 need minor adjustments particularly in module names which may have changed. Third party modules which worked in version 2.0 can also work in version 2.2 but need to be recompiled before you load them. Key modules that need to be noted are authentication and authorization modules. For each of the modules which has been renamed the
LoadModuleline will need to be updated.
mod_userdirmodule will only act on requests if you provide a
UserDirdirective indicating a directory name. If you wish to maintain the procedures used in version 2.0, add the directive
UserDir public_htmlin your configuration file.
- To enable SSL, edit the
httpd.conffile adding the necessary
apachectl startsslis unavailable in version 2.2. You can view an example of SSL configuration for httpd in
- To test your configuration it is advisable to use
service httpd configtestwhich will detect configuration errors.
More information on upgrading from version 2.0 to 2.2 can be found on http://httpd.apache.org/docs/2.2/upgrading.html.
Due to the vulnerability described in POODLE: SSLv3 vulnerability (CVE-2014-3566), Red Hat recommends disabling
SSLand using only
TLSv1.2. Backwards compatibility can be achieved using
TLSv1.0. Many products Red Hat supports have the ability to use
SSLv3protocols, or enable them by default. However, the use of
SSLv3is now strongly recommended against.