In order to route correctly the request to the correct backend API in APIcast, we would need to use the Policy Routing of APIcast.

System will inject the policy routing configuration based on the path of each backend api.

In order to solve the issue with sub-pathing of Backend API in a service, there is a need to have ordering of the paths.

So that this configuration would work correctly

• Backend API Bar with path: /foo/bar
• Backend API Foo with path: /foo

Especially the common issue is :

• the customer will have a single default Backend API with path: /
• then adds a Backend API with path /foo

Without the ability to order, the request will always be caught by the default Backend API

One automatic solution for ordering

• Order automatically by the paths: Reverse Lexicographic order

QE Testing suggestion

• Create 2 Backend APIs under a Product with their path correspondingly to /foo and /foo/bar
• Update the proxy configuration
• Ensure that /foo/bar proxy rule is set before /foo proxy rule in the ProxyConfig JSON for APIcast
• test an integration with APIcast and 2 different backends (echo-api and https://docs.postman-echo.com/?version=latest for example)