connect-to now doing tcp connect instead of dns caching #807
+311
−32
Conversation
This file contains hidden or 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
Author
|
meh. Will check |
Author
|
Yeah, Could not automatically determine the process-level CryptoProvider from Rustls crate features. CryptoProvider issue. Will put it back |
Owner
|
OK |
Author
|
Rerun workflow pls |
added 2 commits
October 24, 2025 12:05
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Updated --connect-to to establish connections directly to the specified IP address, rather than relying on local DNS caching. When a proxy is used, DNS resolution occurs on the proxy server, causing routing issues.
The new connection now uses:
The target IP from --connect-to for the connection.
The original Domain (Host Header) for correct proxy handling.
The original SNI for TLS negotiation.