-
-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Element Web makes request to /_matrix/client/unstable/org.matrix.msc3575/sync
on startup, causing lost to-device-messages
#27426
Comments
This sounds like a deployment issue. Nothing in MSC3575 or MSC3885 says |
This avoids unintended consequences, including high resource usage, which would accompany a "full" sync request. Instead, we just grab headers and enough information for CORS to pass, revealing likely support. Fixes element-hq/element-web#27426
Using It just happens that a byproduct of the proxy is that it starts syncing for you, which was requested by the caller using an action-capable verb. |
* Use OPTIONS for sliding sync detection poke This avoids unintended consequences, including high resource usage, which would accompany a "full" sync request. Instead, we just grab headers and enough information for CORS to pass, revealing likely support. Fixes element-hq/element-web#27426 * Appease the linter * Reset for each test
Introduced by matrix-org/matrix-react-sdk#12307.
Calling
/_matrix/client/unstable/org.matrix.msc3575/sync
causes the SS proxy to start polling synapse with our access token, which means that it will receive (some of) our to-device messages instead of us, which means we will get decryption errors.The text was updated successfully, but these errors were encountered: