Skip to content

Commit fee9039

Browse files
authored
PCX review
1 parent 54cd7d1 commit fee9039

File tree

1 file changed

+1
-3
lines changed

1 file changed

+1
-3
lines changed

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

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -11,9 +11,7 @@ description: Create a rewrite URL rule (part of Transform Rules) to normalize en
1111

1212
import { Example } from "~/components";
1313

14-
## Why normalize `%2F`?
15-
16-
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.
14+
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.
1715

1816
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.
1917

0 commit comments

Comments
 (0)