Commit 40b8df14 authored by William A. Rowe Jr's avatar William A. Rowe Jr
Browse files 

  Gone, see .html.en flavors


git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@89951 13f79535-47bb-0310-9956-ffa450edef68
parent b5e38d39

docs/manual/new_features_2_0.html

deleted100644 → 0
+0 −99
Original line number Diff line number Diff line 
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">

<HTML><HEAD>

<TITLE>New features with Apache 2.0</TITLE>

</HEAD>



<!-- Background white, links blue (unvisited), navy (visited), red (active) -->

<BODY BGCOLOR="#FFFFFF" TEXT="#000000" LINK="#0000FF" 

      VLINK="#000080" ALINK="#FF0000">

<!--#include virtual="header.html" -->

<H1 ALIGN="CENTER">Overview of New Features in Apache 2.0</H1>



<P>Enhancements: <A HREF="#core">Core</A> | <a href="#module">Module</a>



<P><HR>



<H2><A NAME="core">Core Enhancements:</A></H2>



<DL>

<DT><STRONG>Unix Threading</STRONG>

<DD>On Unix systems with POSIX threads support, Apache can now run in a

    hybrid multiprocess, multithreaded mode. This should improve

    scalability. 



<DT><STRONG>New Build System</STRONG>

<DD>The build system has been rewritten from scratch to be based on

    autoconf and libtool. This makes Apache's configuration system more

    similar to that of other packages.



<DT><STRONG>Multiprotocol Support</STRONG>

<DD>Apache now has some of the infrastructure in place to support serving

    multiple protocols. mod_echo has been written as an example.



<DT><STRONG>Better support for non-Unix platforms</STRONG> <DD>Apache

    2.0 is faster and more stable on non-Unix platforms such as BeOS,

    OS/2, and Windows. With the introduction of platform-specific <a

    href="mpm.html">multi-processing modules</a> (MPMs) and the Apache

    Portable Runtime (APR), these platforms are now implemented in their

    native API, avoiding the often buggy and poorly performing

    POSIX-emulation layers.



<DT><STRONG>New Apache API</STRONG>

<DD>The API for modules has changed significantly for 2.0. Many of the

    module-ordering problems from 1.3 should be gone. 2.0 does much of

    this automatically, and module ordering is now done per-hook to

    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

    &lt;VirtualHost&gt; 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>



<H2><A NAME="module">Module Enhancements:</A></H2>



<dl>



<dt><strong>mod_auth_db</strong>

<dd>Now supports Berkely DB 3.0



<dt><strong>mod_auth_digest</strong>

<dd>Includes additional support for session caching across processes 

using shared memory.



<dt><strong>mod_charset_lite</strong> <dd>New module in Apache 2.0.

This experimental module allows for character set translation

or recoding.



<dt><strong>mod_dav</strong>

<dd>New module in Apache 2.0.  This module implements the 

HTTP Distributed Authoring and Versioning (DAV) specification for

posting and maintaining web content.



<dt><strong>mod_file_cache</strong>

<dd>New module in Apache 2.0.  This module includes the functionality

of mod_mmap_static in Apache 1.3, plus adds further caching abilities.



<dt><strong>mod_headers</strong> 

<dd>This module is much more flexible in Apache 2.0.  It can now

modify request headers used by mod_proxy, and it can conditionally set

response headers.



</dl>



<!--#include virtual="footer.html" -->

</BODY>

</HTML>

docs/manual/upgrading.html

deleted100644 → 0
+0 −156
Original line number Diff line number Diff line 
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">

<HTML><HEAD>

<TITLE>Upgrading to 2.0 from 1.3</TITLE>

</HEAD>



<!-- Background white, links blue (unvisited), navy (visited), red (active) -->

<BODY

 BGCOLOR="#FFFFFF"

 TEXT="#000000"

 LINK="#0000FF"

 VLINK="#000080"

 ALINK="#FF0000"

>

<!--#include virtual="header.html" -->

<H1 ALIGN="CENTER">Upgrading to 2.0 from 1.3</H1>



<P>In order to assist folks upgrading, we maintain a document

describing information critical to existing Apache users.  These are

intended to be brief notes, and you should be able to find more

information in either the <A HREF="new_features_2_0.html">New

Features</A> document, or in the <CODE>src/CHANGES</CODE> file.



<H3>Compile-Time Configuration Changes</H3>



<UL>

<LI>Apache now uses an <code>autoconf</code> and <code>libtool</code>

system for <a href="install.html">configuring the build processes</a>.

Using this system is similar to, but not the same as, using the APACI

system in Apache 1.3.</li>



<li>In addition to the usual selection of modules which you can choose

to compile, Apache 2.0 has moved the main part of request processing

into <a href="mpm.html">Multi-Processing Modules</a> (MPMs).</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>Server-Side Includes provided by <a

href="mod/mod_include.html">mod_include</a> are now implemented using

the new

<a href="filter.html">filter system</a> rather than as a handler.

This provides much more power and flexibility, but requires 

the use of the <a href="mod/core.html#setoutputfilter">SetOutputFilter</a>

to activate server-parsed content.  If you were using

<code>AddHandler server-parsed .shtml</code>, you can get

similar functionality using

<blockquote><code>

&lt;FilesMatch "\.shtml(\..+)?$"&gt;<br>

&nbsp;&nbsp;SetOutputFilter INCLUDES<br>

&lt;/FilesMatch&gt;

</code></blockquote></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

with <code>CacheNegotiatedDocs on</code>.</li>



<li>The <code>ErrorDocument</code> directive no longer uses a quote at

the beginning of the argument to indicate a text message.  Instead,

you should enclose the message in double quotes.  For example,

existing instances of <blockquote><code>ErrorDocument 403 "Some

Message</code></blockquote> should be replaced with

<blockquote><code>ErrorDocument 403 "Some

Message"</code></blockquote>  As long as the second argument is not a

valid URL or pathname, it will be treated as a text message.</li>



<li>The <code>AccessConfig</code> and <code>ResourceConfig</code>

directives no longer exist.  Existing instances of these directives

can be replaced with the <a

href="mod/core.html#include"><code>Include</code></a> directive which

has equivalent functionality.  If you were making use of the default

values of these directives without including them in the configuration

files, you may need to add <code>Include conf/access.conf</code> and

<code>Include conf/srm.conf</code> to your httpd.conf.  In order to

assure that Apache reads the configuration files in the same order as

was implied by the older directives, the <code>Include</code>

directives should be placed at the end of httpd.conf, with the one for

<code>srm.conf</code> preceding the one for

<code>access.conf</code>.</li>



<li>The <code>BindAddress</code> directive no longer exists.

Equivalent functionality is provided with the more flexible <code><a

href="mod/mpm_common.html#listen">Listen</a></code> directive.



<li>The <code>ServerType</code> directive no longer exists.

The method used to serve requests is now determined by the selection

of MPM.  There is currently no MPM designed to be launched by

inetd.</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

referer logs are still available using the <a

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>



<UL>



<li>Graceful restarts of the server are now executed by signaling the

parent process with <code>WINCH</code> rather than

<code>USR1</code>.</li>



<li>The <code>httpd</code> command line option <code>-S</code>

which was used for printing the virtual host configuration has

been replaced by <code>-t -D DUMP_VHOSTS</code>.</li>



<li>The <code>httpd</code> command line option <code>-X</code> has

been removed.  Most MPMs allow the same functionality to be requested

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>Third Party Modules</H3>



<p>Extensive changes were made to the server API in Apache 2.0.

Existing modules designed for the Apache 1.3 API will <strong>not</strong>

work in Apache 2.0 without modification.  Details are provided in

the <a href="developer/">developer documentation</a>.</p>



<!--#include virtual="footer.html" -->

</BODY>

</HTML>