Priority

In general, rules are applied from the top down. That is, the more precise the match criteria, the more important it is to ensure that subsequent rules do not alter the behavior in unexpected ways. Therefore, the more specific the criteria, the farther down in the list of rules it should be placed.

For example, if you have a "caching" policy that matches on a "/static/*" URL wildcard and also matches on URL extension, for example "png", "gif", or "jpg", and sets a TTL for this content of 1 day ("1d"), and then add a separate "caching" policy farther down in the JSON for the same "/static/*" URL wildcard pattern that sets a cache TTL of 1 hour ("1h"), then the first policy will never be applied because a more generic set of match conditions replaces the earlier setting.

Therefore, the order of rules is important and must be considered when multiple policies may have been applied. The last set of behaviors across all applied "matches" will always be the resulting behavior of the CDN platform. For a more detailed overview see the "Overlapping Behaviors" examples in the "Combining Matches and Behaviors" section below.