Third-party CDN

When having localized sites on separate domains or subdomains, Glopal is usually configured in front of your existing site, including WAF/CDN. In this default configuration, WAF/CDN features enabled for your existing site are inherited on localized sites.

While this setup simplifies the initial configuration, you can also choose to configure your existing WAF/CDN in front of Glopal localized sites for additional flexibility in traffic management. This is considered an advanced setup, enabling more options, including intelligent bot control for restricting unwanted traffic.

For localized sites on your existing domain with a traffic split setup, your existing WAF/CDN is already in front of Glopal without any extra configuration. In this setup, Glopal is behind your WAF/CDN, serving only delegated paths.

When enabling a third-party WAF/CDN for localized sites, ensure Glopal can fetch source content without going through the same WAF/CDN. Using a CDN in front of both your source and localized sites may cause a "CDN loop," making localized site unreachable.

Before enabling a third-party WAF/CDN in front of your localized sites, please share your "true origin server" details (hostname or IP addresses). Activate your WAF/CDN in front of the localized site only after receiving confirmation from Glopal that configuration is updated to avoid "CDN loop".

Platform Instructions

Select below the correct instructions for the service you are running.

Cloudflare