[Kathryn]

This has been driving me crazy. They are getting rid of the Page Rules. And new the Redirect Rules does not support the * wildcard and $1 target syntax anymore and there is no option for this in the drop down regex.

[Nicholas]

Do you have to pay for this now? What happened? NO EXPLANATION

[Kenneth]

I can’t find it right now. But I saw in the Developer docs a few days ago that wildcards are now only supported in the Business or Enterprise plan. Not sure if it’s accurate. But I saw them say it somewhere like that.

[Christopher]

I see only:

https://developers.cloudflare.com/rules/page-rules/reference/wildcard-matching/

Page Rules are deprecated. You should consider alternative Rules options due to their enhanced configurability. Refer to the migration guide for details.

[Logan]

https://community.cloudflare.com/t/static-vs-dynamic-redirects/584719/5

“Redirect Rules/Ruleset Engine does not support wildcard characters like that.
There is regex/matches support, but only for Business Plans or higher.”

welp.

[Amber]

GIVE US BACK OUR WILDCARDS CLOUDFLARE

[Christopher]

there’s a workaround using concat and substring but it’s pretty ugly and it doesn’t work as well in my tests, a CF employee mentions it on their forum.

Filter expression:

(starts_with(http.request.uri.path, "/old-path/"))

Dynamic URL redirect expression:

concat("/new-path/", substring(http.request.uri.path, 10))

where start byte value (10 in my example) is the length of the old path.

source
https://community.cloudflare.com/t/dynamic-wildcard-redirect-rule/657658/2

[Philip]

Cloudflare deprecates Page Rules and creates major confusion…

[Frances]

wow, looks easy! /s

🥺

[Angela]

I really hope they make a UI option for this, because it’s too difficult

[Author]

Posts