Serving Pages
Cloudflare Pages includes a number of defaults for serving your Pages sites. This page details some of those decisions, so you can understand how Pages works, and how you might want to override some of the default behaviors.
If an HTML file is found with a matching path to the current route requested, Pages will serve it. Pages will also redirect HTML pages to their extension-less counterparts: for instance, /contact.html will be redirected to /contact, and /about/index.html will be redirected to /about/.
You can define a custom page to be displayed when Pages cannot find a requested file by creating a 404.html file. Pages will then attempt to find the closest 404 page. If one is not found in the same directory as the route you are currently requesting, it will continue to look up the directory tree for a matching 404.html file, ending in /404.html. This means that you can define custom 404 paths for situations like /blog/404.html and /404.html, and Pages will automatically render the correct one depending on the situation.
If your project does not include a top-level 404.html file, Pages assumes that you are deploying a single-page application. This includes frameworks like React, Vue, and Angular. Pages' default single-page application behavior matches all incoming paths to the root (/), allowing you to capture URLs like /about or /help and respond to them from within your SPA.
In most situations, you should avoid setting up any custom caching on your site. Pages comes with built in caching defaults that are optimized for caching as much as possible, while providing the most up to date content. Every time you deploy an asset to Pages, the asset remains cached on the Cloudflare CDN until your next deployment.
Therefore, if you add caching to your custom domain, it may lead to stale assets being served after a deployment.
In addition, adding caching to your custom domain may cause issues with Pages redirects or Pages functions. These issues can occur because the cached response might get served to your end user before Pages can act on the request.
However, there are some situations where Cache Rules on your custom domain does make sense. For example, you may have easily cacheable locations for immutable assets, such as CSS or JS files with content hashes in their file names. Custom caching can help in this case, speeding up the user experience until the file (and associated filename) changes. Just make sure that your caching does not interfere with any redirects or Functions.
Please note that tiered caching is not supported for custom domains on Pages.
For browser caching, Pages always sends Etag headers for 200 OK responses, which the browser then returns in an If-None-Match header on subsequent requests for that asset. Pages compares the If-None-Match header from the request with the Etag it's planning to send, and if they match, Pages instead responds with a 304 Not Modified that tells the browser it's safe to use what is stored in local cache.
Pages currently returns 200 responses for HTTP range requests; however, the team is working on adding spec-compliant 206 partial responses.
Pages will also serve Gzip and Brotli responses whenever possible.
We will insert assets into the cache on a per-data center basis. Assets have a time-to-live (TTL) of one week but can also disappear at any time. If you do a new deploy, the assets could exist in that data center up to one week.
By default, Pages automatically adds several HTTP response headers ↗ when serving assets, including:
Access-Control-Allow-Origin: *Cf-Ray: $CLOUDFLARE_RAY_IDReferrer-Policy: strict-origin-when-cross-originEtag: $ETAGContent-Type: $CONTENT_TYPEX-Content-Type-Options: nosniffServer: cloudflare// if the asset has been encodedCache-Control: no-transformContent-Encoding: $CONTENT_ENCODING
// if the asset is cacheable (the request does not have an `Authorization` or `Range` header)Cache-Control: public, max-age=0, must-revalidate
// if requesting the asset over a preview URLX-Robots-Tag: noindexTo modify the headers added by Cloudflare Pages - perhaps to add Early Hints - update the _headers file in your project.