Re: [users@httpd] Re: ModSecurity and custom headers

2017-03-14 Thread Andrei
bump On Sat, Mar 11, 2017 at 4:14 PM, Andrei wrote: > I also tried for example: > > SecDefaultAction "phase:2,deny,log,status:406, > setenv:'env_modsecblk=%{rule.msg}'" > > Header always set X-ModSec-Block %{env_modsecblk}e env=env_modsecblk > > > But that also fails with: > > AH00526: Synta

Re: [users@httpd] Re: ModSecurity and custom headers

2017-03-11 Thread Andrei
I also tried for example: SecDefaultAction "phase:2,deny,log,status:406,setenv:'env_modsecblk=%{rule.msg}'" Header always set X-ModSec-Block %{env_modsecblk}e env=env_modsecblk But that also fails with: AH00526: Syntax error on line 21 of /usr/local/apache/conf/modsec2.conf: Cannot parse con

Re: [users@httpd] Re: ModSecurity and custom headers

2017-03-11 Thread Andrei
Hello again :) So I went to the modsec lists, figured out how to get the environment variable set with the rule message by default for all rules, then push the 'msg' to a custom X header from there. For example: SecDefaultAction "phase:2,deny,log,setenv:'env_msecblk=%{rule.msg}'" Header always se

Re: [users@httpd] Re: ModSecurity and custom headers

2017-03-01 Thread Andrei
Thanks! On Wed, Mar 1, 2017 at 3:36 AM, Luca Toscano wrote: > Hi Andrei, > > 2017-03-01 6:54 GMT+01:00 Andrei : > >> Is there a different list I should be asking this on? >> > > I would start from https://modsecurity.org/help.html (Mod Security is not > part of the httpd release since it is a th

Re: [users@httpd] Re: ModSecurity and custom headers

2017-03-01 Thread Luca Toscano
Hi Andrei, 2017-03-01 6:54 GMT+01:00 Andrei : > Is there a different list I should be asking this on? > I would start from https://modsecurity.org/help.html (Mod Security is not part of the httpd release since it is a third party module). Hope that helps! Luca

[users@httpd] Re: ModSecurity and custom headers

2017-02-28 Thread Andrei
Is there a different list I should be asking this on? On Mon, Feb 27, 2017 at 8:49 AM, Andrei wrote: > Hi all, > > How can I add a custom header using the 'msg' value from a ModSecurity > rule, for all rules triggered? I'm basically trying to track the ModSec > block reason at an edge point (Var