[fix]When using a proxy with WebSocket, the DNS resolution should be performed within the proxy server. #4974
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in 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.
Some exchanges use DNS and CDN technologies. If the domain name is resolved locally, it will return the IP address of the nearest server to the exchange from the local network. In this case, the SOCKS client will pass this IP to the proxy server, and the proxy server will attempt to connect using this IP, leading to a timeout. The best approach is to have the proxy server handle the DNS resolution.
Here is an analysis of part of the Netty source code:
Bootstrap.java2.
Socks5ProxyHandler.java