Open Skylion007 opened 8 years ago
Also Google complains if the connection is SSL and the Websockets are not secure websockets. As such, WebRTC should be changed to use wss:// instead of ws://
I fixed the WebRTC client code to use secure websockets if the page is served via HTTPS.
Javascript does not compile on line 169 in webrts_ros.js. Instead it returns this error stating that navigator.mediadevices.getUserMedia is not a function. It actually requires the site be HTTPS, here is another issue about how you can fix it via tunneling: http://www.tokbox.com/blog/the-impact-of-googles-new-chrome-security-policy-on-webrtc/