-
Notifications
You must be signed in to change notification settings - Fork 384
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
Document access_token in headers #1042
Comments
You can now (as of matrix-org/synapse#1098) put your access token in an Auth header instead. We should spec it. |
I don't really feel this is adequately documented yet. It's nice to have it mentioned in the spec but we need to be clearer about how clients use it, and that servers must provide it. |
@richvdh the section feels fairly clear to me - what kind of improvement were you thinking of? for reference:
|
* Opinionated rewrite of unconflicted state map * Define auth chain
In matrix-org#1042 I incorrectly wrote that the conflicted state set is a set of pairs (K, V). We later take the union of the conflicted state set and the auth difference. The latter is a set of events (V) only. Fix this by making the conflicted state set a set of events rather than a set of pairs. That is, the conflicted state set is a a `Set[Event]` instead of a `Set[((type, state key), event)]`.
…g#1158) * Fix unintentional stateres change added in matrix-org#1042 * Changelog
No description provided.
The text was updated successfully, but these errors were encountered: