Upgrading to 2.4 from 2.2

In order to assist folks upgrading, we maintain a document describing information critical to existing Apache HTTP Server users. These are intended to be brief notes, and you should be able to find more information in either the New Features document, or in the src/CHANGES

file. Application and module developers can find a summary of API changes in the API updates overview.

This document describes changes in server behavior that might require you to change your configuration or how you use the server in order to continue using 2.4 as you are currently using 2.2. To take advantage of new features in 2.4, see the New Features document.

This document describes only the changes from 2.2 to 2.4. If you are upgrading from version 2.0, you should also consult the 2.0 to 2.2 upgrading document.

. You might need to build and load any of these that your configuration uses.LoadModule

You should review the Authentication, Authorization and Access Control Howto, especially the section Beyond just authorization which explains the new mechanisms for controlling the order in which the authorization directives are applied.

Directives that control how authorization modules respond when they don't match the authenticated user have been removed: This includes AuthzLDAPAuthoritative, AuthzDBDAuthoritative, AuthzDBMAuthoritative, AuthzGroupFileAuthoritative, AuthzUserAuthoritative, and AuthzOwnerAuthoritative. These directives have been replaced by the more expressive

, you must port your configuration to use modauthzdbmRequire dbm-group ...

In 2.2, access control based on client hostname, IP address, and other characteristics of client requests was done using the directives

In 2.4, such access control is done in the same way as other authorization checks, using the new module

. The old access control idioms should be replaced by the new authentication mechanisms, although for compatibility with old configurations, the new module modauthzhost

Here are some examples of old and new ways to do the same access control.

In this example, all requests are denied.

Order deny,allow Deny from all

In the following example, all hosts in the example.org domain are allowed access; all other hosts are denied access.

Some other small adjustments may be necessary for particular configurations as discussed below.

has been renamed to MaxConnectionsPerChild

, describes more accurately what it does. The old name is still supported.MaxClients

, which describes more accurately what it does. For async MPMs, like event

, the maximum number of clients is not equivalent than the number of worker threads. The old name is still supported.DefaultType

directive no longer has any effect, other than to emit a warning if it's used with any value other than none

. You need to use other configuration settings to replace it in 2.4. AllowOverride

now defaults to None

now defaults to Off.FileETag

now defaults to "MTime Size" (without INode).moddavfs

: The format of the DavLockDB

file has changed for systems with inodes. The old DavLockDB

file must be deleted on upgrade. KeepAlive

only accepts values of On

. Previously, any value other than "Off" or "0" was treated as "On".Mutex

directive. You will need to evaluate any use of these removed directives in your 2.2 configuration to determine if they can just be deleted or will need to be replaced using Mutex

now does an exact match against the query string instead of a partial match. If your configuration was using partial strings, e.g. using sessionid

to match /someapplication/image.gif;jsessionid=123456789

: The second parameter to CacheEnable

only matches forward proxy content if it begins with the correct protocol. In 2.2 and earlier, a parameter of '/' matched all content.mod_ldap

is now consistently a per-directory setting only. If you use this directive, review your configuration to make sure it is present in all the necessary directory contexts.mod_filter

syntax has changed and now uses a boolean expression to determine if a filter is applied. mod_include

element now uses the new SSILegacyExprParser

option has been removed in favour of per-module LogLevel

: CRL based revocation checking now needs to be explicitly configured through SSLCARevocationCheck

: The maximum line length is now limited to 1MB. mod_reqtimeout

: If the module is loaded, it will now set some default timeouts.mod_dumpio

is no longer supported. Data is always logged at LogLevel

were invoked using /bin/sh -c

in 2.2 and earlier. In 2.4 and later, piped logging commands are executed directly. To restore the old behaviour, see the mod_autoindex

: will now extract titles and display descriptions for .xhtml files, which were previously ignored.mod_ssl

variables has changed. The old format can still be used with the new LegacyDNStringFormat

. The SSLv2 protocol is no longer supported. SSLProxyCheckPeerCN

now default to On, causing proxy requests to HTTPS hosts with bad or outdated certificates to fail with a 502 status code (Bad gateway)htpasswd

now uses MD5 hash by default on all platforms.NameVirtualHost

directive no longer has any effect, other than to emit a warning. Any address/port combination appearing in multiple virtual hosts is implicitly treated as a name-based virtual host. mod_deflate

will now skip compression if it knows that the size overhead added by the compression is larger than the data to be compressed. mod_include

is enabled for the directory containing the error documents. modauthnalias

in previous versions (i.e., the AuthnProviderAlias

directive) has been moved into modauthncore

Many third-party modules designed for version 2.2 will otherwise work unchanged with the Apache HTTP Server version 2.4. Some will require changes; see the API update overview.

Invalid command 'User', perhaps misspelled or defined by a module not included in the server configuration

, or update configuration to 2.4 authorization directives.Ignoring deprecated use of DefaultType in line NN of /path/to/apache2.conf

has moved from the core to mod_filter, which must be loaded.configuration error: couldn't check user: /path

files aren't being processed - Check for an appropriate AllowOverride

Modules | Directives | FAQ | Glossary | Sitemap

Apache HTTP Server Version 2.4