- Edge for Private Cloud release notes

On Wednesday, February 22, 2017, we released a new version of Apigee Edge for Private Cloud.

Update procedure

To update your installation, perform the following procedure:

  1. On all Edge nodes, clean Yum repos:
    > sudo yum clean all

  2. If you are using a local repository, update apigee-mirror:
    > /opt/apigee/apigee-service/bin/apigee-service apigee-mirror update

  3. On all Edge nodes, update edge-gateway:
    >/opt/apigee/apigee-setup/bin/update.sh -c edge -f configFile

Bugs fixed

The following bugs are fixed in this release.

Issue ID Description Build number

Message Processor uses wrong HTTP auth header when tunneling

When a Message Processor uses tunneling with the HTTP CONNECT method, it now sends the correct header: "Proxy-Authorization: Basic value".


Server name field is not populated in TLS request when using a proxy server for a connection from Edge to the target server

The Message Processor is now setting server_name correctly when using a proxy server for a connection from Edge to the target server.


Known Issues

This release has the following known issues:

Issue ID Description

Message Processor does DNS lookup on IPv4 and IPv6

If you have installed and enabled NSCD (Name Service Cache Daemon) you might notice that Message Processors make two DNS lookups: one for IPv4 and one for IPv6.

To disable the DNS lookup on IPv6:

  1. On every Message Processor node, edit /etc/nscd.conf.
  2. Set the following property:

    enable-cache hosts no
DOC-1687 Due to a known package dependency conflict, the Katello agent used in Satellite Server 6 will not install properly on Apigee Edge hosts running the Qpid daemon.

Send feedback about...

Apigee Docs