How it works
Incoming request paths are looked up in a Config Store — Fastly's
globally distributed key-value store. Each entry maps a source path to a
status:destination pair (e.g. 301:https://fastly.com/blog).
The Compute service reads the entry, extracts the HTTP status code and target URL,
and returns an instant redirect — all at the edge, with no origin round-trip.