You're viewing Apigee Edge documentation.
Go to the
Apigee X documentation. info
On Friday, July 24, 2015, we released a new version of Apigee Edge.
New features and enhancements
Following are the new features and enhancements in this release.
Target flow variables are not populated correctly for inline Target and TargetServers
New variables in message flows provide more complete URL information for target endpoints and target servers:
- TargetEndpoint: request.url replaces target.basepath.with.query.
- TargetServer: loadbalancing.targetserver replaces targetserver.name. Also, target.basepath is populated only when the <Path> element is used in the TargetEndpoint's HTTPTargetConnection <LoadBalancer> element. (APIRT-1050)
Edge UI requires Java JDK 1.7
The Edge UI component requires Java JDK 1.7. Before you install this version of Edge, upgrade your servers to use Java JDK 1.7.
If you have already installed this version of Edge, you can change the version of the JDK used by Edge by following this procedure.
Bugs fixed
The following bugs are fixed in this release.
| Issue ID | Description |
|---|---|
| MGMT-2418, TBD-90 | UI config apigee.conf does not support TLS |
| MGMT-2255 | Management server self checks are failing after system password change |
| MGMT-1677 | Log authentication failure and authorization failures in debug |
| CORERT-318 | HTTPServer.streaming.buffer.limit=10 caused intermittent hung
requests While dealing with slow clients and large payloads occasionally the requests would hang and time out from the router. This issue was seen only when the router had the HTTPServer.streaming.buffer.limit property set to a non zero value. The issue has been fixed. |
| APIRT-1766 | Timeouts on WebSockets |
| APIRT-1472 | Messages on system.log every time a health check API is invoked |
| APIRT-1147 | Proxy streaming data from S3 bucket no longer completes download |