<img src="images/mod_filter_new.png" width="423" height="331"
alt="Smart filtering applies different filter providers according to the state of request processing"/>
</p>
-<p><module>mod_filter</module>, included in Apache 2.1 and up,
+<p><module>mod_filter</module>, included in Apache 2.1 and later,
enables the filter chain to be configured dynamically at run time.
So for example you can set up a proxy to rewrite
HTML with an HTML filter and JPEG images with a completely
<status>Extension</status>
<sourcefile>mod_dbd.c</sourcefile>
<identifier>dbd_module</identifier>
-<compatibility>Version 2.1 and higher</compatibility>
+<compatibility>Version 2.1 and later</compatibility>
<summary>
<p><module>mod_dbd</module> manages SQL database connections using
<dd>Use <code>mode=output</code> (the default) for filters which
process the response. Use <code>mode=input</code> for filters
- which process the request. <code>mode=input</code> is new with
- Apache 2.1.</dd>
+ which process the request. <code>mode=input</code> is available
+ in Apache 2.1 and later.</dd>
<dt><code>intype=<var>imt</var></code></dt>
<status>Base</status>
<sourcefile>mod_filter.c</sourcefile>
<identifier>filter_module</identifier>
-<compatibility>Version 2.1 and higher</compatibility>
+<compatibility>Version 2.1 and later</compatibility>
<summary>
<p>This module enables smart, context-sensitive configuration of
content filter modules. This is work-in-progress; the
<directive module="mod_filter">FilterProtocol</directive> implements
some of this functionality for back-compatibility with Apache 2.0
- modules. For httpd 2.1 and up, the
+ modules. For httpd 2.1 and later, the
<code>ap_register_output_filter_protocol</code> and
<code>ap_filter_protocol</code> API enables filter modules to
declare their own behaviour.</p>
general <directive>ProxyPass</directive> directive.</p>
</note>
- <p>New in Apache 2.1, is the ability to use pooled connections to a
- backend server. 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 <directive>ThreadsPerChild</directive>.</p>
+ <p>As of Apache 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
+ <directive>ThreadsPerChild</directive>.</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>
...<br />
</VirtualHost>
</example>
-<p>New in Apache 2.1, <directive>SSLEngine</directive> can be set to <code>
-optional</code>. This enables support for
+<p>In Apache 2.1 and later, <directive>SSLEngine</directive> can be set to
+<code>optional</code>. This enables support for
<a href="http://www.ietf.org/rfc/rfc2817.txt">RFC 2817</a>, Upgrading to TLS
Within HTTP/1.1. At this time no web browsers support RFC 2817.</p>
</usage>
had to take responsibility for managing it themselves. Apart
from reinventing the wheel, this can be very inefficient, for
example when several modules each maintain their own connections.</p>
- <p>Apache 2.1 and up provides the <code>ap_dbd</code> API for
+ <p>Apache 2.1 and later provides the <code>ap_dbd</code> API for
managing database connections (including optimised strategies
- for threaded and unthreaded MPMs), while APR 1.2 and up provides
+ for threaded and unthreaded MPMs), while APR 1.2 and later provides
the <code>apr_dbd</code> API for interacting with the database.</p>
<p>New modules SHOULD now use these APIs for all SQL database
operations. Existing applications SHOULD be upgraded to use it