Edit report at http://bugs.php.net/bug.php?id=53493&edit=1

 ID:                 53493
 Updated by:         ka...@php.net
 Reported by:        martin at kopta dot eu
 Summary:            xmlrpc_decode should not be sensitive to leading
                     whitespace
-Status:             Assigned
+Status:             Closed
 Type:               Feature/Change Request
 Package:            XMLRPC-EPI related
 Operating System:   Ubuntu 10.04 LTS Server
 PHP Version:        5.3.3
 Assigned To:        kalle
 Block user comment: N
 Private report:     N

 New Comment:

This bug has been fixed in SVN.

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/.
 
Thank you for the report, and for helping us make PHP better.




Previous Comments:
------------------------------------------------------------------------
[2010-12-13 10:52:07] ka...@php.net

Automatic comment from SVN on behalf of kalle
Revision: http://svn.php.net/viewvc/?view=revision&revision=306339
Log: Fixed bug #53493 (xmlrpc_decode should not be sensitive to leading
whitespace)

------------------------------------------------------------------------
[2010-12-07 15:51:19] martin at kopta dot eu

Description:
------------
My version of PHP is PHP 5.3.2-1ubuntu4.5. I did some upgrades a few
hours/days back and I noticed that my XMLRPC responses are decoded as
NULL by the xmlrpc_decode() function. As I experimented around this
function, I found that it is sensitive to leading whitespace. When
leading whitespace is present (a newline in my case), xmlrpc_decode()
returns NULL. When ltrim() is used on the string before passed into
xmlrpc_decode(), output is alright. Presence of whitespace present at
the end of the string does not have any effect.



Summary: xmlrpc_decode() is sensitive to leading whitespace and it
should not be.



---

>From manual page: http://www.php.net/function.xmlrpc-decode#Description

---





------------------------------------------------------------------------



-- 
Edit this bug report at http://bugs.php.net/bug.php?id=53493&edit=1

Reply via email to