-
-
Notifications
You must be signed in to change notification settings - Fork 751
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 headers are not returned in redirect responses #4606
Comments
Thank you for opening your first issue here 👍. Be sure to follow the issue template if you chose one. |
Hi @dweber019, thanks for raising this issue. Just quickly went through https://developer.mozilla.org/en-US/docs/Web/http/CORS#simple_requests and maybe this is because the request Content-Type is |
Looks like our default set of headers is not returned by Netlify. It is defined here: Line 35 in 4563e9d
But for redirects we have:
|
Will read in detail https://answers.netlify.com/t/access-control-allow-origin-policy/1813/7 when I have some time to see if something can be done about this issue. In the mean time the best solution is, as @dweber019 recommended it in dweber019/backstage-plugins#3, to use a path that will not cause a redirect. |
If a browser is requesting a product with a redirect, because it has been renamed, a CORS error is thrown.
See dweber019/backstage-plugins#3
Calling https://endoflife.date/api/springboot.json behaves differently than calling https://endoflife.date/api/spring-boot.json CORS wise.
The text was updated successfully, but these errors were encountered: