3 ms·
> There are still two additional round trips on the first https connection vs http. Not with HSTS preload.
by TazeTSchnitzel 11y ago
> There are still two additional round trips on the first https connection vs http.
Not with HSTS preload.
- collinmanderson 11y agoTrue
- pas 11y agoHow. How is that thing still considered a solution? We are talking about Chrome's HSTS preload, right? How come downloading all the Internet's certs with a browser is considered at all? Yes, it's nice, but it's a bigger hack than Win95's GUI on MSDOS.
- toast0 11y agoHSTS preload doesn't reduce the preamble to a TLS connection: You have to send the TLS client hello, wait for the TLS server hello back (1 Round trip), send the handshake finished, wait for the server handshake finished (2nd round trip), before sending application data. TLS 1.3 is supposed to help with that (although I haven't read the spec), but that's probably just bringing it down to one extra round trip in the common case. Add tcp (one round trip), and http (one round trip), and it's four round trips, twice as many as plain http. If you are serving us users on broadband, and you only have servers on one side of the country, half of your users are going to see about 80 ms round trip, so https slows down your first page load by 160 ms, even before you worry about encryption. If you have users around the world, and servers in only one location, you're likely to see many users with 250ms or 300 ms, an very simple https page (short request, short response) is going to take a minimum of 1 second (2 round trips for tls, one for tcp, and one for http), and if your users are on congested mobile networks, ouch.
- collinmanderson 11y agoIt doesn't reduce the TLS connection, but it reduces two round trips for the HTTP->HTTPS redirect. If the link is https in the first place then it's not a problem, but if you type in a domain name it will try HTTP first before starts the TLS connection.