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.
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 settrue
in the config settings duringmake-socks-proxied-conn-manager
.-=david=-