Skip to content

Modsecurity1.9 + nginx An unsolved problem #1360

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

Closed
cloudproxys opened this issue Mar 23, 2017 · 1 comment
Closed

Modsecurity1.9 + nginx An unsolved problem #1360

cloudproxys opened this issue Mar 23, 2017 · 1 comment
Assignees
Labels
2.x Related to ModSecurity version 2.x

Comments

@cloudproxys
Copy link

This is a particularly interesting question,When I use the nginx reverse proxy function,If you only add a server, and the port is used 80,Modsecurity works very well(Of course, early to solve a lot of problems, for example, can not upload more than 8K pictures such as the problem),But when I add a second server, the problem arises,When I add the second server to use the port is also 80,Can not post request, that post request will be blocked,
image
When the second server port is modified to non-80,Everything is fine,But the reverse proxy is the use of different domain names, the use of the same port, why use modsecurity will be such a problem, I hope we can help solve,

@zimmerle zimmerle self-assigned this Mar 23, 2017
@zimmerle zimmerle added the 2.x Related to ModSecurity version 2.x label Mar 23, 2017
@zimmerle
Copy link
Contributor

Hi @houhuijian,

Please have a try on ModSecurity-nginx connector -
https://github.com/SpiderLabs/ModSecurity-nginx

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
2.x Related to ModSecurity version 2.x
Projects
None yet
Development

No branches or pull requests

2 participants