Am 01.12.2016 um 10:53 schrieb Ehsan Mahdavi:
Dear Christian
It isn't very odd to me if Matej uses Nginx with Modsec V2.x.

As an experienced Nginx + Modsec V2.x(nginx_refactoring) user, it looks like to a known bug. While using nginx+modsecV2.x in reverse proxy mode (which is not the case for Matej) we have the very same issue for some post requests.
I can refer you to these links:

http://permalink.gmane.org/gmane.comp.apache.mod-security.user/12502 <http://permalink.gmane.org/gmane.comp.apache.mod-security.user/12502> https://github.com/SpiderLabs/ModSecurity/issues/115 <https://github.com/SpiderLabs/ModSecurity/issues/115> https://github.com/SpiderLabs/ModSecurity/issues/582 <https://github.com/SpiderLabs/ModSecurity/issues/582> https://github.com/SpiderLabs/ModSecurity/issues/664 <https://github.com/SpiderLabs/ModSecurity/issues/664> https://github.com/SpiderLabs/ModSecurity/issues/748 <https://github.com/SpiderLabs/ModSecurity/issues/748>


All complaining about this problem and no one takes the responsibility.
The only way is to disable modsec for the requested uri and wait for the community to release modsec V3.0 or higher and hope that this bug will be fixed.

Meantime he/she might findctl:ruleEngine=off <https://github.com/SpiderLabs/ModSecurity/wiki/Reference-Manual#ctl> useful.

Br. Ehsan

Hi,

I didn't follow all the bugs and issues but how can I reproduce this?
I have a running test setup with nginx 1.11.5, Modsecurity-nginx connector (source 2 weeks old) and Modsecurity v3.

Then I could try to find out if it's already fixed ..

BR,
Michael
_______________________________________________
Owasp-modsecurity-core-rule-set mailing list
Owasp-modsecurity-core-rule-set@lists.owasp.org
https://lists.owasp.org/mailman/listinfo/owasp-modsecurity-core-rule-set

Reply via email to