forked from louketo/louketo-proxy
-
Notifications
You must be signed in to change notification settings - Fork 42
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
Log client_ip with real ip value #209
Comments
sk1m
pushed a commit
to sk1m/gatekeeper
that referenced
this issue
Sep 8, 2022
sk1m
pushed a commit
to sk1m/gatekeeper
that referenced
this issue
Sep 8, 2022
2 tasks
sk1m
pushed a commit
to sk1m/gatekeeper
that referenced
this issue
Sep 8, 2022
@sk1m understand why it is useful but what if you want to e.g. log both |
@p53 agree, much better will be write both |
sk1m
pushed a commit
to sk1m/gatekeeper
that referenced
this issue
Sep 9, 2022
sk1m
pushed a commit
to sk1m/gatekeeper
that referenced
this issue
Sep 9, 2022
p53
pushed a commit
that referenced
this issue
Sep 9, 2022
2 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Log client_ip with real ip value
Summary
Set field value "client_ip" to real ip when logging.
Why?
Currently, field client_ip has value of RemoteAddr, which can be unuseful if gatekeeper placed behind another proxy.
How
Use
utils.RealIP
result for "client_ip" field value.Acceptance criteria
Additional Information
The text was updated successfully, but these errors were encountered: