ID: 19113 Comment by: jtrh at jtrh dot com Reported By: php at jdc dot parodius dot com Status: Bogus Bug Type: Apache related Operating System: FreeBSD PHP Version: 4.3.2-dev New Comment:
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. Previous Comments: ------------------------------------------------------------------------ [2003-03-16 10:59:02] [EMAIL PROTECTED] As per last comment..bogus. (I couldn't reproduce this, but then again, I don't have mod_perl..) ------------------------------------------------------------------------ [2003-03-16 06:40:23] psi-jack at myrddincd dot com I've been testing out all the comments mentioned in this report. The findings I have, is with Apache 1.3.27, and various modules. The modules I use is mod_php 4.3.0, mod_perl 1.27, mod_mp3 0.39, and for mod_perl, I had HTML-Mason and AxKit, and various other non-advertising mod_perl modules. What did I find? With all the mentioned modules loaded, I get the same results as mentioned within these comments. \xe3P TINTE / HTTP/1.0 CONNECT www.google.com:80 HTTP/1.0 Etc, all these, provide the default page, wether it's a DirectoryIndex, or directory listing itself. I unloaded mod_php, as per this bug was about. Still, same results. Once I unloaded mod_perl, however, the problem went away. I started getting 501's with those requests. mod_mp3 didn't seem to effect that at all. My final conclusion, this is very likely to be an Apache DSO bug, and not related directly to PHP, since it occured with mod_perl as well. The only one thing I did not try, was unloading my perlmodules from mod_perl. ------------------------------------------------------------------------ [2003-03-07 10:33:38] php at jdc dot parodius dot com Verified that the latest PHP -STABLE- snapshot does not fix this problem. I fully agree with what keitaro said; this kind-of software QA testing is ineffective. The problem is reproducable, and is _very_ easy to check for, especially since it happens out-of-the-box. I read the NEWS file every time I'm asked to test, just to see if there's anything which looks applicable -- and there never is. I've much respect for the PHP crew, but this style of testing is tedious. Please have a developer *investigate* this problem, rather than just throwing CVS builds at end-users every [X] days, hoping that some other bug was the cause of the problem. Heck, I'm still waiting to know if it's a problem with PHP or Apache! ------------------------------------------------------------------------ [2003-03-06 12:40:38] [EMAIL PROTECTED] Please try using this CVS snapshot: http://snaps.php.net/php4-STABLE-latest.tar.gz For Windows: http://snaps.php.net/win32/php4-win32-STABLE-latest.zip ------------------------------------------------------------------------ [2003-03-06 11:30:44] php at jdc dot parodius dot com Confirmed to exist using PHP 4.3.1 on FreeBSD 4.7-STABLE, 4.8-PRERELEASE, and 5.0-CURRENT. I am appalled that this bug has not been escallated to the Critical or Severe status, especially when it has been verified by a PHP developer (01/05/2003; nohn at php dot net). ------------------------------------------------------------------------ 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
