With respect to maintaining session state between requests, what type of…

Concept: State handling describes whether a protocol retains information about earlier client requests when processing a new one. A stateful protocol keeps such context on the server side across a sequence of requests; a stateless protocol treats every request independently, with no built-in memory of what came before. Application to HTTP: HTTP falls in the second category. Each HTTP request-response exchange is self-contained, so the server does not automatically recall anything about the client's earlier requests. This is exactly why applications that need to track a user across requests (logins, shopping carts) must add a session layer on top of HTTP, using mechanisms such as cookies or tokens, rather than relying on the protocol itself to remember. Cross-check / contrast: It is true that HTTP's name derives from 'HyperText Transfer Protocol', describing WHAT it moves (hypertext and web resources) between client and server -- but that naming/functional label is a separate classification axis from how it treats successive requests. So it does not change HTTP's stateless classification with respect to session handling, and it is not itself an answer to a question about session-state behavior.