-
Notifications
You must be signed in to change notification settings - Fork 448
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Various standalone signaling fixes. #864
Conversation
ea01dab
to
53baa4b
Compare
@@ -275,6 +275,7 @@ protected function getInputStream() { | |||
* https://github.com/nextcloud/spreed/wiki/Spreed-Signaling-API | |||
* | |||
* @PublicPage | |||
* @NoCSRFRequired |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since this is OCS, it should not be necessary. If your requests fail, try adding a OCS-APIRequest: true
header
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, didn't know about that header. If I set it, the @NoCSRFRequired
can be removed - will remove that commit from the PR.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
But looks good in general
Signed-off-by: Joachim Bauch <bauch@struktur.de>
Otherwise messages like `refresh-participant-list` could be stored in the database even if standalone signaling is used. Signed-off-by: Joachim Bauch <bauch@struktur.de>
Signed-off-by: Joachim Bauch <bauch@struktur.de>
Signed-off-by: Joachim Bauch <bauch@struktur.de>
53baa4b
to
98b429e
Compare
Addressed your comment, thanks for the fast review. |
…ist. This avoids a conflict (introduced by #864) with the existing ´usersChanged` event which is triggered when the `inCall` status of a user has changed. Signed-off-by: Joachim Bauch <bauch@struktur.de>
…ist. This avoids a conflict (introduced by #864) with the existing ´usersChanged` event which is triggered when the `inCall` status of a user has changed. Signed-off-by: Joachim Bauch <bauch@struktur.de>
This PR fixes a couple of issues when using the standalone signaling server.
Should be backported to the current stable after landing.