←back to thread

.localhost Domains

(inclouds.space)
301 points todsacerdoti | 1 comments | 10 Apr 25 14:19 UTC | HN request time: 0.209s | source
Show context
andrewstuart2 ◴[10 Apr 25 14:53 UTC] No.43644417[source]▶
I haven't done it for a while (I've mostly just used 127.*), but I found the best one to use for dev purposes was the IETF-reserved `.test` TLD [0]. The main benefit at the time I was messing with this (10ish years ago now) was that all the browsers I needed to test on would actually attempt to resolve `.test`. If I remember correctly, firefox seemed to have issues with `localhost` being anything other than 127.0.0.1 (and would simply go to that address ignoring whatever was in /etc/hosts or DNS, again IIRC). It's been a while, though, so that behavior might have changed.

[0] https://datatracker.ietf.org/doc/rfc2606/

replies(2): >>43644554 #>>43644569 #
1. lima ◴[10 Apr 25 15:04 UTC] No.43644569[source]▶
For development, "localhost" has a convenience bonus: it has special treatment in browsers. Many browser APIs like Service Workers are only available on pages with a valid WebPKI cert, except for localhost.