Re: SecRequestBodyAccess Modsecurity

___ > nginx mailing list > nginx@nginx.org > http://mailman.nginx.org/mailman/listinfo/nginx -- Br., Felipe Zimmerle ___ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx

Re: New compilation failure

Hi, Please upgrade your libModSecurity to v3.0.3: https://github.com/SpiderLabs/ModSecurity/releases/tag/v3.0.3 Br., Z. On Fri, Nov 9, 2018 at 11:14 AM alang wrote: > Yeah I fixed this issue. It was definitely the modsecurity connector. > They > had done an update to master branch that requir

Re: nginx/1.9.9 with modsecurity/2.9.0 crashes with segfault and worker process exited on signal 11

Hi Lukas, On Sun, Jan 10, 2016 at 11:05 AM Lukas wrote: > I found that recommendation. Since I also read that it would not be > fully compatible with OWASP/CRS I have not given it a try. > > What is the situation regrading OWASP/CRS? > Currently there are three different versions of ModSecurit

Re: nginx/1.9.9 with modsecurity/2.9.0 crashes with segfault and worker process exited on signal 11

Hi Lukas, You may want to use the ModSecurity's nginx_refactoring branch instead of the master branch. Here is the link to the branch: https://github.com/SpiderLabs/ModSecurity/tree/nginx_refactoring Br., Felipe Zimmerle Lead dev for ModSecurity On Sun, Jan 10, 2016 at 10:39 AM Lukas

Re: ModSecurity compile, ""WARNING: APR util was not compiled with crypto support."

Hi, It should not be a problem. The parameter "crypto" is optional and should not affect ModSecurity behavior. Check the SecRemoteRules description on ModSecurity reference manual, at: https://github.com/SpiderLabs/ModSecurity/wiki/Reference-Manual#secremoterules Br, Z. Posted at Nginx Forum: