CDN and content
CDN cache and purge
A targeted purge limits impact; a full purge requires explicit intent.
#Overview
A targeted purge limits impact; a full purge requires explicit intent.
#Understand a cache response
Caching depends on HTTP status, origin headers, configured TTL, and path. cdn.pizza response headers distinguish HIT from MISS and identify the serving POP.
A targeted purge invalidates one path in the zone. A full purge invalidates the entire zone and temporarily increases origin load; use it only when several unpredictable objects changed.
#Validate a publication
Request one URL and note status, age, and cache state.
Change the object or publish the new version.
Purge the exact path with
cdn-pizza purge -z ZONE_ID --path /asset.css.Request it again, confirm new content, and watch it return to HIT.
#Verifiable example
cdn-pizza purge -z ZONE_ID --path /assets/app.css