blocks|key|99079|text|没有办法阻止Chrome+(>=+63)在.dev域名上使用https。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|99080|谷歌现在拥有官方的.dev+tld，并且已经声明他们不会删除这一功能。|99081|建议将另一个tld用于开发目的，例如.localhost或.test。|99082|有关此更新的更多信息，请访问this+article+by+Mattias+Geniar。|99083|entityMap|0|LINK|mutability|MUTABLE|url|https://ma.ttias.be/chrome-force-dev-domains-https-via-preloaded-hsts/^0|L|4|0|9|4|0|I|A|T|5|0|E|U|0|0^^$0|@$1|2|3|4|5|6|7|T|8|@$9|U|A|V|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|W|8|@$9|X|A|Y|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|Z|8|@$9|10|A|11|B|C]|$9|12|A|13|B|C]]|D|@]|E|$]]|$1|J|3|K|5|6|7|14|8|@]|D|@$9|15|A|16|1|17]]|E|$]]|$1|L|3|-4|5|6|7|18|8|@]|D|@]|E|$]]]|M|$N|$5|O|P|Q|E|$R|S]]]]

There is no way to prevent Chrome (>= 63) form using https on <code>.dev</code> domain names. 
Google now owns the official <code>.dev</code> tld and has already stated that they will not remove this functionality.

The recommendation is to use another tld for development purposes, such as <code>.localhost</code> or <code>.test</code>.

More information about this update can be found in <a href="https://ma.ttias.be/chrome-force-dev-domains-https-via-preloaded-hsts/" rel="noreferrer">this article by Mattias Geniar</a>.

blocks|key|2845756|text|检查该链接|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2845757|https://laravel-news.com/chrome-63-now-forces-dev-domains-https|offset|length|2845758|根据Danny的这篇文章，他建议您使用以下选项之一：“.localhost”、“.invalid”、“.test”或“.example”。|2845759|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|1R|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@]|9|@$D|Q|E|R|1|S]]|A|$]]|$1|F|3|G|5|6|7|T|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|U|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|C]]]]

Check that link

<a href="https://laravel-news.com/chrome-63-now-forces-dev-domains-https" rel="noreferrer">https://laravel-news.com/chrome-63-now-forces-dev-domains-https</a>

Based on this article by Danny Wahl he recommends you use one of the following: “.localhost”, “.invalid”, “.test”, or “.example”.

blocks|key|2845855|text|HTTPSChrome63通过预先加载的强制HTTPS域，很快所有其他浏览器都会效仿。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2845856|.dev+gTLD已被谷歌购买用于内部使用，不能再与http一起使用，只允许使用https。有关进一步的解释，请参阅本文：|2845857|https://ma.ttias.be/chrome-force-dev-domains-https-via-preloaded-hsts/|offset|length|2845858|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|0|1Y|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|Q|8|@]|9|@$F|R|G|S|1|T]]|A|$]]|$1|H|3|-4|5|6|7|U|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|E]]]]

Chrome 63 forces .dev domains to HTTPS via preloaded HSTS
and soon all other browsers will follow.

.dev gTLD has been bought by Google for internal use and can not be used anymore with http, only https is allowed. See this article for further explanations:

<a href="https://ma.ttias.be/chrome-force-dev-domains-https-via-preloaded-hsts/" rel="noreferrer">https://ma.ttias.be/chrome-force-dev-domains-https-via-preloaded-hsts/</a>

blocks|key|2634408|text|此问题无法修复。原因如下：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2634409|2634410|谷歌拥有.dev+gTLD|ordered-list-item|2634411|Chrome在.dev域中直接强制使用HTTPS的源代码。|2634412|2634413|从下面的第二个链接：|2634414|...
//+eTLDs
//+At+the+moment,+this+only+includes+Google-owned+gTLDs,
//+but+other+gTLDs+and+eTLDs+are+welcome+to+preload+if+they+are+interested.
{+"name":+"google",+"include_subdomains":+true,+"mode":+"force-https",+"pins":+"google"+},
{+"name":+"dev",+"include_subdomains":+true,+"mode":+"force-https"+},
{+"name":+"foo",+"include_subdomains":+true,+"mode":+"force-https"+},
{+"name":+"page",+"include_subdomains":+true,+"mode":+"force-https"+},
{+"name":+"app",+"include_subdomains":+true,+"mode":+"force-https"+},
{+"name":+"chrome",+"include_subdomains":+true,+"mode":+"force-https"+},
...|code-block|syntax|javascript|2634415|参考文献|2634416|2634417|ICANN+Wiki+Google|unordered-list-item|offset|length|2634418|Chromium+Source+-+transport_security_state_static.json|2634419|2634420|entityMap|0|LINK|mutability|MUTABLE|url|https://icannwiki.org/Google|1|https://chromium.googlesource.com/chromium/src.git/%2B/63.0.3239.118/net/http/transport_security_state_static.json#255^0|0|0|0|0|0|0|0|0|0|0|H|0|0|0|1I|1|0|0^^$0|@$1|2|3|4|5|6|7|1A|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|1B|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|1C|8|@]|9|@]|A|$]]|$1|F|3|G|5|E|7|1D|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|1E|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|1F|8|@]|9|@]|A|$]]|$1|K|3|L|5|M|7|1G|8|@]|9|@]|A|$N|O]]|$1|P|3|Q|5|6|7|1H|8|@]|9|@]|A|$]]|$1|R|3|-4|5|6|7|1I|8|@]|9|@]|A|$]]|$1|S|3|T|5|U|7|1J|8|@]|9|@$V|1K|W|1L|1|1M]]|A|$]]|$1|X|3|Y|5|U|7|1N|8|@]|9|@$V|1O|W|1P|1|1Q]]|A|$]]|$1|Z|3|-4|5|6|7|1R|8|@]|9|@]|A|$]]|$1|10|3|-4|5|6|7|1S|8|@]|9|@]|A|$]]]|11|$12|$5|13|14|15|A|$16|17]]|18|$5|13|14|15|A|$16|19]]]]

This problem can't be fixed. Below is the reason:

<ol>
<li>Google owns .dev gTLD</li>
<li>Chrome forces HTTP to HTTPS on .dev domain directly within the source code.</li>
</ol>

From the 2nd link below:

<pre><code>...
// eTLDs
// At the moment, this only includes Google-owned gTLDs,
// but other gTLDs and eTLDs are welcome to preload if they are interested.
{ "name": "google", "include_subdomains": true, "mode": "force-https", "pins": "google" },
{ "name": "dev", "include_subdomains": true, "mode": "force-https" },
{ "name": "foo", "include_subdomains": true, "mode": "force-https" },
{ "name": "page", "include_subdomains": true, "mode": "force-https" },
{ "name": "app", "include_subdomains": true, "mode": "force-https" },
{ "name": "chrome", "include_subdomains": true, "mode": "force-https" },
...
</code></pre>

<h3>References</h3>

<ul>
<li><a href="https://icannwiki.org/Google" rel="noreferrer">ICANN Wiki Google</a></li>
<li><a href="https://chromium.googlesource.com/chromium/src.git/+/63.0.3239.118/net/http/transport_security_state_static.json#255" rel="noreferrer">Chromium Source - transport_security_state_static.json</a></li>
</ul>

blocks|key|2845986|text|对于火狐:你可以通过访问address：about:config来禁用属性network.stricttransportsecurity.preloadlist。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|2845987|对于IE来说，它似乎还在工作。|2845988|对于Chrome，没有解决方案，我认为它在源代码中是硬编码的。|2845989|请参阅那篇文章：How+to+prevent+Firefox+and+Chrome+from+forcing+dev+and+foo+domains+to+use+https|2845990|entityMap|0|LINK|mutability|MUTABLE|url|https://tutoref.com/how-to-prevent-firefox-and-chrome-from-forcing-dev-and-foo-domains-to-use-https/^0|K|C|11|17|0|0|0|8|27|0|0^^$0|@$1|2|3|4|5|6|7|T|8|@$9|U|A|V|B|C]|$9|W|A|X|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|Y|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|Z|8|@]|D|@]|E|$]]|$1|J|3|K|5|6|7|10|8|@]|D|@$9|11|A|12|1|13]]|E|$]]|$1|L|3|-4|5|6|7|14|8|@]|D|@]|E|$]]]|M|$N|$5|O|P|Q|E|$R|S]]]]

For Firefox:
you can disable the property network.stricttransportsecurity.preloadlist by visiting the address : about:config .

For IE it seems to be still working .

For Chrome, there is no solution, I think it's hardcoded in the source code.

See that article : <a href="https://tutoref.com/how-to-prevent-firefox-and-chrome-from-forcing-dev-and-foo-domains-to-use-https/" rel="noreferrer">How to prevent Firefox and Chrome from forcing dev and foo domains to use https</a>

blocks|key|2845898|text|MacOS+：在Chrome63通过预加载的HSTS+phpmyadmin在我的mac+stop+works上强制.dev顶级域使用HTTPS之后。我读了this，只是编辑了/etc/apache2/extra/http-vhosts.conf文件：|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|CODE|entityRanges|data|2845899|<VirtualHost+*:80>
++DocumentRoot+"/Users/.../phpMyAdmin-x.y.z"
++ServerName+phpmyadmin.localhost
</VirtualHost>|code-block|syntax|javascript|2845900|然后重启apache+(通过sudo+/usr/sbin/apachectl+stop;+sudo+/usr/sbin/apachectl+start+)-现在它可以在上工作了:)。对于laravel应用程序，解决方案是类似的。|2845901|好的是，当你建立新的项目时，使用*.localhost顶级域名，你可以忘记编辑/etc/hosts。|2845902|多酷啊？:)|2845903|2845904|也有一个很好的建议给add+the+.localhost+domain+as+a+new+standard，这在这里更合适。|blockquote|2845905|2845906|2845907|更新2018|2845908|使用*.localhost并不好-一些应用程序不会支持它，比如cURL+(由php-+here使用)-更多细节here。更好的方法是使用*.local。|2845909|entityMap|0|LINK|mutability|MUTABLE|url|https://ma.ttias.be/chrome-force-dev-domains-https-via-preloaded-hsts/|1|https://datatracker.ietf.org/doc/html/draft-west-let-localhost-be-localhost-06|2|https://stackoverflow.com/questions/48442382/guzzle-exception-with-localhost-domains|3^0|0|6|2F|Z|25|4|0|0|0|E|1P|0|G|B|13|A|0|0|0|A|17|1|0|0|0|0|2|B|1W|7|17|4|2|1J|4|3|0^^$0|@$1|2|3|4|5|6|7|1E|8|@$9|1F|A|1G|B|C]|$9|1H|A|1I|B|D]]|E|@$9|1J|A|1K|1|1L]]|F|$]]|$1|G|3|H|5|I|7|1M|8|@]|E|@]|F|$J|K]]|$1|L|3|M|5|6|7|1N|8|@$9|1O|A|1P|B|D]]|E|@]|F|$]]|$1|N|3|O|5|6|7|1Q|8|@$9|1R|A|1S|B|D]|$9|1T|A|1U|B|D]]|E|@]|F|$]]|$1|P|3|Q|5|6|7|1V|8|@]|E|@]|F|$]]|$1|R|3|-4|5|6|7|1W|8|@]|E|@]|F|$]]|$1|S|3|T|5|U|7|1X|8|@]|E|@$9|1Y|A|1Z|1|20]]|F|$]]|$1|V|3|-4|5|6|7|21|8|@]|E|@]|F|$]]|$1|W|3|-4|5|6|7|22|8|@]|E|@]|F|$]]|$1|X|3|Y|5|6|7|23|8|@]|E|@]|F|$]]|$1|Z|3|10|5|6|7|24|8|@$9|25|A|26|B|D]|$9|27|A|28|B|D]]|E|@$9|29|A|2A|1|2B]|$9|2C|A|2D|1|2E]]|F|$]]|$1|11|3|-4|5|6|7|2F|8|@]|E|@]|F|$]]]|12|$13|$5|14|15|16|F|$17|18]]|19|$5|14|15|16|F|$17|1A]]|1B|$5|14|15|16|F|$17|1C]]|1D|$5|14|15|16|F|$17|1C]]]]

MacOS Sierra, Apache: After Chrome 63 forces .dev top level domains to HTTPS via preloaded HSTS phpmyadmin on my mac stop works. I read <a href="https://ma.ttias.be/chrome-force-dev-domains-https-via-preloaded-hsts/" rel="nofollow noreferrer">this</a> and just edit <code>/etc/apache2/extra/http-vhosts.conf</code> file:
<pre><code>&lt;VirtualHost *:80&gt;
 DocumentRoot &quot;/Users/.../phpMyAdmin-x.y.z&quot;
 ServerName phpmyadmin.localhost
&lt;/VirtualHost&gt;
</code></pre>
and restart apache (by <code>sudo /usr/sbin/apachectl stop; sudo /usr/sbin/apachectl start</code> ) - and now it works on <a href="http://phpmyadmin.localhost" rel="nofollow noreferrer">http://phpmyadmin.localhost</a> :) . For laravel applications solution is similar.
The nice thing is that using <code>*.localhost</code> top level domain when you set up new project you can forget about editing <code>/etc/hosts</code>.
How cool is that? :)
<blockquote>
There's also an excellent proposal to <a href="https://datatracker.ietf.org/doc/html/draft-west-let-localhost-be-localhost-06" rel="nofollow noreferrer">add the .localhost domain as a
new standard</a>, which would be more appropriate here.
</blockquote>
<h2>UPDATE 2018</h2>
Using <code>*.localhost</code> is not good - some applications will not support it like cURL (used by php-guzzle) - more details <a href="https://stackoverflow.com/questions/48442382/guzzle-exception-with-localhost-domains">here</a>. Better is to use <code>*.local</code>.

blocks|key|99129|text|可能值得注意的是，还有其他TLD被强制转换为https：https://chromium.googlesource.com/chromium/src.git/%2B/63.0.3239.118/net/http/transport_security_state_static.json#262|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|99130|google，dev，foo，page，app和chrome。|style|CODE|99131|entityMap|0|LINK|mutability|MUTABLE|url|https://chromium.googlesource.com/chromium/src.git/%2B/63.0.3239.118/net/http/transport_security_state_static.json#262^0|S|38|0|0|0|6|7|3|B|3|F|4|K|3|O|6|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@$A|Q|B|R|1|S]]|C|$]]|$1|D|3|E|5|6|7|T|8|@$A|U|B|V|F|G]|$A|W|B|X|F|G]|$A|Y|B|Z|F|G]|$A|10|B|11|F|G]|$A|12|B|13|F|G]|$A|14|B|15|F|G]]|9|@]|C|$]]|$1|H|3|-4|5|6|7|16|8|@]|9|@]|C|$]]]|I|$J|$5|K|L|M|C|$N|O]]]]

May be worth noticing that there are other TLD that are forced to https: <a href="https://chromium.googlesource.com/chromium/src.git/+/63.0.3239.118/net/http/transport_security_state_static.json#262" rel="nofollow noreferrer">https://chromium.googlesource.com/chromium/src.git/+/63.0.3239.118/net/http/transport_security_state_static.json#262</a>

<code>google</code>, <code>dev</code>, <code>foo</code>, <code>page</code>, <code>app</code> and <code>chrome</code> right now.

Suddenly Google Chrome redirects my virtual-host domain myapplication.dev to <a href="https://myapplication.dev" rel="noreferrer">https://myapplication.dev</a>. I already tried to go to 

<blockquote>
 chrome://net-internals/#hsts
</blockquote>

And enter myapplication.dev into the textbox at the very bottom "Delete domain security policies" but this had no effect.

I also tried to delete the browser data.

What I also did is to change the v-host to .app instead of .dev but Chrome still redirected me to https:// ... 

It's a Laravel application running on Laragon.
On other PCs in the same network, it works perfectly.

Chrome redirects .dev to https

虚拟主机

MacOS

突然，Google Chrome将我的虚拟主机域名myapplication.dev重定向到。我已经试着去 chrome://net-internals/#hst并在最底部的“Delete域安全策略”文本框中输入myapplication.dev，但这没有任何效果。我还尝试删除了浏览器数据。我还将v-host改为.app，而不是.dev，但Chrome仍然将我重定向到https:// ...这是一

问Chrome将.dev重定向到https
EN

回答 7

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Chrome将.dev重定向到httpsEN

回答 7

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Chrome将.dev重定向到https
EN