6

From last update of Google Chrome 63.0.3239.84 the .dev domain of my local development machine does not work anymore becouse the browser force URL over https and I do not have a sicure certificate on my local machine. Is there a way to make it work with .dev?

I do not want to use other domains like .local or .test

I tried to enable/disable this chrome://flags/#allow-insecure-localhost but nothing.

Alberto Favaro
  • 1,824
  • 3
  • 21
  • 46
  • Yes, you can create a self-signed certificate for yourdomain.dev and make your OS and browser trust it. Then it will work. – Liga Nov 22 '19 at 13:24

2 Answers2

5

You shouldn't change it.

Since 1999 that the Network Working Group(NWG) wrote a memorandum listing the safe Top Level Domains(TLDs) for development.
Choose one of that list to have a future-proof solution.

Because some developers depend on some tools with this poor approach - I was one of them - you can use a hack to solve this: write badidea when the HSTS warning pops up.

Use this only as a temporary solution and dedicate your time upgrading, or helping upgrade, your tools.

EDIT: Other solutions here.

Community
  • 1
  • 1
Narayon
  • 415
  • 3
  • 12
2

No, there is no workaround to make .dev work in Chrome; it now belongs to Google.

https://laravel-news.com/chrome-63-now-forces-dev-domains-https

darylknight
  • 233
  • 1
  • 3
  • 12