nextcloud / nextcloud/richdocuments
Check for protocol mismatch betwen discovery and nextcloud
Open
Nobody has claimed this yet.
1. to develop
bug
setup
- Dominant language
- JavaScript
- Stars
- 453
- Forks
- 147
- Avg merge
- 14h 54m
- Merged PRs (30d)
- 83
Description
@mejo- found that when using ssl without ssl.termination loading started failing after https://github.com/CollaboraOnline/online/commit/b86a1bfd6be124725c09bc8ed26de3bb72aad555 was introduced. We should check that in the admin settings
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the admin settings and review the referenced Collabora Online commit to understand the protocol mismatch between discovery and Nextcloud. Trace the SSL and ssl.termination settings involved in loading, then verify that the admin configuration detects or handles the mismatch correctly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100