ID: 35116
User updated by: [EMAIL PROTECTED]
Reported By: [EMAIL PROTECTED]
-Status: Open
+Status: Bogus
Bug Type: Strings related
Operating System: Linux
PHP Version: 4.4.1
New Comment:
Thinking about it again, I don't consider the change a BC break
anymore. Clearly PHP's implementation of Base64 was incorrect prior to
fixing #34214 and thus people like me, who passed input containing
whitespace to base64_decode(), were doing something wrong in first
place.
Still it was surprising to see an application stop working when
deploying a security release of PHP, but such is live I guess.
Previous Comments:
------------------------------------------------------------------------
[2005-11-05 20:04:18] [EMAIL PROTECTED]
I'm not questioning that a bug shouldn't be fixed. What I'm
questioning is if this should happen within minor releases *if* the fix
imposes a BC break.
------------------------------------------------------------------------
[2005-11-05 20:01:40] [EMAIL PROTECTED]
Why can't a bug be fixed?
------------------------------------------------------------------------
[2005-11-05 20:00:23] [EMAIL PROTECTED]
I understand that whitespaces are not supported in Base64, but still
the behaviour of base64_decode() should not change from 4.4.0 to 4.4.1.
------------------------------------------------------------------------
[2005-11-05 19:28:40] [EMAIL PROTECTED]
Description:
------------
While base64_decode works properly in PHP 4.4.0 and PHP 5, it fails in
PHP 4.4.1. I can reproduce this problem with vanilla sources of PHP
4.4.1 with the following ./configure line:
./configure --disable-all --with-mcrypt --enable-cli
I'm using Linux with glibc 2.3.5 and GCC 4.0.3.
Reproduce code:
---------------
<?php
echo base64_decode("Hello World");
Expected result:
----------------
ée£å¨®W
Actual result:
--------------
ée¡j+
------------------------------------------------------------------------
--
Edit this bug report at http://bugs.php.net/?id=35116&edit=1
