--resolve doesn't work with IPv6 addresses in bracket notation #2087
Comments
An IPv6 address is not generally written with brackets outside of URLs, see RFC 5952 "A Recommendation for IPv6 Address Text Representation". Can you explain why you think you should do it in I also don't see it mentioned in the documentation. |
There are three reasons I thought it should be used with brackets in
|
bagder
added a commit
that referenced
this issue
Nov 17, 2017
... so that IPv6 addresses can be passed like they can for connect-to and how they're used in URLs. Added test 1324 to verify Reported-by: Alex Malinovich Fixes #2087
You convinced me. Thanks! PR for adding support for brackets is in #2091 ! |
Thanks! |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I did this (host/ip are intentionally obfuscated)
I expected the following
For
myhost.domain.com
to resolve to[dead:beef:1234:5678:8765:4321:feed:daed]
, but what I got was:If I specify the IPv6 address incorrectly, that is without the brackets, then it works as expected:
curl/libcurl version
operating system
The text was updated successfully, but these errors were encountered: