ID: 19113 Comment by: keitaro at attbi dot com Reported By: php at jdc dot parodius dot com Status: Feedback Bug Type: Apache related Operating System: FreeBSD PHP Version: 4.3.1 New Comment:
Out of curiosity, I downloaded and tried the snapshot. No change and still the same. I regret to say that I won't be able to do any further testing unless requested as it gets tiresome to recompile the tarball snapshot so frequently on a P133 (30+ minutes to build). You can wake me up when coffee's really ready... Previous Comments: ------------------------------------------------------------------------ [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). ------------------------------------------------------------------------ [2003-03-06 10:47:22] keitaro at attbi dot com Confirmed this with PHP 4.3.1 on Apache 1.3.27, RH7.3 distro. --quote-start-- I was now able reproduce this problem, but only in case when index.php was in DocumentRoot of first defined name-based virtual server (which is accepted as the default on that IP/port in such case), and index.php was the default script to execute (if there was something before index.php in DirectoryIndex and if it also existed in DocumentRoot of the default vhost, the bug did not apply). --quote-ends--- Problem seem to exist on this scenario. Did a fresh tarball install of PHP 4.3.1 and tested it before and after PHP while having an index.html in the root folder. Then I put in a small and simple index.php and got the bug reproduced. Resorted to using Limit CONNECT workaround. Would like to see this bug fixed ASAP. ------------------------------------------------------------------------ [2003-02-06 14:03:45] fearphage at hotmail dot com Im not sure how or why but apache sends a 200 (ok) back from requests for files that do not exist. I do not know how to rememedy this. ------------------------------------------------------------------------ [2003-01-22 05:14:24] karabass at mitino dot ptt dot ru It *is* severe because when I see in apache access_log a message like this: 24.153.155.146 - - [22/Jan/2003:01:25:48 +0300] "CONNECT maildelivery.somewhere:25 HTTP/1.0" 200 44623 "-" "-" it is threatening enough for me to put away what I was doing and start staring at my httpd.conf. And that only takes 3-4 hours to just find this bug-report and make myself comfortable about this new "PHP feature". ------------------------------------------------------------------------ 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
