|
From: Ryan B. (JIRA) <no...@mo...> - 2011-03-02 18:54:31
|
[ https://www.modsecurity.org/tracker/browse/MODSEC-56?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ryan Barnett closed MODSEC-56.
------------------------------
Resolution: Not a Bug
We added notes to the reference manual which specifies when to use before/after the target rule(s) -
https://sourceforge.net/apps/mediawiki/mod-security/index.php?title=Reference_Manual#SecRuleRemoveById
https://sourceforge.net/apps/mediawiki/mod-security/index.php?title=Reference_Manual#ctl
> SecRuleRemoveById vs. ctl:ruleRemoveById order
> ----------------------------------------------
>
> Key: MODSEC-56
> URL: https://www.modsecurity.org/tracker/browse/MODSEC-56
> Project: ModSecurity
> Issue Type: Improvement
> Security Level: Normal
> Components: Core
> Affects Versions: 2.5.9
> Environment: Any
> Reporter: Marc Stern
> Assignee: Breno Silva Pinto
> Fix For: 2.6.0
>
>
> SecRuleRemoveById needs to appear after the rule it disables, whereas ctl:ruleRemoveById must appear before.
> This is not only confusing, but also obliges to put some rules before and some after the rule to disable, which complexifies the management.
> Couldn't SecRuleRemoveById be supported before the rule, by storing the id in a table during config build?
--
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
|
