httpd-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Whit Blauvelt <w...@transpect.com>
Subject [users@httpd] Re: PHP 5.2.4 with Apache 2.2.6 => 302 rather than 200?
Date Thu, 13 Sep 2007 02:33:13 GMT
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 have this problem at all.
> 
> The only difference compared to your build is I use
> PostgreSQL instead of MySQL.

Hi Laurent,

Thanks for the report. If it's something related to configuration, the
question is of course what. The basic configuration has stayed the same from
Apache 2.0 through 2.2.6, but only building PHP 5.2.4 against Apache 2.2.6
presents this strange 302 problem. Building PHP 5.2.3 against Apache 2.2.6,
no problem. Building PHP 5.2.4 against Apache 2.2.4, no problem. And PHP
5.2.4 built against Apache 2.2.4 produces a module that will run against
Apache 2.2.6 with no problem. But the the PHP 5.2.4 module built against
Apache 2.2.6 makes Apache 2.2.6 send a 302 response to every single page
request for every domain and page on the server - despite configuration
files remaining identical.

What species of wrong configuration could produce that very peculiar error
only in this particular circumstance? Nothing's throwing any errors to the
logs. Apache runs, but just serves 302s. This is on a current Gentoo Linux
system - although one that's been around for a few years, so some weirdness
may well have crept in. It's currently running PHP 5.2.4 against Apache
2.2.6 just fine - but the PHP 5.2.4 module compiled against Apache 2.2.4,
not 2.2.6.

Logic suggests a difference in something PHP includes from Apache, that has
changed between Apache 2.2.4 and 2.2.6. Apache 2.2.6 is newer than PHP
5.2.4, so it wouldn't be the PHP team's fault if Apache 2.2.6 breaks
something - or the Apache team's either. But imagining what could produce
this very peculiar sort of breakage is difficult, at least for me. Did you
build your PHP against Apache 2.2.6 or an earlier Apache?

Whit

---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
   "   from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org


Mime
View raw message