Viewing 4 replies - 1 through 4 (of 4 total)
  • Probably not. If Wordfence and your website function normally, then just leave it where it lives. The order of things in .htaccess is usually not a big deal, though there are a few things that can be considered. I’m always curious about optimizations for .htaccess since it’s rather primitive (entire thing is read on each and every request). I found lots of tips using Google, but nothing that seemed critical. Main thing was to keep it as small as possible if any hosting resource issues. When my main site had fairly low traffic I didn’t worry about it, but I now have a moderatly high traffic site on expensive hosting, so I constantly optimize for bandwidth, with one ongoing project being keeping .htaccess tight. I’d probably be best just eliminating .htaccess, but it’s so convenient, as well as plugins sometimes wanting it. MTN

    @hubmacfan,

    That’s exactly where the optimization procedure writes it in case of the “Apache + mod_php” configuration; right below the “# BEGIN WordPress … # END WordPress” block.

    Thread Starter hubmacfan

    (@hubmacfan)

    Thanks.

    Hi @hubmacfan
    Just wanted to confirm that this is the correct place for Wordfence firewall setup rules in .htaccess file.

    Thanks.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘WAF position in .htaccess’ is closed to new replies.