New Features:

• Mixed Mode for Download Delivery. This new feature lets you incorporate use case-based behaviors outside of the Default Rule in a Property Manager configuration. You can now set up multiple origin servers in a single property configuration, as well as set different Origin Characteristics, Content Characteristics, and Client Characteristics in different rules, with different match criteria. You can even incorporate different authentication methods for requests using the same property. See the Mixed Mode for Download Delivery document for more information.

Enhancements:

• We’ve improved delivery performance by reducing forward throttling. This enhancement looks to maximize end to end throughput. It safely raises configurable limits to improve delivery performance.

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.

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:

• Protocol Downgrade (HTTPS Downgrade to Origin): This has been added as a self-serviceable behavior in the Property Editor in Luna, and it does not require additional entitlement. It lets you downgrade HTTPS requests for Standard TLS and Shared Cert options. Complete details on use can be found in the Download Delivery - Implementation Guide.

As part of self-serviceability enhancements, three new mandatory behaviors called Origin Characteristics, Content Characteristics, and Client Characteristics have been added.

Using these behaviors, appropriate optimizations for the property are automatically applied, including settings for Caching and Tiered Distribution.

These behaviors will automatically be part of new configurations. If you update an existing configuration, you will need to add these behaviors (by clicking ‘Add Behavior’ in the Behaviors section of Property Manager). If you aren’t sure which options to select in a new behavior’s drop-down lists, you may leave them set to the default settings of ‘Unknown,’ in which case the Behavior will not take effect. It is a best practice to test configuration changes in staging before deploying to production.