[1.x] Fix IP address retrieval when using reverse proxy #49
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
milwad-dev
changed the title
Member
|
Thanks! |
Contributor
Author
|
@milwad-dev Please update the README to reflect the new configuration options, including use_reverse_proxy_ip. Thank you! |
Member
|
Yes ofcourse |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request fixes the issue where the request()->ip() method doesn't return the correct IP address when using a reverse proxy (such as Nginx or Cloudflare).
When a reverse proxy is used, the IP address of the proxy is returned instead of the client's real IP. To address this, the code now checks the X-Forwarded-For header to retrieve the correct client IP.