You're viewing Apigee Edge documentation.
Go to the Apigee X documentation. info
On Monday, March 20, 2017, we began releasing a new cloud version of Apigee Edge for Public Cloud.
The following bug is fixed in this release. This list is primarily for users checking to see if their support tickets have been fixed. It's not designed to provide detailed information for all users.
|EDGEUI-961||Leave buffer time for calculating token refresh
To prevent calls to Edge from occasionally failing, Edge now checks for and refreshes tokens that are due to expire in the near future, rather than refreshing only those that have expired.
|EDGEUI-954||Proxy editor replacing quotes in conditions with encoded entity
In the proxy editor, quotes are no longer encoded within the
|EDGEUI-952||Trace tool not working when filtered query parameters include special
The Query Parameter filter in the Trace tool works correctly when special characters are specified in the filter.
|EDGEUI-943||Expired /oAuthRefreshToken should not return a 500 error
In the event an OAuth token expires, an 303 HTTP status code is now returned instead of a 5XX server error.
|EDGEUI-942||Node.js Logs page should stop auto-refresh when there is an error
When viewing node.js logs, if an error is encountered, Auto Refresh is disabled automatically. You can re-enable automatic refresh by clicking Start Auto Refresh.
|EDGEUI-941||Issues with error handling and auto logout
Under certain circumstances, when a user needs to re-enter credentials to continue working, the UI does not redirect to the login screen. This issue has been fixed.
|EDGEUI-934||Bundles submitted from proxy editor should be compressed
When you edit a new or existing revision in the proxy editor, a compressed ZIP bundle is now submitted.
Update Apigee Advisory
The Apigee Advisory has been updated as follows:
|EDGEUI-917||Don't wrap 4xx errors as 502
4xx HTTP errors are no longer wrapped as 502 HTTP Bad Gateway errors in the UI.