kubernetes-sigs / kubernetes-sigs/gateway-api

Custom page for 500, 501, 502, 503, ... HTTP status

Open
#3,763 13 comments 25 reactions 0 assignees View on GitHub
kind/feature
Dominant language
Go
Stars
3k
Forks
789
Avg merge
2d 15h
Merged PRs (30d)
45

Description

**What would you like to be added**:

When the backend returns Server Error (500) we want to change the response page to hide any security sensitive information.

Similarily for Bad Gateway (502), we want to change the error page to something less technical (and different between implementations): a maintenance page.

Same for 503 (Service Unavailable), and maybe others (404 Not Found, ...).

I don't know how to do this. Maybe `responseRules` that can match on response status and filter with a `ResponseBodyModifier`.

envoy is able to do this with [custom_response_filter](https://www.envoyproxy.io/docs/envoy/v1.34.0/configuration/http/http_filters/custom_response_filter).

**Why this is needed**:

We want to hide technical details to users.

Contributor guide

Open the contributing guide

Research direction

The issue names no repository file or test. Start by reviewing the proposed responseRules and ResponseBodyModifier concepts, then compare the Envoy custom_response_filter reference. Done should define an implementable API for replacing selected backend error pages while hiding technical details.

Written by the indexing model from the issue text.

Assessment

Domain
api, networking
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.