All demos / Workers · Routes · HTMLRewriter

The core concept

Your origin server never
knows a Worker exists.

A Cloudflare Worker intercepts HTTP requests that match a Route pattern (e.g. *shoplegacy.com/*). Your origin receives a perfectly normal request, returns a normal response, and the Worker transforms it on the way back — invisibly.

✓

Origin code unchanged

0 lines edited

✓

DNS unchanged

same domain, same records

✓

Deploy in 10 seconds

one command: wrangler deploy

Request Flow

Browser

sends request

⚡ Cloudflare Edge
Route Check
*shoplegacy.com/*
Worker
runs here

Your Origin

unchanged ✓

Click "See how routes work" to animate

Everything you need — 2 files + 1 command

1
✏️ Write a Worker

A small TypeScript file. It fetches from your origin, optionally transforms the response, and returns it. Your origin gets a normal HTTP request.

await fetch(request) // calls your origin .then(res => transform(res)) // modify
2
🗺 Add a Route

One line in wrangler.toml tells Cloudflare which URLs this Worker intercepts. Pattern supports wildcards. Multiple routes supported.

pattern = "*shoplegacy.com/*"
3
🚀 Deploy

One command. Worker is live globally in ~10 seconds on Cloudflare's 250+ PoPs. Rollback is one command too.

wrangler deploy # done

Total changes to your origin: 0 — Not one line. The Worker is deployed independently on Cloudflare's infrastructure, not on your servers.

Same URL. Two different experiences.

Left: origin only · Right: Worker route active (chatbot injected via HTMLRewriter)

Click "See Routes in Action" to load both versions

Other things the same route can do

🧠

Add AI Sentiment

Enrich every API response with AI analysis

See demo →

🔍

Rewrite Search

Intercept /api/search and replace with Vectorize

See demo →

⚡

Cache Responses

Store in KV, skip origin on repeat calls

See demo →

🖼️

Optimize Images

Rewrite image URLs to /cdn-cgi/image/...

See demo →