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 was archived by the owner on Apr 26, 2024. It is now read-only.
Repository navigation
This repository was archived by the owner on Apr 26, 2024. It is now read-only.
Synapse responds with a 404 with HTML content for unknown URL prefixes #11600
See element-hq/element-web#19738 (comment) for some background, but if you request an endpoint for Synapse that doesn't have a prefix registered (see here) then Synapse responds with a 404 including HTML content (the default Twisted 404 handler).
This wasn't an issue when adding new /unstable or /r0 endpoints since the prefix was registered, but the /hierarchy endpoint is the first /v1 endpoint we had. This will also bite us once we need to rev an endpoint to /v2 (or /v4) since neither of those are registered right now.
Activity
t3chguy commentedon Dec 17, 2021
and without an ACAO header so browser-based clients can't even read that its a 404 as the browser just gives them a generic failure due to CORS.
clokep commentedon Jan 18, 2022
This was reverted due to poor interaction with a legacy feature.
clokep commentedon Oct 14, 2022
Cross-ref to a similar Dendrite issue: matrix-org/dendrite#2739.