June 2026 promo! Join our Discord free of charge.

Slick­Stack
Lightning-fast WordPress on Nginx

how to implement wildcard 301 in Cloudflare’s new “redirect rules”

  • This topic is empty.
Viewing 10 posts - 1 through 10 (of 10 total)
  • Author
    Posts
  • May 23, 2024 at 8:00 am #25014
    Kathryn
    Guest

    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.

    May 23, 2024 at 8:02 am #25015
    Nicholas
    Guest

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

    May 23, 2024 at 8:05 am #25016
    Kenneth
    Guest

    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.

    May 23, 2024 at 8:06 am #25017
    Christopher
    Guest

    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.

    May 23, 2024 at 8:09 am #25018
    Logan
    Guest

    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.

    May 23, 2024 at 8:09 am #25019
    Amber
    Guest

    GIVE US BACK OUR WILDCARDS CLOUDFLARE

    May 23, 2024 at 8:15 am #25020
    Christopher
    Guest

    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

    May 23, 2024 at 8:16 am #25021
    Philip
    Guest

    Cloudflare deprecates Page Rules and creates major confusion…

    May 26, 2024 at 6:15 am #25053
    Frances
    Guest

    wow, looks easy! /s

    🥺

    May 28, 2024 at 6:14 am #25078
    Angela
    Guest

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

  • Author
    Posts
Viewing 10 posts - 1 through 10 (of 10 total)
Reply To: how to implement wildcard 301 in Cloudflare’s new “redirect rules”

Thanks to our generous sponsors for their support!