Fix graphql API for clusterproxy setup #19207
Merged
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
The websocket connection to the graphql API needs to go directly to the BBB server (bbb-html5) and it the middleware needs to accept requests with a different origin.
schrd
force-pushed
the
graphql-clusterproxy
branch
from
2bfaf29
to
d2a28a6
Compare
|
Kudos, SonarCloud Quality Gate passed!
|
Automated tests Summary✅ All the CI tests have passed! |
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.
What does this PR do?
It fixes BBB 3.0 for a cluster proxy setup. Two things have to be fixed:
Originheader.Updated setup instructions accordingly.
Motivation
I want client settings in local storage consistent across all my BBB server. I need a cluster setup.