You're viewing Apigee Edge documentation.
Go to the
Apigee X documentation. info
On Tuesday, June 9, 2015, we released a new cloud version of Apigee Edge.
If you have questions, go to Apigee Customer Support.
For a list of all Apigee Edge release notes, see Apigee Release Notes.
New features and enhancements
Following are the new features and enhancements in this release.
GeoMap analytics dashboard usability
The analytics GeoMap provides clearer visual indicators for drilling down on specific areas of the map.
Developer Engagement widget performance
The funnel widget on main analytics dashboard (Developer Engagement section) has been enhanced to provide better performance.
Classic Trace in API proxy editor
The newest version of Trace functionality in the API proxy editor has moved from beta to general availability. Access to "classic trace" with the "Access the classic version of trace" link is no longer available.
Threat protection error configuration
By default, Edge throws an HTTP 500 Internal Server Error status code and an ExecutionFailed
error if a message doesn't make it past a JSON or XML Threat Protection policy. You can change
that error behavior with a new organization-level property. When setting org property
features.isPolicyHttpStatusEnabled to true, the following behavior occurs:
- Request: With a threat protection policy attached to any request flow, invalid messages return a 400 status code, along with a corresponding policy error message.
- Response: With a threat protection policy attached to any response flow, invalid messages still return a 500 status code, and one of the corresponding policy error messages is thrown (rather than just ExecutionFailed).
Cloud customers must contact Apigee Support to set the organization property. This feature will be available to Edge Private Cloud customers at the next Private Cloud quarterly release.
UI performance and error enhancements
General enhancements were made to different areas of the management UI, including page display performance and error message cleanup.
Future feature changes and enhancements
This section previews expected future feature changes and enhancements:
Change to Response Cache policy behavior
Coming in a future release (to be determined), the default behavior of the <ExcludeErrorResponse> element of the Response Cache policy will change.
Current behavior: The element <ExcludeErrorResponse> in the response cache policy is false by default. This means that, by default, responses with any possible HTTP status code (including 3xx) are cached by the Response Cache policy.
Future behavior: The element <ExcludeErrorResponse> in the Response Cache policy will default to true. This means that, by default, only responses with HTTP Status codes 200 to 205 will be cached. To override this behavior and to cache responses for all status codes, you will need to set the element <ExcludeErrorResponse> to true explicitly.
Current workaround: For release 150610 and older releases, if you want to cache responses only with the Status codes 200 to 205, you must explicitly set the element <ExcludeErrorResponse> to true.
Bugs fixed
The following bugs are fixed in this release.
| Issue ID | Description |
|---|---|
| MGMT-2246 | Create custom report page is not being displayed correctly in management UI |
| MGMT-2193 | Loading spinner when editing an API |
| MGMT-2162 | JavaScript compilation issue |
| MGMT-2114 | Invalid Syslog IP in MessageLogging policy should throw proper error during deployment |
| MGMT-1843 | API Proxy Won't Open |
| MGMT-1193 | Saving proxy as new revision unexpectedly changes route rule |
| MGMT-619 | Activate pagination in the API proxy UI page |
| AXAPP-1707 | Enhance free pod analytics performance |
| APIRT-1148 | GET of {message.version} variable in ResponseFlow, for a Node.js target throws NPE |