Redirects are part of the request path. WebCheck records them and validates every destination, so a target can fail even when its initial URL is reachable if the chain ends at an invalid, restricted or unexpected destination.
What WebCheck follows
WebCheck handles redirects one hop at a time up to its configured redirect limit. Absolute destinations and supported root-relative paths are resolved, then validated before the next request.
Common redirect problems
- A redirect points to a removed or misspelled path.
- A deployment creates a loop or exceeds the redirect limit.
- An HTTPS page redirects down to HTTP.
- A hostname redirects to a restricted or unintended destination.
- A login or consent redirect replaces the public page response.
What to inspect
Open the run details and review the redirect count, final URL, statuses and error code. Compare the chain with curl or browser developer tools, then inspect routing, CDN and reverse-proxy configuration.
Security boundary
WebCheck does not follow a redirect that downgrades HTTPS or reaches a destination rejected by its network-safety rules. Do not weaken those rules to hide a redirect problem.