Chrome will block http-Content by February 2020

[Marc]

If ya don't know it yet, Google's Chrome browser will block all http:// pages up to February 2020 in various steps.

Particularly affected are the http:// subresources, which are loaded on https:// pages. Google calls them "mixed content" pages. Anyone who uses a mixture of these transmission protocols so far must switch to the more secure https:// by February 2020. Otherwise, s/he risks that Google Chrome will no longer show her/his pages.

For more information see various sources on the net, e.g.:
Chrome to Block HTTPS/HTTP Mixed Content by February 2020
Chrome will block HTTP content from loading on secure sites

 

[Graybeard]

This was coming ...
What's new is the DNS over HTTPS - Wikipedia
DNS over HTTPS (DoH) Chrome will first use DoH where available -- of course, Google DNS will be DoH and may become the default in cases where your ISP DNS is not DoH. What does this mean, Google may know where you connect rather than your ISP.
Is this about your security or you as the "product?"

 

[azgold]

I never use Chrome personally and I let my six year old site and domain go last month, so I'm not concerned about it. However, it never ceases to amaze me at how often things change when it comes to G. Pain in the butt sometimes.

Is this about your security or you as the "product?"

I'd like to think the former but I believe the latter.

 

[Marc]

I never use Chrome personally ...

Think of your customers, maybe they use the fast chrome-browser ...

 

[Graybeard]

I maintain maybe 40 domain/sub-domain SSL (TLS) certs from Let's Encrypt.
the certs are free from the EFF but they expire every 90 days and for reason of my virtial server configurations I need to update them manually. So, it is time consuming and many of the public websites have no data that really needs to be secure.

For someone with a simple landing page or a blog what do you really need a SSL domain for? Because of Edward Snowden and Google's interpretation of the Existential and Imminent Dangers! It's a lot of added work and uncompensated time.

It gets worse; the US Congress is considering privacy legislation to parallel the California Privacy Act and the EU GDRP Directive. So we will have more uncompensated time constructing compliant policies for our websites. You can thank Facebook, Google, DoubleClick, remarketing ads ... Ad Blockers as well as browser blocking of tracker pixel, cookies and beacons where just a symptomatic band-aid ...

Personally, I am designing non cookie platforms now and hidden server tracking. Many affiliate deals will be trashed on any cookie-return conversions -- be forewarned ...

 

[Graybeard]

Exactly. Edge will be built on Chromium soon like the Google Chrome is built on Chromium browser [open source code] now -- that is like 2/3 of the browser share

What the parallel browser policies will be IDK. However, this does not look good in general for affiliates and referral tracking apart from the HTTP/HTTPS issues ...