https://*every site here*
summary
Chrome adds an opt‑in certificate error report that surfaces real-world causes and shows client clocks cause about 47% of validation failures, while misconfigured AV/network proxies account for >2% of errors. Chrome implements a clock interstitial and experiments with seamless redirects for near‑miss hostnames, ships support for the upgrade-insecure-requests header to auto‑fix mixed content, and launches a DevTools security panel plus a public key pinning reporting mode so sites can test pins without bricking themselves.
AI-written summary · about
chapters (8)
- 0:00The case for HTTPS everywhere
- 3:59Identifying HTTPS barriers
- 8:27Client-side HTTPS issues
- 12:40Managing security misconfigs
- 17:43Improving user experience
- 21:47Tooling for developers
- 24:07Public key pinning
- 32:08Security panels and future
