You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 26, 2024. It is now read-only.
The text was updated successfully, but these errors were encountered:
clokep
changed the title
Missing field on send join federation endpoint
Missing 'origin' field when responding to send_join over federation
Nov 20, 2020
I feel like we should remove it from the spec, rather than add it to synapse, since it's redundant to the Authorization header.
Technically that would be a breaking change in the spec, but if synapse has never sent it I'm inclined to simply consider its presence a bug in the spec.
There seems to have been some broken logic here, though I don't think it changes my conclusions.
I feel like we should remove it from the spec, rather than add it to synapse, since it's redundant to the Authorization header.
The Authorization header is irrelevant here, since that applies to requests, and this issue is about responses.
But still, origin serves no purpose here: we know which server we connected to, and that is the what the spec currently defines the origin field to mean:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
A-Spec-Complianceplaces where synapse does not conform to the specz-p2(Deprecated Label)
Description
Synapse is not sending
origin
field on federation send join endpoint as defined on spec: https://matrix.org/docs/spec/server_server/r0.1.4#put-matrix-federation-v2-send-join-roomid-eventidOrigin is missing here:
synapse/synapse/handlers/federation.py
Line 1577 in 79bfe96
The text was updated successfully, but these errors were encountered: