Description: ------------ XML_RPC2_Server specifies a HTTP Content-length header. The length is calculated using strlen(). It mbstring.func_overload is used to overload the strlen() function, strlen() will return the number of characters in a string rather than the number of bytes. Since HTTP expects the number of bytes, multibyte characters inside an XML-RPC response will cause an incorrect Content-length header to be sent. This breaks various HTTP clients in weird and not-so-wonderful ways. When PHP supports unicode, strlen() will also report the number of characters rather than bytes unless a binary cast is used. The patch at: http://labs.silverorange.com/files/pear-patches/XML_RPC2-strlen-utf8-20080218.diff fixes the problem for both mbstring users and future versions of PHP. Test script: --------------- http://labs.silverorange.com/files/tests/XML_RPC2-utf8-strlen-test.phps Expected result: ---------------- Content-length header is: 19 (bytes) Actual result: -------------- Result with (mb_string.func_overload & 2) == 2 Content-length header is 15 (bytes)

Any update on this bug? There is a working patch attached to this report.

Thank you for your bug report. This issue has been fixed in the latest released version of the package, which you can download at http://pear.php.net/get/XML_RPC2