ID: 18371 Updated by: [EMAIL PROTECTED] Reported By: janus at area319 dot de -Status: Open +Status: Feedback Bug Type: CGI related Operating System: ALL PHP Version: 4.3.2 New Comment:
Not enough information was provided for us to be able to handle this bug. Please re-read the instructions at http://bugs.php.net/how-to-report.php If you can provide more information, feel free to add it to this bug and change the status back to "Open". Thank you for your interest in PHP. I do beleive you should not have any configuration for PHP in httpd.conf when you use --enable-discard-path? See http://www.php.net/manual/en/security.cgi-bin.php Case 4. If properly configured in this situation, you should not see the self parsing bug. If --enable-discard-path is not what you really want, use --enable-force-cgi-redirect with the configuration you provided a long time ago. Previous Comments: ------------------------------------------------------------------------ [2003-06-01 16:28:20] janus at area319 dot de Wow! Incredible, it's back again. Powered by 4.3.2-RELEASE this time. ------------------------------------------------------------------------ [2002-12-03 01:09:41] [EMAIL PROTECTED] This bug has been fixed in CVS. In case this was a PHP problem, snapshots of the sources are packaged every three hours; this change will be in the next snapshot. You can grab the snapshot at http://snaps.php.net/. In case this was a documentation problem, the fix will show up soon at http://www.php.net/manual/. In case this was a PHP.net website problem, the change will show up on the PHP.net site and on the mirror sites in short time. Thank you for the report, and for helping us make PHP better. don't use discard path. but really, fixed in cvs. ------------------------------------------------------------------------ [2002-11-29 10:06:07] janus at area319 dot de But the problem also exists with apache1... ------------------------------------------------------------------------ [2002-11-15 01:28:05] [EMAIL PROTECTED] Nobody here runs Apache2. Feel free to pitch in and provide a patch. ------------------------------------------------------------------------ [2002-11-15 01:26:00] janus at area319 dot de Wow... incredible... now i'm getting the same error with SSL too. That's really boring! The people need a safe way to run php... but there isn't any up-to-date solution that really works (especially apache2/cgi). It's hard to believe that php will run at any ISP, when there are so great problems with it. Apache2 is much better in managing resources and has more speed... so it will be the next step in webhosting-environments, please fix it soon. ------------------------------------------------------------------------ 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/18371 -- Edit this bug report at http://bugs.php.net/?id=18371&edit=1
