ID:               19113
 Comment by:       kustosz at bv dot pl
 Reported By:      php_new at jdc dot parodius dot com
 Status:           Bogus
 Bug Type:         Apache related
 Operating System: FreeBSD
 PHP Version:      4.3.2-dev
 New Comment:

apache 1.3.27, php 4.3.1 (LoadModule), the problem of bad 200 response
code exist.

according to the first email, the known (for me) solution for this
problem is to create index.html page and in this page redirect to
index.php, then the response code id 405.


Previous Comments:
------------------------------------------------------------------------

[2003-06-03 22:47:22] php_new at jdc dot parodius dot com

I don't use mod_perl.  The only third-party module I use besides
mod_php is mod_watch, which is not the core of the problem (I've tried
removing it; same result).

Without mod_php installed, this problem disappears.

List of modules loaded:
Loaded Modules  mod_watch, mod_php4, mod_setenvif, mod_so,
mod_usertrack, mod_headers, mod_expires, mod_auth_db, mod_auth,
mod_access, mod_alias, mod_userdir, mod_actions, mod_cgi, mod_dir,
mod_autoindex, mod_include, mod_mime, mod_log_config, mod_env,
mod_mmap_static, http_core

SERVER_SOFTWARE  Apache/1.3.27 (Unix) mod_watch/3.17 PHP/4.3.2RC4  

If I open up an Apache bug report, there is going to be a lot of
finger-pointing.  Are we sure we want to do this?  Is it at all
possible to get the PHP developers to open a report about this problem
rather than the end-user?

------------------------------------------------------------------------

[2003-06-03 22:17:59] [EMAIL PROTECTED]

See comment by: [16 Mar 6:40am CST] psi-jack at myrddincd dot com 

------------------------------------------------------------------------

[2003-06-03 15:09:31] php_new at jdc dot parodius dot com

Sorry, change of Email address.

------------------------------------------------------------------------

[2003-06-03 15:07:22] php at jdc dot parodius dot com

AFAIK, still applies to PHP 4.3.2.  And who set this to Status Bogus? 
It's not bogus.  It's a major faultpoint.

------------------------------------------------------------------------

[2003-05-31 02:30:15] jtrh at jtrh dot com

Just installed php4-STABLE-latest.tar.gz and the problem continues.
This bug has produced me hundreds of thousands of CONNECT x.x.x.x:25
HTTP/1.0 logs, and made the PHP counter on my index.php to go to a very
high number.

The "Limit CONNECT" fix showed here messed up my web server, allowing
the reading of .htpasswd files.

If someone knows where can I find a patch or a good configuration
workaround please post it here, it will be of great help to many
people.

Thanks.

------------------------------------------------------------------------

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/19113

-- 
Edit this bug report at http://bugs.php.net/?id=19113&edit=1

Reply via email to