Right now we are using PostgreSQL-style pattern matching with % and _, even trough it works, there are some limits and features that we want to support:
We want to match paths /some_api and /some_api/123 as different APIs. Current workaroung is defining /some_api_ and /some_api/_% with different match_priority. It looks ugly and will match /some_api1, which will unexpected for most users.
It would be really awesome to take parts of request and substitute them to upstream path. Eg: /blog/:id/comments -> /comments/:id.
Right now we are using PostgreSQL-style pattern matching with
%
and_
, even trough it works, there are some limits and features that we want to support:We want to match paths
/some_api
and/some_api/123
as different APIs. Current workaroung is defining/some_api_
and/some_api/_%
with different match_priority. It looks ugly and will match/some_api1
, which will unexpected for most users.It would be really awesome to take parts of request and substitute them to upstream path. Eg:
/blog/:id/comments
->/comments/:id
.Regex matching is expensive.