The next version of Apache will be 1.2. This will include a
lot of new features, as previewed in our Apache
1.2 article (from issue 29). It will also fix most of the
outstanding bugs identified in 1.1.1. In this issue we
summarise these bugs sorting them by affected function.
There are quite a few bugs listed here, but most will not
have a serious affect on most setups. Many are restricted to
specific operating systems, or to particular configurations
and modules. It should be remembered that Apache 1.1.1 is a
stable release and most users are unlikely to come across
For each bug we have tried to identify its current status in
the latest development version of Apache. If the bug is
followed by the word FIXED then the bug has been fixed and
tested. If the status is VERIFIED then the bug exists but has
not yet been fixed (although in many cases a fix will be in
progress or undergoing initial testing). If neither word is
present, then the bug has not been verified or fixed. We have
tried to ensure that only real bugs are listed here, but the
Apache group receives quite a few bug reports, many of which
relate to incorrectly configured systems or which are caused
by the operating system or other software.
These bugs affect the operation of the core server, or are
related to low-level networking or operating system
DNS Failure causes core dump
Apache can core dump if it cannot obtain the local hostname
from the ServerName directive or from the DNS. FIXED.
High Load Problems
At startup Apache forks the initial children. If it fails
to fork (perhaps because of resource limitations), it
immediately tries again, which can make the load situation
A race condition can cause occasional hung processes on
very high load systems. VERIFIED.
Memory allocation failure causes core dump
The memory allocation return value is not checked which
could cause core dumps. FIXED.
ErrorDocument redirect fails, displays filename.
Docs claim %s in ErrorDocument string prints reason for
error - no code to implement this. VERIFIED
ErrorDocument displays " in string message. FIXED
When a sub-program is about to be run, Apache checks for
correct permissions, but it does not account for other
groups that the current user might be in.
Scoreboard sometimes out of date (shows PID of children
The proxy module has been extensively modified since
1.1.1 to correct a large number of problems and
These bugs are related to specific operating systems.
A/UX: Linger close fails on A/UX FIXED
AIX: Compile warning for SERVICE_UNAVAILABLE
Apollo Domain: Some compilation errors on Apollo
Digital Unix/OSF: V4.0 requires -lm because the
frexp() function has been removed from libc.so.
Incompatible pointer type warning.
IRIX: IRIX kernel fails to notify Apache of dead
Linux: File descriptor bug causing SEGV in
includes module. FIXED.
NeXTSTEP: support/logresolve.c does not compile
because of strdup
OS/2: Simplified code for OS/2 FIXED. OS/2
filesystem is case-independent, can cause URLs to fail
to match protection limitations
QNX: Missing prototypes for QNX FIXED.
SCO: Dumps core in status module with a Floating
exception when compiled with -DSTATUS on SCO ODT 3.0
SGI: Compile warning in http_bprintf FIXED
Ultrix: Compile error in http_main.c
UnixWare: Configuration updated for UnixWare
Finally, a few bugs reports cannot by verified or
discounted. That is, they may or may not exist, but
cannot be reliably reproduced. While they may be Apache
bugs, they could also be bugs in the operating system, or
problems related to particular load conditions or
configurations. Any further information about these
possible bugs should be reported on the apache-bugs email
address or Web page.
CGIs intermittently fail with 'premature end of file
error' on site with 100 vhosts. Occurs even with low
Server will not respond after a few days of running.
Instead of the 5 processes typically running, there is
only one. Server accepts the requests, but never
responds. This site makes heavy use of CGIs (>50% of
Some hits are not logged in the access_log, or logged