How caching works
Every Cloudflare edge location keeps its own copy of the site’s responses, so visitors near it get them without a trip to storage.
When a production deployment succeeds, its files are new cache entries, and Sevalla also purges the cache of every domain of the site. You don’t need to purge after a deployment. The
_redirects and _headers rules run on every request, cached or not.
Browsers keep files other than HTML for 30 days, and purging the edge doesn’t reach them. Give such files a content hash in their name (most build tools do), or set a shorter Cache-Control with a _headers file.
Purge the cache
1
Open the networking settings
In the sidebar, click Static sites, then click the site. Click the Networking tab.
2
Purge
Under CDN/Edge cache, click Purge cache.
Cache purged. confirms it. There’s no dialog to accept first: purging deletes nothing from the site, and the next requests fill the cache again from storage. It clears the edge cache of every domain of the site, not the caches of visitors’ browsers.
Purge the cache:
- After you turn pretty URLs on or off. The change doesn’t deploy the site, so the edge keeps serving responses it cached before.
- When the edge still serves an old version after a deployment.
Purging needs permission to update the static site. Without it, Purge cache is disabled and says why.
HTTPS
Sevalla answers everyhttp:// request with a 301 redirect to the same URL on https://. The sevalla.page domain and every custom domain get an SSL certificate automatically, and custom domains accept TLS 1.2 or later. See SSL certificates.
CORS
Every response carriesAccess-Control-Allow-Origin: *, so other sites can fetch your files from the browser. To allow only some origins, set the header in a _headers file.