Redirect upgrade options

Hi, I'm trying to figure out the process for getting more redirects for our sites. I've found this page: https://developers.cloudflare.com/rules/url-forwarding/#:~:text=Depending%20on%20your%20Cloudflare%20plan,replacement%20operations%20or%20regular%20expressions.

We are currently on the Pro plan, so we have 500 bulk redirects. It seems we need to upgrade to Enterprise for more redirects...

Is this true? We need 300 redirects for one of our sites... is there a way to get more redirects without upgrading from Pro > Enterprise?

Vvince Hi, I'm trying to figure out the process for getting more redirects for our site...

Chaika•1/25/24, 3:35 PM

I would consider other options. Are the redirects you need to make following some sort of format that can be created in a Dynamic Redirect Rule (ex: all pages on /posts/ are now under /blogs)?
You could also use Workers + KV to build your own redirect stuff, something like: https://github.com/Erisa/worker-links

CChaika I would consider other options. Are the redirects you need to make following som...

vinceOP•1/25/24, 3:39 PM

Hey Chaika, thanks for the reply. Unfortunately, all of these are static redirects that aren't able to be consolidated into dynamic redirect rules.

I'm not super familiar with sys admin things so my terminology / explanations could be wrong - but essentially what we need to do is sunset a website and take it off our third party server. That way whenever someone goes to x.comx.com (old website), CF will kick in and just redirect to y.com/slugy.com/slug. Will your second method with Workers work in this case?

Vvince Hey Chaika, thanks for the reply. Unfortunately, all of these are static redirec...

Chaika•1/25/24, 3:50 PM

Will your second method with Workers work in this case?

Workers are Cloudflare's serverless compute option, you can code workers in Javascript, they run on Cloudflare's edge, you can do any sort of redirect logic you can imagine/code with them

That way whenever someone goes to x.com (old website), CF will kick in and just redirect to y.com/slug

They'd all go different places, and that's why you need a bunch of static redirects?

CChaika > Will your second method with Workers work in this case? Workers are Cloudflare...

vinceOP•1/25/24, 3:51 PM

Thank you, and yup to your second point unfortunately.

There's a list of ~300 redirects that all look like:

...
x.com/slug y.com/slug
x.com/slug-1 y.com/slug-1
...

...
x.com/slug y.com/slug
x.com/slug-1 y.com/slug-1
...

frederik•1/25/24, 4:32 PM

If it's always the same slug I think you only need one redirect rule. https://developers.cloudflare.com/rules/url-forwarding/single-redirects/examples/#redirect-all-requests-to-a-different-hostname

Single Redirects — Example rules · Cloudflare Rules docs

The following sections contain example single redirect rule configurations.

Redirect upgrade options

Similar Threads

Similar Threads

Similar Threads