The locally configured *. Dev,*.app domain name is always automatically transferred to https in Google browser, resulting in inaccessibility? - Codes Helper

The locally configured . Dev,.app domain name is always automatically transferred to https in Google browser, resulting in inaccessibility?

the ubuntu system I use has installed ipv6-related software;
regardless of whether parsing is done in hosts or not, all * .dev and * .app will be transferred to https!
other browsers access normally, all http, on Google browser;
Web doesn"t work on chrome://net-internals/-sharphsts delete either;
query the .dev suffix in the Query HSTS/PKP domain of the above address:

Found:
static_sts_domain: dev
static_upgrade_mode: FORCE_HTTPS
static_sts_include_subdomains: true
static_sts_observed: 1512450000
static_pkp_domain: 
static_pkp_include_subdomains: 
static_pkp_observed: 
static_spki_hashes: 
dynamic_sts_domain: 
dynamic_upgrade_mode: UNKNOWN
dynamic_sts_include_subdomains: 
dynamic_sts_observed: 
dynamic_sts_expiry: 
dynamic_pkp_domain: 
dynamic_pkp_include_subdomains: 
dynamic_pkp_observed: 
dynamic_pkp_expiry: 
dynamic_spki_hashes:

< H1 > question: how to make * .dev and * .app not jump to https? in chrom < / H1 >

Https chrome

Mar.22,2021

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.

Previous: Gaud adcode search hint

Next: How does http or websocket protocol solve the MTU problem? if you send data directly using a TCP connection, if you exceed the mtu length, you will be divided into multiple groups of data.

The request is http, and the response is indeed https.
localhosthttp,httphttpshttp the local environment is wamp apach2.4.33 the browser is Google 67.0.3396.99 apach has not set the configuration for http to automatically jump to https ...

Https chrome backend frontend apache

Mar.22,2021