|
php.net | support | documentation | report a bug | advanced search | search howto | statistics | random bug | login |
PatchesPull RequestsHistoryAllCommentsChangesGit/SVN commits
[2011-02-21 21:24 UTC] jani@php.net
-Package: Feature/Change Request
+Package: XMLRPC-EPI related
[2021-04-13 13:53 UTC] cmb@php.net
-Status: Open
+Status: Wont fix
-Assigned To:
+Assigned To: cmb
[2021-04-13 13:53 UTC] cmb@php.net
|
|||||||||||||||||||||||||||||||||
Copyright © 2001-2025 The PHP GroupAll rights reserved. |
Last updated: Tue Nov 04 17:00:01 2025 UTC |
Description: ------------ When registering a php user function to be exposed as xmlrpc method, the resulting xml will be that of an xmlrpc fault response iff the return value of the user function is an array containing a key 'faultCode'. When the result value contains other array members beside faultCode and faultString, or the values of those two members are not an int and a string, the generated xml will not be conforming to the xmlrpc spec, which states: "A <fault> struct may not contain members other than those specified". I know that this situation is the fault of the coder, but, imho, the lib should do its reasonable best to always work within the spec... Reproduce code: --------------- $x = xmlrpc_server_create(); xmlrpc_server_register_method($x, 'pluto', 'pippo'); $out = xmlrpc_server_call_method($x, xmlrpc_encode_request('pluto', array()), null); echo htmlspecialchars($out); function pippo($meth, $params, $extras) { return array('faultCode' => 1, 'faultString' => array(1, 2, 3, 4), 'hello world'); } Actual result: -------------- <?xml version="1.0" encoding="iso-8859-1"?> <methodResponse> <params> <value> <struct> <member> <name>faultCode</name> <value> <int>1</int> </value> </member> <member> <name>faultString</name> <value> <array> <data> <value> <int>1</int> </value> <value> <int>2</int> </value> <value> <int>3</int> </value> <value> <int>4</int> </value> </data> </array> </value> </member> <member> <name/> <value> <string>hello world</string> </value> </member> </struct> </value> </params> </methodResponse>