envoyproxy/gateway

HTTP route rule processing does not check for DirectResponse or Redirect when filter processing has an error

Open

#9 454 ouverte le 8 juil. 2026

Voir sur GitHub
 (0 commentaires) (0 réactions) (0 assignés)Go (802 forks)auto 404
help wantedkind/bugtriage

Métriques du dépôt

Stars
 (2 871 stars)
Métriques de merge PR
 (Métriques PR en attente)

Description

If you are reporting any crash or any potential security issue, do not open an issue in this repo. Please report the issue via emailing envoy-gateway-security@googlegroups.com where the issue will be triaged appropriately.

Description:

What issue is being seen? Describe what should be happening instead of the bug, for example: The expected value isn't returned, etc.

The processFilterError != nil block in HTTPRoute rule processing (ref) is missing the following check present in GRPCRoute rule processing (ref)

if irRoute.DirectResponse != nil || irRoute.Redirect != nil {
					continue
				}

Repro steps:

Include sample requests, environment, etc. All data and inputs required to reproduce the bug.

Note: If there are privacy concerns, sanitize the data prior to sharing.

Environment:

Include the environment like gateway version, envoy version and so on.

Logs:

Include the access logs and the Envoy logs.

Guide contributeur