Skip to content
Avandby Shokoofa AI
All documentation

Delivery and image transforms

How a request reaches an object, and what can happen to it on the way out.

The delivery path

A request arrives at a pull zone's hostname, matches a path, and is answered from the edge cache if the key is present. On a miss the zone fetches from its origin under a lease, so concurrent requests for the same cold key produce one origin fetch rather than one each.

Edge rules run before the cache is consulted. A rule can redirect, block, or bypass the cache, and the order of rules decides which one applies — a broad rule placed above a narrow one shadows it. The rule builder shows shadowing rather than leaving you to discover it in production.

Cache policy

Cache TTL is per zone. A purge clears a key across every replica through Redis pub/sub; a full-zone purge clears everything the zone has cached and asks for confirmation first, because refilling a large zone from origin is a real cost.

Image transforms

Images can be resized, cropped, converted and adjusted on the fly under /img, backed by libvips. The panel's playground asks the API to build the URL rather than assembling one itself, so what you copy is what the server would have produced. A generated srcset is used exactly as returned, width descriptors included.

Transforms are cached like any other delivery response, so a size you serve repeatedly is computed once.