fix: do not ignore host when connect tls

[warjiang]

for bilateral tls verification, the host should not be ignored, if the host field be ignored, it will be set to localhost automatically. But the default host(localhost) is not correspoding to tls certificate.

for kubernetes it will use bilateral tls verification, for tls website it will use single tls verification. And I've already tested the traditional tls web site and the communication of kuberntes apiserver two traditional cases, it all works ok.

relasted issues: #365

[changeset-bot]

⚠️ No Changeset found

Latest commit: e7fec9f

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated (UTC)
proxy-agents	✅ Ready (Inspect)	Visit Preview	Mar 22, 2025 2:35pm

[warjiang]

how to work with changeset @TooTallNate

[warjiang]

@lukekarrys should I reformat the code for passing CI, any local format instructions for me?

[warjiang]

@lukekarrys should I reformat the code for passing CI, any local format instructions for me?

@lukekarrys Sorry, it's not the problem of lint, it's the problem of format task. I've already fix the format problem, could you help me to re-trigger the Node CI action?

[jarroyorodriguez-dashlane]

Hello @TooTallNate 👋 Sorry to bother

I'm also hitting an issue where this would fix it. The root cause is the same although my issue is a bit different.

We're trying to hit a DNS server with an HTTPS proxy using an IP address (on my case cloudflare: 1.1.1.1 DNS resolver 1.1.1.1/dns-query).

I dug through the history and saw that the lib added code to correctly not set SNI for IPs, but in doing so also drops the host from the TLS connect which will then fail because the checkServerIdentity will fallback to the proxy host instead of the 1.1.1.1 host. In my case for cloudflare I can add a workaround by using one.one.one.one so SNI is set.

I thought I'd bring it up. Let me know if I can help