ID: 17249 Updated by: [EMAIL PROTECTED] Reported By: [EMAIL PROTECTED] Status: Bogus Bug Type: Scripting Engine problem Operating System: Solaris 8 PHP Version: 4.2.1 New Comment:
I disagree. A one-line test case (as provided within the documentation) that behaves differently from php4.2.0 and php4.2.1 would indicate a bug (or discrepancy) has snuck into the code during the last release. The fact it can be altered depending on whitespace within the file and whether running through an SSL enabled host is merely additional information I have provided to try to aide it's resolution. I am not requesting support. I am reporting that php's behaviour has been changed, in what appears to me to be a buggish fashion. Previous Comments: ------------------------------------------------------------------------ [2002-05-15 14:37:47] [EMAIL PROTECTED] Sorry, but the bug system is not the appropriate forum for asking support questions. Your problem does not imply a bug in PHP itself. For a list of more appropriate places to ask for help using PHP, please visit http://www.php.net/support.php Thank you for your interest in PHP. ------------------------------------------------------------------------ [2002-05-15 09:50:26] [EMAIL PROTECTED] Just installed php 4.2.1 (over previous 4.2.0 installation). Did not make any changes to the apache conf or php.ini config (my php.ini is identical to php.ini-recommended except for expose_php = Off, though I've confirmed this happens with both Off and On). If I try to view .php pages under SSL, they all work except for a specific file containing only: --- begin file --- <? phpinfo(); ?> --- end file --- If, however, the phpinfo() call is within a larger script it works fine. For example, these both work: --- begin file --- <?php phpinfo(); ?> --- end file --- --- begin file --- <? phpinfo(); ?> --- end file --- The error I receive is a browser popup: the URL (etc) has MIME type application/x-httpd-php. Saving the file shows that it contains the php source. This problem does not occur within the same set of files under a non-SSL enabled apache virtual host. ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=17249&edit=1
