One major use-case, yes. "We'll pay big bucks for you to fix the website. But also, we can't make any changes to the website." Fine, "patch" it with Cloudflare, just one more layer on top of the un-fixable mess for the next guy to deal with (in exchange for even bigger bucks).
- Redirects: We have several clients in the tech industry who host their docs and pages on Github pages. Github pages doesn't support 301s. This allowed us to both create 301s correctly and have a more manageable 301 platform for the non-development team.
- A/B testing through ghosting: A very large e-commerce client of ours wanted to run A/B test by ghosting (not to change URL) and slow roll out of the new platform. Through this they could chose which URL's were on the new platform and which ones on the old one and slowly rolled it all out.
In the future you will also be able to create pipelines so that there is a better management and audit process for bigger firms with security protocols around.
So, there are more benefits to this than just "When it's not practical to make the changes at the origin server". Infact if you are just "patching" then it's trouble.
> When the second barrier arose, we needed to inject Hreflang tags, cross-linking an old multi-lingual website on a bespoke platform build to an outdated spec. This required experiments to find an efficient way of implementing the tags without increasing latency or adding new code to the server – in a manner befitting of search engine crawling.
Is this a primary use case? When it's not practical to make the changes at the origin server?
What are the use cases when you are able to make server changes more easily?
Can you test what workers will do on a local development site somehow?