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
Fails to connect to host specified as IPv6 numerical address + zone id #3902
Comments
hey badger, and I need know what's your release plan, we will publish our GA build at 5/31, so could we use your new release if current master could solve this? |
Our release plans are always public and planned long in advance. 7.65.0 will be released in 48 hours. I believe this bug is already fixed, unless you can still reproduce this with the current source code I will close this duplicate as well. |
Duplicate of #3408 |
Hi Bagder: I have tried this as below:
with old release 7.60.0
so it could be reproduced with current master codes, please take a look, thanks. |
This is a different problem as is made quite clear in the output. Now it succeeds in parsing the URL but fails to connect. This is probably because the zone id isn't used correctly. |
Hi Daniel, when will you resolve and publish it? we need know your plan to decide what should we do before 5/30. |
The zone id parsing fix will be in curl 7.65.0 to be released in one day. It's unclear to me whether that will solve your problem. |
Reported-by: GitYuanQu on github Fixes #3902
@GitYuanQu try out #3914 and help verify if that corrects the problem for you! |
thanks Daniel and jay, I will try to verify this with #3914, thanks. |
Hi Daniel, how could I get the code of #3914, could I get this from snapshot directly? |
If you don't want to use git to get that code, you can for example use a daily snapshot from yesterday and then get #3914 as a regular patch and apply that manually and then rebuild. |
Hi Daniel:
|
sorry, use the wrong case, with the right case could be passed, but I still need investigation a little upper case then to close this.[quyuan@localhost src]$ ./curl --url sftp://root:SYS2009health@[fe80::20c:29ff:fe9c:409b%eth0]/home/ -T ../configure -k |
I have a little confused that why this case is failed? |
this could be passed: |
ok, I know that, thanks Daniel, I will close this, thanks. |
then my question is when will you will public this? |
may be I need use your public build to verify this. so I need reopen this and check it with new release, then to close if could not reproduced. |
Reported-by: GitYuanQu on github Fixes #3902
Reported-by: GitYuanQu on github Fixes #3902
Hi Daniel: |
It was done an hour ago.
|
duplicate with 3480.
I did this
[root@localhost src]# ls ../configure
../configure
[root@localhost src]# ./curl -V
curl 7.64.0-20181225 (x86_64-pc-linux-gnu) libcurl/7.64.0-20181225 OpenSSL/1.0.2p zlib/1.2.11 libssh2/1.7.0
Release-Date: 2018-12-25
Protocols: dict file ftp ftps gopher http https rtsp scp sftp smb smbs telnet tftp
Features: AsynchDNS Debug TrackMemory IPv6 Largefile NTLM NTLM_WB SSL libz TLS-SRP UnixSockets HTTPS-proxy
[root@localhost src]# ./curl --url sftp://root:sys2009health@[fe80::42f2:e9ff:fe30:c17%eth0]/home ../configure
curl: (3) URL using bad/illegal format or missing URL
curl: (6) Could not resolve host: ..
[root@localhost src]# ./curl --url sftp://root:SYS2009health@[2002:97b:c2bb:830:10:240:196:14]/home ../configure
curl: (60) SSL peer certificate or SSH remote key was not OK
More details here: https://curl.haxx.se/docs/sslcerts.html
curl failed to verify the legitimacy of the server and therefore could not
establish a secure connection to it. To learn more about this situation and
how to fix it, please visit the web page mentioned above.
curl: (6) Could not resolve host: ..
[root@localhost src]# ping6 2002:97b:c2bb:830:10:240:196:14
PING 2002:97b:c2bb:830:10:240:196:14(2002:97b:c2bb:830:10:240:196:14) 56 data bytes
64 bytes from 2002:97b:c2bb:830:10:240:196:14: icmp_seq=1 ttl=64 time=0.341 ms
64 bytes from 2002:97b:c2bb:830:10:240:196:14: icmp_seq=2 ttl=64 time=1.71 ms
^C
--- 2002:97b:c2bb:830:10:240:196:14 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1365ms
rtt min/avg/max/mdev = 0.341/1.027/1.714/0.687 ms
[root@localhost src]# ping6 fe80::42f2:e9ff:fe30:c17%eth0
PING fe80::42f2:e9ff:fe30:c17%eth0(fe80::42f2:e9ff:fe30:c17) 56 data bytes
64 bytes from fe80::42f2:e9ff:fe30:c17: icmp_seq=1 ttl=64 time=2.48 ms
64 bytes from fe80::42f2:e9ff:fe30:c17: icmp_seq=2 ttl=64 time=0.353 ms
^C
--- fe80::42f2:e9ff:fe30:c17%eth0 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1466ms
rtt min/avg/max/mdev = 0.353/1.417/2.482/1.065 ms
I expected the following
expect file could uploaded success
curl/libcurl version
curl 7.64.0-20181225 (x86_64-pc-linux-gnu) libcurl/7.64.0-20181225 OpenSSL/1.0.2p zlib/1.2.11 libssh2/1.7.0
Release-Date: 2018-12-25
Protocols: dict file ftp ftps gopher http https rtsp scp sftp smb smbs telnet tftp
Features: AsynchDNS Debug TrackMemory IPv6 Largefile NTLM NTLM_WB SSL libz TLS-SRP UnixSockets HTTPS-proxy
operating system
ALL
even I use release 7.64.1, it still failed.
next step, I will use current master to check this issue, thanks.
The text was updated successfully, but these errors were encountered: