Facebook
TwitterThis is not optimal?
support.plesk.com
Can this be done:
1) diable/block xmlrpc so you are guaranteed to NOT let it cause a problem for server or WP install.
2) don't log all the bots, etc who try to access it.
Meaning, IF I KNOW it can't be used or create a problem, I don't want to know all bad guys trying to access it?
NOTE: My WP sites use these settings (as I believe they provide the fastest performance):
- using FPM
- under nginx settings, ALL 4 checkboxes are checked (proxy mode, smart static files processing, serve static files by nginx, nginx caching)
I guess ultimately, I'm trying to rid my log files of all the bots that hit files that I can "guarantee" will NOT be a problem.
your thoughts?
PS. Obviously, log files are important and can show trouble for when bad things happen... that is a given. BUT can't the xmlrpc file just be completed removed, not logged, etc.
thanks
How to disable XML-RPC for a WordPress instance hosted in Plesk?
Applicable to: Plesk for Linux Question How to disable XML-RPC for a WordPress instance hosted in Plesk? Answer Using a WordPress Security feature This security measure turns off XML-RPC pingb...
Can this be done:
1) diable/block xmlrpc so you are guaranteed to NOT let it cause a problem for server or WP install.
2) don't log all the bots, etc who try to access it.
Meaning, IF I KNOW it can't be used or create a problem, I don't want to know all bad guys trying to access it?
NOTE: My WP sites use these settings (as I believe they provide the fastest performance):
- using FPM
- under nginx settings, ALL 4 checkboxes are checked (proxy mode, smart static files processing, serve static files by nginx, nginx caching)
I guess ultimately, I'm trying to rid my log files of all the bots that hit files that I can "guarantee" will NOT be a problem.
your thoughts?
PS. Obviously, log files are important and can show trouble for when bad things happen... that is a given. BUT can't the xmlrpc file just be completed removed, not logged, etc.
thanks