Rules: Template to normalize encoded slash

Author: nikitacano

src/content/docs/rules/snippets/when-to-use.mdx

@@ -535,6 +535,7 @@ You should consider migrating a Worker to Snippets if it:
 - Needs to run an unlimited number of times for free on a Pro, Business, or Enterprise plan.
 
 Migrating to Snippets allows you to:
+
 - Leverage advanced request matching via the [Ruleset Engine](/ruleset-engine/).
 - Eliminate usage-based billing — Snippets are [included at no cost](/rules/snippets/#availability) on all paid plans.
 - Simplify management by integrating traffic modifications directly into Cloudflare Rules.
@@ -567,4 +568,4 @@ Cloudflare Snippets provide a production-ready solution for fast, declarative ed
 Snippets and Workers solve different problems:
 
 - Use Snippets for fast, lightweight traffic modifications at the edge, including header rewrites, caching, redirects, origin routing, custom responses, A/B testing and authentication.
-- Workers are built for advanced compute, persistent state, and full-stack applications.
+- Workers are built for advanced compute, persistent state, and full-stack applications.

src/content/docs/rules/transform/examples/normalize-encoded-slash.mdx

@@ -0,0 +1,40 @@
+---
+pcx_content_type: example  
+summary: Create a rewrite URL rule (part of Transform Rules) to normalize encoded forward slashes (`%2F`) in the request path to standard slashes (`/`).  
+products:  
+  - Transform Rules  
+operation:  
+  - Rewrite URL  
+title: Normalize encoded slashes in URL path  
+description: Create a rewrite URL rule (part of Transform Rules) to normalize encoded forward slashes (`%2F`) in the request path to standard slashes (`/`).  
+---
+
+import { Example } from "~/components";
+
+## Why normalize `%2F`?
+
+Different web servers and applications handle encoded forward slashes (`%2F`) in URLs differently. Cloudflare follows [RFC 3986](https://datatracker.ietf.org/doc/html/rfc3986), which specifies that `%2F` should **not** be automatically normalized to `/` because `/` is a reserved character in URLs, and decoding it might change the intended meaning of the path.
+
+However, many origin servers **do** automatically decode `%2F` into `/` when processing requests. If your origin server behaves this way, you may want to apply the same normalization at Cloudflare’s edge to ensure consistency in request handling, rule evaluation, and logging.
+
+## How to normalize `%2F`
+
+To normalize encoded forward slashes (`%2F`) to standard slashes (`/`) in the request path before [subsequent](/ruleset-engine/reference/phases-list/) rule evaluation, create a new rewrite URL rule and define a dynamic URL path rewrite using [`url_decode()`](/ruleset-engine/rules-language/functions/#url_decode) function:
+
+<Example>
+
+Text in **Expression Editor**:
+
+```txt
+(lower(raw.http.request.full_uri) wildcard "*%2f*")
+```
+
+Text after **Path** > **Rewrite to...** > _Dynamic_:
+
+```txt
+url_decode(http.request.uri.path)
+```
+
+</Example>
+
+This transformation ensures that `%2F` is always treated as `/` in the request path. This is particularly useful when setting up rules that depend on URL path matching, as it prevents discrepancies caused by differing normalization behaviors.