Added troubleshooting entry in Rules

Author: pedrosousa

src/content/docs/rules/reference/troubleshooting.mdx

@@ -7,10 +7,9 @@ head:
   - tag: title
     content: Rules troubleshooting
 description: Review common troubleshooting scenarios for Rules features.
-
 ---
 
-import { Example, Render } from "~/components"
+import { Example, Render } from "~/components";
 
 ## Interaction between Cloudflare challenges and Rules features
 
@@ -28,6 +27,12 @@ For example, define a compound expression for your rule using the `and` operator
 
 If you are using [HTTP DCV](/ssl/edge-certificates/changing-dcv-method/methods/http/) and also have [Single Redirects](/rules/url-forwarding/single-redirects/) set up in your zone, consider excluding the `/.well-known/*` path from your rule to avoid DCV issues. For details and other resources refer to the [SSL/TLS documentation](/ssl/edge-certificates/changing-dcv-method/).
 
+## Content-Length header removed from response
+
+Cloudflare may remove the `Content-Length` header from responses delivered to website visitors. If the visitor must receive the `Content-Length` header, configure the origin server to include a `cache-control: no-transform` HTTP header in the response.
+
+Alternatively, disable compression using a [compression rule](/rules/compression-rules/) and ensure that no Cloudflare settings are changing the response received from the origin server. For details on which products can change the response content, refer to [Notes about end-to-end compression](/speed/optimization/content/compression/#notes-about-end-to-end-compression).
+
 ## URL rewrites affect other Rules features executed later
 
 If you rewrite a URI path using a [URL rewrite](/rules/transform/url-rewrite/), this may affect other Rules features executed later — such as [Origin Rules](/rules/origin-rules/) — if they include the URI path in their filter expression.
@@ -36,17 +41,17 @@ Consider the following origin rule configuration:
 
 <Example>
 
-* Rule expression: `http.host == "example.com" and starts_with(http.request.uri.path, "/downloads/")`
-* **Host header** > **Rewrite to**: `assets.example.com`
+- Rule expression: `http.host == "example.com" and starts_with(http.request.uri.path, "/downloads/")`
+- **Host header** > **Rewrite to**: `assets.example.com`
 
 </Example>
 
 If you configure a new URL rewrite with the following configuration:
 
 <Example>
 
-* Rule expression: `http.host == "example.com" and starts_with(http.request.uri.path, "/downloads/")`
-* **Path** > **Rewrite to** > **Dynamic**: `regex_replace(http.request.uri.path, "^/downloads/", "/")`
+- Rule expression: `http.host == "example.com" and starts_with(http.request.uri.path, "/downloads/")`
+- **Path** > **Rewrite to** > **Dynamic**: `regex_replace(http.request.uri.path, "^/downloads/", "/")`
 
 </Example>
 
@@ -62,17 +67,17 @@ In the current example, you could use the `raw.http.request.uri.path` field in b
 
 <Example>
 
-* Rule expression: `http.host == "example.com" and starts_with(raw.http.request.uri.path, "/downloads/")`
-* **Path** > **Rewrite to** > **Dynamic**: `regex_replace(raw.http.request.uri.path, "^/downloads/", "/")`
+- Rule expression: `http.host == "example.com" and starts_with(raw.http.request.uri.path, "/downloads/")`
+- **Path** > **Rewrite to** > **Dynamic**: `regex_replace(raw.http.request.uri.path, "^/downloads/", "/")`
 
 </Example>
 
 **Origin rule**
 
 <Example>
 
-* Rule expression: `http.host == "example.com" and starts_with(raw.http.request.uri.path, "/downloads/")`
-* **Host header** > **Rewrite to**: `assets.example.com`
+- Rule expression: `http.host == "example.com" and starts_with(raw.http.request.uri.path, "/downloads/")`
+- **Host header** > **Rewrite to**: `assets.example.com`
 
 </Example>