You can add optional rules

You can add rules via the Add Rule button to include match criteria and behaviors outside of what's included automatically in the Default Rule for your AMD property configuration.

Optional rules available in the Property Manager catalog vary, based on the following:

  • What is included in the AMD product, as well as any additional rules you have added to your contract.
  • Whether you are using NetStorage as your origin, or you have your own custom origin.
Some of the rules are not available if you are using NetStorage as your origin server. When a rule is not available for configurations using NetStorage, it is noted in its description.
Note: It is outside the scope of this document to describe all of the additional optional rules. Those that apply to AMD are detailed in "How to implement..." topics in this documentation. Detailed information on other optional rules can be found in the online help in the Property Manager Editor UI in Control Center: add a rule, mouse-over a behavior in the rule and click the help links.

Rule order precedence and "Match" criteria

One of the key benefits of additional rules is that you can set up specific match criteria that must be met to apply the behaviors you set in this rule. (Unlike the "Default Rule" that applies to all requests.) If you add a new rule, it is read first and applied before the Default Rule. Overall, the last rule in the list is applied first and all subsequent rules are applied, ending with the Default Rule.

For example, you could set up a new rule and apply a match criteria to target a specific property hostname to edge hostname association and add the Prefetching behavior. Only requests to that edge hostname will use Prefetching, and all of the other behaviors you've set in the Default Rule would be applied, because its behaviors apply to all requests. (All other requests will only use the behaviors set in the Default Rule.)