Mixed Content (http/https problem)

dmkroslindale

Vivaldi 3.1.1929.45 (Stable channel) (64-bit)
Revision 1eb3263017ed42270818939fbff241845938a81f
OS Windows 10 OS Version 1909 (Build 18363.900)

I visit a page with mixed content. https://atosradio.org/atosradio/landings.html

While the page itself is https (secure) the embedded player of music is not. The stream server does not support https. The result is that when you click on the player it will not load. You will read on that page that this is a known issue and that it can be fixed in the Settings area of some Chrome browsers.

Google Chrome and Edge Chrome have settings to over-ride the blocked content. I cannot find such a setting on Vivaldi. Is this available and I am missing it, or is is it a pending feature? If Google Chrome and Edge Chrome have established this option to override, but Vivaldi does not allow, that is depreciating my interest in Vivaldi as my default browser -- which it now is.

Please advise.

Thanks

hlehyaric

@dmkroslindale Go to chrome://settings/content/insecureContent and add the site in «Allow» section.

Pathduck

Adding the site to the Allow section in the chrome settings page will probably fix things. The user can also follow the instructions on the linked blog; padlock > site settings > choose Allow on Insecure Content.

But it's strange - there's no "mixed content" warning in the address bar in as expected. I guess audio streams are ignored in that warning.

Vivaldi (and Chromium 83) makes a request to:
https://atosradio.com:8001/;stream/1
Which obviously fails as the server doesn't listen on https.

Tested the same in Chromium 81 and there it requests the http stream and works.

This doesn't match what's written on the Chromium blog referenced on the page:

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.
(https://blog.chromium.org/2019/10/no-more-mixed-messages-about-https.html)

Apparently they didn't make that "autoupgrade" change for audio until C. 83...

hlehyaric

@Pathduck said in Mixed Content (http/https problem):

But it's strange - there's no "mixed content" warning in the address bar in as expected.

That's very strange: I've got «mixed content» warning icon in my address bar.

dmkroslindale

Thanks. This completely eluded me. It seems different developers are using different terminology to get to the same result.