Attempt to define a valid event (#1045)
* Attempt to define a valid event Resolves #1044. Well, maybe. * Changelog * link to /rooms, thanks Travis Co-authored-by: Travis Ralston <travpc@gmail.com> Co-authored-by: Travis Ralston <travpc@gmail.com>
This commit is contained in:
parent
61e7a73a4f
commit
9ede29a01d
2 changed files with 4 additions and 1 deletions
|
@ -0,0 +1 @@
|
||||||
|
Expand a little on what it means for a PDU to be valid when discussing checks on PDUs.
|
|
@ -356,7 +356,9 @@ specification](/rooms).
|
||||||
Whenever a server receives an event from a remote server, the receiving
|
Whenever a server receives an event from a remote server, the receiving
|
||||||
server must ensure that the event:
|
server must ensure that the event:
|
||||||
|
|
||||||
1. Is a valid event, otherwise it is dropped.
|
1. Is a valid event, otherwise it is dropped. For an event to be valid, it
|
||||||
|
must contain a `room_id`, and it must comply with the event format of
|
||||||
|
that [room version](/rooms).
|
||||||
2. Passes signature checks, otherwise it is dropped.
|
2. Passes signature checks, otherwise it is dropped.
|
||||||
3. Passes hash checks, otherwise it is redacted before being processed
|
3. Passes hash checks, otherwise it is redacted before being processed
|
||||||
further.
|
further.
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue