A redirect chain
One old address takes three redirects to reach the guide.
/training/examples/redirect-chain/start 301 → /training/examples/redirect-chain/old-guide 301 → /training/examples/redirect-chain/moved-guide 301 → /training/examples/redirect-chain/final 200
Open Network, turn on Persist Logs, then follow a link. Filter for HTML documents to see each response. Inspect the Location header on a 301.
| Request | Status | Location header |
|---|---|---|
/training/examples/redirect-chain/start | 301 | /training/examples/redirect-chain/old-guide |
/training/examples/redirect-chain/old-guide | 301 | /training/examples/redirect-chain/moved-guide |
/training/examples/redirect-chain/moved-guide | 301 | /training/examples/redirect-chain/final |
/training/examples/redirect-chain/final | 200 | None |
Compare the requests without navigating away
These buttons fetch the same routes. The result counts actual HTTP redirects returned by the same redirect handler used by the links above.
The responses use Cache-Control: no-store so the browser makes the requests again during the demonstration. No artificial delay is added.