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.

Sign up for GitHub

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

Jump to bottom

Take into account the X-Forwarded-For header in order to get the visitor information, in case the server is behind a load balancer or proxy #40

Closed
acelaya opened this issue Aug 5, 2016 · 0 comments
Closed

Take into account the X-Forwarded-For header in order to get the visitor information, in case the server is behind a load balancer or proxy #40

acelaya opened this issue Aug 5, 2016 · 0 comments
Assignees
@acelaya
Labels
bug
Milestone
1.1.0

Comments

@acelaya
Copy link
Member

acelaya commented Aug 5, 2016

No description provided.

@acelaya acelaya added this to the 1.1.0 milestone Aug 5, 2016
@acelaya acelaya self-assigned this Aug 5, 2016
@acelaya acelaya changed the title Take into account X-Forwarded header in order to get the referrer, in case the server is behind a load balancer or proxy Take into account X-Forwarded-* headers in order to get the visiter onformation, in case the server is behind a load balancer or proxy Aug 5, 2016
@acelaya acelaya changed the title Take into account X-Forwarded-* headers in order to get the visiter onformation, in case the server is behind a load balancer or proxy Take into account X-Forwarded-* headers in order to get the visiter information, in case the server is behind a load balancer or proxy Aug 5, 2016
@acelaya acelaya changed the title Take into account X-Forwarded-* headers in order to get the visiter information, in case the server is behind a load balancer or proxy Take into account the X-Forwarded-For header in order to get the visitor information, in case the server is behind a load balancer or proxy Aug 5, 2016
@acelaya acelaya added bug and removed enhancement labels Aug 8, 2016
@acelaya acelaya closed this as completed Aug 9, 2016
@levdad levdad mentioned this issue Jun 7, 2020
Closed
@rumeau rumeau mentioned this issue May 24, 2021
Closed
@ghost ghost mentioned this issue Nov 11, 2022
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@acelaya acelaya

Labels
bug
Projects
None yet
Milestone
1.1.0
Development

No branches or pull requests
1 participant
@acelaya