Description: ------------ Maybe XMLRPC2 should read POST data using php://input instead of GLOBALS['HTTP_RAW_POST_DATA'] ? We can read in the manual : """ always_populate_raw_post_data boolean Always populate the $HTTP_RAW_POST_DATA containing the raw POST data. Otherwise, the variable is populated only with unrecognized MIME type of the data. However, the preferred method for accessing the raw POST data is php://input. $HTTP_RAW_POST_DATA is not available with enctype="multipart/form-data". """ php://input seems to be the preferred way to read XMLRPC request content

Furthermore, because of a nasty bug, XML_RPC2 in its current state can't be used with PHP 5.2.2 on some platforms (bug mentions Ubuntu and Centos, I've personally experienced it on Debian Etch). http://bugs.php.net/bug.php?id=41293 Just one more reason to move to php://input.

I recall having run into some issues trying to use php://input, which was my first attempt. For the sake of documentation, I'll try to use php://input again. If it works, great. If it does not, at least I can point my finger at someone :-)

This bug has been fixed in SVN. If this was a documentation problem, the fix will appear on pear.php.net by the end of next Sunday (CET). If this was a problem with the pear.php.net website, the change should be live shortly. Otherwise, the fix will appear in the package's next release. Thank you for the report and for helping us make PEAR better. Corrected by commit version 308615. XML_RPC2_Server now accepts as option an XML_RPC2_Server_Input class. The default remains the usage of $GLOBALS['HTTP_RAW_POST_DATA'] via XML_RPC2_Server_Input_RawPostData. Users requiring php://input may pass input => 'XML_RPC2_Server_Input_PhpInput' to the server options array upon creation, to read input from php://input