Well, I know virtually nothing about IPv6, but that "%eth2" looks like it's
part of the target host address, seeing as it comes before the ":8080" port
number. Could it be as simple as "send this out via the eth2 interface"??
If so,I suppose when converting the string to a binary IPv6 address, you
need to somehow attach routing to make sure it goes through eth2.

Would the % need to be escaped at all?? I wouldn't expect it to reach the
target if it's specifying routing.

Just my $0.02, in case it inspires someone else... :)

Ralph Mitchell

On 12/1/05, Daniel Stenberg <daniel_at_haxx.se> wrote:
>
> Hey
>
> We got this anonymous bug report claiming we aren't RFC2732 compliant in
> regard to IPv6 numerical addresses in URLs:
>
> http://curl.haxx.se/bug/view.cgi?id=1371118
>
> The report says we don't support "zone IDs" and it claims you can use URLs
> like this in Firefox:
>
> http://[fe80::2e0:81ff:fe28:d04c%eth2]:8080/
>
> (Note the %eth2 thing)
>
> I just read RFC2732 and RFC3986 without seeing "the light". The latter
> claims:
> "This syntax does not support IPv6 scoped addressing zone identifiers".
>
> Now, is there anyone with some facts or opinions on this matter?
>
> Supporting '%eth2' as a literal in the URL is truly horrible, but if
> Firefox
> does it, it might be reason enough for us to do it (% is a reserved
> character
> in URLs and should be used as '%25').
>
> What are we supposed to do with the '%eth2' part when we convert the
> string to
> a binary IPv6 address?
>
> --
> Commercial curl and libcurl Technical Support: http://haxx.se/curl.html
>
Received on 2005-12-02