-
-
Notifications
You must be signed in to change notification settings - Fork 6.4k
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.
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
Problem with resolving hostname with socks5 proxy on 7.69.0 #5053
Comments
Does the fix apply to socks4 proxy too? I am using socks4 and facing similar problem after upgrading from curl 7.67.0 to 7.69
It worked fine with 7.67.0 |
It does not, as I wasn't aware of any problem there. Can you please submit this as a new issue and I'll see if it has the same bug there perhaps... |
1. The socks4 state machine was broken in the host resolving phase 2. The code now insists on IPv4-only when using SOCKS4 as the protocol only supports that. Regression from #4907 and 4a4b63d, shipped in 7.69.0 Reported-by: amishmm on github Bug: #5053 (comment)
1. The socks4 state machine was broken in the host resolving phase 2. The code now insists on IPv4-only when using SOCKS4 as the protocol only supports that. Regression from #4907 and 4a4b63d, shipped in 7.69.0 Reported-by: amishmm on github Bug: #5053 (comment) Closes #5061
Hi,
I have some problems with resolving host name
~ curl --version
curl 7.69.0 (x86_64-apple-darwin19.3.0) libcurl/7.69.0 SecureTransport zlib/1.2.11
Release-Date: 2020-03-04
Protocols: dict file ftp ftps gopher http https imap imaps ldap ldaps pop3 pop3s rtsp smb smbs smtp smtps telnet tftp
Features: AsynchDNS IPv6 Largefile libz NTLM NTLM_WB SSL UnixSockets
When trying to use socks5 proxy after upgrade i get :
curl: (6) Couldn't resolve host name
Command: curl -x socks5://username:password@11.11.11.11:1080 https://google.com -v
if I use socks5h everything ok
Command curl -x socks5h://username:password@11.11.11.11:1080 https://google.com -v
On version 7.68.0 command curl -x socks5://username:password@11.11.11.11:1080 https://google.com -v works well
The text was updated successfully, but these errors were encountered: