ID: 32706
User updated by: dwd at polyserve dot com
Reported By: dwd at polyserve dot com
Status: Bogus
Bug Type: Unknown/Other Function
Operating System: SuSE Linux Enterprise Server 9
PHP Version: 4.3.9
New Comment:
Sorry for the botched description.
Issue 1: I cannot upgrade PHP. We are not allowed to upgrade packages
outside of std. SuSE releases, so 4.3.4 is what I have to work with,
full stop. (Note: Your stupid bug interface would not let me specify an
earlier release than 4.3.9, so I had to lie.)
Issue 2: Yes, I know that PHP is server side. Although I botched the
description, what I meant to say is that the code isn't being parsed
correctly from Apache, and parts of the code (after the <> op) are
displayed as content in my browser. Changing to != worked, but it's
puzzling. N.B. This code has been in production for years now, on
earlier versions of PHP, and we only noticed this now after migrating
from RHEL3 to SLES9 with a later version (4.3.4) of PHP.
Issue 3: Try reproducing on 4.3.4 using a SuSE Linux Enterprise 9
system with Apache2 before you tell me again that it's not
reproducible. I can reproduce at will here.
Previous Comments:
------------------------------------------------------------------------
[2005-04-14 19:48:53] [EMAIL PROTECTED]
1) 4.3.9 is too old. Upgrade first.
2) Can't reproduce it.
3) What browser are you talking about? PHP is a server side language
and it's not supposed to be parsed by a "browser". If you see PHP code
in your browser, your server is just misconfigured.
------------------------------------------------------------------------
[2005-04-14 19:39:09] dwd at polyserve dot com
Description:
------------
Our index.php has some code at the top that uses the '<>' operator:
<?
...
if ($email <> "")
{
...
}
?>
This code was not being parsed correctly, and the web browser would
spit out the text following the <> operator as if it was content.
Changing the <> to != fixed the problem, but I'd like to know why, as
<> should be equivalent to != according to the documentation.
------------------------------------------------------------------------
--
Edit this bug report at http://bugs.php.net/?id=32706&edit=1
