Skip to content
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

Closed
codebien opened this issue Feb 1, 2016 · 4 comments
Closed

502 Bad gateway in html format #927

codebien opened this issue Feb 1, 2016 · 4 comments
Assignees

Comments

@codebien
Copy link

codebien commented Feb 1, 2016

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!

@codebien codebien closed this as completed Feb 1, 2016
@codebien codebien reopened this Feb 1, 2016
@subnetmarco subnetmarco self-assigned this Feb 3, 2016
@subnetmarco
Copy link
Member

This will require a configuration change and can land in 0.7.0. I will work on it.

@elruwen
Copy link

elruwen commented 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.

@subnetmarco
Copy link
Member

Once this issue is closed, a next iteration on the feature could include what @elruwen is suggesting. I opened #972 to keep track of this.

@elruwen
Copy link

elruwen commented Feb 10, 2016

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants