.localhost Domains
inclouds.space
.localhost Domains
1–10 of 212 posts
Re: .localhost Domains
#2[deleted]
Re: .localhost Domains
#3[deleted]
Re: .localhost Domains
#4I use .localhost for all my projects. Just one annoying note: Safari doesn't recognize the TLD localhost so it will try to perform a search. Adding a slash at the end will fix this; ie example.localhost/
Re: .localhost Domains
#5Avoid using `.local`. In my experience Chrome does not like it with HTTPS. It takes much much longer to resolve. I found a Chrome bug relating to this but do not have it handy to share. `.localhost` makes more sense for local development anyways.
Re: .localhost Domains
#6Once again, .local should _never_ have been assigned to any organization. Just like .lan should also be reserved like the private IP blocks.
Re: .localhost Domains
#7People used localtest.me back in the days :)
https://weblogs.asp.net/owscott/introducing-testing-domain-l...
Re: .localhost Domains
#8Wow! Today I learned that you can have subdomains of localhost. Never realized it!
Re: .localhost Domains
#9Avoid using `.local`. In my experience Chrome does not like it with HTTPS. It takes much much longer to resolve. I found a Chrome bug relating to this but do not have it handy to share. `.localhost` makes more sense for local development anyways.
Actually, MacOS gives your computer a .local domain on DHCP and Bonjour usually
Re: .localhost Domains
#10I 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.