On Thursday, September 18, 2014, we released a new cloud version of Apigee Edge.
New features and enhancements
Following are the new features and enhancements in this release.
- Rules and Alerts - A rule lets you specify a condition that, when it evaluates to true, generates an alert.
- Virtual Dimensions - User-agents, timestamps, and IP addresses are automatically mapped to dimensions such as OS version, device family, day of the week, city, country, and timezone.
- Newly designed interface for Custom Reports (Beta)
- Support for Apigee 127 built proxies
- "/" resource on productsAPIRT-667
When you add a resource to an API product as a single forward slash "/", by default Apigee treats it the same as "/**", which gives developers access to all URIs under the base path. A new organization-level
features.isSingleForwardSlashBlockingEnabledproperty lets you change the default behavior of "/". By changing the property to "true" (cloud customers must contact Apigee Support to do this), "/" gives developers access to only the base path as a resource.
For more information, see Configuring the behavior of a Resource Path.
HTTP response error configuration for Quota and Spike ArrestAPIRT-664
Apigee Edge organizations can now be configured to return an HTTP status code of 429 (Too Many Requests) for all requests that exceed a rate limit set by a Quota or Spike Arrest policy. The default configuration returns an HTTP status code of 500 (Internal Server Error).
Contact Apigee Support to have the
features.isHTTPStatusTooManyRequestEnabledproperty set to true for organizations for which you want Quota and Spike Arrest violations to return an HTTP status code of 429.
The following bugs are fixed in this release.
|204 error on missing key in Key Value Map
|The absence of a key in a Key Value Map returned an HTTP response of 204 (No Content) instead of the expected 404 (Not Found). This issue has been fixed to return a 404.|
|Permissions for user in multiple roles
|Permissions for a user assigned to two or more roles were not being combined correctly. This issue has been fixed.|
|Lowercase character set encoding on policies
|In a policy XML configuration, setting character encoding with lowercase "utf-8" or "utf-16" caused policies to fail. This issue has been fixed to support both lower- and uppercase encoding.|