[Mod-security-developers] [JIRA] Resolved: (MODSEC-37) SecRuleUpdateActionById doesn't seem to work as expected

[Breno S. P. (JIRA) <no...@mo...>]

     [ https://www.modsecurity.org/tracker/browse/MODSEC-37?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Breno Silva Pinto resolved MODSEC-37.
-------------------------------------

    Resolution: Fixed

> SecRuleUpdateActionById  doesn't seem to work as expected
> ---------------------------------------------------------
>
>                 Key: MODSEC-37
>                 URL: https://www.modsecurity.org/tracker/browse/MODSEC-37
>             Project: ModSecurity
>          Issue Type: Bug
>      Security Level: Normal
>          Components: Core
>    Affects Versions: 2.5.6
>         Environment: Apache2/Ubuntu 8.04 LTS
>            Reporter: Peter Termaten
>            Assignee: Breno Silva Pinto
>             Fix For: 2.6.0
>
>
> I'm trying to change the actions of rule 960015, which is in modsecurity_crs_21_protocol_anomalies.conf.
> I added:
> SecRuleUpdateActionById 960015 "deny,status:400,msg:'Rule 960015 denied'"
> to modsecurity_crs_60_customrules.conf
> but I see no changes in the behaviour.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://www.modsecurity.org/tracker/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira