3 ms·
12 kilobytes is nothing when accessing a web page that's 2MB. One possible improvement: only negotiate one key per server. When opening a new connection to a s
by immibis 3y ago
12 kilobytes is nothing when accessing a web page that's 2MB.
One possible improvement: only negotiate one key per server. When opening a new connection to a server that was very recently accessed, just keep using the existing security channel. In other words, mandate HTTP 2.
- _trampeltier 3y agoYeah, with todays bloated websites, this few KBs don't really matter at all. Where do you even find a webpage today who is "just" 2MB.
- hinkley 3y agoNo it’s still a lot. The 2 MB can be streamed. In HTTP 3 it can be streamed in parallel. But none of those requests can start before the connection integrity is verified, otherwise you leak the intent of the request to a MITM agent. So you have head of line blocking on that 12k. And on mobile networking that comes with a lot of packet loss. If server certificates worked more like PGP you could probably avoid that, but that’s not how TLS works.
- remram 3y agoIf the web page is 2MB because it's loading ads, fonts, JavaScript libraries, images, cookie banners, trackers, etc each from a different domain or CDN... the problem is much bigger. This is 14k per connection...