-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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 features improvements #1553
Conversation
Please do not merge yet, need to test this in a production environment. |
I'm just finishing some other tests, maybe tomorrow I'll release this. |
Need some help here. It seems controller is not returning any values to template. Although everything is working 'fine', any value used in ingress is discarded. I've put a comment in here but even setting the right annotation ( Probably is something small that I'm missing. The temporal image is Thanks! |
f2dd452
to
89f18ba
Compare
CORS annotations improvements Cors improvements Cors improevements Cors improvements Cors improvements
89f18ba
to
2097676
Compare
Finished the PR. @aledbf Thanks for the help! |
/lgtm |
@rikatz thanks! |
What this PR does / why we need it: This PR adds new forms to control CORS in a server, allowing user to specify not only if CORS is enabled, but also what are the allowed METHODS, HEADERS, the ORIGIN and credentials behaviour
Which issue this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close that issue when PR gets merged): fixes #1171, fixes #676, fixes #625Special notes for your reviewer:
This PR adds 4 new annotations that allow user to control CORS behaviour in his ingress.
This code inserts some regex validations, as it's not desired that user is allowed to insert values as $nginx_version in allowed methods, as this is going to be returned directly to the final user and can cause an internal information leak, and also Ingress misconfiguration.