You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/cdn/cdn-verizon-premium-rules-engine.md
+75-26Lines changed: 75 additions & 26 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ author: duongau
6
6
7
7
ms.service: azure-cdn
8
8
ms.topic: how-to
9
-
ms.date: 05/31/2019
9
+
ms.date: 04/13/2022
10
10
ms.author: duau
11
11
12
12
---
@@ -27,53 +27,59 @@ To access the rules engine, you must first select **Manage** from the top of the
27
27
28
28
Select the **HTTP Large** tab, then select **Rules Engine**.
29
29
30
-
30
+
:::image type="content" source="./media/cdn-rules-engine/cdn-http-rules-engine.png" alt-text="Screenshot of rules engine for HTTP.":::
31
31
32
32
- Endpoints optimized for DSA:
33
33
34
34
Select the **ADN** tab, then select **Rules Engine**.
35
35
36
36
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.
37
37
38
-
38
+
:::image type="content" source="./media/cdn-rules-engine/cdn-dsa-rules-engine.png" alt-text="Screenshot of rules engine for DSA.":::
39
39
40
40
## Tutorial
41
41
42
-
1. From the **CDN profile** page, select **Manage**.
1. From the **CDN profile** page, select **Manage** to open the CDN management portal.
47
43
48
-
2. Select the **HTTP Large** tab, then select **Rules Engine**.
49
-
50
-
The options for a new rule are displayed.
51
-
52
-
44
+
:::image type="content" source="./media/cdn-rules-engine/cdn-manage-btn.png" alt-text="Screenshot of the manage button from the CDN profile.":::
45
+
46
+
1. Select the **HTTP Large** tab, then select **Rules Engine**.
47
+
48
+
1. Select **+ New** to create a new draft policy.
49
+
50
+
:::image type="content" source="./media/cdn-rules-engine/new-draft.png" alt-text="Screenshot of the create a new policy button.":::
53
51
52
+
1. Give the policy a name. Select **Continue**, then select **+ Rule**.
53
+
54
+
:::image type="content" source="./media/cdn-rules-engine/new-draft-2.png" alt-text="Screenshot of the policy creation page.":::
55
+
54
56
> [!IMPORTANT]
55
57
> 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.
56
58
>
57
59
58
-
3. Enter a name in the **Name / Description** textbox.
60
+
1. Enter a name in the **Name / Description** textbox.
59
61
60
-
4. Identify the type of requests the rule applies to. Use the default match condition, **Always**.
62
+
1. Select the **+** button and then select **Match** or **Select First Match** for the match logic. The difference between the two is described in [Request Identification](https://docs.edgecast.com/cdn/index.html#HRE/MatchesConcept.htm?).
63
+
64
+
1. Identify the type of requests the rule applies to. Use the default match condition, **Always**.
61
65
62
-
66
+
:::image type="content" source="./media/cdn-rules-engine/cdn-request-type.png" alt-text="Screenshot of the CDN rule match condition.":::
63
67
64
68
> [!NOTE]
65
69
> 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.
66
70
>
67
-
> For a detailed list of conditional expressions, see [Rules engine conditional expressions](cdn-verizon-premium-rules-engine-reference-match-conditions.md).
71
+
> For a detailed list of conditional expressions, see [Rules engine conditional expressions](cdn-verizon-premium-rules-engine-reference-match-conditions.md).
68
72
>
69
73
> For a detailed list of match conditions, see [Rules engine match conditions](cdn-verizon-premium-rules-engine-reference-match-conditions.md).
70
74
>
71
75
>
72
76
73
-
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.
77
+
1. To add a new feature, select the **+** button in the conditional statement.
:::image type="content" source="./media/cdn-rules-engine/cdn-new-feature.png" alt-text="Screenshot of the CDN rules feature in a rule.":::
76
80
81
+
1. From the *category* drop-down, select **Caching**. Then from the *feature* drop-down, select **Force Internal Max-Age**. In the text box enter the value **300**. Leave the rest of the settings as default and select **Save** to complete the configuration of the rule.
82
+
77
83
> [!NOTE]
78
84
> Multiple features are available in the dropdown list. For information about the currently selected feature, select the blue informational icon to its left.
79
85
>
@@ -83,12 +89,55 @@ To access the rules engine, you must first select **Manage** from the top of the
83
89
>
84
90
>
85
91
86
-
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**.
87
-
88
-
> [!IMPORTANT]
89
-
> Rules changes can take up to 10 minutes to propagate through Azure CDN.
90
-
>
91
-
>
92
+
1. Select **Lock Draft as Policy**. Once you lock the draft into a policy, you won't be able to add or update any rules within that policy.
93
+
94
+
:::image type="content" source="./media/cdn-rules-engine/policy-builder.png" alt-text="Screenshot of the CDN policy builder.":::
95
+
96
+
1. Select **Deploy Request**.
97
+
98
+
:::image type="content" source="./media/cdn-rules-engine/policy-builder-2.png" alt-text="Screenshot of the deploy request button in policy builder.":::
99
+
100
+
1. If this CDN profile is new with no previous rules or production traffic, you can select the environment as **Production** in the drop-down menu. Enter a description of the environment and then select **Create Deploy Request**.
101
+
102
+
:::image type="content" source="./media/cdn-rules-engine/policy-builder-environment.png" alt-text="Screenshot of the CDN policy builder environment.":::
103
+
104
+
> [!NOTE]
105
+
> Once the policy has been deployed, it will take about 30 mins for it propagate. If you want to add or update more rules, you'll need to duplicate the current rule and deploy the new policy.
106
+
107
+
## Add rules to an existing policy deployed in production
108
+
109
+
1. Select the policy that is deployed in production.
110
+
111
+
:::image type="content" source="./media/cdn-rules-engine/policy-production-overview.png" alt-text="Screenshot of the policy production overview page.":::
112
+
113
+
1. Select **Duplicate** to clone the existing policy in production.
114
+
115
+
:::image type="content" source="./media/cdn-rules-engine/policy-production-duplicate.png" alt-text="Screenshot of the duplicate button on the policy overview page.":::
116
+
117
+
1. Select the pencil icon to edit an existing rule or select **+ Rule** to add a new rule to the policy.
118
+
119
+
:::image type="content" source="./media/cdn-rules-engine/policy-production-edit.png" alt-text="Screenshot of the edit button and new rule for duplicate policy." lightbox="./media/cdn-rules-engine/policy-production-edit-expanded.png":::
120
+
121
+
1. Once you're happy with the updates, follow steps 10-12 in the last section to deploy the policy.
122
+
123
+
## Rules Engine staging environment
124
+
125
+
* The staging environment provides a sandbox where you can test the new CDN configuration end to end without impacting the production environment. This configuration allows you to replicate traffic flow through your staging network to an origin server.
126
+
* The staging environment is designed for functional testing and is at a smaller scale than the production CDN environment. Therefore, you shouldn't use this environment for scale, high volume or throughput testing.
127
+
* Traffic should be kept under 50 Mbps or 500 requests per second.
128
+
* Changes made to the staging environment will not affect your live site environment.
129
+
* Testing HTTPS traffic using the staging environment will result in a TLS certificate mismatch.
130
+
* Testing mechanism:
131
+
* After locking a draft into a policy, select **Deploy Request**. Select the environment as **Staging** and then select **Create Deploy Request**.
132
+
133
+
:::image type="content" source="./media/cdn-rules-engine/policy-staging.png" alt-text="Screenshot of a staging policy." lightbox="./media/cdn-rules-engine/policy-staging-expanded.png":::
134
+
135
+
* Edit your local host file to create an A record for your endpoint or custom domain.
136
+
* Check the test asset for the custom domain in the browser and proceed without using HTTPS.
137
+
138
+
> [!NOTE]
139
+
> Once a policy is deployed in the staging environment, it will take 15 mins to propagate.
140
+
>
92
141
93
142
## See also
94
143
@@ -97,4 +146,4 @@ To access the rules engine, you must first select **Manage** from the top of the
97
146
-[Rules engine match conditions](cdn-verizon-premium-rules-engine-reference-match-conditions.md)
0 commit comments