Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MSC4154: Request max body size #4154

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

turt2live
Copy link
Member

Rendered

In line with matrix-org/matrix-spec#1700, the following disclosure applies:

I am Director of Standards Development at The Matrix.org Foundation C.I.C., Matrix Spec Core Team (SCT) member, employed by Element, and operate the t2bot.io service. This proposal is written and published as Director of Standards Development to assist in furthering the spec.

@turt2live turt2live added proposal A matrix spec change proposal client-server Client-Server API kind:maintenance MSC which clarifies/updates existing spec needs-implementation This MSC does not have a qualifying implementation for the SCT to review. The MSC cannot enter FCP. labels Jun 11, 2024
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Implementation requirements:

  • Reverse proxy configuration demonstrating Matrix standard error response.
    • nginx
    • apache2
    • haproxy
    • traefik
    • caddy

Comment on lines +17 to +20
API endpoints. If a request exceeds this limit, the client SHOULD be presented with a `413 M_TOO_LARGE`
error. The `M_TOO_LARGE` error code [already exists](https://spec.matrix.org/v1.10/client-server-api/#other-error-codes).

Servers MAY raise this limit to higher than 1 MB, but SHOULD NOT lower it below 1 MB.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I find this wording a little unclear: Is it that servers should send M_TOO_LARGE for requests larger than 1 MB? Or that servers should send M_TOO_LARGE for requests larger than the servers' limit, which may be above 1 MB, but should not be under it?

I personally prefer the second interpretation, but whichever is the intended one, I think the wording should make it clear.

DISCLAIMER: I am just an ordinary matrix user with zero standards writing experience.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
client-server Client-Server API kind:maintenance MSC which clarifies/updates existing spec needs-implementation This MSC does not have a qualifying implementation for the SCT to review. The MSC cannot enter FCP. proposal A matrix spec change proposal
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants