Solutions Engineering Lab

Pages, Functions, redirects, and edge diagnostics.

This lab demonstrates how Cloudflare can serve static application content through Pages, run dynamic logic with Pages Functions, normalize routes with redirects, and expose practical diagnostics from the Cloudflare edge.

Open App Page API Info Health Diagnostics Headers

Lab 3 Identifiers

Static Page Identifier

Static page served by Cloudflare Pages.

This landing page is static content delivered globally by Cloudflare Pages under the primary www hostname.

Dynamic API Response

Loading live /api/info response...

Lab Routes

/app/

Static application route served by Cloudflare Pages under the primary hostname.

Open /app/ →

/api/info

Dynamic Pages Function response showing service, Cloudflare colo, country, and time.

Open /api/info →

/health

Health check endpoint for quick availability and edge reachability testing.

Test /health →

Restored Diagnostics

/diag

Shows request and Cloudflare edge metadata including colo, TLS, hostname, and path.

View /diag →

/headers

Displays request headers visible to the edge function in a readable table.

View /headers →

/app redirect

Normalizes /app to /app/ for consistent route behavior.

Test /app redirect →

What This Demonstrates

Static Delivery Cloudflare Pages serves the landing page and app route as static content.

Dynamic Edge Logic Pages Functions handle API, health, diagnostic, and header inspection routes.

Route Ownership www.ybarra-cflab.com stays owned by Pages instead of being moved back to a standalone Worker.

Redirect Behavior /app normalizes to /app/, giving the application path predictable behavior.

Edge Observability Diagnostic routes show what Cloudflare sees at the edge, including request headers and Cloudflare metadata.