Skip to main content
Serve a site or files from an origin, and set cache, HTTPS, and request logs for that hostname. The base URL is https://api.gcore.com/cdn.

Delivery

A hostname pulls files from an origin group. A rule or a preset can override cache and security for one path.
  • CDN service — see whether CDN is enabled, which features are on, and the account limits
  • CDN resources — create the hostname, set where it pulls from, and change how responses are cached and delivered
  • Origins — group the servers that hold the original files
  • Rules — override settings for one path or file type; an option left unset keeps the resource value
  • Rule templates — save those overrides and apply them to another resource
  • Presets — apply a fixed bundle of options; the included options stay locked until the bundle is removed
  • Aliases — serve a second hostname with the same settings and a separate certificate
  • Origin shielding — send origin pulls through one location instead of every edge server

HTTPS

A resource can use an uploaded certificate, one issued for that hostname, or a CA certificate when the CDN connects to the origin.

Logs and usage

Request history, exported logs, and consumption figures are separate calls.
  • CDN activity logs — see who changed CDN settings, from the API or the Customer Portal
  • Log viewer — read recent requests; the field set and the time range are limited
  • Logs uploader — send the full request log to external storage, with a format and a destination
  • Statistics — read traffic and request series, including shielding, exported logs, and extra hostnames
  • Advanced analytics — query visitors, traffic, and requests for the last 90 days by country, directory, browser, device, or operating system

Cache and origin access

  • Tools — delete cached files, or load files onto edge servers before anyone requests them
  • Purge history — see whether a purge finished
  • IP addresses list — the addresses that connect to the origin, for an origin firewall