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

On Thursday, September 18, 2014, we released a new cloud 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.

- **Analytics features**
  - Rules and Alerts - A rule lets you specify a condition that, when it evaluates to true, generates an alert.
  - [Virtual
    Dimensions](https://docs.apigee.com/api-platform/analytics/analytics-reference) - User-agents, timestamps, and IP addresses are automatically mapped to dimensions such as OS version, device family, day of the week, city, country, and timezone.
  - [Newly designed interface
    for Custom Reports](https://docs.apigee.com/api-platform/analytics/custom-report-dashboard) (Beta)
  - [Support
    for Apigee 127 built proxies](https://github.com/apigee-127/a127-documentation/wiki/Quick-Start:-Add-Apigee-Analytics)
- **"/" resource on products** APIRT-667  
  When you add a resource to an API product as a single forward slash "/", by default Apigee treats it the same as "/\*\*", which gives developers access to all URIs under the base path. A new organization-level `features.isSingleForwardSlashBlockingEnabled` property lets you change the default behavior of "/". By changing the property to "true" (cloud customers must contact Apigee Support to do this), "/" gives developers access to only the base path as a resource.  

  For more information, see [Configuring the behavior of a
  Resource Path](https://docs.apigee.com/api-platform/publish/create-api-products#resourcebehavior).
- **HTTP response error configuration for Quota and Spike Arrest** APIRT-664  
  Apigee Edge organizations can now be configured to return an HTTP status code of 429 (Too Many Requests) for all requests that exceed a rate limit set by a Quota or Spike Arrest policy. The default configuration returns an HTTP status code of 500 (Internal Server Error).  

  Contact Apigee Support to have the `features.isHTTPStatusTooManyRequestEnabled` property set to true for organizations for which you want Quota and Spike Arrest violations to return an HTTP status code of 429.

  > [!NOTE]
  > **Private Cloud:** Edge on-premises customers can set this property with the following API call:
  >
  > ```
  > curl -u email:password -X POST -H "Content-type:application/xml" http://host:8080/v1/o/myorg -d \
  > "<Organization type="trial" name="MyOrganization">
  >     <DisplayName>MyOrganization</DisplayName>
  >     <Environments/>
  >     <Properties>
  >         <Property name="features.isHTTPStatusTooManyRequestEnabled">true</Property>
  >     </Properties>
  > </Organization>"
  > ```

## Bugs fixed

The following bugs are fixed in this release.

| Topic | Description |
|---|---|
| 204 error on missing key in Key Value Map MGMT-960 | The absence of a key in a Key Value Map returned an HTTP response of 204 (No Content) instead of the expected 404 (Not Found). This issue has been fixed to return a 404. |
| Permissions for user in multiple roles MGMT-656 | Permissions for a user assigned to two or more roles were not being combined correctly. This issue has been fixed. |
| Lowercase character set encoding on policies APIRT-703 | In a policy XML configuration, setting character encoding with lowercase "utf-8" or "utf-16" caused policies to fail. This issue has been fixed to support both lower- and uppercase encoding. |