Hi, Yes I followed that documentation and all redirect rules are correctly firing except for this type of redirect. It looks like the problem is I have set them up with the most restrictive at the top and the least restrictive at the bottom. The problem is, as in my example, I can’t get the more general rule to execute. Is there a syntax problem? Essentially, I want to do what :splat: does except without the splat part.
/webinars/blockchain 301 isn’t a valid redirect rule. You’d need something like /webinars/blockchain /webinars 301 or /webinars/* /webinars 301
If /webinars/blockchain exists (a page/file is present) but you still want to redirect, you’ll need to use 301! in your rule (note the exclamation mark which forces the rule).
/webinars/blockchain is just an example. I want to redirect anything else in /webinars to the webinars directory without explicitly creating a rule for it. For example:
How do I make the first rule work and make a single rule that would apply to the rest? I have a thousand URLs and I dont want to create a separate rule for each if there is a way to do them at once.
Well, that depends what each URL is, there won’t be a one-size-fits-all
If you’ve got /webinars/amsterdam going to /custom/url/here and /webinars/berlin going to /another/even/randomer/link, we can’t create a pattern and there won’t be a one-size-fits-all rule.
