upgrading.html revision f4d23ce8ea0d2ac6133a86d465f2147be6ac30f5
edd67c61375d89ff863e754caff339cd1ac77b38vboxsync<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
edd67c61375d89ff863e754caff339cd1ac77b38vboxsync<!-- Background white, links blue (unvisited), navy (visited), red (active) -->
edd67c61375d89ff863e754caff339cd1ac77b38vboxsync BGCOLOR="#FFFFFF"
edd67c61375d89ff863e754caff339cd1ac77b38vboxsync TEXT="#000000"
edd67c61375d89ff863e754caff339cd1ac77b38vboxsync LINK="#0000FF"
edd67c61375d89ff863e754caff339cd1ac77b38vboxsync VLINK="#000080"
edd67c61375d89ff863e754caff339cd1ac77b38vboxsync ALINK="#FF0000"
edd67c61375d89ff863e754caff339cd1ac77b38vboxsync<!--#include virtual="header.html" -->
edd67c61375d89ff863e754caff339cd1ac77b38vboxsync<P>In order to assist folks upgrading, we maintain a document
edd67c61375d89ff863e754caff339cd1ac77b38vboxsyncdescribing information critical to existing Apache users. These are
edd67c61375d89ff863e754caff339cd1ac77b38vboxsyncintended to be brief notes, and you should be able to find more
edd67c61375d89ff863e754caff339cd1ac77b38vboxsyncinformation in either the <A HREF="new_features_2_0.html">New
edd67c61375d89ff863e754caff339cd1ac77b38vboxsyncFeatures</A> document, or in the <CODE>src/CHANGES</CODE> file.
edd67c61375d89ff863e754caff339cd1ac77b38vboxsync<LI>Apache now uses an <code>autoconf</code> and <code>libtool</code>
edd67c61375d89ff863e754caff339cd1ac77b38vboxsyncsystem for configuring the build processes. Using this system
edd67c61375d89ff863e754caff339cd1ac77b38vboxsyncis similar to, but not the same as, using the APACI system in
edd67c61375d89ff863e754caff339cd1ac77b38vboxsyncApache 1.3. Further documentation to follow.</li>
edd67c61375d89ff863e754caff339cd1ac77b38vboxsync<li>In addition to the usual selection of modules which you can choose
edd67c61375d89ff863e754caff339cd1ac77b38vboxsyncto compile, Apache 2.0 has moved the main part of request processing
edd67c61375d89ff863e754caff339cd1ac77b38vboxsyncinto <a href="mpm.html">Multi-Processing Modules</a> (MPMs).</li>
edd67c61375d89ff863e754caff339cd1ac77b38vboxsync<li>The <code>CacheNegotiatedDocs</code> directive now takes
edd67c61375d89ff863e754caff339cd1ac77b38vboxsyncthe argument <code>on</code> or <code>off</code>. Existing
edd67c61375d89ff863e754caff339cd1ac77b38vboxsyncinstances of <code>CacheNegotiatedDocs</code> should be replaced
edd67c61375d89ff863e754caff339cd1ac77b38vboxsync<li>The <code>ErrorDocument</code> directive no longer uses a quote at
edd67c61375d89ff863e754caff339cd1ac77b38vboxsyncthe beginning of the argument to indicate a text message. Instead,
edd67c61375d89ff863e754caff339cd1ac77b38vboxsyncyou should enclose the message in double quotes. For example,
edd67c61375d89ff863e754caff339cd1ac77b38vboxsyncexisting instances of <blockquote><code>ErrorDocument 403 "Some
edd67c61375d89ff863e754caff339cd1ac77b38vboxsyncMessage"</code></blockquote> As long as the second argument is not a
edd67c61375d89ff863e754caff339cd1ac77b38vboxsyncvalid URL or pathname, it will be treated as a text message.</li>
directives should be placed at the end of httpd.conf, with the one for
<!--#include virtual="footer.html" -->