Add bbb-origin-server-name to metadata on meeting creation #5705
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
|
I like this approach better |
farhatahmad
approved these changes
Feb 20, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Many BBB frontends as well as GL2 (if I remember correctly) include the hostname from the base URL as 'bbb-origin-server-name' in the meeting metadata. This is useful in analytics / statistics to differentiate usage by different frontend deployments.
GL3 does not include the bbb-origin-server-name in metadata, it is only implicitly included in the callback-url. This PR makes GL3 include bbb-origin-server-name in the metadata on meeting creation.