Defending against WordPress xmlrpc attacks
Hi I have my own sites as well as a lot of my clients' sites on inMotion and I'd like your opinion. I have seen .htaccess rules protecting against xmlrpc attacks using... Redirect 301 /xmlrpc.php http://127.0.0.1 This reflects attacks back to the offender. I've also seen... Order allow,deny Deny from all Which will just plain deny access to the file. Does inMotion have a preference? Is one easier on cpu bandwidth than the other? Thanks!