Skip to content
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

IPv6 address in URL #3218

Closed
tpaukrt opened this issue Nov 2, 2018 · 1 comment
Closed

IPv6 address in URL #3218

tpaukrt opened this issue Nov 2, 2018 · 1 comment
Labels

Comments

@tpaukrt
Copy link

@tpaukrt tpaukrt commented Nov 2, 2018

I did this

curl http://[fd00:a41::50]

I did not expected the following

curl: (3) URL using bad/illegal format or missing URL

curl/libcurl version

curl 7.62.0 (arm-unknown-linux-gnu) libcurl/7.62.0 OpenSSL/1.0.2o zlib/1.2.11
Release-Date: 2018-10-31
Protocols: ftp ftps http https
Features: IPv6 Largefile NTLM SSL libz TLS-SRP UnixSockets HTTPS-proxy

@bagder
Copy link
Member

@bagder bagder commented Nov 2, 2018

Clearly a regression from the URL parser overhaul. I'm on it. A work-around that seems to avoid this bug is to add the port number:

curl 'http://[fd00:a41::50]:80/'
bagder added a commit that referenced this issue Nov 2, 2018
Regression from 46e1640. Extended test 1560 to verify.

Reported-by: tpaukrt on github
Fixes #3218
@bagder bagder closed this in b280948 Nov 2, 2018
delroth added a commit to delroth/nixpkgs that referenced this issue Nov 22, 2018
Upstream bug: curl/curl#3218.

This causes nixos/tests/ipv6.nix to fix since the last staging merge.
FRidh added a commit to NixOS/nixpkgs that referenced this issue Nov 22, 2018
Upstream bug: curl/curl#3218.

This causes nixos/tests/ipv6.nix to fix since the last staging merge.
vcunat added a commit to NixOS/nixpkgs that referenced this issue Nov 25, 2018
Upstream bug: curl/curl#3218.

This causes nixos/tests/ipv6.nix to fix since the last staging merge.

(cherry picked from commit 90720d0)
In the end I decided to pick it directly without staging,
so that the various security fixes get to stable* channels fast.
@lock lock bot locked as resolved and limited conversation to collaborators Jan 31, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.