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 <meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type" />
6 XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
7 This file is generated from xml source: DO NOT EDIT
8 XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
10 <title>Upgrading to 2.4 from 2.2 - Apache HTTP Server Version 2.5</title>
11 <link href="./style/css/manual.css" rel="stylesheet" media="all" type="text/css" title="Main stylesheet" />
12 <link href="./style/css/manual-loose-100pc.css" rel="alternate stylesheet" media="all" type="text/css" title="No Sidebar - Default font size" />
13 <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" />
14 <script src="./style/scripts/prettify.min.js" type="text/javascript">
17 <link href="./images/favicon.ico" rel="shortcut icon" /></head>
18 <body id="manual-page"><div id="page-header">
19 <p class="menu"><a href="./mod/">Modules</a> | <a href="./mod/quickreference.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>
20 <p class="apache">Apache HTTP Server Version 2.5</p>
21 <img alt="" src="./images/feather.png" /></div>
22 <div class="up"><a href="./"><img title="<-" alt="<-" src="./images/left.gif" /></a></div>
24 <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>
26 <p><span>Available Languages: </span><a href="./en/upgrading.html" title="English"> en </a> |
27 <a href="./fr/upgrading.html" hreflang="fr" rel="alternate" title="Français"> fr </a></p>
30 <p>In order to assist folks upgrading, we maintain a document
31 describing information critical to existing Apache HTTP Server users. These
32 are intended to be brief notes, and you should be able to find
33 more information in either the <a href="new_features_2_4.html">New Features</a> document, or in
34 the <code>src/CHANGES</code> file. Application and module developers
35 can find a summary of API changes in the <a href="developer/new_api_2_4.html">API updates</a> overview.</p>
37 <p>This document describes changes in server behavior that might
38 require you to change your configuration or how you use the server
39 in order to continue using 2.4 as you are currently using 2.2.
40 To take advantage of new features in 2.4, see the New Features
43 <p>This document describes only the changes from 2.2 to 2.4. If you
44 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
45 upgrading document.</a></p>
48 <div id="quickview"><ul id="toc"><li><img alt="" src="./images/down.gif" /> <a href="#compile-time">Compile-Time Configuration Changes</a></li>
49 <li><img alt="" src="./images/down.gif" /> <a href="#run-time">Run-Time Configuration Changes</a></li>
50 <li><img alt="" src="./images/down.gif" /> <a href="#misc">Misc Changes</a></li>
51 <li><img alt="" src="./images/down.gif" /> <a href="#third-party">Third Party Modules</a></li>
52 <li><img alt="" src="./images/down.gif" /> <a href="#commonproblems">Common problems when upgrading</a></li>
53 </ul><h3>See also</h3><ul class="seealso"><li><a href="new_features_2_4.html">Overview of new features in
54 Apache HTTP Server 2.4</a></li><li><a href="#comments_section">Comments</a></li></ul></div>
55 <div class="top"><a href="#page-header"><img alt="top" src="./images/up.gif" /></a></div>
57 <h2><a name="compile-time" id="compile-time">Compile-Time Configuration Changes</a></h2>
60 <p>The compilation process is very similar to the one used in
61 version 2.2. Your old <code>configure</code> command line (as
62 found in <code>build/config.nice</code> in the installed server
63 directory) can be used in most cases. There are some changes in
64 the default settings. Some details of changes:</p>
67 <li>These modules have been removed: mod_authn_default,
68 mod_authz_default, mod_mem_cache. If you were using
69 mod_mem_cache in 2.2, look at <code class="module"><a href="./mod/mod_cache_disk.html">mod_cache_disk</a></code> in
72 <li>All load balancing implementations have been moved to
73 individual, self-contained mod_proxy submodules, e.g.
74 <code class="module"><a href="./mod/mod_lbmethod_bybusyness.html">mod_lbmethod_bybusyness</a></code>. You might need
75 to build and load any of these that your configuration
78 <li>Platform support has been removed for BeOS, TPF, and
79 even older platforms such as A/UX, Next, and Tandem. These were
80 believed to be broken anyway.</li>
82 <li>configure: dynamic modules (DSO) are built by default</li>
84 <li>configure: By default, only a basic set of modules is loaded. The
85 other <code class="directive">LoadModule</code> directives are commented
86 out in the configuration file.</li>
88 <li>configure: the "most" module set gets built by default</li>
90 <li>configure: the "reallyall" module set adds developer modules
94 </div><div class="top"><a href="#page-header"><img alt="top" src="./images/up.gif" /></a></div>
96 <h2><a name="run-time" id="run-time">Run-Time Configuration Changes</a></h2>
98 <p>There have been significant changes in authorization configuration,
99 and other minor configuration changes, that could require changes to your 2.2
100 configuration files before using them for 2.4.</p>
102 <h3><a name="authz" id="authz">Authorization</a></h3>
105 <p>Any configuration file that uses authorization will likely
108 <p>You should review the <a href="howto/auth.html">Authentication,
109 Authorization and Access Control Howto</a>, especially the section
110 <a href="howto/auth.html#beyond">Beyond just authorization</a>
111 which explains the new mechanisms for controlling the order in
112 which the authorization directives are applied.</p>
114 <p>Directives that control how authorization modules respond when they don't match
115 the authenticated user have been removed: This includes
116 AuthzLDAPAuthoritative, AuthzDBDAuthoritative, AuthzDBMAuthoritative,
117 AuthzGroupFileAuthoritative, AuthzUserAuthoritative,
118 and AuthzOwnerAuthoritative. These directives have been replaced by the
119 more expressive <code class="directive"><a href="./mod/mod_authz_core.html#requireany">RequireAny</a></code>,
120 <code class="directive"><a href="./mod/mod_authz_core.html#requirenone">RequireNone</a></code>, and
121 <code class="directive"><a href="./mod/mod_authz_core.html#requireall">RequireAll</a></code>.</p>
123 <p>If you use <code class="module"><a href="./mod/mod_authz_dbm.html">mod_authz_dbm</a></code>, you must port your
124 configuration to use <code>Require dbm-group ...</code> in place
125 of <code>Require group ...</code>.</p>
127 <h4><a name="access" id="access">Access control</a></h4>
130 <p>In 2.2, access control based on client hostname, IP address,
131 and other characteristics of client requests was done using the
132 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>
134 <p>In 2.4, such access control is done in the same way as other
135 authorization checks, using the new module
136 <code class="module"><a href="./mod/mod_authz_host.html">mod_authz_host</a></code>. The old access control idioms
137 should be replaced by the new authentication mechanisms,
138 although for compatibility with old configurations, the new
139 module <code class="module"><a href="./mod/mod_access_compat.html">mod_access_compat</a></code> is provided.</p>
141 <div class="note"><h3>Mixing old and new directives</h3>
142 <p>Mixing old directives like <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> or <code class="directive"><a href="./mod/mod_access_compat.html#deny">Deny</a></code> with new ones like
143 <code class="directive"><a href="./mod/mod_authz_core.html#require">Require</a></code> is technically possible
144 but discouraged. <code class="module"><a href="./mod/mod_access_compat.html">mod_access_compat</a></code> was created to support
145 configurations containing only old directives to facilitate the 2.4 upgrade.
146 Please check the examples below to get a better idea about issues that might arise.
150 <p>Here are some examples of old and new ways to do the same
153 <p>In this example, there is no authentication and all requests are denied.</p>
154 <div class="example"><h3>2.2 configuration:</h3><pre class="prettyprint lang-config">Order deny,allow
157 <div class="example"><h3>2.4 configuration:</h3><pre class="prettyprint lang-config">Require all denied</pre>
160 <p>In this example, there is no authentication and all requests are allowed.</p>
161 <div class="example"><h3>2.2 configuration:</h3><pre class="prettyprint lang-config">Order allow,deny
164 <div class="example"><h3>2.4 configuration:</h3><pre class="prettyprint lang-config">Require all granted</pre>
167 <p>In the following example, there is no authentication and all hosts in the example.org domain
168 are allowed access; all other hosts are denied access.</p>
170 <div class="example"><h3>2.2 configuration:</h3><pre class="prettyprint lang-config">Order Deny,Allow
172 Allow from example.org</pre>
174 <div class="example"><h3>2.4 configuration:</h3><pre class="prettyprint lang-config">Require host example.org</pre>
177 <p>In the following example, mixing old and new directives leads to
178 unexpected results.</p>
180 <div class="example"><h3>Mixing old and new directives: NOT WORKING AS EXPECTED</h3><pre class="prettyprint lang-config">DocumentRoot "/var/www/html"
182 <Directory "/">
188 <Location "/server-status">
189 SetHandler server-status
193 access.log - GET /server-status 403 127.0.0.1
194 error.log - AH01797: client denied by server configuration: /var/www/html/server-status</pre>
196 <p>Why httpd denies access to servers-status even if the configuration seems to allow it?
197 Because <code class="module"><a href="./mod/mod_access_compat.html">mod_access_compat</a></code> directives take precedence
198 over the <code class="module"><a href="./mod/mod_authz_host.html">mod_authz_host</a></code> one in this configuration
199 <a href="sections.html#merging">merge</a> scenario.</p>
201 <p>This example conversely works as expected:</p>
203 <div class="example"><h3>Mixing old and new directives: WORKING AS EXPECTED</h3><pre class="prettyprint lang-config">DocumentRoot "/var/www/html"
205 <Directory "/">
210 <Location "/server-status">
211 SetHandler server-status
217 access.log - GET /server-status 200 127.0.0.1</pre>
219 <p>So even if mixing configuration is still
220 possible, please try to avoid it when upgrading: either keep old directives and then migrate
221 to the new ones on a later stage or just migrate everything in bulk.
225 <p>In many configurations with authentication, where the value of the
226 <code class="directive">Satisfy</code> was the default of <em>ALL</em>, snippets
227 that simply disabled host-based access control are omitted:</p>
229 <div class="example"><h3>2.2 configuration:</h3><pre class="prettyprint lang-config">Order Deny,Allow
231 AuthBasicProvider File
232 AuthUserFile /example.com/conf/users.passwd
234 Require valid-user</pre>
236 <div class="example"><h3>2.4 configuration:</h3><pre class="prettyprint lang-config"># No replacement needed
237 AuthBasicProvider File
238 AuthUserFile /example.com/conf/users.passwd
240 Require valid-user</pre>
243 <p>In configurations where both authentication and access control were meaningfully combined, the
244 access control directives should be migrated. This example allows requests meeting <em>both</em> criteria:</p>
245 <div class="example"><h3>2.2 configuration:</h3><pre class="prettyprint lang-config">Order allow,deny
247 # Satisfy ALL is the default
250 AuthBasicProvider File
251 AuthUserFile /example.com/conf/users.passwd
253 Require valid-user</pre>
255 <div class="example"><h3>2.4 configuration:</h3><pre class="prettyprint lang-config">AuthBasicProvider File
256 AuthUserFile /example.com/conf/users.passwd
261 </RequireAll></pre>
264 <p>In configurations where both authentication and access control were meaningfully combined, the
265 access control directives should be migrated. This example allows requests meeting <em>either</em> criteria:</p>
266 <div class="example"><h3>2.2 configuration:</h3><pre class="prettyprint lang-config">Order allow,deny
270 AuthBasicProvider File
271 AuthUserFile /example.com/conf/users.passwd
273 Require valid-user</pre>
275 <div class="example"><h3>2.4 configuration:</h3><pre class="prettyprint lang-config">AuthBasicProvider File
276 AuthUserFile /example.com/conf/users.passwd
278 # Implicitly <RequireAny>
280 Require ip 127.0.0.1</pre>
285 <h3><a name="config" id="config">Other configuration changes</a></h3>
288 <p>Some other small adjustments may be necessary for particular
289 configurations as discussed below.</p>
292 <li><code class="directive">MaxRequestsPerChild</code> has been renamed to
293 <code class="directive"><a href="./mod/mpm_common.html#maxconnectionsperchild">MaxConnectionsPerChild</a></code>,
294 describes more accurately what it does. The old name is still
297 <li><code class="directive">MaxClients</code> has been renamed to
298 <code class="directive"><a href="./mod/mpm_common.html#maxrequestworkers">MaxRequestWorkers</a></code>,
299 which describes more accurately what it does. For async MPMs, like
300 <code class="module"><a href="./mod/event.html">event</a></code>, the maximum number of clients is not
301 equivalent than the number of worker threads. The old name is still
304 <li>The <code class="directive"><a href="./mod/core.html#defaulttype">DefaultType</a></code>
305 directive no longer has any effect, other than to emit a
306 warning if it's used with any value other than
307 <code>none</code>. You need to use other configuration
308 settings to replace it in 2.4.
311 <li><code class="directive"><a href="./mod/core.html#allowoverride">AllowOverride</a></code> now
312 defaults to <code>None</code>.</li>
314 <li><code class="directive"><a href="./mod/core.html#enablesendfile">EnableSendfile</a></code> now
315 defaults to Off.</li>
317 <li><code class="directive"><a href="./mod/core.html#fileetag">FileETag</a></code> now
318 defaults to "MTime Size" (without INode).</li>
320 <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
321 systems with inodes. The old <code class="directive"><a href="./mod/mod_dav_fs.html#davlockdb">DavLockDB</a></code> file must be deleted on
325 <li><code class="directive"><a href="./mod/core.html#keepalive">KeepAlive</a></code> only
326 accepts values of <code>On</code> or <code>Off</code>.
327 Previously, any value other than "Off" or "0" was treated as
330 <li>Directives AcceptMutex, LockFile, RewriteLock, SSLMutex,
331 SSLStaplingMutex, and WatchdogMutexPath have been replaced
332 with a single <code class="directive"><a href="./mod/core.html#mutex">Mutex</a></code>
333 directive. You will need to evaluate any use of these removed
334 directives in your 2.2 configuration to determine if they can
335 just be deleted or will need to be replaced using <code class="directive"><a href="./mod/core.html#mutex">Mutex</a></code>.</li>
337 <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>
338 now does an exact match against the query string instead of a
339 partial match. If your configuration was using partial
340 strings, e.g. using <code>sessionid</code> to match
341 <code>/someapplication/image.gif;jsessionid=123456789</code>,
342 then you will need to change to the full string
343 <code>jsessionid</code>.
346 <li><code class="module"><a href="./mod/mod_cache.html">mod_cache</a></code>: The second parameter to
347 <code class="directive"><a href="./mod/mod_cache.html#cacheenable">CacheEnable</a></code> only
348 matches forward proxy content if it begins with the correct
349 protocol. In 2.2 and earlier, a parameter of '/' matched all
352 <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
353 consistently a per-directory setting only. If you use this
354 directive, review your configuration to make sure it is
355 present in all the necessary directory contexts.</li>
357 <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
358 now uses a boolean expression to determine if a filter is applied.
361 <li><code class="module"><a href="./mod/mod_include.html">mod_include</a></code>:
363 <li>The <code>#if expr</code> element now uses the new <a href="expr.html">expression parser</a>. The old syntax can be
364 restored with the new directive <code class="directive"><a href="./mod/mod_include.html#ssilegacyexprparser">SSILegacyExprParser</a></code>.
366 <li>An SSI* config directive in directory scope no longer causes
367 all other per-directory SSI* directives to be reset to their
372 <li><code class="module"><a href="./mod/mod_charset_lite.html">mod_charset_lite</a></code>: The <code>DebugLevel</code>
373 option has been removed in favour of per-module <code class="directive"><a href="./mod/core.html#loglevel">LogLevel</a></code> configuration.
376 <li><code class="module"><a href="./mod/mod_ext_filter.html">mod_ext_filter</a></code>: The <code>DebugLevel</code>
377 option has been removed in favour of per-module <code class="directive"><a href="./mod/core.html#loglevel">LogLevel</a></code> configuration.
380 <li><code class="module"><a href="./mod/mod_proxy_scgi.html">mod_proxy_scgi</a></code>: The default setting for
381 <code>PATH_INFO</code> has changed from httpd 2.2, and
382 some web applications will no longer operate properly with
383 the new <code>PATH_INFO</code> setting. The previous setting
384 can be restored by configuring the <code>proxy-scgi-pathinfo</code>
387 <li><code class="module"><a href="./mod/mod_ssl.html">mod_ssl</a></code>: CRL based revocation checking
388 now needs to be explicitly configured through <code class="directive"><a href="./mod/mod_ssl.html#sslcarevocationcheck">SSLCARevocationCheck</a></code>.
391 <li><code class="module"><a href="./mod/mod_substitute.html">mod_substitute</a></code>: The maximum line length is now
395 <li><code class="module"><a href="./mod/mod_reqtimeout.html">mod_reqtimeout</a></code>: If the module is loaded, it
396 will now set some default timeouts.</li>
398 <li><code class="module"><a href="./mod/mod_dumpio.html">mod_dumpio</a></code>: <code class="directive">DumpIOLogLevel</code>
399 is no longer supported. Data is always logged at <code class="directive"><a href="./mod/core.html#loglevel">LogLevel</a></code> <code>trace7</code>.</li>
401 <li>On Unix platforms, piped logging commands configured using
402 either <code class="directive"><a href="./mod/core.html#errorlog">ErrorLog</a></code> or
403 <code class="directive"><a href="./mod/mod_log_config.html#customlog">CustomLog</a></code> were invoked using
404 <code>/bin/sh -c</code> in 2.2 and earlier. In 2.4 and later,
405 piped logging commands are executed directly. To restore the
406 old behaviour, see the <a href="logs.html#piped">piped logging
407 documentation</a>.</li>
411 </div><div class="top"><a href="#page-header"><img alt="top" src="./images/up.gif" /></a></div>
412 <div class="section">
413 <h2><a name="misc" id="misc">Misc Changes</a></h2>
417 <li><code class="module"><a href="./mod/mod_autoindex.html">mod_autoindex</a></code>: will now extract titles and
418 display descriptions for .xhtml files, which were previously
421 <li><code class="module"><a href="./mod/mod_ssl.html">mod_ssl</a></code>: The default format of the <code>*_DN</code>
422 variables has changed. The old format can still be used with the new
423 <code>LegacyDNStringFormat</code> argument to <code class="directive"><a href="./mod/mod_ssl.html#ssloptions">SSLOptions</a></code>. The SSLv2 protocol is
424 no longer supported. <code class="directive"><a href="./mod/mod_ssl.html#sslproxycheckpeercn">SSLProxyCheckPeerCN
425 </a></code> and <code class="directive"><a href="./mod/mod_ssl.html#sslproxycheckpeerexpire">SSLProxyCheckPeerExpire
426 </a></code> now default to On, causing proxy requests to HTTPS hosts
427 with bad or outdated certificates to fail with a 502 status code (Bad
430 <li><code class="program"><a href="./programs/htpasswd.html">htpasswd</a></code> now uses MD5 hash by default on
433 <li>The <code class="directive"><a href="./mod/core.html#namevirtualhost">NameVirtualHost</a></code>
434 directive no longer has any effect, other than to emit a
435 warning. Any address/port combination appearing in multiple
436 virtual hosts is implicitly treated as a name-based virtual host.
439 <li><code class="module"><a href="./mod/mod_deflate.html">mod_deflate</a></code> will now skip compression if it knows
440 that the size overhead added by the compression is larger than the data
444 <li>Multi-language error documents from 2.2.x may not work unless
445 they are adjusted to the new syntax of <code class="module"><a href="./mod/mod_include.html">mod_include</a></code>'s
446 <code>#if expr=</code> element or the directive
447 <code class="directive"><a href="./mod/mod_include.html#ssilegacyexprparser">SSILegacyExprParser</a></code> is
448 enabled for the directory containing the error documents.
451 <li>The functionality provided by <code>mod_authn_alias</code>
452 in previous versions (i.e., the <code class="directive"><a href="./mod/mod_authn_core.html#authnprovideralias">AuthnProviderAlias</a></code> directive)
453 has been moved into <code class="module"><a href="./mod/mod_authn_core.html">mod_authn_core</a></code>.
456 <li><code class="module"><a href="./mod/mod_cgid.html">mod_cgid</a></code> uses the servers <code class="directive"><a href="./mod/core.html#timeout">Timeout</a></code> to limit the length of time to wait for CGI output.
457 This timeout can be overridden with <code class="directive"><a href="./mod/mod_cgid.html#cgidscripttimeout">
458 CGIDScriptTImeout</a></code>.
463 </div><div class="top"><a href="#page-header"><img alt="top" src="./images/up.gif" /></a></div>
464 <div class="section">
465 <h2><a name="third-party" id="third-party">Third Party Modules</a></h2>
467 <p>All modules must be recompiled for 2.4 before being loaded.</p>
469 <p>Many third-party modules designed for version 2.2 will
470 otherwise work unchanged with the Apache HTTP Server version 2.4.
471 Some will require changes; see the <a href="developer/new_api_2_4.html">API
472 update</a> overview.</p>
473 </div><div class="top"><a href="#page-header"><img alt="top" src="./images/up.gif" /></a></div>
474 <div class="section">
475 <h2><a name="commonproblems" id="commonproblems">Common problems when upgrading</a></h2>
477 <ul><li>Startup errors:
479 <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>
480 <li><code>Invalid command 'Require', perhaps misspelled or defined by a module not included in the server configuration</code>, or
481 <code>Invalid command 'Order', perhaps misspelled or defined by a module not included in the server configuration</code>
482 - 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>
483 <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>
484 and replace with other configuration settings.</li>
485 <li><code>Invalid command 'AddOutputFilterByType', perhaps misspelled
486 or defined by a module not included in the server configuration
487 </code> - <code class="directive"><a href="./mod/mod_filter.html#addoutputfilterbytype">AddOutputFilterByType</a></code>
488 has moved from the core to mod_filter, which must be loaded.</li>
490 <li>Errors serving requests:
492 <li><code>configuration error: couldn't check user: /path</code> -
493 load module <code class="module"><a href="./mod/mod_authn_core.html">mod_authn_core</a></code>.</li>
494 <li><code>.htaccess</code> files aren't being processed - Check for an
495 appropriate <code class="directive"><a href="./mod/core.html#allowoverride">AllowOverride</a></code> directive;
496 the default changed to <code>None</code> in 2.4.</li>
501 <div class="bottomlang">
502 <p><span>Available Languages: </span><a href="./en/upgrading.html" title="English"> en </a> |
503 <a href="./fr/upgrading.html" hreflang="fr" rel="alternate" title="Français"> fr </a></p>
504 </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>
505 <script type="text/javascript"><!--//--><![CDATA[//><!--
506 var comments_shortname = 'httpd';
507 var comments_identifier = 'http://httpd.apache.org/docs/trunk/upgrading.html';
509 if (w.location.hostname.toLowerCase() == "httpd.apache.org") {
510 d.write('<div id="comments_thread"><\/div>');
511 var s = d.createElement('script');
512 s.type = 'text/javascript';
514 s.src = 'https://comments.apache.org/show_comments.lua?site=' + comments_shortname + '&page=' + comments_identifier;
515 (d.getElementsByTagName('head')[0] || d.getElementsByTagName('body')[0]).appendChild(s);
518 d.write('<div id="comments_thread">Comments are disabled for this page at the moment.<\/div>');
520 })(window, document);
521 //--><!]]></script></div><div id="footer">
522 <p class="apache">Copyright 2016 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>
523 <p class="menu"><a href="./mod/">Modules</a> | <a href="./mod/quickreference.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[//><!--
524 if (typeof(prettyPrint) !== 'undefined') {