WordPress.org

Make WordPress Core

Changes between Version 1 and Version 2 of Ticket #36055, comment 16


Ignore:
Timestamp:
03/04/2016 08:20:44 AM (3 years ago)
Author:
mensmaximus
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #36055, comment 16

    v1 v2  
    33> We can't change the behaviour of that filter now to also block pingbacks. What we could do instead is add a new way to completely remove XML-RPC all together, but I'm not sure of the intentions behind that (as this ticket doesn't have any context as to where it came from).
    44
    5 The request came originally from me. I contacted @markoheijnen on slack due to the nature of the issue I discovered. As you already said in an other comment this filter is named badly and users get a bad idea from what it is doing. The main reason behind it is to have an option do "really" disable/switch off/remove XML-RPC if a user does not need it. This has different reasons like security, philosophy and architectural design (take the one you like most).
     5The request came originally from me. I contacted @markoheijnen on slack due to the nature of the issue I discovered. As you already said in an other comment this filter is named badly and users get a bad idea from what it is doing. The main reason behind it is to have an option to "really" disable/switch off/remove XML-RPC if a user does not need it. This has different reasons like security, philosophy and architectural design (take the one you like most).
    66
    77My suggestion was to filter the server_request: