Differences

This shows you the differences between two versions of the page.

--- litespeed_wiki:config:waf:disable-waf-in-htaccess [2018/12/10 16:45]
Jackson Zhang created
+++ litespeed_wiki:config:waf:disable-waf-in-htaccess [2019/12/25 12:56] (current)
qtwrk
@@ Line 1: / Line 1: @@
-====== How to disable ModSecurity for a single domain in .htaccess? ======
+====== How to Disable ModSecurity for a Single Domain in .htaccess ======
-ModSecurity is normally enabled on server level and applied to all domains on the shared hosting server. In some circumstance, some rule/rules might cause a certain application site-breaking and you might want to disable ModSecurity for that domain in .htaccess.
+ModSecurity is normally enabled at the server level and applied to all domains on the shared hosting server. In some circumstances, particular rules might cause an application to break the site, and you might want to disable ModSecurity for that domain in the site's ''.htaccess'' file.
-As far as "AllowOverride" permitted, you can place the following directives to .htaccess:
+As long as **AllowOverride** is permitted, you can place the following directives in ''.htaccess''.
 To disable ModSecurity for that virtual host:
   <IfModule mod_security.c>
      SecRuleEngine Off
@@ Line 11: / Line 12: @@
   </IfModule>
-or to disable a certain rule for that virtual host:
+To disable a particular rule for that virtual host:
   <IfModule mod_security.c>
@@ Line 17: / Line 18: @@
   </IfModule>
+**Please Note**: The following old syntax directives are not supported at more since LSWS 5.3RC1. Please only use the new syntax directives as shown above. If you still have clients using the following old syntax on latest LSWS version, you can write a script to scan and update .htaccess.
-The following old syntax directives are not supported and please ensure to use the above new syntax directives.
   <IfModule mod_security.c>