Cloudflare Driver #120
Merged
Cloudflare Driver #120
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
nik-418
force-pushed
the
cloudflare
branch
5 times, most recently
from
992bcf4
to
55e558e
Compare
MrAnassBaba
reviewed
Dec 21, 2022
style fix useless import xx and t1 style fix readme unused var
|
Thanks @nik-418! 👍 |
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.
This PR adds support for Cloudflare as a built-in driver.
If your domain is behind Cloudflare's nameservers, you get geolocation for free in one of two ways: https://support.cloudflare.com/hc/en-us/articles/200168236-Configuring-IP-geolocation
cf-ipcountryheader to all incoming requests.cf-ipcountry,cf-ipcity,cf-iplongitude, andcf-iplatitudeheaders.This means that you can get (limited) geolocation data without any additional API calls or local database lookups if this is enough for your use case.