API responses are not consistent with different URI paths

Google Cloud Apigee
1

We have an API Proxy with wildcard character in the basepath.

We get a successful call when we make the request with the following URL

[https://<hostalias>/qa/mpi/search](https://<hostalias>/qa/mpi/search)

However, when we make the call with the following URL

[https://<hostalias>/dev/mpi/search](https://<hostalias>/dev/mpi/search)

we get a 404 response with the following error message:

{ "fault": { "faultstring": "Unable to identify proxy for host: secure and url: /dev/mpi/search", "detail": { "errorcode": "messaging.adaptors.http.flow.ApplicationNotFound" } }

Can you help us understand why are we seeing this inconsistent behaviour ?

2
  1. Looking at the URLs and also the Proxy endpoint code it was noticed that the wildcard () character was used as the first element in the basepath (//mpi)
  2. As per the documentation here, it says:
    • Important: Apigee does NOT support using a wildcard “" as the first element of a base path. For example, this is NOT supported: /*/search. Starting the base path with a "” can lead to unexpected errors because of the way Edge identifies valid paths.

So modified the basepath to remove the use of wildcard character as the first element of the basepath to fix the issue. Used the basepath something like this (/v1/*/mpi).