-
Notifications
You must be signed in to change notification settings - Fork 1.6k
nginx/1.8.0+ ModSecurity 2.9 ERR_EMPTY_RESPONSE #928
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Are you using the nginx-refactoring branch ? Are you willing to test the development version of ModSecurity 3.0 ? |
No, I am using a main branch. I would love to test it. |
Hi @rz300, What are the rule set that you are currently using? OWASP? is that v3.0? Custom? The current version does not have support for all the operators, neither transformations yet, but should work on a reduced scope |
It's kind of works, but I'm not sure. I have been download tar from official site, version 2.8.I have not figured out how to connect owasp, so there is default rules from modsecurity.conf |
i solved my problem. there is stupid config of nginx vhost. I've catched another error. in some sites i catch 403 with owasp rules e.g. |
@rz300 that is a rule in the 2.0 version of the ruleset that is known to be particularly prone to false positives... please attempt to use the 3.x branch https://github.com/SpiderLabs/owasp-modsecurity-crs/tree/v3.0.0-dev |
Hi, I got this problem after installing ModSec. Google Chrome says net :: ERR_EMPTY_RESPONSE and several files didn't load, e.g. logo.png and font-awesome.ttf
mod security debug.log http://pastebin.com/Nfhjvk7T
Debian 8
And i've unusual nginx config, and i dont'n know where
ModSecurityEnable on;
is necessary to insertThe text was updated successfully, but these errors were encountered: