The problem, if we can call it that, is that it fetches a single URL per TCP connection. To elaborate upon this, suppose a page has two images. The browser opens a connection and gets the HTML file first, closes the connection, opens a new connection and gets the first image, closes the connection, and so on. The goals of HTTP 1.1 are to reduce HTTP's impact on the Internet, make it a well-behaved protocol, and be as compatible as possible with HTTP 1.0. Persistent connections are the default behavior for HTTP 1.1.
Users experience a performance gain, and the network gains in overall efficiency.
Savings result in opening and closing of TCP connections, CPU time, and memory used for TCP control buffers. The OMI Web Server 1.1 implements HTTP 1.0. It supports more than 1,000 concurrent client connections. Access to the Web server can be controlled on the basis of such factors as hostname, time of day, username, browser, and version and authentication method. The Web server provides an enhanced log format that integrates each request's access, error, and security information.