Wordfence Breaks site if Redirect 301 in .htaccess
-
Help me understand why an entire WordPress site is taken down by Wordfence if there happens to be either a Redirect 301 or RedirectMatch 301 within the default WordPress htaccess code?
For example, Redirect 301 /olddoc.pdf https://yoursite.com/newdoc.pdf works perfectly fine until the Wordfence plugin is fully activated. When Wordfence adds its code to the htaccess file the ENTIRE site breaks… wp-admin and all.
If I didn’t have access to the backend via command line and FTP access to change permissions and fix the htaccess file, this could be very troublesome.
As soon as I remove the Wordfence code, then the site will come back up.
Apparently WAF and Redirect 301 cannot co-exist. Why?
- The topic ‘Wordfence Breaks site if Redirect 301 in .htaccess’ is closed to new replies.