#45915 [Opn]: xmlrpc_encode_request does not encode numeric keys properly

ID: 45915 User updated by: matt at waggoner dot com Reported By: matt at waggoner dot com Status: Open -Bug Type: Feature/Change Request +Bug Type: XMLRPC-EPI related Operating System: * PHP Version: 5.2.6 New Comment: Any word on this? I wonder if this one's getting ignored because it doesn't show up in the bug search. Previous Comments: ------------------------------------------------------------------------ [2008-08-25 21:26:08] matt at waggoner dot com Description: ------------ This issue has been marked as bogus or wontfix before, but I believe this is a bad idea and that this issue should be fixed. Bug #21949 ends with this comment: "Not a bug, XML-RPC is ambigous as to the value that the <name> field can contain. However, all indications point to it being a string value, in XML this represents a value that is non-numeric." This is false; XML's string type is not restricted to "non-numeric" values. http://www.w3.org/TR/xmlschema-2/#string says that a string's value space is "the set of finite-length sequences of characters (as defined in [XML 1.0 (Second Edition)]) that match the Char production". The "Char production" is the following grammar: char ::= #x9 | #xA | #xD | [#x20-#xD7FF] | [#xE000-#xFFFD] | [#x10000-#x10FFFF] The characters 0-9 are within the [#x20-#xD7FF] range, ergo the string XML datatype can validly contain a set of only numeric characters such as "123", which eliminates that objection. The XML-RPC spec does indeed not specify what value a <name> element may contain, but it seems fairly useless to simply drop numeric keys; a string is a string regardless of whether it contains letters or not. Re bug #37746: "It has been this way for a long time" is not a valid reason to avoid fixing this (see any number of longstanding bugs in PHP's history); "this might break existing code" is also not a valid reason (see any number of backward-incompatible changes in PHP's history). Please fix this bug. Reproduce code: --------------- See bugs #21949 and #37746. ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=45915&edit=1