Cache & Redirects

Browser cache stores redirect responses to speed up navigation. It also affects analytics if clicks repeat without triggering new requests.

---

How it works

• 301: signals a permanent move. By default browsers may cache it, unless cache headers say otherwise.
• 302/307: indicate a temporary redirect and are usually re-checked on revisit.
• 308: is similar to 301 but preserves the original HTTP method.

With Cuttly in practice

Cuttly sends redirect responses with no-cache headers, so browsers revalidate the target on each click instead of relying on stored redirects. This keeps analytics accurate and ensures that any change you make to a destination is applied immediately.