Opting Out of Mod_Security
The following information is no longer valid. Newer versions of mod_security/Apache2 do not allow for user-level changes to mod_security filtering. Please contact support to have specific files excluded from filtering. We’re sorry for the inconvenience.
It is highly recommended that you do not enable “opt-out” for anything other than your content management system’s entry posting form.
Create or edit an .htaccess file within your content management system’s administrative directory, enter the following (this is an example for WordPress):
<Files post.php>
SecFilterInheritance Off
</Files>
Change post.php to whatever name your content management system’s posting page is, as mentioned, the above is for Wordpress, and you’d want to place it in your wp-admin directory.
This will turn off mod_security filtering so that you may post using the banned keywords, but will still prevent comments, referrers, and trackbacks on the blacklist from accessing your comments form.
You may also wish to do this for the file options-discussion.php, which contains the Wordpress blacklist, otherwise any word that matches our mod_security blacklist will cause your page to render a 406: Not Acceptable error.
Follow these examples for Movable Type and other content management systems, but instead of post.php, use the appropriate page and appropriate directory that matches your installation.
