Cache Management

Cache Settings

Configure how Fast Edge Cache handles your content.

Default Behavior

Fast Edge Cache uses intelligent defaults that work for most websites. You can customize behavior using Cache-Control headers from your origin server.

Respect Origin Headers

Default: On

If your server sends Cache-Control headers, we'll respect them. Otherwise, we use smart defaults.

Browser Cache

Default: On

We send cache headers to browsers so returning visitors load even faster from their local cache.

Query String Caching

Default: Include

URLs with different query strings are cached separately (e.g., ?v=1 and ?v=2 are different cache entries).

Using Cache-Control Headers

Control caching behavior by setting headers on your origin server:

# Cache for 1 hour

Cache-Control: public, max-age=3600

# Cache for 1 year (versioned assets)

Cache-Control: public, max-age=31536000, immutable

# Don't cache (dynamic pages)

Cache-Control: private, no-store

Bypass Cache for Specific Paths

These paths automatically bypass the cache:

/admin/*
/wp-admin/*
/cart/*
/checkout/*
/my-account/*
/api/*

Need to bypass cache for additional paths? Contact support and we'll configure it for you.

Best Practice

Use versioned filenames for CSS and JS (e.g., app.v2.js) and set long cache times. This way you get maximum caching while still being able to push updates instantly.