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

Relax the mimetype check of the .well-known/web-identity file #11

Open
samuelgoto opened this issue May 17, 2024 · 0 comments
Open

Relax the mimetype check of the .well-known/web-identity file #11

samuelgoto opened this issue May 17, 2024 · 0 comments

Comments

@samuelgoto
Copy link
Collaborator

samuelgoto commented May 17, 2024

The algorithm for fetching and parsing the .well-known file enforces that the mime type must be text/json here.

Unfortunately, there are many occasions where developers don't have the ability to control the mime type in their hosting servers. For example, everybody using github pages can't serve an text/json file unless it matches the predefined extension, .js.

https://docs.github.com/en/pages/getting-started-with-github-pages/about-github-pages#mime-types-on-github-pages

Since .well-known/web-identity doesn't have a file extension, the server serves application/octet-stream instead by default.

For example:

curl http://sgo.to/.well-known/web-identity --verbose

Ideally, unless something else breaks, we should relax the requirement of mime types, and be more accepting of different HTTP responses, as long as we can get the providers_urls list.

I ran into this while trying to set up #2 .

I think this could also be solved with #9.

@samuelgoto samuelgoto transferred this issue from w3c-fedid/FedCM Sep 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant