thehighhomie2017-12-07 08:57:48
thehighhomie, 2017-12-07 08:57:48

After the update, chrome began to redirect apache domains to https protocol?

Today I updated chrome and it began to open Apache sites in the https protocol, cleared the cache, reinstalled chrome, and all to no avail. In the fox, everything is fine, but in chrome and reset everything, nothing helps.
Redirects even sites where there is no .htaccess, just 1 index.php file with "Hello Wordl!

Answer the question

In order to leave comments, you need to log in

3 answer(s)
Maxim Kudryavtsev, 2017-12-07

I ran into the same problem after typing in the morning apt update && apt -y full-upgrade
My development environment deployed on Docker containers, i.e. MySQL works in one, nginx in the second, php-fpm in the third. To access the container from the host OS, I used the host.dev domain. After updating Google Chrome to version 63.0.3239.84 (Official Build) (64-bit)07-12-2017, my developer domain stopped working, and only in Chrome. In Firefox everything is OK
Began to dig. The first thing I came across was this post on Stackoverflow Google Chrome redirecting localhost to https . The answer from BigJump, marked with the solution , is not our case, however, I was hooked by his note about HSTS, so just in case, I added the following to my nginx config:

server {
    add_header Strict-Transport-Security "max-age=0;";

I scroll down a little, the same question and see a wonderful answer from rafawhs . It turns out that the zone .devis a new gTLD that is now owned by Google . This is what is the root. Google Chrome is a browser from Google, in which they added a restriction ERR_ICANN_NAME_COLLISION, due to which no domain that has a zone .devfrom my local server will now work. Other browsers, in particular FireFox, have apparently not caught up yet, however, I think that this is only a matter of time.
At the time of this writing, this issue only occurs in Google Chrome from 63.0.3239.84. I had Chrome version 61 on my netbook, there is no restriction ERR_ICANN_NAME_COLLISIONon domains .devfrom the local server.
I solved the problem simply by opening /etc/hostsand changing host.devto host.ld, which is currently not a gTLD zone. I corrected the domain name in the application settings and now everything works for me again.

Maxim Fedorov, 2018-01-20

.dev domains in Chrome are being force redirected to...

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question