Google I/O 2014 - HTTPS Everywhere
Why Stack Overflow recommends it
Stack Overflow users link it when arguing for moving sites to HTTPS, especially on the privacy and performance case alongside SPDY and HTTP/2.
Recommended by 0 people across 0 different months, 2014 to 2016.
What it is
A Google I/O 2014 session by Ilya Grigorik and Pierre Far arguing that all web traffic should be encrypted. It walks through the technology, configuration and performance practices for HTTPS, and how to migrate a site while staying user and search friendly.
Cited in 1 Wikipedia article, including HTTPS.
What people said
Cites igrigorik · 2014-08 · Stack Overflow · on “How can I detect, server side, if the client supports SPDY?”
All data is sensitive: the sites you visit, the pages you've viewed, etc. By aggregating this data across many pages, you can infer a lot about the user: their intent, interests, and so on. Hence, we need HTTPS everywhere. For more, see our Google I/O talk [1] on the subject. In terms of detecting SPDY support, yes you want to use NPN/ALPN (ALPN is a successor [2]). The client sends a ProtocolNameList in their handshake, which advertises which protocols they support. Most servers will use this to auto-negotiate SPDY, but if you want to control this decision yourself, you'd have to modify your server implementation to invoke some sort of callback when the secure handshake is being performed.
Cites alexrogers · 2015-05 · Stack Overflow · on “What is the best and current way to move to HTTPS on a large website?”
From watching HTTPS everywhere on YouTube [this video] they suggest that HTTPS and SPDY combined will be quicker than just serving web pages/assets over HTTP but then since reading SPDY is Dead. Long Live HTTP/2 [LINK] and what with with HTTP2 support being a way off I am in two minds as to whether to move a large site I'm working on to HTTPS entirely as ultimately it will be slower since doing perf comparison tests (the DOM content loaded took twice the time to load). I also just read somewhere that browsers are dropping support for SPDY. What is the state of SPDY and should I just wait until HTTP2 until I advocate moving everything to HTTPS everywhere? Should I accept the performance hit?
Cites Kevin Chen · 2016-04 · Stack Overflow · on “Where should you enable SSL?”
Browsing a TLS connection has no perceptible overhead for client or server [LINK] and enabling HTTPS improves users' privacy [this video] and protects your site from being modified in transit [LINK] by ISPs and core network operators. If HTTP/2 is enabled, TLS can even improve web page performance [LINK] .