CDN.gd Documentation

Appearance

Storage Zone error handling and pairing ​

Shape how missing objects are served and connect Storage Zones to Pull Zones for global delivery.

Error handling ​

  • 404 rewriting: toggle on when you want missing objects to return a friendly asset (for example 404.html).
  • Not-found file path: set the path to the fallback object to keep static sites polished instead of exposing raw storage errors.
  • Keep fallback assets small to avoid wasteful egress on high-miss routes.

Pairing with Pull Zones ​

  • Origin selection: in a Pull Zone, choose “Storage Zone” as the origin type and pick the zone from the list (or create it inline).
  • Hostname strategy: route user-facing domains through the Pull Zone so CDN.gd manages TLS and caching; avoid exposing the Storage Zone endpoint directly.
  • Caching alignment: set longer TTLs on Pull Zones fronting Storage Zones and rely on purging rather than bypassing unless the path is dynamic.

Operational tips ​

  • Use a dedicated Storage Zone per application or per environment to keep error handling and cache policies isolated.
  • When publishing single-page apps, enable 404 rewriting to the main 200.html (vary by framework) or index.html to support client routing without server rewrites.