mirror of
https://github.com/matrix-org/matrix-spec
synced 2026-04-27 04:54:08 +02:00
Compare commits
3 commits
d20af54299
...
c75e612883
| Author | SHA1 | Date | |
|---|---|---|---|
|
|
c75e612883 | ||
|
|
74a0d5f289 | ||
|
|
282a44f5c5 |
|
|
@ -0,0 +1 @@
|
|||
M_RESOURCE_LIMIT_EXCEEDED is now listed as a common error code.
|
||||
1
changelogs/internal/newsfragments/2238.clarification
Normal file
1
changelogs/internal/newsfragments/2238.clarification
Normal file
|
|
@ -0,0 +1 @@
|
|||
Silence failing redocly-cli rule.
|
||||
|
|
@ -136,6 +136,17 @@ code if the endpoint is implemented, but the incorrect HTTP method is used.
|
|||
{{% added-in v="1.17" %}} The device ID supplied by the application service does
|
||||
not belong to the user ID during [identity assertion](/application-service-api/#identity-assertion).
|
||||
|
||||
`M_RESOURCE_LIMIT_EXCEEDED`
|
||||
The request cannot be completed because the homeserver has reached a
|
||||
resource limit imposed on it. For example, a homeserver held in a shared
|
||||
hosting environment may reach a resource limit if it starts using too
|
||||
much memory or disk space. The error MUST have an `admin_contact` field
|
||||
to provide the user receiving the error a place to reach out to.
|
||||
Typically, this error will appear on routes which attempt to modify
|
||||
state (e.g.: sending messages, account data, etc) and not routes which
|
||||
only read state (e.g.: [`/sync`](#get_matrixclientv3sync),
|
||||
[`/user/{userId}/account_data/{type}`](#get_matrixclientv3useruseridaccount_datatype), etc).
|
||||
|
||||
`M_UNKNOWN`
|
||||
An unknown error has occurred.
|
||||
|
||||
|
|
@ -221,17 +232,6 @@ The request or entity was too large.
|
|||
The resource being requested is reserved by an application service, or
|
||||
the application service making the request has not created the resource.
|
||||
|
||||
`M_RESOURCE_LIMIT_EXCEEDED`
|
||||
The request cannot be completed because the homeserver has reached a
|
||||
resource limit imposed on it. For example, a homeserver held in a shared
|
||||
hosting environment may reach a resource limit if it starts using too
|
||||
much memory or disk space. The error MUST have an `admin_contact` field
|
||||
to provide the user receiving the error a place to reach out to.
|
||||
Typically, this error will appear on routes which attempt to modify
|
||||
state (e.g.: sending messages, account data, etc) and not routes which
|
||||
only read state (e.g.: [`/sync`](#get_matrixclientv3sync),
|
||||
[`/user/{userId}/account_data/{type}`](#get_matrixclientv3useruseridaccount_datatype), etc).
|
||||
|
||||
`M_CANNOT_LEAVE_SERVER_NOTICE_ROOM`
|
||||
The user is unable to reject an invite to join the server notices room.
|
||||
See the [Server Notices](#server-notices) module for more information.
|
||||
|
|
|
|||
|
|
@ -8,4 +8,7 @@ rules:
|
|||
no-invalid-media-type-examples: off
|
||||
no-path-trailing-slash: off
|
||||
operation-2xx-response: off
|
||||
spec-strict-refs: error
|
||||
spec-strict-refs: error
|
||||
# $ref in examples are not spec-compliant, yet we find them useful. Disable this rule
|
||||
# and instead check example schema using `check-event-schema-examples.py`
|
||||
no-invalid-schema-examples: off
|
||||
|
|
|
|||
Loading…
Reference in a new issue