Verified
Status Update
Comments
kh...@google.com <kh...@google.com>
lu...@webranking.it <lu...@webranking.it> #2
I agree with request
bu...@aframesoftware.com <bu...@aframesoftware.com> #3
+1 The ability to customize the error page seems like it should have been part of the original spec. For example, there is no way to give the user a message during a "planned upgrade" that might have a short window of downtime. There are many other scenarios where displaying a custom message makes more sense than the one that is currently displayed.
ad...@gmail.com <ad...@gmail.com> #4
Thank you
sa...@google.com <sa...@google.com>
sa...@google.com <sa...@google.com>
os...@transcarent.ai <os...@transcarent.ai> #6
+1 (also +1ed the semi-duplicate issue)
Description
Please provide as much information as possible. At least, this should include a description of your issue and steps to reproduce the problem. If possible please provide a summary of what steps or workarounds you have already tried, and any docs or articles you found (un)helpful.
What you expected to happen:
Provide customers the ability to customize the error pages returned by the HTTP(S) LBs when they are unable to forward requests to backends, either due to server (5xx) or client (4xx) errors.
Typical use case:
Customers would like to customize these pages to align with company identity and/or branding