wholetrans/docs-matrix-spec
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

Give more guidance on how invalid events should be handled.

Browse source 
Co-authored-by: Richard van der Hoff <1389908+richvdh@users.noreply.github.com>
This commit is contained in:
Patrick Cloke 2020-05-20 08:58:32 -04:00 • committed by GitHub
parent f5ebe33a9c
commit 07716711f1
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 4 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

6
proposals/2540-stricter-event-validation.md
View file

@ -21,8 +21,10 @@ even support these by default. One common additional feature is handling
## Proposal ## Proposal
In a future room version, homeserver implementations are to strictly enforce In a future room version, homeserver implementations are to strictly enforce
the JSON compliance of the Canonical JSON specification for events. Events that the JSON compliance of the Canonical JSON specification for events.
do not abide by these rules should be treated like any other bad JSON value. Non-compliant events should be treated like any other malformed event,
for example by rejecting the request with an HTTP 400 error with `M_BAD_JSON`,
or by discarding the event.
The rationale for doing this in a future room version is to avoid a split brain The rationale for doing this in a future room version is to avoid a split brain
room -- where some federated servers believe an event is valid and others reject room -- where some federated servers believe an event is valid and others reject