Cloudflare Edge Configuration Demo

DNS, TLS, HTTP, cache, and performance validation on a custom domain.

This small technical demo documents how a static site is deployed through Cloudflare Workers Static Assets and validated with DNS lookups, HTTPS/TLS, response headers, redirects, cache behavior, and page-load checks.

Architecture diagram showing browser traffic reaching Cloudflare edge and a Pages origin

DNS

The custom subdomain resolves through Cloudflare DNS and invokes a Worker that serves static assets at the edge.

TLS

HTTPS is served at the Cloudflare edge and validated with browser inspection and command-line checks.

HTTP

Response headers and redirects are configured explicitly so their behavior can be tested with curl -I.

Performance

Static assets are cacheable and can be evaluated with repeated requests, Cloudflare headers, and page-load tooling.