Use a .dev domain? Not anymore (medium.engineering)

10 points by xm 8y ago ↗ HN

5 comments

[ 1.2 ms ] story [ 16.2 ms ] thread

Heh... I remember having an internal dns server with zone files for a whole bunch of internal servers using $our-real-domain-name.local as dupes of $our-real-domain-name.com. Then an early OSX upgrade brought in Rendezvous/Bonjour in maybe '02 or '03 - and all the Macs stopped being able to find the local machines... (And the sysadmin who'd set it all up didn't believe the problem reports at first, 'cause her CentOS machine were still working just fine.)

jaredcwhite 8y ago ↗

Great explanation. But I use Safari for development so probably no need to change for the time being. :)

jaredcwhite 8y ago ↗

Hmm, I stand corrected. Just upgraded to the latest macOS High Sierra, and it appears that Safari is automatically redirecting http to https for .dev. I changed a local dev domain in my hosts file to .dew and it started working via http again.

[dead] mofino 8y ago ↗

TLDR. Why are the Chrome devs deciding who should be secured and who shouldn't? I suspect a fork will be made sooner than later.

TonnyGaric 8y ago ↗

Well, this reminds me of the following article I just read: "Please build websites for the web, not just Google Chrome." — https://thenextweb.com/dd/2017/11/28/please-build-websites-w...