envoyproxy/gateway

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

Open

#9.454 geöffnet am 8. Juli 2026

Auf GitHub ansehen
 (0 Kommentare) (0 Reaktionen) (0 zugewiesene Personen)Go (802 Forks)auto 404
help wantedkind/bugtriage

Repository-Metriken

Stars
 (2.871 Stars)
PR-Merge-Metriken
 (PR-Metriken ausstehend)

Beschreibung

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.

Contributor Guide