| title | author | date | url | thumbnail | categories | ||
|---|---|---|---|---|---|---|---|
HTTP/2 for everyone |
svennd |
2016-02-01 20:46:28 +0000 |
/http2-for-everyone/ |
/img/2021/03/simon-stratford-_ILkd7aVqAM-unsplash.jpg |
|
After reading the slides of ma.ttias.be on http/2 I feel more interesses in the topic of http/2. While the presentation is aimed at PHP developers, I think most Linux users/sysadmins can pick something up of the presentation. I'm a bit ashamed I did not already knew about this, but hey, we learn everyday. Http/2 seems to be an enhancement of http/1.1 and certainly an upgrade on http/1. While i am clearly no expert on the topic, it goes like this :
- http/1 : header and TCP handshake are send for every request (request is : index / style.css / jquery.js / ...) There was an addition of keepalive to the protocol but it is not on by default
- http/1.1 : keepalive is on per default unless defined otherwise, now multiple requests can happen in one handshake. Although still restricted to 6-8 connections per domain. (meaning you can download 6-8 items at a time once the page is parsed)
- http/2 : keepalive is on by default and server can now send multiple files concurrent at once per connection line, headers are compressed saving space. Serverside pushes can happen (this is freaking awesome if working, one could send a css file while the page is not yet parsed by the client)
Be sure to check out ma.ttias.be's his slides those are really a good explanation :
Slides: HTTP/2 for PHP developers
All (?) browsers supporting http/2 also require https, but we know where to find that : lets encrypt. Although short, might be a good read for http/2 on wikipedia, here.