Rules: Add URL Rewrite Template for Normalizing Encoded Forward Slashes (%2F) #20994
Conversation
|
Howdy and thanks for contributing to our repo. The Cloudflare team reviews new, external PRs within two (2) weeks. If it's been two weeks or longer without any movement, please tag the PR Assignees in a comment. We review internal PRs within 1 week. If it's something urgent or has been sitting without a comment, start a thread in the Developer Docs space internally. PR Change SummaryIntroduced a new Transform Rules template for normalizing encoded forward slashes in request paths.
Added Files
How can I customize these reviews?Check out the Hyperlint AI Reviewer docs for more information on how to customize the review. If you just want to ignore it on this PR, you can add the Note specifically for link checks, we only check the first 30 links in a file and we cache the results for several hours (for instance, if you just added a page, you might experience this). Our recommendation is to add What is Hyperlint?Hyperlint is an AI agent that helps you write, edit, and maintain your documentation. Learn more about the Hyperlint AI reviewer and the checks that we can run on your documentation. |
|
Preview URL: https://54cd7d15.preview.developers.cloudflare.com Files with changes (up to 15) |
src/content/docs/rules/transform/examples/normalize-encoded-slash.mdx
Outdated
Show resolved
Hide resolved
…es (%2F) (#20994) * Rules: Add URL Rewrite Template for Normalizing Encoded Forward Slashes (%2F) * PCX review --------- Co-authored-by: Pedro Sousa <[email protected]>
2 participants
Summary
This PR introduces a new Transform Rules template that allows customers to normalize encoded forward slashes (%2F) in the request path to standard slashes (/). This helps align Cloudflare’s request handling with origin server behavior, as many web servers automatically decode %2F into /.
The template uses the url_decode(http.request.uri.path) function to ensure consistency in URL-based rule evaluation, logging, and request processing. This change does not alter Cloudflare’s default behavior, which follows RFC 3986 by preserving encoded reserved characters. Instead, it provides an optional one-click solution for users who need it.