[Webkit-unassigned] [Bug 11773] IPv6 addresses with interface don't do anything when clicked

[bugzilla-daemon at webkit.org]

http://bugs.webkit.org/show_bug.cgi?id=11773


bdash at webkit.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |bdash at webkit.org




------- Comment #1 from bdash at webkit.org  2006-12-11 18:04 PDT -------
I've done a little digging into this case: the reason the link has no effect is
that KURL::parse decides the URL is invalid due to the presence of non-IPv6
address characters inside the hostname portion of the URL (the invalid
characters being "%en0").  The reason why these are considered invalid is
somewhat interesting...  RFC 2732, Format for Literal IPv6 Addresses in URL's,
(<http://www.faqs.org/rfcs/rfc2732.html>) changes the host portion of the URL
syntax to:

      host          = hostname | IPv4address | IPv6reference
      ipv6reference = "[" IPv6address "]"

where IPv6address is defined over in RFC 2373, IP Version 6 Addressing
Architecture (<http://www.faqs.org/rfcs/rfc2373.html>).  It's definition is:

      IPv6address = hexpart [ ":" IPv4address ]
      IPv4address = 1*3DIGIT "." 1*3DIGIT "." 1*3DIGIT "." 1*3DIGIT

      IPv6prefix  = hexpart "/" 1*2DIGIT

      hexpart = hexseq | hexseq "::" [ hexseq ] | "::" [ hexseq ]
      hexseq  = hex4 *( ":" hex4)
      hex4    = 1*4HEXDIG

which is, more or less, a colon-delimited sequence of hexadecimal digits.  It
makes no allowance for the scoped address format.  The scoped address format is
introduced in RFC 4007, IPv6 Scoped Address Architecture
(<http://www.faqs.org/rfcs/rfc4007.html>), and optionally append a percent
character followed by an arbitrary zone identifier to the end of an IPv6
literal address.  Unfortunately in section 11.7 it says:

   [T]his document does not specify how the format for non-global
   addresses should be combined with the preferred format for literal
   IPv6 addresses.  In any case, it is recommended to use an FQDN
   instead of a literal IPv6 address in a URL, whenever an FQDN is
   available.

So in summary, the scoped address format appears to be totally unspecified when
used in the context of a URL.

Recent builds of Firefox also appear to have issues with URLs of this format,
attempting to treat them as a hostname to be resolved.  This leads to a "host
not found" error being displayed, which is misleading but in many ways more
useful than ignoring the mouse click like WebKit currently does.  It's not
obvious whether the loader code that is used to load pages will function
correctly in the presence of the scoped address, or whether this would also
need addressed at other levels.


-- 
Configure bugmail: http://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.