Welcome to the GGXG CDN developer documentation. These guides cover origin setup, cache configuration, the REST management API, and advanced routing rules.
Point your domain's CNAME record to your assigned edge hostname. Your edge hostname is visible in the Control Panel under Zones → Details.
; DNS configuration www.example.com. CNAME cname.eu1.ggxg.net.
After propagation (TTL 60–300 s) your traffic will begin routing through the nearest EU PoP. Verify with:
curl -I https://www.example.com/ # X-Cache: HIT from fra-edge-01.ggxg.net # X-GGXG-Pop: FRA
Base URL: https://api.ggxg.org/v2. All requests require a bearer token from Settings → API Keys in the Control Panel.
curl -X GET https://api.ggxg.org/v2/zones \ -H "Authorization: Bearer <API_KEY>"
Control caching behaviour by setting standard Cache-Control response headers on your origin, or by configuring page rules in the Control Panel.
Cache-Control: public, max-age=86400, stale-while-revalidate=3600
Assets matched by page rules override origin headers. Rule priority is evaluated top-down; the first matching rule wins.
Purge cached objects immediately via the API or Control Panel. Purge by URL, tag, or prefix.
POST /v2/zones/{zone_id}/purge
Content-Type: application/json
{
"files": ["https://example.com/image.png"],
"tags": ["product-images"],
"prefixes": ["https://example.com/static/"]
}
Certificates are provisioned automatically via ACME (Let's Encrypt) upon zone creation. Custom certificates can be uploaded in PEM format. Minimum TLS version is configurable: 1.2 or 1.3.
Managed rulesets are enabled by default at all PoPs. Custom rate-limit rules can be defined per zone with thresholds down to 10 req/s. Rules are applied at the PoP edge before reaching origin.
API keys are scoped to read, write, or admin. Rotate keys at any time without downtime. IP allowlists for API access are configurable under Settings → Security.