ID: 42634
Updated by: [EMAIL PROTECTED]
Reported By: php at transpect dot com
-Status: Open
+Status: Bogus
Bug Type: Apache2 related
Operating System: Gentoo Linux
PHP Version: 5.2.4
New Comment:
Apache bugs are not PHP bugs. Please report this to Apache people
instead.
Previous Comments:
------------------------------------------------------------------------
[2007-09-13 14:22:14] 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-13 10:11:20] [EMAIL PROTECTED]
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-12 14:45:16] 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-12 14:36:16] 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 13:55:18] 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.
------------------------------------------------------------------------
The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
http://bugs.php.net/42634
--
Edit this bug report at http://bugs.php.net/?id=42634&edit=1
