Apache HTTP Server Version 1.3
Is this the version you want? For more recent
versions, check our documentation
Upgrading to 1.3 from 1.2
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
src/CHANGES file which tracks
These are intended to be brief notes, and you should be able
to find more information in either the New Features document, or in
Compile-Time Configuration Changes
- The source code has been reorganized, which affects anyone
with custom modules or modifications. But also, the
Module directive has been changed to the
EXTRA_LFLAGS has been renamed
-DMAXIMUM_DNS definition has been
obsoleted by changes to
double-reverse DNS lookups when necessary.
compile-time option has been replaced with the run-time API
modification of the server identity by the configuration
scripts is no longer supported.
mod_dir has been split into two pieces
been replaced by
- IRIX systems with untrusted users who can write CGIs
which execute as the same uid as httpd should consider using
suexec, or adding
EXTRA_CFLAGS. This is slower, more information
is available on the performance tuning
page. There is a mild denial of service attack possible
with the default config, but the default config is an order
of magnitude faster.
mod_auth_msql has been removed from the
- 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.
Run-Time Configuration Changes
ServerType inetd has been deprecated. It
still exists, but bugs are unlikely to be fixed.
httpd_monitor has been deprecated. The
replacement is to use
mod_status and make a
request to a URL such as
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
(e.g., perl) this shouldn't have a detrimental
effect on performance.
"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".
dbmmanage has been overhauled.
Third Party Modules
The following changes between the 1.2 and 1.3 API may
require slight changes in third party modules not maintained by
Apache HTTP Server