anchor.diff:    * *enableResponseBodyInspection* - Enable response body inspection for this transaction.
     * *disableResponseBodyInspection* - Disable response body inspection for this transaction.
   
  +
  +==== Directives
  +
  +[[directive.XRuleEventTag]]
  +===== XRuleEventTag
  +[cols=">h,<9"]
  +|===============================================================================
  +|Description|Add an extended EventTag rule.
  +|		Type|Directive
  +|     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
  +----
  +
  +[[directive.XRuleException]]
  +===== XRuleException
  +[cols=">h,<9"]
  +|===============================================================================
  +|Description|Add an extended Exception rule, which allows combining multiple XRules.
  +|		Type|Directive
  +|     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
  +----
  +
  +[[directive.XRuleGenerateEvent]]
  +===== XRuleGenerateEvent
  +[cols=">h,<9"]
  +|===============================================================================
  +|Description|Controls if log events are generated by matching XRules.
  +|		Type|Directive
  +|     Syntax|`XRuleGenerateEvent On \| Off`
  +|    Default|Off
  +|    Context|Any
  +|Cardinality|0..1
  +|     Module|xrules
  +|    Version|0.10
  +|===============================================================================
  +
  +If set to `On`, then XRules that match will produce an event. For example, an XRuleIpv4 would produce an event similar to the following regular rule actions:
  +
  +.XRuleIpv4 1.2.3.4/32 Block
  +----
  +Rule REMOTE_ADDR @ipmatch 1.2.3.4/32 id:xrule/ipv4 tag:xrule/ipv4 event "msg:Ipv4 1.2.3.4/32 matched: Block"
  +----
  +
  +[[directive.XRuleGeo]]
  +===== XRuleGeo
  +[cols=">h,<9"]
  +|===============================================================================
  +|Description|Add an extended geo rule.
  +|		Type|Directive
  +|     Syntax|`XRuleGeo <2-char-country> <Action> [priority=N]`
  +|    Default|None
  +|    Context|Any
  +|Cardinality|0..n
  +|     Module|xrules
  +|    Version|0.8
  +|===============================================================================
  +
  +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. The priority allows conflicts to be resolved - higher priority (lower numerical value) rules will override lower priority rules.
  +
  +An XRuleGeo is used to setup Geo (country) based rules.
  +
  +.Example:
  +----
  +XRuleGeo US scaleThreat=0.8 priority=1
  +----
  +
  +[[directive.XRuleIpv4]]
  +===== XRuleIpv4
  +[cols=">h,<9"]
  +|===============================================================================
  +|Description|Add an extended IPv4 rule.
  +|		Type|Directive
  +|     Syntax|`XRuleIpv4 <cidr4> <Action> [priority=N]`
  +|    Default|None
  +|    Context|Any
  +|Cardinality|0..n
  +|     Module|xrules
  +|    Version|0.8
  +|===============================================================================
  +
  +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. The priority allows conflicts to be resolved - higher priority (lower numerical value) rules will override lower priority rules.
  +
  +An XRuleIpv4 is used to setup IPv4 based rules.
  +
  +Example:
  +----
  +XRuleIpv4 192.168.0.0/16 block priority=1
  +----
  +
   [[directive.XRuleIpv6]]
   ===== XRuleIpv6
   [cols=">h,<9"]
  
positive.code: XRuleRequestContentType application/x-www-form-urlencoded enableRequestBodyInspection
  ----
  
  For available actions, see <<directive.XRuleIpv4,XRuleIpv4>>.
  
  [[directive.XRuleResponseContentType]]
  ===== XRuleResponseContentType
  [cols=">h,<9"]
  
negative.code: ----
  XRuleResponseContentType image/png disableResponseBodyInspection
  ----
  
  [[directive.XRuleTime]]
  ===== XRuleTime
  