Behind edge ✓host cdn-playground-five.vercel.appproto httpscdn-loop vergcloud-staging; count=1

Panel setup → hit playground route → see result → iterate

CDN Playground lab index

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.

Setup checklist

  1. Deploy this app to a stable public origin URL.
  2. Create a Verge CDN domain pointing at the origin.
  3. Open this page through the CDN hostname (banner shows edge ✓).
  4. Pick a feature card, apply its panel config, run the probe.
echoready

Inspect what the origin received

Dump headers, IP, URL and timing to distinguish edge vs direct origin hits.

Open labecho-inspect
cacheready

Short edge TTL

Cacheable JSON with s-maxage=60. First hit MISS, second hit HIT at edge.

Open labcache-edge-ttl
cacheready

Immutable static asset

Long-lived fingerprinted asset under /assets with immutable cache-control.

Open labcache-immutable
cacheready

no-store bypass

Personalized endpoint that must never be cached at the edge.

Open labcache-no-store
firewallready

Allow-listed fixture

Benign path that WAF rules must let through with origin JSON intact.

Open labfirewall-allow
firewallready

Block probe path

Suspicious probe that a firewall rule should stop at the edge.

Open labfirewall-block-path
custom-pagesready

Forced 403 with origin fingerprint

Origin returns a unique 403 body; edge custom page should replace it when configured.

Open labcustom-403
custom-pagesready

Forced 404 with origin fingerprint

Deterministic 404 body used to verify edge custom 404 pages.

Open labcustom-404
custom-pagesready

Forced 502/503 with origin fingerprint

5xx fixtures for origin-error custom pages and retry behavior.

Open labcustom-502
rate-limitready

Rate-limit canary

Cheap ping endpoint; send N requests and count 200 vs 429.

Open labrate-limit-ping
tlspartial

HTTPS / HSTS observation

Check scheme, redirects, and HSTS visibility through the edge.

Open labtls-https
analyticspartial

Labeled traffic generator

Generate N hits to unique tagged paths, then find them in analytics.

Open labanalytics-tagged
/lab/cache
Cache lab
HIT/MISS, TTL, immutable, no-store
/lab/firewall
Firewall lab
Allow vs block fixtures
/lab/custom-pages
Custom pages
403/404/502 fingerprints
/lab/rate-limit
Rate limit
429 canary with N-request sender
/lab/tls
TLS lab
HTTPS, HSTS, redirects
/lab/analytics
Analytics
Tagged traffic generator