- Apigee Edge on-premises release notes

You're viewing Apigee Edge documentation.
Go to the Apigee X documentation.

On Friday, November 7, 2014, we released a patch for the on-premises version of Apigee Edge.

New features and enhancements

Following are the new features and enhancements in this release.

  • Configure URL encoding when serializing a request

    You can now configure http.properties in your message processor to not encode the URL when serializing a request line. These properties are global to the message processor.
    To configure your message processor to not encode the URL when serializing a request line:
    1. Access the property file .../conf/http.properties.
    2. Edit the file to set the HTTPClient.urlencode.request.line property to false and HTTPClient.urlencode.request.line to false.

Bugs fixed

The following bugs are fixed in this release.

Topic Description
Netty profile Netty profile on the router is no longer blocking the PATCH HTTP method. The method no longer returns a "501 NOT IMPLEMENTED" error.
Added missing configuration params
Two missing configurations were added to the apigee4/config/ui.apigee.conf file:
  • apigee.branding.companyNameShort=<some_name>
  • apigee.branding.contactEmailSales=<some_email>
Once you set these values, an admin user will be able to add users, activation link emails will be sent (if a valid SMTP configuration exists), and the forgot password link on the login page will work.
Developer Page now shows developers The Developers page in the Edge management UI now correctly shows the list of developers.
Email addresses containing hyphens now supported A GET of a user with an email address that includes a hyphen now works as expected.
Prorated usage fee and actual fee charged are being calculated using an inconsistent number of decimal places. All transaction fees are now calculated to the granularity of two decimal places.