Description: ------------ When decoding a message that contains a character entity (an ampersand for instance), the final value contains both the full expansion and the decoded value. What happens is that the default handler (XML_RPC_dh) receives the expanded entity '&' and the character handler (XML_RPC_cd) receives the character '&'. Both append the string to the accumulator. I think that I have solved this problem by removing the default handler from the equation entirely. I can't see how this handler would be needed - XML RPC is sufficiently simple that it doesn't need to understand <!DOCTYPE or any other special tags. Change the call to xml_set_default_handler: - xml_set_default_handler($parser, "XML_RPC_dh"); + xml_set_default_handler($parser, false); Reproduce code: --------------- #server - add the usual stuff as well function echo($params) { $ret = new XML_RPC_Value($params->getParam(0), 'string'); return new XML_RPC_Response($ret); } # client $params = array(new XML_RPC_Value("<&>", "string")); $msg = new XML_RPC_Message("echo", $params); $client = new XML_RPC_Client("/RPC2", "localhost", 8080); $response = $client->send($msg); print($response->value()); Expected result: ---------------- The value that comes out should be the same as the value that went in: "<&>". Actual result: -------------- The returned string should just contain the request parameter. Instead the value returned is "<<&&>>".

Hello, This bug seems to be fixed in CVS. Can you give it a try using the cvs files? pierre

Hi, I am still seeing the same problem with the latest files from CVS. It doesn't look like the code specific to the problem has changed between versions 1.11 and 1.21 of RPC.php. If I use a PHP server, the problem is compounded, since both ends exhibit the same problem. For example, for a simple 'echo' command, if I send the string 'hello&', I get a response of 'hello&&&&'. It is possible that the version of xmllib/libxml2 affects this, I have version 2.6.4 installed. Regards, Martin

Hi, I'm using the following regex cludge in the method 'parseResponse' (XML_RPC_Message object) ... RPC.inc line 738, after 'xml_parser_free($parser);': $data= $XML_RPC_xh[$parser]['st']; $data= ereg_replace("<<","<",$data); $data= ereg_replace(">>",">",$data); $data= ereg_replace("&&","&",$data); $data= ereg_replace('"','',$data); $XML_RPC_xh[$parser]['st']= $data; It seems to work for now... Cheers Amir

ps. The extra characters seem to appear during 'xml_parse' in the 'xml_set_character_data_handler function', 'XML_RPC_cd' It's definitely a bit complicated!

Fixed in CVS.