This repository has been archived by the owner on Apr 26, 2024. It is now read-only.
Synapse uses an unstable prefix for thirdparty
application service requests
#11158
Labels
A-Spec-Compliance
places where synapse does not conform to the spec
O-Occasional
Affects or can be seen by some users regularly or most users rarely
S-Minor
Blocks non-critical functionality, workarounds exist.
T-Defect
Bugs, crashes, hangs, security vulnerabilities, or other reported issues.
Z-Help-Wanted
We know exactly how to fix this issue, and would be grateful for any contribution
The appservice code has an
APP_SERVICE_PREFIX
constant:synapse/synapse/appservice/api.py
Line 52 in bf72d10
Which it then uses for any
.../thirdparty/...
request:synapse/synapse/appservice/api.py
Lines 137 to 142 in bf72d10
synapse/synapse/appservice/api.py
Lines 172 to 176 in bf72d10
However, the spec says that these endpoints should have the prefix
/_matrix/app/v1
, not/_matrix/app/unstable
. This means that if an application service correctly implements the spec, Synapse will 404 when trying to contact it on these endpoints (when e.g. looking up which third-party protocol an application service uses).The text was updated successfully, but these errors were encountered: