|
From: Ryan B. (JIRA) <no...@mo...> - 2011-03-10 16:31:49
|
[ https://www.modsecurity.org/tracker/browse/MODSEC-201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ryan Barnett closed MODSEC-201.
-------------------------------
Resolution: Won't Fix
As Brian showed, this type of functionality can be achieved through different SecRule methods (setvars and skipAfters)
> Expiration/activation date
> --------------------------
>
> Key: MODSEC-201
> URL: https://www.modsecurity.org/tracker/browse/MODSEC-201
> Project: ModSecurity
> Issue Type: New Feature
> Security Level: Normal
> Components: Core
> Affects Versions: 2.5.13
> Reporter: Marc Stern
> Assignee: Breno Silva Pinto
>
> It would be very handy to be able to specify a date range when a rule should be active.
> The main interest is when using rules to "open" an application.
> For example: SecAction "ctl:ruleRemoveById=200111,date=20110213-20110215" to disable a rule for 2 days
> We could also used "timestamp" if we want to be able to specify a time on top of the date.
> One of the parameters could be optional "date=-20110215" (up to) or "date=20110213-" (from).
> This is a good practice in network firewalls to not forget to remove a rule used during tests or specific occasions.
--
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
|
