Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Appservice spec doesn't say you can use the Auth header #1424

Closed
turt2live opened this issue Jul 17, 2018 · 0 comments
Closed

Appservice spec doesn't say you can use the Auth header #1424

turt2live opened this issue Jul 17, 2018 · 0 comments
Assignees
@turt2live
Labels
spec-omission implemented but not currently specified
Projects
August 2018 r0

Comments

@turt2live
Copy link
Member

You can
@turt2live turt2live added the spec-omission implemented but not currently specified label Jul 17, 2018
@turt2live turt2live added this to To do: appservices (prioritized) in August 2018 r0 Aug 14, 2018
@turt2live turt2live self-assigned this Aug 17, 2018
turt2live added a commit to turt2live/matrix-doc that referenced this issue Aug 17, 2018
@turt2live
Encourage appservices to use the Authorization header
857bcc0 
This also throws in a mention about how to handle a request with a lack of user_id.

The request samples now encourage the use of the header over the query string, and have had their sample values added for some readability. 

Fixes matrix-org#1296
Fixes matrix-org#1424
@turt2live turt2live mentioned this issue Aug 17, 2018
Merged
@turt2live turt2live moved this from To do: appservices (prioritized) to In review in August 2018 r0 Aug 17, 2018
August 2018 r0 automation moved this from In review to Done (this list will be incomplete) Aug 21, 2018
@jplatte jplatte mentioned this issue Mar 1, 2022
Closed
RiotTranslateBot pushed a commit to RiotTranslateBot/matrix-doc that referenced this issue Aug 22, 2023
@richvdh
Clarify terminology around aggregations (matrix-org#1424)
d26794e 
I've done my best to remove the word "bundle", because I feel like it causes
more confusion than it provides. Instead I have favoured "aggregated child
events" which I think is clearer.

Some general clarification around these parts of the spec.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@turt2live turt2live

Labels
spec-omission implemented but not currently specified
Projects
No open projects
August 2018 r0
  
Done (this list will be incomplete)
Milestone
No milestone
Development

No branches or pull requests
1 participant
@turt2live