Resolve a relative Location and find the end of a redirect capture
Admin ·
Start with the address the client requested and the order of the captured responses. Those facts determine how a relative redirect target is interpreted.
Resolve a relative redirect
A 302 for https://example.org/docs/old with Location: ../guide resolves to https://example.org/guide. A following 200 is the recorded outcome at the inferred address. If you recorded only the first response, the final status is unknown.
Interpret a repeated address
A 307 can send a client to a previously observed address. Compare the recorded statuses and Location fields. More than one Location in one redirect makes the next target ambiguous, so the report stops inferring an address until another absolute target appears.
Recognize where the evidence runs out
A recorded 302 and Location field show that the server told the client where to go. Without the next captured response you cannot say that the target returned 200. Keep the last inferred URL separate from the last observed status.
Compare the recorded starting URL with the base used to resolve relative Location values. A wrong path or trailing slash can produce a plausible but incorrect next hop.
Common questions
Is a 304 a redirect hop here?
A 304 reports that a cached representation can be reused. The redirect tracker follows Location on 301, 302, 303, 307 and 308.
Does the checker visit a URL from a capture?
All addresses are parsed as local text. The report records what the supplied capture shows.
Sources
Put it into practice.
Related guides
- Read a saved HTTP response header dump
- Compare recorded response headers
- Interpret a security header grade
- How to Read a Recorded HTTP Status Sequence
- HTTP Method Safety and Retry Guide
- How to Validate Hreflang Return Links
- Test Apache Page and Folder Redirects
- Read a Saved Link Header for Pagination
- Check an App Seller File and Its Host
- Compare Saved Redirect Chains
- Check Redirect Rules Before Export