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

log X-Forwarded-For as ClientHost if present #1946

Merged
merged 4 commits into from
Aug 25, 2017
Merged

Conversation

mildis
Copy link
Contributor

@mildis mildis commented Aug 11, 2017

Log X-Forwarded-For value as ClientHost, if present.
Allow access log to display the correct caller behind a reverse proxy.

@emilevauge
Copy link
Member

@mildis Thanks for your contribution!
@rjshep as the author of this part, LGTY ?

@m3co-code
Copy link
Contributor

For me this change makes sense. AFAIK this is what is usually required from applications that sit behind a proxy and Traefik could also sit behind another proxy :D

Copy link
Contributor

@ldez ldez left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Copy link
Contributor

@nmengin nmengin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@Jancis
Copy link

Jancis commented May 28, 2020

I don't think this checks the forwardedHeaders.trustedIPs and so the access log can be filled with forged addresses.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/logs kind/enhancement a new or improved feature. size/S
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants