Improve reconnect/error handling if server requests take long or return an unexpected status
Open
@max-nextcloud is already working on this.
Since Feb 19, 2025.
bug
feature: sync
- Dominant language
- JavaScript
- Stars
- 659
- Forks
- 133
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 110
Description
We currently don't handle those cases very well, we should check and fix
- The requests to the server take long (e.g. 30s and then time out)
- The server replies with a http code like
- 503, Apache HTML response: The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.
- 504 Gateway timeout
- 502 bad gateway
- Nextcoud maintenance mode
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.
Assessment
This issue has not been assessed yet.