This repository has been archived by the owner on Apr 26, 2024. It is now read-only.
-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Trailing slashes required on some federation endpoints #3622
Labels
z-minor
(Deprecated Label)
Comments
turt2live
changed the title
Federation GET /event/$whatever is unrecognized, but /event/$whatever/ is fine
Trailing slashes required on some federation endpoints
Jul 31, 2018
neilisfragile
added a commit
that referenced
this issue
Feb 4, 2019
Proposed implementation is for Synapse to be permissive in what it accepts, ensure that its own requests are spec compliant but if the remote end rejects, then retry on the alternative form. |
So what do people think about removing the |
Sytest is going to need some changes as well in terms of what it expects ( |
3 tasks
anoadragon453
added a commit
that referenced
this issue
Mar 21, 2019
…n 400 (#4840) As per #3622, we remove trailing slashes from outbound federation requests. However, to ensure that we remain backwards compatible with previous versions of Synapse, if we receive a HTTP 400 with `M_UNRECOGNIZED`, then we are likely talking to an older version of Synapse in which case we retry with a trailing slash appended to the request path.
reopening this because #4793 got reverted |
Done in #4935 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
PUT /send/$txnId
Unused endpointGET /pull
GET /event/$eventId
GET /state/$context
GET /state_ids/$roomId
GET /backfill/$context
GET /groups/$groupId/roles
GET /groups/$groupdId/categories
The text was updated successfully, but these errors were encountered: