- Impact
- 21,788
Wondering why your internal .dev web app has stopped working?
Blame Google. And ICANN
Blame Google. And ICANN
Source: http://www.theregister.co.uk/2017/11/29/google_dev_network/Network admins, code wranglers and other techies have hit an unusual problem this week: their test and development environments have vanished.
Rather than connecting to private stuff on an internal .dev domain to pick up where they left off, a number of engineers and sysadmins are facing an error message in their web browser complaining it is "unable to provide a secure connection."
How come? It's thanks to a recent commit to Chromium that has been included in the latest version of Google Chrome. As developers update their browsers, they may find themselves booted out their own systems.
Under the commit, Chrome forces connections to all domains ending in .dev (as well as .foo) to use HTTPS via a HTTP Strict Transport Security (HSTS) header. This is part of Google's larger and welcome push for HTTPS to be used everywhere for greater security. Essentially, you have to use HTTPS to connect to .dev websites, and if you haven't bothered configuring secure HTTP on your internal .dev work servers, your browser won't connect.
...
