because Chrome has upgraded its browser version to 63 today, all .dev
and .app
will automatically transfer HTTP
to HTTPS
, because Google has taken down the top-level domain of .dev
; the upcoming problems of .dev
have been explained in the September report. At present, the only way is to change your .dev
or .app
domain name, or change it to Firefox. It is recommended to change your domain name to .test
or .localhost
Chrome upgrade related solution
has been working all morning and almost got into it all day.
Welcome to use this gadget to self-sign the pan-domain name certificate to facilitate local developers / local area networks:
https://github.com/Fishdrowne.
anyway, https is the mainstream in the future, so consider it an opportunity to learn to use https
I have no choice but to upgrade Chrome 63. There seems to be no other way but to change the suffix.
I have replaced .app with .lara now.
I can only say that I, who is also the victim, wept silently when I saw this post. I thought my dnsmasq would fail.
I rely on me, and I am also a victim. What to do now
Real Japanese Dog
means that I also suffer from it. I always thought it was the firewall and nginx of my computer. Later, I changed other browsers to open it, knowing only that it was a google problem. The real reason is that Google has acquired the top-level domain name of .dev. And keep doing chrome://net-internals/-sharphsts; thank you
so
dev.alibababbabab.com
I am also a victim
how disgusting! Google
this is really disgusting. I just adjusted it myself for a long time, and now I have to go back and change the domain name
. I've wasted half an hour. MMP's Google
has been popular for more than a few days.