1 <?xml version="1.0" encoding="ISO-8859-1"?>
2 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
3 <html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en"><head><!--
4 XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
5 This file is generated from xml source: DO NOT EDIT
6 XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
8 <title>Upgrading to 2.4 from 2.2 - Apache HTTP Server</title>
9 <link href="./style/css/manual.css" rel="stylesheet" media="all" type="text/css" title="Main stylesheet" />
10 <link href="./style/css/manual-loose-100pc.css" rel="alternate stylesheet" media="all" type="text/css" title="No Sidebar - Default font size" />
11 <link href="./style/css/manual-print.css" rel="stylesheet" media="print" type="text/css" />
12 <link href="./images/favicon.ico" rel="shortcut icon" /></head>
13 <body id="manual-page"><div id="page-header">
14 <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>
15 <p class="apache">Apache HTTP Server Version 2.3</p>
16 <img alt="" src="./images/feather.gif" /></div>
17 <div class="up"><a href="./"><img title="<-" alt="<-" src="./images/left.gif" /></a></div>
19 <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.3</a></div><div id="page-content"><div id="preamble"><h1>Upgrading to 2.4 from 2.2</h1>
21 <p><span>Available Languages: </span><a href="./en/upgrading.html" title="English"> en </a> |
22 <a href="./fr/upgrading.html" hreflang="fr" rel="alternate" title="Français"> fr </a></p>
25 <p>In order to assist folks upgrading, we maintain a document
26 describing information critical to existing Apache HTTP Server users. These
27 are intended to be brief notes, and you should be able to find
28 more information in either the <a href="new_features_2_4.html">New Features</a> document, or in
29 the <code>src/CHANGES</code> file. Application and module developers
30 can find a summary of API changes in the <a href="new_api_2_4.html">API updates</a> overview.</p>
32 <p>This document describes changes in server behavior that might
33 require you to change your configuration or how you use the server
34 in order to continue using 2.4 as you are currently using 2.2.
35 To take advantage of new features in 2.4, see the New Features
38 <p>This document describes only the changes from 2.2 to 2.4. If you
39 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
40 upgrading document.</a></p>
43 <div id="quickview"><ul id="toc"><li><img alt="" src="./images/down.gif" /> <a href="#compile-time">Compile-Time Configuration Changes</a></li>
44 <li><img alt="" src="./images/down.gif" /> <a href="#run-time">Run-Time Configuration Changes</a></li>
45 <li><img alt="" src="./images/down.gif" /> <a href="#misc">Misc Changes</a></li>
46 <li><img alt="" src="./images/down.gif" /> <a href="#third-party">Third Party Modules</a></li>
47 <li><img alt="" src="./images/down.gif" /> <a href="#commonproblems">Common problems when upgrading</a></li>
48 </ul><h3>See also</h3><ul class="seealso"><li><a href="new_features_2_4.html">Overview of new features in
49 Apache HTTP Server 2.4</a></li></ul></div>
50 <div class="top"><a href="#page-header"><img alt="top" src="./images/up.gif" /></a></div>
52 <h2><a name="compile-time" id="compile-time">Compile-Time Configuration Changes</a></h2>
55 <p>The compilation process is very similar to the one used in
56 version 2.2. Your old <code>configure</code> command line (as
57 found in <code>build/config.nice</code> in the installed server
58 directory) can be used in most cases. There are some changes in
59 the default settings. Some details of changes:</p>
62 <li>These modules have been removed: mod_authn_default,
63 mod_authz_default, mod_mem_cache. If you were using
64 mod_mem_cache in 2.2, look at <code class="module"><a href="./mod/mod_disk_cache.html">mod_disk_cache</a></code> in
67 <li>All load balancing implementations have been moved to
68 individual, self-contained mod_proxy submodules, e.g.
69 <code class="module"><a href="./mod/mod_lbmethod_bybusyness.html">mod_lbmethod_bybusyness</a></code>. You might need
70 to build and load any of these that your configuration
73 <li>Platform support has been removed for BeOS, TPF, and
74 even older platforms such as A/UX, Next, and Tandem. These were
75 believed to be broken anyway.</li>
77 <li>configure: dynamic modules (DSO) are built by default</li>
79 <li>configure: the "most" module set gets built by default</li>
82 </div><div class="top"><a href="#page-header"><img alt="top" src="./images/up.gif" /></a></div>
84 <h2><a name="run-time" id="run-time">Run-Time Configuration Changes</a></h2>
86 <p>There have been significant changes in authorization configuration,
87 and other minor configuration changes, that could require changes to your 2.2
88 configuration files before using them for 2.4.</p>
90 <h3><a name="authz" id="authz">Authorization</a></h3>
93 <p>Any configuration file that uses authorization will likely
96 <p>You should review the <a href="howto/auth.html">Authentication,
97 Authorization and Access Control Howto</a>, especially the section
98 <a href="howto/auth.html#beyond">Beyond just authorization</a>
99 which explains the new mechanisms for controlling the order in
100 which the authorization directives are applied.</p>
102 <h4><a name="access" id="access">Access control</a></h4>
105 <p>In 2.2, access control based on client hostname, IP address,
106 and other characteristics of client requests was done using the
107 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>
109 <p>In 2.4, such access control is done in the same way as other
110 authorization checks, using the new module
111 <code class="module"><a href="./mod/mod_authz_host.html">mod_authz_host</a></code>. The old access control idioms
112 should be replaced by the new authentication mechanisms,
113 although for compatibility with old configurations, the new
114 module <code class="module"><a href="./mod/mod_access_compat.html">mod_access_compat</a></code> is provided.</p>
116 <p>Here are some examples of old and new ways to do the same
119 <p>In this example, all requests are denied.</p>
120 <div class="example"><h3>2.2 configuration:</h3><p><code>
122 Order deny,allow<br />
125 <div class="example"><h3>2.4 configuration:</h3><p><code>
130 <p>In this example, all requests are allowed.</p>
131 <div class="example"><h3>2.2 configuration:</h3><p><code>
133 Order allow,deny<br />
136 <div class="example"><h3>2.4 configuration:</h3><p><code>
141 <p>In the following example, all hosts in the apache.org domain
142 are allowed access; all other hosts are denied access.</p>
144 <div class="example"><h3>2.2 configuration:</h3><p><code>
146 Order Deny,Allow<br />
148 Allow from apache.org
150 <div class="example"><h3>2.4 configuration:</h3><p><code>
152 Require host apache.org
158 <h3><a name="config" id="config">Other configuration changes</a></h3>
161 <p>Some other small adjustments may be necessary for particular
162 configurations as discussed below.</p>
165 <li>The <code class="directive"><a href="./mod/core.html#defaulttype">DefaultType</a></code>
166 directive no longer has any effect, other than to emit a
167 warning if it's used with any value other than
168 <code>none</code>. You need to use other configuration
169 settings to replace it in 2.4.
172 <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>
173 matches whole cookie names. Previously any substring would
176 <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
177 systems with inodes. The old <code class="directive"><a href="./mod/dav_fs.html#davlockdb">DavLockDB</a></code> file must be deleted on
181 <li><code class="directive"><a href="./mod/core.html#keepalive">KeepAlive</a></code> only
182 accepts values of <code>On</code> or <code>Off</code>.
183 Previously, any value other than "Off" or "0" was treated as
186 <li>Directives AcceptMutex, LockFile, RewriteLock, SSLMutex,
187 SSLStaplingMutex, and WatchdogMutexPath have been replaced
188 with a single <code class="directive"><a href="./mod/core.html#mutex">Mutex</a></code>
189 directive. You will need to evaluate any use of these removed
190 directives in your 2.2 configuration to determine if they can
191 just be deleted or will need to be replaced using <code class="directive"><a href="./mod/core.html#mutex">Mutex</a></code>.</li>
193 <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>
194 now does an exact match against the query string instead of a
195 partial match. If your configuration was using partial
196 strings, e.g. using <code>sessionid</code> to match
197 <code>/someapplication/image.gif;jsessionid=123456789</code>,
198 then you will need to change to the full string
199 <code>jsessionid</code>.
202 <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
203 consistently a per-directory setting only. If you use this
204 directive, review your configuration to make sure it is
205 present in all the necessary directory contexts.</li>
209 </div><div class="top"><a href="#page-header"><img alt="top" src="./images/up.gif" /></a></div>
210 <div class="section">
211 <h2><a name="misc" id="misc">Misc Changes</a></h2>
215 <li><code class="module"><a href="./mod/mod_auto_index.html">mod_auto_index</a></code>: will now extract titles and
216 display descriptions for .xhtml files, which were previously
218 <li><code class="program"><a href="./programs/htpasswd.html">htpasswd</a></code> now uses MD5 hash by default on
223 </div><div class="top"><a href="#page-header"><img alt="top" src="./images/up.gif" /></a></div>
224 <div class="section">
225 <h2><a name="third-party" id="third-party">Third Party Modules</a></h2>
227 <p>All modules must be recompiled for 2.4 before being loaded.</p>
229 <p>Many third-party modules designed for version 2.2 will
230 otherwise work unchanged with the Apache HTTP Server version 2.4.
231 Some will require changes; see the <a href="new_api_2_4.html">API
232 update</a> overview.</p>
233 </div><div class="top"><a href="#page-header"><img alt="top" src="./images/up.gif" /></a></div>
234 <div class="section">
235 <h2><a name="commonproblems" id="commonproblems">Common problems when upgrading</a></h2>
237 <ul><li>Startup errors:
239 <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>
240 <li><code>Invalid command 'Require', perhaps misspelled or defined by a module not included in the server configuration</code>, or
241 <code>Invalid command 'Order', perhaps misspelled or defined by a module not included in the server configuration</code>
242 - 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>
243 <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>
244 and replace with other configuration settings.</li>
246 <li>Errors serving requests:
248 <li><code>configuration error: couldn't check user: /path</code> -
249 load module <code class="module"><a href="./mod/mod_authn_core.html">mod_authn_core</a></code>.</li>
254 <div class="bottomlang">
255 <p><span>Available Languages: </span><a href="./en/upgrading.html" title="English"> en </a> |
256 <a href="./fr/upgrading.html" hreflang="fr" rel="alternate" title="Français"> fr </a></p>
257 </div><div id="footer">
258 <p class="apache">Copyright 2010 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>
259 <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>