Documentation

Point a hostname at the gateway and start serving cached media over HTTPS. Most integrations take a few minutes.

Quick start

Create a CNAME from your media hostname to your assigned gateway endpoint, then request assets over HTTPS as usual. The gateway terminates TLS and caches responses at the edge.

media.example.com.  CNAME  cdn.streamcache-media.com.

DNS setup

Two records are enough to get started: one for the asset hostname, and an optional apex alias.

media   CNAME  cdn.streamcache-media.com.
@       ALIAS  cdn.streamcache-media.com.

Propagation usually completes within 15–30 minutes. TLS certificates are issued automatically once the hostname resolves to the edge.

Cache control

Standard Cache-Control headers from your origin are respected, so you keep full control of freshness and TTLs. You can also override TTLs per path from the dashboard.

Cache-Control: public, max-age=86400, stale-while-revalidate=600
Vary: Accept-Encoding

Purge API

The API is provisioned per account: your base URL and bearer token are shown in the dashboard once you sign up. The example below is illustrative.

Invalidate a path across all edge nodes with a single authenticated request.

curl -X POST https://cdn.streamcache-media.com/v1/purge \
  -H "Authorization: Bearer $TOKEN" \
  -d '{"paths":["/video/intro.mp4","/img/*"]}'

Response headers

Every response carries diagnostic headers so you can inspect cache behaviour:

X-Cache — HIT, MISS or STALE
X-Edge-Location — the PoP that served the request
Age — seconds the object has been cached

Media & range requests

Range requests are honoured end to end, so players can seek within large audio and video objects without pulling the whole file. Large objects are streamed from the edge and revalidated in the background.