Final answer:
The statement that HTTP drops connections after processing a request is true for HTTP/1.0, but with HTTP/1.1 and HTTP/2, persistent connections via 'keep-alive' feature allow multiple requests over the same connection.
Step-by-step explanation:
The statement that HTTP drops connections between client and server after processing a request is generally considered to be true. The HTTP/1.0 protocol utilizes a 'request-response' cycle, after which the connection is typically closed or 'dropped'. This behavior means that each request requires a new connection to be established between the client and the server, which can result in inefficiencies and increased load times for web pages requiring multiple requests.
However, with the evolution of HTTP, things changed slightly. The introduction of HTTP/1.1 included a feature known as 'keep-alive', allowing for persistent connections over which multiple requests can be sent. While this is true for HTTP/1.1 and newer protocols like HTTP/2, the foundational behavior of HTTP involving dropping connections after a request was still designed into HTTP/1.0, and earlier implementations of HTTP/1.1 where keep-alive was not explicitly stated.