Allow NoopHostNameVerifier to be set for SOCKS Proxy #647
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
It's useful, during testing, when using a SOCKS Proxy, to allow the HostnameVerifier to be set to a NoopHostNameVerifier - similar to how *non SOCKS proxy* connections allow this to be done. This change allows a NoopHostNameVerifier to be used if the key `:insecure` (or `:insecure?`) is set `true` in the config settings during `make-socks-proxied-conn-manager`. -=david=-
# for free
to join this conversation on GitHub.
Already have an account?
# 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.
It's useful, during testing, when using a SOCKS Proxy, to allow the HostnameVerifier to be set to a NoopHostNameVerifier - similar to how non SOCKS proxy connections allow this to be done.
This change allows a NoopHostNameVerifier to be used if the key
:insecure(or:insecure?) is settruein the config settings duringmake-socks-proxied-conn-manager.-=david=-