Cloudflare worker as reverse proxy for webflow

Developers Workers
1

hi

I am working on a project where we have a webflow project and the requirement is that different customers can point their own domain to a subsite with us.

Example:
career.customer1.com points to xyproject.webflow.io/page1
and career page of customer 2 points to xyproject.webflow.io/page2
and so on…

The goal is also that the url of the customer remains visible in the address bar and not the target url of Webflow Hence the reverse proxy

As the domains are managed by our customers, I cannot set up the domain in Cloudflare. However, I was able to make a CNAME entry at customer1 for a test, which points to my worker. However, when I call up the page, I get the error message 1001.

I.e. the subdomain ends up at Cloudflare, but I think the worker is not called (there is nothing in the logs)

Is it even possible to solve the problem in this way?

Many thanks

3

Two things;

First, don’t reverse proxy webflow.io with a custom domain, you’d be violating Webflow’s terms of service by circumventing systems, and abusing their free staging-site hosting.

Second, you can’t modify a DNS that you don’t control, so if you want a client’s domain to point to your site then someone will need to make the necessary DNS changes for that domain. In a Cloudflare setup, that generally means having the client’s DNS running on Cloudflare.

However the basic arrangement of what you’re describing → a site partitioned into parts with different domains exposing each “micro-site”, is very possible. You could simply do redirects, or use workers to create a micro-site with its own homepage, sitemap, etc.