php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login

go to bug id or search bugs for

Bug #42634 Apache 2.2.6 + PHP 5.2.4 => 302
Submitted: 2007-09-12 01:42 UTC Modified: 2007-09-18 12:30 UTC
Votes:1
Avg. Score:4.0 ± 0.0
Reproduced:1 of 1 (100.0%)
Same Version:1 (100.0%)
Same OS:1 (100.0%)
From: php at transpect dot com Assigned:
Status: Not a bug Package: Apache2 related
PHP Version: 5.2.4 OS: Gentoo Linux
Private report: No CVE-ID: None
View Developer Edit
 [2007-09-12 01:42 UTC] php at transpect dot com 
Description:
------------
Apache 2.2.6 with php 5.2.3's libphp5.so works fine. But with 5.2.4 Apache starts without error, but every request to the server (whether to a PHP or HTML page) results in a blank page in the browser, and a "302" (redirect) rather than a "200" response in the log. In all respects this is the same system except for the switch between 5.2.3 and 5.2.4.


Reproduce code:
---------------
These are the configuration options used - building by hand in each case:

HTTPD
./configure --enable-so --enable-ssl --enable-rewrite
PHP
./configure --with-apxs2=/usr/local/apache2/bin/apxs --with-mysql --disable-cgi

Patches

Pull Requests

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2007-09-12 11:39 UTC] jani@php.net 
Are you sure you have installed PHP correctly? That same combination works just fine for me..
 [2007-09-12 13:55 UTC] php at transpect dot com 
Hi Jani, I used the same standard installation steps for PHP 5.2.3 and 5.2.4 - and also now php5.2-200709120230, which also produces this strange 302 result. I configure as above, make, make test (all versions failed a couple of tests and I sent in the reports), make install (then eliminate the redundant module load that make install keeps putting in httpd.conf - it should check first).

I'm sure he combination works for most people, or there'd be other reports of trouble by now. That something different in the PHP module could cause HTML pages to load wrong seems like there has to be an Apache bug involved - it shouldn't be possible for a module to cause a misfire in stuff it shouldn't even handle. There must be something peculiar to my system, but I'm really scratching my head on what could cause it to work fine with 5.2.3 but serve 302's rather than pages with 5.2.4.
 [2007-09-12 14:36 UTC] php at transpect dot com 
Here are the tests failed by 5.2.4 on my system, just in case they are pertinent:

Bug #16069 (ICONV transliteration failure) [ext/iconv/tests/bug16069.phpt]
iconv stream filter [ext/iconv/tests/iconv_stream_filter.phpt]
Bug #41567 (json_encode() double conversion is inconsistent with PHP) [ext/json/tests/bug41567.phpt]
Test lstat() and stat() functions: usage variations - effects of touch() on link [ext/standard/tests/file/lstat_stat_variation6.phpt]
 [2007-09-12 14:45 UTC] php at transpect dot com 
Maybe narrowing it down:

PHP 5.2.4 built against Apache 2.2.4 works - both with Apache 2.2.4 and 2.2.6. (The PHP 5.2.3 module that works with both Apaches was also built against Apache 2.2.4.) So the bug only enters building PHP 5.2.4 (and last night's snapshot) against Apache 2.2.6.
 [2007-09-13 10:11 UTC] jani@php.net 
To be sure it's regression between 5.2.3 / 5.2.4 can you try with PHP 5.2.3 + Apache 2.2.6 ?
 [2007-09-13 14:22 UTC] php at transpect dot com 
PHP 5.2.3 built against Apache 2.2.6 also produces the 302 error.

So it seems to be something about Apache 2.2.6 (at least on my system) that's included by PHP 5.2.3 and 5.2.4 when the module's built?
 [2007-09-18 12:30 UTC] jani@php.net 
Apache bugs are not PHP bugs. Please report this to Apache people instead.
 
PHP Copyright © 2001-2025 The PHP Group
All rights reserved. 		Last updated: Wed Apr 30 20:01:28 2025 UTC