MatrixSynapse/synapse/handlers
Richard van der Hoff 64765e5199 When we do an invite rejection, save the signed leave event to the db
During a rejection of an invite received over federation, we ask a remote
server to make us a `leave` event, then sign it, then send that with
`send_leave`.

We were saving the *unsigned* version of the event (which has a different event
id to the signed version) to our db (and sending it to the clients), whereas
other servers in the room will have seen the *signed* version. We're not aware
of any actual problems that caused, except that it makes the database confusing
to look at and generally leaves the room in a weird state.
2017-04-07 14:39:32 +01:00
..
__init__.py
_base.py
account_data.py
admin.py
appservice.py
auth.py
device.py
devicemessage.py
directory.py Ignore backoff history for invites, aliases, and roomdirs 2017-03-23 12:23:22 +00:00
e2e_keys.py Merge pull request #2050 from matrix-org/rav/federation_backoff 2017-03-23 22:27:01 +00:00
events.py
federation.py When we do an invite rejection, save the signed leave event to the db 2017-04-07 14:39:32 +01:00
identity.py
initial_sync.py
message.py
presence.py Cache hosts in room 2017-03-24 11:46:24 +00:00
profile.py Ignore backoff history for invites, aliases, and roomdirs 2017-03-23 12:23:22 +00:00
receipts.py
register.py
room.py
room_list.py
room_member.py
search.py
sync.py Comments 2017-03-16 13:04:07 +00:00
typing.py