-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Fix error logging for standalone module #3374
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
Fix error logging for standalone module #3374
Conversation
I have tested this on a standalone installation of ModSecurity v2.9.8 and can confirm that it restores client IP address logging as intended. |
A reminder to me (or to us 😄) - we should add more tests, eg. which will check standalone build (and test it...?) too. |
Thanks @RedXanadu, my last request: could you pick up the current state from |
Restores the original format string for error logging for ModSecurity when compiled as a standalone module. Specifically, the format string has "[client %s]" back again: this is required for standalone modules as Apache is not present to implicitly log the client source IP address.
b16f088
to
0c7dadc
Compare
|
@airween Sure: now rebased onto the current |
Awesome, thank you! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
what
This PR:
[client %s]
back again: this is required for standalone modules as Apache is not present to implicitly log the client source IP address.why
It is essential for the client source IP address to be written to the error log. This is required for resolving false positives, monitoring, detecting attacks, and the majority of day to day WAF operations.
This PR fixes the bug introduced in an attempt to tidy error logging for Apache in PR #3192.
references
closes #3373