Released on February 4, 2020, Google Chrome’s latest version (v80) now blocks mixed content loaded via HTTP. It has suddenly caused audio and videos, loaded over insecure HTTP connections, to stop loading automatically on HTTPS-secured sites.
Many radio broadcasters have suddenly found that their stream players are not playing back HTTP audio streams since the browser views the connections as insecure.
Here is all you need to know about this latest turn of events and why you should not worry when broadcasting with CloudRadio.
Official Google Statement
Thursday, October 3, 2019
Today we’re announcing that Chrome will gradually start ensuring that https:// pages can only load secure https:// subresources. In a series of steps outlined below, we’ll start blocking mixed content (insecure http:// subresources on https:// pages) by default. This change will improve user privacy and security on the web, and present a clearer browser security UX to users.
In Chrome 80, mixed audio and video resources will be autoupgraded to https://, and Chrome will block them by default if they fail to load over https://. Chrome 80 will be released to early release channels in January 2020. Users can unblock affected audio and video resources with the setting described above"
Are you hosting with CloudRadio? Just enable HTTPS for your player
If you’re hosting your radio station with CloudRadio, you don’t have to panic about your stream player not working on Chrome.
Just enable the HTTPS proxy.
To do so, simply go to the console, and navigate to Listen > Player > Toggle On Enable HTTPS.
Read more on how the HTTPS proxy works: https://help.cloudrad.io/s/article/player-https-proxy
Do you host your radio with another company, but use our free player?
You can make your audio stream compatible with Chrome 80 and future versions by also turning on the free HTTP proxy from your console dashboard.
Note that we provide this service on a best effort basis and that we might restrict its usage at any time.
We recommend hosting your radio station with us if your radio host doesn't provide a HTTPS secure stream.
It's the best way to ensure that your stream will be compatible with future versions of Chrome like the upcoming Chrome 81. You'll also enjoy other benefits like:
Other changes that come with Chrome 80
- SameSite cookie changes (Read more: https://blog.chromium.org/2019/10/developers-get-ready-for-new.html)
- Quieter notification permission UI (Find out more: https://blog.chromium.org/2020/01/introducing-quieter-permission-ui-for.html)
Start your internet radio with us
We offer two excellent options. It’s easy to get started.