No more HTTP for WebRTC on Chrome, only HTTPS

Posted on by Igor Khomenko

“‘getUserMedia‘ in Chrome will require HTTPS soon” – this is what we have got from the Kranky Geek mini conference in San Francisco. That was announced during Google’s WebRTC update – Chrome will no longer support getUserMedia calls from a site that’s served up over http.

The Chrome team will roll this out in Chrome 47 before the end of 2015. That means any of your sites that leverage getUserMedia will be required to be served up via the https protocol to work across all browsers.

 

 

 

 

 

 

 

 

 

 

 

 

 

So if you want getUserMedia to work on your site, you’ll need to start serving up content via HTTPS.

Don’t forget to roll out this update before 2016.

Check out Google WebRTC team’s update