Spreed: TURN/STUN not working if they have a protocol

Created on 17 Jan 2018  路  3Comments  路  Source: nextcloud/spreed

Say I put: https://stun.mario.com:443 - This would NOT work!

If I put: stun.mario.com:443 - this works.

Is this expected behaviour? Because it's strange UX :-/

cc @nickvergessen

enhancement good first issue

Most helpful comment

@fancycode yup, that's what we should do - on the server side :p

All 3 comments

Hmm, not sure if it's strange UX, the default of stun is without protocol aswell, that is, because webrtc itself uses stun:stun.mario.com:442 later to connect.
Also we don't control the endpoint of saving this configs, but yeah we could strip it with JS before sending it to the server.

STUN doesn't use https as protocol, so it shouldn't be part of the setting. Maybe we can simply strip any protocols from the entered string?

@fancycode yup, that's what we should do - on the server side :p

Was this page helpful?
0 / 5 - 0 ratings

Related issues

jospoortvliet picture jospoortvliet  路  3Comments

llamallama picture llamallama  路  4Comments

jospoortvliet picture jospoortvliet  路  4Comments

fancycode picture fancycode  路  5Comments

ChristophAGietl picture ChristophAGietl  路  4Comments