A real site, standing in for a customer origin.

This property exists to test one thing: whether a customer's site can be served from a Vercel project through a Cloudflare Worker, on the customer's own domain, with nothing leaking and nothing breaking.

Read the test plan See the page set

Live request diagnostics

Browser host: —
Full URL: —
Protocol: —
Asset host: —
Canonical: —
API probe: —
Rendered: —

What each page is for

Deep paths

Nested routes like /blog/reverse-proxy-notes confirm the proxy forwards the whole path, not just the root.

Static assets

CSS, JS and an SVG are all served from /assets/ using root-relative paths, which should survive proxying untouched.

Canonical tags

Every page declares an absolute canonical. This is where an upstream hostname usually leaks, so it's worth watching.

JSON endpoint

/api/health.json is fetched by client-side JavaScript to confirm same-origin requests still work through the hop.

404 handling

A missing path must return a real 404, not a soft 200 — otherwise search engines index junk.

Trailing slashes

Both /about and /about/ should resolve without redirecting off the public domain.