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
request to the path /api/v1/users/1 can be proxied to the target_url, which is expected.
request to the path /api/v1/users/1/profile now be proxied to the target_url as well, which is not expected.
It seems like the proxy.listen_path behaves like a prefix matching, I would like to know why and I'm wondering if there is a way to define a proxy.listen_path as a exact path.
The text was updated successfully, but these errors were encountered:
@andyo-tyk Hey. The configuration http_server_options.enable_strict_routes does not work for this case. Request to /api/v1/users/1/profile still be proxied to the target_url.
I have an API definition as below:
/api/v1/users/1
can be proxied to the target_url, which is expected./api/v1/users/1/profile
now be proxied to the target_url as well, which is not expected.It seems like the proxy.listen_path behaves like a prefix matching, I would like to know why and I'm wondering if there is a way to define a proxy.listen_path as a exact path.
The text was updated successfully, but these errors were encountered: