On Thu, Sep 13, 2007 at 10:26:12AM +0200, Laurent FAILLIE wrote:
> When I spoke about configuration, I means system
> configuration in general, not only Apache's one.
Hi Laurent,
You may well be right about "system configuration in general." Still, the
question is "What?" I've now confirmed that
On Wed, Sep 12, 2007 at 11:30:59PM +0200, Laurent FAILLIE wrote:
> I think it's something related to your configuration,
> because I built the same configuration on my
> development system (Sun Ultra60 w/ Solaris 10) and on
> my production one (Sun SparcStation 20 under NetBSD
> 3.1) and I don't h
Can you clarify? Apache is running at home? Your trouble accessing it is
from home? From a different machine? The "other devices" are at home, or
external? If your Apache is served from home via your cable modem, has
anyone tried to test it from outside? Have you tried running Apache on a
different
Further clues:
The PHP 5.2.4 module built against Apache 2.2.4 works fine with both Apache
2.2.4 and Apache 2.2.6. So it's only when PHP 5.2.4 is built against Apache
2.2.6 that I end up with Apache serving "302" instead of "200" to every page
request.
The apxs files for both Apache versions are
On Wed, Sep 12, 2007 at 07:51:44AM -0500, McDougall, Marshall (FSH) wrote:
> anything that says, "to upgrade do this". I can't believe it is as
> simple as configure, make, make install and I need to preserve my conf
> files. Any enlightenment appreciated. Thanks.
I've never had it
This is a fairly simple Apache + PHP install, built like this:
HTTPD
./configure --enable-so --enable-ssl --enable-rewrite
PHP
./configure --with-apxs2=/usr/local/apache2/bin/apxs --with-mysql --disable-cgi
Things work fine with PHP 5.2.3 (which was actually built against Apache
2.2.4), but when
