You're viewing **Apigee Edge** documentation.  
[Go to the
**Apigee X** documentation](http://cloud.google.com/apigee/docs). info

On Tuesday, September 23, 2014, we released a patch for the on-premises version of Apigee
Edge.

> [!NOTE]
> **Note:** If you have questions, contact [Apigee Edge Support](https://docs.apigee.com/api-platform/troubleshoot/support).
>
> For a list of all Apigee Edge release notes, see [Apigee Release Notes](https://docs.apigee.com/release/notes/apigee-release-notes).

## New features and enhancements

Following are the new features and enhancements in this release.

- **Netty router request pipelining** CORERT-275  
  Netty router now supports HTTP request pipelining, where multiple HTTP requests can be sent to the router without waiting for the response. The router processes requests in FIFO order. However, if any of the responses require that the connection be closed, then the connection is closed immediately.  

  Request pipelining support is enabled by default but can be disabled by setting the following property in router.properties: `HTTPServer.pipelining.enabled=false`

## Bugs fixed

The following bugs are fixed in this release.

| Topic | Description |
|---|---|
| Netty router backport fix CORERT-277 | Backporting a fix from a newer version of the product to address Netty router issues. |
| Routers with multiple data centers CORERT-26 | In environments with multiple data centers, routers in one region were sending requests to message processors across regions. Routers now send requests to message processors only within the same POD. |