-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Enable CORS #121
Comments
@g3gurung
|
I'm adding support for CORS. I hope to create a Pull Request this week. The annotations I'm creating are 'nginx.org/cors-domains' and 'nginx.org/cors-enabled'. If just cors-enabled is defined, it'll allow all "*" Origins. Defining 'cors-domains' will act as a domain whitelist. I was going to add this to the server block rather than the location block. We can change 'nginx.org' to 'ingress.kubernetes.io' if that's better. Does this sounds like a good solution? |
@bporter2387 It is important that all
|
I created PR #144 . I added a 401 on non-whitelisted domains. Not sure if this ideal, but I noticed our upstream endpoints are still hit from non-whitelisted Origins unless I had this 401 in place. However, in browsers I still got the CORS error without the 401, so that's good. |
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days. |
This issue was closed because it has been stalled for 7 days with no activity. |
I have successfully added
and I tried to use cors by adding another annotation like this but it is not working
ingress.kubernetes.io/enable-cors: "true"
Is there some other way to enable cors!
The text was updated successfully, but these errors were encountered: