Skip to content
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

Client's (remote) IP is logged as both source and destination in audit log #167

Closed
defanator opened this issue Sep 24, 2019 · 0 comments
Closed

Comments

@defanator
Copy link
Collaborator

Log example:

10.69.65.6 - "GET /?abc../ HTTP/1.1" 302 0 - "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/73.0.3683.103 Safari/537.36" 156837944484.860433 - /var/log/modsecurity/audit/20190913/20190913-0957/20190913-095724-156837944484.860433 0 2663.000000 md5:06faa89af0fbe889c27bbe9b2d9051f6
---XtkwNdGM---A--
[13/Sep/2019:09:57:24 -0300] 156837944484.860433 10.69.65.6 52327 10.69.65.6 443
defanator added a commit to defanator/ModSecurity-nginx that referenced this issue Sep 24, 2019
Closes owasp-modsecurity#167.

While here, adjusted related code to use nginx own macros instead
of direct functions (htons, inet_ntoa).
pracj3am pushed a commit to cdn77/ModSecurity-nginx that referenced this issue Nov 4, 2022
Closes owasp-modsecurity#167.

While here, adjusted related code to use nginx own macros instead
of direct functions (htons, inet_ntoa).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant