383N/A<!
DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
383N/A<
TITLE>Upgrading to 2.0 from 1.3</
TITLE>
383N/A<!-- Background white, links blue (unvisited), navy (visited), red (active) --> 6982N/A<
H1 ALIGN="CENTER">Upgrading to 2.0 from 1.3</
H1>
6982N/A<
P>In order to assist folks upgrading, we maintain a document
6982N/Adescribing information critical to existing Apache users. These are
383N/Aintended to be brief notes, and you should be able to find more
383N/A<
H3>Compile-Time Configuration Changes</
H3>
383N/A<
LI>Apache now uses an <
code>autoconf</
code> and <
code>libtool</
code>
383N/Asystem for configuring the build processes. Using this system
383N/Ais similar to, but not the same as, using the APACI system in
383N/AApache 1.3. Further documentation to follow.</
li>
383N/A<
li>In addition to the usual selection of modules which you can choose
6105N/Ato compile, Apache 2.0 has moved the main part of request processing
383N/A<
H3>Run-Time Configuration Changes</
H3>
383N/A<
li>The <
code>CacheNegotiatedDocs</
code> directive now takes
383N/Athe argument <
code>on</
code> or <
code>off</
code>. Existing
383N/Ainstances of <
code>CacheNegotiatedDocs</
code> should be replaced
383N/Awith <
code>CachNegotiatedDocs on</
code>.</
li>
383N/A<
li>The <
code>ErrorDocument</
code> directive no longer uses a quote at
383N/Athe beginning of the argument to indicate a text message. Instead,
383N/Ayou should enclose the message in double quotes. For example,
383N/Aexisting instances of <
blockquote><
code>ErrorDocument 403 "Some
383N/AMessage</
code></
blockquote> should be replaced with
383N/A<
blockquote><
code>ErrorDocument 403 "Some
383N/AMessage"</
code></
blockquote> As long as the second argument is not a
383N/Avalid URL or pathname, it will be treated as a text message.</
li>
383N/A<
li>The <
code>AccessConfig</
code> and <
code>ResourceConfig</
code>
383N/Adirectives no longer exist. Existing instances of these directives
383N/Acan be replaced with the <
a 383N/Ahas equivalent functionality. If you were making use of the default
383N/Avalues of these directives without including them in the configuration
383N/Aassure that Apache reads the configuration files in the same order as
383N/Awas implied by the older directives, the <
code>Include</
code>
383N/A<
li>The <
code>BindAddress</
code> directive no longer exists.
383N/AEquivalent functionality is provided with the more flexible <
code><
a 383N/A<
li>The <
code>ExtendedStatus</
code> directive no longer exists.
383N/AStatus reporting has been completely rewritten to take advantage
383N/Aof the new MPM system.</
li>
383N/A<
li>The <
code>ServerType</
code> directive no longer exists.
383N/AThe method used to serve requests is now determined by the selection
4352N/Aof MPM. There is currently no MPM designed to be launched by
3888N/A<
li>Many directives that were in the core server in Apache 1.3
383N/A<
li>The mod_log_agent and mod_log_referer modules which provided the
383N/A<
code>AgentLog</
code>, <
code>RefererLog</
code> and
383N/A<
code>RefererIgnore</
code> directives have been removed. Agent and
383N/Areferer logs are still available using the <
a 383N/A<
li>Graceful restarts of the server are now executed by signaling the
383N/Aparent process with <
code>WINCH</
code> rather than
3888N/A<
li>The <
code>httpd</
code> command line option <
code>-S</
code>
4352N/Awhich was used for printing the virtual host configuration has
3888N/Abeen replaced by <
code>-t -D DUMP_VHOSTS</
code>.</
li>
3888N/A<
li>The <
code>httpd</
code> command line option <
code>-X</
code> has
3888N/Abeen removed. Most MPMs allow the same functionality to be requested
3888N/Aby setting the <
code>ONE_PROCESS</
code> and <
code>NO_DETACH</
code>
383N/Aenvironment variables prior to launching <
code>httpd</
code>.</
li>
383N/A<
li>The module mod_auth_digest, which was experimental in Apache 1.3
383N/Ais now a standard module.</
li>
383N/A<
li>The mod_mmap_static module, which was experimental in Apache 1.3
383N/Ahas been replaced with mod_file_cache.</
li>
497N/A<
H3>Third Party Modules</
H3>
383N/A<
p>Extensive changes were made to the server API in Apache 2.0.
497N/AExisting modules designed for the Apache 1.3 API will <
strong>not</
strong>
383N/Awork in Apache 2.0 without modification. Details are provided in
497N/Athe <
a href="developer/">developer documentation</
a>.</
p>