New Features: 

We have added support for new behaviors in a subcustomer policy:

• Request Header Rewrite: Use this behavior to modify the outgoing request headers sent from Akamai to an origin. This also works on request headers sent from a client if the request is sent back to the origin, but not a cache hit.
• Response Header Rewrite: Use this behavior to modify the outgoing response headers sent from the origin or CDN edge back to the client.

Details on the use of this behavior are covered in the documentation for the Akamai Cloud Embed API v2

New Features:

We have added support for a new behavior in a subcustomer policy:

• URL Redirect: You can include this behavior to configure redirect responses for specific client requests, and stop them from contacting the origin.

Details on the use of this behavior are covered in the documentation for the Akamai Cloud Embed API v2.

New features:

You can associate a Vanity Domain with a different Partner Domain. To accomplish this you need to do the following:

1. Disable HTTPS for the Vanity Domain. This ensures that the vanity domain is successfully de-linked from the current or old partner domain.
2. Enable HTTPS for the Vanity Domain with the new Partner domain. 

A request to enable HTTPS on a Vanity Domain is rejected with a status “HTTP 409 - Request Conflict” in the following scenarios:

• If the Vanity Domain is HTTPS enabled with the old Partner Domain.
• If there are pending changes against the old Partner Domain.

Bug fixes:

• PUT requests for /secure-delivery that have a non-empty endpoint domain are rejected with a status “HTTP 400” and an associated message.

New Features:

We have added support for new rule match criteria in a subcustomer policy:

• Geography: You can test the requesting client’s location, either by continent, country, region, or designated market area (DMA).

Details on the use of this match criteria are covered in the documentation for the Akamai Cloud Embed API v2.

New Features

We have added support for new rule match criteria in a subcustomer policy:

• Client IP match: You can specify an individual or a range of IP addresses. If a request originates from a specified address, the behavior applied in a policy rule is applied.
• Cookie match: You can specify a specific cookie name, and optionally include associated cookie values. If a request for content uses the named cookie (and optionally, the cookie values), the behavior applied in a policy rule is applied.

Details on the use of these match criteria are covered in the documentation for the Akamai Cloud Embed API v2.