Page rules detection
I have several Ghost blogs, for each of them I set up a 301 redirect when they were installed www to root. However, in the Cloudflare rules pages, the redirect only appears for one of my blogs, I don't understand why. It's as if Cloudflare didn't detect it for certain blogs.
70 Replies
yup
Are you saying you created a Page rule before, and it's gone now?
If you're saying it just doesn't work for the other blogs, you need to create an "originless" DNS Record so the traffic reaches Cloudflare and hits the redirect.
AAAA www 100:: Proxied would do the trick. 100:: is IPv6 discard, just saying "If you get through the entire CF flow without hitting a redirect rule/etc, go nowhere". Even though this is an IPv6, since it is proxied, it'll work for both IPv4 & IPv6 Visitors to hit your Page RuleNo, this is not exactly that
I say that I manually created a redirect rule on my server for all my blogs, but when creating DNS zone in Cloudflare this redirect www to root domain is detected by Cloudflare by only one of the 4 blogs, and I don’t understand why
hmm like it didn't autodetect the www dns record?
no, it did not imported in rules the www redirect to root for 3 blogs, and it did for one
Page Rules aren't imported or anything, it wouldn't create one for you, unless you or an integration did specifically
you could check audit logs if it was recently enough to see what created itt
It is maybe amazing but I never created the rule
it has been automatically created for one of my blog
and match exactly the 301 redirect I set up on my server
but only in 1 case over 4 different websites
yea there's no auto import/auto creation based on your server doing a redirect or anything like that. If Ghost has an integration where you give it an CF API Key, then maybe it. Otherwise, you can check Audit Logs and filter for that specific domain, if it was recently enough it should show it
no integration of cloudflare, just my dns zone but there is no link between ghost and cloudflare
Then most likely you created it.
CF wouldn't auto create a page rule redirect for you, it wouldn't make sense anyway, some redirects are server-side and based on other attributes like IP/Country/etc, how would CF sense all of these?
They don't
I swear I never created it !
so in a way or another cloudflare understood or have been able to read it. or it created this rule because it is a famous rule ?
but finally, what I would like to know is, can I delete this rule I set it up on my server directly ?
Sure, it could have been an integration or something else. The Audit logs are the only real way you'd find out, https://dash.cloudflare.com/?to=/:account/audit-log, you can filter by domain (just put your domain name/zone name).
so in a way or another cloudflare understood or have been able to read it. or it created this rule because it is a famous rule ?No, my point was just that it's not feasible for Cloudflare to try to understand redirects. Cloudflare didn't create the page rule.
but finally, what I would like to know is, can I delete this rule I set it up on my server directly ?Absolutely, if your server normally handles it you'd be fine. Cloudflare redirects are faster though and less load on your origin, if you can use them, I would
to your mind, I would better use cloudflare redirect rather than my personal server redirect ? but in that case should I delete the redirect of my server ? or can I let both ?
If your redirect is simple enough to be in a Page rule/bulk redirect rule/dynamic redirect, Cloudflare. But I would keep both if you can, it won't hurt anything, if it matches Cloudflare, Cloudflare will serve it, and in case you ever need to pause Cloudflare/forget to set it up, you've got a backup
nice to know