Adding Cloudflare IP detection compatibility #110
Merged
Conversation
This file contains 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
|
@eightam thanks for the PR! I’ve set this for our next release and will get back to you if there are any questions or concerns after review. |
dinhtungdu
approved these changes
Feb 3, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description of the Change
Adding proprietary Cloudflare headers to IP detection.
Alternate Designs
Cloudflare only stores the real client IP in these headers, no other solution found.
Benefits
Plugin will work with sites served through Cloudflare.
Possible Drawbacks
None noticed.
Verification Process
Clicking the "Add my own IP Address" button produced the real client IP.
Checklist:
Applicable Issues
#109