From 97f80b1e835bd3cd27bdfe250845242b0906681f Mon Sep 17 00:00:00 2001 From: Victor Hora Date: Tue, 27 Jun 2017 15:08:48 -0400 Subject: [PATCH] Update to SecRuleRemove directives to reflect what it's currently missing for ModSecv3 --- Reference-Manual.mediawiki | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/Reference-Manual.mediawiki b/Reference-Manual.mediawiki index ee305fd..c56f5fd 100644 --- a/Reference-Manual.mediawiki +++ b/Reference-Manual.mediawiki @@ -1353,7 +1353,9 @@ This directive supports multiple parameters, each of which can be a rule ID or a '''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 don’t, 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 -'''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 don’t, 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