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
{{ message }}
This repository has been archived by the owner on Apr 17, 2019. It is now read-only.
It seems to me right now there is no way to configure the nginx ingress controller to not intercept errors and serve them from the default/error backend.
In our case this is problematic. Our backends serve meaningful error pages for 500 errors which contain exception ids which help us debugging problems when customers create support requests.
We also have a JSON API backend where 404 error contain additional information that help api clients to fail more gracefully.
How about adding an option to (potentially partially) disable the error interception ?
I can submit an initial PR of this would be considered useful.
The text was updated successfully, but these errors were encountered:
databus23
changed the title
Nginx Ingress Controller - Option to disable nginx error pages
Nginx Ingress Controller - Option to disable interception of errors
May 4, 2016
@aledbf Ups missed that one. Ok, so 500 errors should work, I actually never tested this. But we have had problems with 404 and 403 errors where backend developers where unhappy that there response didn't get served to the client. For a start I would like a global flag to have nginx not mingle any responses. Having this configurable per error or even per backend would be nice to have.
It seems to me right now there is no way to configure the nginx ingress controller to not intercept errors and serve them from the default/error backend.
In our case this is problematic. Our backends serve meaningful error pages for 500 errors which contain exception ids which help us debugging problems when customers create support requests.
We also have a JSON API backend where 404 error contain additional information that help api clients to fail more gracefully.
How about adding an option to (potentially partially) disable the error interception ?
I can submit an initial PR of this would be considered useful.
The text was updated successfully, but these errors were encountered: