Once upon a time, Josh Stone <jistone(a)redhat.com> said:
On 06/21/2011 05:54 AM, Andreas Schwab wrote:
> David Woodhouse <dwmw2(a)infradead.org> writes:
>
>> And curl is just broken for numeric IPv6 addresses completely:
>>
>> [dwmw2@i7 activesyncd]$ curl
http://[2001:8b0:10b:1:21d:7dff:fe04:dbe2]/
>> curl: (3) [globbing] error: bad range specification after pos 9
>
> $ curl http://\\\[2001:8b0:10b:1:21d:7dff:fe04:dbe2\\\]/
> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
"http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
Or "curl -g" to disable globbing...
It still can't handle link-local addresses:
$ curl -g 'http://[fe80::230:48ff:fe41:51d5%br0]/'
curl: (6) Could not resolve host: [fe80::230:48ff:fe41:51d5%br0]; Cannot allocate memory
Lynx and Elinks make the request OK but includes the '%br0' in the Host:
header, which lighttpd (at least) answers with "400 Bad Request".
Firefox works (it strips the %br0 from the address before putting it in
the Host: header).
It would appear that the CLI/terminal web client support for IPv6
link-local addresses is lacking.
--
Chris Adams <cmadams(a)hiwaay.net>
Systems and Network Administrator - HiWAAY Internet Services
I don't speak for anybody but myself - that's enough trouble.