Support custom 502 error page [36407571]

Verified

Feature Request

Status Update

No update yet.

Description

pp...@paradisemarketing.com

created issue #1

Mar 18, 2017 06:15AM

When all backends are down, the L7 load balancer displays a very boring, non-customizeable error page. I'd like for there to be a way to display a custom static error page instead.

Comments

pa...@google.com <pa...@google.com> #2Mar 20, 2017 07:16PM

Thanks for this request. It seems well-formed and concise, and I'll forward this to specialists for the L7 Load Balancer.

pa...@google.com <pa...@google.com> Mar 27, 2017 07:38PM

Accepted by pa...@google.com.

mo...@gmail.com <mo...@gmail.com> #3Apr 5, 2017 09:09AM

It would be nice if the Content-Type can be specified too.

We have an API endpoint that is load balanced, and it would be nice if we can return JSON with an "application/json" media type to clients in case the backend becomes unavailable.

ja...@panopta.com <ja...@panopta.com> #4Nov 14, 2017 03:38PM

This is a significant issue for us - is there any ETA on when this support might be available?

ra...@gmail.com <ra...@gmail.com> #5Feb 16, 2018 03:21AM

I'd say this is a feature request and it would be a nice addition to LB.

is...@google.com <is...@google.com> May 11, 2018 07:59PM

Status: New

fa...@google.com <fa...@google.com> Jul 19, 2018 04:04PM

Assigned to gc...@google.com.

hi...@gmail.com <hi...@gmail.com> #6Dec 27, 2018 12:39PM

In GCS bucket, we want to skip to the custom error page on GCS when 503 occurs

br...@hotpads.com <br...@hotpads.com> #7Oct 18, 2019 01:13AM

Could there at least be some documentation about this limitation? it's an unpleasant discovery otherwise

[Deleted User] <[Deleted User]> #8Dec 2, 2020 05:36PM

Are there any updates on this feature request? We would also like to update the static error page that the load balancer serves when all backends are down

na...@opendr.com <na...@opendr.com> #9Mar 27, 2021 06:44AM

Error: Server Error
The server encountered a temporary error and could not complete your request
Please try again in 30 seconds

Who wants to see a blunt error page with a try after 30 sec, it is shameful as a developer, Please provide a solution for the custom error page.

Thanks
-nisar

ad...@gmail.com <ad...@gmail.com> #10Jun 9, 2021 05:21AM

+1 on this feature request. I'd love this.

lc...@fmlogistic.com <lc...@fmlogistic.com> #11Jun 15, 2021 07:18AM

se...@google.com <se...@google.com> Jun 21, 2021 08:33AM

Reassigned to gc...@google.com.

mi...@getharvest.com <mi...@getharvest.com> #12Oct 8, 2021 10:36AM

li...@google.com <li...@google.com> #13Nov 12, 2021 05:58AM

Comment has been deleted.

Message last modified on Mar 9, 2023 02:54AM

ag...@google.com <ag...@google.com> #14Jan 18, 2022 09:00AM

Comment has been deleted.

Message last modified on Mar 9, 2023 02:55AM

va...@novozhenov.com <va...@novozhenov.com> #15Jan 18, 2022 12:03PM

Comment has been deleted.

Message last modified on Jan 18, 2022 12:04PM

pe...@afosto.io <pe...@afosto.io> #16May 17, 2022 07:59AM

[Deleted User] <[Deleted User]> #17Jul 18, 2022 07:41PM

+1 on this feature, it's very important for us to be able to return JSON instead of HTML.

gr...@gmail.com <gr...@gmail.com> #18Jul 19, 2022 04:49PM

In light of today's Google Could outage in London UK, we could definitely use this feature to better manage the user experience for high traffic websites when these experience downtime.

mi...@gdplabs.id <mi...@gdplabs.id> #19Oct 2, 2022 06:25AM

Message last modified on Oct 2, 2022 06:26AM

ab...@k-mino.com <ab...@k-mino.com> #20Oct 24, 2022 05:13PM

bo...@gmail.com <bo...@gmail.com> #21Dec 1, 2022 10:32AM

+1 on that.

[Deleted User] <[Deleted User]> #22Dec 15, 2022 04:40AM

jo...@tab32.com <jo...@tab32.com> #23Dec 29, 2022 11:31PM

We have planned downtime during the yearend holidays (in the us) and the smoothest way I can see to do that is reducing cluster size to 0 and showing a custom maintenance page.

So yea: +1

re...@gmail.com <re...@gmail.com> #24Feb 28, 2023 05:54PM

ra...@gcp.entel.cl <ra...@gcp.entel.cl> #25Mar 7, 2023 04:29PM

at...@zoominfo.com <at...@zoominfo.com> #26May 11, 2023 02:50PM

Message last modified on May 11, 2023 02:51PM

jo...@ackstorm.com <jo...@ackstorm.com> #27Jun 13, 2023 12:13PM

du...@meucrediario.com.br <du...@meucrediario.com.br> #28Jun 29, 2023 10:33PM

[Deleted User] <[Deleted User]> #29Jul 3, 2023 11:19AM

This one would be useful. We block or throttle many requests at the moment. Additionally when backends are not working for any reason, we want to show a user friendly error page rather than letting people know error code and error details. This one will help us. Please check and see if this can be added as a feature in the external HTTPs LB.

f....@haut.ai <f....@haut.ai> #30Jul 7, 2023 06:08PM

It would be great to see this feature!

g....@linqhost.nl <g....@linqhost.nl> #31Jul 25, 2023 08:25AM

Howdy! This feature is requested multiple times from our customers. I found https://saturncloud.io/blog/how-to-change-the-default-html-page-for-server-error-on-google-cloud-lb/ but I don't know what kind of release channel they are using, but I cannot find the options they are talking about, also not in the documentation. So i'm not sure how they are doing this :-)

la...@gmail.com <la...@gmail.com> #32Jul 25, 2023 11:50AM

Seems like something is coming - I think the mentioned fields are what we can see in the beta API documentation for url maps: https://cloud.google.com/compute/docs/reference/rest/beta/urlMaps/insert (look for defaultCustomErrorResponsePolicy). However, this says "defaultCustomErrorResponsePolicy specifies how the Load Balancer returns error responses when BackendService or BackendBucket responds with an error" - not sure if this will cover also the errors described here where no backends are available.

[Deleted User] <[Deleted User]> #33Jul 31, 2023 06:30AM

+1, would love this feature getting done

pr...@gmail.com <pr...@gmail.com> #34Oct 12, 2023 06:03AM

If this feature get implemented for all kind of load balancer, it will be great.

os...@transcarent.ai <os...@transcarent.ai> #35Dec 8, 2023 09:53PM

jr...@challiance.org <jr...@challiance.org> #36Jan 4, 2024 03:21AM

na...@mgb.ch <na...@mgb.ch> #37Feb 2, 2024 11:48AM

ma...@visma.com <ma...@visma.com> #38Feb 23, 2024 12:58PM

zb...@visma.com <zb...@visma.com> #39Feb 23, 2024 01:30PM

pe...@skyone.solutions <pe...@skyone.solutions> #40Mar 6, 2024 07:06PM

de...@db.com <de...@db.com> #41Mar 26, 2024 11:54AM

zb...@primitybio.com <zb...@primitybio.com> #42May 26, 2024 04:56AM

This is now pre-GA:

https://cloud.google.com/load-balancing/docs/https/custom-error-response

me...@google.com <me...@google.com> #43Oct 5, 2024 05:43AM

Verified by me...@google.com.

This feature is now GA

https://cloud.google.com/load-balancing/docs/https/custom-error-response

-- GCP Load Balancing Team

Issue 36407571

Description

Issue summary

Comments

pa...@google.com <pa...@google.com> #2Mar 20, 2017 07:16PM

pa...@google.com <pa...@google.com> Mar 27, 2017 07:38PM

mo...@gmail.com <mo...@gmail.com> #3Apr 5, 2017 09:09AM

ja...@panopta.com <ja...@panopta.com> #4Nov 14, 2017 03:38PM

ra...@gmail.com <ra...@gmail.com> #5Feb 16, 2018 03:21AM

is...@google.com <is...@google.com> May 11, 2018 07:59PM

fa...@google.com <fa...@google.com> Jul 19, 2018 04:04PM

hi...@gmail.com <hi...@gmail.com> #6Dec 27, 2018 12:39PM

br...@hotpads.com <br...@hotpads.com> #7Oct 18, 2019 01:13AM

[Deleted User] <[Deleted User]> #8Dec 2, 2020 05:36PM

na...@opendr.com <na...@opendr.com> #9Mar 27, 2021 06:44AM

ad...@gmail.com <ad...@gmail.com> #10Jun 9, 2021 05:21AM

lc...@fmlogistic.com <lc...@fmlogistic.com> #11Jun 15, 2021 07:18AM

se...@google.com <se...@google.com> Jun 21, 2021 08:33AM

mi...@getharvest.com <mi...@getharvest.com> #12Oct 8, 2021 10:36AM

li...@google.com <li...@google.com> #13Nov 12, 2021 05:58AM

ag...@google.com <ag...@google.com> #14Jan 18, 2022 09:00AM

va...@novozhenov.com <va...@novozhenov.com> #15Jan 18, 2022 12:03PM

pe...@afosto.io <pe...@afosto.io> #16May 17, 2022 07:59AM

[Deleted User] <[Deleted User]> #17Jul 18, 2022 07:41PM

gr...@gmail.com <gr...@gmail.com> #18Jul 19, 2022 04:49PM

mi...@gdplabs.id <mi...@gdplabs.id> #19Oct 2, 2022 06:25AM

ab...@k-mino.com <ab...@k-mino.com> #20Oct 24, 2022 05:13PM

bo...@gmail.com <bo...@gmail.com> #21Dec 1, 2022 10:32AM

[Deleted User] <[Deleted User]> #22Dec 15, 2022 04:40AM

jo...@tab32.com <jo...@tab32.com> #23Dec 29, 2022 11:31PM

re...@gmail.com <re...@gmail.com> #24Feb 28, 2023 05:54PM

ra...@gcp.entel.cl <ra...@gcp.entel.cl> #25Mar 7, 2023 04:29PM

at...@zoominfo.com <at...@zoominfo.com> #26May 11, 2023 02:50PM

jo...@ackstorm.com <jo...@ackstorm.com> #27Jun 13, 2023 12:13PM

du...@meucrediario.com.br <du...@meucrediario.com.br> #28Jun 29, 2023 10:33PM

[Deleted User] <[Deleted User]> #29Jul 3, 2023 11:19AM

f....@haut.ai <f....@haut.ai> #30Jul 7, 2023 06:08PM

g....@linqhost.nl <g....@linqhost.nl> #31Jul 25, 2023 08:25AM

la...@gmail.com <la...@gmail.com> #32Jul 25, 2023 11:50AM

[Deleted User] <[Deleted User]> #33Jul 31, 2023 06:30AM

pr...@gmail.com <pr...@gmail.com> #34Oct 12, 2023 06:03AM

os...@transcarent.ai <os...@transcarent.ai> #35Dec 8, 2023 09:53PM

jr...@challiance.org <jr...@challiance.org> #36Jan 4, 2024 03:21AM

na...@mgb.ch <na...@mgb.ch> #37Feb 2, 2024 11:48AM

ma...@visma.com <ma...@visma.com> #38Feb 23, 2024 12:58PM

zb...@visma.com <zb...@visma.com> #39Feb 23, 2024 01:30PM

pe...@skyone.solutions <pe...@skyone.solutions> #40Mar 6, 2024 07:06PM

de...@db.com <de...@db.com> #41Mar 26, 2024 11:54AM

zb...@primitybio.com <zb...@primitybio.com> #42May 26, 2024 04:56AM

me...@google.com <me...@google.com> #43Oct 5, 2024 05:43AM

Add comment

Issue metadata