HTTP redirects
When a server responds with a 3xx status and a Location header, clients follow that next URL. ChainTrace follows those hops manually (up to 10), recording status and timing for each.
Common statuses
- 301 — Permanent redirect (cached aggressively by browsers).
- 302 — Temporary redirect (historical “Found”).
- 307 / 308 — Temporary / permanent while preserving the request method more strictly.
Why chains matter
Each extra hop adds latency and can dilute how clearly a preferred URL is signaled to crawlers. After migrations, aiming for a single hop to the final URL is a common hygiene goal.
Loops
If a hop returns to a URL already seen in the chain, ChainTrace stops and flags a loop. Browsers and crawlers also stop after detecting cycles.