CDN Overview

Architecture basics and request lifecycle.

CDN Overview

acdn.uz uses pull zones: the edge fetches content from your origin on cache miss and serves cached objects from nearby nodes on subsequent requests.

  • Each pull zone has a zone hostname and can include additional hostnames.
  • The origin endpoint is configurable per zone, including optional Host header override.
  • TLS certificates are issued centrally by ACDN and securely deployed to edge nodes.
  • Traffic is optimized through edge cache, request coalescing, and routing logic.

Request Lifecycle

  • Client requests an asset from your pull zone hostname.
  • Optional token checks are applied before origin access.
  • Cache key is generated from scheme, host, path, and normalized query arguments.
  • If object is cached, edge returns it immediately with cache status metadata.
  • If object is missing or expired, edge fetches from origin, stores response, and serves it to client.