Skip to content

Commit 9ede29a

Browse files
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>
1 parent 61e7a73 commit 9ede29a

File tree

2 files changed

+4
-1
lines changed

2 files changed

+4
-1
lines changed
Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
Expand a little on what it means for a PDU to be valid when discussing checks on PDUs.

content/server-server-api.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -356,7 +356,9 @@ specification](/rooms).
356356
Whenever a server receives an event from a remote server, the receiving
357357
server must ensure that the event:
358358

359-
1. Is a valid event, otherwise it is dropped.
359+
1. Is a valid event, otherwise it is dropped. For an event to be valid, it
360+
must contain a `room_id`, and it must comply with the event format of
361+
that [room version](/rooms).
360362
2. Passes signature checks, otherwise it is dropped.
361363
3. Passes hash checks, otherwise it is redacted before being processed
362364
further.

0 commit comments

Comments
 (0)