Taurus CDN — Demo Origin

Request headers seen by origin

The values below come from /headers on this origin — what Taurus's edge forwarded after applying its proxy_set_header rules. X-Forwarded-For should show the real client IP + Taurus's edge IP appended; X-Real-IP is the originating client; X-Customer-ID appears only when the per-customer header rewrite is enabled on the matching domain.

Host—

X-Forwarded-For—

X-Real-IP—

X-Forwarded-Proto—

User-Agent—

X-Customer-ID(not set)

All headers (raw JSON)

…

Static assets

Vary in size + MIME type so Taurus's static-asset caching, range requests, and content-type routing can be exercised. Right-click → copy link if you want to feed them to a load-test driver.

sample.jpg —

/static/sample.jpg

CSS

style.css —

/static/style.css

JS

app.js —

/static/app.js

PDF

sample.pdf —

/static/sample.pdf

MP4

sample.mp4 —

/static/sample.mp4

TXT

largetext.txt (gzip target) —

/largetext.txt

Cache-Control variants

Three endpoints, three different Cache-Control headers. Hit "Probe" to issue a fresh request and inspect the response headers Taurus sees from origin. The edge should respect these on first hit and apply them to its own TTL.

/cc/no-store

Returns Cache-Control: no-store. Taurus must NOT cache the response.

—

/cc/max-age-10

Returns Cache-Control: max-age=10. Short-lived TTL, useful for testing revalidation.

—

/cc/max-age-3600

Returns Cache-Control: max-age=3600. Hour-long TTL, the steady-state case.

—

Health & failure endpoints

Two synthetic endpoints to drive uptime probes and stale-if-error scenarios.

✓

/up Always returns 200 + plain text. Use as a liveness probe target.

—

✗

/500 Always returns 500. Use for stale-if-error + retry-budget tests.

—

ACME challenge passthrough

Requests to /.well-known/acme-challenge/<token> are served from /var/www/acme/.well-known/acme-challenge/ on origin so Let's Encrypt HTTP-01 challenges work when the edge proxies through. This origin's own cert is issued the same way.