Known limitations with MMC
Mixed Mode Configuration (MMC) allows you to reuse the various use case-based behaviors to implement several different scenarios. Be aware that there are some limitations.
- You can only include the Origin Characteristics behavior if Origin Server is also in the rule. Since the Default Rule applies to all requests, settings in its instance of the Origin Characteristics behavior must be used. You can't have a unique instance of this behavior in a subsequent rule to apply settings for unique requests. Origin Characteristics must apply to the same Origin Server called out in a rule.
- Signature Header Authentication is not supported in a rule when NetStorage is set as the Origin Type in the Default Rule. If you have NetStorage set as your Origin Type in the Default Rule and a custom origin ("Your Origin") set in a subsequent rule, NetStorage authentication header information may be leaked to the custom origin. To avoid this issue, we have disabled the use of Signature Header Auth in rules.
- MMC will not optimize delivery of files that are delivered using another product. for example MMC does not optimize delivery of non-segmented media files in your AMD configuration.
- MMC is only supported for use with AMD. MMC is not yet supported for other products, such as Download Delivery and Object Delivery. MMC will not merge features between these products and AMD.
- MMC is not supported with AMD through Akamai Cloud Embed (ACE).