Bugs item #1371118, was opened at 2005-12-01 19:50
Message generated for change (Comment added) made by bagder
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100976&aid=1371118&group_id=976

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: http
Group: wrong behaviour
Status: Open
Resolution: Accepted
Priority: 5
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Daniel Stenberg (bagder)
Summary: IPv6 RFC 2732 addrs are not fully supported

Initial Comment:
Recently support for RFC 2732 style IPv6 addresses was
added to the proxy option, but a non-proxy address
remains broken.

Also, it seems zone IDs are not properly parsed..

Bad zone parsing:

curl -x 'http://[fe80::2e0:81ff:fe28:d04c%eth2]:8080/'
http://moo/
curl: (5) Couldn't resolve proxy 'fe80'

No 2732 parsing on addreses:

curl -6 'http://[fe80::2e0:81ff:fe28:d04c]:8080/'
curl: (3) [globbing] illegal pattern or range
specification after pos 9

curl -V
curl 7.15.0 (i686-pc-linux-gnu) libcurl/7.15.0
OpenSSL/0.9.7e zlib/1.2.2 libidn/0.5.13
Protocols: tftp ftp gopher telnet dict ldap http file
https ftps
Features: IDN IPv6 Largefile NTLM SSL libz

It doesn't seem clear what the correct format is for a
zone ID in a URI should be WRT to escaping the %, but
at least firefox 1.0.4 requires the % be unescaped..

----------------------------------------------------------------------

>Comment By: Daniel Stenberg (bagder)
Date: 2005-12-02 00:44

Message:
Logged In: YES
user_id=1110

Yes, it fails with IPv6 numericals if -g isn't used.

----------------------------------------------------------------------

Comment By: Dan Fandrich (dfandrich)
Date: 2005-12-02 00:42

Message:
Logged In: YES
user_id=236775

Note the second part of the bug report: curl doesn't seem to
handle numeric-format IPv6 addresses in the URL, even
without a zone ID. I just tried it myself with the same results.

----------------------------------------------------------------------

Comment By: Daniel Stenberg (bagder)
Date: 2005-12-01 23:07

Message:
Logged In: YES
user_id=1110

Where is that "%eth2" thing defined?

It is not mentioned in RFC2732 (AFAICS) and not in RFC2373
(which RFC2732 refers to in regard how the literal string
should look like between the brackets).

So, I would say that it seems curl _is_ RFC2732 compliant
but we might need to extend its compliance to some other
spec that defines the "%ethN" suffix.

----------------------------------------------------------------------

Comment By: Daniel Stenberg (bagder)
Date: 2005-12-01 23:00

Message:
Logged In: YES
user_id=1110

The second case works if you disable "globbing" with -g.

----------------------------------------------------------------------

You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100976&aid=1371118&group_id=976
Received on 2005-12-02