Image pipeline
Source files are normalised once and delivered in AVIF, WebP or JPEG depending on what the requesting client advertises. Width and density variants are generated on first request and cached thereafter.
Asset delivery
Media assets, served close to your readers.
This host serves static assets — images, fonts, stylesheets and video posters — for Northwind Media properties. Origin content is cached at the edge and revalidated on publish, so editorial changes propagate within seconds.
Cache policy
Fingerprinted paths are immutable and carry a one-year max-age. Unversioned paths use a short TTL with stale-while-revalidate, so a slow origin never blocks a page render.
Availability
Requests are answered from the nearest healthy region. If a region is drained for maintenance, traffic shifts automatically and no configuration change is required.
Access
Public assets are open. Pre-release and embargoed material is signed with a short-lived token issued by the editorial CMS and is not reachable without it.
Common questions
- Why does an asset return 404 right after publishing?
- The path is fingerprinted at build time. Re-run the publish step so the CMS emits the current URL.
- Can I hotlink from an external site?
- Yes for public assets. Referrer-restricted buckets are documented in the integration guide.
- How do I purge a cached object?
- Purges are automatic on republish. Manual invalidation is available to editorial staff from the CMS.