We have some errors in javascript when running youtube playback tests because the URLs are using HTTP protocol instead of HTTPS.

21:29:17.091 Using Encrypted Media Extensions at http://ec2-52-214-163-93.eu-west-1.compute.amazonaws.com/tes…raptor=true&exclude=1,2&muted=true&command=run#1585938365155 on an insecure (i.e. non-HTTPS) context is deprecated and will soon be removed. You should consider switching to a secure origin such as HTTPS. emeManager.js:61:19

I opened this bug to enable HTTPS on amazon development server.

Well, why aren't we using HTTPS even for our [current production site]https://searchfox.org/mozilla-central/source/testing/raptor/raptor/tests/benchmarks/raptor-youtube-playback.ini#19)? Looks like the patch on bug 1553486 landed 9 months ago was faulty and didn't actually change the protocol to HTTPS when moving the tests from the dev site to production.

And HTTPS still works fine:
https://yttest.prod.mozaws.net/2019/main.html?test_type=playbackperf-test&raptor=true&command=run&exclude=1,2&muted=true#1586805011364

As such we should just change all the Raptor configs for this test type to HTTPS. Marian, I think that is something you can do and we don't have to require Tarek's time for it.

For YTP 2020 where i am using the development server, if i want to use https we have this error:
"Unable to connect
Firefox can’t establish a connection to the server at ec2-52-214-163-93.eu-west-1.compute.amazonaws.com."
https://ec2-52-214-163-93.eu-west-1.compute.amazonaws.com/testing_2020/perf-youtube-playback/2019/main.html?test_type=playbackperf-widevine-sfr-h264-test&raptor=true&exclude=1,2&muted=true&command=run

I'll make the changes for the current YTP tests, since the https works by default.

Thanks, best would be to do this on a new bug, and keep this one then for the dev server. Please file a new one one reference bug 1553486 as I did here.

https://yttest.dev.mozaws.net/2019/main.html