Override HTTP behavior using the Azure CDN from Verizon Premium rules engine


This is a feature of Azure CDN Premium from Verizon only, to configure rules on Azure CDN from Microsoft please use the Standard rules engine. Advanced rules are not available for Azure CDN from Akamai. For a full comparison of CDN features, see Azure CDN product features.


The Azure CDN rules engine allows you to customize how HTTP requests are handled. For example, blocking the delivery of certain content types, defining a caching policy, or modifying an HTTP header. This tutorial demonstrates how to create a rule that changes the caching behavior of CDN assets. For more information about the rules engine syntax, see Azure CDN rules engine reference.


To access the rules engine, you must first select Manage from the top of the CDN profile page to access the Azure CDN management page. Depending on whether your endpoint is optimized for dynamic site acceleration (DSA), you then access the rules engine with the set of rules appropriate for your type of endpoint:

  • Endpoints optimized for general web delivery or other non-DSA optimization:

    Select the HTTP Large tab, then select Rules Engine.

    Rules engine for HTTP

  • Endpoints optimized for DSA:

    Select the ADN tab, then select Rules Engine.

    ADN is a term used by Verizon to specify DSA content. Any rules you create here are ignored by any endpoints in your profile that are not optimized for DSA.

    Rules engine for DSA


  1. From the CDN profile page, select Manage.

    CDN profile Manage button

    The CDN management portal opens.

  2. Select the HTTP Large tab, then select Rules Engine.

    The options for a new rule are displayed.

    CDN new rule options


    The order in which multiple rules are listed affects how they are handled. A subsequent rule may override the actions specified by a previous rule. For example, if you have a rule that allows access to a resource based on a request property and a rule that denies access to all requests, the second rule overrides the first one. Rules will override earlier rules only if they interact with the same properties.

  3. Enter a name in the Name / Description textbox.

  4. Identify the type of requests the rule applies to. Use the default match condition, Always.

    CDN rule match condition


    Multiple match conditions are available in the dropdown list. For information about the currently selected match condition, select the blue informational icon to its left.

    For a detailed list of conditional expressions, see Rules engine conditional expressions.

    For a detailed list of match conditions, see Rules engine match conditions.

  5. To add a new feature, select the + button next to Features. In the dropdown on the left, select Force Internal Max-Age. In the textbox that appears, enter 300. Do not change the remaining default values.

    CDN rule feature


    Multiple features are available in the dropdown list. For information about the currently selected feature, select the blue informational icon to its left.

    For Force Internal Max-Age, the asset's Cache-Control and Expires headers are overridden to control when the CDN edge node refreshes the asset from the origin. In this example, the CDN edge node caches the asset for 300 seconds, or 5 minutes, before it refreshes the asset from its origin.

    For a detailed list of features, see Rules engine features.

  6. Select Add to save the new rule. The new rule is now awaiting approval. After it has been approved, the status changes from Pending XML to Active XML.


    Rules changes can take up to 10 minutes to propagate through Azure CDN.

See also