Stop Hardcoding 301s: How I Built a Redirect Engine That Doesn't Break at 2 A.M.

Marketing wants an A/B landing page by Friday. Product wants to gracefully deprecate a legacy API without breaking old mobile clients. Growth wants ten thousand short links, and Ops does not want ten thousand Nginx edits.

At some point, a single return 301 in your CDN stops being a configuration problem and becomes a routing product. Someone has to answer, on every HTTP request: Given this host, path, query, and method—where does this visitor go, and with which status code?

I built that answer as a pipeline at LinkShift. Not a pile of special cases, but a fixed sequence of steps that runs the exact same way for real visitors and for the tools you use to test rules before rollout.

Here is how I designed a deterministic redirect engine, the pipeline that powers it, and the edge cases that kept me up at night so they don't have to keep you up.

Why "Usually Works" Is Not Enough