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/frontdoor/front-door-routing-limits.md
+15-12Lines changed: 15 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -23,27 +23,30 @@ The composite route metric for each Front Door profile can't exceed 5000.
23
23
> [!TIP]
24
24
> Most Front Door deployments don't approach the composite route limit. However, if you have a large Front Door deployment, consider whether you could exceed the limit and plan accordingly.
25
25
26
-
## Calculate your composite route metric
26
+
## Calculate your profile's composite route metric
27
27
28
-
Use the following formula to calculate the composite route metric for your Front Door profile:
28
+
Follow these steps to calculate the composite route metric for your Front Door profile:
1. Multiply the number of HTTP domains by the number of HTTP paths.
32
+
1. Multiply the number of HTTPS domains by the number of HTTPS paths.
33
+
1. Add the results of steps 1a and 1b together to give the composite route metric for this individual route.
34
+
1. Repeat these steps for each route in your profile.
35
+
36
+
Add together all of the composite route metrics for each route. This is your profile's composite route metric.
33
37
34
38
### Example
35
39
36
-
Suppose you have have two routes in your Front Door profile. The routes are named *Route1* and *Route2*. You want to configure the routes as follows:
37
-
**Route1* will have 50 domains associated to it, and requires HTTPS for all inbound requests. *Route1* specifies 80 paths.
38
-
**Route2* will have 25 domains associated to it. *Route2* specifies 25 paths, and supports both the HTTP and HTTPS protocols.
40
+
Suppose you have have two routes in your Front Door profile. The routes are named *Route 1* and *Route 2*. You plan to configure the routes as follows:
41
+
**Route 1* will have 50 domains associated to it, and requires HTTPS for all inbound requests. *Route 1* specifies 80 paths.
42
+
**Route 2* will have 25 domains associated to it. *Route 2* specifies 25 paths, and supports both the HTTP and HTTPS protocols.
39
43
40
44
The following calculation illustrates how to determine the composite route metric for this scenario:
0 commit comments