Update to SecRuleRemove directives to reflect what it's currently missing for ModSecv3

Victor Hora
2017-06-27 15:08:48 -04:00
parent 123bcec531
commit 97f80b1e83

@@ -1353,7 +1353,9 @@ This directive supports multiple parameters, each of which can be a rule ID or a
'''Scope:''' Any '''Scope:''' Any
'''Version:''' 2.0.0 '''Version:''' 2.0.0-2.9.x
'''Supported on libModSecurity:''' TBI
Normally, you would use SecRuleRemoveById to remove rules, but that requires the rules to have IDs defined. If they dont, then you can remove them with SecRuleRemoveByMsg, which matches a regular expression against rule messages. Normally, you would use SecRuleRemoveById to remove rules, but that requires the rules to have IDs defined. If they dont, then you can remove them with SecRuleRemoveByMsg, which matches a regular expression against rule messages.
@@ -1368,7 +1370,9 @@ Normally, you would use SecRuleRemoveById to remove rules, but that requires the
'''Scope:''' Any '''Scope:''' Any
'''Version:''' 2.6 '''Version:''' 2.6-2.9.x
'''Supported on libModSecurity:''' TBI
Normally, you would use SecRuleRemoveById to remove rules, but that requires the rules to have IDs defined. If they dont, then you can remove them with SecRuleRemoveByTag, which matches a regular expression against rule tag data. This is useful if you want to disable entire groups of rules based on tag data. Example tags used in the OWASP ModSecurity CRS include: Normally, you would use SecRuleRemoveById to remove rules, but that requires the rules to have IDs defined. If they dont, then you can remove them with SecRuleRemoveByTag, which matches a regular expression against rule tag data. This is useful if you want to disable entire groups of rules based on tag data. Example tags used in the OWASP ModSecurity CRS include:
*AUTOMATION/MALICIOUS *AUTOMATION/MALICIOUS