-
Notifications
You must be signed in to change notification settings - Fork 27
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
Transfer of real client IP #55
Comments
Same for me, for the moment i use this trick |
I already tried this but it doesn't work for me((( on haproxy I have it like this `global defaults backend my_backend backend spoe-modsecurity frontend fe_main but in the logs I still don’t understand why logs are not written to moaudit.log file is empty |
Tell me why not all parameters are accepted? Maybe because of this the normal IP is not transmitted? spoe-message check-request spoe-message check-request |
This solution works Use this fork : https://github.com/infra-octave/spoa-modsecurity spoe-modsecurity.conf
|
Well, I wanted to figure out why the docker from this turnip does not work as expected |
haproxy/spoa-modsecurity@master...infra-octave:spoa-modsecurity:master#diff-8c7cd210990f9430651c54ed753427ec1bb59cc3f4ae2003daed70f490e3a6d0R251 |
I don't test with ipv6 |
Hello, I'm testing modsec and haproxy in the logs of my container, the client IP is always 127.0.0.1
example
1697202928.470503 [00] [client 127.0.0.1] ModSecurity: Warning. Operator GE matched 5 at TX:inbound_anomaly_score.
I can’t find how to make it work with a real IP client
Please tell me what needs to be done?
The text was updated successfully, but these errors were encountered: