O optize Well-Known Member Mar 8, 2012 #1 Mar 8, 2012 #1 I have a simple mod_sec rule to block spam.html: SecRule SCRIPT_BASENAME "spam\.html" "t:none,deny" This works fine in Apache, however it doesn't trigger on Litespeed. Is this a known issue?
I have a simple mod_sec rule to block spam.html: SecRule SCRIPT_BASENAME "spam\.html" "t:none,deny" This works fine in Apache, however it doesn't trigger on Litespeed. Is this a known issue?
W webizen Well-Known Member Mar 8, 2012 #2 Mar 8, 2012 #2 litespeed skips modsec rules for static file like *.html as it would not cause any real issue. so it is by design not an overlook or bug.
litespeed skips modsec rules for static file like *.html as it would not cause any real issue. so it is by design not an overlook or bug.
O optize Well-Known Member Mar 8, 2012 #3 Mar 8, 2012 #3 webizen said: litespeed skips modsec rules for static file like *.html as it would not cause any real issue. so it is by design not an overlook or bug. Click to expand... Is there a way to turn it on? I need mod_sec to work on all file types.
webizen said: litespeed skips modsec rules for static file like *.html as it would not cause any real issue. so it is by design not an overlook or bug. Click to expand... Is there a way to turn it on? I need mod_sec to work on all file types.
W webizen Well-Known Member Mar 9, 2012 #4 Mar 9, 2012 #4 use workaround like followings: <Files ~ "spam.html"> Order allow,deny Deny from all Satisfy All </Files> <FilesMatch "\.php"> Order allow,deny Deny from all Satisfy All </FilesMatch> Click to expand...
use workaround like followings: <Files ~ "spam.html"> Order allow,deny Deny from all Satisfy All </Files> <FilesMatch "\.php"> Order allow,deny Deny from all Satisfy All </FilesMatch> Click to expand...