A bounded HTTP request followed three or more redirects
ShipReady observed three or more redirect responses before a final HTTP 200 response for the scanned target.
Why it matters
A redirect chain is useful to review because entry URLs can often be simplified without changing the intended destination.
How ShipReady detects it
What it inspects
ShipReady makes one streamed redirect-following HTTP GET for the target and reads response history, status, and headers without reading the body.
What triggers a finding
It triggers when that request ends at HTTP 200 with at least three redirect responses in its history.
What the evidence shows
The evidence proves the number of redirects observed in that bounded scan-time request.
Limits of this check
The base response must be successfully fetched with status 200 first. Request failures and 408, 429, or 5xx responses are incomplete inspections, not findings.
ShipReady does not use a browser, measure latency, inspect every entry URL, or establish the same chain for all users, networks, caches, or future requests.
How to fix it
Review the observed evidence
Trace the reported chain and point entry URLs directly to their intended destination where compatible with the deployment.
How to verify the change
Verify the intended behavior
Repeat a redirect trace for the public entry URLs after deployment.
Expected: The intended entry URL reaches its destination with the planned redirect count.