Changes between Initial Version and Version 1 of Ticket #36055, comment 16
- Timestamp:
- 03/04/2016 08:19:10 AM (10 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #36055, comment 16
initial v1 3 3 > 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). 4 4 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 fro what it is doing. The main reason behind it is to have an option do "really" disable/switch off/remove XML-RPC if a customer does not need it. This has different reasons like security, philosophy and architectural design (take the one you like most).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). 6 6 7 7 My suggestion was to filter the server_request: