If you, like me, are using *.dev as your local TLD then you’re going to be affected by an Chrome update in the next release. The next release will force the browser to switch to https automatically on the .dev domains. Annoying, yes, but let’s face it…. if you’re doing local dev and pushing to a live site then it’s probably time you set up both sites with SSL anyway (it’s certainly forced me to do the same).
Wait, there’s a legit .dev gTLD?
It’s been bought by Google as one of their 100+ new gTLDs. What do they use it for? No clue. But it’s going to cause a fair bit of confusion and pain to webdevelopers.
The .dev gTLD has nameservers and is basically like any other TLD out there, we as developers just happen to have chosen that name as a good placeholder for local development, too, overwriting the public DNS.An excerpt from Chrome to force .dev domains to HTTPS via preloaded HSTS