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

CORS not supported when API-key is incorrect #2863

Open
jalas167 opened this issue Oct 24, 2023 · 0 comments
Open

CORS not supported when API-key is incorrect #2863

jalas167 opened this issue Oct 24, 2023 · 0 comments
Labels
sdk-request issue requested by SDK team

Comments

@jalas167
Copy link
Contributor

Even if the yagna is started with option --api-allow-origin=... if the api-key is incorrect the response is without CORS headers resulting in 2 errors:

Access to XMLHttpRequest at 'http://127.0.0.1:7465/me' from origin 'http://localhost:8080'
has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.

GET http://127.0.0.1:7465/me net::ERR_FAILED 401 (Unauthorized)

The response should include CORS headers so the user would get only 401 error.

@grisha87 grisha87 added the sdk-request issue requested by SDK team label Mar 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
sdk-request issue requested by SDK team
Projects
None yet
Development

No branches or pull requests

2 participants