[ https://www.modsecurity.org/tracker/browse/MODSEC-297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Breno Silva Pinto resolved MODSEC-297.
--------------------------------------
Resolution: Fixed
Fixed in the trunk. Also changed in the documentation to set it as a Disruptive action.
Do you have time for test ? I can send you a tarball.
Thanks
Breno
> Pause-action silently ignored in combination with Pass-action
> -------------------------------------------------------------
>
> Key: MODSEC-297
> URL: https://www.modsecurity.org/tracker/browse/MODSEC-297
> Project: ModSecurity
> Issue Type: Bug
> Security Level: Normal
> Components: Rules
> Affects Versions: 2.6.3
> Environment: SUSE Linux Enterprise Server 11 SP1 (x86_64), selfcompiled. Apache 2.2.22
> Reporter: Christian Folini
> Assignee: Breno Silva Pinto
> Priority: Low
> Fix For: 2.8.0
>
>
> Trying to find new uses for ModSecurity, I am not using it as a backend application simulator in reverse proxy performance test.
> This rule does not work as expected:
> SecRule ARGS_GET:pause "^(1000)$" "phase:2,pass,pause:1000"
> While these two work fine:
> SecRule ARGS_GET:pause "^(2000)$" "phase:2,allow,pause:2000"
> SecRule ARGS_GET:pause "^(3000)$" "phase:2,deny,pause:3000"
> I admit this is a small bug, but it I ModSecurity to behave as expected. Or to find some hint/explanation in the documentation.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
|