3 ms·
I didn't know HTTP/2 had caught on. I thought the current meta was HTTP/1.1 by default, and HTTP/3 if you need it.
by 01HNNWZ0MV43FF 2y ago
I didn't know HTTP/2 had caught on. I thought the current meta was HTTP/1.1 by default, and HTTP/3 if you need it.
- Joker_vD 2y agoIt's all HTTP/1.1 at the application layer, still. The HTTP/2 and HTTP/3 are mostly a binary encoding scheme (to use on top of good old TLS on top of TCP) and a different transport protocol (on top of UDP instead of TCP), respectively, but their goal is to carry good old HTTP/1.1 messages around.
- wbl 2y agoNot exactly. HTTP now has multiple substrates some with different features and documents describe the mapping of HTTP onto each substrate.
- shanemhansen 2y agoIt depends on if your tools make it easy. For example in Go the default http client and server basically just enable HTTP/2 by default. My understanding is that bradfitz championed that.