←back to thread

.localhost Domains

(inclouds.space)
301 points todsacerdoti | 1 comments | | HN request time: 0.212s | source
Show context
mohsen1 ◴[] No.43644362[source]
Avoid 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.
replies(8): >>43644412 #>>43644418 #>>43644420 #>>43644480 #>>43644481 #>>43644511 #>>43644548 #>>43646934 #
Pxtl ◴[] No.43644548[source]
Honestly, if I had my druthers there would be a standardized exception for .local domains that self-signed HTTPS certs would be accepted without known roots. It's insane how there's no good workflow for HTTPS on LAN-only services.
replies(2): >>43644623 #>>43644673 #
Spooky23 ◴[] No.43644623[source]
It’s actually gotten worse, you need to run a CA or use a public domain where it’s easy to get your internal naming schemes in a transparency log.
replies(1): >>43644769 #
1. jeroenhd ◴[] No.43644769[source]
The easy workaround I've seen companies use for that is by using a basic wildcard certificate (*.local.mydomain.biz).