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.

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

It's not clear whether /versions should fail if auth is invalid #1779

Open
Kladki opened this issue Apr 7, 2024 · 4 comments · May be fixed by matrix-org/matrix-spec-proposals#4128
Open
Labels
A-Client-Server Issues affecting the CS API clarification An area where the expected behaviour is understood, but the spec could do with being more explicit

Comments

@Kladki
Copy link
Contributor

Kladki commented Apr 7, 2024

Link to problem area:

https://spec.matrix.org/v1.10/client-server-api/#get_matrixclientversions

Issue:

As of v1.10, the /versions endpoint has become the first to optionally accept authentication. However, it is not specified whether if authentication is provided and is invalid whether the server should return an error, or just perform like there was no authentication provided in the first place.

@Kladki Kladki added the clarification An area where the expected behaviour is understood, but the spec could do with being more explicit label Apr 7, 2024
@richvdh
Copy link
Member

richvdh commented Apr 8, 2024

@Kladki could you look at the changelog to see which MSC proposed this change, to see if there is more detail there?

@Kladki
Copy link
Contributor Author

Kladki commented Apr 8, 2024 via email

@richvdh
Copy link
Member

richvdh commented Apr 8, 2024

Mhmm. Seems like we need another MSC!

@Kladki
Copy link
Contributor Author

Kladki commented Apr 8, 2024 via email

@richvdh richvdh added the A-Client-Server Issues affecting the CS API label Apr 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-Client-Server Issues affecting the CS API clarification An area where the expected behaviour is understood, but the spec could do with being more explicit
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants