Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Allow NoopHostNameVerifier to be set for SOCKS Proxy #647

Open
wants to merge 1 commit into
base: 3.x
Choose a base branch
from
Open

Allow NoopHostNameVerifier to be set for SOCKS Proxy #647

wants to merge 1 commit into from

Commits on May 21, 2024

  1. Allow NoopHostNameVerifier to be set for SOCKS Proxy 

    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=-
    @dharrigan
    dharrigan committed May 21, 2024
    Configuration menu
    Copy the full SHA
    c98f783 View commit details
    Browse the repository at this point in the history