Bug #16515 Updated: Files with execute-bit are always php-parsed - I cannot disable this!
ID: 16515 Updated by: [EMAIL PROTECTED] Reported By: [EMAIL PROTECTED] Status: Open Bug Type: Apache related Operating System: Linux 2.4.16 PHP Version: 4.1.2 New Comment: I have the same problem, with php 4.1.2 and apache 1.3.6 on Solaris. In some directories, php parses html files. In others, mod_include parses them. It seems that when I add any php configuration directives to apache in per-directory context, then php parses html files. I've tried setting xbithack to Off in php.ini and in apache.conf, but it does not help. Previous Comments: [2002-04-18 16:57:48] [EMAIL PROTECTED] I have the very same problem here regarding parsing of html files by the php module, if x-bit is set. apache 1.3.23 with php 4.1.2 as apache module and XBitHack off running on FreeBSD 4.5-STABLE. [2002-04-10 12:24:48] [EMAIL PROTECTED] I discussed the problem already with Zeev (@Zend) some weeks ago and he wrote: >I'm not sure what to tell you... It's definitely not a >known bug in PHP, I've never heard it being reported >before ever. So, please can anybody check this behaviour/bug? Please tell me if I can help somehow or test some config-params on my system. Thank you very much. [2002-04-10 09:05:44] [EMAIL PROTECTED] Reopening on user request. [2002-04-09 11:32:19] [EMAIL PROTECTED] The bug system is not the appropriate forum for asking support questions. For a list of a range of more appropriate places to ask for help using PHP, please visit http://www.php.net/support.php I'm sure this is a configuration issue; ask support on the appropriate mailinglist. [2002-04-09 11:06:13] [EMAIL PROTECTED] Hello! After updating 4.04pl1 to 4.1.1, I encountered the following problem: All .htm and .html-files with the execute-bit set, are PHP parsed! I disabled the xbithack-feature of Apache and phpinfo() tells me correctly, that xbithack is disabled (ok, the xbithack-feature will normally enable SSI-parsing in Apache, but I wanted to be sure that everything is disabled). Then I updated to 4.1.2, but the files are still PHP-parsed. I updated Apache from 1.3.19 to 1.3.22, but the files are still PHP-parsed. I tried everything, but my xbit-files are still PHP-parsed - and I don't want this (sigh!). Is this a bug or a hidden feature? Is there something I can do? Can anybody reproduce the problem? (just set chmod 755 for a .html-file, put some php-code in it and look if it is being PHP-parsed) Help! Thanks for your support. Greetings ... tobias wiersch from germany -- Edit this bug report at http://bugs.php.net/?id=16515&edit=1
Bug #16515 Updated: Files with execute-bit are always php-parsed - I cannot disable this!
ID: 16515 Updated by: [EMAIL PROTECTED] Reported By: [EMAIL PROTECTED] Status: Open Bug Type: Apache related Operating System: Linux 2.4.16 PHP Version: 4.1.2 New Comment: I have the very same problem here regarding parsing of html files by the php module, if x-bit is set. apache 1.3.23 with php 4.1.2 as apache module and XBitHack off running on FreeBSD 4.5-STABLE. Previous Comments: [2002-04-10 12:24:48] [EMAIL PROTECTED] I discussed the problem already with Zeev (@Zend) some weeks ago and he wrote: >I'm not sure what to tell you... It's definitely not a >known bug in PHP, I've never heard it being reported >before ever. So, please can anybody check this behaviour/bug? Please tell me if I can help somehow or test some config-params on my system. Thank you very much. [2002-04-10 09:05:44] [EMAIL PROTECTED] Reopening on user request. [2002-04-09 11:32:19] [EMAIL PROTECTED] The bug system is not the appropriate forum for asking support questions. For a list of a range of more appropriate places to ask for help using PHP, please visit http://www.php.net/support.php I'm sure this is a configuration issue; ask support on the appropriate mailinglist. [2002-04-09 11:06:13] [EMAIL PROTECTED] Hello! After updating 4.04pl1 to 4.1.1, I encountered the following problem: All .htm and .html-files with the execute-bit set, are PHP parsed! I disabled the xbithack-feature of Apache and phpinfo() tells me correctly, that xbithack is disabled (ok, the xbithack-feature will normally enable SSI-parsing in Apache, but I wanted to be sure that everything is disabled). Then I updated to 4.1.2, but the files are still PHP-parsed. I updated Apache from 1.3.19 to 1.3.22, but the files are still PHP-parsed. I tried everything, but my xbit-files are still PHP-parsed - and I don't want this (sigh!). Is this a bug or a hidden feature? Is there something I can do? Can anybody reproduce the problem? (just set chmod 755 for a .html-file, put some php-code in it and look if it is being PHP-parsed) Help! Thanks for your support. Greetings ... tobias wiersch from germany -- Edit this bug report at http://bugs.php.net/?id=16515&edit=1
Bug #16515 Updated: Files with execute-bit are always php-parsed - I cannot disable this!
ID: 16515 Updated by: [EMAIL PROTECTED] Reported By: [EMAIL PROTECTED] Status: Open Bug Type: Apache related Operating System: Linux 2.4.16 PHP Version: 4.1.2 New Comment: I discussed the problem already with Zeev (@Zend) some weeks ago and he wrote: >I'm not sure what to tell you... It's definitely not a >known bug in PHP, I've never heard it being reported >before ever. So, please can anybody check this behaviour/bug? Please tell me if I can help somehow or test some config-params on my system. Thank you very much. Previous Comments: [2002-04-10 09:05:44] [EMAIL PROTECTED] Reopening on user request. [2002-04-09 11:32:19] [EMAIL PROTECTED] The bug system is not the appropriate forum for asking support questions. For a list of a range of more appropriate places to ask for help using PHP, please visit http://www.php.net/support.php I'm sure this is a configuration issue; ask support on the appropriate mailinglist. [2002-04-09 11:06:13] [EMAIL PROTECTED] Hello! After updating 4.04pl1 to 4.1.1, I encountered the following problem: All .htm and .html-files with the execute-bit set, are PHP parsed! I disabled the xbithack-feature of Apache and phpinfo() tells me correctly, that xbithack is disabled (ok, the xbithack-feature will normally enable SSI-parsing in Apache, but I wanted to be sure that everything is disabled). Then I updated to 4.1.2, but the files are still PHP-parsed. I updated Apache from 1.3.19 to 1.3.22, but the files are still PHP-parsed. I tried everything, but my xbit-files are still PHP-parsed - and I don't want this (sigh!). Is this a bug or a hidden feature? Is there something I can do? Can anybody reproduce the problem? (just set chmod 755 for a .html-file, put some php-code in it and look if it is being PHP-parsed) Help! Thanks for your support. Greetings ... tobias wiersch from germany -- Edit this bug report at http://bugs.php.net/?id=16515&edit=1
Bug #16515 Updated: Files with execute-bit are always php-parsed - I cannot disable this!
ID: 16515 Updated by: [EMAIL PROTECTED] Reported By: [EMAIL PROTECTED] -Status: Bogus +Status: Open Bug Type: Apache related Operating System: Linux 2.4.16 PHP Version: 4.1.2 New Comment: Reopening on user request. Previous Comments: [2002-04-09 11:32:19] [EMAIL PROTECTED] The bug system is not the appropriate forum for asking support questions. For a list of a range of more appropriate places to ask for help using PHP, please visit http://www.php.net/support.php I'm sure this is a configuration issue; ask support on the appropriate mailinglist. [2002-04-09 11:06:13] [EMAIL PROTECTED] Hello! After updating 4.04pl1 to 4.1.1, I encountered the following problem: All .htm and .html-files with the execute-bit set, are PHP parsed! I disabled the xbithack-feature of Apache and phpinfo() tells me correctly, that xbithack is disabled (ok, the xbithack-feature will normally enable SSI-parsing in Apache, but I wanted to be sure that everything is disabled). Then I updated to 4.1.2, but the files are still PHP-parsed. I updated Apache from 1.3.19 to 1.3.22, but the files are still PHP-parsed. I tried everything, but my xbit-files are still PHP-parsed - and I don't want this (sigh!). Is this a bug or a hidden feature? Is there something I can do? Can anybody reproduce the problem? (just set chmod 755 for a .html-file, put some php-code in it and look if it is being PHP-parsed) Help! Thanks for your support. Greetings ... tobias wiersch from germany -- Edit this bug report at http://bugs.php.net/?id=16515&edit=1
