- From: Philipp Hancke via GitHub <sysbot+gh@w3.org>
- Date: Wed, 01 Jan 2020 08:59:45 +0000
- To: public-webrtc-logs@w3.org
this one is a bit tricky. One of the advantages of onicecandidateerror is that it returns a concrete STUN error code, e.g. when the credential is wrong. We could restrict it to STUN errors. Note that at least for UDP its possible to infer wrong credentials. The other important use case is discovering whether a client can not connect to a certain TURN server. Not gathering a relay candidate is an indication for this but I would have preferred an explicit error. Unfortunately this is the case that can be used for portscanning. -- GitHub Notification of comment by fippo Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2426#issuecomment-570035443 using your GitHub account
Received on Wednesday, 1 January 2020 08:59:47 UTC