Redirect HTTPS straight to the other host's HTTPS page
Why it matters
The HTTPS homepage of this host redirects visitors to the plain http page of its www or non-www twin, although the twin serves the site over https itself and visitors lose the encrypted connection on the way. Point the redirect at the twin's https address instead.
The fix
- Follow the redirect with the command below. The first Location header starts with http:// and names the other form of your host (www.example.com or example.com); that hop is the one to change.
- Make the https server of example.com answer with a redirect straight to the https:// address of that other host, keeping the path. Do not send https visitors to http:// first.
- Check that https:// of the other host answers with the site and not with another redirect back.
bash
curl -sIL https://example.com/ | grep -iE '^(HTTP/|location:)' The examples use example.com. Replace it with your own domain.
Related
- Reported by the HTTP to HTTPS redirect check
- Serve the site over HTTPS
- Stop redirecting HTTPS to HTTP
- Redirect HTTP to HTTPS
- Redirect HTTP to HTTPS instead of answering an error
- Check that browsers are redirected from HTTP to HTTPS
- Fix the broken HTTPS redirect chain
- Shorten the redirect chain
- Fix the HTTP redirect chain
- Redirect HTTP straight to HTTPS
- Answer HTTP with a redirect to HTTPS
- Redirect www and apex to one host
- Make the www or apex name work over HTTPS
Scan your domain to see whether this applies to you.