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 Nov 25, 2024. It is now read-only.
What is the problem:
This endpoint /_matrix/client/unstable/org.matrix.msc2432/rooms/:room_id/aliases?access_token=<redacted> is being called from a subdomain where the client lives(chat.<DOMAIN>, meanwhile the server at <DOMAIN>) and it's the only call that have CORS issues about Access-Control-Allow-Origin missing despite it is already set as a proxy_set_header Access-Control-Allow-Origin '*'; in nginx.
Is this a bug?
The text was updated successfully, but these errors were encountered:
In this instance, you are seeing a CORS error because the endpoint does not exist in Dendrite.
Seeing as MSC2432 was merged into the spec back in 2020, Dendrite instead implements the stable endpoint at /_matrix/client/r0/rooms/{roomId}/aliases and /_matrix/client/v3/rooms/{roomId}/aliases.
You should raise a bug with Cinny about incorrectly using an unstable endpoint for a stable feature.
Background information
go version
: 1.18.1Description
This endpoint
/_matrix/client/unstable/org.matrix.msc2432/rooms/:room_id/aliases?access_token=<redacted>
is being called from a subdomain where the client lives(chat.<DOMAIN>
, meanwhile the server at<DOMAIN>
) and it's the only call that have CORS issues about Access-Control-Allow-Origin missing despite it is already set as aproxy_set_header Access-Control-Allow-Origin '*';
in nginx.Is this a bug?
The text was updated successfully, but these errors were encountered: