close

Slick­Stack

July 2024 promo! Join our Discord free of charge.

Slick­Stack
Lightning-fast WordPress on Nginx

Cloudflare deprecates Page Rules and creates major confusion…

  • This topic is empty.
Viewing 12 posts - 1 through 12 (of 12 total)
  • Author
    Posts
  • #25008 Reply
    Laura
    Guest

    Last week they put a notice that Page Rules is being deprecated. Now everyone is supposed to use the other rules like Cache Rules, Configuration Rules, Redirection Rules. But the documentation totally sucks. And the regex/etc is totally different from Page Rules.

    #25009 Reply
    Frances
    Guest

    I noticed that, when will page rules disappear?

    #25012 Reply
    Douglas
    Guest

    https://developers.cloudflare.com/rules/page-rules/

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

    no date given.

    #25013 Reply
    Pamela
    Guest

    They are probably aware that it would break half the internet if they hurry to cancel the Page Rules functionality so they are just trying to push everyone to stop using it

    #25022 Reply
    Gregory
    Guest
    #25023 Reply
    Marie
    Guest

    Yah, idk seems sus.

    Is this really improving the UI or some plot to make it more confusing lol

    #25029 Reply
    Aaron
    Guest

    Another thing I noticed is the new “Cache Rules” no longer support “Cache Everything” setting like the old Page Rules did, which sucks. Because it eliminated cookies from requests.

    #25042 Reply
    Janet
    Guest

    🥲🥲

    #25335 Reply
    Patrick
    Guest

    did they reverse course? I no longer see “Deprecated” notice on Page Rules?

    #25362 Reply
    Andrew
    Guest

    If you’re looking for an alternative, check out Cloudflare’s new feature: https://developers.cloudflare.com/rules/snippets.

    It lets you control your cache easily.

    Try this snippet:

    `javascript
    const response = await fetch(request, {
    cf: {
    cacheEverything: true,
    cacheKey: request.url,
    cacheTtlByStatus: {
    “200-299”: 604800, // Cache successful responses for 7 days
    “404”: 1, // Cache not found responses for 1 second
    “500-599”: 0 // Do not cache server errors
    }
    }
    });
    `

    Using this method doesn’t add any extra charges. Workers could do the same, but they come with a per-request fee, which adds up.

    Snippets aren’t free, but a basic paid plan gives you 10. One advanced snippet can replace multiple page-rules, making it a cost-effective solution.

    However, this isn’t a solution if you were utilizing the free plan for many domains.

    – Chad 😉

    #25363 Reply
    Ruth
    Guest

    Is this really improving the UI or some plot to make it more confusing lol

    probably more a plot to make more money. because they are saying the “wildcard” redirect rule is now only available on paid plans, which is some greedy a*****e s**t to do after half the internet has been using Cloudflare for years already…

    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.”

    #25453 Reply
    Matthew
    Guest

    did they reverse course? I no longer see “Deprecated” notice on Page Rules?

    seems like they are keeping it now.

    https://developers.cloudflare.com/rules/page-rules/

Viewing 12 posts - 1 through 12 (of 12 total)
Reply To: Cloudflare deprecates Page Rules and creates major confusion…

Thanks to our generous sponsors for their support!