🍌 BANANA HTTP 🍌

Each request is independent. The server retains no memory of previous interactions. Session state must be managed externally via cookies, tokens, or server-side sessions.

HTTP sits atop the OSI stack, relying on TCP (or QUIC for HTTP/3) for reliable transport. It defines the semantics of web communication, not the transmission mechanics.

HTTP/1.x uses human-readable ASCII messages. HTTP/2 introduced binary framing for efficiency, while HTTP/3 runs over QUIC/UDP.

Communication is always initiated by the client. The server cannot push data without a prior request in HTTP/1.x (server push was introduced in HTTP/2).