Is Webflow blocking the proxied requests when using a reverse proxy in front of it?
TL;DR
- Webflow is optimized for direct access and generally incompatible with reverse proxies, which can break features or cause requests to be blocked.
- While workarounds exist (e.g., using NGINX or Cloudflare Workers), they require careful header handling and HTTPS passthrough, and remain unsupported by Webflow.
Webflow does not officially support or guarantee compatibility with reverse proxies, and it may block or behave inconsistently with proxied requests depending on how the reverse proxy is configured.
1. Webflow's Hosting Model
- Webflow is a fully managed hosting platform, optimized for direct access via its own servers and CDN.
- Using a reverse proxy can interfere with TLS termination, custom header validation, and Webflow’s internal logic for security and optimization.
2. Potential Issues with Reverse Proxies
- Blocked requests: If your reverse proxy removes or alters standard headers (like
Host,X-Forwarded-For, orReferer), Webflow may reject or misroute those requests. - Rate limiting or caching errors: Webflow uses CDNs (e.g., Fastly, AWS CloudFront) which may interpret reverse-proxied traffic as suspicious if it looks like a bot or abuse pattern.
- Session or form handling errors: Reverse proxies might strip or mishandle Webflow-required cookies or POST payloads, leading to failures in forms, CMS filters, or logins.
- Dynamic features: Proxies may break Webflow features like Site Search, Memberstack/Membership integrations, or ecommerce functionality.
3. Known Workarounds (Risky/Unsupported)
- Some developers use a reverse proxy (e.g., with NGINX or Cloudflare Workers) to:
- Rewrite or hide URLs,
- Integrate Webflow into a larger non-Webflow app,
- Localize routing or load balance.
- Success depends on:
- Preserving headers (especially
Host), - Passing through HTTPS correctly without downgrading,
- Maintaining origin request integrity,
- Avoiding blocked user-agents or suspicious IPs.
4. Webflow's Stand on Proxies
- Webflow doesn't offer support for debugging proxy setups and may throttle or block traffic that doesn’t look like a direct browser-level interaction.
- Traffic that appears as automated, manipulated, or inconsistent may be treated as hostile or as bot traffic.
Summary
Webflow is not designed to work behind a reverse proxy, and proxied requests may be blocked or behave unpredictably. While some setups may temporarily function, they are unsupported and likely to break or be throttled by Webflow’s infrastructure.
