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
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<HTML><HEAD>
<TITLE>Upgrading to 1.3 from 1.2</TITLE>
</HEAD>
<!-- Background white, links blue (unvisited), navy (visited), red (active) -->
<BODY
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#000080"
ALINK="#FF0000"
>
<DIV ALIGN="CENTER">
<IMG SRC="images/sub.gif" ALT="[APACHE DOCUMENTATION]">
<H3>
Apache HTTP Server Version 1.3
</H3>
</DIV>
<H1 ALIGN="CENTER">Upgrading to 1.3 from 1.2</H1>
<P>In order to assist folks upgrading we are now going to maintain a
document describing information critical to existing Apache users. Note
that it only lists differences between recent major releases, so
for example, folks using Apache 1.1 or earlier will have to figure out
what changed up to Apache 1.2 before this document can be considered
relevant. Old users could look at the <CODE>src/CHANGES</CODE> file
which tracks code changes.
<P>These are intended to be brief notes, and you should be able to find
more information in either the <A HREF="new_features_1_3.html">New Features</A>
document, or in the <CODE>src/CHANGES</CODE> file.
<H3>Compile-Time Configuration Changes</H3>
<UL>
<LI>The source code has been <A HREF="sourcereorg.html">reorganized</A>,
which affects anyone with custom modules or modifications. But also,
the <CODE>Module</CODE> directive has been changed to the
<CODE>AddModule</CODE> directive.
<LI>The <CODE>Configuration</CODE> variable <CODE>EXTRA_LFLAGS</CODE> has
been renamed <CODE>EXTRA_LDFLAGS</CODE>.
<LI>The <CODE>-DMAXIMUM_DNS</CODE> definition has been obsoleted by
changes to <CODE>mod_access</CODE> enforcing double-reverse DNS lookups
when necessary.
<LI>The <CODE>-DSERVER_SUBVERSION=\"string\"</CODE> compile-time option has
been replaced with the run-time API call
<CODE>ap_add_version_component()</CODE>. Compile-time modification of the
server identity by the configuration scripts is no longer supported.
</LI>
<LI><CODE>mod_dir</CODE> has been split into two pieces
<CODE><A HREF="mod/mod_autoindex.html">mod_autoindex</A></CODE>, and
<CODE><A HREF="mod/mod_dir.html">mod_dir</A></CODE>.
<LI><A HREF="mod/mod_browser.html"><CODE>mod_browser</CODE></A> has been
replaced by <A HREF="mod/mod_setenvif.html"><CODE>mod_setenvif</CODE></A>.
<LI>IRIX systems with untrusted users who can write CGIs which execute
as the same uid as httpd should consider using <CODE>suexec</CODE>,
or adding <CODE>-DUSE_FCNTL_SERIALIZED_ACCEPT</CODE> to
<CODE>EXTRA_CFLAGS</CODE>. This is slower, more information is available
on the <A HREF="misc/perf-tuning.html#serialize">performance tuning
page</A>. There is a mild denial of service attack possible with the
default config, but the default config is an order of magnitude faster.
<LI><CODE>mod_auth_msql</CODE> has been removed from the distribution.
<LI>The new Apache Autoconf-style Interface (APACI) was added to
the top-level to provide a real out-of-the-box build and installation
procedure for the complete Apache package.
</UL>
<H3>Run-Time Configuration Changes</H3>
<UL>
<LI>There have been numerous changes to the default config files.
Ensure that you compare your existing configuration files with the
new ones to ensure there aren't any undesired differences. In
particular:
<UL>
<LI>As of Apache 1.3.0, the current config files apply different
<A HREF="mod/core.html#options">Options</A> and
<A HREF="mod/core.html#allowoverride">AllowOverride</A> settings to
various directories than were used in 1.2.
</LI>
<LI>As of the release following Apache 1.3.3, the three
config file templates have been merged into <SAMP>httpd.conf-dist</SAMP>
and the order of the directives changed.
</LI>
</UL>
<LI>As of 1.3.2, <A HREF="mod/mod_expires.html"><CODE>mod_expires</CODE></A>
will add Expires headers to content that does not come from a file
on disk, unless you are using a modification time based setting.
Previously, it would never add an Expires header unless content came
from a file on disk. This could result in Expires headers being added
in places where they were not previously added.
<LI>Standalone <STRONG><SAMP>FancyIndexing</SAMP></STRONG> directives
are now combined with the settings of any <SAMP>IndexOptions</SAMP>
directive already in effect, rather than replacing them.
</LI>
<LI><STRONG><SAMP>AuthName</SAMP> strings will need to be quoted</STRONG>
in <SAMP>.htaccess</SAMP> or server configuration files if they contain
blank characters (like spaces). For example, if you use
an <SAMP>AuthName</SAMP> directive like this:
<P>
<PRE>
AuthName This and That
</PRE>
</P>
you will need to change it to
<P>
<PRE>
AuthName "This and That"
</PRE>
</P>
This change was made for consistency in the config language.
<LI><STRONG>As of Apache 1.3.1, methods listed in <SAMP><Limit></SAMP>
directives must be uppercase.</STRONG> Method names, such as
<SAMP>GET</SAMP>, <SAMP>POST</SAMP>, and <SAMP>PUT</SAMP> are
defined as being case-sensitive. That is, a <SAMP>GET</SAMP>
request is different from a <SAMP>get</SAMP> request. Prior
to Apache 1.3.1, the <SAMP><Limit></SAMP> directive
parser incorrectly treated both of these as being the same.
Apache's built-in method limit processing currently only understands
uppercase method names, so if you've used clauses such as
"<SAMP><Limit Get post></SAMP>" in your configuration
files, you need to correct them to use uppercase names.
<P>
Unrecognized method names in the server configuration files will
result in the server logging an error message and failing to start.
In <SAMP>.htaccess</SAMP> files, unknown methods will cause the
server to log an error to its error log and return an 'Internal
Server Error' page to the client.
</P>
</LI>
<LI><STRONG>The default Apache ServerRoot directory changed</STRONG>
from the NCSA-compatible <SAMP>/usr/local/etc/httpd/</SAMP> to
<SAMP>/usr/local/apache/</SAMP>. This change covers only the default
setting (and the documentation); it is of course possible to override it
using the <EM>-d ServerRoot</EM> and <EM>-f httpd.conf</EM> switches
when starting apache.
<LI>Folks using HTTP/1.1-style virtual hosting will need to list the
ip:port pairs that are supposed to have HTTP/1.1-style virtual hosting
via the <A HREF="mod/core.html#namevirtualhost"><CODE>
NameVirtualHost</CODE></A> directive (one directive per pair).
Previously this support was given implicitly on the "main server
address". Now it has to be explicitly listed so as to avoid many
problems that users had.
Please see the <A HREF="vhosts/index.html">Apache Virtual Host
documentation</A> for further details on configuration.
<LI>The precedence of virtual hosts has been reversed (applies mainly to
vhosts using HTTP/1.1 Host: headers, and the
<A HREF="mod/core.html#serverpath">ServerPath</A> directive). Now
the earlier vhosts in the file have precedence over the later vhosts.
<LI><CODE>HostnameLookups</CODE> defaults to Off.
<LI><STRONG><SAMP>REMOTE_HOST</SAMP> CGI variable changed.</STRONG>
In Apache 1.2 and earlier, the <SAMP>REMOTE_HOST</SAMP> environment
variable made available to CGI scripts was set to either the
full DNS name of the client, or else to the client's IP address
if the name was not known. This behaviour differed from that
specified by the CGI specification, which defines this variable as being
NULL if the name isn't known. In Apache 1.3, we have made this correction.
<SAMP>REMOTE_ADDR</SAMP> always contains the client's IP address,
but <SAMP>REMOTE_HOST</SAMP> is only defined when the server has
been able to determine the client's DNS name.
</LI>
<LI>The undocumented
<A HREF="mod/mod_access.html"><CODE>mod_access</CODE></A>
syntax "allow user-agents" was removed. The replacement is the
more general "allow from env".
<LI>When using wildcards in pathnames (such as * and ?) they no longer
match / (slash). That is, they more closely behave how a UNIX shell
behaves. This affects <CODE><Directory></CODE> directives,
for example.
<LI>If no <CODE>TransferLog</CODE> directive is given then nothing will
be logged.
(Previously it would default to <CODE>logs/access_log</CODE>.)
<LI>Apache now has <A HREF="mod/core.html#loglevel">configurable error
logging levels</A>, and the default eliminates some messages that
earlier versions always generated.
<LI>When booting, Apache will now detach itself from stdin, stdout,
and stderr. stderr will not be detached until after the config
files have been read so you will be able to see initial error
messages. After that all errors are logged in the error_log.
This makes it more convenient to start Apache via rsh, ssh,
or crontabs.
<LI><Files> sections previously could take a full pathname, and
were matched against the full pathnames. This had some
inconsistencies, and was removed. To emulate this older behaviour
use a <Files> section nested inside a <Directory>
section.
<LI><Location> matching behaviour with respect to slashes has
changed. See the <A HREF="mod/core.html#location"><Location>
documentation</A> for more info.
</UL>
<H3>Misc Changes</H3>
<UL>
<LI><CODE>ServerType inetd</CODE> has been deprecated. It still exists,
but bugs are unlikely to be fixed.
<LI><CODE>httpd_monitor</CODE> has been deprecated. The replacement is
to use <CODE>mod_status</CODE> and make a request to a URL such as
<CODE>http://myhost/server-status?refresh=10</CODE>.
<LI>
Apache now provides an effectively unbuffered connection for
CGI scripts. This means that data will be sent to the client
as soon as the CGI pauses or stops output; previously, Apache would
buffer the output up to a fixed buffer size before sending, which
could result in the user viewing an empty page until the CGI finished
or output a complete buffer. It is no longer necessary to use an
"nph-" CGI to get unbuffered output. Given that most CGIs are written
in a language that by default does buffering (<EM>e.g.</EM>, perl) this
shouldn't have a detrimental effect on performance.
<P>"nph-" CGIs, which formerly provided a direct socket to the client
without any server post-processing, were not fully compatible with
HTTP/1.1 or SSL support. As such they would have had to implement
the transport details, such as encryption or chunking, in order
to work properly in certain situations. Now, the only difference
between nph and non-nph scripts is "non-parsed headers".
<LI>
<CODE>dbmmanage</CODE> has been overhauled.
</UL>
<H3>Third Party Modules</H3>
<P>The following changes between the 1.2 and 1.3 API may require slight
changes in third party modules not maintained by Apache.
<UL>
<LI>
To avoid symbol clashes with third-party code compiled into the server, the
general prefix `<CODE>ap_</CODE>' was globally applied to the following
classes of symbols: Apache provided general functions (<EM>e.g.</EM>,
<CODE>ap_cpystrn</CODE>), public API functions (<EM>e.g.</EM>,
<CODE>palloc</CODE>,
<CODE>bgets</CODE>) and private functions which can't be made static
(because of cross-object usage) but should be (<EM>e.g.</EM>,
<CODE>new_connection</CODE>). For backward source compatibility with
Apache 1.2 a new header file named <CODE>compat.h</CODE> was created which
provides defines for the old symbol names.
You'll either have to <CODE>#include compat.h</CODE> or update the API
symbols you use.
</LI>
<LI>
Be sure and examine the <A HREF="sourcereorg.html">source code
reorganization page</A> to see whether any item there affects you.
</LI>
<LI>Use of <SAMP>SERVER_VERSION</SAMP> definition. If third-party
modules reference the server version string using this symbol,
they should be corrected to obtain it by calling the new API routine
<CODE>const char *ap_get_server_version()</CODE>.
</LI>
<LI><CODE>ap_construct_url</CODE> prototype change. The second parameter
was previously a <CODE>server_rec</CODE>, it has been changed to
a <CODE>request_rec</CODE>.
<LI>The <CODE>table</CODE> datatype has been made an opaque type.
Code which assumes a <CODE>table</CODE> is the same as an
<CODE>array_header</CODE> will not compile. This is actually a
change to enforce the API the way it was intended, all versions
of Apache have had a <CODE>table_elts()</CODE> function which
is intended for code which needs to access the elements of
a table. The changes required for this are pretty easy, and
work with all versions of Apache.
<P>Suppose <CODE>t</CODE> is a table. Whenever code refers to
<CODE>t->elts</CODE>, replace it with something like this:
<BLOCKQUOTE><PRE>
array_header *arr = table_elts(t);
table_entry *elts = (table_entry *)arr->elts;
</PRE></BLOCKQUOTE>
Whenever code refers to <CODE>t->nelts</CODE> use
<CODE>arr->nelts</CODE>. Many examples can be found in
the standard modules, search for <CODE>table_elts</CODE>.
</LI>
</UL>
<HR>
<H3 ALIGN="CENTER">
Apache HTTP Server Version 1.3
</H3>
<A HREF="./"><IMG SRC="images/index.gif" ALT="Index"></A>
</BODY>
</HTML>
|
