Add 'get_recursive' option for legacy whois to RIPE NCC #295
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 patch adds an argument
get_recursivetolookup_whois(). Theargument default is True, which causes no change to the behavior. If
the user passes
get_recursive=False, and the IP is allocated toRIPE, this causes the
-rflag to be included in the query string.The
-rflag asks RIPE WHOIS servers not to perform recursivequeries, such as for related "person" or "role" objects. This helps
users avoid IP blacklisting by RIPE.
The
-rflag is only supported by RIPE, so this patch only affectsqueries to RIPE servers.
Resolves #292