W3C home > Mailing lists > Public > whatwg@whatwg.org > June 2015

Re: [whatwg] IPv4 parsing

From: Tim Streater <tim@clothears.org.uk>
Date: 24 Jun 2015 21:50 +0100
To: Peter Kasting <pkasting@google.com>, Tab Atkins Jr. <jackalmage@gmail.com>
Message-Id: <E1Z7rcY-0007Dj-NZ@mailscan5.hi.local>
Cc: timeless <timeless@gmail.com>, Alexey Proskuryakov <ap@webkit.org>, David Walp <David.Walp@microsoft.com>, WHATWG <whatwg@whatwg.org>, Mike West <mkwst@google.com>, Ryan Sleevi <sleevi@google.com>, Valentin Gosu <valentin.gosu@gmail.com>
On 24 Jun 2015 at 20:15, Peter Kasting <pkasting@google.com> wrote: 

> How Chrome's omnibox handles this (which I think is compliant with most
> other places):
>
> If there are no dots in the middle of the expression, the number is
> converted to powers-of-256 format and leading 0s are prepended to reach
> four octets:
>
> 66 = 0.0.0.66
> 256 = 0.0.1.0
>
> If there are dots in the middle, the number after the last dot is treated
> as above, while the numbers before the dots must satisfy 0 <= n <= 255 and
> are placed into the highest octets in order:
>
> 1.66 = 1.0.0.66
> 1.256 = 1.0.1.0
> 1.2.66 = 1.2.0.66
> 1.256.66 = invalid

This makes no sense at all.

--
Cheers  --  Tim
Received on Wednesday, 24 June 2015 20:50:42 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 17:00:33 UTC