New Features: 

• Akamai Cloud Embed (ACE) map expansion. This lets us use the Akamai edge map without restrictions and we expect it will improve performance for subcustomers. ACE policy activations now take longer to complete (eight minutes versus one minute), but this update provides marked benefits for safety and performance (improvement in throughput, latency, and time to first byte (TTFB)).
• Live delivery optimizations. This feature provides optimizations for live streaming to ACE partners and their customers. This is available as a new option, “streaming-video-live” in the existing “content-characteristics” behavior. See the ACE - Implementation Guide for full usage instructions.
• Prefetching of streaming content. Prefetching positions target media content at the Edge in anticipation of requests by end users. This reduces the time to deliver that content. The origin housing content needs to be configured to support the origin-assist model, and prefetching is supported for use with DASH, HLS, and Smooth streaming formats. Complete usage is also explained in the ACE - Implementation Guide.
• Origin failover. This feature identifies primary origin connection failures based on a type you specify and marks that origin as “bad” after connections to all its IPs fail repeatedly. Rather than issuing a redirect to the end user, requests are failed over to a backup origin you call out. You can add this support for subcustomers via a new behavior in the ACE API.

Enhancements

• HTTPS orchestration. We’ve made improvements to certification selection logic.

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.