Live data from Hacker News

https://16777217/

1.0.0.1

21–30 of 90 posts

Re: https://16777217/

#22

  $ man 3 inet_aton

  […]

   inet_aton() converts the Internet host address cp from the IPv4
   numbers-and-dots notation into binary form (in network byte order)
   and stores it in the structure that inp points to.  inet_aton()
   returns nonzero if the address is valid, zero if not.  The address
   supplied in cp can have one of the following forms:

   a.b.c.d   Each of the four numeric parts specifies a byte  of  the
             address;  the bytes are assigned in left-to-right order
             to produce the binary address.

   a.b.c     Parts a and b specify the first two bytes of the  binary
             address.   Part c is interpreted as a 16-bit value that
             defines the rightmost two bytes of the binary address.
             This notation is  suitable  for  specifying  (outmoded)
             Class B network addresses.

   a.b       Part a specifies the first byte of the binary address.
             Part b is interpreted as a 24-bit value that defines the
             rightmost three bytes of the binary address.  This
             notation is suitable for specifying (outmoded) Class A
             network addresses.

   a         The  value  a is interpreted as a 32-bit value that is
             stored directly into the binary address without any byte
             rearrangement.

   In all of the above forms, components of the dotted address can be
   specified in decimal, octal (with a leading 0), or hexadecimal,
   with a leading 0X).  Addresses in any of these forms are
   collectively termed IPV4 numbers-and-dots notation.  The form that
   uses exactly four decimal numbers is referred to as IPv4 dotted-
   decimal notation (or sometimes: IPv4 dotted-quad notation).
https://manpages.debian.org/stable/manpages-dev/inet_aton.3....

Re: https://16777217/

#27

Not working in FF (Desktop stable, win)

there's a dot at the end of the url when you click on it which breaks it

https://1.0.0.1. works though, so the question is why a final period works for traditionally formatted IPv4 addresses (uint8.uint8.uint8.uint8), but not those formatted as a plain old uint32. If I wasn't jetlagged and a tad drunk I'd dig into it a bit.

I do wonder if there's a typo in the URL that OP intended, because the title is "https://16777217/" whereas the URL is "https://16777217." and . and / are only a key away from each other (at least on my IE/UK ISO layout).

Re: https://16777217/

#30
post #27

Earlier quoted context omitted.

there's a dot at the end of the url when you click on it which breaks it

https://1.0.0.1 . works though, so the question is why a final period works for traditionally formatted IPv4 addresses (uint8.uint8.uint8.uint8), but not those formatted as a plain old uint32. If I wasn't jetlagged and a tad drunk I'd dig into it a bit. I do wonder if there's a typo in the URL that OP intended, because the title is " https://16777217/ " whereas the URL is " https://16777217 ." and . and / are only a…

I had to add the trailing period for HN to accept it as a valid URL. However, for me (using Chrome on macOS Monterey), Chrome ignores the period and renders it as "https://16777217/". I thought it would be the same on other browsers. Interesting.
Post reply on HN