tools / redirect-inspector
Redirect Inspector
Inspect redirect chains, status codes, canonical loops, HTTPS upgrades, auth callbacks, and cache-control mistakes.
4 signals detected. Start with redirect loop.
Redirect loop
The same route or auth callback may be redirecting repeatedly.
Compare each Location value and break the loop at the first repeated destination.
HTTP/HTTPS scheme issue
Scheme handling or proxy headers may be wrong.
Check forwarded headers, canonical host config, and HTTPS enforcement at each layer.
Redirect status code
Redirect status codes are present.
Use 307/308 when method preservation matters and avoid accidental permanent caching.
Redirect caching risk
A redirect may be cached by browser or CDN.
Purge CDN/browser state and use temporary status while debugging.
HTTP/1.1 301 Moved Permanently
Location: http://example.com/login
HTTP/1.1 302 Found
Location: https://example.com/login?next=/login
redirect loop detected
DebugTools product
Redirect Inspector
Redirect Inspector is a focused DebugTools mini-product for developers. Inspect redirect chains, status codes, canonical loops, HTTPS upgrades, auth callbacks, and cache-control mistakes.
Use cases
- Debug request, response, header, status, redirect, and payload problems.
- Create a small reproduction before changing client or backend code.
- Compare working and failing network evidence without leaving the browser.
How it works
- Paste or load the snippet you want to inspect in Redirect Inspector.
- Run the tool in the browser and review the highlighted output.
- Copy, export, or turn the result into the next debugging step.
Privacy
- Redirect Inspector is local-first. The core workflow runs in your browser and does not require sending pasted content to DebugTools servers.
This tool history
Recent Redirect Inspector sessions
Only visits for this tool are shown. Pasted content, tokens, request bodies, and logs are not stored here.