New Features:

• Origin Failover for AMD: This lets you configure an Origin Failure Recovery Policy for AMD to recognize certain errors and connection timeout situations as failure scenarios. You also configure associated Origin Failure Recovery Methods to address the different failure scenarios. A recovery method can either redirect a failed request to a backup origin or return a custom HTTP status code to the end-user. Origin Failover use is covered in the AMD - Implementation Guide.
• Mixed Mode Configuration for AMD: This lets you apply the various use case-based behaviors (Client Characteristics, Content Characteristics, Origin Characteristics, and Segmented Media Delivery Mode) outside the default rule in an AMD property configuration. This way, you can define different match criteria for different instances of these behaviors, in order to optimize delivery for unique use cases. Instructions on its use are covered in Mixed Mode Configuration for AMD.

Enhancements:

• Support for Origin-assist Prefetching for Azure URLs: We have incorporated metadata changes to support Azure URLs for HLS and DASH format media. Currently, CMAF format manifests and manifests that have KEY frames are not supported. (A DOS does not occur for these formats, they are just not supported. Content is still fetched, just not in prefetch mode.)

New Features:

• Origin Assisted Prefetching: Prefetching positions your HLS live and on-demand objects at the Edge to ready them for requests and reduces the overall time for delivery. To implement this, we now offer the Segmented Media Streaming - Prefetch behavior in Property Manager, which relies on the “origin assist” prefetch model–your origin needs to be set up to send details on the objects that need to be prefetched, in its response.

Bug Fixes:

• Denial for certain unauthorized ServerIP Requests: We’ve fixed a bug that prevented denial of ServerIP requests, even though other requests from a related client were denied by AMD’s Enhanced Proxy Detection or the Content Targeting functionalities. These associated ServerIP requests are now denied as expected in such cases.

New Features:

• Protocol Downgrade supports the OPTIONS request/method: In addition to the HTTP, GET, and HEAD request/method formats, you can also use OPTIONS with the Protocol Downgrade feature.

Fixes/Changes:

Files using the extension “m4i” are now recognized as DASH “init” segments, and their Content-Type is set as “video/mp4.” Prior to this change, files using the “m4i” extension were treated as an “unknown” stream format.

Introducing the “Time Interval” match type

This match allows you to invoke certain property behaviors in a scheduled manner. (You configure them within a specified time range under this match.) Currently, this match type is not supported for use with the following behaviors:

• Cache Key Query Parameters
• Client Characteristics
• Content Characteristics
• Content Provider Code
• HTTPS Cache Key Sharing
• Ignore Case In Cache Key
• Origin Characteristics
• Origin Server
• Segmented Media Delivery Mode

Introducing the Edge IP Binding application

This application provides a unified view of all your Edge IP Binding configurations, as well as access to advanced settings. It is open to Edge IP Binding customers, and can be accessed via the Luna Control Center under CONFIGURE > Edge IP Binding.

Contact your Account Representative for more information and to add Edge IP Binding to your contract.

New Features:

• Manifest Personalization: This new feature for Adaptive Media Delivery (AMD) allows you to improve the viewing experience at scale by modifying the HLS Master Manifests that are served to your end users. You can filter in bitrates based on end user request, as well as set a preferred bitrate at the top of the manifest. We also provide a ‘Best Practice’ mode that allows you to use Apple recommended settings for iOS and TvOS devices. Please contact your account representative for more information on Manifest Personalization. The feature is currently in the Beta phase.

Fixes:

• Media Encryption-related fix:  With this update, if you have Media Encryption enabled, a valid session ID should be present in the query string for the init segment request. This is applicable to HLS Live and VOD streams that use CMAF segments.

New Features:

• The Protocol Downgrade (HTTPS Downgrade to Origin) behavior is now GA and available in the Property Editor in Control Center, without requiring any additional entitlement. This behavior enables downgrade of HTTPS requests for Standard TLS and Shared Cert options. Complete details on use can be found in the relevant product’s Implementation Guide on https://learn.akamai.com/en-us/products/. (See the pages for Adaptive Media Delivery, Download Delivery and Object Delivery.)
• The Proxy Protection option has been removed from the Content Targeting - Protection behavior, for Adaptive Media Delivery property configurations in Property Editor in Control Center.
• For Adaptive Media Delivery, the Access-Control-Expose-Headers response header available in the Modify Outgoing Response Header behavior in the Default CORS Policy in Property Editor now contains two additional header names: “Akamai-Mon-Iucid-Ing” and “Akamai-Mon-Iucid-Del.”  These both support client-side analytics. Creating a new property configuration or updating an existing one will automatically add these two headers to the Access-Control-Expose-Headers list.

This service pack release includes a new feature and a bug fix: * New Feature: ** Content Targeting - Protection for Adaptive Media Delivery is available as a self-serviceable behavior for customers with it added to their contract.  It can be applied to an AMD configuration via the Property Manager in Control Center.  * Bug Fix: ** Authentication requests to Google Cloud Platform and Amazon Web Services were failing if either Token Auth or Media Encryption was enabled. This fix addresses this issue.

• Content Targeting: Protection for Adaptive Media Delivery is available as a self-serviceable behavior for customers with it added to their contract.  It can be applied to an AMD configuration via the Property Manager in Luna. 

Fixes:

• Authentication request failure issue: Requests to the Google Cloud Platform and Amazon Web Services were failing if either Token Auth or Media Encryption were enabled.

This option can be enabled by using the “Segmented Content Protection” Behavior in Property Manager. If Media Encryption is not present on your contract, enabling this option will show an error.

Please see the documentation for this feature for more information.