UPSTREAM BASELINE: nextcloud/spreed v22.0.12 (без изменений)
Type checking / changes (push) Has been cancelled
Type checking / test (push) Has been cancelled
Type checking / typescript-summary (push) Has been cancelled
Node tests / changes (push) Has been cancelled
Node tests / test (push) Has been cancelled
Node tests / test-summary (push) Has been cancelled
Type checking / changes (push) Has been cancelled
Type checking / test (push) Has been cancelled
Type checking / typescript-summary (push) Has been cancelled
Node tests / changes (push) Has been cancelled
Node tests / test (push) Has been cancelled
Node tests / test-summary (push) Has been cancelled
Источник: https://github.com/nextcloud/spreed/archive/refs/tags/v22.0.12.tar.gz С этого коммита ветка официального Nextcloud Talk отрезана (решение владельца 2026-07-06). Все дальнейшие изменения — только наши; версии релизов: 22.0.12-f7.N.
This commit is contained in:
@@ -0,0 +1,58 @@
|
||||
# Global API status and headers
|
||||
|
||||
## Maintenance mode
|
||||
|
||||
Server is in maintenance mode, when the header is not available it could be a missing execution of a database upgrade or any other general server failure.
|
||||
|
||||
* Response:
|
||||
- Status code:
|
||||
+ `503 Service Unavailable`
|
||||
|
||||
- Header:
|
||||
|
||||
| field | type | Description |
|
||||
|--------------------------------|------|-------------|
|
||||
| `X-Nextcloud-Maintenance-Mode` | int | Value `1` |
|
||||
|
||||
|
||||
## Rate limit
|
||||
|
||||
The remote address sent too many requests targeting the same endpoint, see the [Nextcloud Developer manual](https://docs.nextcloud.com//server/stable/developer_manual/basics/controllers.html#rate-limiting) for more information.
|
||||
|
||||
* Response:
|
||||
- Status code:
|
||||
+ `429 Too Many Requests`
|
||||
|
||||
## Brute force protection
|
||||
|
||||
The remote address sent too many requests targeting the same action, see the [Nextcloud Developer manual](https://docs.nextcloud.com//server/stable/developer_manual/basics/controllers.html#brute-force-protection) for more information.
|
||||
|
||||
* Response:
|
||||
- Status code:
|
||||
+ `429 Too Many Requests`
|
||||
|
||||
## Outdated client
|
||||
|
||||
From time to time it is unavoidable to break compatibility. In such cases we try to be as helpful for the users as possible and instead of behaving unexpected, a dedicated error response is returned and the clients should handle it properly and show a message that the client is outdated and needs to be upgraded in order to continue using this server.
|
||||
|
||||
* Response:
|
||||
- Status code:
|
||||
+ `426 Upgrade Required`
|
||||
- Body:
|
||||
+ `ocs.meta.message` contains the minimum required version of the used client
|
||||
|
||||
## Federation - Not supported
|
||||
|
||||
Endpoints without a "Federation capability: `federation-vX`" will return a `406 Not Acceptable` status code, when called with tokens that actually refer to a so-called proxy conversation on the local server.
|
||||
|
||||
* Response:
|
||||
- Status code:
|
||||
+ `406 Not Acceptable`
|
||||
|
||||
## Federation - Remote error
|
||||
|
||||
When a request is performed on a proxy conversation and the host can not be reached `422 Unprocessable Content` will be returned. The only exception will be leaving the room, where the request will still execute it's part locally so the user is no longer bothered. A background job will be queued to retry informing the remote server about the leave automatically.
|
||||
|
||||
* Response:
|
||||
- Status code:
|
||||
+ `422 Unprocessable Content`
|
||||
Reference in New Issue
Block a user