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
In Azure Front Door [Rule sets](front-door-rules-engine.md), a rule consists of none or some match conditions and an action. This article provides detailed descriptions of match conditions you can use in Azure Front Door rule sets.
17
+
In Azure Front Door [Rule sets](front-door-rules-engine.md), a rule consists of one or more match conditions and an action. This article provides detailed descriptions of the match conditions you can use in Azure Front Door rule sets.
18
18
19
19
::: zone-end
20
20
21
21
::: zone pivot="front-door-classic"
22
22
23
23
[!INCLUDE [Azure Front Door (classic) retirement notice](../../includes/front-door-classic-retirement.md)]
24
24
25
-
In Azure Front Door (classic) [Rules engines](front-door-rules-engine.md), a rule consists of none or some match conditions and an action. This article provides detailed descriptions of match conditions you can use in Azure Front Door (classic) Rules engines.
25
+
In Azure Front Door (classic) [Rules engines](front-door-rules-engine.md), a rule consists of one or more match conditions and an action. This article provides detailed descriptions of the match conditions you can use in Azure Front Door (classic) Rules engines.
26
26
27
27
::: zone-end
28
28
29
-
The first part of a rule is a match condition or set of match conditions. A rule can consist of up to 10 match conditions. A match condition identifies specific types of requests for which defined actions are done. If you use multiple match conditions, the match conditions are grouped together by using AND logic. For all match conditions that support multiple values, OR logic is used.
29
+
A rule starts with a match condition or a set of match conditions. A rule can have up to 10 match conditions. A match condition identifies specific types of requests for which defined actions are performed. If you use multiple match conditions, they're grouped together using AND logic. For match conditions that support multiple values, OR logic is used.
30
30
31
31
You can use a match condition to:
32
32
@@ -35,25 +35,21 @@ You can use a match condition to:
35
35
* Filter requests based on a specific IP address, port, or country/region.
36
36
* Filter requests by header information.
37
37
* Filter requests from mobile devices or desktop devices.
38
-
* Filter requests from request file name and file extension.
39
-
* Filter requests by hostname, SSL protocol, request URL, protocol, path, query string, post args, and other values.
38
+
* Filter requests by request file name and file extension.
39
+
* Filter requests by hostname, SSL protocol, request URL, protocol, path, query string, post arguments, and other values.
40
40
41
41
::: zone-end
42
42
43
43
::: zone pivot="front-door-classic"
44
44
45
-
* Filter requests based on a specific IP address, or country/region.
45
+
* Filter requests based on a specific IP address or country/region.
46
46
* Filter requests by header information.
47
47
* Filter requests from mobile devices or desktop devices.
48
-
* Filter requests from request file name and file extension.
48
+
* Filter requests by request file name and file extension.
49
49
* Filter requests by request URL, protocol, path, query string, post arguments, and other values.
50
50
51
51
::: zone-end
52
52
53
-
::: zone pivot="front-door-standard-premium"
54
-
55
-
::: zone-end
56
-
57
53
## Device type
58
54
59
55
Use the **device type** match condition to identify requests that is from a mobile device or desktop device.
0 commit comments