forked from Rob--W/cors-anywhere
-
Notifications
You must be signed in to change notification settings - Fork 0
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
Add dnsLookup option to allow custom blacklist/whitelist logic #1
Merged
Merged
Changes from 3 commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
e3ddf7c
Add dnsLookup option to allow custom blacklist/whitelist logic
jonhaddow ed5a5b7
Add exclusion logic to server.js
jonhaddow 6dec16a
Re-add config option
jonhaddow 686de88
Add IP check into dns.lookup
jonhaddow 2c6453c
Set dnsLookup to null by default
jonhaddow File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does this not need to include the
logic? Also, we need to exclude loopback addresses (IPv4 addresses starting with
127.
or IPv6 addresses starting with::1
) and site local addresses (IPv4 addresses starting with10.
,172.16.
or192.168.
, you might have to ask Google what the IPv6 equivalents are...)There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, I can include that in this PR. Was wondering if it should be a separate PR specific to our use case.
I guess any PR submitted upstream can have it separated.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Marc's request was
so it should be fine to tackle all of those use cases in a single PR (and you're right, we could always tidy up the code in future by adding separate
isLoopbackAddress
andisLocalAddress
methods)...