DevFW-CICD/ingress-nginx-helm
6
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Revert "feat: multiple-cors-allow-origin support (#7134)" (#7168)

Browse source 
This reverts commit 8a55801cc0.
This commit is contained in:
Ricardo Katz 2021-05-27 09:38:24 -03:00 • committed by GitHub
parent 68ec350388
commit 11d4ddca8e
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
4 changed files with 7 additions and 31 deletions
Download patch file Download diff file Expand all files Collapse all files

6
docs/user-guide/nginx-configuration/annotations.md
View file

@ -348,10 +348,10 @@ CORS can be controlled with the following annotations:
- Example: `nginx.ingress.kubernetes.io/cors-expose-headers: "*, X-CustomResponseHeader"`
* `nginx.ingress.kubernetes.io/cors-allow-origin`
controls which Origin(s) are allowed for CORS.
This is a multi-valued field, separated by ',', each value should obey the following format: `http(s)://origin-site.com` or `http(s)://origin-site.com:port`
controls what's the accepted Origin for CORS.
This is a single field value, with the following format: `http(s)://origin-site.com` or `http(s)://origin-site.com:port`
- Default: `*`
- Example: `nginx.ingress.kubernetes.io/cors-allow-origin: "https://origin-site.com:4443, https://origin-site-2.com"`
- Example: `nginx.ingress.kubernetes.io/cors-allow-origin: "https://origin-site.com:4443"`
* `nginx.ingress.kubernetes.io/cors-allow-credentials`
controls if credentials can be passed during CORS operations.