Known limitations with MMC
Mixed Mode Configuration (MMC) lets you reuse the various use case-based behaviors for Object Delivery (Object Delivery) to implement several different scenarios. There are some limitations, though.
| Limitation | Detail |
|---|---|
| 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 the delivery of non-segmented media files in your Object Delivery configuration. |
| MMC is not supported with Object Delivery through Akamai Cloud Embed (ACE). | N/A |
Updated about 3 years ago