-
Notifications
You must be signed in to change notification settings - Fork 278
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
Add custom error page for unavailable upstream #4761
Comments
Hi @dennissetiawan, as a first step we'll change the default behavior to return an HTML error page — basically option (2) as you've listed above. |
What's news here ? shall we use |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
This is related to envoy issues that previously blocked this. (envoyproxy/envoy#1178) But the issue has been resolved recently.
Describe the solution you'd like
I need to have a custom page for upstreams service that returns unavailable (503) error code.
So in case of unavailable service we can choose to :
Additional Context
It's great if we can configure the solutions at route level also
The text was updated successfully, but these errors were encountered: