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.

Sign up for GitHub

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

Jump to bottom

Document event size errors (SPEC-406) #183

Open
matrixbot opened this issue May 21, 2016 · 3 comments
Open

Document event size errors (SPEC-406) #183

matrixbot opened this issue May 21, 2016 · 3 comments
Labels
A-Client-Server Issues affecting the CS API clarification An area where the expected behaviour is understood, but the spec could do with being more explicit

Comments

@matrixbot
Copy link
Member

The "Event structure" subsection "Size limits" in the C-S API spec states some data size limits for events and for some of the events' fields. There should be an explanation of what a homeserver is expected to do if it receives an event which violates one of these limits, as well as how clients and servers should behave when wanting to send an event that would violate the limits, e.g. an event with an extremely long message body.

(Imported from https://matrix.org/jira/browse/SPEC-406)

(Reported by Jimmy Cuadra)
@matrixbot
Copy link
Member Author

Jira watchers: @richvdh

@matrixbot
Copy link
Member Author

Yes, there really really should.

Synapse returns an HTTP 413 with a matrix error code of M_TOO_LARGE when a client tries to send such an event.

Clients aren't expected to provide a way of sending the complete works of Shakespeare in an event...

-- @richvdh

@matrixbot matrixbot added the clarification An area where the expected behaviour is understood, but the spec could do with being more explicit label Oct 28, 2016
@matrixbot matrixbot changed the title Document event size errors Document event size errors (SPEC-406) Oct 31, 2016
@matrixbot matrixbot added spec-bug Something which is in the spec, but is wrong and removed spec-bug Something which is in the spec, but is wrong labels Nov 7, 2016
@jimmycuadra jimmycuadra mentioned this issue Aug 16, 2017
Open
@turt2live turt2live self-assigned this Sep 6, 2018
@richvdh
Copy link
Member

richvdh commented Sep 7, 2018

related: #365

@turt2live turt2live removed their assignment Oct 16, 2018
@turt2live turt2live added the A-Client-Server Issues affecting the CS API label Feb 6, 2019
@richvdh richvdh transferred this issue from matrix-org/matrix-spec-proposals Mar 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
A-Client-Server Issues affecting the CS API clarification An area where the expected behaviour is understood, but the spec could do with being more explicit
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@neilisfragile @turt2live @richvdh @matrixbot