http2

I am building a webapp and serving it over http2. However when I analyze network in Google Chrome (Version 59.0.3071.115 (Official Build) (64-bit))'s developers tools, it is clear that multiplexing does not work as there are only 6 active connections (like with http1.1) and the rest of connections are queued. Why is this? Or are my expectations not correct? The screenshot (you can see that protocol is http2): Update #1: The backend runs on nginx 1.13; I am using custom modules loader which loads all the scripts at once (by creating script tag with async attribute in a loop); The screenshot

I understand that http2 uses one tcp connection to serve multiple requests, for example, if I request index.html which contains a.css and a.js, these three requests will be done in one tcp connection. What happens if user clicks index2.html? does this request still use the same previous tcp connection? If so, will the browser keep the connection open until user closes the browser? And on the server side, does the server keep many connections open all the time? When using HTTP/2, browsers typically open only one connection per domain. In your example, index2.html will be sent on the same TCP

I'm trying to debug difference between HTTP/1.1 and HTTP/2. Is there any possibility for disabling HTTP/2 in chrome or chromium? I couldn't find this option flag in chrome 56. I have tried chromium 58 with flag --disable-http2 : ./Chromium.app/Contents/MacOS/Chromium --disable-http2 But content is still delivered with HTTP/2 protocol after using this flag: For what it is worth, the flag works. The issue is that you need to quit EVERYTHING Chrome for it to take effect. Including plugin shims and other chrome tabs and so on. It is not enough just to add the command line switch. An easier way to

I am experimenting with migration to http/2. I have set up a Wordpress website and configured NGINX to serve it using http/2 (using SSL/TLS). My understanding of http/2 is that by default it uses one connection to transfer a number of files - rather than opening new connections and repeating SSL handshakes for each file. To achieve a similar effect for http/1.x, NGINX offered the keepalive directive. So does using the keepalive directive make sense when using http/2 exclusively? Checking my config files with "nginx -t" reports no errors when I include it. But does it have any effect?

The HTTP/2 specification indicates that any resource identified in a PUSH_PROMISE frame won't be pushed if the client cancels it. When a browser detects a resource already in the cache, it should cancel the push for this resource. However, I don't see how the browser can detect it. Do the frames provide additional informations like etag or last modified to allow the browser to detect if any cache entry must be evicted or if the push could be canceled? If it's possible, some bandwidth could be saved. However, it seems server-push compromises any client cache optimization. In HTTP/2 the server