| 1 | | It's common for servers and clients to exhibit quirks with respect to XMLRPC, and it's loosely specified enough that I don't know if you can even find consensus for how it should 100% behave. I would argue that the status quo trumps most other considerations and that changes to XMLRPC behavior in WordPress should only be made to achieve specific, tangible goals. I tend to think that [35509] should be reverted and that additional fixes to XMLRPC support should be considered skeptically, |
| 2 | | as they might cause similarly unexpected side-effects. |
| | 1 | It's common for servers and clients to exhibit quirks with respect to XMLRPC, and it's loosely specified enough that I don't know if you can even find consensus for how it should 100% behave. I would argue that the status quo trumps most other considerations and that changes to XMLRPC behavior in WordPress should only be made to achieve specific, tangible goals. I tend to think that [35509] should be reverted and that additional fixes to XMLRPC support should be considered skeptically, as they might cause similarly unexpected side-effects. |