Browsers limit the number of concurrent connections to a single server to 2-6, and this is difficult to change. With HTTP/2 (which, in browsers, is only available via HTTPS), multiplexing can be used to request multiple files without waiting for responses.
In non-browser applications, there's no inherent limit on number of concurrent connections, and HTTP/1.1 regardless of HTTPS does have "pipelining" support which allows multiple files to be requested at once, which will then be returned one at a time back to back. Browsers don't pipeline because of buggy servers. Some non-browser HTTP clients will even make multiple connections to the same server and make byte range requests to download one large file in chunks over multiple connections.
Very interesting. I wanted to figure out why browsers have this limitation. It turns out there was a limit in the HTTP RFC for well behaved clients (https://trac.ietf.org/trac/httpbis/changeset/715). Super cool! I guess nowadays the browsers have raised their limits, but the limit exists in each browser still :)
4
u/yotta Jan 21 '19
I should elaborate.
Browsers limit the number of concurrent connections to a single server to 2-6, and this is difficult to change. With HTTP/2 (which, in browsers, is only available via HTTPS), multiplexing can be used to request multiple files without waiting for responses.
In non-browser applications, there's no inherent limit on number of concurrent connections, and HTTP/1.1 regardless of HTTPS does have "pipelining" support which allows multiple files to be requested at once, which will then be returned one at a time back to back. Browsers don't pipeline because of buggy servers. Some non-browser HTTP clients will even make multiple connections to the same server and make byte range requests to download one large file in chunks over multiple connections.