Inspect what the origin received
Dump headers, IP, URL and timing to distinguish edge vs direct origin hits.
cdn-playground-five.vercel.appproto httpscdn-loop vergcloud-staging; count=1Panel setup → hit playground route → see result → iterate
A deterministic Next.js origin for testing Verge CDN behavior. Point a CDN hostname at this app, change settings in the Verge panel, then run the probes below to see edge vs origin results.
Dump headers, IP, URL and timing to distinguish edge vs direct origin hits.
Cacheable JSON with s-maxage=60. First hit MISS, second hit HIT at edge.
Long-lived fingerprinted asset under /assets with immutable cache-control.
Personalized endpoint that must never be cached at the edge.
Benign path that WAF rules must let through with origin JSON intact.
Suspicious probe that a firewall rule should stop at the edge.
Origin returns a unique 403 body; edge custom page should replace it when configured.
Deterministic 404 body used to verify edge custom 404 pages.
5xx fixtures for origin-error custom pages and retry behavior.
Cheap ping endpoint; send N requests and count 200 vs 429.
Check scheme, redirects, and HSTS visibility through the edge.
Generate N hits to unique tagged paths, then find them in analytics.