4 ms·
> Keeping in mind that 127.0.0.1 is not the only loopback address at your disposal – you have the whole /8. Tell that to Google Chrome developers, who are so a
by pwdisswordfishc 3y ago
> Keeping in mind that 127.0.0.1 is not the only loopback address at your disposal – you have the whole /8.
Tell that to Google Chrome developers, who are so arrogant they think they know better than the operating system, and force-resolve *.localhost. to 127.0.0.1
- loloquwowndueo 3y agoThen use a non-brain dead browser :)
- yrro 3y agoLooks like someone might have been trying to prepare the ground for a hijack of 127.0.0.0/8...
- bluejekyll 3y ago‘The ".localhost" TLD has traditionally been statically defined in host DNS implementations as having an A record pointing to the loop back IP address and is reserved for such use. Any other use would conflict with widely deployed code which assumes this use.’ Reading that sentence implies a single loop back address. I appreciate that IPv6 “fixed” this confusion by having a single loop back address of ::1. While you are correct that IPv4 reserved the entire /8 in practice the expectation is generally that 127.0.0.1 is the loopback address, and using other addresses in the 127/8 space tends to lead to unexpected issues across many pieces of software. The intention of the .localhost domain is to ensure that DNS resolutions never resolves to something external, for security reasons. See also, RFC 5735: “… This is ordinarily implemented using only 127.0.0.1/32 for loopback.” — https://datatracker.ietf.org/doc/html/rfc5735 https://datatracker.ietf.org/doc/html/rfc5735