upgrading.html.en revision fcd7f1f7d11d39b8379972a455e1c7e67a5dfa9d
b66914021bd429f41311d2909a7e9289866da7fdnd<?xml version="1.0" encoding="ISO-8859-1"?>
b51bf223f42d43ca6b1b33c95124edcfa5a871a4nd<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
9963f91528694fb21e93da8584c31f226c6de97akess<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en"><head><!--
b66914021bd429f41311d2909a7e9289866da7fdnd XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
b66914021bd429f41311d2909a7e9289866da7fdnd This file is generated from xml source: DO NOT EDIT
08cb74ca432a8c24e39f17dedce527e6a47b8001jerenkrantz XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
08cb74ca432a8c24e39f17dedce527e6a47b8001jerenkrantz -->
b66914021bd429f41311d2909a7e9289866da7fdnd<title>Upgrading to 2.4 from 2.2 - Apache HTTP Server</title>
b66914021bd429f41311d2909a7e9289866da7fdnd<link href="/style/css/manual.css" rel="stylesheet" media="all" type="text/css" title="Main stylesheet" />
b66914021bd429f41311d2909a7e9289866da7fdnd<link href="/style/css/manual-loose-100pc.css" rel="alternate stylesheet" media="all" type="text/css" title="No Sidebar - Default font size" />
b66914021bd429f41311d2909a7e9289866da7fdnd<link href="/style/css/manual-print.css" rel="stylesheet" media="print" type="text/css" />
b66914021bd429f41311d2909a7e9289866da7fdnd<link href="/images/favicon.ico" rel="shortcut icon" /></head>
b66914021bd429f41311d2909a7e9289866da7fdnd<body id="manual-page"><div id="page-header">
b66914021bd429f41311d2909a7e9289866da7fdnd<p class="menu"><a href="/mod/">Modules</a> | <a href="/mod/directives.html">Directives</a> | <a href="/faq/">FAQ</a> | <a href="/glossary.html">Glossary</a> | <a href="/sitemap.html">Sitemap</a></p>
b66914021bd429f41311d2909a7e9289866da7fdnd<p class="apache">Apache HTTP Server Version 2.3</p>
b66914021bd429f41311d2909a7e9289866da7fdnd<img alt="" src="/images/feather.gif" /></div>
b66914021bd429f41311d2909a7e9289866da7fdnd<div class="up"><a href="./"><img title="&lt;-" alt="&lt;-" src="/images/left.gif" /></a></div>
b66914021bd429f41311d2909a7e9289866da7fdnd<div id="path">
b66914021bd429f41311d2909a7e9289866da7fdnd<a href="http://www.apache.org/">Apache</a> &gt; <a href="http://httpd.apache.org/">HTTP Server</a> &gt; <a href="http://httpd.apache.org/docs/">Documentation</a> &gt; <a href="./">Version 2.3</a></div><div id="page-content"><div id="preamble"><h1>Upgrading to 2.4 from 2.2</h1>
b66914021bd429f41311d2909a7e9289866da7fdnd<div class="toplang">
b66914021bd429f41311d2909a7e9289866da7fdnd<p><span>Available Languages: </span><a href="/en/upgrading.html" title="English">&nbsp;en&nbsp;</a> |
eed2a23d9b5986937f1e2b1c120be97744508a72nd<a href="/fr/upgrading.html" hreflang="fr" rel="alternate" title="Fran�ais">&nbsp;fr&nbsp;</a></p>
eed2a23d9b5986937f1e2b1c120be97744508a72nd</div>
eed2a23d9b5986937f1e2b1c120be97744508a72nd
eed2a23d9b5986937f1e2b1c120be97744508a72nd <p>In order to assist folks upgrading, we maintain a document
eed2a23d9b5986937f1e2b1c120be97744508a72nd describing information critical to existing Apache HTTP Server users. These
eed2a23d9b5986937f1e2b1c120be97744508a72nd are intended to be brief notes, and you should be able to find
eed2a23d9b5986937f1e2b1c120be97744508a72nd more information in either the <a href="new_features_2_4.html">New Features</a> document, or in
eed2a23d9b5986937f1e2b1c120be97744508a72nd the <code>src/CHANGES</code> file. Application and module developers
eed2a23d9b5986937f1e2b1c120be97744508a72nd can find a summary of API changes in the <a href="developer/new_api_2_4.html">API updates</a> overview.</p>
eed2a23d9b5986937f1e2b1c120be97744508a72nd
eed2a23d9b5986937f1e2b1c120be97744508a72nd <p>This document describes changes in server behavior that might
eed2a23d9b5986937f1e2b1c120be97744508a72nd require you to change your configuration or how you use the server
eed2a23d9b5986937f1e2b1c120be97744508a72nd in order to continue using 2.4 as you are currently using 2.2.
eed2a23d9b5986937f1e2b1c120be97744508a72nd To take advantage of new features in 2.4, see the New Features
eed2a23d9b5986937f1e2b1c120be97744508a72nd document.</p>
eed2a23d9b5986937f1e2b1c120be97744508a72nd
eed2a23d9b5986937f1e2b1c120be97744508a72nd <p>This document describes only the changes from 2.2 to 2.4. If you
eed2a23d9b5986937f1e2b1c120be97744508a72nd are upgrading from version 2.0, you should also consult the <a href="http://httpd.apache.org/docs/2.2/upgrading.html">2.0 to 2.2
eed2a23d9b5986937f1e2b1c120be97744508a72nd upgrading document.</a></p>
eed2a23d9b5986937f1e2b1c120be97744508a72nd
eed2a23d9b5986937f1e2b1c120be97744508a72nd</div>
eed2a23d9b5986937f1e2b1c120be97744508a72nd<div id="quickview"><ul id="toc"><li><img alt="" src="/images/down.gif" /> <a href="#compile-time">Compile-Time Configuration Changes</a></li>
eed2a23d9b5986937f1e2b1c120be97744508a72nd<li><img alt="" src="/images/down.gif" /> <a href="#run-time">Run-Time Configuration Changes</a></li>
eed2a23d9b5986937f1e2b1c120be97744508a72nd<li><img alt="" src="/images/down.gif" /> <a href="#misc">Misc Changes</a></li>
eed2a23d9b5986937f1e2b1c120be97744508a72nd<li><img alt="" src="/images/down.gif" /> <a href="#third-party">Third Party Modules</a></li>
eed2a23d9b5986937f1e2b1c120be97744508a72nd<li><img alt="" src="/images/down.gif" /> <a href="#commonproblems">Common problems when upgrading</a></li>
eed2a23d9b5986937f1e2b1c120be97744508a72nd</ul><h3>See also</h3><ul class="seealso"><li><a href="new_features_2_4.html">Overview of new features in
eed2a23d9b5986937f1e2b1c120be97744508a72nd Apache HTTP Server 2.4</a></li></ul></div>
eed2a23d9b5986937f1e2b1c120be97744508a72nd<div class="top"><a href="#page-header"><img alt="top" src="/images/up.gif" /></a></div>
eed2a23d9b5986937f1e2b1c120be97744508a72nd<div class="section">
eed2a23d9b5986937f1e2b1c120be97744508a72nd<h2><a name="compile-time" id="compile-time">Compile-Time Configuration Changes</a></h2>
eed2a23d9b5986937f1e2b1c120be97744508a72nd
eed2a23d9b5986937f1e2b1c120be97744508a72nd
eed2a23d9b5986937f1e2b1c120be97744508a72nd <p>The compilation process is very similar to the one used in
eed2a23d9b5986937f1e2b1c120be97744508a72nd version 2.2. Your old <code>configure</code> command line (as
eed2a23d9b5986937f1e2b1c120be97744508a72nd found in <code>build/config.nice</code> in the installed server
eed2a23d9b5986937f1e2b1c120be97744508a72nd directory) can be used in most cases. There are some changes in
eed2a23d9b5986937f1e2b1c120be97744508a72nd the default settings. Some details of changes:</p>
eed2a23d9b5986937f1e2b1c120be97744508a72nd
eed2a23d9b5986937f1e2b1c120be97744508a72nd <ul>
eed2a23d9b5986937f1e2b1c120be97744508a72nd <li>These modules have been removed: mod_authn_default,
eed2a23d9b5986937f1e2b1c120be97744508a72nd mod_authz_default, mod_mem_cache. If you were using
eed2a23d9b5986937f1e2b1c120be97744508a72nd mod_mem_cache in 2.2, look at <code class="module"><a href="/mod/mod_cache_disk.html">mod_cache_disk</a></code> in
eed2a23d9b5986937f1e2b1c120be97744508a72nd 2.4.</li>
eed2a23d9b5986937f1e2b1c120be97744508a72nd
eed2a23d9b5986937f1e2b1c120be97744508a72nd <li>All load balancing implementations have been moved to
eed2a23d9b5986937f1e2b1c120be97744508a72nd individual, self-contained mod_proxy submodules, e.g.
eed2a23d9b5986937f1e2b1c120be97744508a72nd <code class="module"><a href="/mod/mod_lbmethod_bybusyness.html">mod_lbmethod_bybusyness</a></code>. You might need
eed2a23d9b5986937f1e2b1c120be97744508a72nd to build and load any of these that your configuration
eed2a23d9b5986937f1e2b1c120be97744508a72nd uses.</li>
eed2a23d9b5986937f1e2b1c120be97744508a72nd
bcf004854091600aa279525d6772e1827114d39dnd <li>Platform support has been removed for BeOS, TPF, and
eed2a23d9b5986937f1e2b1c120be97744508a72nd even older platforms such as A/UX, Next, and Tandem. These were
eed2a23d9b5986937f1e2b1c120be97744508a72nd believed to be broken anyway.</li>
eed2a23d9b5986937f1e2b1c120be97744508a72nd
eed2a23d9b5986937f1e2b1c120be97744508a72nd <li>configure: dynamic modules (DSO) are built by default</li>
eed2a23d9b5986937f1e2b1c120be97744508a72nd
eed2a23d9b5986937f1e2b1c120be97744508a72nd <li>configure: the "most" module set gets built by default</li>
eed2a23d9b5986937f1e2b1c120be97744508a72nd </ul>
eed2a23d9b5986937f1e2b1c120be97744508a72nd
eed2a23d9b5986937f1e2b1c120be97744508a72nd </div><div class="top"><a href="#page-header"><img alt="top" src="/images/up.gif" /></a></div>
eed2a23d9b5986937f1e2b1c120be97744508a72nd<div class="section">
eed2a23d9b5986937f1e2b1c120be97744508a72nd<h2><a name="run-time" id="run-time">Run-Time Configuration Changes</a></h2>
eed2a23d9b5986937f1e2b1c120be97744508a72nd
eed2a23d9b5986937f1e2b1c120be97744508a72nd <p>There have been significant changes in authorization configuration,
eed2a23d9b5986937f1e2b1c120be97744508a72nd and other minor configuration changes, that could require changes to your 2.2
eed2a23d9b5986937f1e2b1c120be97744508a72nd configuration files before using them for 2.4.</p>
eed2a23d9b5986937f1e2b1c120be97744508a72nd
eed2a23d9b5986937f1e2b1c120be97744508a72nd <h3><a name="authz" id="authz">Authorization</a></h3>
eed2a23d9b5986937f1e2b1c120be97744508a72nd
eed2a23d9b5986937f1e2b1c120be97744508a72nd
eed2a23d9b5986937f1e2b1c120be97744508a72nd <p>Any configuration file that uses authorization will likely
eed2a23d9b5986937f1e2b1c120be97744508a72nd need changes.</p>
eed2a23d9b5986937f1e2b1c120be97744508a72nd
9963f91528694fb21e93da8584c31f226c6de97akess <p>You should review the <a href="howto/auth.html">Authentication,
bcf004854091600aa279525d6772e1827114d39dnd Authorization and Access Control Howto</a>, especially the section
9963f91528694fb21e93da8584c31f226c6de97akess <a href="howto/auth.html#beyond">Beyond just authorization</a>
eed2a23d9b5986937f1e2b1c120be97744508a72nd which explains the new mechanisms for controlling the order in
eed2a23d9b5986937f1e2b1c120be97744508a72nd which the authorization directives are applied.</p>
b51bf223f42d43ca6b1b33c95124edcfa5a871a4nd
b51bf223f42d43ca6b1b33c95124edcfa5a871a4nd <h4><a name="access" id="access">Access control</a></h4>
eed2a23d9b5986937f1e2b1c120be97744508a72nd
eed2a23d9b5986937f1e2b1c120be97744508a72nd
eed2a23d9b5986937f1e2b1c120be97744508a72nd <p>In 2.2, access control based on client hostname, IP address,
eed2a23d9b5986937f1e2b1c120be97744508a72nd and other characteristics of client requests was done using the
eed2a23d9b5986937f1e2b1c120be97744508a72nd directives <code class="directive"><a href="/mod/mod_access_compat.html#order">Order</a></code>, <code class="directive"><a href="/mod/mod_access_compat.html#allow">Allow</a></code>, <code class="directive"><a href="/mod/mod_access_compat.html#deny">Deny</a></code>, and <code class="directive"><a href="/mod/mod_access_compat.html#satisfy">Satisfy</a></code>.</p>
eed2a23d9b5986937f1e2b1c120be97744508a72nd
eed2a23d9b5986937f1e2b1c120be97744508a72nd <p>In 2.4, such access control is done in the same way as other
eed2a23d9b5986937f1e2b1c120be97744508a72nd authorization checks, using the new module
eed2a23d9b5986937f1e2b1c120be97744508a72nd <code class="module"><a href="/mod/mod_authz_host.html">mod_authz_host</a></code>. The old access control idioms
b51bf223f42d43ca6b1b33c95124edcfa5a871a4nd should be replaced by the new authentication mechanisms,
eed2a23d9b5986937f1e2b1c120be97744508a72nd although for compatibility with old configurations, the new
eed2a23d9b5986937f1e2b1c120be97744508a72nd module <code class="module"><a href="/mod/mod_access_compat.html">mod_access_compat</a></code> is provided.</p>
eed2a23d9b5986937f1e2b1c120be97744508a72nd
eed2a23d9b5986937f1e2b1c120be97744508a72nd <p>Here are some examples of old and new ways to do the same
eed2a23d9b5986937f1e2b1c120be97744508a72nd access control.</p>
eed2a23d9b5986937f1e2b1c120be97744508a72nd
eed2a23d9b5986937f1e2b1c120be97744508a72nd <p>In this example, all requests are denied.</p>
eed2a23d9b5986937f1e2b1c120be97744508a72nd <div class="example"><h3>2.2 configuration:</h3><p><code>
eed2a23d9b5986937f1e2b1c120be97744508a72nd
eed2a23d9b5986937f1e2b1c120be97744508a72nd Order deny,allow<br />
eed2a23d9b5986937f1e2b1c120be97744508a72nd Deny from all
eed2a23d9b5986937f1e2b1c120be97744508a72nd </code></p></div>
eed2a23d9b5986937f1e2b1c120be97744508a72nd <div class="example"><h3>2.4 configuration:</h3><p><code>
eed2a23d9b5986937f1e2b1c120be97744508a72nd
eed2a23d9b5986937f1e2b1c120be97744508a72nd Require all denied
eed2a23d9b5986937f1e2b1c120be97744508a72nd </code></p></div>
eed2a23d9b5986937f1e2b1c120be97744508a72nd
eed2a23d9b5986937f1e2b1c120be97744508a72nd <p>In this example, all requests are allowed.</p>
<div class="example"><h3>2.2 configuration:</h3><p><code>
Order allow,deny<br />
Allow from all
</code></p></div>
<div class="example"><h3>2.4 configuration:</h3><p><code>
Require all granted
</code></p></div>
<p>In the following example, all hosts in the example.org domain
are allowed access; all other hosts are denied access.</p>
<div class="example"><h3>2.2 configuration:</h3><p><code>
Order Deny,Allow<br />
Deny from all<br />
Allow from example.org
</code></p></div>
<div class="example"><h3>2.4 configuration:</h3><p><code>
Require host example.org
</code></p></div>
<h3><a name="config" id="config">Other configuration changes</a></h3>
<p>Some other small adjustments may be necessary for particular
configurations as discussed below.</p>
<ul>
<li><code class="directive">MaxRequestsPerChild</code> has been renamed to
<code class="directive"><a href="/mod/mpm_common.html#maxconnectionsperchild">MaxConnectionsPerChild</a></code>,
which describes more accurately what it does.</li>
<li>The <code class="directive"><a href="/mod/core.html#defaulttype">DefaultType</a></code>
directive no longer has any effect, other than to emit a
warning if it's used with any value other than
<code>none</code>. You need to use other configuration
settings to replace it in 2.4.
</li>
<li><code class="directive"><a href="/mod/core.html#enablesendfile">EnableSendfile</a></code> now
defaults to Off.</li>
<li><code class="module"><a href="/mod/mod_log_config.html">mod_log_config</a></code>: <a href="modules/mod_log_config.html#formats">${cookie}C</a>
matches whole cookie names. Previously any substring would
match.</li>
<li><code class="module"><a href="/mod/mod_dav_fs.html">mod_dav_fs</a></code>: The format of the <code class="directive"><a href="/mod/dav_fs.html#davlockdb">DavLockDB</a></code> file has changed for
systems with inodes. The old <code class="directive"><a href="/mod/dav_fs.html#davlockdb">DavLockDB</a></code> file must be deleted on
upgrade.
</li>
<li><code class="directive"><a href="/mod/core.html#keepalive">KeepAlive</a></code> only
accepts values of <code>On</code> or <code>Off</code>.
Previously, any value other than "Off" or "0" was treated as
"On".</li>
<li>Directives AcceptMutex, LockFile, RewriteLock, SSLMutex,
SSLStaplingMutex, and WatchdogMutexPath have been replaced
with a single <code class="directive"><a href="/mod/core.html#mutex">Mutex</a></code>
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 <code class="directive"><a href="/mod/core.html#mutex">Mutex</a></code>.</li>
<li><code class="module"><a href="/mod/mod_cache.html">mod_cache</a></code>: <code class="directive"><a href="/mod/cache.html#cacheignoreurlsessionidentifiers">CacheIgnoreURLSessionIdentifiers</a></code>
now does an exact match against the query string instead of a
partial match. If your configuration was using partial
strings, e.g. using <code>sessionid</code> to match
<code>/someapplication/image.gif;jsessionid=123456789</code>,
then you will need to change to the full string
<code>jsessionid</code>.
</li>
<li><code class="module"><a href="/mod/mod_ldap.html">mod_ldap</a></code>: <code class="directive"><a href="/mod/ldap.html#ldaptrustedclientcert">LDAPTrustedClientCert</a></code> 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.</li>
<li><code class="module"><a href="/mod/mod_filter.html">mod_filter</a></code>: <code class="directive"><a href="/mod/filter.html#filterprovider">FilterProvider</a></code> syntax has changed and
now uses a boolean expression to determine if a filter is applied.
</li>
<li><code class="module"><a href="/mod/mod_include.html">mod_include</a></code>:
<ul>
<li>The <code>#if expr</code> element now uses the new <a href="expr.html">expression parser</a>. The old syntax can be
restored with the new directive <code class="directive"><a href="/mod/include.html#ssilegacyexprparser">SSILegacyExprParser</a></code>.
</li>
<li>An SSI* config directive in directory scope no longer causes
all other per-directory SSI* directives to be reset to their
default values.</li>
</ul>
</li>
</ul>
</div><div class="top"><a href="#page-header"><img alt="top" src="/images/up.gif" /></a></div>
<div class="section">
<h2><a name="misc" id="misc">Misc Changes</a></h2>
<ul>
<li><code class="module"><a href="/mod/mod_autoindex.html">mod_autoindex</a></code>: will now extract titles and
display descriptions for .xhtml files, which were previously
ignored.</li>
<li><code class="module"><a href="/mod/mod_ssl.html">mod_ssl</a></code>: The default format of the <code>*_DN</code>
variables has changed. The old format can still be used with the new
<code>LegacyDNStringFormat</code> argument to <code class="directive"><a href="/mod/mod_ssl.html#ssloptions">SSLOptions</a></code>.</li>
<li><code class="program"><a href="/programs/htpasswd.html">htpasswd</a></code> now uses MD5 hash by default on
all platforms.</li>
<li>The <code class="directive"><a href="/mod/core.html#namevirtualhost">NameVirtualHost</a></code>
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.
</li>
</ul>
</div><div class="top"><a href="#page-header"><img alt="top" src="/images/up.gif" /></a></div>
<div class="section">
<h2><a name="third-party" id="third-party">Third Party Modules</a></h2>
<p>All modules must be recompiled for 2.4 before being loaded.</p>
<p>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 <a href="developer/new_api_2_4.html">API
update</a> overview.</p>
</div><div class="top"><a href="#page-header"><img alt="top" src="/images/up.gif" /></a></div>
<div class="section">
<h2><a name="commonproblems" id="commonproblems">Common problems when upgrading</a></h2>
<ul><li>Startup errors:
<ul>
<li><code>Invalid command 'User', perhaps misspelled or defined by a module not included in the server configuration</code> - load module <code class="module"><a href="/mod/mod_unixd.html">mod_unixd</a></code></li>
<li><code>Invalid command 'Require', perhaps misspelled or defined by a module not included in the server configuration</code>, or
<code>Invalid command 'Order', perhaps misspelled or defined by a module not included in the server configuration</code>
- load module <code class="module"><a href="/mod/mod_access_compat.html">mod_access_compat</a></code>, or update configuration to 2.4 authorization directives.</li>
<li><code>Ignoring deprecated use of DefaultType in line NN of /path/to/httpd.conf</code> - remove <code class="directive"><a href="/mod/core.html#defaulttype">DefaultType</a></code>
and replace with other configuration settings.</li>
</ul></li>
<li>Errors serving requests:
<ul>
<li><code>configuration error: couldn't check user: /path</code> -
load module <code class="module"><a href="/mod/mod_authn_core.html">mod_authn_core</a></code>.</li>
</ul>
</li>
</ul>
</div></div>
<div class="bottomlang">
<p><span>Available Languages: </span><a href="/en/upgrading.html" title="English">&nbsp;en&nbsp;</a> |
<a href="/fr/upgrading.html" hreflang="fr" rel="alternate" title="Fran�ais">&nbsp;fr&nbsp;</a></p>
</div><div id="footer">
<p class="apache">Copyright 2011 The Apache Software Foundation.<br />Licensed under the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.</p>
<p class="menu"><a href="/mod/">Modules</a> | <a href="/mod/directives.html">Directives</a> | <a href="/faq/">FAQ</a> | <a href="/glossary.html">Glossary</a> | <a href="/sitemap.html">Sitemap</a></p></div>
</body></html>