![]() By placing directive inside the # BEGIN WordPress / # END WordPress block then it will likely get overwritten when WordPress updates.These URLs probably don't map to real files/directories, so again it would never match. By placing this directive after the front-controller, it will only be seen for URL requests that map to physical files or directories.So, this RewriteRule would never match anything in this context. htaccess files, the URL-path that the RewriteRule pattern matches against never starts with a slash. ![]() ![]() As it stands, it will not do anything, but also has several "errors": The WordPress 404 eats up system memory and I'd like a more elegant and efficient way to handle these URLs. It keeps going to a the WordPress 404 page. I tried to make the end part of the file ( ?gurkha) to go to fail.php but it doesn't seem to work. How can I change those URL to 410 Gone? I'd like to redirect them to a page I've made (fail.php) that issues a 410 header. I am seeing a lot of requests like those below even after I've cleaned up my server: /cobwebbing-gurkha1486mskh27556/64b75843rl69s2/Į/countercheck-gurkha1486mskh22793/n4a670a2h43m/Į/countercheck-gurkha1486mskh19573/36c9on2137rs/ htaccess file was changed to wildcard redirect (spam).
0 Comments
Leave a Reply. |