Optimizing File Cacheing and HTTP2

Let’s clarify a few things: My understanding is that http2 renders optimization techniques like file concatenation obsolete, since a server using http2 just sends one request. HTTP/2 renders optimisation techniques like file concatenation somewhat obsolete since HTTP/2 allows many files to download in parallel across the same connection. Previously, in HTTP/1.1, the browser could request … Read more

Is the per-host connection limit raised with HTTP/2?

Browsers impose a per-domain limit of 6-8 connections when using HTTP/1.1, depending on the browser implementation. This allows at most 6-8 concurrent requests per domain. With HTTP/2, browsers open only 1 connection per domain. However, thanks to the multiplexing feature of the HTTP/2 protocol, the number of concurrent requests per domain is not limited to … Read more

Does HTTP/2 make websockets obsolete?

After just getting finished reading RFC 7540, HTTP/2 does obsolete websockets for all use cases except for pushing binary data from the server to a JS webclient. HTTP/2 fully supports binary bidi streaming (read on), but browser JS doesn’t have an API for consuming binary data frames and AFAIK such an API is not planned. … Read more

HTTP2 with node.js behind nginx proxy

In general, the biggest immediate benefit of HTTP/2 is the speed increase offered by multiplexing for the browser connections which are often hampered by high latency (i.e. slow round trip speed). These also reduce the need (and expense) of multiple connections which is a work around to try to achieve similar performance benefits in HTTP/1.1. … Read more

What does multiplexing mean in HTTP/2

Put simply, multiplexing allows your Browser to fire off multiple requests at once on the same connection and receive the requests back in any order. And now for the much more complicated answer… When you load a web page, it downloads the HTML page, it sees it needs some CSS, some JavaScript, a load of … Read more