[ https://www.modsecurity.org/tracker/browse/MODSEC-348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Breno Silva Pinto resolved MODSEC-348.
--------------------------------------
Resolution: Fixed
Hello Mike,
I did some tests with the new trunk. Looks fixed.
If you can test and send a feedback.
Thanks
Breno
> initcol not working with NGINX port of mod_sec
> ----------------------------------------------
>
> Key: MODSEC-348
> URL: https://www.modsecurity.org/tracker/browse/MODSEC-348
> Project: ModSecurity
> Issue Type: Bug
> Security Level: Normal
> Components: Actions, Core, Logging
> Affects Versions: 2.7.0
> Environment: EL6
> Reporter: Mike Fisher
> Assignee: Breno Silva Pinto
> Fix For: 2.7.3
>
>
> I've already reported this by mail 14 days ago, but want to make sure it doesn't get lost, so I'm creating this bug report.
> With the current NGINX version of mod_security, if you use rules that include initcol, such as "initcol:ip=%{REMOTE_ADDR}", the collection file doesn't get written at all (eg. '/tmp/ip' or '/tmp/ip.pag' in my example case). Therefore it's impossible to track IPs/actions and so on.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
