handler + lua bypass

donatas.abraitis · 2014-09-06T05:03:12+00:00

Hello I'm using nginx 1.6.1. I will test the same in 1.7.4. Thanks for the info.

handler + lua bypass

donatas.abraitis

Hey,

have you any idea how to tell ModSecurity handler to go next to post_action after handling? Because now it proxy_pass and that's it.

My configuration is like:

location /logging {

content_by_lua_file /usr/local/openresty/nginx/conf/logs.lua;

}

location ~* \.(js|css)$ {

ModSecurityEnabled on;

proxy_pass http://backend;

post_action /logging;

}

If I commented ModSecurityEnabled, I'm redirected to /logging and lua content is parsed good.

If I commented out ModSecurityEnabled, no post_action is made..

Maybe it's possible with Lua to bypass this?

agentzh

Hello!

On Fri, Sep 5, 2014 at 2:03 PM, Donatas Abraitis wrote:
> have you any idea how to tell ModSecurity handler to go next to post_action
> after handling? Because now it proxy_pass and that's it.
>

The undocumented "post_action" feature is buggy and better avoid using
it (and I won't bother spending any of my time to debug any issues
with it).

One can try using log_by_lua (+ ngx.timer.at(), if IO is involved) to
replace "post_action".

Regards,
-agentzh