Common questions
Short answers. For field-level API detail, see the docs.
Is this compatible with KeyCDN’s API?
Management uses HTTP Basic with the API key as username and an empty password. Zones, aliases, referrers, purge, and reports follow KeyCDN envelopes and field names. Shared zone hosts use your CDN domain instead of kxcdn.com.
Push vs pull zones?
Push (static) stores files under /data/static/<zone>/ and serves with sendfile. Pull fetches from an origin URL; the edge caches responses (with a separate image cache) and returns X-Cache HIT/MISS headers.
How do I upload many files?
Open Media library, pick a push zone, then use Files, Folder, or drag-and-drop. Uploads run one file at a time so the browser and server stay stable. Folder pick uses the standard HTML directory input and keeps relative paths.
How does purge work?
Zone or URL purge from the panel or API. Control fans out to every active edge. A purge_generation in the snapshot is the backstop if a node missed the fan-out.
Do I put the CDN behind Cloudflare?
Use Cloudflare for DNS if you want, but keep CDN hostnames DNS-only (grey cloud). Proxying (orange cloud) puts another CDN in front of yours and breaks direct edge IPs, purge semantics, and simple HTTP-01 for aliases.
What about Let’s Encrypt?
One alias per zone can use Let’s Encrypt (HTTP-01). Shared zones use a shared/wildcard certificate on your CDN domain. Custom PEM pairs are supported when sslcert=custom.
Is streaming / HLS included?
No. First launch is static and pull delivery for web assets. HLS and HTTP/3 are catalogued for later.