Fun fact: Because port numbers are reserved per IP address in OS routing tables, you can bind virtually unlimited instances of a server on localhost IPs to the same port number as long as you are careful not to bind to all IPs. Only works on IPv4 but is an extremely useful feature. IPv6 only has one reserved localhost IP, which is extremely limiting. I guess IANA/IETF didn't want to reserve a full /64 for localhost but also didn't want to fix the limited port numbers issue in TCP either. So we get the worst of both worlds in pure IPv6. :( At least IPv4 to IPv6 bridging works fine.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Someone needs to make a pedantic version of that floor mat that says:
"There's no place like 127.0.0.0/8"
And also various "calculator words" versions of the floor mat:
"There's no place like 127.1.33.7"
Fun fact: Because port numbers are reserved per IP address in OS routing tables, you can bind virtually unlimited instances of a server on localhost IPs to the same port number as long as you are careful not to bind to all IPs. Only works on IPv4 but is an extremely useful feature. IPv6 only has one reserved localhost IP, which is extremely limiting. I guess IANA/IETF didn't want to reserve a full /64 for localhost but also didn't want to fix the limited port numbers issue in TCP either. So we get the worst of both worlds in pure IPv6. :( At least IPv4 to IPv6 bridging works fine.