Caching Profiles

Cache profiles outline the broad settings most applicable to your site. They provide a reliable default configuration, which you can modify to match exactly what your site needs.

Profile	HTML Pages	Redirects	404s	Assets	Cache-Control Respected
Full Site Profile	180 mins	180 mins	4 mins	3 days	No
Assets Only Profile	Not Cached	10 mins	1 min	3 days	Yes, except asset URLs

Full Site Profile

Use this profile if your entire site is public, with pages that do not require users to log in and do not display different information to different users.

Pages cached 180 minutes
Redirects cached 180 minutes
404's cached for 4 minutes
Asset files (images, js, and css) cached 3 days
Cache-Control Headers Ignored

Assets Only Profile

Use this profile if your application is mostly dynamic, with each page being customized to the user that is logged in or if pages are updated with data in the background.

Pages are not cached
Redirects cached for 10 minutes
404's cached for 1 minute
Asset files (images, js, and css) cached 3 days
Cache-Control Headers Respected (except asset URLs, see below)

HTTP Response Cache-Control header directives are how your application tells the WAF what URLs should be cached and for how long.

Asset URLs Are an Exception

In both profiles, any URL whose path ends in an asset file extension (images, CSS, JavaScript, PDFs, and similar) is handled by the asset caching rules instead of your application’s Cache-Control headers. The edge network replaces the response’s Cache-Control and Expires headers with its own long-lived values. This applies to redirects served at those URLs as well as to the files themselves.

See the Asset File Caching article for the full list of extensions and details on how these headers behave.