Skip to content
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

Merged
merged 4 commits into from
May 8, 2018

Conversation

fancycode
Copy link
Member

This PR fixes a couple of issues when using the standalone signaling server.

Should be backported to the current stable after landing.

@fancycode fancycode requested a review from nickvergessen May 8, 2018 08:12
@fancycode fancycode force-pushed the standalone-signaling-fixes branch from ea01dab to 53baa4b Compare May 8, 2018 09:06
@@ -275,6 +275,7 @@ protected function getInputStream() {
* https://github.com/nextcloud/spreed/wiki/Spreed-Signaling-API
*
* @PublicPage
* @NoCSRFRequired
Copy link
Member

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

Copy link
Member Author

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.

Copy link
Member

@nickvergessen nickvergessen left a 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

fancycode added 4 commits May 8, 2018 11:41
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>
@fancycode fancycode force-pushed the standalone-signaling-fixes branch from 53baa4b to 98b429e Compare May 8, 2018 09:42
@fancycode
Copy link
Member Author

Addressed your comment, thanks for the fast review.

@nickvergessen nickvergessen added this to the 4.0 (Nextcloud 14) milestone May 8, 2018
@nickvergessen nickvergessen merged commit 2b4e48c into master May 8, 2018
@nickvergessen nickvergessen deleted the standalone-signaling-fixes branch May 8, 2018 10:59
fancycode added a commit that referenced this pull request May 8, 2018
…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>
fancycode added a commit that referenced this pull request May 9, 2018
…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>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
3. to review bug feature: signaling 📶 Internal and external signaling backends
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants