anchor.diff:  XRuleTime !1,2,3,4,5@08:00-17:00-0500 scaleThreat=1.5 enableBlockingMode
   ------------------------------------------------------------------------
   
  -For available actions, see `XRuleIpv4`
  +For available actions, see <<_xruleipv4>>
  
positive.code: XRulePath /admin scaleThreat=1.5 enableBlockingMode priority=1
  --------------------------------------------------------------
  
  For available actions, see `XRuleIpv4`
  
  === XRuleRequestContentType
  [cols=">h,<9"]
  |===============================================================================
  |Description|Add an extended request content type rule.
  |     Syntax|`XRuleRequestContentType`
  |    Default|None
  |    Context|Any
  |Cardinality|0..n
  
negative.code: * *SITE_NAME* - Selected site name
  * *LOCATION_PATH* - Selected location path
  
  === XRuleEventTag
  [cols=">h,<9"]
  |===============================================================================
  |Description|Add an extended EventTag rule.
  |     Syntax|`XRuleEventTag <tag1> <tag2> ... <tagN> <Action>`
  |    Default|None
  |    Context|Any
  |Cardinality|0..n
  |     Module|xrules
  |    Version|0.10
  |===============================================================================
  
  [NOTE]
  XRules, or extended rules, are rules that implement common operations,
  such as Access Control Lists (ACLs). These extended rules hide much of
  the complexities of normal rules so that these common operations are
  easier to use. For EventTags, priority is ignored.
  
  An XRuleEventTag directive is used to setup EventTag based rules. These rules
  will match (potentially multiple times) if an event is generated with one of
  the given tag values as a prefix.  For example, you may have tags such
  as "SQLi" which are added by any SQLi rules that match.
  
  Example:
  ----------------------------
  XRuleEventTag SQLi XSS block
  ----------------------------
  
  For available actions, see <<_xruleipv4>>
  
  === XRuleException
  [cols=">h,<9"]
  |===============================================================================
  |Description|Add an extended Exception rule, which allows combining multiple XRules.
  |     Syntax|`XRuleException <xrule1> <xrule2> ... <xruleN> <Action> [priority=N]`
  |    Default|None
  |    Context|Any
  |Cardinality|0..n
  |     Module|xrules
  |    Version|0.10
  |===============================================================================
  
  [NOTE]
  XRules, or extended rules, are rules that implement common operations,
  such as Access Control Lists (ACLs). These extended rules hide much of
  the complexities of normal rules so that these common operations are
  easier to use. Exception xrules are used to AND together multiple other xrule types.
  
  Typically to produce an exception, you need to AND together multiple XRules. For
  instance you may want to combine IPv4 with Path and EventTags to disable blocking.
  
  Each `xrule` is specified as a type prefix followed by a colon and the xrule
  expression. For example, `Ipv4:1.2.3.4/32` or `Path:/some-path`. Each `xrule`
  argument must resolve true for the action to be executed.
  
  Example: Disable blocking for IPs in net 1.2.3.0/24 using path /admin where SQLi is found.
  ----------------------------------------------------------------------------------
  XRuleException "Ipv4:1.2.3.0/24" "Path:/admin" "EventTag:SQLi" disableBlockingMode
  ----------------------------------------------------------------------------------
  
  For available actions, see <<_xruleipv4>>
  
  === XRuleGeo
  [cols=">h,<9"]
  |===============================================================================
  |Description|Add an extended geo rule.
  |     Syntax|`XRuleGeo <2-char-country> <Action> [priority=N]`
  |    Default|None
  |    Context|Any
  |Cardinality|0..n
  