matrix-spec/changelogs/server_server/newsfragments/2575.clarification at db72e7caeaf9b1dbc70d99a7aa1488a8cb8df4f1 - Filip/matrix-spec - Forgejo: Beyond coding. We forge.

Filip/matrix-spec

mirror of https://github.com/matrix-org/matrix-spec synced 2026-02-22 14:03:42 +01:00

Travis Ralston 67d46fa881 Clarify the auth_chain and state for send_join

Fixes https://github.com/matrix-org/matrix-doc/issues/2467
Fixes https://github.com/matrix-org/matrix-doc/issues/2464

This is based on looking at Synapse, not actually testing it. Within the send_join handling functions, an "event context" is acquired [here](d14c4d6b6d/synapse/handlers/federation.py (L1472)) which then later uses the previous state (populated [here](d14c4d6b6d/synapse/state/__init__.py (L286-L289)) in the event context) [here](d14c4d6b6d/synapse/handlers/federation.py (L1494-L1501)) to return a response. Within the event context, the previous state IDs are populated [here](d14c4d6b6d/synapse/state/__init__.py (L351)).

2020-05-25 11:58:50 -06:00

2 lines

62 B

Plaintext

Raw Blame History

Clarify the state/auth chain requirements for ``/send_join``.