1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
|
<!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 configuring the build processes. Using this system
is similar to, but not the same as, using the APACI system in
Apache 1.3. Further documentation to follow.</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>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>ExtendedStatus</code> directive no longer exists.
Status reporting has been completely rewritten to take advantage
of the new MPM system.</li>
<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>
|
