Replies: 3 comments 1 reply
-
|
cc @guydc |
Beta Was this translation helpful? Give feedback.
-
|
We previously had an issue where mixing extended HTTPRouteFilters with built-in filters on the same route led to some of them being ignored: #6557. This was fixed in 1.5. |
Beta Was this translation helpful? Give feedback.
-
|
I do some test on version v1.5.3 with httbin as backend : Simple test with credentials injection and host rewrite response is : Api-Key is injected and host is rewrite Test with JWT and routing with client name, credentials injection and host rewrite response is : Host is still rewrite but Api-Key is NOT injected |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
I have a backend secured by api key. Two clients want to call this backend using their own api key. So I'm using a Security policy to authenticate the caller (field in auth token) and put the value in a header. This header is used to call the good rule based on the path and the value of the header. In each rule, I put a filter to inject the good credential for the client.
When I call the api, I get a 401 Unauthorized because no credentials are injected but if I put client1-host-rewrite filter on the "catch all" rule, I get a 200 OK. It's like the urlRewrite part of the custom client rule work but not the HTTPRouteFilter ExtensionRef part.
version : v1.4.1
Beta Was this translation helpful? Give feedback.
All reactions