upgrading.html.en revision 43365cc9aaf2bea5be539bea80c5eb7c926ce148
<?xml version="1.0" encoding="ISO-8859-1"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
This file is generated from xml source: DO NOT EDIT
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-->
<title>Upgrading to 2.4 from 2.2 - Apache HTTP Server</title>
<link href="/style/css/manual.css" rel="stylesheet" media="all" type="text/css" title="Main stylesheet" />
<link href="/style/css/manual-loose-100pc.css" rel="alternate stylesheet" media="all" type="text/css" title="No Sidebar - Default font size" />
<link href="/style/css/manual-print.css" rel="stylesheet" media="print" type="text/css" /><link rel="stylesheet" type="text/css" href="/style/css/prettify.css" />
</script>
<body id="manual-page"><div id="page-header">
<p class="menu"><a href="/mod/">Modules</a> | <a href="/mod/directives.html">Directives</a> | <a href="http://wiki.apache.org/httpd/FAQ">FAQ</a> | <a href="/glossary.html">Glossary</a> | <a href="/sitemap.html">Sitemap</a></p>
<p class="apache">Apache HTTP Server Version 2.5</p>
<div id="path">
<a href="http://www.apache.org/">Apache</a> > <a href="http://httpd.apache.org/">HTTP Server</a> > <a href="http://httpd.apache.org/docs/">Documentation</a> > <a href="./">Version 2.5</a></div><div id="page-content"><div id="preamble"><h1>Upgrading to 2.4 from 2.2</h1>
<div class="toplang">
<p><span>Available Languages: </span><a href="/en/upgrading.html" title="English"> en </a> |
</div>
<p>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
can find a summary of API changes in the <a href="developer/new_api_2_4.html">API updates</a> overview.</p>
<p>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.</p>
<p>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 <a href="http://httpd.apache.org/docs/2.2/upgrading.html">2.0 to 2.2
upgrading document.</a></p>
</div>
<div id="quickview"><ul id="toc"><li><img alt="" src="/images/down.gif" /> <a href="#compile-time">Compile-Time Configuration Changes</a></li>
<li><img alt="" src="/images/down.gif" /> <a href="#run-time">Run-Time Configuration Changes</a></li>
<li><img alt="" src="/images/down.gif" /> <a href="#commonproblems">Common problems when upgrading</a></li>
</ul><h3>See also</h3><ul class="seealso"><li><a href="new_features_2_4.html">Overview of new features in
Apache HTTP Server 2.4</a></li></ul><ul class="seealso"><li><a href="#comments_section">Comments</a></li></ul></div>
<div class="section">
<h2><a name="compile-time" id="compile-time">Compile-Time Configuration Changes</a></h2>
<p>The compilation process is very similar to the one used in
version 2.2. Your old <code>configure</code> command line (as
directory) can be used in most cases. There are some changes in
the default settings. Some details of changes:</p>
<ul>
<li>These modules have been removed: mod_authn_default,
mod_authz_default, mod_mem_cache. If you were using
mod_mem_cache in 2.2, look at <code class="module"><a href="/mod/mod_cache_disk.html">mod_cache_disk</a></code> in
2.4.</li>
<li>All load balancing implementations have been moved to
individual, self-contained mod_proxy submodules, e.g.
<code class="module"><a href="/mod/mod_lbmethod_bybusyness.html">mod_lbmethod_bybusyness</a></code>. You might need
to build and load any of these that your configuration
uses.</li>
<li>Platform support has been removed for BeOS, TPF, and
believed to be broken anyway.</li>
<li>configure: dynamic modules (DSO) are built by default</li>
<li>configure: By default, only a basic set of modules is loaded. The
other <code class="directive">LoadModule</code> directives are commented
out.</li>
<li>configure: the "most" module set gets built by default</li>
<li>configure: the "reallyall" module set adds developer modules
to the "all" set</li>
</ul>
<div class="section">
<h2><a name="run-time" id="run-time">Run-Time Configuration Changes</a></h2>
<p>There have been significant changes in authorization configuration,
and other minor configuration changes, that could require changes to your 2.2
configuration files before using them for 2.4.</p>
<h3><a name="authz" id="authz">Authorization</a></h3>
<p>Any configuration file that uses authorization will likely
need changes.</p>
Authorization and Access Control Howto</a>, especially the section
which explains the new mechanisms for controlling the order in
which the authorization directives are applied.</p>
<h4><a name="access" id="access">Access control</a></h4>
<p>In 2.2, access control based on client hostname, IP address,
and other characteristics of client requests was done using the
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>
<p>In 2.4, such access control is done in the same way as other
authorization checks, using the new module
<code class="module"><a href="/mod/mod_authz_host.html">mod_authz_host</a></code>. The old access control idioms
should be replaced by the new authentication mechanisms,
although for compatibility with old configurations, the new
module <code class="module"><a href="/mod/mod_access_compat.html">mod_access_compat</a></code> is provided.</p>
<p>Here are some examples of old and new ways to do the same
access control.</p>
<p>In this example, all requests are denied.</p>
<div class="example"><h3>2.2 configuration:</h3><pre class="prettyprint lang-config">
Order deny,allow
Deny from all
</pre>
</div>
<div class="example"><h3>2.4 configuration:</h3><pre class="prettyprint lang-config">
Require all denied
</pre>
</div>
<p>In this example, all requests are allowed.</p>
<div class="example"><h3>2.2 configuration:</h3><pre class="prettyprint lang-config">
Order allow,deny
Allow from all
</pre>
</div>
<div class="example"><h3>2.4 configuration:</h3><pre class="prettyprint lang-config">
Require all granted
</pre>
</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><pre class="prettyprint lang-config">
Order Deny,Allow
Deny from all
Allow from example.org
</pre>
</div>
<div class="example"><h3>2.4 configuration:</h3><pre class="prettyprint lang-config">
Require host example.org
</pre>
</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>,
describes more accurately what it does. The old name is still
supported.</li>
<li><code class="directive">MaxClients</code> has been renamed to
<code class="directive"><a href="/mod/mpm_common.html#maxrequestworkers">MaxRequestWorkers</a></code>,
which describes more accurately what it does. For async MPMs, like
<code class="module"><a href="/mod/event.html">event</a></code>, the maximum number of clients is not
equivalent than the number of worker threads. The old name is still
supported.</li>
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>
defaults to Off.</li>
defaults to "MTime Size" (without INode).</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/mod_dav_fs.html#davlockdb">DavLockDB</a></code> file has changed for
systems with inodes. The old <code class="directive"><a href="/mod/mod_dav_fs.html#davlockdb">DavLockDB</a></code> file must be deleted on
upgrade.
</li>
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
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/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
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/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/mod_filter.html#filterprovider">FilterProvider</a></code> syntax has changed and
now uses a boolean expression to determine if a filter is applied.
</li>
<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/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>
<li><code class="module"><a href="/mod/mod_charset_lite.html">mod_charset_lite</a></code>: The <code>DebugLevel</code>
option has been removed in favour of per-module <code class="directive"><a href="/mod/core.html#loglevel">LogLevel</a></code> configuration.
</li>
<li><code class="module"><a href="/mod/mod_ext_filter.html">mod_ext_filter</a></code>: The <code>DebugLevel</code>
option has been removed in favour of per-module <code class="directive"><a href="/mod/core.html#loglevel">LogLevel</a></code> configuration.
</li>
<li><code class="module"><a href="/mod/mod_ssl.html">mod_ssl</a></code>: CRL based revocation checking
now needs to be explicitly configured through <code class="directive"><a href="/mod/mod_ssl.html#sslcarevocationcheck">SSLCARevocationCheck</a></code>.
</li>
<li><code class="module"><a href="/mod/mod_substitute.html">mod_substitute</a></code>: The maximum line length is now
limited to 1MB.
</li>
<li><code class="module"><a href="/mod/mod_reqtimeout.html">mod_reqtimeout</a></code>: If the module is loaded, it
will now set some default timeouts.</li>
</ul>
<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>. The SSLv2 protocol is
no longer supported. <code class="directive"><a href="/mod/mod_ssl.html#sslproxycheckpeercn 	 ">SSLProxyCheckPeerCN
</a></code> and <code class="directive"><a href="/mod/mod_ssl.html#sslproxycheckpeerexpire 	 ">SSLProxyCheckPeerExpire
</a></code> now default to On, causing proxy requests to HTTPS hosts
with bad or outdated certificates to fail with a 502 status code (Bad
gateway)</li>
<li><code class="program"><a href="/programs/htpasswd.html">htpasswd</a></code> now uses MD5 hash by default on
all platforms.</li>
directive no longer has any effect, other than to emit a
virtual hosts is implicitly treated as a name-based virtual host.
</li>
<li><code class="module"><a href="/mod/mod_deflate.html">mod_deflate</a></code> will now skip compression if it knows
that the size overhead added by the compression is larger than the data
to be compressed.
</li>
<li>Multi-language error documents from 2.2.x may not work unless
they are adjusted to the new syntax of <code class="module"><a href="/mod/mod_include.html">mod_include</a></code>'s
<code>#if expr=</code> element or the directive
<code class="directive"><a href="/mod/mod_include.html#ssilegacyexprparser">SSILegacyExprParser</a></code> is
enabled for the directory containing the error documents.
</li>
<li>The functionality provided by <code>mod_authn_alias</code>
in previous versions (i.e., the <code class="directive"><a href="/mod/mod_authn_core.html#authnprovideralias">AuthnProviderAlias</a></code> directive)
has been moved into <code class="module"><a href="/mod/mod_authn_core.html">mod_authn_core</a></code>.
</li>
</ul>
<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 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> -
</ul>
</li>
</ul>
</div></div>
<div class="bottomlang">
<p><span>Available Languages: </span><a href="/en/upgrading.html" title="English"> en </a> |
</div><div class="top"><a href="#page-header"><img src="/images/up.gif" alt="top" /></a></div><div class="section"><h2><a id="comments_section" name="comments_section">Comments</a></h2><div class="warning"><strong>Notice:</strong><br />This is not a Q&A section. Comments placed here should be pointed towards suggestions on improving the documentation or server, and may be removed again by our moderators if they are either implemented or considered invalid/off-topic. Questions on how to manage the Apache HTTP Server should be directed at either our IRC channel, #httpd, on Freenode, or sent to our <a href="http://httpd.apache.org/lists.html">mailing lists</a>.</div>
var comments_shortname = 'httpd';
var comments_identifier = 'http://httpd.apache.org/docs/trunk/upgrading.html';
(function(w, d) {
if (w.location.hostname.toLowerCase() == "httpd.apache.org") {
d.write('<div id="comments_thread"><\/div>');
var s = d.createElement('script');
s.type = 'text/javascript';
s.async = true;
s.src = 'https://comments.apache.org/show_comments.lua?site=' + comments_shortname + '&page=' + comments_identifier;
(d.getElementsByTagName('head')[0] || d.getElementsByTagName('body')[0]).appendChild(s);
}
else {
d.write('<div id="comments_thread">Comments are disabled for this page at the moment.<\/div>');
}
})(window, document);
//--><!]]></script></div><div id="footer">
<p class="apache">Copyright 2012 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="http://wiki.apache.org/httpd/FAQ">FAQ</a> | <a href="/glossary.html">Glossary</a> | <a href="/sitemap.html">Sitemap</a></p></div><script type="text/javascript"><!--//--><![CDATA[//><!--
if (typeof(prettyPrint) !== 'undefined') {
prettyPrint();
}
//--><!]]></script>
</body></html>