Pull Zone caching and performance

Configure cache behaviour, compression, and on-the-fly optimizations to keep responses fast without breaking origin intent.

Caching controls

• Toggle caching per zone. When enabled:
  • Cache-Control max-age override: pick presets from no-cache up to one year.
  • TTL for valid content and TTL for invalid content: keep success responses long-lived and errors short-lived.
  • Respect or ignore query strings for cache keys.
  • Optionally respect origin headers instead of overriding them.
• Bypass rules:
  • Paths: skip cache for exact or glob-style paths that must remain dynamic.
  • Cookies: bypass when a request carries specific cookies (useful for authenticated sessions).

Compression

• Brotli: enable and choose the MIME types to compress.
• Gzip: enable, toggle Vary: Accept-Encoding, and select MIME types.
• Use Brotli for modern browsers and keep gzip enabled for legacy clients.

Protocols and optimization

• HTTP/2 and HTTP/3 can be toggled independently.
• Asset optimization:
  • Minify CSS and JavaScript at the edge.
  • Convert compatible images to WebP automatically.
• Start with all performance toggles on, then tune per application if you see anomalies (e.g. JS minification on already-optimized bundles).

Operational tips

• Keep TTL for invalid content low to avoid sticky 404/500s.
• Combine cache bypass rules with security policies so personalized content is never cached.
• When attaching a Storage Zone, expect higher cache-hit ratios; set longer TTLs and lean on cache invalidation rather than bypassing.