Shortest URLs on the Internet
11–20 of 208 posts
Re: Shortest URLs on the Internet
#12Close second: http://1.1
Why does 1.1 resolve to 1.0.0.1? I don't recall this being in any of the documents about CIDRs. Are browsers implicitly mapping IPv4 addresses temporarily into IPv6 addresses during parsing, such that "1.1" becomes "1::1", and then gets IPv6 abbreviated-form expansion applied to it?
% curl 'http://1.1/'
error code: 1003
while curl 7.85.0 (Release-Date: 2022-08-31, on FreeBSD) says: % curl 'http://1.1/'
301 Moved Permanently
301 Moved Permanently
cloudflare
Re: Shortest URLs on the Internet
#13Close second: http://1.1
Why does 1.1 resolve to 1.0.0.1? I don't recall this being in any of the documents about CIDRs. Are browsers implicitly mapping IPv4 addresses temporarily into IPv6 addresses during parsing, such that "1.1" becomes "1::1", and then gets IPv6 abbreviated-form expansion applied to it?
TL;DR: the second "1" in "1.1" is treated as a 24-bit integer.
Longer explanation: https://blog.dave.tf/post/ip-addr-parsing/
Re: Shortest URLs on the Internet
#14Close second: http://1.1
Why does 1.1 resolve to 1.0.0.1? I don't recall this being in any of the documents about CIDRs. Are browsers implicitly mapping IPv4 addresses temporarily into IPv6 addresses during parsing, such that "1.1" becomes "1::1", and then gets IPv6 abbreviated-form expansion applied to it?
> IPv4 addresses may be represented in any notation expressing a 32-bit integer value.
I remember reading a man page that explained this really succinctly but I cannot remember which one it was. A tool like ping I believe.
Re: Shortest URLs on the Internet
#15Close second: http://1.1
Why does 1.1 resolve to 1.0.0.1? I don't recall this being in any of the documents about CIDRs. Are browsers implicitly mapping IPv4 addresses temporarily into IPv6 addresses during parsing, such that "1.1" becomes "1::1", and then gets IPv6 abbreviated-form expansion applied to it?
Re: Shortest URLs on the Internet
#16Re: Shortest URLs on the Internet
#17Earlier quoted context omitted.
Why does 1.1 resolve to 1.0.0.1? I don't recall this being in any of the documents about CIDRs. Are browsers implicitly mapping IPv4 addresses temporarily into IPv6 addresses during parsing, such that "1.1" becomes "1::1", and then gets IPv6 abbreviated-form expansion applied to it?
I suspect it gets mapped to 1.0.0.1 because no other resolution is possible. Any other locations for the two zeros results in an invalid IP (either starting or ending in 0).
Re: Shortest URLs on the Internet
#18Earlier quoted context omitted.
Why does 1.1 resolve to 1.0.0.1? I don't recall this being in any of the documents about CIDRs. Are browsers implicitly mapping IPv4 addresses temporarily into IPv6 addresses during parsing, such that "1.1" becomes "1::1", and then gets IPv6 abbreviated-form expansion applied to it?
I'm also curious. Especially since curl 7.64.1 (Release-Date: 2019-03-27, on macOS) says: % curl 'http://1.1/' error code: 1003 while curl 7.85.0 (Release-Date: 2022-08-31, on FreeBSD) says: % curl 'http://1.1/' 301 Moved Permanently 301 Moved Permanently cloudflare