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

Document .well-known setup, etc (including ACAO headers) #7760

Closed
turt2live opened this issue Nov 28, 2018 · 5 comments
Closed

Document .well-known setup, etc (including ACAO headers) #7760

turt2live opened this issue Nov 28, 2018 · 5 comments
Labels
A-Documentation P1 T-Task Tasks for the team like planning

Comments

@turt2live
Copy link
Member

So far there's been about 80% of people I've seen caught by not having Access-Control-Allow-Origin: * (or similar) on the .well-known file

@lampholder lampholder added T-Task Tasks for the team like planning P1 A-Documentation labels Nov 30, 2018
@jryans
Copy link
Collaborator

jryans commented Dec 17, 2018

Is something that would be added the spec?

@turt2live
Copy link
Member Author

yes and no:

yes - it would be something that would fit nicely as a reminder in the spec

no - we should have our own documentation on how to set up .well-known and not rely on the spec here. The spec is overly complicated for "I want to log in to my homeserver".

@n1trux
Copy link

n1trux commented Mar 24, 2019

Just found out that if you get the error Invalid /api/v1 response it could be because you specified an identity server in .well-known/matrix/client which doesn't provide that functionality (e.g. synapse which is only a home server, not an identity server).

@aaronraimist
Copy link
Collaborator

Definitely still an issue since the flagship Mozilla server ran into the same thing #12311

@t3chguy
Copy link
Member

t3chguy commented May 15, 2023

@t3chguy t3chguy closed this as completed May 15, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-Documentation P1 T-Task Tasks for the team like planning
Projects
None yet
Development

No branches or pull requests

6 participants