[whatwg] URL: IPv6 parsing and model/serializing
Anne van Kesteren
annevk at annevk.nl
Wed Nov 14 10:35:57 PST 2012
* Opera does not appear to support IPv4 addresses in the parser, is
that intentional? Putting http://[fd::220.127.116.11]/ in <a> gives protocol
opera: and pathname illegal-url-... href returns the input.
* Chrome supports "IPv4-like" syntax no other browser supports, e.g.
http://[::129.144.52]/ (missing fourth IPv4 component). I do not plan
on allowing that.
* All browsers lowercase. http://[FFFF::]/ -> http://[ffff::]/
* Chrome normalizes IPv4 away. I kinda a like that, but wonder if it's
problematic? http://[fD::18.104.22.168]/ -> http://[fd::202:304]/
* Chrome follows http://tools.ietf.org/html/rfc5952#section-4 but no
other browser does. I think it makes sense to follow Chrome here.
Chrome's implementation (except for parsing invalid IPv4) makes a lot
of sense I think as it allows for minimizing what needs to be stored
internally. It only requires a sequence of eight 16-bit components.
More information about the whatwg