Data Types

Cloudflare Setup Guide

Please follow this guide if you've configured an External HTTP URL that points to a website or API that runs behind Cloudflare.

Cloudflare is a leading CDN provider and is well-known for its DDoS challenge response screens:

Configuring an AWS S3 bucket

Cloudflare challenge responses are designed to intercept the first request to a website, which is usually an HTML webpage.

Once the user has been verified, Cloudflare sets a cookie to skip challenge responses for subsequent requests, allowing images to be downloaded for the page, and for subsequent pages to be requested.

  1. User makes an HTTP request to a Cloudflare-protected URL.

  2. Cloudflare may return a challenge response:

    • Receiving a challenge response is considered normal and does not always indicate your browser's signature or your IP is suspicious.

    • The HTTP status code will always be 403, even if the response automatically passes (see below).

    • The HTTP response body will be an HTML document containing JavaScript.

    • The JavaScript will either:

      • Redirect you automatically to the underlying webpage/asset.

      • Display a human captcha form.

      • Reject the request.

Cloudflare challenge responses are good for protecting URLs that are accessed by humans.

However, challenge responses often cause problems for URLs that are accessed by external services, like the Bytescale CDN:

  1. Since the initial URL loaded by the Bytescale CDN is often an asset (e.g. an image) as opposed to a webpage, there is no way for the Bytescale CDN to forward the challenge response to the user, since the user won't see the challenge response due to the asset being loaded via an <img /> element as opposed to a browser tab.

  2. The Bytescale CDN cannot adopt the user's existing Cloudflare session cookie, since this will be tied to your site's domain as opposed to the Bytescale CDN's domain.

  3. The Bytescale CDN is likely to issue many concurrent requests on behalf of your users, especially for high-traffic sites, meaning Cloudflare is likely to trigger challenge responses more regularly.

We recommend pointing your External HTTP URL directly to your origin, as opposed to routing your requests via Cloudflare.

If this is not possible, you can whitelist the Bytescale CDN in your Cloudflare account to prevent challenge responses.

Please follow these steps:

  1. Login to the Cloudflare Dashboard

  2. Click "Websites"

  3. Click on the website referenced by your External HTTP URL

  4. Click "Rules" > "Configuration Rules"

  5. Click "Create Rule"

  6. Rule name: "Bytescale CDN Whitelist Rule"

  7. When incoming requests match...

    1. Select "Custom filter expression"

    2. Rule details:

      • Field: "User Agent"

      • Operator: "equals"

      • Value: UploadCDN

        • Note: this field is case sensitive.

  8. Add "Browser Integrity Check" and set to OFF

  9. Add "Hotlink Protection" and set to OFF

  10. Add "Security Level" and set to OFF or ESSENTIALLY OFF

  11. Click "Deploy"

Additional steps for "Super Bot Fight Mode":

If your site has "Super Bot Fight Mode" enabled, then you may need to perform the above steps under Security > WAF > Custom Rules instead.

Please note: the Bytescale CDN performs its own DDoS protection and caching to protect your origin from distributed attacks.

These pages may also be helpful:

Was this section helpful? Yes No

You are using an outdated browser.

This website requires a modern web browser -- the latest versions of these browsers are supported: