BigBlueButton/bigbluebutton-Github
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

fix: encode user-name before sending it as header to checkAuthorization users

Browse Source 
Lack of encoding is causing some specific languages to have the user-name
header stripped out from the HTTP Upgrade requests used by the
checkAuthorization users (bbb-webrtc-sfu). That translates to
webcam/screenshare/listen only failing due to an incomplete header set.
This commit is contained in:
prlanzarin 2023-03-06 10:12:30 -03:00
parent d5449a05e5
commit 58f7fa3df6
1 changed files with 2 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
bigbluebutton-web/grails-app/controllers/org/bigbluebutton/web/controllers/ConnectionController.groovy
View File

@ -22,6 +22,7 @@ import org.bigbluebutton.api.MeetingService
import org.bigbluebutton.api.domain.UserSession
import org.bigbluebutton.api.util.ParamsUtil
import org.bigbluebutton.api.ParamsProcessorUtil
import java.nio.charset.StandardCharsets
class ConnectionController {
MeetingService meetingService
@ -42,7 +43,7 @@ class ConnectionController {
response.addHeader("User-Id", userSession.internalUserId)
response.addHeader("Meeting-Id", userSession.meetingID)
response.addHeader("Voice-Bridge", userSession.voicebridge )
response.addHeader("User-Name", userSession.fullname)
response.addHeader("User-Name", URLEncoder.encode(userSession.fullname, StandardCharsets.UTF_8.name()))
response.setStatus(200)
response.outputStream << 'authorized'
} else {