freshness review

Author: duongau

articles/cdn/cdn-troubleshoot-compression.md

@@ -2,26 +2,26 @@
 title: Troubleshooting file compression in Azure CDN | Microsoft Docs
 description: Learn how to troubleshoot issues with file compression in Azure Content Delivery Network. This article covers several possible causes.
 services: cdn
-documentationcenter: ''
-author: sohamnc
-manager: danielgi
-editor: ''
-
+author: duongau
+manager: kumudd
 ms.assetid: a6624e65-1a77-4486-b473-8d720ce28f8b
 ms.service: azure-cdn
 ms.workload: tbd
 ms.tgt_pltfrm: na
 ms.topic: troubleshooting
-ms.date: 01/23/2017
+ms.date: 02/27/2023
 ms.author: mazha
 
 ---
+
 # Troubleshooting CDN file compression
+
 This article helps you troubleshoot issues with [CDN file compression](cdn-improve-performance.md).
 
-If you need more help at any point in this article, you can contact the Azure experts on [the MSDN Azure and the Stack Overflow forums](https://azure.microsoft.com/support/forums/). Alternatively, you can also file an Azure support incident. Go to the [Azure Support site](https://azure.microsoft.com/support/options/) and click **Get Support**.
+If you need more help at any point in this article, you can contact the Azure experts on [the MSDN Azure and the Stack Overflow forums](https://azure.microsoft.com/support/forums/). Alternatively, you can also file an Azure support incident. Go to the [Azure Support site](https://azure.microsoft.com/support/options/) and select **Get Support**.
 
 ## Symptom
+
 Compression for your endpoint is enabled, but files are being returned uncompressed.
 
 > [!TIP]
@@ -32,14 +32,16 @@ Compression for your endpoint is enabled, but files are being returned uncompres
 > 
 
 ## Cause
+
 There are several possible causes, including:
 
-* The requested content is not eligible for compression.
-* Compression is not enabled for the requested file type.
-* The HTTP request did not include a header requesting a valid compression type.
+* The requested content isn't eligible for compression.
+* Compression isn't enabled for the requested file type.
+* The HTTP request didn't include a header requesting a valid compression type.
 * Origin is sending chunked content.
 
 ## Troubleshooting steps
+
 > [!TIP]
 > As with deploying new endpoints, CDN configuration changes take some time to propagate through the network.  Usually, changes are applied within 90 minutes.  If this is the first time you've set up compression for your CDN endpoint, you should consider waiting 1-2 hours to be sure the compression settings have propagated to the POPs. 
 > 
@@ -64,7 +66,7 @@ First, we should do a quick sanity check on the request.  You can use your brows
 > 
 > 
 
-Navigate to your endpoint in the [Azure portal](https://portal.azure.com) and click the **Configure** button.
+Navigate to your endpoint in the [Azure portal](https://portal.azure.com) and select the **Configure** button.
 
 * Verify compression is enabled.
 * Verify the MIME type for the content to be compressed is included in the list of compressed formats.
@@ -77,7 +79,7 @@ Navigate to your endpoint in the [Azure portal](https://portal.azure.com) and cl
 > 
 > 
 
-Navigate to your endpoint in the [Azure portal](https://portal.azure.com) and click the **Manage** button.  The supplemental portal will open.  Hover over the **HTTP Large** tab, then hover over the **Cache Settings** flyout.  Click **Compression**. 
+Navigate to your endpoint in the [Azure portal](https://portal.azure.com) and select the **Manage** button.  The supplemental portal opens.  Hover over the **HTTP Large** tab, then hover over the **Cache Settings** flyout.  Select **Compression**. 
 
 * Verify compression is enabled.
 * Verify the **File Types** list contains a comma-separated list (no spaces) of MIME types.
@@ -91,7 +93,7 @@ Navigate to your endpoint in the [Azure portal](https://portal.azure.com) and cl
 > 
 > 
 
-Using your browser's developer tools, check the response headers to ensure the file is cached in the region where it is being requested.
+Using your browser's developer tools, check the response headers to ensure the file is cached in the region where it's being requested.
 
 * Check the **Server** response header.  The header should have the format **Platform (POP/Server ID)**, as seen in the following example.
 * Check the **X-Cache** response header.  The header should read **HIT**.  
@@ -110,7 +112,7 @@ To be eligible for compression, a file must meet the following size requirements
 * Smaller than 3 MB
 
 ### Check the request at the origin server for a **Via** header
-The **Via** HTTP header indicates to the web server that the request is being passed by a proxy server.  Microsoft IIS web servers by default do not compress responses when the request contains a **Via** header.  To override this behavior, perform the following:
+The **Via** HTTP header indicates to the web server that the request is being passed by a proxy server.  Microsoft IIS web servers by default don't compress responses when the request contains a **Via** header.  To override this behavior, perform the following:
 
 * **IIS 6**: [Set HcNoCompressionForProxies="FALSE" in the IIS Metabase properties](/previous-versions/iis/6.0-sdk/ms525390(v=vs.90))
 * **IIS 7 and up**: [Set both **noCompressionForHttp10** and **noCompressionForProxies** to False in the server configuration](https://www.iis.net/configreference/system.webserver/httpcompression)