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

Custom pages lab

Forced error statuses with unique origin bodies. Compare edge custom pages vs origin fingerprints.

Setup guide

CDN → Domain [domain] → Custom Page

Suggested config

  • Keys: firewall_error (403), error_500, rate_limit_exceeded (429) — no 404/502 keys in API
  • Upload type=file via POST /v1/custom-pages/{domain}
  • Origin /status/403, /404, /502 keep ORIGIN-*-FINGERPRINT (passthrough by design)

Verify

  1. Firewall block ?mode=evil → branded firewall_error 403 page
  2. Fetch /status/403, /404, /502 → ORIGIN fingerprints (no edge replace)
  3. Status code stays the same, body source differs

Origin routes

All probes are same-origin through the CDN hostname. Open routes in a new tab to compare edge vs origin headers.

No request yet — hit a button above to run a probe.