SecRuleUpdateTargetById in 3.0.4

Hi everyone,

I attempted an upgrade to 3.0.4 today from 3.0.3. Unfortunately I can't get
over a hurdle.

I have an existing rule:

```
# Rule 930110 matches "..\u003e" in body (HTML escaped JSON value "..<")
# Replacing REQUEST_BODY with ARGS_NAMES|ARGS fixes the issue as the rule
see
# the value after Unicode decoding '\u003e' => '>'.
SecRuleUpdateTargetById 930110 "!REQUEST_BODY"
SecRuleUpdateTargetById 930110 ARGS_NAMES,ARGS
```

Due to modsec issue https://github.com/SpiderLabs/ModSecurity/issues/2251
it seems i'm using the 'non-regex' form of the rule that's fixed in master
but not yet released.

First I tried a patch, which failed to apply (any advice on how to patch
this from the 3.0.4 tag would be appreciated) with this in my build process:

```
curl -fSL
https://github.com/SpiderLabs/ModSecurity/commit/1b1fdc055b8071ad3b24573abfe9b96e546c7abf.patch
| patch -p1 && \
```

When that didn't apply I tried (as a temporary workaround) removing the
rule, but for some reason it was still triggering in my unit tests. For
that I used:

```
SecRuleRemoveById 930110
```

I don't really know where to go from here, i'm using the CRS 3.2.0 ruleset.

Best Regards,

Henri

_______________________________________________
mod-security-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mod-security-users
Commercial ModSecurity Rules and Support from Trustwave's SpiderLabs:
http://www.modsecurity.org/projects/commercial/rules/
http://www.modsecurity.org/projects/commercial/support/