Apache HTTP Server Version 1.3
Known Bugs in Apache
The most up-to-date resource for bug tracking and information is the
Apache bug database.
Significant bugs at release time will also be noted there.
If you are running a 1.2 beta release or version 1.1.3 or earlier
and think you have found a bug, please upgrade to 1.2. Many bugs
in early versions have been fixed in 1.2. It is also appreciated
if you could check the latest 1.3 beta releases, or at least review
the CHANGES file
for it and ensure that your problem has not already been corrected.
This document is not a complete list of known bugs, but simply
a list of some of the more common ones. Be sure
to check the bug database before assuming that if it isn't listed
here it isn't reported or fixed.
See Also: Compatibility notes,
and our list of known client problems.
Apache 1.3b2 Bugs
- CGI scripts that are called with information appended to the script
name that does not have an "
=" in it
do not work.
- Passwords stored in htpasswd files need to be stored in plain text,
since we do not yet have a
crypt() under Win32.
- On Windows 95,
DirectoryIndex does not work.
- On some versions of Windows 95, CGI scripts fail and paths given
with "#!" must contains \ instead of /.
- When a CGI starts with "#!" to indicate an interpreter there must
be no space between the #! and the path.
- If the CGI program cannot be run Apache logs a "premature end-of-headers"
error instead of an error about running the program.
- The USE_FLOCK_SERIALIZED_ACCEPT define is completely broken and does
not work at all. It has been this way since birth. A fix is pending.
Apache 1.3a1 Bugs
directive does not work when running under Windows.
- For some reason, mod_isapi
does not work (with Windows) when compiled using the
Release setting; it will crash the server whenever you
access an ISA DLL. It works fine when the server is compiled with
Apache 1.2 Bugs
Bugs still present in 1.2.4
- On some architectures
if your configuration uses multiple
Listen directives then it is possible
that the server will starve one of the sockets while serving hits on
another. The work-around is to add
-DUSE_FLOCK_SERIALIZED_ACCEPT to the
EXTRA_CFLAGS line in your Configuration and rebuild.
(If you encounter problems with that, you can also try
This affects any architecture that doesn't use one of the
USE_xxxxx_SERIALIZED_ACCEPT definitions, see the
conf.h for your architecture.
This is being tracked as
To resolve this problem, we are adding one of the above settings
to the default settings for platforms as we discover which is
appropriate for them. New as of 1.3b3: the server will
issue a warning when your architecture/config are subject to
this bug. The fixes and such are described in the PORTING
file. We are closing out this bug.
The PATH_INFO part of a request URI cannot include the sequence
%2f. This will be tracked as
- Users of early 1.2 betas reported problems with many
connections stuck in the FIN_WAIT_2 state due to server
timeouts. Several changes were made during the beta testing of 1.2
to reduce this problem as much as possible, although you may still
see sockets in FIN_WAIT_2 state due to network or operating system
issues outside the control of Apache. See our FIN_WAIT_2 page for more details.
SunOS4 has a kernel bug in the allocation of memory for the mbuf table.
When it fills up, the result is a Panic the next time any routine tries
to set something in an imaginary mbuf beyond the range of the table.
Due to buggy browser behavior and the lack of a FIN_WAIT_2 timeout
on SunOS4, "KeepAlive Off" is necessary to avoid filling up the mbuf
table on busy sites.
Compiling on Solaris 2 with SunSoft's C compiler gives the warning
"mod_include.c", line 1123: warning: end-of-loop code not
reached. This is a bogus warning and can be ignored.
- If compilation fails complaining about "unknown symbol __inet_ntoa()"
then you have probably installed version 8 of bind. You will need to
explicitly link with the bind library by adding
Apache FAQ. This is not a bug
- The message "
created shared memory segment #730499"
in error_log is not an error and should be ignored. See
Fixed in 1.2.4:
On Solaris 2.x the server will stop running after receiving a
SIGHUP. Four workarounds exist (choose one):
- Recommended: upgrade to 1.2.4.
- If you are running Apache 1.2.1, retrieve
cd to your
apache_1.2.1 directory, and
patch -s -p1 < /path/to/patchfile. Then rebuild
- Use SIGUSR1 instead of SIGHUP, see
Stopping and Restarting Apache for more details.
Configuration file, re-run
and rebuild your server. This disables the
descriptor slack workaround
This problem was tracked as
- (Exists in 1.2.0 and in 1.2.1 after either of the
NO_SLACK or patch provided by the previous bug are applied.)
Solaris 2.5.1 (and probably other versions of Solaris) appear to have
a race condition completely unrelated to all the others. It is possible
during a SIGHUP that the server will fail to start because it will not
be able to re-open its sockets. To our knowledge this has only shown
up during testing when we pummel the server with as many SIGHUP requests
per second as we can. This appears unrelated to the similar sounding bug
described in PR#832.
Fixed in 1.2.1
- Workaround added
There appears to be a problem on BSDI 2.1 with large numbers of
virtual hosts. This appears similar to a file-descriptor limit
but BSDI should not have this problem. This will be tracked as
See also the Apache FAQ.
- Workaround added.
Solaris 2 has problems with large numbers of virtual hosts. This is
because of an operating system limit of 256 file pointers, not due
to Apache. See also the Apache FAQ.
Negotiation should pick the smallest variant if there
are several that are equally acceptable. A bug in 1.2 means it no
longer does this unless all the variants have character sets.
fixes this problem. It also fixes the problem which makes Apache
pick the last equally acceptable variant instead of the first.
This will be tracked as
Compilation fails on SCO3 when using gcc instead of cc, complaining
gcc: noinline: No such file or directory". Fix
is given in PR#695.
Apache HTTP Server Version 1.3