Google Chrome update makes HTTPS the default for incomplete URLs

[Hypersot]

I know most of you probably know this but still:

https://www.techradar.com/news/google-chrome-is-making-https-the-default-for-incomplete-urls

I can't even imagine the impact this will have onto parking if there are no steps taken from the parking services to implement certificates to as many domains as possible.

 

[BrandingGo]

Why do you use Chrome?

Checkout this https://mobile.twitter.com/DuckDuckGo/status/1371509053613084679

 

[noneisnone]

so if i type google.com i would be redirected for https://google.com instead of http://google.com ? what about small sites without ssl certificate ?

 

[alcy]

Why do you use Chrome?

Checkout this https://mobile.twitter.com/DuckDuckGo/status/1371509053613084679

I think people who dont use chrome have no clue about browsers..

 

[noneisnone]

@alcy i don't use chrome because i can't afford enough ram to keep it running.

 

[Hypersot]

@matt_bodis

I recently got a .app domain just to see how, what is mentioned on the Blog, works regarding https.

I have set Bodis' NS, waited for the NS to fully propagate and then I started visiting the domain a few times (with about an hour between each visit) to see when the domain would get the cert.

For the past few hours I'm visiting the domain and I still get the ERR_SSL_PROTOCOL error.

How long should I wait to see if this works or.. have I understood this whole thing totally wrong?

thanks

 

[matt_bodis]

Hi Hypersot,

We have an unusually large queue of domains today, hence why. It should catch up eventually. If it still hasn't caught up in 24 hrs please let us know.

Typically though it'd be a few minutes.

We've made some improvements but the next step will be DNS wild card / resolving without the first visit. We're working on this.

 

[Future Sensors]

We've made some improvements but the next step will be DNS wild card / resolving without the first visit. We're working on this.

Hi @matt_bodis

This is very positive news. It was in fact the main reason I stopped using the DAN-Bodis integration a while back.

 

[Hypersot]

If it still hasn't caught up in 24 hrs please let us know.

it's been ~2 days and domain still doesn't resolve.

 

[Hypersot]

@matt_bodis
4 days and still nothing. I can't imagine how much traffic is lost if this happens on other domains too.

Will DM you.

 

[matt_bodis]

Hi Hypersot,

We're backed up by a few million domains at this time. I am sorry for not letting you know earlier. It is just a once occurence.

Once it catches up (and we implement on DNS) the issue will be resolved. Sorry for the troubles.

 

[Hypersot]

@matt_bodis

that's no trouble at all. The point in purchasing that domain was to have an understanding how (and, more importantly, if) the https works.

Do you plan to have a public announcement when you are fully ready to accept domains with https traffic and for them to work as intended?

thanks for replying

 

[matt_bodis]

It def works, we now resolve HTTPS on over 9M domains.

There's various levels of integrations.

The next step is DNS which probably will solve most these issues.

Sorry for the inconvenience.

We'll announce DNS soon.

 

[Sutruk]

From Chromium Blog:

A safer default for navigation: HTTPS

https://blog.chromium.org/2021/03/a-safer-default-for-navigation-https.html


"For sites that don’t yet support HTTPS, Chrome will fall back to HTTP when the HTTPS attempt fails (including when there are certificate errors, such as name mismatch or untrusted self-signed certificate, or connection errors, such as DNS resolution failure)."