Caching
Caching
Caching is the core mechanism that makes fast.site fast. It stores copies of your website's responses at our global Edge Servers to serve content instantly.
How caching works
1
Cache MISS (First Request)
fast.site forwards the request to your origin server, returns the response, and stores a copy in memory.
2
Cache HIT (Subsequent Requests)
The cached copy is found and served in under 5ms without contacting your origin server.
3
Expiration
Entries expire based on your origin's Cache-Control headers or rules you define.
Response Headers
fs-cacheValues: HIT, MISS, BYPASS. Indicates if content came from cache or origin.
fs-cache-ageNumber of seconds the cached object has been stored at the Edge.
fs-cache-hitsNumber of times the cached entry has been served. Useful for spotting hot URLs.
Cache Purging
When your website content changes, manually clear cached copies to force a fresh fetch from your origin.
Purge by URL
https://example.com/about
API Purge
DELETE /my/domains/:id/cache