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
title: Azure CDN from Microsoft Standard Rules Engine actions | Microsoft Docs
3
-
description: Reference documentation for Azure CDN from Microsoft Standard Rules Engine actions.
2
+
title: Actions in the Standard rules engine for Azure CDN | Microsoft Docs
3
+
description: Reference documentation for actions in the Standard rules engine for Azure Content Delivery Network (Azure CDN).
4
4
services: cdn
5
5
author: mdgattuso
6
6
@@ -11,108 +11,103 @@ ms.author: magattus
11
11
12
12
---
13
13
14
-
# Azure CDN from Microsoft Standard Rules Engine actions
14
+
# Actions in the Standard rules engine for Azure CDN
15
15
16
-
This article lists detailed descriptions of the available actions for Azure Content Delivery Network (CDN) from Microsoft [Standard Rules Engine](cdn-standard-rules-engine.md).
16
+
In the [Standard rules engine](cdn-standard-rules-engine.md)for Azure Content Delivery Network (Azure CDN), a rule consists of one or more match conditions and an action. This article provides detailed descriptions of the actions you can use in the Standard rulesengine for Azure CDN.
17
17
18
-
The second part of a rule is an action. An action defines the behavior that is applied to the request type that is identified by a set of match conditions.
18
+
The second part of a rule is an action. An action defines the behavior that's applied to the request type that a match condition or set of match conditions identifies.
19
19
20
20
## Actions
21
21
22
-
The following actions are available to use.
22
+
The following actions are available to use in the Standard rules engine for Azure CDN.
23
23
24
-
## Cache Expiration
24
+
###Cache expiration
25
25
26
-
This action allows you to overwrite the TTLof the endpoint for requests specified by the rules match conditions.
26
+
Use this action to overwrite the time to live (TTL) value of the endpoint for requests that the rules match conditions specify.
27
27
28
-
**Required fields**
28
+
#### Required fields
29
29
30
-
Cache Behavior |
30
+
Cache behavior | Description
31
31
---------------|----------------
32
-
Bypass Cache | When this option is selected and the rule matches, the content will not be cached.
33
-
Override | When this option is selected and the rule matches, the TTL value returned from origin will be overwritten with the value specified in the action.
34
-
Set if missing | When this option is selected and the rule matches, if there was no TTL value returned from origin, the rule will set the TTL to the value specified in the action.
32
+
Bypass cache | When this option is selected and the rule matches, the content is not cached.
33
+
Override | When this option is selected and the rule matches, the TTL value returned from your origin is overwritten with the value specified in the action.
34
+
Set if missing | When this option is selected and the rule matches, if no TTL value was returned from your origin, the rule sets the TTL to the value specified in the action.
35
35
36
-
**Additional fields**
36
+
#### Additional fields
37
37
38
38
Days | Hours | Minutes | Seconds
39
39
-----|-------|---------|--------
40
40
Int | Int | Int | Int
41
41
42
-
## Cache Key query string
42
+
###Cache key query string
43
43
44
-
This action allows you to modify the cache key based on query strings.
44
+
Use this action to modify the cache key based on query strings.
45
45
46
-
**Required fields**
46
+
#### Required fields
47
47
48
48
Behavior | Description
49
49
---------|------------
50
-
Include | When this option is selected and the rule matches, query strings specified in the parameters will be included when generating the cache key.
51
-
Cache every unique URL | When this option is selected and the rule matches, each unique URL will have its own cache key.
52
-
Exclude | When this option is selected and the rule matches, query strings specified in the parameters will be excluded when generating the cache key.
53
-
Ignore query strings | When this option is selected and the rule matches, query strings will not be considered when generating the cache key.
50
+
Include | When this option is selected and the rule matches, query strings specified in the parameters are included when the cache key is generated.
51
+
Cache every unique URL | When this option is selected and the rule matches, each unique URL has its own cache key.
52
+
Exclude | When this option is selected and the rule matches, query strings specified in the parameters are excluded when the cache key is generated.
53
+
Ignore query strings | When this option is selected and the rule matches, query strings aren't considered when the cache key is generated.
54
54
55
-
## Modify Request header
55
+
###Modify request header
56
56
57
-
This action allows you to modify headers present in requests sent to your origin.
57
+
Use this action to modify headers that are present in requests sent to your origin.
58
58
59
-
**Required fields**
59
+
#### Required fields
60
60
61
-
Action | HTTP Header Name | Value
61
+
Action | HTTP header name | Value
62
62
-------|------------------|------
63
-
Append | When this option is selected and the rule matches, the header specified in Header name will be added to the request with the specified Value. If the header is already present, the Value will be appended to the existing value. | String
64
-
Overwrite | When this option is selected and the rule matches, the header specified in Header name will be added to the request with the specified Value. If the header is already present, the Value will overwrite the existing value. | String
65
-
Delete | When this option is selected and the rule matches, and the header specified in the rule is present, it will be deleted from the request. | String
63
+
Append | When this option is selected and the rule matches, the header specified in **Header name** is added to the request with the specified value. If the header is already present, the value is appended to the existing value. | String
64
+
Overwrite | When this option is selected and the rule matches, the header specified in **Header name** is added to the request with the specified value. If the header is already present, the specified value overwrites the existing value. | String
65
+
Delete | When this option is selected, the rule matches, and the header specified in the rule is present, the header is deleted from the request. | String
66
66
67
-
## Modify Response header
67
+
###Modify response header
68
68
69
-
This action allows you to modify headers present in responses returned to your end clients
69
+
Use this action to modify headers that are present in responses returned to your clients.
70
70
71
-
**Required fields**
71
+
#### Required fields
72
72
73
-
Action | HTTP Header Name | Value
73
+
Action | HTTP Header name | Value
74
74
-------|------------------|------
75
-
Append | When this option is selected and the rule matches, the header specified in Header name will be added to the response with the specified Value. If the header is already present, the Value will be appended to the existing value. | String
76
-
Overwrite | When this option is selected and the rule matches, the header specified in Header name will be added to the response with the specified Value. If the header is already present, the Value will overwrite the existing value. | String
77
-
Delete | When this option is selected and the rule matches, and the header specified in the rule is present, it will be deleted from the response. | String
75
+
Append | When this option is selected and the rule matches, the header specified in **Header name** is added to the response by using the specified **Value**. If the header is already present, **Value** is appended to the existing value. | String
76
+
Overwrite | When this option is selected and the rule matches, the header specified in **Header name** is added to the response by using the specified **Value**. If the header is already present, **Value** overwrites the existing value. | String
77
+
Delete | When this option is selected, the rule matches, and the header specified in the rule is present, the header is deleted from the response. | String
78
78
79
-
## URL Redirect
79
+
###URL redirect
80
80
81
-
This action allows you to redirect end clients to a new URL.
81
+
Use this action to redirect clients to a new URL.
82
82
83
-
**Required fields**
83
+
#### Required fields
84
84
85
85
Field | Description
86
86
------|------------
87
-
Type | Select the response type that will be returned to the requestor. Options are - 302 Found, 301 Moved, 307 Temporary redirect, and 308 Permanent redirect
88
-
Protocol | Match Request, HTTP, or HTTPS
89
-
Hostname | Select the hostname the request will be redirected to. Leave empty to preserve the incoming host.
90
-
Path | Define the path to be used in the redirect. Leave empty to preserve the incoming path.
91
-
Query String | Define the query string used in the redirect. Leave empty to preserve the incoming query string.
92
-
Fragment | Define the fragment to be used in the redirect. Leave empty to preserve the incoming fragment.
87
+
Type | Select the response type to return to the requestor: Found (302), Moved (301), Temporary redirect (307), and Permanent redirect (308).
88
+
Protocol | Match Request, HTTP, HTTPS.
89
+
Hostname | Select the host name you want the request to be redirected to. Leave blank to preserve the incoming host.
90
+
Path | Define the path to use in the redirect. Leave blank to preserve the incoming path.
91
+
Query string | Define the query string used in the redirect. Leave blank to preserve the incoming query string.
92
+
Fragment | Define the fragment to use in the redirect. Leave blank to preserve the incoming fragment.
93
93
94
-
It is highly recommended to use an absolute URL. The use of a relative URL may redirect CDN URLs to an invalid path.
94
+
We highly recommend that you use an absolute URL. Using a relative URL might redirect Azure CDN URLs to an invalid path.
95
95
96
-
## URL Rewrite
96
+
###URL rewrite
97
97
98
-
This action allows you to rewrite the path of a request en route to your origin.
98
+
Use this action to rewrite the path of a request that's en route to your origin.
99
99
100
-
**Required fields**
100
+
#### Required fields
101
101
102
102
Field | Description
103
103
------|------------
104
-
Source Pattern | Define the source pattern in the URL path to replace. Currently, source pattern uses a prefix-based match. To match all URL paths, use “/” as the source pattern value.
105
-
Destination | Define the destination path for be used in the rewrite. This will overwrite the source pattern
106
-
Preserve unmatched path | If Yes, the remaining path after the source pattern will be appended to the new destination path.
107
-
108
-
109
-
[Back to top](#actions)
110
-
111
-
</br>
104
+
Source pattern | Define the source pattern in the URL path to replace. Currently, source pattern uses a prefix-based match. To match all URL paths, use a forward slash (**/**) as the source pattern value.
105
+
Destination | Define the destination path to use in the rewrite. The destination path overwrites the source pattern.
106
+
Preserve unmatched path | If set to **Yes**, the remaining path after the source pattern is appended to the new destination path.
0 commit comments