HTTPRoute Filter not applying #5059
Replies: 1 comment 1 reply
-
We were able to resolve this by replacing the PrefixMatch filter with a Regex filter. We also had to create a second filter with the exact same functionality and only a different name, otherwise we'd receive the error: "Cannot configure multiple urlRewrite filters for a single HTTPRouteRule". It is very strange that the same filter cannot be applied to two distinct routes. Without this silly fix, we could only create one of the two routes. Creating the second one would lead to this error message. This looks like a bug to us. Even the error message is totally misleading, because the problem was not "multiple filters for the same rule", but "the same filter for two routes". When the situation became "two distinct filters for two distinct routes" the problem was resolved. So now the working YAML is this:
|
Beta Was this translation helpful? Give feedback.
-
We'd appreciate your help with this:
Using version 1.2.1, we have this somewhat complex HTTPRoute definition that differentiates between HTTP methods. We have confirmed that the filters we define do not actually apply to the traffic and therefore the request is received by the backend with the full initial prefix, even though the route is accepted/validated. What are we doing wrong?
The first block below shows the route that fails, and the second block shows a simpler route (all methods treated the same) where the filter is applied as expected.
Beta Was this translation helpful? Give feedback.
All reactions