www-apache-bugdb mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Remco v.Hest <s...@arachnafobic.cx>
Subject general/5580: I keep getting 403's on cgi's en server-status after compiling on a smp box
Date Thu, 13 Jan 2000 15:44:59 GMT

>Number:         5580
>Category:       general
>Synopsis:       I keep getting 403's on cgi's en server-status after compiling on a smp
>Confidential:   no
>Severity:       critical
>Priority:       medium
>Responsible:    apache
>State:          open
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Thu Jan 13 07:50:00 PST 2000
>Originator:     spin@arachnafobic.cx
>Release:        1.3.9
Linux linuxserver 2.2.14 #1 SMP Wed Jan 5 09:47:09 CET 2000 i686 unknown
pgcc-2.95.2 & gcc-
A few months ago I build a webserver for the coop. I work for. It looks like this:
Server Version: Apache/1.3.9 (Unix) PHP/3.0.12 mod_ssl/2.4.8 OpenSSL/0.9.4
Server Built: Nov 16 1999 09:25:57

This works fine, but since some of these version are out dated now and because 
I wanted to include mod_auth_mysql, which I also use at home together with mod_ssl and php3
(no problems here).
But every time I start the new server and want to test it all the cgi's and
the server-status url come up with a 403. :(

Even compiling exactly the same server again fails, the old one dates from when
the box was nonsmp, since it is smp no apache has yet been succesfully used exempt the old
(which was compiled on a pII350 nonsmp system, but also works with changes on the smp system)

I would like to know if this problem comes with apache or with an other module
I'm compiling with it ?
(I'm thinking its smp related, although I'm praying that I'm wrong)
Somewhere in this step-by-step it fails (no error, but de bugs come when running)

    $ cd mod_ssl-2.4.10-1.3.9
    $ ./configure \

    $ cd ../mod_auth_mysql-2.20
    $ ./configure \
          --with-mysql=/usr/local/mysql \
    $ make

    $ cd ../apache_1.3.9
    $  ./configure \

    $ cd ../php-3.0.13
    $ CFLAGS='-O2 -I/usr/local/ssl/include' \
      ./configure \
          --with-apache=../apache_1.3.9 \
          --with-mysql=/usr/local/mysql \
          --enable-memory-limit=yes \
          --enable-debug=no \
    $ make
    $ make install

    $ cd ../apache_1.3.9
    $ SSL_BASE=/usr/local/ssl \
      ./configure \
          --prefix=/usr/local/apache \
          --enable-module=ssl \
          --activate-module=src/modules/php3/libphp3.a \
          --enable-module=php3 \
          --enable-module=info \
          --enable-module=rewrite \
          --enable-module=proxy \
          --add-module=../mods/mod_bandwidth/mod_bandwidth.c \
          --add-module=../mods/mod_roaming/mod_roaming.c \
          --add-module=../mods/mod_urlcount/mod_urlcount.c \
          --add-module=../mod_layout-0.5/mod_layout.c \
    $ make
    $ make certificate
    $ make install
    $ cd ..

(mods/ = apache-contrib-1.0.7)
Searching for a fix/answer
 [In order for any reply to be added to the PR database, you need]
 [to include <apbugs@Apache.Org> in the Cc line and make sure the]
 [subject line starts with the report component and number, with ]
 [or without any 'Re:' prefixes (such as "general/1098:" or      ]
 ["Re: general/1098:").  If the subject doesn't match this       ]
 [pattern, your message will be misfiled and ignored.  The       ]
 ["apbugs" address is not added to the Cc line of messages from  ]
 [the database automatically because of the potential for mail   ]
 [loops.  If you do not include this Cc, your reply may be ig-   ]
 [nored unless you are responding to an explicit request from a  ]
 [developer.  Reply only with text; DO NOT SEND ATTACHMENTS!     ]

View raw message