Redirect Chain Inspect

Parse and diagnose HTTP headers and routing signals in your browser. No input is sent to a server. Use it for first-pass observation-gap troubleshooting.

Status

Runs in your browser. No input is sent to a server. Use this as a first-pass diagnostic step.

How to use

Paste redirect logs or Location lines and click “Parse”. It lists steps and URLs.

Notes (this tool)

  • Relative URLs require a base URL; interpret them with the previous step.

About this page

What does this tool do?

Paste multiple Location/status lines to list the redirect chain.

Useful for diagnosing https loops, domain mismatches, and missing query params.

Basics (why chains matter)

  • Redirects often chain; seeing only one step can hide the real cause.
  • You must track both Location and status (301/302/307/308).
  • Loops occur when you return to the same URL or bounce between schemes/hosts.

Input examples

  • HTTP/1.1 301 + Location: https://example.com/
  • Location: /login
  • 301 https://example.com/ → 302 https://example.com/login

Why it helps (find loops/mismatches)

You need to see where the change happens. A chain view makes that obvious.

Examples (common patterns)

  • http→https→http loop
  • www ↔ non-www bounce
  • Query drops mid-chain

How to test (measure)

Redirects should be verified from real responses. Use curl to see status and Location together (replace the URL).

  • Check single-step Location with curl -I https://example.com/
  • Follow the chain with curl -I -L https://example.com/ (useful for loops)

Common pitfalls

  • Relative URLs depend on base URL and can be misread
  • X-Forwarded-Proto/Host can change generated Location
  • Ignoring status semantics (307/308)

Troubleshooting checklist by symptom

  • HTTPS loop: check if Location flips scheme and verify X-Forwarded-Proto/Host consistency
  • Unexpected domain: check for Host/Forwarded/X-Forwarded-Host rewrites
  • Query loss: suspect URL building/encoding mistakes

Debugging workflow (recommended)

  • Use curl -I -L to capture the chain
  • Paste here to organize steps/patterns
  • Use Location Inspect for per-URL details
  • Location Inspect
  • X-Forwarded-Proto Inspect
  • Host/Authority/Origin Inspect
  • Response Headers Parser

What this tool does

  • Organize multiple Location/status lines into steps
  • Show hints for repeated URLs (loops)
  • Extract Location from logs/full headers

Operational notes

  • Intermediaries may rewrite headers. Compare captures from equivalent points.
  • Confirm final decisions with server logs and configuration such as trusted proxy and routing.

Referenced specs

  • RFC 9110 (HTTP Semantics)
  • MDN: Redirections

FAQ

How are relative URLs resolved?

They are resolved against the previous URL; the prior step is crucial.

How to detect loops?

Loops usually repeat URLs or patterns; list the chain to spot repeats.

References

  1. RFC 9110
  2. MDN: Redirections

These links are generated from site_map rules in recommended diagnostic order.

  1. HTTP Status Inspect — Analyze HTTP status codes and suggest handling direction
  2. Location Inspect — Parse Location header and split destination URL

Redirects

Use status codes and Location chains to isolate redirect issues