general <code class="directive">ProxyPass</code> directive.</p>
</div>
- <p>As of Apache HTTP Server 2.1, the ability to use pooled connections to a backend
- server is available. Using the <code>key=value</code> parameters it is
- possible to tune this connection pooling. The default for a <code>Hard
- Maximum</code> for the number of connections is the number of threads per
- process in the active MPM. In the Prefork MPM, this is always 1, while with
- the Worker MPM it is controlled by the
- <code class="directive">ThreadsPerChild</code>.</p>
-
- <p>Setting <code>min</code> will determine how many connections will always
- be open to the backend server. Upto the Soft Maximum or <code>smax</code>
- number of connections will be created on demand. Any connections above
- <code>smax</code> are subject to a time to live or <code>ttl</code>. Apache httpd
- will never create more than the Hard Maximum or <code>max</code> connections
- to the backend server.</p>
+ <p>In Apache HTTP Server 2.1 and later, mod_proxy supports pooled
+ connections to a backend server. Connections created on demand
+ can be retained in a pool for future use. Limits on the pool size
+ and other settings can be coded on
+ the <code class="directive">ProxyPass</code> directive
+ using <code>key=value</code> parameters, described in the table
+ below.</p>
+
+ <p>Setting <code>min</code> will determine how many connections to
+ the backend server will be retained after use. Up to the
+ Soft Maximum, or <code>smax</code>, number of connections will be
+ created on demand. Any connections above <code>smax</code> are
+ subject to a time to live, or <code>ttl</code>. Apache httpd will
+ never create more than the Hard Maximum or, <code>max</code>,
+ connections to the backend server.</p>
+
+ <p>The pool of connections is maintained per web server child
+ process, and the <code>min</code>, <code>max</code>, and
+ and <code>smax</code> settings are not coordinated among all child
+ processes, except when only one child process is allowed by
+ configuration or MPM design.</p>
- <div class="example"><p><code>
+ <div class="example"><h3>Example</h3><p><code>
ProxyPass /example http://backend.example.com smax=5 max=20 ttl=120 retry=300
</code></p></div>
<th>Description</th></tr>
<tr><td>min</td>
<td>0</td>
- <td>Minimum number of connections that will always
- be open to the backend server.</td></tr>
+ <td>Minimum number of connections to the backend server that
+ will be retained after use.</td></tr>
<tr><td>max</td>
<td>1...n</td>
<td>Hard Maximum number of connections that will be
to the backend server.</td></tr>
<tr><td>smax</td>
<td>max</td>
- <td>Upto the Soft Maximum
+ <td>Up to the Soft Maximum
number of connections will be created on demand. Any connections above
<code>smax</code> are subject to a time to live or <code>ttl</code>.
</td></tr>
<?xml version="1.0" encoding="UTF-8" ?>
<!DOCTYPE modulesynopsis SYSTEM "../style/modulesynopsis.dtd">
<?xml-stylesheet type="text/xsl" href="../style/manual.ja.xsl"?>
-<!-- English Revision: 344971:931689 (outdated) -->
+<!-- English Revision: 344971:956059 (outdated) -->
<!--
Licensed to the Apache Software Foundation (ASF) under one or more
--- /dev/null
+# GENERATED FROM XML -- DO NOT EDIT
+
+URI: new_api_2_4.html.en
+Content-Language: en
+Content-type: text/html; charset=ISO-8859-1
--- /dev/null
+<?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">
+<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en"><head><!--
+ XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
+ This file is generated from xml source: DO NOT EDIT
+ XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
+ -->
+<title>API Changes in Apache HTTP Server 2.4 since 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 href="./images/favicon.ico" rel="shortcut icon" /></head>
+<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="./faq/">FAQ</a> | <a href="./glossary.html">Glossary</a> | <a href="./sitemap.html">Sitemap</a></p>
+<p class="apache">Apache HTTP Server Version 2.3</p>
+<img alt="" src="./images/feather.gif" /></div>
+<div class="up"><a href="./"><img title="<-" alt="<-" src="./images/left.gif" /></a></div>
+<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.3</a></div><div id="page-content"><div id="preamble"><h1>API Changes in Apache HTTP Server 2.4 since 2.2</h1>
+<div class="toplang">
+<p><span>Available Languages: </span><a href="./en/new_api_2_4.html" title="English"> en </a></p>
+</div>
+
+ <p>This document describes changes to the Apache HTTPD API from
+ version 2.2 to 2.4, that may be of interest to module/application
+ developers and core hacks. At the time of writing, the 2.4 API
+ is not finalised, and this document may serve to highlight
+ points that call for further review.</p>
+ <p>API changes fall into two categories: APIs that are altogether new,
+ and existing APIs that are expanded or changed. The latter are
+ further divided into those where all changes are back-compatible
+ (so existing modules can ignore them), and those that might
+ require attention by maintainers. As with the transition from
+ HTTPD 2.0 to 2.2, existing modules and applications will require
+ recompiling and may call for some attention, but most should not
+ require any substantial updating (although some may be able to
+ take advantage of API changes to offer significant improvements).</p>
+ <p>For the purpose of this document, the API is split according
+ to the public header files. These headers are themselves the
+ reference documentation, and can be used to generate a browsable
+ HTML reference with <code>make docs</code>.</p>
+</div>
+<div id="quickview"><ul id="toc"><li><img alt="" src="./images/down.gif" /> <a href="#ap_expr">ap_expr (NEW!)</a></li>
+<li><img alt="" src="./images/down.gif" /> <a href="#ap_listen">ap_listen (changed; back-compatible)</a></li>
+<li><img alt="" src="./images/down.gif" /> <a href="#ap_mpm">ap_mpm (changed)</a></li>
+<li><img alt="" src="./images/down.gif" /> <a href="#ap_slotmem">ap_slotmem (NEW!)</a></li>
+<li><img alt="" src="./images/down.gif" /> <a href="#ap_socache">ap_socache (NEW!)</a></li>
+<li><img alt="" src="./images/down.gif" /> <a href="#heartbeat">heartbeat (NEW!)</a></li>
+<li><img alt="" src="./images/down.gif" /> <a href="#http_config">http_config (changed)</a></li>
+<li><img alt="" src="./images/down.gif" /> <a href="#http_core">http_core (changed)</a></li>
+<li><img alt="" src="./images/down.gif" /> <a href="#httpd">httpd (changed)</a></li>
+<li><img alt="" src="./images/down.gif" /> <a href="#http_log">http_log (changed)</a></li>
+<li><img alt="" src="./images/down.gif" /> <a href="#http_request">http_request (changed)</a></li>
+<li><img alt="" src="./images/down.gif" /> <a href="#mod_auth">mod_auth (NEW!)</a></li>
+<li><img alt="" src="./images/down.gif" /> <a href="#mod_core">mod_core (NEW!)</a></li>
+<li><img alt="" src="./images/down.gif" /> <a href="#mod_request">mod_request (NEW!)</a></li>
+<li><img alt="" src="./images/down.gif" /> <a href="#mpm_common">mpm_common (changed)</a></li>
+<li><img alt="" src="./images/down.gif" /> <a href="#scoreboard">scoreboard (changed)</a></li>
+<li><img alt="" src="./images/down.gif" /> <a href="#util_cookies">util_cookies (NEW!)</a></li>
+<li><img alt="" src="./images/down.gif" /> <a href="#util_ldap">util_ldap (changed)</a></li>
+<li><img alt="" src="./images/down.gif" /> <a href="#util_mutex">util_mutex (NEW!)</a></li>
+<li><img alt="" src="./images/down.gif" /> <a href="#util_script">util_script (changed)</a></li>
+<li><img alt="" src="./images/down.gif" /> <a href="#util_time">util_time (changed)</a></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="ap_expr" id="ap_expr">ap_expr (NEW!)</a></h2>
+
+ <p>Introduces a new API to parse and evaluate boolean and algebraic
+ expressions, including provision for a standard syntax and
+ customised variants.</p>
+ </div><div class="top"><a href="#page-header"><img alt="top" src="./images/up.gif" /></a></div>
+<div class="section">
+<h2><a name="ap_listen" id="ap_listen">ap_listen (changed; back-compatible)</a></h2>
+
+ <p>Introduces new API to enable apache child processes to serve different purposes.</p>
+ </div><div class="top"><a href="#page-header"><img alt="top" src="./images/up.gif" /></a></div>
+<div class="section">
+<h2><a name="ap_mpm" id="ap_mpm">ap_mpm (changed)</a></h2>
+
+ <p><code>ap_mpm_run</code> is replaced by a new <code>mpm</code> hook.
+ Also <code>ap_graceful_stop_signalled</code> is lost, and
+ <code>ap_mpm_register_timed_callback</code> is new.</p>
+ </div><div class="top"><a href="#page-header"><img alt="top" src="./images/up.gif" /></a></div>
+<div class="section">
+<h2><a name="ap_slotmem" id="ap_slotmem">ap_slotmem (NEW!)</a></h2>
+
+ <p>Introduces an API for modules to allocate and manage memory slots
+ (normally) for shared memory.</p>
+ </div><div class="top"><a href="#page-header"><img alt="top" src="./images/up.gif" /></a></div>
+<div class="section">
+<h2><a name="ap_socache" id="ap_socache">ap_socache (NEW!)</a></h2>
+
+ <p>API to manage a shared object cache.</p>
+ </div><div class="top"><a href="#page-header"><img alt="top" src="./images/up.gif" /></a></div>
+<div class="section">
+<h2><a name="heartbeat" id="heartbeat">heartbeat (NEW!)</a></h2>
+
+ <p>common structures for heartbeat modules (should this be public API?)</p>
+ </div><div class="top"><a href="#page-header"><img alt="top" src="./images/up.gif" /></a></div>
+<div class="section">
+<h2><a name="http_config" id="http_config">http_config (changed)</a></h2>
+
+ <ul>
+ <li>Introduces per-module, per-directory loglevels, including macro wrappers.</li>
+ <li>New AP_DECLARE_MODULE macro to declare all modules.</li>
+ <li>New APLOG_USE_MODULE macro necessary for per-module loglevels in
+ multi-file modules.</li>
+ <li>New API to retain data across module unload/load</li>
+ <li>New check_config hook</li>
+ <li>New ap_process_fnmatch_configs() to process wildcards</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="http_core" id="http_core">http_core (changed)</a></h2>
+
+ <ul>
+ <li>REMOVED ap_default_type, ap_requires, all 2.2 authnz API</li>
+ <li>Introduces Optional Functions for logio and authnz</li>
+ <li>New function ap_get_server_name_for_url to support ipv6 literals.</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="httpd" id="httpd">httpd (changed)</a></h2>
+
+ <ul>
+ <li>Introduce per-directory, per-module loglevel</li>
+ <li>New loglevels APLOG_TRACEn</li>
+ <li>Support for mod_request kept_body</li>
+ <li>Support buffering filter data for async requests</li>
+ <li>New CONN_STATE values</li>
+ <li>Function changes: ap_escape_html updated; ap_unescape_all, ap_escape_path_segment_buffer</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="http_log" id="http_log">http_log (changed)</a></h2>
+
+ <ul>
+ <li>Introduce per-directory, per-module loglevel</li>
+ <li>New loglevels APLOG_TRACEn</li>
+ <li>ap_log_*error become macro wrappers (fully back-compatible if
+ APLOG_MARK macro is used)</li>
+ <li>piped logging revamped</li>
+ <li>module_index added to error_log hook</li>
+ <li>new function: ap_log_command_line</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="http_request" id="http_request">http_request (changed)</a></h2>
+
+ <ul>
+ <li>New auth_internal API and auth_provider API</li>
+ <li>New EOR bucket type</li>
+ <li>New function ap_process_async_request</li>
+ <li>New functions ap_hook_check_access, ap_hook_check_authn, ap_hook_check_authz (why are these called ap_hook_* when they are functions not hooks?)</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="mod_auth" id="mod_auth">mod_auth (NEW!)</a></h2>
+
+ <p>Introduces the new provider framework for authn and authz</p>
+ </div><div class="top"><a href="#page-header"><img alt="top" src="./images/up.gif" /></a></div>
+<div class="section">
+<h2><a name="mod_core" id="mod_core">mod_core (NEW!)</a></h2>
+
+ <p>This introduces low-level APIs to send arbitrary headers,
+ and exposes functions to handle HTTP OPTIONS and TRACE.</p>
+ </div><div class="top"><a href="#page-header"><img alt="top" src="./images/up.gif" /></a></div>
+<div class="section">
+<h2><a name="mod_request" id="mod_request">mod_request (NEW!)</a></h2>
+
+ <p>The API for <code class="module"><a href="./mod/mod_request.html">mod_request</a></code>, to make input data
+ available to multiple application/handler modules where required,
+ and to parse HTML form data.</p>
+ </div><div class="top"><a href="#page-header"><img alt="top" src="./images/up.gif" /></a></div>
+<div class="section">
+<h2><a name="mpm_common" id="mpm_common">mpm_common (changed)</a></h2>
+
+ <ul>
+ <li>REMOVES: accept, lockfile, lock_mech, set_scoreboard (locking uses the new ap_mutex API)</li>
+ <li>NEW API to drop privileges (delegates this platform-dependent
+ function to modules)</li>
+ <li>NEW Hooks: mpm_query, mpm_note_child_killed, timed_callback, get_name, and function ap_mpm_note_child_killed</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="scoreboard" id="scoreboard">scoreboard (changed)</a></h2>
+
+ <p>ap_get_scoreboard_worker is gratuitously made non-back-compatible
+ as an alternative version is introduced. Additional proxy_balancer
+ support. Child status stuff revamped.</p>
+ </div><div class="top"><a href="#page-header"><img alt="top" src="./images/up.gif" /></a></div>
+<div class="section">
+<h2><a name="util_cookies" id="util_cookies">util_cookies (NEW!)</a></h2>
+
+ <p>Introduces a new API for managing HTTP Cookies.</p>
+ </div><div class="top"><a href="#page-header"><img alt="top" src="./images/up.gif" /></a></div>
+<div class="section">
+<h2><a name="util_ldap" id="util_ldap">util_ldap (changed)</a></h2>
+
+ <p>I have yet to get a handle on this update.</p>
+ </div><div class="top"><a href="#page-header"><img alt="top" src="./images/up.gif" /></a></div>
+<div class="section">
+<h2><a name="util_mutex" id="util_mutex">util_mutex (NEW!)</a></h2>
+
+ <p>A wrapper for APR proc and global mutexes in httpd.</p>
+ </div><div class="top"><a href="#page-header"><img alt="top" src="./images/up.gif" /></a></div>
+<div class="section">
+<h2><a name="util_script" id="util_script">util_script (changed)</a></h2>
+
+ <p>NEW: ap_args_to_table</p>
+ </div><div class="top"><a href="#page-header"><img alt="top" src="./images/up.gif" /></a></div>
+<div class="section">
+<h2><a name="util_time" id="util_time">util_time (changed)</a></h2>
+
+ <p>NEW: ap_recent_ctime_ex</p>
+ </div></div>
+<div class="bottomlang">
+<p><span>Available Languages: </span><a href="./en/new_api_2_4.html" title="English"> en </a></p>
+</div><div id="footer">
+<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>
+<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>
\ No newline at end of file
--- /dev/null
+<?xml version="1.0" encoding="UTF-8" ?>
+<!-- GENERATED FROM XML: DO NOT EDIT -->
+
+<metafile>
+ <basename>new_api_2_4</basename>
+ <path>/</path>
+ <relpath>.</relpath>
+
+ <variants>
+ <variant>en</variant>
+ </variants>
+</metafile>
<code class="module"><a href="../mod/mod_alias.html">mod_alias</a></code> et la documentation sur la <a href="../urlmapping.html">Mise en correspondance des URLs avec le
système de fichiers</a>.</p>
-<p>Enfin, avant de procéder, assurez-vous d'avoir configuré la directive
-<code class="directive"><a href="../mod/mod_rewrite.html#rewritelog">RewriteLog</a></code>. Bien que ce
-fichier journal puisse contenir une quantité impressionnante d'informations,
-il s'avère indispensable pour le débogage des problèmes avec la
-configuration de <code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code>, car il vous indiquera
-exactement la manière dont chaque règle est traitée.</p>
-
-<div class="note">
-<p>On ne peut pas utiliser la directive RewriteLog dans les fichiers
-.htaccess, car elle doit être définie au niveau du fichier
-de configuration du serveur principal.</p>
-</div>
+<p>Enfin, avant de procéder, assurez-vous d'avoir configuré le niveau de
+journalisation de <code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code> à un des niveaux de trace
+via la directive <code class="directive"><a href="../mod/core.html#loglevel">LogLevel</a></code>. Bien que
+ceci risque de vous submerger sous une énorme quantité d'informations,
+le débogage des problèmes avec la configuration de
+<code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code> est à ce prix car vous verrez alors
+exactement comment chaque règle est traitée.</p>
+
</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
<div class="section">
<h2><a name="regex" id="regex">Expressions rationnelles</a></h2>
<p>La directive <code class="directive"><a href="../mod/mod_rewrite.html#rewritemap">RewriteMap</a></code>
permet en quelque sorte de faire appel à une fonction externe pour
effectuer la réécriture à votre place. Tout ceci est décrit plus en
-détails dans la <a href="rewritemap.html">Documentation supplémentaire
-sur RewriteMap</a>.</p>
+détails dans la <a href="rewritemap.html">Documentation supplémentaire sur RewriteMap</a>.</p>
</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
<div class="section">
<h2><a name="htaccess" id="htaccess">Fichiers .htaccess</a></h2>
the <code>src/CHANGES</code> file. Application and module developers
can find a summary of API changes in the <a href="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>
<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="#misc">Misc Changes</a></li>
<li><img alt="" src="./images/down.gif" /> <a href="#third-party">Third Party Modules</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></div>
<div class="top"><a href="#page-header"><img alt="top" src="./images/up.gif" /></a></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
+ found in <code>build/config.nice</code> in the installed server
+ 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_disk_cache.html">mod_disk_cache</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, OS/2, TPF, and
+ even older platforms such as A/UX, Next, and Tandem. These were
+ believed to be broken anyway.</li>
+
+ <li>configure: dynamic modules (DSO) are built by default</li>
+
+ <li>configure: the "most" module set gets built by default</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="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>
+
+ <p>You should review the <a href="howto/auth.html">Authentication,
+ Authorization and Access Control Howto</a>, especially the section
+ <a href="howto/auth.html#beyond">Beyond just authorization</a>
+ 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><p><code>
+
+ Order deny,allow<br />
+ Deny from all
+ </code></p></div>
+ <div class="example"><h3>2.4 configuration:</h3><p><code>
+
+ Require all denied
+ </code></p></div>
+
+ <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 apache.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 apache.org
+ </code></p></div>
+ <div class="example"><h3>2.4 configuration:</h3><p><code>
+
+ Require host apache.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>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="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>
+
+ </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_auto_index.html">mod_auto_index</a></code>: will now extract titles and
+ display descriptions for .xhtml files, which were previously
+ ignored.</li>
+ <li><code class="program"><a href="./programs/htpasswd.html">htpasswd</a></code> now uses MD5 hash by default on
+ all platforms.</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="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"> en </a> |
<?xml-stylesheet type="text/xsl" href="./style/manual.fr.xsl"?>
<!-- French translation : Lucien GENTIS -->
<!-- Reviewed by : Vincent Deffontaines -->
-<!-- English Revision: 922232:954230 (outdated) -->
+<!-- English Revision: 922232:956396 (outdated) -->
<!--
Licensed to the Apache Software Foundation (ASF) under one or more
projects / apache / commitdiff