HTTP and browser diagnostics guides

Compare saved HTTP redirect chains across a URL migration

·

Compare one saved response chain per starting URL. The starting address gives the first relative Location its base. Each response block supplies the recorded status and any redirect target used to interpret the next block.

Bulk Redirect Checker

Assemble one capture per starting address

Put the first address in Starting URL. Paste the response status lines and headers in order, beginning with the response from that address. Keep a blank line between recorded header blocks. Leave out bodies and add a separate chain for each starting address.

Choose Load example and Compare captures. Chain 1 starts at /old/ with status 301. Its relative Location ../catalog resolves to /catalog on the same host. The second block supplies status 200. The report displays the path and indicates omitted query and fragment values.

RFC 9110, Location fieldRFC 9110, HTTP redirection status codes

Distinguish repeated targets, errors and unavailable evidence

Open Chain 2 details. It records /a redirecting to /b and /b redirecting back to /a. Chain 3 records a 404. Chain 4 shows Capture unavailable because it has no response blocks.

Remove the final 200 block from Chain 1 and compare again. The checker shows Final response unavailable. Add a second Location to the saved 301 to see Unresolved redirect, because the captured target is ambiguous.

Distinguish repeated targets, errors and unavailable evidence
Saved evidenceComparison outcome
301 with relative Location followed by 200Recorded final response · 200
Location returns to an earlier addressRepeated address
Saved 404 responseRecorded HTTP error · 404
301 with a usable Location and no following blockFinal response unavailable

RFC 9110, Location fieldRFC 9110, HTTP redirection status codes

Review the report before sharing

Download redirect-comparison.json. It contains the chain number, observed status, outcome and per-block findings. Address paths and status codes remain visible. Review paths if your application puts identifiers in them.

Use the capture time and environment when documenting a migration. The workspace compares response evidence collected elsewhere. Location values identify intended targets, and the status lines provide the observed responses.

RFC 9110, HTTP redirection status codes

Common questions

Can I paste a proxy tunnel or informational response?

Yes. The report displays those response blocks while preserving the address for the next response. A final status comes from a non-interim block.

What happens if I leave the starting URL empty?

Absolute HTTP(S) targets can establish the next address. A relative Location remains unresolved when the address of its response is unknown.

Does changing only the fragment make a new HTTP request target?

The checker compares HTTP resource addresses without fragments, so a fragment-only change can appear as a repeated address.

Sources

Put it into practice.

Related guides