You should use configuration rules. Page rules are old an probably going away eventually.
You should use configuration rules. Page rules are old an probably going away eventually.
Cwell it's not probably it's just a matter of time they announced
Ayea i just read that
Cbut yea you can use a config rule and
Host starts with .<yourdomain>.com should work
Uah didnt know they publicly said this did they say when yet?
CThe Cloudflare Blog
Learn about four new products that will eventually replace Page Rules by putting more power into the hands of users.
Cit was a while ago, no further update then that afaik
UOh the initial blog said they would kill them didnt realize that 
Cyea they said definitively they will be going away, just no eta/time
We’re replacing Page Rules with four new dedicated products, offering increased rules quota, more functionality, and better granularity. These products are available immediately for testing. Page Rules is not going away yet, but we do anticipate being able to formally begin the end-of-life process soon.
ASo a configuration rule like this?
UI would just put hostname is not
site.comAhostname?
U
Aoh.. reverse it. ok
Ai was hoping there was a variable for site.com
EWhats up?
Cthat would also run on any cf for saas custom hostnames if you have any, but otherwise pretty simple and would get the job done
UEh yeah for disabling zaraz though doesnt matter so 
UAlso probably not many people use that anyways
UI do think the configuration for saas should be more explicit though
Ahmm.. i should try to migrate my current page rule (redirects from www.site.com to site.com)
Alittle lacking in the doc as well. wonder if this uses the $1 and such like page rules
Aweird. community is still suggesting the use of page rules.. https://community.cloudflare.com/t/redirect-the-www-to-non-www/558655
UThat was 4 days before the new rules
Ahah
Uor actually it was wrong year lol
Uit was 1 year after but
EBulk Redirects is what I would recommend for that
EIn this guide, you will learn how to redirect the www subdomain to your apex domain (example.com). This is a common question and can be achieved by …
EIts out of beta now
Awhats the difference between the top and bottom? other than the fact the top doesnt work
Aoh, bulk redirects are account specific. not domain specific
EThe bottom defines the lists, the top shows which are deployed
EI need to remember to update that doc it seems the dash changed a bit
Ayea this doc doesnt follow anything 
EIt made sense at one point, sorry about that
Cthe dash is nice and guided now, hard to mess up
Aare the source and target urls regex or what?
Acan i make 1 bulk rule to handle all domains?
Cno regex, you can enable subdomain matching or subpath matching in edit parameters though
CNothing is regex really except if you specifically use match(), Page Rules supported wildcards but none of the new stuff using Ruleset Engine (the new rules, cache, config, etc) or Bulk Redirects support wildcards outside of using match() (which is biz or higher), have to use specific functions like starts with, contains, etc
Acloudflare tunnels are also regex
Cehh they cheat, the path regex bit is local
Ayea surpised me when my regular domain/paths weren't working and overmatching 
AI'll leave my page rules for the www bit for now. no need to change it.. tho it would be amazing to have a simple way to make all www become apex
Cyea, all that runs on the connector/cloudflared in Go, Cloudflare's part is just having the dns record proxied cname and sending traffic down the tunnel, can use dns wildcards for that but no regex running on CF's edge
Cpage rules aren't going away yet thankfully, still some stuff like redirecting subdomain + path which is really hard in redirect rules but easy in Page Rules, the matching/replacement wildcards is super powerful
C(well, hard to do without business match function)
Ayea thats what i'm using. it seems like the perfect design www.site.com becomes site.com/$1
UThe UX for bulk redirects is very bad ngl. Took me way too long to setup a simple www. to root
Normal redirect rules are easy to shuffle through in the UI but needs a function to preserve the path which is annoying.
Normal redirect rules are easy to shuffle through in the UI but needs a function to preserve the path which is annoying.
Awere you able to do this with wildcards? or did you have to specify everything