Merge pull request #175765 from duongau/patch-1

AFDx patterns to match - add case insensitive info

Author: PRMerger17

articles/frontdoor/front-door-route-matching.md

@@ -69,7 +69,9 @@ After determining the specific frontend host and filtering possible routing rule
 3. If no routing rules are found with a matching Path, then reject the request and return a 400: Bad Request error HTTP response.
 
 >[!NOTE]
-> Any Paths without a wildcard are considered to be exact-match Paths. Even if the Path ends in a slash, it's still considered exact match.
+> * Any Paths without a wildcard are considered to be exact-match Paths. Even if the Path ends in a slash, it's still considered exact match.
+> * Patterns to match paths are case insensitive, meaning paths with different casings are treated as duplicates. For example, you have the same host using the same protocol with paths `/FOO` and `/foo`. These paths are considered duplicates which is not allowed in the Patterns to match setting.
+> 
 
 To explain further, let's look at another set of examples:
 
@@ -119,7 +121,7 @@ Given that configuration, the following example matching table would result:
 
 ### Routing decision
 
-After you have matched to a single Front Door routing rule, choose how to process the request. If Front Door has a cached response available for the matched routing rule, the cached response is served back to the client. If Front Door doesn't have a cached response for the matched routing rule, what's evaluated next is whether you have configured [URL wewrite (a custom forwarding path)](front-door-url-rewrite.md) for the matched routing rule. If no custom forwarding path is defined, the request is forwarded to the appropriate backend in the configured backend pool as-is. If a custom forwarding path has been defined, the request path is updated per the defined [custom forwarding path](front-door-url-rewrite.md) and then forwarded to the backend.
+After you have matched to a single Front Door routing rule, choose how to process the request. If Front Door has a cached response available for the matched routing rule, the cached response is served back to the client. If Front Door doesn't have a cached response for the matched routing rule, what's evaluated next is whether you have configured [URL rewrite (a custom forwarding path)](front-door-url-rewrite.md) for the matched routing rule. If no custom forwarding path is defined, the request is forwarded to the appropriate backend in the configured backend pool as-is. If a custom forwarding path has been defined, the request path is updated per the defined [custom forwarding path](front-door-url-rewrite.md) and then forwarded to the backend.
 
 ## Next steps
 

articles/frontdoor/standard-premium/how-to-configure-route.md

@@ -51,7 +51,7 @@ To set up an origin group, see [Create a new Azure Front Door Standard/Premium o
     | --- | --- |
     | Name | Enter a unique name for the new Route. |   
     | Domain| Select one or more domains that have been validated and isn't associated to another Route |
-    | Patterns to Match  | Configure all URL path patterns that this route will accept. For example, you can set this to `/images/*` to accept all requests on the URL `www.contoso.com/images/*`. AFD will try to determine the traffic based on Exact Match first, if no exact match Paths, then look for a wildcard Path that matches. If no routing rules are found with a matching Path, then reject the request and return a 400: Bad Request error HTTP response. |
+    | Patterns to Match  | Configure all URL path patterns that this route will accept. For example, you can set this to `/images/*` to accept all requests on the URL `www.contoso.com/images/*`. AFD will try to determine the traffic based on Exact Match first, if no exact match Paths, then look for a wildcard Path that matches. If no routing rules are found with a matching Path, then reject the request and return a 400: Bad Request error HTTP response. Patterns to match paths are case insensitive, meaning paths with different casings are treated as duplicates. For example, you have the same host using the same protocol with paths `/FOO` and `/foo`. These paths are considered duplicates which is not allowed in the Patterns to match setting. |
     | Accepted protocols | Specify the protocols you want Azure Front Door to accept when the client is making the request. |
     | Redirect | Specify whether HTTPS is enforced for the incoming request with HTTP request |
     | Origin group | Select which origin group should be forwarded to when the back to origin request occurs. |