When redirecting users from a region-agnostic URL to a region-specific URL on a load balancer, Apply4 originally used HTTP 301 but found that Chrome cached the response too aggressively, breaking subsequent redirects. They switched to 302 — semantically imperfect but it worked in practice.