Meeting the New York Times Challenge – Delivering the news over HTTPS
summary
The New York Times challenges sites to be fully HTTPS by 2015 and this session explains moving FiveThirtyEight to HTTPS: buying certificates (wildcard limits, SGC is obsolete), using Let's Encrypt and sslmate for issuance and renewal (Let’s Encrypt uses 90‑day certs), configuring servers with HSTS preload and SNI, fixing mixed content with a crawler and CSP reporting, and noting HTTP/2 (over HTTPS) benchmarks show 1.88× faster load times; ads and some third‑party embeds remain the main blockers.
AI-written summary · about
