Merge pull request #226453 from johndowns/front-door-caching-february-2023

Front Door - Update caching query string behavior documentation

Author: prmerger-automator[bot]

articles/frontdoor/front-door-caching.md

@@ -123,13 +123,15 @@ If there's more than one key-value pair in a query string of a request then thei
 
 When you configure caching, you specify how the cache should handle query strings. The following behaviors are supported:
 
-* **Ignore query strings**: In this mode, Azure Front Door passes the query strings from the client to the origin on the first request and caches the asset. All ensuing requests for the asset that are served from the Front Door environment ignore the query strings until the cached asset expires.
+* **Ignore Query String**: In this mode, Azure Front Door passes the query strings from the client to the origin on the first request and caches the asset. Future requests for the asset that are served from the Front Door environment ignore the query strings until the cached asset expires.
 
-* **Cache every unique URL**: In this mode, each request with a unique URL, including the query string, is treated as a unique asset with its own cache. For example, the response from the origin for a request for `www.example.ashx?q=test1` is cached at the Front Door environment and returned for ensuing caches with the same query string. A request for `www.example.ashx?q=test2` is cached as a separate asset with its own time-to-live setting.
+* **Use Query String**: In this mode, each request with a unique URL, including the query string, is treated as a unique asset with its own cache. For example, the response from the origin for a request for `www.example.ashx?q=test1` is cached at the Front Door environment and returned for ensuing caches with the same query string. A request for `www.example.ashx?q=test2` is cached as a separate asset with its own time-to-live setting.
+
+  The order of the query string parameters doesn't matter. For example, if the Azure Front Door environment includes a cached response for the URL `www.example.ashx?q=test1&r=test2`, then a request for `www.example.ashx?r=test2&q=test1` is also served from the cache.
 
 ::: zone pivot="front-door-standard-premium"
 
-* **Specify cache key query string** behavior to include or exclude specified parameters when the cache key is generated.
+* **Ignore Specified Query Strings** and **Include Specified Query Strings**: In this mode, you can configure Azure Front Door to include or exclude specified parameters when the cache key is generated.
 
   For example, suppose that the default cache key is `/foo/image/asset.html`, and a request is made to the URL `https://contoso.com/foo/image/asset.html?language=EN&userid=100&sessionid=200`. If there's a rules engine rule to exclude the `userid` query string parameter, then the query string cache key would be `/foo/image/asset.html?language=EN&sessionid=200`.
 

articles/frontdoor/front-door-rules-engine-actions.md

@@ -470,10 +470,10 @@ Use these settings to control how files get cached for requests that contain que
 
 | Cache behavior |  Description |
 | -------------- | ------------ |
-| Ignore query strings | Once the asset is cached, all ensuing requests ignore the query strings until the cached asset expires. |
-| Cache every unique URL | Each request with a unique URL, including the query string, is treated as a unique asset with its own cache. |
-| Ignore specified query strings | Request URL query strings listed in "Query parameters" setting are ignored for caching. |
-| Include specified query strings | Request URL query strings listed in "Query parameters" setting are used for caching. |
+| Ignore Query String | Once the asset is cached, all ensuing requests ignore the query strings until the cached asset expires. |
+| Use Query String | Each request with a unique URL, including the query string, is treated as a unique asset with its own cache. |
+| Ignore Specified Query Strings | Request URL query strings listed in "Query parameters" setting are ignored for caching. |
+| Include Specified Query Strings | Request URL query strings listed in "Query parameters" setting are used for caching. |
 
 | Additional fields |  Description 
 ------------------|---------------

articles/frontdoor/scenario-storage-blobs.md

@@ -63,7 +63,7 @@ As a content delivery network (CDN), Front Door caches the content at its global
 
 #### Authentication
 
-Front Door is designed to be internet-facing, and this scenario is optimized for publicly available blobs. If you need to authenticate access to blobs, consider using [shared access signatures](../storage/common/storage-sas-overview.md), and ensure that you enable the [*Cache every unique URL* query string behavior](front-door-caching.md#query-string-behavior) to avoid Front Door from serving requests to unauthenticated clients. However, this approach might not make effective use of the Front Door cache, because each request with a different shared access signature must be sent to the origin separately.
+Front Door is designed to be internet-facing, and this scenario is optimized for publicly available blobs. If you need to authenticate access to blobs, consider using [shared access signatures](../storage/common/storage-sas-overview.md), and ensure that you enable the [*Use Query String* query string behavior](front-door-caching.md#query-string-behavior) to avoid Front Door from serving requests to unauthenticated clients. However, this approach might not make effective use of the Front Door cache, because each request with a different shared access signature must be sent to the origin separately.
 
 #### Origin security