Linux Server / Networking, SSH & Web Services
Investigate an HTTP redirect loop through proxy and origin evidence
A site can loop when the application misinterprets forwarded scheme or hostname information. Inspect one response before following an unlimited chain.
Environment and inputs: Linux server baseline · Ubuntu 24.04 LTS / RHEL 9-style systems. Use the specified distribution, init system and installed tool; service names, privileges and supported options can differ.
Start with this check
Confirm the host, shell and access role. Replace sample names, paths, domains and interfaces with approved targets. These are diagnostic commands; assess policy and workload impact before making changes.
curl -I --connect-timeout 5 --max-time 10 https://example.comRead the result
The response headers expose the first Location value where present. A HEAD response can differ from GET and does not reproduce browser cookies or authentication.
Resolve and verify
Compare the public URL, proxy forwarding policy and application's trusted-proxy configuration. Correct the verified scheme or host mismatch and test the normal user flow.
Before changing production
Do not trust arbitrary forwarded headers from the public internet or remove HTTPS enforcement to hide the loop.