Re: websocket connection seems to cause nginx to not reload

Hi, On Tue, Apr 16, 2019, at 07:14, Andrea Y Ma wrote: > Seeing nginx not picking up changes to its configuration. Running > `nginx -t` does not reveal any errors and no errors generated when > running `nginx -s reload`. However nginx access logs show that the old > IPs from the previous config

Re: SecRequestBodyAccess Modsecurity

Hi Carlos There is a known problem on ModSercurity 2.x which leads to a problem somewhat similar to what you have reported. If you are running 2.x I would recommend you to move forward to 3.0.3: - https://github.com/SpiderLabs/ModSecurity - https://github.com/SpiderLabs/ModSecurity-nginx If tha

SecRequestBodyAccess Modsecurity

Hello everyone, can anyone help me? I recently compiled NGINX with Modsecurity and noticed that if I keep "On", the SecRequestBodyAccess parameter, I have problems with the POST method. If I keep the parameter as Off, access normally occurs. Does anyone have NGINX with Modsecurity and the SecReq

websocket connection seems to cause nginx to not reload

Seeing nginx not picking up changes to its configuration.  Running `nginx -t` does not reveal any errors and no errors generated when running `nginx -s reload`.  However nginx access logs show that the old IPs from the previous configuration are still being served.  Upon closer inspection seeing th