-
Notifications
You must be signed in to change notification settings - Fork 270
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-allow-origin - use more than 1 URL #477
Comments
Hi, from this mdn doc:
So it sounds you can only use one origin or a wildcard |
Hi. Big thanks for this. Should have been more attentive.Thanks for link |
FYI, nginx is going to support it. They are fixing a bug now |
I would like a link to the confirmation of this |
@hAh0L13 can't believe I forgot to paste the link kubernetes/ingress-nginx#5496 |
How one would implement this? It's technically pretty simple but it's apparently unsupported? https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS/Errors/CORSMultipleAllowOriginNotAllowed It seems to me that I cannot add more than one header and this one should have one origin or a wildcard. |
It looks like the solution is in a conditional block where CORS headers are configured on the fly based on a compare origin domain with list of allowed domains. |
Ah sure, a dynamic response based on the request. It seems promising, will have a look on this. |
Just to let you know added to |
Hello all.
We use HAProxy-ingress 0.7.2 in our cluster (OKD, openshift)
Can I use two or more URLs in ingress annotation ingress.kubernetes.io/cors-allow-origin ?
If I adding two annotations, it use last applied. If I adding list of URLs delimited by comma, controller switch header to any - "*"
Docs didn't cover this case
The text was updated successfully, but these errors were encountered: