-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
502 Bad gateway in html format #927
Comments
This will require a configuration change and can land in 0.7.0. I will work on it. |
This was referenced Feb 9, 2016
I would be nice if one could configure an error page per API. Maybe even per status code and having a catch all. Of course if those pages fail, one could still show the current error page, but it would at least allow a little bit more customisation. |
Thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Kong version: 0.6.0
If upstream is unreachable Nginx returns a bad gateway response in HTML format. IMO a JSON response would be better.
Thank you for this great product!
The text was updated successfully, but these errors were encountered: