What it means
Somewhere in a redirect chain an https:// address sends visitors to an http:// address. The
connection that was encrypted becomes unencrypted for the next request. The detail names the entry points
where this happens.
Why it matters
Anyone on the network can read and change the plain HTTP request, so the protection HTTPS gave
on the first hop is lost. If you send HSTS, browsers refuse the downgrade and visitors see an error instead.
Downgrades usually come from an application that builds absolute URLs from a setting that still says
http://, or from a redirect rule written before the site moved to HTTPS.
How to fix it
- Find the hop in the chain that goes to
http://; the result shows its status and address. - Change that redirect to point at the
https://address. - Check your application's base URL setting: WordPress Address and Site Address,
APP_URLin Laravel,SITE_URLor similar. Set it tohttps://. - Behind a proxy or CDN, make the application trust
X-Forwarded-Protoso it knows the visitor used HTTPS.
Check it worked
Run the HTTP and security headers check again. No chain should contain an http:// hop after an
https:// one, and the finding should be gone.