1.3.1 - Apigee hybrid runtime release notes

On August 24, 2020, we released Apigee hybrid runtime version 1.3.1.


Upgrade is supported to Apigee hybrid version 1.3.1.

Apigee hybrid version 1.3.0 to version 1.3.1

To upgrade from hybrid version 1.3.0 to version 1.3.1, download the new hybrid runtime, and run apigeectl init and apigeectl apply.

PlatformDownload hybrid runtime
Mac 64 bit
curl -LO \
Linux 64 bit
curl -LO \
Mac 32 bit
curl -LO \
Linux 32 bit
curl -LO \

Apigee hybrid version 1.2.0 to version 1.3.1

To upgrade from hybrid version 1.2.0 to version 1.3.1 follow the instructions in Upgrading Apigee hybrid to version 1.3.1.

Apigee hybrid version 1.1.1 or older to version 1.3.1

If you are upgrading from Apigee hybrid version 1.0 or 1.1, you must first upgrade to hybrid version 1.2 before upgrading to version 1.3.1. See the instructions for Upgrading Apigee hybrid to version 1.2.

New features and updates

This section describes the new features and enhancements in this release.

New command line tool, tools/cas_cleanup.sh

The tools/cas_cleanup.sh tool helps clean up and decommission previous Cassandra instances upon completing the upgrade from hybrid version 1.2.0 to version 1.3.1. See Upgrading Apigee hybrid to version 1.3.1.

For new features and changes introduced in Apigee hybrid version 1.3.0, see the 1.3.0 - Apigee hybrid runtime release notes

Bugs fixed

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 Description
162759110 Base paths consisting of only "/" would fail. Base paths of "/" are now supported.
162772922 Incorrect deployment of fluentd controller caused wrong configuration input to log agent causing it to error out.
165198951 GKE On Prem - Synchronizer failing to connect to apigee.googleapis.com when HTTP_PROXY was configured.

Known issues

The following table describes the known issues for this release:

Issue Description
172332786 Double slashes (//) in a request can cause the request not to resolve. You can solve this by applying a configuration to your Istio ingress that filters for double slashes. See Remove double slashes from requests for instructions.
161658025 Inaccurate deployment status for Shared Flows

For Shared Flows, the deployment status is not being reported correctly to the UI, resulting in an indefinitely spinning deployment icon. If you have deployed a Shared Flow and see the spinning deployment icon, you must assume that the deployment has in fact failed.

To obtain the correct deployment status, use the v1.organizations.environments.sharedflows.revisions.deployments API. For example:

curl -s -H "$AUTH" \


146222881 Invalid HTTP Header error: The Istio ingress switches all incoming target responses to the HTTP2 protocol. Because the hybrid message processor only supports HTTP1, you may see the following error when an API proxy is called:

http2 error: Invalid HTTP header field was received: frame type: 1, stream: 1,

name: [:authority], value: [domain_name]

If you see this error, you can take either of the following actions to correct the problem:

  • Modify the target service to omit the Host header in the response.
  • Remove the Host header using the AssignMessage policy in your API proxy if necessary.
143659917 The PopulateCache policy's expiration setting must be set to an explicit value between 1 and 30. For example: