Edge Microgateway Aware API Proxy using wildcard

pengdu30 · 03-10-2019 11:56 AM

Based on the Apigee Document Using wildcards in Microgateway-aware proxies the feature supported in v2.4.x, I could not find any apiproxy example to see how this works, especially not clear how should target URL to be configured when wildcard presented in basePath:

For example, if basePath is /team/*/members as the document, what should target URL should be configured for the apiproxy:

https://[host]/team/ or https://[host]/team/*/members or something else?

in order to support following request as per document:

https://[host]/team/blue/members

https://[host]/team/green/members

Appreciate any feedback? Thanks.

pengdu30

Did some testing and found out this feature is not working for the above scenario. The issue is the target URL does not support wildcard. One scenario it works is if the wildcard is the last section of the basePath. In order to support the above scenario using wildcard, not sure if custom plugin is the only option available.

pengdu30

checked the source code (microgateway-core/lib/config-proxy-middleware.js) on GitHub repo, I think if the feature suppose to be supported by microgateway, it will require code fix to make the scenario while wildcard is in the middle of the basePath to work. This should be the better option compare to add a customized plugin to handle this.

pengdu30

Wildcard support is a common needs for API Proxy to access backend Restful APIs for most large organizations. I will debug more and will submit the pull request for the fix of this issue. Without this we would not be able to support some of our APIs to use Edge Microgateway.