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
So far we have seen it is most common to develop an API with paths relative to root and then add a prefix path to the Gateway. For example, when creating an OrderService with an API at GET /list it could be accessed in a Gateway as GET /order/list. If the OrderService were to have many other API endpoints with different route configurations then StripPrefix=1 would have to be added to each route.
Proposed Solution
Default StripPrefix to 1 instead of its current default of 0. Given that the above Gateway to service API prefix of routes is common approach, this would reduce the need to duplicate StripPrefix=1 across all routes perhaps across a number of route configurations.
The text was updated successfully, but these errors were encountered:
Inconvenience
So far we have seen it is most common to develop an API with paths relative to root and then add a prefix path to the Gateway. For example, when creating an
OrderService
with an API atGET /list
it could be accessed in a Gateway asGET /order/list
. If theOrderService
were to have many other API endpoints with different route configurations thenStripPrefix=1
would have to be added to each route.Proposed Solution
Default
StripPrefix
to1
instead of its current default of0
. Given that the above Gateway to service API prefix of routes is common approach, this would reduce the need to duplicateStripPrefix=1
across all routes perhaps across a number of route configurations.The text was updated successfully, but these errors were encountered: