HTTP/2
ELI5 — The Vibe Check
HTTP/2 is a supercharged version of HTTP. With HTTP/1.1, you could only ask for one thing at a time per connection. HTTP/2 lets you send many requests simultaneously over one connection, like sending multiple texts in parallel instead of waiting for each reply before sending the next.
Real Talk
HTTP/2 is a major revision of HTTP that introduces binary framing, multiplexing (multiple requests over one connection), header compression (HPACK), and server push. It dramatically reduces latency and improves page load performance, especially for resource-heavy pages.
When You'll Hear This
"Enable HTTP/2 on the Nginx server to improve page load times." / "HTTP/2 multiplexing eliminates the head-of-line blocking problem."
Related Terms
HTTP (HyperText Transfer Protocol)
HTTP is the language your browser uses to ask websites for stuff. You type a URL, your browser shouts 'hey, give me that page!
HTTP/3
HTTP/3 is the newest version of HTTP and it ditches TCP entirely in favor of QUIC.
HTTPS (HyperText Transfer Protocol Secure)
HTTPS is HTTP but with a bodyguard. All the data flying between your browser and the website is scrambled so nobody can spy on it.
QUIC (Quick UDP Internet Connections)
QUIC is Google's invention that takes the speed of UDP and adds the reliability of TCP, all while encrypting everything.
TLS Handshake (Transport Layer Security Handshake)
The TLS handshake is the 'hello, do we trust each other?' ceremony that happens before any HTTPS data flows.