Skip to content
This repository has been archived by the owner on Apr 26, 2024. It is now read-only.

Missing 'origin' field when responding to send_join over federation #8786

Closed
gnieto opened this issue Nov 19, 2020 · 5 comments
Closed

Missing 'origin' field when responding to send_join over federation #8786

gnieto opened this issue Nov 19, 2020 · 5 comments
Labels
A-Spec-Compliance places where synapse does not conform to the spec z-p2 (Deprecated Label)

Comments

@gnieto
Copy link

gnieto commented Nov 19, 2020

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-eventid

Origin is missing here:

return {"state": list(state.values()), "auth_chain": auth_chain}

@clokep clokep changed the title Missing field on send join federation endpoint Missing 'origin' field when responding to send_join over federation Nov 20, 2020
@clokep clokep added z-p2 (Deprecated Label) A-Spec-Compliance places where synapse does not conform to the spec labels Nov 20, 2020
@richvdh
Copy link
Member

richvdh commented 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.

@richvdh
Copy link
Member

richvdh commented Nov 20, 2020

@richvdh
Copy link
Member

richvdh commented Sep 26, 2022

Closing this; I consider it a spec bug, not a Synapse one.

@richvdh richvdh closed this as completed Sep 26, 2022
@DMRobertson
Copy link
Contributor

Recently related: matrix-org/sytest#1293

@richvdh
Copy link
Member

richvdh commented Oct 12, 2022

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:

image

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
A-Spec-Compliance places where synapse does not conform to the spec z-p2 (Deprecated Label)
Projects
None yet
Development

No branches or pull requests

4 participants