You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Kernel (e.g. uname -a): Linux k8s-master-18117938-0 4.4.0-104-generic #127-Ubuntu SMP Mon Dec 11 12:16:42 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
Install tools: acs-engine
Others:
What happened:
I have an ingress service with CORs enabled. When the ingress upstream does not respond for some reason, the nginx controller returns a 504 gateway timeout as expected. However, the 504 timeout does not contain the required CORs headers to allow the browser code to read the error response.
What you expected to happen:
The 504 error should contain the requested CORS headers.
How to reproduce it (as minimally and precisely as possible):
Create a service that does nothing with the request, to cause a gateway timeout. Configure the ingress with any CORs rules, and enable CORs. Try to make the request.
Anything else we need to know: No
The text was updated successfully, but these errors were encountered:
Is this a request for help? No
What keywords did you search in NGINX Ingress controller issues before filing this one? cors 504 gateway timeout
Is this a BUG REPORT or FEATURE REQUEST? (choose one): BUG REPORT
NGINX Ingress controller version: 0.11.0
Kubernetes version (use
kubectl version
):Environment:
uname -a
):Linux k8s-master-18117938-0 4.4.0-104-generic #127-Ubuntu SMP Mon Dec 11 12:16:42 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
What happened:
I have an ingress service with CORs enabled. When the ingress upstream does not respond for some reason, the nginx controller returns a 504 gateway timeout as expected. However, the 504 timeout does not contain the required CORs headers to allow the browser code to read the error response.
What you expected to happen:
The 504 error should contain the requested CORS headers.
How to reproduce it (as minimally and precisely as possible):
Create a service that does nothing with the request, to cause a gateway timeout. Configure the ingress with any CORs rules, and enable CORs. Try to make the request.
Anything else we need to know: No
The text was updated successfully, but these errors were encountered: