Tracking issue for MSC4452: Preview URL capability
Context
Synapse has had the ability to disable URL Previews for a long time, however the clients are unaware of the state of the feature. This adds a capability and tidies up the endpoint so that the feature can be known ahead of time in clients, and can thus know whether to present the setting to users and whether to make requests.
https://github.com/element-hq/integrations-internal/issues/35#issuecomment-4303403986
Implemented in #19715
Current design in Synapse
The old design in Synapse 404'd any requests if the preview feature was disabled in the config.
The new one 403s requests.
Caveats to be aware of
None. Existing clients should react the same to a 404 as a 403.
How do we know when to remove this
I suspect that this MSC will be relatively easy to land, and thus we can remove this when it gets merged.
Tracking issue for MSC4452: Preview URL capability
Context
Synapse has had the ability to disable URL Previews for a long time, however the clients are unaware of the state of the feature. This adds a capability and tidies up the endpoint so that the feature can be known ahead of time in clients, and can thus know whether to present the setting to users and whether to make requests.
https://github.com/element-hq/integrations-internal/issues/35#issuecomment-4303403986
Implemented in #19715
Current design in Synapse
The old design in Synapse 404'd any requests if the preview feature was disabled in the config.
The new one 403s requests.
Caveats to be aware of
None. Existing clients should react the same to a 404 as a 403.
How do we know when to remove this
I suspect that this MSC will be relatively easy to land, and thus we can remove this when it gets merged.