Content delivery
Test how your CDN serves a regional asset.
Compare the delivered asset revision
A CDN rollout changes a first-party stylesheet. From approved test regions, record the requested asset key, expected version, returned checksum and relevant cache evidence. Check content identity before investigating timing differences.
How to run the review
Record cache headers and the file checksum on an endpoint you own. Distinguish content selection errors from slow network delivery.
Network selection
Compare the characteristics of datacenter proxies with the test's geographic and session requirements. Check the planned region in the coverage directory.
Session setup
Use a fixed datacenter exit for a regional asset series and record the cache state. Move to another documented exit only when starting a separate market comparison.
Frequently asked questions
Does an older asset automatically indicate a broken cache?
Check its documented lifetime, cache key and deployment time. An earlier asset can remain valid until the stated freshness interval ends.
Can a faster response still be a failed delivery test?
Yes. If the returned asset has the wrong revision or market variant, it fails a content-correctness check regardless of speed.