New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 908740 link

Starred by 1 user

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

reject TURN urls containing a username

Project Member Reported by philipp....@googlemail.com, Nov 27

Issue description

from https://stackoverflow.com/questions/53488035/rtcpeerconnection-with-rtcconfiguration-breaks-on-firefox/53488438#53488438

Chrome Version: 72.0.3610.2
OS: all

What steps will reproduce the problem?
(1) paste this into the JS console:
const configuration = {
iceServers: [
  {
    urls: 'turn:user@myserver.com:3478', // <- here remove "user@"
    username: 'user',
    credential: 'mypwd'
  }
 ]
};
const pc = new RTCPeerConnection(configuration)

What is the expected result?
It throws.

What happens instead?
It accepts this as valid.

Firefox is getting blamed for erroring because Chrome is too lenient. Passing the user in the URL went away in 2012 around Chrome 25 I think
 
Components: -Blink>WebRTC>PeerConnection Blink>WebRTC>Network
Status: Available (was: Untriaged)

Sign in to add a comment