Webflow wants us to be on Enterprise to get this "Reverse Proxy as a Service" feature. This costs $50k minimum per annum.
Has anybody had any luck in getting Webflow to work consistently behind Cloudflare? We've got it semi-working, but get the occasional HTTP 406 for a few hours every now and then when they block Cloudflare's IP range.
upstream webflow {
server proxy-ssl.webflow.com:443;
}
location @webflow {
resolver ;
proxy_pass https://webflow;
proxy_set_header Host $webflow_host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $corrected_proxy_scheme;
proxy_ssl_verify off;
proxy_ssl_session_reuse on;
proxy_ssl_server_name on;
proxy_ssl_name $webflow_host;
}
Elsewhere (a Lua script), I set the $webflow_host variable and URI for the request, which is exec-ed from that Lua script (which is basically an internal redirect to the @webflow location block).
I haven't had issues with Cloudflare blocking IPs - however the site in question is rather low traffic, so we probably don't pop up on their list.
Main reason for doing this was having routing control. We also had a long list of redirects to manage from an old site, and it was easier to do this in an nginx config.
Does your site change so fast that punishing it then hosting it yourself doesn’t work?
Can you cache the requests more aggressively?