You're viewing Apigee Edge documentation.
View Apigee X documentation.
On the following dates, we began releasing component updates to Apigee Edge for Public Cloud:
- Router: Monday, May 31, 2021
- Management Server: Tuesday, June 15, 2021
- Message Processor: Wednesday, June 30, 2021
Help & notifications
Private Cloud customers: Is this cloud release included in your Private Cloud version? See your version's release notes to see which cloud releases it contains. Also, see About release numbering to understand how you can figure it out by comparing release numbers.
Questions or issues? Get help here.
Release notifications: Go to http://status.apigee.com and click Subscribe to Updates.
New features and updates
Following are the new features and updates in this release.
New org-level flag to restrict user permissions for Audits resource
A new org-level flag was added:
isAuditEnabledOnlyForOrgAdmin. If this flag
is set to
true for a specific org, then only OrgAdmin users can access
the Audits resource. This feature allows customers to turn off audits for all user roles
except OrgAdmin. Default is the existing behavior.
identity transfer encoding is no longer supported
Transfer-Encoding: identity will now receive an HTTP 501 response.
New property for Message Processor
We have introduced a new property for Message Processor that you can use to configure
proxy forwarding to a backend server:
conf_http_HTTPClient.use.proxy.host.header.with.target.uri. The property sets
the target host and port as a HOST header.
Health Check ID Header
When using a HealthMonitor, and specifically an HTTP Monitor, it is now possible to configure the health check requests to include an HTTP Header with a well-known name, which gets a unique, dynamically assigned value for each health check request.
Support for property sets in Apigee Edge
Property sets are now supported in Apigee Edge. See Using property sets.
The following bugs are 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.
|Issue ID||Component Name||Description|
An issue was fixed where a 409 HTTP status was returned in some cases when trying to fetch audit logs.
An issue was fixed where the request body was not logged correctly for some requests in audit logs.
An issue was fixed where if an OpenAPI definition did not return valid JSON or YAML, an exception was thrown that exposed parts of the target response.
An issue was fixed where users were able to assign user roles to their accounts, allowing access to orgs they did not own. With this fix, such operations are not allowed.
An issue was fixed where users could not update existing KVM entries whose names started with '/'. This change allows such updates.
An issue was fixed where it was possible for the revision numbers of removed proxy revisions to be persisted. This fix allows users to forcibly remove those dangling revision numbers.
An issue was fixed where the flow variable
An issue was fixed where setting
A Service Callout policy issue was fixed so that when
Additional checks were added during KVM creation to validate if the specified environment exists.
An issue was fixed where messages containing newlines logged over
An issue was fixed where the Health Monitor ignored the value of
Now the value of
Prevent accidental modification of an object in the L1 cache.
When an object is placed or retrieved to or from the L1 cache, a copy is placed or retrieved instead.
An issue was fixed that caused the entire Message Processor bootstrap to fail when trying to load a corrupt jar file.
Stale value in KVM after expiry is decreased.
An issue was fixed where
RaiseFault validates the Name in any AssignVariable
When the RaiseFault policy includes an AssignVariable element, the policy now validates that the Name is non-empty.
The HMAC policy now correctly handles the case when the referenced variable for the Message element is unset: it throws a Fault with a message indicating that a referenced variable cannot be resolved.
An issue was fixed where client certificates were not sent, even though
An issue was fixed where non-string JSON values in payloads were converted to strings in the Debug tool.
The flow variable
The flow variable
An issue was fixed where a proxy with the AssignMessage policy failed to deploy when a name was not specified for headers and other elements.
Prevent two policies from executing in parallel.
In some limited cases, if the Message Processor encountered an error in the target response, it could allow two or more policies to execute in parallel. This would appear in the Debug tool as policies executing out of order or in the wrong flow.