From: pcs Date: Fri, 11 Jul 1997 13:01:19 +0000 (+0000) Subject: Bring known bugs in 1_2_X up-to-date from HEAD X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=2c25910d87137d2b1cc549ac4bc69c3b01257c68;p=thirdparty%2Fapache%2Fhttpd.git Bring known bugs in 1_2_X up-to-date from HEAD git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/branches/1.3@78588 13f79535-47bb-0310-9956-ffa450edef68 --- diff --git a/APACHE_1_2_X/htdocs/manual/misc/known_bugs.html b/APACHE_1_2_X/htdocs/manual/misc/known_bugs.html index 8ce19caeff7..cc376902999 100644 --- a/APACHE_1_2_X/htdocs/manual/misc/known_bugs.html +++ b/APACHE_1_2_X/htdocs/manual/misc/known_bugs.html @@ -27,8 +27,41 @@ in early versions have been fixed in 1.2.

Apache 1.2 Bugs

-
    -
  1. On some architectures if your configuration uses multiple +
      +
    1. Exists in 1.2.1 only. + On Solaris 2.x the server will stop running after receiving a + SIGHUP. Four workarounds exist (choose one):

      +

        +
      • Retrieve this patch. + cd to your apache_1.2.1 directory, and + type patch -s -p1 < /path/to/patchfile. Then rebuild + Apache.

        +

      • Use SIGUSR1 instead of SIGHUP, see + Stopping and Restarting Apache for more details.

        +

      • Add -DNO_SLACK to + EXTRA_CFLAGS in + your Configuration file, re-run Configure + and rebuild your server. This disables the + descriptor slack workaround

        +

      • (Least preferable) Use Apache 1.2.0 instead of 1.2.1.

        +

      + This problem will be tracked as + PR#832.

      +

      2. + +
    2. (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. +

      + +

    3. 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 @@ -43,12 +76,11 @@ in early versions have been fixed in 1.2. PR#467.

      4. -
    4. Fixed in 1.2.1. - Apache's Content + Apache's Content 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. + longer does this unless all the variants have character sets. This patch fixes this problem. It also fixes the problem which makes Apache pick the last equally acceptable variant instead of the first. @@ -58,7 +90,7 @@ in early versions have been fixed in 1.2.
    5. The PATH_INFO part of a request URI cannot include the sequence - %2f. This will be tracked as + %2f. This will be tracked as PR#543.

      6. @@ -80,15 +112,15 @@ in early versions have been fixed in 1.2.
    6. 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 -lbind - to EXTRA_LFLAGS in Configuration. See + explicitly link with the bind library by adding -lbind + to EXTRA_LDFLAGS in Configuration. See PR#616 - and the + and the Apache FAQ.

    7. The message "created shared memory segment #730499" - in error_log is not an error and should be ignored. See + in error_log is not an error and should be ignored. See PR#696.

      8. @@ -104,7 +136,7 @@ in early versions have been fixed in 1.2. virtual hosts. This appears similar to a file-descriptor limit but BSDI should not have this problem. This will be tracked as PR#611. - See also the Apache FAQ. + See also the Apache FAQ.

    8. Workaround available in 1.2.1.