-
Notifications
You must be signed in to change notification settings - Fork 1k
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
GitHub API does not include user-agent
in Access-Control-Allow-Headers
#817
Comments
👋 @flaki thanks a lot for the heads up, I was able to reproduce the issue in Firefox. I’ll check in with GitHub’s API team |
For clarification, here is what we mean
The |
I've reported this to the GitHub API team and will let you know if there are any updates. |
This is shipped!
|
That was fast, thanks! I double checked and things are working now. Let us know if something is still funky in Firefox @flaki. Thanks again for the report 🙏 |
Fantastic turnaround, thanks so much! 💖 |
Unless I'm missing something, this issue seems to be mildly related to #758 (except that it affects api.github.com).
It seems browsers are blocking the CORS pre-flight request if a User-Agent is present in the request headers and the server doesn't explicitly list
user-agent
as a modifiable property in the returned response'sAccess-Control-Allow-Headers
header. This seems to be a rather recent addition to the spec (the ability to change the User Agent, and thus the requirement for opt-in). This has already landed in Firefox 43, is in the works for Chrome.Source code used:
Octokit version: v15.2.4
The text was updated successfully, but these errors were encountered: