Rate-limiting behaviour is not well-defined for clients in the Client-Server API #1889
Labels
clarification
An area where the expected behaviour is understood, but the spec could do with being more explicit
Link to problem area: https://spec.matrix.org/v1.11/client-server-api/#rate-limiting
Example real-world case where this matters is that matrix.org's Synapse converts 503s to 429s to avoid cloudflare taking the whole system down. These 429s don't have a retry-after time and they have an
M_UNKNOWN
error code.Is this dodgy? Should clients be ready to handle this? The spec only makes some suggestions with SHOULD but doesn't clarify for servers or clients what is allowed and what isn't.
It is worth remembering that middleboxes, not understanding Matrix, may have reason to inject 429 response codes.
The text was updated successfully, but these errors were encountered: