You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In its examples, the Gateway API uses "foo" in "Prefix Match". However, we can conclude that the HTTPPathModifier should also work on / as the path prefix match.
The PR #5254 PR demonstrates that / is not handled correctly.
Repro steps:
Follow the end-2-end test, which is added in #5254
Environment:
In our environment, we use docker.io/envoyproxy/gateway:v1.3.0. The bug is reproducible in the main branch, and is reproducible in v1.2.5
The text was updated successfully, but these errors were encountered:
Description:
In its examples, the Gateway API uses "foo" in "Prefix Match". However, we can conclude that the
HTTPPathModifier
should also work on/
as the path prefix match.The PR #5254 PR demonstrates that
/
is not handled correctly.Repro steps:
Follow the end-2-end test, which is added in #5254
Environment:
In our environment, we use
docker.io/envoyproxy/gateway:v1.3.0
. The bug is reproducible in themain
branch, and is reproducible inv1.2.5
The text was updated successfully, but these errors were encountered: