allow more flexibility. Also, new calls have been added that provide
additional module capabilities without patching the core Apache server.
+<DT><STRONG>IPv6 Support</STRONG></DT>
+<DD>On systems where IPv6 is supported by the underlying Apache
+ Portable Runtime library, Apache gets IPv6 listening sockets by
+ default. Additionally, the Listen, NameVirtualHost, and
+ <VirtualHost> directives support IPv6 numeric address
+ strings (e.g., "Listen [fe80::1]:8080").</DD>
+
+<DT><STRONG>Filtering</STRONG></DT>
+<DD>Apache modules may now be written as filters which act on the
+ stream of content as it is delivered to or from the server. This
+ allows, for example, the output of CGI scripts to be parsed for
+ Server Side Include directive by mod_include.</DD>
+
</DL>
<P><HR>
allow more flexibility. Also, new calls have been added that provide
additional module capabilities without patching the core Apache server.
+<DT><STRONG>IPv6 Support</STRONG></DT>
+<DD>On systems where IPv6 is supported by the underlying Apache
+ Portable Runtime library, Apache gets IPv6 listening sockets by
+ default. Additionally, the Listen, NameVirtualHost, and
+ <VirtualHost> directives support IPv6 numeric address
+ strings (e.g., "Listen [fe80::1]:8080").</DD>
+
+<DT><STRONG>Filtering</STRONG></DT>
+<DD>Apache modules may now be written as filters which act on the
+ stream of content as it is delivered to or from the server. This
+ allows, for example, the output of CGI scripts to be parsed for
+ Server Side Include directive by mod_include.</DD>
+
</DL>
<P><HR>
<H3>Run-Time Configuration Changes</H3>
<UL>
+<li>Many directives that were in the core server in Apache 1.3
+are now in the MPMs. If you wish the behavior of the server
+to be as similar as possible to the behavior of Apache 1.3,
+you should select the <a href="mod/prefork.html">prefork</a>
+MPM. Other MPMs will have different directives to control process
+creation and request processing.</li>
+
<li>The <code>CacheNegotiatedDocs</code> directive now takes
the argument <code>on</code> or <code>off</code>. Existing
instances of <code>CacheNegotiatedDocs</code> should be replaced
of MPM. There is currently no MPM designed to be launched by
inetd.</li>
-<li>Many directives that were in the core server in Apache 1.3
-are now in the MPMs.</li>
-
<li>The mod_log_agent and mod_log_referer modules which provided the
<code>AgentLog</code>, <code>RefererLog</code> and
<code>RefererIgnore</code> directives have been removed. Agent and
href="mod/mod_log_config.html#customlog">CustomLog</a> directive of
mod_log_config.</li>
+<li>The <code>AddModule</code> and <code>ClearModuleList</code>
+directives no longer exist. These directives where used to ensure
+that modules could be enabled in the correct order. The new
+Apache 2.0 API allows modules to explicitly specify their ordering,
+eliminating the need for these directives.</li>
+
</UL>
<H3>Misc Changes</H3>
<li>The <code>httpd</code> command line option <code>-X</code> has
been removed. Most MPMs allow the same functionality to be requested
-by setting the <code>ONE_PROCESS</code> and <code>NO_DETACH</code>
-environment variables prior to launching <code>httpd</code>.</li>
+by using the <code>-D ONE_PROCESS</code> command line
+option. In addition, a <code>-D NO_DETACH</code> command line
+option is available.</li>
<li>The module mod_auth_digest, which was experimental in Apache 1.3
is now a standard module.</li>
<li>The mod_mmap_static module, which was experimental in Apache 1.3
has been replaced with mod_file_cache.</li>
+<li>The distribution has been completely reorganized so that it no
+longer contains an independent <code>src</code> directory. Instead,
+the sources are logically organized under the main distribution
+directory, and installations of the compiled server should be
+directed to a separate directory.</li>
</UL>
<H3>Run-Time Configuration Changes</H3>
<UL>
+<li>Many directives that were in the core server in Apache 1.3
+are now in the MPMs. If you wish the behavior of the server
+to be as similar as possible to the behavior of Apache 1.3,
+you should select the <a href="mod/prefork.html">prefork</a>
+MPM. Other MPMs will have different directives to control process
+creation and request processing.</li>
+
<li>The <code>CacheNegotiatedDocs</code> directive now takes
the argument <code>on</code> or <code>off</code>. Existing
instances of <code>CacheNegotiatedDocs</code> should be replaced
of MPM. There is currently no MPM designed to be launched by
inetd.</li>
-<li>Many directives that were in the core server in Apache 1.3
-are now in the MPMs.</li>
-
<li>The mod_log_agent and mod_log_referer modules which provided the
<code>AgentLog</code>, <code>RefererLog</code> and
<code>RefererIgnore</code> directives have been removed. Agent and
href="mod/mod_log_config.html#customlog">CustomLog</a> directive of
mod_log_config.</li>
+<li>The <code>AddModule</code> and <code>ClearModuleList</code>
+directives no longer exist. These directives where used to ensure
+that modules could be enabled in the correct order. The new
+Apache 2.0 API allows modules to explicitly specify their ordering,
+eliminating the need for these directives.</li>
+
</UL>
<H3>Misc Changes</H3>
<li>The <code>httpd</code> command line option <code>-X</code> has
been removed. Most MPMs allow the same functionality to be requested
-by setting the <code>ONE_PROCESS</code> and <code>NO_DETACH</code>
-environment variables prior to launching <code>httpd</code>.</li>
+by using the <code>-D ONE_PROCESS</code> command line
+option. In addition, a <code>-D NO_DETACH</code> command line
+option is available.</li>
<li>The module mod_auth_digest, which was experimental in Apache 1.3
is now a standard module.</li>
<li>The mod_mmap_static module, which was experimental in Apache 1.3
has been replaced with mod_file_cache.</li>
+<li>The distribution has been completely reorganized so that it no
+longer contains an independent <code>src</code> directory. Instead,
+the sources are logically organized under the main distribution
+directory, and installations of the compiled server should be
+directed to a separate directory.</li>
</UL>