Fixing E2E CSR transmission failure for new connections #1420
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
…type on sendrequest()) Signed-off-by: Dominique Fuchs <32204802+DominiqueFuchs@users.noreply.github.com>
camilasan
approved these changes
Sep 15, 2019
|
Amazing contributions @DominiqueFuchs 🎉 |
This was referenced Sep 25, 2019
|
/backport to stable-2.6 |
|
The backport to stable-2.6 failed. Please do this backport manually. |
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.
Fixes at least:
nextcloud/server#12365
nextcloud/end_to_end_encryption#87
#560
#868
#977
#830
Summary/problem: After E2E-activation on the server, desktop client fails on initial setup (wizard) or sync (when already configured).
Summary/bug: Missing content-type setting on QNetworkRequest when doing sendrequest() for the corresponding API job.