On Thursday, March 10, 2016, we released a new version of Apigee Edge for Public Cloud.
New features and enhancements
Following are the new features and enhancements in this release.
Wildcard in API proxy Base
Path
The management UI supports the use of one or more /*/ wildcards in API proxy
base paths. For example, a base path of /team/*/members allows clients to call
your proxy with https://[host]/team/blue/members or
https://[host]/team/green/members without you having to create a new proxy to
support new teams. Note that /**/ is not allowed. (MGMT-3154)
Proxy chaining in Service
Callout policy
To improve API proxy performance by reducing network overhead, the Service Callout policy now
supports local proxy chaining, as described in Chaining API proxies
together. (MGMT-3050)
Bugs fixed
The following bugs are fixed in this release.
Issue ID
Description
MGMT-3158
Apigee RBAC control does not manage API proxies access
effectively
MGMT-3142
Issue with Error Analysis page
MGMT-3118
UI displays incorrect SSL virtual host config for "clientAuthEnabled"
parameter
DEVRT-2344
Single-day report definitions don't load transactions in UI
