301 Redirect Rule for Path Not Triggering — Wildcard Rule Ignored

What is the name of the domain?

example com

What is the issue you’re encountering

We’ve set up a Redirect Rule in Cloudflare to redirect all requests from https://example.com/s/* to https://subdomain.example.com/s/${1} using a 301 permanent redirect. Despite following all the correct steps (wildcard pattern, proxy enabled, rule at top of list, preserve query string checked), the rule is completely ignored. Testing via https://httpstatus.io confirms that the URL loads the original app instead — no redirect happens. We also tested by redirecting to https://example.com to isolate the issue — still no result. It appears Cloudflare’s redirect engine is not triggering for path-based rules despite proper config.

What steps have you taken to resolve the issue?

What are the steps to reproduce the issue?

  1. Create a Redirect Rule with:
  2. Enable proxy on DNS for example.com
  3. Try visiting https://example.com/s/abc123
  4. Observe that no redirect occurs

It’s easier to check if you can give the domain.

Otherwise…

  • make sure you have a DNS record for the hostname you are redirecting from (use proxied AAAA 100:: if you don’t have a real origin) and that it is proxied
  • if the DNS record is for a host that also uses Cloudflare, you will need to see if they are using Cloudflare for SaaS and use their CNAME to point at them - otherwise requests will go direct to them and not through your Cloudflare account
1 Like