Lighthouse
flags pages that aren't redirected to HTTPS:
Lighthouse audit that shows that HTTP traffic isn't redirected to HTTPS.
Lighthouse changes the page's URL to HTTP, loads the page, then waits for the
Chrome Remote Debugging Protocol
event that indicates that the page is secure.
If Lighthouse doesn't receive the event within 10 seconds, the audit fails.
How to redirect HTTP traffic to HTTPS
Once you've set up HTTPS,
make sure that all unsecure HTTP traffic to your site is redirected to HTTPS:
Use canonical links in the head of your HTML
document to help search engines figure out the best way to get to the page.
Configure your server to redirect HTTP traffic to HTTPS:
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2024-04-16 UTC."],[],[]]