From 10798be4ce4c4222820b8f836c9c25213fda5219 Mon Sep 17 00:00:00 2001 From: Chaim Sanders Date: Fri, 26 Aug 2016 18:32:39 -0400 Subject: [PATCH] Updated Reference Manual (mediawiki) --- Reference-Manual.mediawiki | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/Reference-Manual.mediawiki b/Reference-Manual.mediawiki index 61cdb9c..f455487 100644 --- a/Reference-Manual.mediawiki +++ b/Reference-Manual.mediawiki @@ -4045,6 +4045,15 @@ SecRule REQUEST_HEADERS:User-Agent "@strmatch WebZIP" "id:177" ; Note : Starting on ModSecurity v2.6.0 this operator supports a snort/suricata content style. ie: "@strmatch A|42|C|44|F". +== unconditionalMatch == +'''Description:''' Will force the rule to always return true. This is similar to SecAction however all actions that occur as a result of a rule matching will fire such as the setting of MATCHED_VAR. This can also be part a chained rule. + +'''Example:''' +
+SecRule REMOTE_ADDR "@unconditionalMatch" "id:1000,phase:1,pass,nolog,t:hexEncode,setvar:TX.ip_hash=%{MATCHED_VAR}"
+
+ + == validateByteRange == '''Description:''' Validates that the byte values used in input fall into the range specified by the operator parameter. This operator matches on an input value that contains bytes that are not in the specified range.