We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Without CORS headers, responses from the Package Registry cannot be used in javascript applications running in browsers.
Given that all the Package Registry APIs are public and read-only, we don't really need restricting its cross origin access.
It would be probably fine to always allow any origin:
Access-Control-Allow-Origin: *
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
Without CORS headers, responses from the Package Registry cannot be used in javascript applications running in browsers.
Given that all the Package Registry APIs are public and read-only, we don't really need restricting its cross origin access.
It would be probably fine to always allow any origin:
The text was updated successfully, but these errors were encountered: